Professional Documents
Culture Documents
PRTG Manual For Monitoring Paessler
PRTG Manual For Monitoring Paessler
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
15
16
18
19
21
23
32
33
36
44
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
77
81
83
88
90
91
92
93
94
95
98
100
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
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
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
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
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 Microsoft SQL Server 2012 Sensor
WMI Microsoft SQL Server 2014 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
2209
2217
2220
2227
2238
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
2433
2434
2437
2438
2445
2447
2449
2451
2453
2455
2457
2459
2461
2462
2465
2471
2478
2479
2482
2483
2486
2490
2491
2495
2498
2500
2502
2505
2507
2512
2514
2515
2524
2526
2536
2537
2560
2568
2569
2571
2572
Contents
4
5
6
7
8
9
10
11
12
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
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.
14
19.09.2014
1.1
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
15
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.
19.09.2014
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
1.3
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
1.4
Available Licenses
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.
Supports all available sensor types.
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
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
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
18.11.2014
21
More
Updat e From Previous Versions
47
22
18.11.2014
1.5.1
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
27
28
28
28
29
29
29
29
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
Sy st em
DELL Alienware
DELL PowerEdge
2900 III
CPU
RAM
8 GB
16 GB
1 GB
Windows 7 64-Bit
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
1 minute
1 minute
5 minutes
Number of Probes
3%
20 %
35 %
20 %
30 %
85 %
3 GB
3.5 GB
260 MB
800 GB
800 GB
55 GB
550 kbit/s
150 kbit/s
Operat ing Sy st em
Sensors
18.11.2014
* CPU load is higher while users are accessing the web interface.
Client OS
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
27
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.
28
18.11.2014
More
Updat e From Previous Versions
47
18.11.2014
29
30
18.11.2014
Part 2
Quick Start Guide
19.09.2014
31
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!
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.
32
33
36
19.09.2014
2.1
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
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
36
More
Video Tutorials for PRTG Network Monitor:
http://www.paessler.com/support/video_tutorials
19.09.2014
35
2.2
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
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
38
38
38
39
39
40
40
41
41
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
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.
38
19.09.2014
For a general introduction to the technology behind WMI, please see Monit oring via WMI
section.
2495
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.
19.09.2014
39
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.
2498
section.
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.
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.
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.
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.
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.
42
19.09.2014
Part 3
Installing the Software
19.09.2014
43
This section describes how to download and install your PRTG product.
PRTG Setup
45
51
56
57
60
62
44
47
67
71
19.09.2014
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
19.09.2014
45
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.
46
19.09.2014
3.2
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.
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.
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 .
More
Knowledge Base: How do I backup all data and configuration of my PRTG installation?
http://kb.paessler.com/en/topic/523
Knowledge Base: What about my web interface customizations as of PRTG 13.2.3?
http://kb.paessler.com/en/topic/44703
19.09.2014
49
50
19.09.2014
3.3
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.
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
52
19.09.2014
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.
Please choose the folder you wish to install the software in. We recommend using the default
value.
19.09.2014
53
As soon as you click Next , the necessary files will be copied to your disk.
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
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?
http://kb.paessler.com/en/topic/8063
Knowledge Base: How can I establish a secure web interface connection to PRTG?
http://kb.paessler.com/en/topic/273
Knowledge Base: PRTG blocks port 80 although I'm using SSL on port 443. How to free port
80?
http://kb.paessler.com/en/topic/5373
19.09.2014
55
3.4
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.
2602
More
Knowledge Base: What's the Clustering Feature in PRTG?
http://kb.paessler.com/en/topic/6403
56
19.09.2014
3.5
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.
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.
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.
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.
18.11.2014
59
3.6
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.
60
18.11.2014
More
Knowledge Base: Which servers does PRTG connect to for Software Auto-Update and for
Activation?
http://kb.paessler.com/en/topic/32513
18.11.2014
61
3.7
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.
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.
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.
62
19.09.2014
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
As soon as you click Next , the necessary files will be copied to your disk.
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
When asked if you want to start the probe service, confirm with Yes. The installation is
completed.
19.09.2014
65
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
3.8
51
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.
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
67
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.
As soon as you click Next , the necessary files will be copied to your disk.
19.09.2014
69
More
Please see section Ent erprise Console
User Interface (GUI).
70
2430
19.09.2014
3.9
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.
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.
Step 3
Confirm the removal of the software by clicking the Yes button.
19.09.2014
71
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?
http://kb.paessler.com/en/topic/27383
19.09.2014
73
Part 4
Understanding Basic Concepts
19.09.2014
75
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.
81
Object Hierarchy
83
Scheduling
Not ify ing
91
92
93
94
76
88
90
Dependencies
IPv6
77
95
98
19.09.2014
4.1
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
System Administration
Program
19.09.2014
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 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.
http://www.paessler.com/support/video_tutorials
80
19.09.2014
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.
2602
More
Knowledge Base: What's the Clustering Feature in PRTG?
18.11.2014
81
http://kb.paessler.com/en/topic/6403
82
18.11.2014
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 ).
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
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
20.11.2014
87
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).
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.
88
19.09.2014
228
19.09.2014
2227
for details.
89
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.
90
18.11.2014
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.
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
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.
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
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
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.
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.
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
94
19.09.2014
4.10
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.
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 .
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
Admin rights
Domain User
Read Only
96
19.09.2014
PRTG User
Read/Writ e
Read-only rights
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
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
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
102
105
108
121
130
124
133
137
141
143
146
Ticket s
148
158
155
159
162
163
174
175
192
2238
Related Topics
Ent erprise Console
2430
19.09.2014
2482
101
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.
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
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,
please see More 104 section below.
Click on the Login button to proceed to the PRTG web interface.
More
Knowledge Base: Why are Internet Explorer IE6 and IE7 not supported by PRTG's Ajax Interface?
http://kb.paessler.com/en/topic/7633
Knowledge Base: How can I access the AJAX web interface of PRTG with Internet Explorer 9 or
IE10?
http://kb.paessler.com/en/topic/46893
104
19.09.2014
5.2
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.
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.
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
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?
http://kb.paessler.com/en/topic/11813
Knowledge Base: Why can't I save my PRTG password in Google Chrome?
http://kb.paessler.com/en/topic/61982
18.11.2014
107
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
2421
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 .
108
18.11.2014
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.
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
Page Content
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
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.
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
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
'Breadcrumbs'
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.
112
18.11.2014
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 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
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
Sensor Status
Bar
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
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.
Collapsed Dev ic e With Summarized Ups and Unusuals and Indiv idual Downs
18.11.2014
115
116
18.11.2014
18.11.2014
117
Flag
Flag Color
Object St at us
Meaning
Red
Down
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
Orange
Unusual
Green
Up
Blue
Paused
Black (Grey)
Unknown
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).
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.
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:
Review Monit oring Dat a
18.11.2014
124
119
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?
http://kb.paessler.com/en/topic/24963
120
18.11.2014
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
18.11.2014
Bright-Red
Down
(Acknowledged)
121
Sensor
Color
St at us Name
Meaning
Yellow
Warning
Orange
Unusual
Green
Up
Blue
Paused
Black
(Gray)
Unknown
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)?
http://kb.paessler.com/en/topic/25643
18.11.2014
123
5.5
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.
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 .
20.11.2014
125
2 Day s Tab of a Firewall with Ov erv iew Graph and Sensor Mini Graphs
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
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.
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.
Graph 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?
http://kb.paessler.com/en/topic/313
20.11.2014
129
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.
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
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
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
5.7
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 .
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
133
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
File Format
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
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
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.
Up to 40 days
Any
40 to 500 days
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
Review Monit oring Dat a
Report s
124
2291
More
Knowledge Base: Why is there missing data in historical data reports?
http://kb.paessler.com/en/topic/61382
136
18.11.2014
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 .
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.
26.09.2014
137
SIMILAR SENSOR S
Similarity
Channel
Similar Channel
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
You can sort the list by clicking on the column headers. The similar sensors overview page
provides the following information:
Similarity
26.09.2014
139
Item Count
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
5.9
Object Settings
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.
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
228
Neuer Link
95
262
284
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
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
142
124
2240
18.11.2014
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.
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
ALAR MS
All
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
Warnings Only
Unusuals Only
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:
144
19.09.2014
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?
http://kb.paessler.com/en/topic/26303
19.09.2014
145
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.
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.
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 .
146
19.09.2014
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 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
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.
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
2263
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
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
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
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
102
105
108
121
130
124
133
137
141
143
146
Ticket s
148
158
159
162
163
174
19.09.2014
155
175
153
192
2238
Related Topics
Ent erprise Console
2430
154
2482
19.09.2014
5.13
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.
18.11.2014
155
FE DISPLAY
AT
U
RE
WHAT IT DOES
Pa
gin
g
Ne
w
Wi
nd
ow
Da
te
Ra
ng
e
Sel
ect
Ra
ng
e
156
Ite
ms
18.11.2014
Related Topics
Mult i-Edit List s
18.11.2014
2248
157
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.
158
19.09.2014
5.15
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.
Note: Select 4 or 5 stars for particular sensors to activate their gauges on device overview
pages.
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.
160
18.11.2014
18.11.2014
161
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
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.
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 .
162
19.09.2014
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
166
168
171
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.
244
2263
tab.
tab.
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
226
tab.
Pause
The pause menu will appear.
If the probe 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 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.
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.
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
166
20.11.2014
Set t ings...
This will open the Group Set t ings
Not ificat ions...
This will open the Not ificat ions
262
2263
tab.
tab.
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).
Sort Alphabet ically
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
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.
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
The historic data menu will appear.
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
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
168
20.11.2014
Set t ings...
This will open the Device Set t ings
284
tab.
2263
tab.
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 .
Sort Alphabet ically
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
detailed instructions, please see Clone Object 2246 .
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
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.
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
The historic data menu will appear.
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.
Go To Service URL...
This will open the service page you have defined in the Device Set t ings
284
170
20.11.2014
151
304
tab.
2263
tab.
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
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
detailed instructions, please see Clone Object 2246 .
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.
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.
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.
Priorit y /Favorit e
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
The historic data menu will appear.
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
View Hist oric Dat a... opens the Hist oric Dat a
133
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
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
20.11.2014
151
173
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.
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
5.19
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.
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 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
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
HOME
Dashboard 1
Dashboard 3
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.
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.
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
Add Group
178
18.11.2014
DEVICES
Add Device
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.
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
Select Library
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
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
Favorit e Sensors
159
180
18.11.2014
SENSOR S
Top 10 List s
By Current Value
By Current St at us
18.11.2014
181
SENSOR S
By Group
By Ty pe
By Tag
Cross Reference
Compare Sensors
Similar Sensors
Overview
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
ALAR MS
All
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
Warnings Only
Unusuals Only
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.
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
Select 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.
R EPOR TS
All
Open the Reports overview page where you can view or add
reports of your monitoring data.
Add Report
Select 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
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 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 .
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
SETU P
Overview
Open the My Account 2329 settings. Hover to show and open the
tabs of account settings directly. Choose from:
My Account
2327
2329
2334
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
User Groups
2379
2385
2390
18.11.2014
2372
2394
User Account s
PRTG St at us
2349
2396
2401
Clust er St at us
2416
187
SETU P
License
2418
2418
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
Choose from:
2421
2421
2421
2421
2421
2422
2423
PRTG API
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
Open the Help and Support Cent er to get help if you have any questions regarding your
PRTG setup.
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
189
Part 6
Ajax Web InterfaceDevice and Sensor Setup
19.09.2014
191
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 device and sensor setup in the Ajax Graphical User Interface
(GUI).
194
208
226
228
244
262
284
304
2217
2220
192
305
2227
19.09.2014
100
2238
Related Topics
Ent erprise Console
2430
19.09.2014
2482
193
6.1
Auto-Discovery
36
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
108
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.
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.
19.09.2014
195
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.
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
Device Template(s)
19.09.2014
197
198
19.09.2014
IPv4 Base
19.09.2014
199
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.
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
200
19.09.2014
Name Resolution
Device Rescan
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!
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
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
credentials with administrator privileges.
Enter a login name for the access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Login
Password
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
Monit oring via SSH 2498 .
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
relevant when using WBEM sensors. Choose between:
19.09.2014
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.
Target Username
Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password
19.09.2014
203
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
Authentication Type
204
19.09.2014
Password
Encryption Type
Context Name
SNMP Port
19.09.2014
205
Name
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
Password
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
Video Tutorial: There is a video available on the Paessler video tutorials page.
http://www.paessler.com/support/video_tutorials
19.09.2014
207
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
6.2
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
208
2588
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
1 Add a Group
6.2.1
Add a Group
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.
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.
St ep 2
Add group settings as described below.
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 .
19.09.2014
209
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
1 Add a Group
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.
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
credentials with administrator privileges.
Enter a login name for the access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Login
Password
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
Monit oring via SSH 2498 .
210
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
1 Add a Group
Define the port that will be used for WBEM. This setting is only
relevant when using WBEM sensors. Choose between:
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
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.
Target Username
19.09.2014
211
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
1 Add a Group
Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password
VMware Protocol
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
212
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
1 Add a Group
User
Password
Encryption Type
Context Name
SNMP Port
19.09.2014
213
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
1 Add a Group
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!
214
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
2 Add a Device
6.2.2
Add a Device
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.
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.
St ep 2
Add device settings as described below.
IP Version
19.09.2014
215
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
2 Add a Device
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
automatically inherited 90 .
Device Icon
Choose a device icon from the list. It will be shown in the device
tree.
DEVICE TYPE
Sensor Management
Discovery Schedule
216
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
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)
19.09.2014
217
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
2 Add a Device
DEVICE TYPE
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.
218
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
2 Add a Device
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.
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
credentials with administrator privileges.
Enter a login name for the access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Login
Password
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
Monit oring via SSH 2498 .
19.09.2014
219
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
2 Add a Device
Define the port that will be used for WBEM. This setting is only
relevant when using WBEM sensors. Choose between:
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
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.
Target Username
220
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
2 Add a Device
Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password
VMware Protocol
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
19.09.2014
221
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
2 Add a Device
User
Password
Encryption Type
Context Name
SNMP Port
222
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
2 Add a Device
ACCESS R IGHTS
User Group Access
Define which user group(s) will have access to the object you're
editing. A table with user groups and 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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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!
19.09.2014
223
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
3 Add a Sensor
6.2.3
Add a Sensor
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.
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.
224
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
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?
http://kb.paessler.com/en/topic/59788
19.09.2014
225
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 3 Manage Device Tree
6.3
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
226
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 3 Manage Device Tree
2250
Related Topics
For other ways to arrange objects, please see
Arrange Object s
2245
19.09.2014
2253
2246
227
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
6.4
On the Root group's overview page, click on the Set t ings tab to change settings.
BASIC GR OU P SETTINGS
Group Name
Status
228
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
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.
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.
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
credentials with administrator privileges.
19.09.2014
Enter a login name for the access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
229
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
Password
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
Monit oring via SSH 2498 .
For WBEM Use Protocol Define the protocol that will be used for WBEM. This setting is only
relevant when using WBEM sensors. Choose between:
HTTP: Use an unencrypted connection for WBEM.
HTTPS: Use an SSL-encrypted connection for WBEM.
For WBEM Use Port
Define the port that will be used for WBEM. This setting is only
relevant when using WBEM sensors. Choose between:
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
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.
230
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
Target Username
Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password
VMware Protocol
19.09.2014
Select the SNMP version that will be used for device connection.
231
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
Authentication Type
User
Password
232
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
Context Name
SNMP Port
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
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
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.
Failed Requests
234
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
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.
We recommend using the default value. If you experience
problems, change this option.
32-bit/64-bit Counters
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
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
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
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
Start Port
For SNMP Traffic sensors, define at which port number PRTG will
start to create sensors. Use 0 for automatic. We recommend using
the default value.
End Port
For SNMP Traffic sensors, define at which port number PRTG will
stop to create sensors. Use 0 for automatic. We recommend using
the default value.
19.09.2014
237
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
Name
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
Password
238
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
Maintenance Window
Maintenance Begins At
Maintenance End At
240
244
, Group Settings
262
, Device
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
Similar Sensors
Detection
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 does PRTG compute CPU Index, Traffic Index and Response Time Index?
http://kb.paessler.com/en/topic/313
Knowledge Base: How can I add my own device icons for use in the PRTG web interface?
http://kb.paessler.com/en/topic/7313
242
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
Knowledge Base: How can I change the defaults for names automatically generated for new
SNMP sensors?
http://kb.paessler.com/en/topic/7363
Knowledge Base: Automatically update port name and number for SNMP Traffic sensors when
the device changes them
http://kb.paessler.com/en/topic/25893
19.09.2014
243
6.5
Probe Settings
On a probe's overview page, click on the Set t ings tab to change settings.
2588
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
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.
Tags
Enter one or more tags; confirm each tag by hitting space, comma,
or enter key. You can use tags to group objects and use tagfiltered views later on. Tags are not case sensitive.
Status
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
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.
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.
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.
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
credentials with administrator privileges.
19.09.2014
245
Enter a login name for the access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Login
Password
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
Monit oring via SSH 2498 .
For WBEM Use Protocol Define the protocol that will be used for WBEM. This setting is only
relevant when using WBEM sensors. Choose between:
HTTP: Use an unencrypted connection for WBEM.
HTTPS: Use an SSL-encrypted connection for WBEM.
For WBEM Use Port
Define the port that will be used for WBEM. This setting is only
relevant when using WBEM sensors. Choose between:
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
246
19.09.2014
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.
Target Username
Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password
VMware Protocol
19.09.2014
247
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
Authentication Type
User
Password
248
19.09.2014
Context Name
SNMP Port
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:
249
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.
Failed Requests
250
19.09.2014
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.
We recommend using the default value. If you experience
problems, change this option.
32-bit/64-bit Counters
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
251
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.
252
19.09.2014
Start Port
For SNMP Traffic sensors, define at which port number PRTG will
start to create sensors. Use 0 for automatic. We recommend using
the default value.
End Port
For SNMP Traffic sensors, define at which port number PRTG will
stop to create sensors. Use 0 for automatic. We recommend using
the default value.
19.09.2014
253
Name
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
Password
254
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
255
Maintenance Window
Maintenance Begins At
Maintenance Ends At
Dependency Type
256
19.09.2014
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
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
258
19.09.2014
Similar Sensors
Detection
19.09.2014
259
Restart Schedule
Specify Day
260
19.09.2014
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 does PRTG compute CPU Index, Traffic Index and Response Time Index?
http://kb.paessler.com/en/topic/313
Knowledge Base: How can I add my own device icons for use in the PRTG web interface?
http://kb.paessler.com/en/topic/7313
Knowledge Base: How can I change the defaults for names automatically generated for new
SNMP sensors?
http://kb.paessler.com/en/topic/7363
Knowledge Base: Automatically update port name and number for SNMP Traffic sensors when
the device changes them
http://kb.paessler.com/en/topic/25893
19.09.2014
261
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.
We recommend defining as many settings as possible in the Root
them to all other objects further down in the tree hierarchy.
228
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.
BASIC GR OU P SETTINGS
Group Name
Status
Tags
262
Enter one or more tags; confirm each tag by hitting space, comma,
or enter key. You can use tags to group objects and use tagfiltered views later on. Tags are not case sensitive.
19.09.2014
BASIC GR OU P SETTINGS
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
Device Template(s)
19.09.2014
263
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)
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)
264
19.09.2014
IP Selection Method
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
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
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.
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
266
19.09.2014
Device Rescan
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.
19.09.2014
267
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.
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.
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
credentials with administrator privileges.
268
Enter a login name for the access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
19.09.2014
Password
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
Monit oring via SSH 2498 .
For WBEM Use Protocol Define the protocol that will be used for WBEM. This setting is only
relevant when using WBEM sensors. Choose between:
HTTP: Use an unencrypted connection for WBEM.
HTTPS: Use an SSL-encrypted connection for WBEM.
For WBEM Use Port
Define the port that will be used for WBEM. This setting is only
relevant when using WBEM sensors. Choose between:
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
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.
19.09.2014
269
Target Username
Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password
VMware Protocol
270
Select the SNMP version that will be used for device connection.
19.09.2014
Authentication Type
User
Password
19.09.2014
271
Context Name
SNMP Port
272
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:
19.09.2014
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.
Failed Requests
19.09.2014
273
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.
We recommend using the default value. If you experience
problems, change this option.
32-bit/64-bit Counters
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.
274
19.09.2014
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.
19.09.2014
275
Start Port
For SNMP Traffic sensors, define at which port number PRTG will
start to create sensors. Use 0 for automatic. We recommend using
the default value.
End Port
For SNMP Traffic sensors, define at which port number PRTG will
stop to create sensors. Use 0 for automatic. We recommend using
the default value.
276
19.09.2014
Name
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
Password
19.09.2014
277
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
278
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance Ends At
Dependency Type
19.09.2014
279
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.
280
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
281
Similar Sensors
Detection
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
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!
282
19.09.2014
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 does PRTG compute CPU Index, Traffic Index and Response Time Index?
http://kb.paessler.com/en/topic/313
Knowledge Base: How can I add my own device icons for use in the PRTG web interface?
http://kb.paessler.com/en/topic/7313
Knowledge Base: How can I change the defaults for names automatically generated for new
SNMP sensors?
http://kb.paessler.com/en/topic/7363
Knowledge Base: Automatically update port name and number for SNMP Traffic sensors when
the device changes them
http://kb.paessler.com/en/topic/25893
19.09.2014
283
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.
We recommend defining as many settings as possible in the Root
them to all other objects further down in the tree hierarchy.
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.
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.
Status
IP Version
284
19.09.2014
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. 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).
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
DEVICE TYPE
Sensor Management
19.09.2014
285
DEVICE TYPE
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
Device Template(s)
286
19.09.2014
DEVICE TYPE
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
19.09.2014
287
DEVICE TYPE
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.
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.
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.
288
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.
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
credentials with administrator privileges.
Enter a login name for the access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Login
Password
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
Monit oring via SSH 2498 .
19.09.2014
289
Define the port that will be used for WBEM. This setting is only
relevant when using WBEM sensors. Choose between:
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
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.
Target Username
290
19.09.2014
Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password
VMware Protocol
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
19.09.2014
291
User
Password
Encryption Type
Context Name
SNMP Port
292
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:
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.
19.09.2014
293
Failed Requests
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.
We recommend using the default value. If you experience
problems, change this option.
32-bit/64-bit Counters
294
19.09.2014
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.
We recommend using the default value. If you experience
problems, change this option.
19.09.2014
295
Define how PRTG will react if you change port names in your
physical device (e.g. a switch or router). Choose between:
Keep port names (use t his if y ou edit t he names in PRTG): Do
not automatically adjust sensor names. This is the best option if
you want to change names in PRTG manually.
Aut omat ic sensor name updat e if name changes in device: If
PRTG detects changes of port names in your physical device, it
will try to automatically adjust sensor names accordingly. For
detailed information please see More section below.
Port Identification
Start Port
For SNMP Traffic sensors, define at which port number PRTG will
start to create sensors. Use 0 for automatic. We recommend using
the default value.
End Port
For SNMP Traffic sensors, define at which port number PRTG will
stop to create sensors. Use 0 for automatic. We recommend using
the default value.
296
19.09.2014
Name
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
Password
19.09.2014
297
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
298
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance Ends At
Dependency Type
19.09.2014
299
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.
300
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
301
Similar Sensors
Detection
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 does PRTG compute CPU Index, Traffic Index and Response Time Index?
http://kb.paessler.com/en/topic/313
Knowledge Base: How can I add my own device icons for use in the PRTG web interface?
http://kb.paessler.com/en/topic/7313
302
19.09.2014
Knowledge Base: How can I change the defaults for names automatically generated for new
SNMP sensors?
http://kb.paessler.com/en/topic/7363
Knowledge Base: Automatically update port name and number for SNMP Traffic sensors when
the device changes them
http://kb.paessler.com/en/topic/25893
19.09.2014
303
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.
304
2217
2220
304
305
2227
19.09.2014
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
306
306
307
310
311
311
312
312
313
313
314
315
316
309
316
322
Common Sensors
HTTP Sensor
553
Ping Sensor
948
Port Sensor
986
994
1611
1753
18.11.2014
1901
305
350
741
751
770
780
846
856
865
875
907
916
1094
1103
1169
1183
1412
1503
1557
1611
1901
545
553
562
584
593
604
613
620
306
575
629
18.11.2014
638
647
659
1753
1867
SNMP Sensors
SNMP APC Hardware Sensor
SNMP Cisco ADSL Sensor
1161
1169
1183
1191
1198
1205
1213
1221
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
1405
1412
1423
1433
1440
1447
1455
1463
1471
1480
1487
1495
1511
1518
1533
1541
1549
1557
1572
1580
1596
1604
1611
1621
1565
1588
1503
1526
1373
1632
18.11.2014
432
932
940
1851
1859
323
940
1843
1884
1892
1901
1909
1935
1943
1917
1926
1952
1961
1986
1996
2006
2015
2024
2032
2043
2052
2060
2068
2080
18.11.2014
1969
1977
1876
309
2113
2091
2121
2129
2138
2147
2155
2169
2162
2176
2184
2201
2209
Linux/Unix/OS X Sensors
SNMP Linux Disk Free Sensor
1423
1440
1656
1664
1672
1680
1724
1734
1688
1697
1706
310
1447
1645
1433
1715
1835
18.11.2014
341
365
373
423
681
688
672
697
706
1058
1067
1744
1790
1797
1803
1810
1818
1826
442
450
459
467
714
733
969
977
1134
18.11.2014
475
1142
1151
311
1753
2006
2015
1851
1859
332
795
804
817
824
MySQL v2 Sensor
833
884
894
1001
2068
2080
2091
2102
391
504
512
520
528
536
726
1112
1119
312
399
1463
18.11.2014
1471
1480
1487
1503
1511
1776
2024
2032
2184
408
416
789
948
761
956
963
986
994
1035
RADIUS v2 Sensor
1042
1051
1621
1639
1760
1753
1783
358
1126
18.11.2014
1020
313
1027
1198
391
423
1161
1205
1213
1221
399
1229
1236
1262
1270
1278
1286
1294
1301
1309
1325
1333
1341
1349
1365
1405
1412
1455
1480
314
1381
1397
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
963
1076
1103
1243
1252
1724
1835
1977
18.11.2014
916
1986
315
381
385
1014
1771
332
341
(v7)
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)
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)
350
(v7)
DHCP Sensor
(v8.3.0)
(v8.1.0)
323
520
512
(v7)
(v7)
18.11.2014
FTP Sensor
(v7)
528
(v8.3.0)
536
(v12.x.1)
545
(v7)
553
(v7)
562
575
(v12.x.3)
(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)
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
875
(v7)
(v7)
884
(v7)
(v7)
865
856
(v14.x.13)
894
907
(v7)
916
(v7)
932
(v12.x.3)
(v12.x.6)
(v8.3.0)
956
(v8.4.0)
963
(v7)
969
940
(v7)
948
POP3 Sensor
(v13.x.4)
925
977
(v8.3.0)
(v7)
986
(v12.x.4)
994
PostgreSQL Sensor
1001
(v14.x.12)
1014
(v9.1.0)
1020
1035
RADIUS v2 Sensor
1042
1058
1051
(v7)
(v12.x.6)
1076
1067
(v12.x.6)
(v7)
(v7)
1103
(v7)
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
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
(v13.x.8)
1405
(v13.x.8)
319
(v7)
1412
(v8.1.0)
1423
(v8.1.0)
1440
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)
(v14.x.11)
1526
1541
(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
1611
1621
(v7)
1632
(v13.x.8)
(v8.1.0)
(v8.1.0)
1645
1656
1672
(v8.1.1)
1664
(v8.1.0)
(v8.1.0)
(v13.x.4)
(v7)
1604
1596
(v7)
SNTP Sensor
(v13.x.4)
1680
(v12.x.1)
18.11.2014
(v14.x.12)
1688
(v14.1.9)
1697
1724
1734
(v12.x.6)
(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)
1835
(v12.x.1)
(v8.1.0)
1843
(v7)
1867
(v8.1.0)
1859
(v12.x.1)
1909
1943
1917
1926
(v8.3.0)
(v7)
(v9.1.0)
(v8.3.0)
(v7)
(v9.1.0)
1892
(v12.x.4)
1901
(v8.3.0)
(v8.3.0)
1884
1876
1952
1961
(v9.1.1)
(v8.1.0)
321
1977
1986
(v12.x.4)
(v7)
1996
2006
(v7.1.1)
2024
(v13.x.6)
(v7)
1969
2015
(v12.x.1)
(v7)
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
(v12.x.1)
2121
(v9)
(v7)
2129
(v8.1.0)
2138
2147
(v12.x.1)
2155
(v8.1.0)
2169
2184
2176
(v7)
(v7)
(v8.1.0)
(v9.2.0)
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
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.
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
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.
Tags
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).
324
18.11.2014
SENSOR SETTINGS
Replication Neighbor
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
Chart Type
18.11.2014
325
SENSOR DISPLAY
Stack Unit
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.
326
18.11.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
18.11.2014
327
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
328
18.11.2014
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 sensor 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. 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
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
330
18.11.2014
More
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
331
6.8.3
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
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.
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.
Tags
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).
332
19.09.2014
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
Record Count
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
Condition "Warning"
Value
Condition "Down"
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
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
335
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
336
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
337
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 sensor 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. 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 .
338
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Monitoring (Almost) Any SQL Server Through ADO with PRTG Network
Monitor
http://kb.paessler.com/en/topic/2053
Knowledge Base: How do I correctly configure credentials for ADO SQL sensors?
http://kb.paessler.com/en/topic/13103
19.09.2014
339
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
For more general information about settings, please see Object Set t ings
340
141
section.
19.09.2014
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.
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.
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.
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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.
342
18.11.2014
Tags
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).
AMAZON CR EDENTIALS
AWS Access Key ID
Region
18.11.2014
343
Instance
Topic Name
Availability Zone
SENSOR DISPLAY
Primary Channel
Chart Type
344
18.11.2014
SENSOR DISPLAY
Stack Unit
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.
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.
Maintenance Window
18.11.2014
345
Maintenance End At
Dependency Type
Dependency
346
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 sensor will be
dependent on.
18.11.2014
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. 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 .
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
18.11.2014
347
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.
More
Knowledge Base: How do I define access rights for Amazon CloudWatch queries?
http://kb.paessler.com/en/topic/38083
Knowledge Base: How much does Amazon charge for using the CloudWatch API?
http://kb.paessler.com/en/topic/37543
Knowledge Base: Why can't I use EU Frankfurt as region for my Amazon CloudWatch sensor?
http://kb.paessler.com/en/topic/61916
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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.
348
18.11.2014
Others
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
349
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
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.
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.
350
18.11.2014
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).
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
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.
18.11.2014
351
DEBU G OPTIONS
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received from the sensor to the
"Logs (Sensor)" directory (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
Chart Type
Stack Unit
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.
352
18.11.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
18.11.2014
353
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
354
18.11.2014
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 sensor 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. 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
355
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
356
18.11.2014
More
Knowledge Base: How do I activate UPnP for my Fritz!Box?
http://kb.paessler.com/en/topic/38603
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
357
6.8.6
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
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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. 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
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.
Tags
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).
IP SLA SPECIFIC
ID
Type
Name (Tag)
Owner
Frequency
19.09.2014
359
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
360
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
361
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
362
19.09.2014
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 sensor 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. 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 .
19.09.2014
363
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
364
141
section.
19.09.2014
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.
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.
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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.
Tags
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).
366
18.11.2014
HOST SETTINGS
UUID
Name
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
18.11.2014
367
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
368
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
369
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 sensor 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. 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 .
370
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
Knowledge Base: Does PRTG impair my Citrix environment?
http://kb.paessler.com/en/topic/61880
18.11.2014
371
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
For more general information about settings, please see Object Set t ings
372
141
section.
18.11.2014
6.8.8
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.
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.
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.
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
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
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.
Tags
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).
374
18.11.2014
Name
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
18.11.2014
375
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
376
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
377
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 sensor 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. 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 .
378
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
Knowledge Base: Does PRTG impair my Citrix environment?
http://kb.paessler.com/en/topic/61880
18.11.2014
379
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
For more general information about settings, please see Object Set t ings
380
141
section.
18.11.2014
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
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.
Tags
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).
SENSOR DISPLAY
Primary Channel
19.09.2014
381
SENSOR DISPLAY
Chart Type
Stack Unit
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.
382
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
383
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
384
141
section.
19.09.2014
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.
18.11.2014
385
Tags
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).
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
386
18.11.2014
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.
18.11.2014
387
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
388
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
389
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
For more general information about settings, please see Object Set t ings
390
141
section.
18.11.2014
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
SENSOR SETTINGS
Virtual Disks
Select the disks 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.
26.09.2014
391
Tags
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).
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
reference purposes only. If you need to change this, please add
the sensor anew.
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
392
26.09.2014
SENSOR DISPLAY
Chart Type
Stack Unit
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.
26.09.2014
393
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
394
26.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
26.09.2014
395
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 sensor 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. 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 .
396
26.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
26.09.2014
397
More
Where do I find the Dell PowerVault Modular Disk Storage Manager for use with my MDi SAN?
http://kb.paessler.com/en/topic/38743
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
For more general information about settings, please see Object Set t ings
398
141
section.
26.09.2014
"Mode" Channel
Descript ion
Unassigned (status:
up)
Assigned
Unassigned
Hot Spare In Use
Hot Spare Standby
Replaced (status: up)
Assigned
Pending Failure
(status: down)
Assigned
Unassigned
Hot Spare In Use
Hot Spare Standby
None (status:
warning)
26.09.2014
399
"Mode" Channel
Descript ion
Undefined (status:
down)
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
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.
To monitor physical 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
SENSOR SETTINGS
Physical Disks
Select the disks 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.
400
26.09.2014
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.
Tags
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).
SENSOR SETTINGS
Physical Disks
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.
26.09.2014
401
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
402
26.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
26.09.2014
403
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
404
26.09.2014
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 sensor 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. 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 .
26.09.2014
405
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
406
26.09.2014
More
Where do I find the Dell PowerVault Modular Disk Storage Manager for use with my MDi SAN?
http://kb.paessler.com/en/topic/38743
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
For more general information about settings, please see Object Set t ings
26.09.2014
141
section.
407
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 DHCP servers, PRTG will create one sensor for each network interface 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:
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
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.
408
19.09.2014
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).
DHCP SPECIFIC
MAC
Client IP
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.
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
DHCP SPECIFIC
Server IP
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.
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)
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
410
19.09.2014
DHCP SPECIFIC
Note: Regardless of this setting, those entries will always be added
to the sensor Log.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
411
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
412
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
413
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 sensor 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. 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 .
414
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
415
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.
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.
Tags
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).
DNS SPECIFIC
Timeout (Sec.)
416
19.09.2014
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
Write Result
Define what PRTG will do with the result of the sensor. Choose
between:
19.09.2014
417
DNS SPECIFIC
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
Chart Type
Stack Unit
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.
418
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
419
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
420
19.09.2014
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 sensor 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. 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 .
19.09.2014
421
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
422
141
section.
19.09.2014
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.
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
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
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:
EVA SETTINGS
Modules
Select the modules 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.
Tags
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).
424
19.09.2014
EVA CR EDENTIALS
Username
Password
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
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.
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received to the "Logs (Sensors)"
directory (on the Master node, if in a cluster). This is for
debugging purposes. The file will be overridden with each
scanning interval. For information on how to find the folder used
for storage, please see Dat a St orage 2611 section.
SENSOR DISPLAY
Primary Channel
Chart Type
19.09.2014
425
SENSOR DISPLAY
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).
Stack Unit
426
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
427
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
428
19.09.2014
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 sensor 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. 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 .
19.09.2014
429
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
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?
http://kb.paessler.com/en/topic/55983
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
431
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.
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.
Tags
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).
432
19.09.2014
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
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.
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
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
this option, this sensor processes only messages that match the
defined value. Choose between:
Off: Do not filter by event category.
On: Enable filtering by event category.
Filter by User
Filter all received events for a certain event user. If you enable this
option, this sensor processes only messages that match the
defined value. Choose between:
Off: Do not filter by event user.
On: Enable filtering by event user.
Filter by Computer
Filter all received events for a certain event computer. If you enable
this option, this sensor processes only messages that match the
defined value. Choose between:
Off: Do not filter by event computer.
On: Enable filtering by event computer.
434
19.09.2014
Filter all received events for a certain event message. If you enable
this option, this sensor processes only messages that match the
defined value. Choose between:
Off: Do not filter by event message.
On: Enable filtering by event message.
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
Stack Unit
19.09.2014
435
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.
436
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
437
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
438
19.09.2014
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 sensor 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. 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 .
19.09.2014
439
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My Event Log sensor ignores changes in the event log. What can I do?
http://kb.paessler.com/en/topic/59803
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.
440
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
441
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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.
Tags
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).
SENSOR SETTINGS
Database
Sensor Result
Define what will be done with the results the sensor receives.
Choose between:
19.09.2014
443
SENSOR SETTINGS
Discard sensor result : Do not store the results.
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received to the "Logs (Sensors)"
directory (on the Master node, if in a cluster). This is for
debugging purposes. The file will be overridden with each
scanning interval. For information on how to find the folder used
for storage, please see Dat a St orage 2611 section.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
444
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
445
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
446
19.09.2014
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 sensor 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. 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 .
19.09.2014
447
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Resolving Exchange PowerShell Sensors Issues
http://kb.paessler.com/en/topic/54353
Knowledge Base: How do I enable and use remote commands in Windows PowerShell?
http://kb.paessler.com/en/topic/44453
Knowledge Base: My Powershell sensor returns an error message. What can I do?
http://kb.paessler.com/en/topic/59473
Knowledge Base: "No Logon Servers Available" when Using PowerShell Sensors
http://kb.paessler.com/en/topic/59745
Knowledge Base: How can I increase memory for Remote PowerShell?
448
19.09.2014
http://kb.paessler.com/en/topic/61922
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
449
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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.
Tags
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).
SENSOR SETTINGS
Database
AutoRemount
Database
19.09.2014
451
SENSOR SETTINGS
Try t o remount
Just report t he current reading, keep unmount ed if so
Sensor Result
Define what will be done with the results the sensor receives.
Choose between:
Discard sensor result : Do not store the results.
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received to the "Logs (Sensors)"
directory (on the Master node, if in a cluster). This is for
debugging purposes. The file will be overridden with each
scanning interval. For information on how to find the folder used
for storage, please see Dat a St orage 2611 section.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
452
19.09.2014
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.
19.09.2014
453
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
454
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
455
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 sensor 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. 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 .
456
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Resolving Exchange PowerShell Sensors Issues
http://kb.paessler.com/en/topic/54353
Knowledge Base: How do I enable and use remote commands in Windows PowerShell?
http://kb.paessler.com/en/topic/44453
Knowledge Base: My Powershell sensor returns an error message. What can I do?
http://kb.paessler.com/en/topic/59473
Knowledge Base: "No Logon Servers Available" when Using PowerShell Sensors
http://kb.paessler.com/en/topic/59745
Knowledge Base: How can I increase memory for Remote PowerShell?
19.09.2014
457
http://kb.paessler.com/en/topic/61922
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
For more general information about settings, please see Object Set t ings
458
141
section.
19.09.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
19.09.2014
459
SENSOR SETTINGS
Mailboxes to be
monitored
Select the mailboxes 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.
Tags
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).
SENSOR SETTINGS
Mailbox Name
Sensor Result
Define what will be done with the results the sensor receives.
Choose between:
460
19.09.2014
SENSOR SETTINGS
Discard sensor result : Do not store the results.
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received to the "Logs (Sensors)"
directory (on the Master node, if in a cluster). This is for
debugging purposes. The file will be overridden with each
scanning interval. For information on how to find the folder used
for storage, please see Dat a St orage 2611 section.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
461
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
462
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
463
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 sensor 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. 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 .
464
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Resolving Exchange PowerShell Sensors Issues
http://kb.paessler.com/en/topic/54353
Knowledge Base: How do I enable and use remote commands in Windows PowerShell?
http://kb.paessler.com/en/topic/44453
Knowledge Base: My Powershell sensor returns an error message. What can I do?
http://kb.paessler.com/en/topic/59473
Knowledge Base: "No Logon Servers Available" when Using PowerShell Sensors
http://kb.paessler.com/en/topic/59745
Knowledge Base: How can I increase memory for Remote PowerShell?
19.09.2014
465
http://kb.paessler.com/en/topic/61922
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
For more general information about settings, please see Object Set t ings
466
141
section.
19.09.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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.
Tags
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).
SENSOR SETTINGS
Sensor Result
Define what will be done with the results the sensor receives.
Choose between:
Discard sensor result : Do not store the results.
468
19.09.2014
SENSOR SETTINGS
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received to the "Logs (Sensors)"
directory (on the Master node, if in a cluster). This is for
debugging purposes. The file will be overridden with each
scanning interval. For information on how to find the folder used
for storage, please see Dat a St orage 2611 section.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
469
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
470
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
471
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 sensor 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. 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 .
472
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Resolving Exchange PowerShell Sensors Issues
http://kb.paessler.com/en/topic/54353
Knowledge Base: How do I enable and use remote commands in Windows PowerShell?
http://kb.paessler.com/en/topic/44453
Knowledge Base: My Powershell sensor returns an error message. What can I do?
http://kb.paessler.com/en/topic/59473
Knowledge Base: "No Logon Servers Available" when Using PowerShell Sensors
http://kb.paessler.com/en/topic/59745
Knowledge Base: How can I increase memory for Remote PowerShell?
19.09.2014
473
http://kb.paessler.com/en/topic/61922
Knowledge Base: Types of Transport Queues in Microsoft Exchange
http://kb.paessler.com/en/topic/55413
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
For more general information about settings, please see Object Set t ings
474
141
section.
19.09.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
19.09.2014
475
SENSOR SETTINGS
Public Folder
Select the folders 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.
Tags
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).
SENSOR SETTINGS
Public Folder
Sensor Result
Define what will be done with the results the sensor receives.
Choose between:
476
19.09.2014
SENSOR SETTINGS
Discard sensor result : Do not store the results.
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received to the "Logs (Sensors)"
directory (on the Master node, if in a cluster). This is for
debugging purposes. The file will be overridden with each
scanning interval. For information on how to find the folder used
for storage, please see Dat a St orage 2611 section.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
477
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
478
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
479
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 sensor 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. 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 .
480
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Resolving Exchange PowerShell Sensors Issues
http://kb.paessler.com/en/topic/54353
Knowledge Base: How do I enable and use remote commands in Windows PowerShell?
http://kb.paessler.com/en/topic/44453
Knowledge Base: My Powershell sensor returns an error message. What can I do?
http://kb.paessler.com/en/topic/59473
Knowledge Base: "No Logon Servers Available" when Using PowerShell Sensors
http://kb.paessler.com/en/topic/59745
Knowledge Base: How can I increase memory for Remote PowerShell?
19.09.2014
481
http://kb.paessler.com/en/topic/61922
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
For more general information about settings, please see Object Set t ings
482
141
section.
19.09.2014
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
19.09.2014
483
SENSOR SETTINGS
Script
Value Type
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
On the sensor's details page, click on the Set t ings tab to change settings.
484
19.09.2014
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.
Tags
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).
SENSOR SETTINGS
EXE/Script
Parameters
Environment
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.)
Value Type
If Value Changes
486
19.09.2014
SENSOR SETTINGS
EXE Result
Define what will be done with the result the executable file gives
back. Choose between:
Discard EX E result : Do not store the requested web page.
Writ e EX E result t o disk: Store the last result received from the
script with the file name "Result of Sensor [ID].txt" to the "Logs
(Sensors)" directory (on the Master node, if in a cluster). This is
for debugging purposes. The file will be overridden with each
scanning interval. For information on how to find the folder used
for storage, please see Dat a St orage 2611 section.
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
Stack Unit
19.09.2014
487
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.
488
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
489
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
490
19.09.2014
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 sensor 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. 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 .
19.09.2014
491
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
492
19.09.2014
More
Information about custom scripts and executables
Applicat ion Programming Int erface (API) Definit ion
Addit ional Sensor Ty pes (Cust om Sensors)
2571
2217
Knowledge Base: What is the Mutex Name in PRTG's EXE/Script Sensor's settings?
http://kb.paessler.com/en/topic/6673
Knowledge Base: How and Where Does PRTG Store its Data?
http://kb.paessler.com/en/topic/463
Knowledge Base: How can I test if parameters are correctly transmitted to my script when
using an EXE/Script sensor?
http://kb.paessler.com/en/topic/11283
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
493
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
SENSOR SETTINGS
EXE/Script
494
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
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.
Tags
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).
SENSOR SETTINGS
EXE/Script
19.09.2014
495
Parameters
Environment
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
503 section below. Please enter a string or leave the field empty.
Timeout (Sec.)
EXE Result
Define what will be done with the results the executable file gives
back. Choose between:
496
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
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
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.
498
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
499
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
500
19.09.2014
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 sensor 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. 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 .
19.09.2014
501
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
502
19.09.2014
More
Information about custom scripts and executables
Applicat ion Programming Int erface (API) Definit ion
Addit ional Sensor Ty pes (Cust om Sensors)
2571
2217
Knowledge Base: What is the Mutex Name in PRTG's EXE/Script Sensor's settings?
http://kb.paessler.com/en/topic/6673
Knowledge Base: How and Where Does PRTG Store its Data?
http://kb.paessler.com/en/topic/463
Knowledge Base: How can I test if parameters are correctly transmitted to my script when
using an EXE/Script sensor?
http://kb.paessler.com/en/topic/11283
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
503
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.
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.
Tags
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).
504
19.09.2014
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
SENSOR DISPLAY
Primary Channel
19.09.2014
505
SENSOR DISPLAY
Chart Type
Stack Unit
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.
506
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
507
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
508
19.09.2014
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 sensor 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. 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 .
19.09.2014
509
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
510
19.09.2014
More
Knowledge Base: What can I do if PRTG doesn't succeed with monitoring a share? PE029 PE032
http://kb.paessler.com/en/topic/513
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
511
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.
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.
Tags
512
26.09.2014
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).
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.
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
If Value Changes
Define what this sensor will do when the sensor value changes.
You can choose between:
Ignore changes (default ): The sensor takes no action on
change.
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever the sensor value changes.
SENSOR DISPLAY
Primary Channel
Chart Type
514
26.09.2014
SENSOR DISPLAY
Stack Unit
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.
26.09.2014
515
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
516
26.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
26.09.2014
517
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 sensor 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. 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 .
518
26.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
26.09.2014
141
section.
519
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.
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.
Tags
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).
520
19.09.2014
FOLDER MONITOR
Folder Name
Enter the full path to the folder this sensor will monitor. For
example, enter C:\Windows. If the file is located on a network
device, use the Uniform Naming Convention (UNC) path without the
server part (you would only enter share\folder). The server part (\
\server\) is taken from this sensor's parent device's settings.
Please enter a valid path name. Note: In order to provide any
shares, the LanmanServer "Server" Windows service must be
running on the target computer.
Sub-Folder Recursion
Monitor Folder
Changes
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.
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
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
522
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
523
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
524
19.09.2014
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 sensor 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. 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 .
19.09.2014
525
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
526
19.09.2014
More
Knowledge Base: What can I do if PRTG doesn't succeed with monitoring a share? PE029 PE032
http://kb.paessler.com/en/topic/513
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
527
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.
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.
Tags
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).
SENSOR SPECIFIC
Timeout (Sec.)
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
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.
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
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
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
Chart Type
Stack Unit
530
18.11.2014
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.
18.11.2014
531
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
532
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
533
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 sensor 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. 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 .
534
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
535
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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.
536
18.11.2014
Tags
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).
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
If Value Changes
Define what this sensor will do when the sensor value changes.
You can choose between:
Ignore changes (default ): The sensor takes no action on
change.
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever the sensor value changes.
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.
538
18.11.2014
DEBU G OPTIONS
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received from the sensor to the
"Logs (Sensor)" directory (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
Chart Type
Stack Unit
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.
18.11.2014
539
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
540
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
541
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 sensor 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. 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 .
542
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
543
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
For more general information about settings, please see Object Set t ings
544
141
section.
18.11.2014
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.
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.
18.11.2014
545
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).
Enter how often the sensor will query data. Choose between:
1 Day
2 Day s
3 Day s
1 Week
Username
Password
Profile ID
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
546
18.11.2014
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
Chart Type
18.11.2014
547
SENSOR DISPLAY
Stack Unit
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.
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.
Maintenance Window
548
18.11.2014
Maintenance End At
Dependency Type
Dependency
18.11.2014
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 sensor will be
dependent on.
549
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. 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 .
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
550
18.11.2014
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.
Name
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
Password
More
Knowledge Base: Where do I find my Google Analytics profile ID?
http://kb.paessler.com/en/topic/35363
18.11.2014
551
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
For more general information about settings, please see Object Set t ings
552
141
section.
18.11.2014
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.
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.
Tags
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).
HTTP SPECIFIC
Timeout (Sec.)
19.09.2014
Enter a timeout in seconds for the HTTP request. If the reply takes
longer than this value the request is aborted and an error message
is triggered. The maximum value is 900 seconds (15 minutes).
553
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
Postdata
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
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
Stack Unit
19.09.2014
555
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.
Name
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
Password
556
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
557
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
558
19.09.2014
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 sensor 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. 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 .
19.09.2014
559
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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
Note: Smart URL replacement does not work for sensors running on the "Probe Device".
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
561
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.
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.
Tags
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).
HTTP SPECIFIC
Timeout (Sec.)
562
Enter a timeout in seconds for the HTTP request. If the reply takes
longer than this value the request is aborted and an error message
is triggered. The maximum value is 900 seconds (15 minutes).
19.09.2014
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
Postdata
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
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.
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
Note: This sensor type implicitly supports Server Name Identification (SNI), an extension to the
TLS protocol.
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.
Content Changes
Define what will be done in case the content of the monitored web
page (element) changes. You can choose between:
Ignore changes: No action will be taken on change.
Trigger 'change' not ificat ion: The sensor will send an internal
message indicating that the web page content has changed. In
combination with a Change Trigger, you can use this mechanism
to trigger a notification 2227 whenever the web page content
changes.
19.09.2014
565
566
19.09.2014
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
19.09.2014
567
AU THENTICATION
User
Password
Authentication Method
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
568
19.09.2014
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.
Name
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
Password
19.09.2014
569
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
570
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
571
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 sensor 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. 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 .
572
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
573
More
Knowledge Base: Which user agent should I use in the HTTP Advanced sensor's settings?
http://kb.paessler.com/en/topic/30593
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
For more general information about settings, please see Object Set t ings
574
141
section.
19.09.2014
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.
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.
Tags
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).
HTTP SPECIFIC
Timeout (Sec.)
19.09.2014
Enter a timeout in seconds for the HTTP request. If the reply takes
longer than this value the request is aborted and an error message
is triggered. The maximum value is 900 seconds (15 minutes).
575
HTTP SPECIFIC
URL
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.
AU THENTICATION
Authentication
User
Password
576
19.09.2014
AU THENTICATION
Authentication Method
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
19.09.2014
577
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.
Name
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
Password
578
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
579
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
580
19.09.2014
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 sensor 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. 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 .
19.09.2014
581
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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
Note: Smart URL replacement does not work for sensors running on the "Probe Device".
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
583
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.
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.
Tags
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).
HTTP SPECIFIC
Timeout (Sec.)
584
Enter a timeout in seconds for the HTTP request. If the reply takes
longer than this value the request is aborted and an error message
is triggered. The maximum value is 900 seconds (15 minutes).
19.09.2014
HTTP SPECIFIC
URL
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.
AU THENTICATION
Authentication
User
Password
19.09.2014
585
AU THENTICATION
Authentication Method
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
586
19.09.2014
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.
Name
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
Password
19.09.2014
587
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
588
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
589
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 sensor 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. 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 .
590
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
591
Note: Smart URL replacement does not work for sensors running on the "Probe Device".
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
For more general information about settings, please see Object Set t ings
592
141
section.
19.09.2014
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
HTTP SPECIFIC
Value Type
Define what kind of values your HTML file gives back. Choose
between:
Int eger: An integer is expected as return value.
Float : A float is expected as return value, with a dot (.) between
pre-decimal position and decimal places. In this setting, the
sensor will also display integer values unless they don't produce
a buffer overflow.
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
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.
19.09.2014
593
Tags
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).
HTTP SPECIFIC
Timeout (Sec.)
Enter a timeout in seconds for the HTTP request. If the reply takes
longer than this value the request is aborted and an error message
is triggered. The maximum value is 900 seconds (15 minutes).
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
created, you cannot change this value. It is shown for reference
purposes only. If you need to change this, please add the sensor
anew.
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
594
19.09.2014
SSL SPECIFIC
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.
Define what will be done in case the content of the monitored web
page changes. You can choose between:
Ignore changes: No action will be taken on change.
Trigger 'change' not ificat ion: The sensor will send an internal
message indicating that the web page content has changed. In
combination with a Change Trigger, you can use this mechanism
to trigger a notification 2227 whenever the web page content
changes.
Sensor Result
Define what will be done with the results the sensor receives.
Choose between:
Discard sensor result : Do not store the results.
Writ e sensor result t o disk (Filename: "Result of Sensor
(ID].t xt "): Store the last result received to the "Logs (Sensors)"
directory (on the Master node, if in a cluster). This is for
debugging purposes. The file will be overridden with each
scanning interval. For information on how to find the folder used
for storage, please see Dat a St orage 2611 section.
AU THENTICATION
Authentication
19.09.2014
595
AU THENTICATION
User
Password
Authentication Method
SENSOR DISPLAY
Primary Channel
Chart Type
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
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.
19.09.2014
597
Name
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
Password
598
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
599
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
600
19.09.2014
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 sensor 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. 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 .
19.09.2014
601
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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
Note: Smart URL replacement does not work for sensors running on the "Probe Device".
More
Knowledge Base article: How can I monitor internal values of a web application with PRTG?
http://kb.paessler.com/en/topic/4
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
603
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.
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.
Tags
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).
604
19.09.2014
Enter a timeout in seconds for the HTTP request. If the reply takes
longer than this value the request is aborted and an error message
is triggered. The maximum value is 900 seconds (15 minutes).
URL
Please enter the URL the sensor will load. 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.
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
Define the Windows user account that will be used to run the
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
Authentication
606
19.09.2014
Password
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.
19.09.2014
607
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
608
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
609
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 sensor 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. 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 .
610
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
611
Note: Smart URL replacement does not work for sensors running on the "Probe Device".
More
Knowledge Base: What to do when I see a CreateUniqueTempDir() error message for my HTTP
Full Webpage Sensor?
http://kb.paessler.com/en/topic/40783
Knowledge Base: HTTP Full Web Page sensor is "unable to navigate". What can I do?
http://kb.paessler.com/en/topic/59999
Knowledge Base: How can I change the size of PhantomJS full web page screenshots?
http://kb.paessler.com/en/topic/60247
Knowledge Base: What is the difference between "HTTP" and "HTTP Full Web Page" Web Server
sensors?
http://kb.paessler.com/en/topic/943
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
For more general information about settings, please see Object Set t ings
612
141
section.
19.09.2014
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.
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.
19.09.2014
613
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).
HTTP PU SH
Request Method
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
Stack Unit
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.
19.09.2014
615
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
616
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
617
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 sensor 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. 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 .
618
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
619
Note: You can use several sensors with the same port and identification token. In this case,
the data of push messages will be shown in each of these sensors.
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
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.
620
19.09.2014
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.
Tags
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).
19.09.2014
621
HTTP PU SH
Request Method
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.
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
19.09.2014
623
SENSOR DISPLAY
Stack Unit
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.
624
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
625
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
626
19.09.2014
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 sensor 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. 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 .
19.09.2014
627
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
628
141
section.
19.09.2014
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
Note: You can use several sensors with the same port and identification token. In this case,
the data of push messages will be shown in each of these sensors.
18.11.2014
629
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
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.
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.
Tags
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).
630
18.11.2014
HTTP PU SH
Request Method
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.
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
632
18.11.2014
SENSOR DISPLAY
Stack Unit
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.
18.11.2014
633
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
634
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
635
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 sensor 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. 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 .
636
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
637
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.
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.
638
20.11.2014
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).
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
Certificate Name
Validation
20.11.2014
639
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.
Name
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
Password
640
20.11.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
20.11.2014
641
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
642
20.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
20.11.2014
643
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 sensor 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. 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 .
644
20.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My HTTP sensors could not create an SSL secure channel and are down.
What can I do?
http://kb.paessler.com/en/topic/61045
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
20.11.2014
645
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
For more general information about settings, please see Object Set t ings
646
141
section.
20.11.2014
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.
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.
Tags
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).
HTTP SPECIFIC
Timeout (Sec.)
19.09.2014
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
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.
648
19.09.2014
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.
Note: This sensor type implicitly supports Server Name Identification (SNI), an extension to the
TLS protocol.
Cookie Management
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
AU THENTICATION
Authentication
User
Password
Authentication Method
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
encoded! If you enter an absolute URL, this address will be
independent from the IP address/DNS name setting of the device
this sensor is created on. PRTG uses a smart URL replacement
which allows you to use the parent device's IP address/DNS name
setting as part of the URL. For more information, please see
section Smart URL Replacement below.
Request Method
Postdata
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.
Check For Existing Key
Words (Negative)
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
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.
652
19.09.2014
Name
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
Password
19.09.2014
653
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
654
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
655
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 sensor 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. 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 .
656
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
657
Note: Smart URL replacement does not work for sensors running on the "Probe Device".
More
Knowledge Base: Configuration Tips for HTTP Transaction Sensors needed
http://kb.paessler.com/en/topic/443
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
For more general information about settings, please see Object Set t ings
658
141
section.
19.09.2014
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
On the sensor's details page, click on the Set t ings tab to change settings.
18.11.2014
659
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.
Tags
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).
SENSOR SETTINGS
URL
Enter the URL that returns the XML file. It has to be URL encoded! If
you enter an absolute URL, the sensor uses this address
independently from the IP Address/DNS Name setting of the
device on which you create this sensor.
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
670 below.
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
18.11.2014
SENSOR SETTINGS
HTTP Password
Sensor Value
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
Content Type in
Header
670
section below.
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
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
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
Define what this sensor will do when the sensor value changes.
You can choose between:
Ignore changes (default ): The sensor takes no action on
change.
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever the sensor value changes.
662
18.11.2014
SENSOR SETTINGS
Unit String
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
Chart Type
Stack Unit
18.11.2014
663
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.
664
18.11.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
18.11.2014
665
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
666
18.11.2014
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 sensor 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. 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
667
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
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:
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?
http://kb.paessler.com/en/topic/48783
Knowledge Base: How do I extract values from XML nodes (with nested tags) using PRTG's
XML/Rest Value Sensor?
http://kb.paessler.com/en/topic/43223
Knowledge Base: How can I use XPath with PRTG's XML/Rest Value Sensor?
http://kb.paessler.com/en/topic/26393
Knowledge Base: HTTP XML/REST Value Sensor shows protocol violation. What can I do?
http://kb.paessler.com/en/topic/26793
Knowledge Base: Why does my HTTP XML/REST Value Sensor return a 404 error?
http://kb.paessler.com/en/topic/46503
Knowledge Base: My HTTP sensors could not create an SSL secure channel and are down.
What can I do?
http://kb.paessler.com/en/topic/61045
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
671
680
section below.
672
18.11.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
DISK FR EE SETTINGS
Disk
Select the disks 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: 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
More 695 section below.
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.
Tags
18.11.2014
673
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).
DISK FR EE SETTINGS
Disk
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
Chart Type
674
18.11.2014
SENSOR DISPLAY
Stack Unit
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.
18.11.2014
675
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
676
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
677
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 sensor 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. 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 .
678
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
679
More
Knowledge Base: Why don't my Hyper-V sensors work after changing names?
http://kb.paessler.com/en/topic/15533
Knowledge Base: How do I enable and use remote commands in Windows PowerShell?
http://kb.paessler.com/en/topic/44453
Knowledge Base: My Powershell sensor returns an error message. What can I do?
http://kb.paessler.com/en/topic/59473
Knowledge Base: "No Logon Servers Available" when Using PowerShell Sensors
http://kb.paessler.com/en/topic/59745
Knowledge Base: How can I increase memory for Remote PowerShell?
http://kb.paessler.com/en/topic/61922
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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
For more general information about settings, please see Object Set t ings
680
141
section.
18.11.2014
2495
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
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.
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.
Tags
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).
Sensor Result
Define what PRTG will do with the result of the sensor. Choose
between:
Discard sensor result : Do not store the sensor result.
682
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
683
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
684
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
685
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 sensor 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. 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 .
686
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
687
2495
688
26.09.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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: 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
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.
26.09.2014
689
Tags
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).
Name
Name
Shows the name of the host server. Once a sensor is created, you
cannot change this value. It is shown for reference purposes only.
If you need to change this, please add the sensor anew.
Sensor Result
690
Define what PRTG will do with the result of the sensor. Choose
between:
26.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
26.09.2014
691
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
692
26.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
26.09.2014
693
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 sensor 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. 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 .
694
26.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Why don't my Hyper-V Virtual Machine / Network Adapter Sensor work after
changing names?
http://kb.paessler.com/en/topic/15533
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.
26.09.2014
695
Others
For more general information about settings, please see Object Set t ings
696
141
section.
26.09.2014
2495
19.09.2014
697
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
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 network adapters, PRTG will create one sensor for each adapter. 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:
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
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.
698
19.09.2014
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).
Sensor Result
Define what will be done with the results the sensor receives.
Choose between:
Discard sensor result : Do not store the results.
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received to the "Logs (Sensors)"
directory (on the Master node, if in a cluster). This is for
debugging purposes. The file will be overridden with each
scanning interval. For information on how to find the folder used
for storage, please see Dat a St orage 2611 section.
SENSOR DISPLAY
Primary Channel
Chart Type
19.09.2014
699
SENSOR DISPLAY
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).
Stack Unit
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.
700
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
701
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
702
19.09.2014
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 sensor 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. 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 .
19.09.2014
703
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Why don't my Hyper-V Virtual Machine / Network Adapter Sensor work after
changing names?
http://kb.paessler.com/en/topic/15533
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.
704
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
705
2495
706
19.09.2014
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
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
Tags
19.09.2014
707
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).
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
Chart Type
708
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
709
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
710
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
711
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 sensor 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. 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 .
712
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
713
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
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.
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.
Tags
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).
714
19.09.2014
IMAP SPECIFIC
Timeout (Sec.)
Enter a timeout in seconds for the SMTP connect. If the reply takes
longer than this value the request is aborted and an error message
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
Username
Password
TLS (Transport-Level
Security)
19.09.2014
715
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.
We recommend using the default value. Only if you experience
connection problems, try another setting. Choose between:
SSL V2
SSL V2 or V3
SSL V3
TLS V1
IDENTIFY EMAIL
Process Email Content
Mailbox Name
716
19.09.2014
IDENTIFY EMAIL
Search For
Identify by "Subject"
Field
Search For
Search For
19.09.2014
717
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
Check Method
Search Text
718
19.09.2014
SENSOR BEHAVIOR
Error Message
Set to Warning
Check Method
Search Text
Warning Message
No Matching Mail
Behavior
19.09.2014
719
SENSOR BEHAVIOR
Message
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
720
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
721
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
722
19.09.2014
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 sensor 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. 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 .
19.09.2014
723
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: How can I monitor my backup software to be sure backup succeeded last
night?
http://kb.paessler.com/en/topic/47023
Knowledge Base: My IMAP sensor does not process HTML emails correctly using regex. What
can I do?
http://kb.paessler.com/en/topic/61019
724
19.09.2014
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
725
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.
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.
Tags
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).
726
19.09.2014
SENSOR SETTINGS
INI File Name
Enter the full path to the file this sensor will monitor. For example,
enter C:\Windows\win.ini. If the file is located on a network device
use the Uniform Naming Convention (UNC) path without the server
part (you would only enter share\folder\file.ini). The server part (\
\server\) is taken from 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.
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.
You can choose between:
Ignore changes: No action will be taken on change.
Trigger 'change' not ificat ion: The sensor will send an internal
message indicating that 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.
SENSOR DISPLAY
Primary Channel
Chart Type
19.09.2014
727
SENSOR DISPLAY
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).
Stack Unit
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.
728
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
729
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
730
19.09.2014
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 sensor 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. 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 .
19.09.2014
731
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
732
141
section.
19.09.2014
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.
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.
18.11.2014
733
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).
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
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.
734
18.11.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
18.11.2014
735
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
736
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
737
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 sensor 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. 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 .
738
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Is there a list of anti spam black list servers?
http://kb.paessler.com/en/topic/37633
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.
18.11.2014
739
Others
For more general information about settings, please see Object Set t ings
740
141
section.
18.11.2014
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.
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.
Tags
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).
18.11.2014
741
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.
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
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
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
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
Stack Unit
PR IMAR Y TOPLIST
Primary Toplist
744
18.11.2014
PR IMAR Y TOPLIST
Top Connect ions
Top Prot ocols
[Any custom toplists you have added]
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.
18.11.2014
745
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
746
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
747
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 sensor 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. 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 .
748
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
749
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?
http://kb.paessler.com/en/topic/60203
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
For more general information about settings, please see Object Set t ings
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
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.
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.
18.11.2014
751
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).
Enter the UDP port number on which the flow packets are
received. It must match the one 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.
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.
752
18.11.2014
Channel Definition
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.
Note: Use with caution! When enabled, huge data files can be
created. Please use for a short time and for debugging purposes
only.
SENSOR DISPLAY
Primary Channel
Chart Type
18.11.2014
753
SENSOR DISPLAY
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).
Stack Unit
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.
PR IMAR Y TOPLIST
Primary Toplist
754
18.11.2014
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.
18.11.2014
755
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
756
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
757
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 sensor 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. 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 .
758
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
759
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.
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
For more general information about settings, please see Object Set t ings
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
760
2576
18.11.2014
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.
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
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:
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.
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.
Tags
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).
IPMI CR EDENTIALS
Username
Password
762
26.09.2014
IPMI SPECIFIC
Group
Logfile 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
Chart Type
Stack Unit
26.09.2014
763
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.
764
26.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
26.09.2014
765
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
766
26.09.2014
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 sensor 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. 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 .
26.09.2014
767
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
768
26.09.2014
More
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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
For more general information about settings, please see Object Set t ings
26.09.2014
141
section.
769
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.
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.
Tags
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).
770
19.09.2014
Enter the UDP port number on which PRTG receives the flow
packets. It must match the one you have configured in the jFlow
export options of your hardware router device. Please enter an
integer value.
Note: When you configure the export, please make sure you select
the appropriate jFlow version for this sensor.
Sender IP
Enter the IP address of the sending device you want to receive the
jFlow 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.
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.
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
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:
19.09.2014
771
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.
772
19.09.2014
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
19.09.2014
773
SENSOR DISPLAY
Stack Unit
PR IMAR Y TOPLIST
Primary Toplist
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.
774
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
775
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
776
19.09.2014
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 sensor 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. 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 .
19.09.2014
777
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
778
19.09.2014
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
Knowledge Base: Where is the volume line in graphs?
http://kb.paessler.com/en/topic/61272
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
For more general information about settings, please see Object Set t ings
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
19.09.2014
2576
779
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.
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.
Tags
780
19.09.2014
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).
Enter the UDP port number on which PRTG receives the flow
packets. It must match the one you have configured in the jFlow
export options of your hardware router device. Please enter an
integer value.
Note: When you configure the export, please make sure you select
the appropriate jFlow version for this sensor.
Sender IP
Enter the IP address of the sending device you want to receive the
jFlow 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.
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.
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.
19.09.2014
781
Channel Definition
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.
Note: Use with caution! When enabled, huge data files can be
created. Please use for a short time and for debugging purposes
only.
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.
782
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
PR IMAR Y TOPLIST
Primary Toplist
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.
19.09.2014
783
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
784
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
785
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 sensor 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. 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 .
786
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
787
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
Knowledge Base: Where is the volume line in graphs?
http://kb.paessler.com/en/topic/61272
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
For more general information about settings, please see Object Set t ings
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
788
2576
19.09.2014
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.
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.
Tags
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).
LDAP SPECIFIC
Port
19.09.2014
Enter the LDAP port number, usually port 389 for unencrypted
connections. Please enter an integer value.
789
LDAP SPECIFIC
Distinguished Name
Passwort
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
790
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
791
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
792
19.09.2014
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 sensor 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. 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 .
19.09.2014
793
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
794
141
section.
19.09.2014
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
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.
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.
Tags
19.09.2014
795
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).
Instance
Port
Port
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
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
Password
DATA
SQL Expression
Record Count
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.
19.09.2014
797
Value
Condition "Down"
Value
798
19.09.2014
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.
Response Must Not
include
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
799
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
800
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
801
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 sensor 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. 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 .
802
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
803
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.
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.
804
26.09.2014
Tags
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).
DATABASE CR EDENTIALS
Port
Database
Enter the name of the SQL database the sensor will connect to.
For example, such a database's name could be MyDatabase. This is
a logical entity on the database server where database objects like
tables or stored procedures exist.
Authentication
User
Password
26.09.2014
805
DATABASE CR EDENTIALS
Database Timeout
(Sec.)
DATA
SQL Query File
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
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.
This setting is only visible if you selected the process data table
option above. Define how the desired cell in the database table will
be selected. This is necessary to configure the cells which will be
used in the sensor channels. Choose between:
Column number: The channel value will be determined by using
the value in row 0 of the column whose number you specify
below.
Column name: The channel value will be determined by using the
value in row 0 of the column whose name you specify below.
Row number: The channel value will be determined by using the
value in column 0 of the row whose number you specify below.
Key value pair: The channel value will be determined by
searching in column 0 for the key you specify below and
returning the value in column 1 of the same row where the key
value was found.
Sensor Channel #x
This setting is only visible if you selected the process data table
option above. You can define up to 10 different channels for the
data processing of this sensor. You have to define at least one
data channel if you process the data table, so you will see all
available settings for Channel #1 without enabling it manually. For
all other possible channels, choose between:
Disable: This channel will not be added to the sensor.
Enable: This channel will be added to the sensor. Define the
settings as described above.
26.09.2014
807
DATA
Once a sensor is created, you cannot change this value. It is
shown for reference purposes only. If you need to change this,
please add the sensor anew.
Sensor Channel #x
Name
This setting is only visible if you selected the process data table
option above. Enter a unique name for the channel. Please enter a
string. Channels will be generated dynamically with this name as
identifier. Once a sensor is created, you cannot change this value.
It is shown for reference purposes only. If you need to change
this, please add the sensor anew.
Sensor Channel #x
Column Number
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
This setting is only visible if you selected the process data table
option above. Define how to display the determined value in the
channel. Once a sensor is created, you cannot change this value. It
is shown for reference purposes only. If you need to change this,
please add the sensor anew. Choose between:
Absolut e (recommended): 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
sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew. Choose between:
BytesBandwidth
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
whose value will be shown in the sensor message. Please enter an
integer value.
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
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
Chart Type
810
26.09.2014
SENSOR DISPLAY
Stack Unit
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.
26.09.2014
811
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
812
26.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
26.09.2014
813
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 sensor 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. 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 .
814
26.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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.
26.09.2014
815
Others
For more general information about settings, please see Object Set t ings
816
141
section.
26.09.2014
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.
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.
Tags
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).
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
User
Password
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
818
26.09.2014
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.
26.09.2014
819
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
820
26.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
26.09.2014
821
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 sensor 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. 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 .
822
26.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
26.09.2014
141
section.
823
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
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.
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.
Tags
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).
824
19.09.2014
Timeout (sec.)
DB/SQL DATA
Database
Enter the name of the SQL database the sensor will connect to.
For example, such a database's name could be MyDatabase. This is
a logical entity on the database server where database objects like
tables or stored procedures exist. In case of the mySQL server it
also reflects a physical directory structure where your database
objects are stored. Enter the appropriate string which is the same
as you would supply when invoking the mysql.exe admin tool (with
the command line switch -p) or after the login with mysql.exe with
the command use.
User
Enter the user name that will be used for the database connection.
Password
Enter the password that will be used for the database connection.
DATA
SQL Expression
Record Count
19.09.2014
825
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.
Condition "Warning"
Value
Condition "Down"
826
19.09.2014
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.
Response Must Not
include
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
19.09.2014
827
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.
828
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
829
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
830
19.09.2014
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 sensor 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. 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 .
19.09.2014
831
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
832
141
section.
19.09.2014
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.
Sensor Settings
On the sensor's details page, click on the Set t ings tab to change settings.
26.09.2014
833
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.
Tags
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).
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.
DATABASE CR EDENTIALS
Port
Database
Enter the name of the SQL database the sensor will connect to.
For example, such a database's name could be MyDatabase. This is
a logical entity on the database server where database objects like
tables or stored procedures exist.
Authentication
834
26.09.2014
DATABASE CR EDENTIALS
SQL server aut hent icat ion: Choose this option if you want to
use explicit credentials for the database connection.
User
Password
Database Timeout
(Sec.)
DATA
SQL Query File
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.
26.09.2014
835
DATA
Use t ransact ion and alway s rollback: Choose this option to
ensure that no data in the database will be changed by the
query. In the SQL Query field above, separate the single steps of
the transaction with semicolons.
Use t ransact ion and commit on success: Choose this option
to perform changes on the database with the query. The
changes will only apply if all execution steps succeed without
any errors. In the SQL Query field above, separate the single
steps of the transaction with semicolons.
Data Processing
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.
This setting is only visible if you selected the process data table
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.
836
26.09.2014
DATA
Sensor Channel #x
This setting is only visible if you selected the process data table
option above. You can define up to 10 different channels for the
data processing of this sensor. You have to define at least one
data channel if you process the data table, so you will see all
available settings for Channel #1 without enabling it manually. For
all other possible channels, choose between:
Disable: This channel will not be added to the sensor.
Enable: This channel will be added to the sensor. Define the
settings as described above.
Once a sensor is created, you cannot change this value. It is
shown for reference purposes only. If you need to change this,
please add the sensor anew.
Sensor Channel #x
Name
This setting is only visible if you selected the process data table
option above. Enter a unique name for the channel. Please enter a
string. Channels will be generated dynamically with this name as
identifier. Once a sensor is created, you cannot change this value.
It is shown for reference purposes only. If you need to change
this, please add the sensor anew.
Sensor Channel #x
Column Number
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
This setting is only visible if you selected the process data table
option above. Define how to display the determined value in the
channel. Once a sensor is created, you cannot change this value. It
is shown for reference purposes only. If you need to change this,
please add the sensor anew. Choose between:
Absolut e (recommended): The value will be shown as the
sensor retrieves it from the data table.
26.09.2014
837
DATA
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
sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew. Choose between:
BytesBandwidth
BytesMemory
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.
838
26.09.2014
DATA
Sensor Message
Column Number
This setting is only visible if you selected the column number and
sensor message options above. Specify the number of the column
whose value will be shown in the sensor message. Please enter an
integer value.
Sensor Message
Column Name
This setting is only visible if you selected the column name and
sensor message options above. Specify the name of the column
whose value will be shown in the sensor message. Please enter a
string.
This setting is only visible if you selected the row number and
sensor message options above. Specify the number of the row
whose value will be shown in the sensor message. Please enter an
integer value.
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
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
26.09.2014
839
SENSOR DISPLAY
Chart Type
Stack Unit
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.
840
26.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
26.09.2014
841
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
842
26.09.2014
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 sensor 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. 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 .
26.09.2014
843
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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.
844
26.09.2014
Others
For more general information about settings, please see Object Set t ings
26.09.2014
141
section.
845
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.
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.
Tags
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).
846
19.09.2014
Enter the UDP port number on which the flow packets are
received. It must match the one you have configured in the
NetFlow export options of your hardware router device. Please
enter an integer value.
Note: When configuring export, make sure you select the
appropriate NetFlow version for this sensor.
Sender IP
Enter the IP address of the sending device you want to receive the
NetFlow from. Enter an IP address to receive data from a specific
device only, or leave the field empty to receive data from any
device on the specified port.
Receive NetFlow
Packets on IP
Enter a time span in minutes after which new flow data must be
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
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
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:
19.09.2014
847
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.
848
19.09.2014
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
19.09.2014
849
SENSOR DISPLAY
Stack Unit
PR IMAR Y TOPLIST
Primary Toplist
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.
850
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
851
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
852
19.09.2014
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 sensor 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. 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 .
19.09.2014
853
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
854
19.09.2014
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?
http://kb.paessler.com/en/topic/60203
Knowledge Base: Where is the volume line in graphs?
http://kb.paessler.com/en/topic/61272
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
For more general information about settings, please see Object Set t ings
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
19.09.2014
2576
855
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.
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.
Tags
856
19.09.2014
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).
Enter the UDP port number on which the flow packets are
received. It must match the one you have configured in the
NetFlow export options of your hardware router device. Please
enter an integer value.
Note: When configuring export, make sure you select the
appropriate NetFlow version for this sensor.
Sender IP
Enter the IP address of the sending device you want to receive the
NetFlow from. Enter an IP address to receive data from a specific
device only, or leave the field empty to receive data from any
device on the specified port.
Receive NetFlow
Packets on IP
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 the timeout 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.
19.09.2014
857
Channel Definition
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.
Note: Use with caution! When enabled, huge data files can be
created. Please use for a short time and for debugging purposes
only.
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.
858
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
PR IMAR Y TOPLIST
Primary Toplist
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.
19.09.2014
859
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
860
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
861
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 sensor 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. 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 .
862
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
863
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
Knowledge Base: Where is the volume line in graphs?
http://kb.paessler.com/en/topic/61272
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
For more general information about settings, please see Object Set t ings
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
864
2576
19.09.2014
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.
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.
Tags
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).
19.09.2014
865
Enter the UDP port number on which the flow packets are
received. It must match the one you have configured in the
NetFlow export options of your hardware router device. Please
enter an integer value.
Note: When configuring export, make sure you select the
appropriate NetFlow version for this sensor.
Sender IP
Enter the IP address of the sending device you want to receive the
NetFlow from. Enter an IP address to receive data from a specific
device only, or leave the field empty to receive data from any
device on the specified port.
Receive NetFlow
Packets on IP
Enter a time span in minutes after which new flow data must be
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
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
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:
866
19.09.2014
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.
19.09.2014
867
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
868
19.09.2014
SENSOR DISPLAY
Stack Unit
PR IMAR Y TOPLIST
Primary Toplist
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.
19.09.2014
869
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
870
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
871
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 sensor 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. 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 .
872
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
873
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?
http://kb.paessler.com/en/topic/60203
Knowledge Base: Where is the volume line in graphs?
http://kb.paessler.com/en/topic/61272
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
For more general information about settings, please see Object Set t ings
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
874
2576
19.09.2014
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.
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.
Tags
19.09.2014
875
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).
Enter the UDP port number on which the flow packets are
received. It must match the one you have configured in the
NetFlow export options of your hardware router device. Please
enter an integer value.
Note: When configuring export, make sure you select the
appropriate NetFlow version for this sensor.
Sender IP
Enter the IP address of the sending device you want to receive the
NetFlow from. Enter an IP address to receive data from a specific
device only, or leave the field empty to receive data from any
device on the specified port.
Receive NetFlow
Packets on IP
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 the timeout 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.
876
19.09.2014
Channel Definition
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.
Note: Use with caution! When enabled, huge data files can be
created. Please use for a short time and for debugging purposes
only.
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.
19.09.2014
877
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
PR IMAR Y TOPLIST
Primary Toplist
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.
878
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
879
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
880
19.09.2014
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 sensor 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. 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 .
19.09.2014
881
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
882
19.09.2014
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
Knowledge Base: Where is the volume line in graphs?
http://kb.paessler.com/en/topic/61272
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
For more general information about settings, please see Object Set t ings
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
19.09.2014
2576
883
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
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.
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.
884
19.09.2014
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).
Port
Enter the port number that will be used for the connection. Default
value is 1521. Please enter an integer value.
Connection Mode
DB/SQL DATA
Service Name / Alias
Enter the name of the SQL database the sensor will connect to.
For example, such a database's name could be orcl
User
Enter the user name that will be used for the database connection.
Password
Enter the password that will be used for the database connection.
19.09.2014
885
DATA
SQL Expression
Record Count
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.
Condition "Warning"
886
19.09.2014
Condition "Down"
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.
Response Must Not
include
SENSOR DISPLAY
Primary Channel
19.09.2014
887
SENSOR DISPLAY
Chart Type
Stack Unit
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.
888
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
889
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
890
19.09.2014
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 sensor 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. 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 .
19.09.2014
891
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: How do PRTG sensors connect to Oracle databases?
http://kb.paessler.com/en/topic/52803
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.
892
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
893
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.
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.
894
26.09.2014
Tags
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).
DATABASE CR EDENTIALS
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
Password
26.09.2014
895
DATABASE CR EDENTIALS
Database Timeout
(Sec.)
DATA
SQL Query File
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.
896
26.09.2014
DATA
Data Processing
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.
This setting is only visible if you selected the process data table
option above. Define how the desired cell in the database table will
be selected. This is necessary to configure the cells which will be
used in the sensor channels. Choose between:
Column number: The channel value will be determined by using
the value in row 0 of the column whose number you specify
below.
Column name: The channel value will be determined by using the
value in row 0 of the column whose name you specify below.
Row number: The channel value will be determined by using the
value in column 0 of the row whose number you specify below.
Key value pair: The channel value will be determined by
searching in column 0 for the key you specify below and
returning the value in column 1 of the same row where the key
value was found.
Sensor Channel #x
This setting is only visible if you selected the process data table
option above. You can define up to 10 different channels for the
data processing of this sensor. You have to define at least one
data channel if you process the data table, so you will see all
available settings for Channel #1 without enabling it manually. For
all other possible channels, choose between:
Disable: This channel will not be added to the sensor.
Enable: This channel will be added to the sensor. Define the
settings as described above.
26.09.2014
897
DATA
Once a sensor is created, you cannot change this value. It is
shown for reference purposes only. If you need to change this,
please add the sensor anew.
Sensor Channel #x
Name
This setting is only visible if you selected the process data table
option above. Enter a unique name for the channel. Please enter a
string. Channels will be generated dynamically with this name as
identifier. Once a sensor is created, you cannot change this value.
It is shown for reference purposes only. If you need to change
this, please add the sensor anew.
Sensor Channel #x
Column Number
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
This setting is only visible if you selected the process data table
option above. Define how to display the determined value in the
channel. Once a sensor is created, you cannot change this value. It
is shown for reference purposes only. If you need to change this,
please add the sensor anew. Choose between:
Absolut e (recommended): 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
sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew. Choose between:
BytesBandwidth
BytesMemory
898
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
899
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
whose value will be shown in the sensor message. Please enter an
integer value.
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
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
Chart Type
900
26.09.2014
SENSOR DISPLAY
Stack Unit
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.
26.09.2014
901
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
902
26.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
26.09.2014
903
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 sensor 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. 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 .
904
26.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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.
26.09.2014
905
Others
For more general information about settings, please see Object Set t ings
906
141
section.
26.09.2014
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.
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.
Tags
19.09.2014
907
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).
SNIFFER SPECIFIC
Include Filter
Define if you want to filter any traffic. If you leave this field empty,
the sensor includes all traffic. 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 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.
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. We
recommend this for normal use cases.
Only for t he 'Ot her' channel: Only write log files of data that is
not filtered otherwise and therefore accounted to the default
Ot her channel.
All st ream dat a: Write log files for all data received.
Note: Use with caution! When enabled, huge data files can be
created. Please use for a short time and for debugging purposes
only.
908
Define the categories the sensor accounts the traffic to. There are
different groups of traffic available. Choose between:
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
19.09.2014
909
SENSOR DISPLAY
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).
Stack Unit
PR IMAR Y TOPLIST
Primary Toplist
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.
910
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
911
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
912
19.09.2014
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 sensor 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. 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 .
19.09.2014
913
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
914
19.09.2014
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
Knowledge Base: How can I change the default groups and channels for xFlow and Packet
Sniffer sensors?
http://kb.paessler.com/en/topic/60203
Knowledge Base: Where is the volume line in graphs?
http://kb.paessler.com/en/topic/61272
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
For more general information about settings, please see Object Set t ings
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
19.09.2014
2576
915
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.
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.
916
19.09.2014
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).
SNIFFER SPECIFIC
Include Filter
Define if you want to filter any traffic. If you leave this field empty,
the sensor includes all traffic. To include specific traffic only, define
filters using a special syntax. For detailed information, please see
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
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.
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:
19.09.2014
917
SNIFFER SPECIFIC
None (recommended): Do not write additional log files.
Recommended for normal use cases.
Only for t he 'Ot her' channel: Only write log files of data that is
not filtered otherwise and therefore accounted to the default
Ot her channel.
All st ream dat a: Write log files for all data received.
Note: Use with caution! When enabled, huge data files can be
created. Please use for a short time and for debugging purposes
only.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
PR IMAR Y TOPLIST
Primary Toplist
918
19.09.2014
PR IMAR Y TOPLIST
Top Talkers
Top Connect ions
Top Prot ocols
[Any custom toplists you have added]
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.
19.09.2014
919
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
920
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
921
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 sensor 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. 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 .
922
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
923
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
Knowledge Base: Where is the volume line in graphs?
http://kb.paessler.com/en/topic/61272
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
For more general information about settings, please see Object Set t ings
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
924
2576
19.09.2014
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.
Sensor Settings
On the sensor's details page, click on the Set t ings tab to change settings.
19.09.2014
925
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.
Tags
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).
APPLICATIONS
Network Adapter
Applications
SENSOR DISPLAY
Primary Channel
Chart Type
926
19.09.2014
SENSOR DISPLAY
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).
Stack Unit
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.
19.09.2014
927
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
928
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
929
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 sensor 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. 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 .
930
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
931
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
932
19.09.2014
Mode
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.
Tags
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).
19.09.2014
933
Mode
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
934
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
935
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
936
19.09.2014
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 sensor 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. 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 .
19.09.2014
937
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
938
19.09.2014
More
Knowledge Base: How can I find out the names of available Performance Counters?
http://kb.paessler.com/en/topic/50673
Knowledge Base: Remote Monitoring of Specific Performance Counters
http://kb.paessler.com/en/topic/59804
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
939
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.
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
sensors that are created.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
Tags
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).
19.09.2014
941
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
942
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
943
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
944
19.09.2014
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 sensor 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. 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 .
19.09.2014
945
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
946
19.09.2014
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
947
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.
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.
Tags
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).
PING SETTINGS
Timeout (Sec.)
948
Enter a timeout in seconds for the Ping. If the reply takes longer
than this value the request is aborted and an error message is
triggered. The maximum timeout value is 300 seconds (5 minutes).
19.09.2014
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
Ping Count
Auto Acknowledge
19.09.2014
949
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
950
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
951
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
952
19.09.2014
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 sensor 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. 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 .
19.09.2014
953
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: How to create/customize statistical PING sensor?
http://kb.paessler.com/en/topic/1873
954
19.09.2014
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
955
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.
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.
956
19.09.2014
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).
SENSOR SETTINGS
Ping Count
Define the number of pings that this sensor sends. Please enter an
integer value.
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
19.09.2014
957
SENSOR DISPLAY
Chart Type
Stack Unit
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.
958
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
959
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
960
19.09.2014
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 sensor 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. 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 .
19.09.2014
961
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
962
141
section.
19.09.2014
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.
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.
Tags
19.09.2014
963
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).
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
Password
If Value Changes
Define what this sensor will do when the sensor value changes.
You can choose between:
Ignore changes (default ): The sensor takes no action on
change.
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever the sensor value changes.
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.
964
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
965
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
966
19.09.2014
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 sensor 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. 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 .
19.09.2014
967
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
968
141
section.
19.09.2014
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.
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.
Tags
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).
19.09.2014
969
POP3 SPECIFIC
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. The maximum value is 900 seconds (15 minutes). Please
enter an integer value.
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
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.
We recommend using the default value. Only if you experience
connection problems, try another setting. Choose between:
SSL V2
SSL V2 or V3
SSL V3
TLS V1
970
19.09.2014
POP3 AU THENTICATION
Type
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
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
Chart Type
19.09.2014
971
SENSOR DISPLAY
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).
Stack Unit
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.
972
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
973
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
974
19.09.2014
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 sensor 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. 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 .
19.09.2014
975
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
976
141
section.
19.09.2014
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.
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.
Tags
26.09.2014
977
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).
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.
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
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.
978
26.09.2014
SENSOR SETTINGS
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever the sensor value changes.
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
Chart Type
26.09.2014
979
SENSOR DISPLAY
Stack Unit
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.
980
26.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
26.09.2014
981
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
982
26.09.2014
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 sensor 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. 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 .
26.09.2014
983
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
984
26.09.2014
More
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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
For more general information about settings, please see Object Set t ings
26.09.2014
141
section.
985
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.
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.
Tags
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).
POR T SPECIFIC
Timeout (sec.)
Enter a timeout in seconds for the port connect. If the reply takes
longer than this value the request is aborted and an error message
is triggered.
Port
986
19.09.2014
POR T SPECIFIC
SSL (Secure Sockets
Layer)
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.
We recommend using the default value. Only if you experience
connection problems, try another setting. Choose between:
SSL V2
SSL V2 or V3
SSL V3
TLS V1
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
Command
19.09.2014
987
Allowed Code
Define the method that you want to use for the search string.
Choose between:
Plain Text : Search for a simple string.
Regular Expression: Search using a regular expression. For
more details, see Regular Expressions 2587 section.
Define the method you want to use for the search string. Choose
between:
988
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
989
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
990
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
991
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 sensor 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. 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 .
992
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
993
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.
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.
Tags
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).
994
Enter a timeout in seconds for the port connect. If the reply takes
longer than this value the request is aborted and an error message
is triggered.
19.09.2014
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
SENSOR DISPLAY
Primary Channel
Chart Type
19.09.2014
995
SENSOR DISPLAY
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).
Stack Unit
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.
996
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
997
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
998
19.09.2014
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 sensor 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. 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 .
19.09.2014
999
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
1000
141
section.
19.09.2014
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.
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.
26.09.2014
1001
Tags
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).
DATABASE CR EDENTIALS
Port
Database
Enter the name of the SQL database the sensor will connect to.
For example, such a database's name could be MyDatabase. This is
a logical entity on the database server where database objects like
tables or stored procedures exist.
Authentication
User
Password
1002
26.09.2014
DATABASE CR EDENTIALS
Database Timeout
(Sec.)
DATA
SQL Query File
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.
26.09.2014
1003
DATA
Data Processing
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.
This setting is only visible if you selected the process data table
option above. Define how the desired cell in the database table will
be selected. This is necessary to configure the cells which will be
used in the sensor channels. Choose between:
Column number: The channel value will be determined by using
the value in row 0 of the column whose number you specify
below.
Column name: The channel value will be determined by using the
value in row 0 of the column whose name you specify below.
Row number: The channel value will be determined by using the
value in column 0 of the row whose number you specify below.
Key value pair: The channel value will be determined by
searching in column 0 for the key you specify below and
returning the value in column 1 of the same row where the key
value was found.
Sensor Channel #x
This setting is only visible if you selected the process data table
option above. You can define up to 10 different channels for the
data processing of this sensor. You have to define at least one
data channel if you process the data table, so you will see all
available settings for Channel #1 without enabling it manually. For
all other possible channels, choose between:
Disable: This channel will not be added to the sensor.
Enable: This channel will be added to the sensor. Define the
settings as described above.
1004
26.09.2014
DATA
Once a sensor is created, you cannot change this value. It is
shown for reference purposes only. If you need to change this,
please add the sensor anew.
Sensor Channel #x
Name
This setting is only visible if you selected the process data table
option above. Enter a unique name for the channel. Please enter a
string. Channels will be generated dynamically with this name as
identifier. Once a sensor is created, you cannot change this value.
It is shown for reference purposes only. If you need to change
this, please add the sensor anew.
Sensor Channel #x
Column Number
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
This setting is only visible if you selected the process data table
option above. Define how to display the determined value in the
channel. Once a sensor is created, you cannot change this value. It
is shown for reference purposes only. If you need to change this,
please add the sensor anew. Choose between:
Absolut e (recommended): 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
sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew. Choose between:
BytesBandwidth
BytesMemory
26.09.2014
1005
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.
1006
26.09.2014
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
whose value will be shown in the sensor message. Please enter an
integer value.
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
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
Chart Type
26.09.2014
1007
SENSOR DISPLAY
Stack Unit
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.
1008
26.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
26.09.2014
1009
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1010
26.09.2014
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 sensor 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. 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 .
26.09.2014
1011
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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.
1012
26.09.2014
Others
For more general information about settings, please see Object Set t ings
26.09.2014
141
section.
1013
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
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.
Tags
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).
SENSOR DISPLAY
Primary Channel
Chart Type
18.11.2014
1015
SENSOR DISPLAY
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).
Stack Unit
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.
1016
18.11.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
18.11.2014
1017
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1018
18.11.2014
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
1019
2246
function.
For a general introduction to the technology behind Quality of Service monitoring, please see
Monit oring Qualit y of Service 2507 section.
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.
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.
Tags
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).
1020
19.09.2014
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.
19.09.2014
1021
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1022
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1023
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1024
19.09.2014
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 sensor 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. 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 .
19.09.2014
1025
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
1026
141
section.
19.09.2014
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.
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.
Tags
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).
19.09.2014
1027
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
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.
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
1029
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1030
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1031
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 sensor 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. 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 .
1032
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: How can I monitor QoS roundtrips without using remote probes?
http://kb.paessler.com/en/topic/61176
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.
19.09.2014
1033
Others
For more general information about settings, please see Object Set t ings
1034
141
section.
19.09.2014
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
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.
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.
Tags
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).
26.09.2014
1035
R ADIU S SPECIFIC
Timeout (Sec.)
User
Define the user name that is used for authentication at the server.
Please enter a string.
Password
Secret
Port
Enter the port number used for connection to the server. Default
value is 1812. Please enter an integer value.
NAS IP Address
NAS-Identifier
Enter a NAS identifier. Please enter a string or leave the field empty.
Chap
SENSOR DISPLAY
Primary Channel
Chart Type
1036
26.09.2014
SENSOR DISPLAY
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).
Stack Unit
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.
26.09.2014
1037
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1038
26.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
26.09.2014
1039
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 sensor 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. 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 .
1040
26.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
26.09.2014
141
section.
1041
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.
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.
1042
20.11.2014
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).
20.11.2014
1043
R ADIU S SPECIFIC
Timeout (Sec.)
User
Define the user name that is used for authentication at the server.
Please enter a string.
Password
Secret
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
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
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.
1044
20.11.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
20.11.2014
1045
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1046
20.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
20.11.2014
1047
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 sensor 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. 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 .
1048
20.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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.
20.11.2014
1049
Others
For more general information about settings, please see Object Set t ings
1050
141
section.
20.11.2014
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.
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.
Tags
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).
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
recommend using the default value.
18.11.2014
1051
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1052
18.11.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
18.11.2014
1053
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1054
18.11.2014
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 sensor 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. 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
1055
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Does PRTG impair my Citrix environment?
http://kb.paessler.com/en/topic/61880
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.
1056
18.11.2014
Others
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
1057
1058
1065
section below.
18.11.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
18.11.2014
1059
HOST SETTINGS
Host
Select the hosts 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: 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
monitoring. For detailed information, please see More 695 section
below.
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.
Tags
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).
HOST SETTINGS
Sensor Result
Define what will be done with the results the sensor receives.
Choose between:
Discard sensor result : Do not store the results.
1060
18.11.2014
HOST SETTINGS
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received to the "Logs (Sensors)"
directory (on the Master node, if in a cluster). This is for
debugging purposes. The file will be overridden with each
scanning interval. For information on how to find the folder used
for storage, please see Dat a St orage 2611 section.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
18.11.2014
1061
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1062
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1063
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 sensor 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. 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 .
1064
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Why don't my Hyper-V sensors work after changing names?
http://kb.paessler.com/en/topic/15533
Knowledge Base: How do I enable and use remote commands in Windows PowerShell?
http://kb.paessler.com/en/topic/44453
Knowledge Base: My Powershell sensor returns an error message. What can I do?
http://kb.paessler.com/en/topic/59473
Knowledge Base: "No Logon Servers Available" when Using PowerShell Sensors
http://kb.paessler.com/en/topic/59745
Knowledge Base: How can I increase memory for Remote PowerShell?
18.11.2014
1065
http://kb.paessler.com/en/topic/61922
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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
For more general information about settings, please see Object Set t ings
1066
141
section.
18.11.2014
18.11.2014
1074
section below.
1067
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
1068
18.11.2014
Select the Virtual Machines (VMs) you want to add a sensor for.
You see a list with the names of all items which are available to
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: 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
monitoring. For detailed information, please see More 695 section
below.
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.
Tags
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).
Define what will be done with the results the sensor receives.
Choose between:
Discard sensor result : Do not store the results.
18.11.2014
1069
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1070
18.11.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
18.11.2014
1071
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1072
18.11.2014
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 sensor 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. 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
1073
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Why don't my Hyper-V sensors work after changing names?
http://kb.paessler.com/en/topic/15533
Knowledge Base: How do I enable and use remote commands in Windows PowerShell?
http://kb.paessler.com/en/topic/44453
Knowledge Base: My Powershell sensor returns an error message. What can I do?
http://kb.paessler.com/en/topic/59473
Knowledge Base: "No Logon Servers Available" when Using PowerShell Sensors
http://kb.paessler.com/en/topic/59745
Knowledge Base: How can I increase memory for Remote PowerShell?
1074
18.11.2014
http://kb.paessler.com/en/topic/61922
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
1075
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.
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.
1076
19.09.2014
Tags
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).
19.09.2014
1077
Error Handling
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
1078
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
1079
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1080
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1081
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 sensor 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. 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 .
1082
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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
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 .
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.
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.
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.
1086
1085
functions.
19.09.2014
Examples
avg(20,10)
This function returns the average of channel 1 of the sensor with ID 2001 and channel 1 of
the sensor with ID 2002.
1085
function.
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.
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.
19.09.2014
1089
gigabit = giga / 8
t erabit = tera / 8
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)
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.
81
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?
http://kb.paessler.com/en/topic/5143
Knowledge Base: How can I monitor the overall status of the business process "Email"?
http://kb.paessler.com/en/topic/60737
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.
1092
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1093
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.
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.
1094
19.09.2014
Tags
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).
Enter the UDP port number on which the flow packets are
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
Enter the IP address of the sending device you want to receive the
sFlow 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.
Define the categories the sensor accounts the traffic to. There are
different groups of traffic available. Choose between:
Web: Internet web traffic.
19.09.2014
1095
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.
1096
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
PR IMAR Y TOPLIST
Primary Toplist
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.
19.09.2014
1097
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1098
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1099
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 sensor 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. 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 .
1100
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1101
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 sFlow Tester
http://www.paessler.com/tools/sflowtester
Knowledge Base: How can I change the default groups and channels for xFlow and Packet
Sniffer sensors?
http://kb.paessler.com/en/topic/60203
Knowledge Base: Where is the volume line in graphs?
http://kb.paessler.com/en/topic/61272
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
For more general information about settings, please see Object Set t ings
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
1102
2576
19.09.2014
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.
19.09.2014
1103
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.
Tags
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).
Enter the UDP port number on which the flow packets are
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
Enter the IP address of the sending device you want to receive the
sFlow 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.
1104
19.09.2014
Channel Definition
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
Stack Unit
19.09.2014
1105
PR IMAR Y TOPLIST
Primary Toplist
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.
1106
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1107
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1108
19.09.2014
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 sensor 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. 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 .
19.09.2014
1109
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1110
19.09.2014
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 sFlow Tester
http://www.paessler.com/tools/sflowtester
Knowledge Base: Where is the volume line in graphs?
http://kb.paessler.com/en/topic/61272
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
For more general information about settings, please see Object Set t ings
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
19.09.2014
2576
1111
2498
section.
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.
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.
Tags
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).
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.
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.
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
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
Chart Type
19.09.2014
1113
SENSOR DISPLAY
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).
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
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.
1114
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1115
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1116
19.09.2014
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 sensor 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. 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 .
19.09.2014
1117
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
1118
141
section.
19.09.2014
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.
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.
Tags
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).
19.09.2014
1119
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
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
Stack Unit
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.
1120
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1121
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1122
19.09.2014
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 sensor 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. 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 .
19.09.2014
1123
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1124
19.09.2014
More
Knowledge Base: What can I do if PRTG doesn't succeed with monitoring a share? PE029 PE032
http://kb.paessler.com/en/topic/513
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1125
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.
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.
1126
26.09.2014
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).
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
enter an integer value.
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.
Please enter an integer value.
SENSOR DISPLAY
Primary Channel
26.09.2014
1127
SENSOR DISPLAY
Chart Type
Stack Unit
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.
1128
26.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
26.09.2014
1129
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1130
26.09.2014
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 sensor 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. 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 .
26.09.2014
1131
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1132
26.09.2014
More
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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
For more general information about settings, please see Object Set t ings
26.09.2014
141
section.
1133
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
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.
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.
Tags
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).
SMTP SPECIFIC
Timeout (Sec.)
1134
Enter a timeout in seconds for the SMTP connect. If the reply takes
longer than this value the request is aborted and an error message
is triggered. The maximum value is 900 seconds (15 minutes).
Please enter an integer value.
19.09.2014
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.
TLS (Transport-Level
Security)
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.
We recommend using the default value. Only if you experience
connection problems, try another setting. Choose between:
SSL V2
SSL V2 or V3
SSL V3
TLS V1
AU THENTICATION
Type
Username
Password
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
MONITOR ING
Send Email
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
leave the field empty.
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
Chart Type
1136
19.09.2014
SENSOR DISPLAY
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).
Stack Unit
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.
19.09.2014
1137
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1138
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1139
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 sensor 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. 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 .
1140
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1141
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.
We recommend adding this sensor on an SMTP server device only, because this sensor type's
settings are optimized for this scenario.
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.
Tags
1142
19.09.2014
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).
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.
EMAIL SETTINGS
From
Specify which address the sent emails will contain in the from field.
Please enter a valid email address.
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
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.
Enter a timeout in seconds for the SMTP connect. If the reply takes
longer than this value the request is aborted and an error message
is triggered.
TLS (Transport-Level
Security)
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
connection problems, try another setting. Choose between:
SSL V2
SSL V2 or V3
SSL V3
TLS V1
SMTP Authentication
Type
Username
Password
1144
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
another port number.
TLS (Transport-Level
Security)
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
recommend using the default value. If you experience connection
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.
IMAP Authentication
Type
Username
Password
19.09.2014
1145
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1146
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1147
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1148
19.09.2014
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 sensor 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. 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 .
19.09.2014
1149
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
1150
141
section.
19.09.2014
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.
We recommend adding this sensor on an SMTP server device only, as the sensor's settings are
optimized for this scenario.
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.
Tags
19.09.2014
1151
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).
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.
EMAIL SETTINGS
From
Specify which address the sent emails will contain in the from field.
Please enter a valid email address.
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
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.
Enter a timeout in seconds for the SMTP connect. If the reply takes
longer than this value the request is aborted and an error message
is triggered.
TLS (Transport-Level
Security)
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.
We recommend using the default value. Only if you experience
connection problems, try another setting. Choose between:
SSL V2
SSL V2 or V3
SSL V3
TLS V1
SMTP Authentication
Type
19.09.2014
1153
Username
Password
1154
19.09.2014
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
another port number.
TLS (Transport-Level
Security)
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
recommend using the default value. If you experience connection
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.
POP3 Authentication
Type
Username
Password
19.09.2014
1155
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.
1156
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1157
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1158
19.09.2014
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 sensor 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. 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 .
19.09.2014
1159
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
1160
141
section.
19.09.2014
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
APC U PS SPECIFIC
Library OIDs
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.
10.11.2014
1161
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).
APC U PS SPECIFIC
Selected Interface
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
Stack Unit
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.
10.11.2014
1163
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1164
10.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
10.11.2014
1165
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 sensor 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. 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 .
1166
10.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: How can I monitor additional counters with the SNMP APC Hardware sensor?
http://kb.paessler.com/en/topic/60367
10.11.2014
1167
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
For more general information about settings, please see Object Set t ings
1168
141
section.
10.11.2014
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
19.09.2014
1169
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).
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1170
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1171
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1172
19.09.2014
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 sensor 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. 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 .
19.09.2014
1173
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
1174
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1175
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.
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.
Tags
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).
1176
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
1177
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1178
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1179
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 sensor 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. 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 .
1180
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
19.09.2014
1181
Others
For more general information about settings, please see Object Set t ings
1182
141
section.
19.09.2014
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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.
19.09.2014
1183
Tags
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).
SENSOR DISPLAY
Primary Channel
Chart Type
1184
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
1185
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1186
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1187
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 sensor 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. 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 .
1188
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
19.09.2014
1189
Others
For more general information about settings, please see Object Set t ings
1190
141
section.
19.09.2014
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.
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.
Tags
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).
19.09.2014
1191
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1192
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1193
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1194
19.09.2014
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 sensor 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. 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 .
19.09.2014
1195
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
1196
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1197
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 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
sensors that are created.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
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.
1198
19.09.2014
Tags
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).
Bitmask
ObjectID
ConfigID
19.09.2014
1199
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1200
19.09.2014
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.
Maintenance Window
Maintenance Begins At
Maintenance End At
19.09.2014
1201
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 sensor 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. 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 .
1202
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
19.09.2014
1203
Others
For more general information about settings, please see Object Set t ings
1204
141
section.
19.09.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
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.
19.09.2014
1205
Tags
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).
SENSOR DISPLAY
Primary Channel
Chart Type
1206
19.09.2014
SENSOR DISPLAY
Stack Unit
19.09.2014
1207
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1208
19.09.2014
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.
Maintenance Window
Maintenance Begins At
Maintenance End At
19.09.2014
1209
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 sensor 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. 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 .
1210
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1211
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1212
141
section.
19.09.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
SENSOR SETTINGS
Chassis
Select the chassis 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.
19.09.2014
1213
Tags
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).
SENSOR SETTINGS
Chassis
SENSOR DISPLAY
Primary Channel
Chart Type
1214
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
1215
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1216
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1217
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 sensor 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. 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 .
1218
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1219
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1220
141
section.
19.09.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
U CS PHYSICAL DISK
Disks
Select the disks 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: Only working disks (with the current status Up or Warning)
will be shown here.
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.
19.09.2014
1221
Tags
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).
U CS PHYSICAL DISK
Disk
Display Name
Shows the display name of the physical disk which this sensor
monitors. Once a sensor is created, you cannot change this value.
It is shown for reference purposes only. If you need to change
this, please add the sensor anew.
SENSOR DISPLAY
Primary Channel
Chart Type
1222
19.09.2014
SENSOR DISPLAY
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).
Stack Unit
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.
19.09.2014
1223
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1224
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1225
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 sensor 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. 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 .
1226
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1227
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1228
141
section.
19.09.2014
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.
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.
Tags
19.09.2014
1229
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).
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1230
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1231
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1232
19.09.2014
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 sensor 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. 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 .
19.09.2014
1233
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1234
19.09.2014
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1235
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.
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.
Tags
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).
SENSOR DISPLAY
Primary Channel
1236
19.09.2014
SENSOR DISPLAY
Chart Type
Stack Unit
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.
19.09.2014
1237
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1238
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1239
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 sensor 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. 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 .
1240
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1241
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1242
141
section.
19.09.2014
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
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 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.
19.09.2014
1243
Tags
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).
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
change this value. It is shown for reference purposes only. If you
need to change this, please add the sensor anew.
Multiplication
If you want to multiply the received data with a certain value, enter
the multiplier here. Please enter an integer value. Otherwise, use
the default value 1 to not change the received value.
Division
If you want to divide the received data by a certain value, enter the
divisor here. Please enter an integer value. Otherwise, use the
default value 1 to not change the received value.
If Value Changes
Define what this sensor will do when the sensor value changes.
You can choose between:
Ignore changes (default ): The sensor takes no action on
change.
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever the sensor value changes.
SENSOR DISPLAY
Primary Channel
Chart Type
19.09.2014
1245
SENSOR DISPLAY
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).
Stack Unit
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.
1246
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1247
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1248
19.09.2014
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 sensor 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. 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 .
19.09.2014
1249
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: How do I find out what OID I need to use for a custom sensor?
http://kb.paessler.com/en/topic/903
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
1250
19.09.2014
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1251
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.
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.
Tags
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).
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
enter a string or leave the field empty.
For Keyword Search
Use
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
enter a string or leave the field empty.
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
enter a string or leave the field empty.
For Keyword Search
Use
1254
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
Index of Capturing
Group
Decimal Separator
Thousands Separator
SENSOR DISPLAY
Primary Channel
Chart Type
19.09.2014
1255
SENSOR DISPLAY
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).
Stack Unit
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.
1256
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1257
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1258
19.09.2014
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 sensor 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. 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 .
19.09.2014
1259
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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"
Group 3 contains "3.555"
Group 4 contains "3.90"
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?
http://kb.paessler.com/en/topic/903
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1261
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
1262
19.09.2014
Tags
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).
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
Define what will be done in case the value of this sensor changes.
You can choose between:
Ignore changes: No action will be taken on change.
Trigger 'change' not ificat ion: The sensor will send an internal
message indicating that 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.
19.09.2014
1263
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1264
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1265
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1266
19.09.2014
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 sensor 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. 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 .
19.09.2014
1267
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: What do I need to monitor Dell servers?
http://kb.paessler.com/en/topic/45333
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
1268
19.09.2014
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1269
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the disks 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.
1270
18.11.2014
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.
Tags
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).
Shows the name of the disk that this sensor is monitoring. 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.
Data Source
SENSOR DISPLAY
Primary Channel
Chart Type
18.11.2014
1271
SENSOR DISPLAY
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).
Stack Unit
1272
18.11.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
18.11.2014
1273
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1274
18.11.2014
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 sensor 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. 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
1275
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1276
18.11.2014
More
Knowledge Base: What do I need to monitor Dell servers?
http://kb.paessler.com/en/topic/45333
Knowledge Base: My Dell PowerEdge sensor fails to validate and I can't add it. What can I do?
http://kb.paessler.com/en/topic/61784
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
1277
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 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
sensors that are created.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
1278
Select the chassis 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.
19.09.2014
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.
Tags
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).
Channel Mask
Data Source
19.09.2014
1279
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
1280
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1281
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1282
19.09.2014
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 sensor 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. 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 .
19.09.2014
1283
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1284
19.09.2014
More
Knowledge Base: What do I need to monitor Dell servers?
http://kb.paessler.com/en/topic/45333
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1285
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 memory usage, PRTG will create one sensor for each memory type 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:
DISK FR EE SETTINGS
Disk
Select one or more disks 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.
1286
19.09.2014
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).
DISK FR EE SETTINGS
Disk
Shows the name of the disk that this sensor is monitoring. 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
19.09.2014
1287
SENSOR DISPLAY
Stack Unit
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.
1288
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1289
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1290
19.09.2014
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 sensor 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. 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 .
19.09.2014
1291
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1292
19.09.2014
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1293
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.
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.
Tags
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).
1294
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
1295
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1296
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1297
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 sensor 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. 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 .
1298
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
19.09.2014
1299
Others
For more general information about settings, please see Object Set t ings
1300
141
section.
19.09.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
19.09.2014
1301
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).
Type
SENSOR DISPLAY
Primary Channel
Chart Type
1302
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
1303
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1304
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1305
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 sensor 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. 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 .
1306
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
19.09.2014
1307
Others
For more general information about settings, please see Object Set t ings
1308
141
section.
19.09.2014
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 an HP LaserJet printer, PRTG will create one sensor for each performance
counter 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
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.
19.09.2014
1309
Tags
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).
If Value Changes
SENSOR DISPLAY
Primary Channel
Chart Type
1310
19.09.2014
SENSOR DISPLAY
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).
Stack Unit
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.
19.09.2014
1311
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1312
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1313
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 sensor 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. 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 .
1314
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
19.09.2014
1315
Others
For more general information about settings, please see Object Set t ings
1316
141
section.
19.09.2014
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 logical disks in a HP server, 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
18.11.2014
1317
Select the disks 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.
Tags
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).
1318
Shows the name of the disk that this sensor is monitoring. 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.
18.11.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
18.11.2014
1319
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1320
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1321
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 sensor 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. 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 .
1322
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
1323
More
Knowledge Base: Monitor HP ProLiant via SNMP
http://kb.paessler.com/en/topic/33133
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1324
141
section.
18.11.2014
1332
below.
For a general introduction to the technology behind SNMP, please see Monit oring via SNMP
2491 section.
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
18.11.2014
1325
Select the controllers 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.
Tags
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).
1326
18.11.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
18.11.2014
1327
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1328
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1329
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 sensor 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. 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 .
1330
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
1331
More
Knowledge Base: Monitor HP ProLiant via SNMP
http://kb.paessler.com/en/topic/33133
Knowledge Base: Which lookup values are supported by the SNMP HP ProLiant Memory
Controller Sensor?
http://kb.paessler.com/en/topic/44803
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1332
141
section.
18.11.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
18.11.2014
1333
Select the interfaces 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: 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
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.
Tags
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).
1334
18.11.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
18.11.2014
1335
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1336
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1337
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 sensor 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. 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 .
1338
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
1339
More
Knowledge Base: Monitor HP ProLiant via SNMP
http://kb.paessler.com/en/topic/33133
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1340
141
section.
18.11.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
18.11.2014
1341
Select the disks 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.
Tags
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).
1342
Shows the name of the disk that this sensor is monitoring. 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.
18.11.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
18.11.2014
1343
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1344
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1345
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 sensor 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. 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 .
1346
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
1347
More
Knowledge Base: Monitor HP ProLiant via SNMP
http://kb.paessler.com/en/topic/33133
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1348
141
section.
18.11.2014
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.
18.11.2014
1349
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.
Tags
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).
SENSOR DISPLAY
Primary Channel
Chart Type
1350
18.11.2014
SENSOR DISPLAY
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
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.
18.11.2014
1351
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1352
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1353
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 sensor 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. 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 .
1354
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
1355
More
Knowledge Base: Monitor HP ProLiant via SNMP
http://kb.paessler.com/en/topic/33133
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
Knowledge Base: Why is my SNMP HP ProLiant System Health sensor in error status after
updating PRTG?
http://kb.paessler.com/en/topic/61805
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
For more general information about settings, please see Object Set t ings
1356
141
section.
18.11.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the logical disks 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.
19.09.2014
1357
Tags
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).
SENSOR DISPLAY
Primary Channel
Chart Type
1358
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
1359
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1360
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1361
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 sensor 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. 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 .
1362
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1363
More
Knowledge Base: What are the requirements to monitor IBM System x?
http://kb.paessler.com/en/topic/59393
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1364
141
section.
19.09.2014
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 the physical 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the physical disks 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.
19.09.2014
1365
Tags
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).
SENSOR DISPLAY
Primary Channel
Chart Type
1366
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
1367
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1368
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1369
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 sensor 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. 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 .
1370
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1371
More
Knowledge Base: What are the requirements to monitor IBM System x?
http://kb.paessler.com/en/topic/59393
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1372
141
section.
19.09.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
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.
19.09.2014
1373
Tags
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).
Size
SENSOR DISPLAY
Primary Channel
Chart Type
1374
19.09.2014
SENSOR DISPLAY
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).
Stack Unit
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.
19.09.2014
1375
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1376
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1377
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 sensor 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. 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 .
1378
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1379
More
Knowledge Base: What are the requirements to monitor IBM System x?
http://kb.paessler.com/en/topic/59393
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1380
141
section.
19.09.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
19.09.2014
1381
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.
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.
Tags
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).
Measurement
1382
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
1383
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1384
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1385
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 sensor 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. 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 .
1386
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1387
More
Knowledge Base: What are the requirements to monitor IBM System x?
http://kb.paessler.com/en/topic/59393
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1388
141
section.
19.09.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the measuring points 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.
19.09.2014
1389
Tags
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).
Measuring Point
SENSOR DISPLAY
Primary Channel
Chart Type
1390
19.09.2014
SENSOR DISPLAY
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).
Stack Unit
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.
19.09.2014
1391
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1392
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1393
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 sensor 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. 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 .
1394
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1395
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1396
141
section.
19.09.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the disks 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.
19.09.2014
1397
Tags
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).
Name
Size
SENSOR DISPLAY
Primary Channel
Chart Type
1398
19.09.2014
SENSOR DISPLAY
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).
Stack Unit
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.
19.09.2014
1399
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1400
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1401
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 sensor 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. 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 .
1402
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
19.09.2014
1403
Others
For more general information about settings, please see Object Set t ings
1404
141
section.
19.09.2014
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.
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.
Tags
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).
19.09.2014
1405
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1406
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1407
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1408
19.09.2014
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 sensor 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. 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 .
19.09.2014
1409
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
1410
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1411
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 .
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.
18.11.2014
1413
1414
18.11.2014
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
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.
Tags
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).
18.11.2014
1415
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
If Value Changes
Define what this sensor will do when the sensor value changes.
You can choose between:
Ignore changes (default ): The sensor takes no action on
change.
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever the sensor value changes.
SENSOR DISPLAY
Primary Channel
Chart Type
1416
18.11.2014
SENSOR DISPLAY
Stack Unit
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.
18.11.2014
1417
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1418
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1419
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 sensor 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. 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 .
1420
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: How do SNMP, MIBs and OIDs work?
http://kb.paessler.com/en/topic/653
Knowledge Base: How can I import my MIB files into PRTG?
http://kb.paessler.com/en/topic/733
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
18.11.2014
1421
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
For more general information about settings, please see Object Set t ings
1422
141
section.
18.11.2014
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.
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.
Tags
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).
26.09.2014
1423
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!
This field is only visible if you enable percentage limit check above.
Specify an upper limit in percent for a Warning status. If the free
disk space of one of your drives overruns this percent value, the
sensor switches to Warning. Please enter an integer value or leave
the field empty.
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!
1424
26.09.2014
This field is only visible if you enable percentage limit check above.
Specify a lower limit in percent for a Warning status. If the free disk
space of one of your drives undercuts this percent value, the
sensor switches to warning. Please enter an integer value or leave
the field empty.
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!
This field is only visible if you enable percentage limit check above.
Specify a lower limit in percent for a Down status. If the free disk
space of one of your drives undercuts this percent value, the
sensor switches to Down. Please enter an integer value or leave
the field empty.
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!
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.
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 (byte
size channels). Additional fields appear below. The sensor enters
a Warning or Down status when free space limits are undercut
or overrun.
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.
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!
26.09.2014
1425
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 Warning. 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!
This field is only visible if you enable byte limit check above. Specify
a lower limit. Use the same unit as shown by the free bytes
channels of this sensor (by default this is MByte). If the free disk
space of one of your drives undercuts this bytes value, the sensor
switches to Warning. Please enter an integer value or leave the
field empty.
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!
This field is only visible if you enable byte limit check above. Specify
a lower limit. Use the same unit as shown by the free bytes
channels of this sensor (by default this is MByte). If the free disk
space of one of your drives undercuts this bytes value, the sensor
switches to Down. Please enter an integer value or leave the field
empty.
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!
Alarm on Missing/
Removed Disk
1426
26.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
26.09.2014
1427
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1428
26.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
26.09.2014
1429
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 sensor 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. 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 .
1430
26.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
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?
http://kb.paessler.com/en/topic/43183
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
Knowledge Base: Checklist: Setting up SNMP on Linux
http://kb.paessler.com/en/topic/5353
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
For more general information about settings, please see Object Set t ings
1432
141
section.
26.09.2014
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.
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.
Tags
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).
19.09.2014
1433
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1434
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1435
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1436
19.09.2014
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 sensor 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. 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 .
19.09.2014
1437
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
Knowledge Base: Checklist: Setting up SNMP on Linux
http://kb.paessler.com/en/topic/5353
1438
19.09.2014
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1439
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.
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.
Tags
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).
1440
26.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
26.09.2014
1441
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1442
26.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
26.09.2014
1443
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 sensor 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. 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 .
1444
26.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
26.09.2014
1445
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
Knowledge Base: Checklist: Setting up SNMP on Linux
http://kb.paessler.com/en/topic/5353
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
For more general information about settings, please see Object Set t ings
1446
141
section.
26.09.2014
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.
To monitor I/O on disks of a Linux/Unix system, PRTG creates one sensor for each disk 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:
Select one or more disks 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.
18.11.2014
1447
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).
SENSOR DISPLAY
Primary Channel
Chart Type
1448
18.11.2014
SENSOR DISPLAY
Stack Unit
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.
18.11.2014
1449
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1450
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1451
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 sensor 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. 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 .
1452
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
1453
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
Knowledge Base: Checklist: Setting up SNMP on Linux
http://kb.paessler.com/en/topic/5353
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
For more general information about settings, please see Object Set t ings
1454
141
section.
18.11.2014
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 memory usage, PRTG will create one sensor for each memory type 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:
MEMOR Y SETTINGS
Memory
Select one or more memory types 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.
19.09.2014
1455
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).
MEMOR Y SETTINGS
Memory
SENSOR DISPLAY
Primary Channel
Chart Type
1456
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
1457
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1458
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1459
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 sensor 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. 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 .
1460
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1461
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1462
141
section.
19.09.2014
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 disk space on a NetApp, 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the disks 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.
19.09.2014
1463
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).
Shows the name of the disk that this sensor is monitoring. 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.
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
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
1464
19.09.2014
SENSOR DISPLAY
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
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.
19.09.2014
1465
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1466
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1467
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 sensor 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. 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 .
1468
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1469
More
Knowledge Base: How can I monitor capacity and used disk space on a NetApp?
http://kb.paessler.com/en/topic/61231
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1470
141
section.
19.09.2014
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
18.11.2014
1471
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).
Measurement
1472
18.11.2014
NETAPP SPECIFIC
N/A Measurements
SENSOR DISPLAY
Primary Channel
Chart Type
18.11.2014
1473
SENSOR DISPLAY
Stack Unit
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.
1474
18.11.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
18.11.2014
1475
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1476
18.11.2014
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 sensor 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. 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
1477
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1478
18.11.2014
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
1479
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.
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.
Tags
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).
1480
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
1481
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1482
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1483
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 sensor 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. 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 .
1484
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1485
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1486
141
section.
19.09.2014
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 licenses on a NetApp, PRTG will create one sensor for each license. 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:
Select the licenses 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.
19.09.2014
1487
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).
SENSOR DISPLAY
Primary Channel
Chart Type
1488
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
1489
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1490
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1491
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 sensor 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. 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 .
1492
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1493
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1494
141
section.
19.09.2014
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 logical units on a NetApp, PRTG will create one sensor for each unit. 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:
Select the logical units 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.
19.09.2014
1495
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).
Shows the name of the logical unit that this sensor is monitoring.
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
1496
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
1497
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1498
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1499
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 sensor 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. 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 .
1500
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1501
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1502
141
section.
19.09.2014
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the interfaces 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.
19.09.2014
1503
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).
SENSOR DISPLAY
Primary Channel
Chart Type
1504
19.09.2014
SENSOR DISPLAY
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
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.
19.09.2014
1505
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1506
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1507
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 sensor 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. 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 .
1508
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1509
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1510
141
section.
19.09.2014
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.
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.
Tags
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).
19.09.2014
1511
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1512
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1513
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1514
19.09.2014
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 sensor 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. 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 .
19.09.2014
1515
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1516
19.09.2014
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1517
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 performance counters for environmental measurements on Poseidon
hardware, PRTG will create one sensor for each measuring point you choose. The settings you
make in this dialog are valid for all of the sensors that are created.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
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.
1518
19.09.2014
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).
SENSOR DISPLAY
Primary Channel
Chart Type
19.09.2014
1519
SENSOR DISPLAY
Stack Unit
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.
1520
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1521
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1522
19.09.2014
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 sensor 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. 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 .
19.09.2014
1523
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
1524
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1525
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.
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.
Tags
1526
19.09.2014
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).
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
1527
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1528
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1529
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 sensor 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. 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 .
1530
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
19.09.2014
1531
Others
For more general information about settings, please see Object Set t ings
1532
141
section.
19.09.2014
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 the logical disks in a QNAP NAS, 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the logical disks 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.
19.09.2014
1533
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).
SENSOR DISPLAY
Primary Channel
Chart Type
1534
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
1535
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1536
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1537
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 sensor 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. 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 .
1538
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
19.09.2014
1539
Others
For more general information about settings, please see Object Set t ings
1540
141
section.
19.09.2014
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 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
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:
Select the physical disks 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.
Unit
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.
19.09.2014
1541
Tags
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).
Unit
SENSOR DISPLAY
Primary Channel
Chart Type
1542
19.09.2014
SENSOR DISPLAY
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).
Stack Unit
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.
19.09.2014
1543
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1544
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1545
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 sensor 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. 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 .
1546
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
19.09.2014
1547
Others
For more general information about settings, please see Object Set t ings
1548
141
section.
19.09.2014
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 the system health of a QNAP NAS, please specify the unit of the
temperature measurement.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
19.09.2014
1549
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).
SENSOR DISPLAY
Primary Channel
Chart Type
1550
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
1551
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1552
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1553
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 sensor 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. 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 .
1554
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
19.09.2014
1555
Others
For more general information about settings, please see Object Set t ings
1556
141
section.
19.09.2014
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.
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
sensors that are created.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
R MON SPECIFIC
Ports
Select the ports 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.
26.09.2014
1557
Tags
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).
R MON SPECIFIC
Port
Channel Mask
SENSOR DISPLAY
Primary Channel
Chart Type
1558
26.09.2014
SENSOR DISPLAY
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).
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
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.
26.09.2014
1559
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1560
26.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
26.09.2014
1561
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 sensor 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. 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 .
1562
26.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
26.09.2014
1563
More
Knowledge Base: What value does the "Transmitted" channel of an RMON sensor show?
http://kb.paessler.com/en/topic/59821
Knowledge Base: How do PRTG's automatic port name and number updates work for SNMP
traffic sensors?
http://kb.paessler.com/en/topic/25893
Knowledge Base: Where is the volume line in graphs?
http://kb.paessler.com/en/topic/61272
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1564
141
section.
26.09.2014
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.
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.
Tags
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).
18.11.2014
1565
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1566
18.11.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
18.11.2014
1567
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1568
18.11.2014
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 sensor 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. 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
1569
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1570
18.11.2014
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
Knowledge Base: Why does PRTG write error messages into my SonicWALL log?
http://kb.paessler.com/en/topic/61961
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
1571
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the connections 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.
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
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.
Tags
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).
Index
Identification Method
SENSOR DISPLAY
Primary Channel
18.11.2014
1573
SENSOR DISPLAY
Chart Type
Stack Unit
1574
18.11.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
18.11.2014
1575
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1576
18.11.2014
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 sensor 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. 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
1577
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1578
18.11.2014
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
Knowledge Base: Why does PRTG write error messages into my SonicWALL log?
http://kb.paessler.com/en/topic/61961
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
1579
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 the logical disks in a Synology NAS, 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the logical disks 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.
1580
19.09.2014
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).
Name
SENSOR DISPLAY
Primary Channel
Chart Type
19.09.2014
1581
SENSOR DISPLAY
Stack Unit
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.
1582
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1583
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1584
19.09.2014
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 sensor 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. 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 .
19.09.2014
1585
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
1586
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1587
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 the physical disks in a Synology NAS, 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the physical disks 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.
1588
19.09.2014
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).
Type
SENSOR DISPLAY
Primary Channel
Chart Type
19.09.2014
1589
SENSOR DISPLAY
Stack Unit
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.
1590
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1591
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1592
19.09.2014
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 sensor 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. 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 .
19.09.2014
1593
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
1594
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1595
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 the system health of a Synology NAS, please specify the unit of the
temperature measurement.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
1596
19.09.2014
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).
SENSOR DISPLAY
Primary Channel
Chart Type
19.09.2014
1597
SENSOR DISPLAY
Stack Unit
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.
1598
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1599
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1600
19.09.2014
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 sensor 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. 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 .
19.09.2014
1601
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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.
1602
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1603
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.
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.
Tags
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).
SENSOR DISPLAY
Primary Channel
1604
19.09.2014
SENSOR DISPLAY
Chart Type
Stack Unit
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.
19.09.2014
1605
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1606
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1607
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 sensor 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. 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 .
1608
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Why does the SNMP System Uptime sensor report wrong values?
http://kb.paessler.com/en/topic/61249
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
19.09.2014
1609
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
For more general information about settings, please see Object Set t ings
1610
141
section.
19.09.2014
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
26.09.2014
1611
TR AFFIC SPECIFIC
Interface Number
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. 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
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.
Tags
1612
26.09.2014
26.09.2014
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).
1613
TR AFFIC SPECIFIC
Interface Number
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
1614
26.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
26.09.2014
1615
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1616
26.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
26.09.2014
1617
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 sensor 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. 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 .
1618
26.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
26.09.2014
1619
More
Knowledge Base: How do PRTG's automatic port name and number updates work for SNMP
traffic sensors?
http://kb.paessler.com/en/topic/25893
Knowledge Base: Where is the volume line in graphs?
http://kb.paessler.com/en/topic/61272
Knowledge Base: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
1620
141
section.
26.09.2014
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.
18.11.2014
1621
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.
Tags
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).
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
using the default value.
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
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 .
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 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
18.11.2014
1623
SENSOR DISPLAY
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).
Stack Unit
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.
1624
18.11.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
18.11.2014
1625
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1626
18.11.2014
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 sensor 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. 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
1627
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
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.
Recommended for normal use cases.
On: Write log files for all data received.
Note: Use with caution! When enabled, huge data files can be
created. Please use for a short time and for debugging purposes
only.
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]
source[10.0.23.50],
source[10.0.23.10-50],
source[10.0.23.10/255]
agent [ip]
agent[10.0.0.1]
ent erprise
[oid]
enterprise
[1.3.6.1.4.1.2.6.182.1.2.3
1.1.0]
bindings
[text]
bindings
[oid,value]
bindings
[1.3.6.1.4.1.2.6.182.1.2.3
1.1.0,error]
gent rap
[number]
gentrap[3], gentrap[2-6]
18.11.2014
1629
spect rap
[number]
spectrap[4], spectrap[0-3]
version
[number]
version[1], version[2]
communit y
[text]
community[public],
community[private]
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?
http://kb.paessler.com/en/topic/10193
Knowledge Base: What placeholders can I use with PRTG?
http://kb.paessler.com/en/topic/373
Knowledge Base: My SNMP sensors don't work. What can I do?
1630
18.11.2014
http://kb.paessler.com/en/topic/46863
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
1631
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the services 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.
1632
19.09.2014
Tags
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).
SENSOR DISPLAY
Primary Channel
Chart Type
19.09.2014
1633
SENSOR DISPLAY
Stack Unit
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.
1634
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1635
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1636
19.09.2014
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 sensor 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. 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 .
19.09.2014
1637
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
1638
141
section.
19.09.2014
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.
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.
Tags
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).
SENSOR SPECIFC
Timeout (Sec.)
26.09.2014
1639
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1640
26.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
26.09.2014
1641
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1642
26.09.2014
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 sensor 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. 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 .
26.09.2014
1643
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
1644
141
section.
26.09.2014
2498
section.
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.
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.
Tags
19.09.2014
1645
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).
SSH SPECIFIC
Connection Timeout
(Sec.)
Define a timeout for the connection. This is the the time the
sensor waits to establish a connection to the host. You should
keep this value as low as possible. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
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). 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:
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 settings, but define a different port number
below.
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
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.
1646
19.09.2014
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!
This field is only visible if you enable percentage limit check above.
Specify an upper limit in percent for a Warning status. If the free
disk space of one of your drives overruns this percent value, the
sensor switches to Warning. Please enter an integer value or leave
the field empty.
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!
19.09.2014
1647
This field is only visible if you enable percentage limit check above.
Specify a lower limit in percent for a Warning status. If the free disk
space of one of your drives undercuts this percent value, the
sensor switches to warning. Please enter an integer value or leave
the field empty.
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!
This field is only visible if you enable percentage limit check above.
Specify a lower limit in percent for a Down status. If the free disk
space of one of your drives undercuts this percent value, the
sensor switches to Down. Please enter an integer value or leave
the field empty.
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!
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.
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 (byte
size channels). Additional fields appear below. The sensor enters
a Warning or Down status when free space limits are undercut
or overrun.
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.
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!
1648
19.09.2014
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 Warning. 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!
This field is only visible if you enable byte limit check above. Specify
a lower limit. Use the same unit as shown by the free bytes
channels of this sensor (by default this is MByte). If the free disk
space of one of your drives undercuts this bytes value, the sensor
switches to Warning. Please enter an integer value or leave the
field empty.
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!
This field is only visible if you enable byte limit check above. Specify
a lower limit. Use the same unit as shown by the free bytes
channels of this sensor (by default this is MByte). If the free disk
space of one of your drives undercuts this bytes value, the sensor
switches to Down. Please enter an integer value or leave the field
empty.
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!
Alarm on Missing/
Removed Disk
19.09.2014
1649
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1650
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1651
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1652
19.09.2014
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 sensor 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. 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 .
19.09.2014
1653
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1654
19.09.2014
More
Knowledge Base: How and Where Does PRTG Store its Data?
http://kb.paessler.com/en/topic/463
Knowledge Base: Why do SSH Disk Free and SNMP Linux Disk Free show different values for
my target Linux system?
http://kb.paessler.com/en/topic/43183
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1655
2498
section.
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.
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.
Tags
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).
1656
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. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
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). 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:
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 settings, but define a different port number
below.
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
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
19.09.2014
1657
SENSOR DISPLAY
Chart Type
Stack Unit
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.
1658
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1659
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1660
19.09.2014
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 sensor 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. 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 .
19.09.2014
1661
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1662
19.09.2014
More
Knowledge Base: How and Where Does PRTG Store its Data?
http://kb.paessler.com/en/topic/463
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1663
2498
section.
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.
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.
Tags
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).
1664
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. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
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). 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:
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 settings, but define a different port number
below.
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
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
19.09.2014
1665
SENSOR DISPLAY
Chart Type
Stack Unit
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.
1666
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1667
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1668
19.09.2014
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 sensor 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. 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 .
19.09.2014
1669
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1670
19.09.2014
More
Knowledge Base: How and Where Does PRTG Store its Data?
http://kb.paessler.com/en/topic/463
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1671
2498
section.
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.
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.
Tags
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).
1672
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. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
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). 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:
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 settings, but define a different port number
below.
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
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
19.09.2014
1673
SENSOR DISPLAY
Chart Type
Stack Unit
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.
1674
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1675
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1676
19.09.2014
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 sensor 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. 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 .
19.09.2014
1677
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1678
19.09.2014
More
Knowledge Base: How and Where Does PRTG Store its Data?
http://kb.paessler.com/en/topic/463
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1679
2498
section.
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.
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.
Tags
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).
1680
19.09.2014
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.
Enter the packet size in bytes for the Ping. You can choose any
value between 1 and 10000. Please enter an integer value. We
recommend using the default value.
Packet Count
Custom Parameter
SSH SPECIFIC
Connection Timeout
(Sec.)
Define a timeout for the connection. This is the the time the
sensor waits to establish a connection to the host. You should
keep this value as low as possible. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
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). 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:
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 settings, but define a different port number
below.
19.09.2014
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.
1681
SSH SPECIFIC
Result Handling
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
Chart Type
Stack Unit
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.
1682
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1683
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1684
19.09.2014
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 sensor 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. 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 .
19.09.2014
1685
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: How and Where Does PRTG Store its Data?
http://kb.paessler.com/en/topic/463
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.
1686
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1687
2498
section.
This sensor type uses lookups to determine the status values of some sensor channels. For
details, please see section Define Lookups 2579 .
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the enclosures 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.
1688
19.09.2014
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.
Tags
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).
Durable ID
Name
Shows the name of the enclosure that this sensor monitors. Once
a sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew.
WWN
Shows the WWN (World Wide Name) of the enclosure that this
sensor monitors. Once a sensor is created, you cannot change this
value. It is shown for reference purposes only. If you need to
change this, please add the sensor anew.
19.09.2014
1689
SSH SPECIFIC
Connection Timeout
(Sec.)
Define a timeout for the connection. This is the the time the
sensor waits to establish a connection to the host. You should
keep this value as low as possible. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
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). 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:
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 settings, but define a different port number
below.
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
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
1690
19.09.2014
SENSOR DISPLAY
Chart Type
Stack Unit
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.
19.09.2014
1691
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1692
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1693
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 sensor 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. 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 .
1694
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Why does my SSH SAN sensor show a wrong status?
http://kb.paessler.com/en/topic/60145
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.
19.09.2014
1695
Others
For more general information about settings, please see Object Set t ings
1696
141
section.
19.09.2014
2498
section.
This sensor type uses lookups to determine the status values of some sensor channels. For
details, please see section Define Lookups 2579 .
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 volumes on an SAN device, PRTG will create one sensor for each volume
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:
Select the volumes 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.
19.09.2014
1697
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.
Tags
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).
SSH SPECIFIC
Connection Timeout
(Sec.)
Define a timeout for the connection. This is the the time the
sensor waits to establish a connection to the host. You should
keep this value as low as possible. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
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). 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:
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 settings, but define a different port number
below.
1698
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.
19.09.2014
SSH SPECIFIC
Result Handling
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.
Size
Shows the size of the volume that this sensor monitors. Once a
sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew.
SENSOR DISPLAY
Primary Channel
Chart Type
19.09.2014
1699
SENSOR DISPLAY
Stack Unit
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.
1700
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1701
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1702
19.09.2014
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 sensor 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. 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 .
19.09.2014
1703
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1704
19.09.2014
More
Knowledge Base: Why does my SSH SAN sensor show a wrong status?
http://kb.paessler.com/en/topic/60145
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1705
2498
section.
This sensor type uses lookups to determine the status values of some sensor channels. For
details, please see section Define Lookups 2579 .
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 disks on an SAN 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the disks 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.
1706
19.09.2014
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.
Tags
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).
SSH SPECIFIC
Connection Timeout
(Sec.)
Define a timeout for the connection. This is the the time the
sensor waits to establish a connection to the host. You should
keep this value as low as possible. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
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). 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:
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 settings, but define a different port number
below.
19.09.2014
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.
1707
SSH SPECIFIC
Result Handling
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.
Disk Name
Shows the label of disk that this sensor monitors. Once a sensor is
created, you cannot change this value. It is shown for reference
purposes only. If you need to change this, please add the sensor
anew.
Size
Shows the size of the disk that this sensor monitors. Once a
sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew.
SENSOR DISPLAY
Primary Channel
Chart Type
1708
19.09.2014
SENSOR DISPLAY
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).
Stack Unit
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.
19.09.2014
1709
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1710
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1711
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 sensor 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. 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 .
1712
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1713
More
Knowledge Base: Why does my SSH SAN sensor show a wrong status?
http://kb.paessler.com/en/topic/60145
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
For more general information about settings, please see Object Set t ings
1714
141
section.
19.09.2014
2498
section.
This sensor type uses lookups to determine the status values of some sensor channels. For
details, please see section Define Lookups 2579 .
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
19.09.2014
Select the metrics 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.
1715
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.
Tags
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).
SSH SPECIFIC
Connection Timeout
(Sec.)
Define a timeout for the connection. This is the the time the
sensor waits to establish a connection to the host. You should
keep this value as low as possible. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
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). The maximum value
is 60 seconds (1 minute). Please enter an integer value.
1716
19.09.2014
SSH SPECIFIC
SSH Port
Define which port this sensor uses for the SSH connection.
Choose between:
Inherit port number from parent device (default ): Use the
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 settings, but define a different port number
below.
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
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
Chart Type
19.09.2014
1717
SENSOR DISPLAY
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).
Stack Unit
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.
1718
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1719
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1720
19.09.2014
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 sensor 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. 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 .
19.09.2014
1721
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1722
19.09.2014
More
Knowledge Base: Why does my SSH SAN sensor show a wrong status?
http://kb.paessler.com/en/topic/60145
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1723
2498
section.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
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!
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.
18.11.2014
1725
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).
SENSOR SETTINGS
Script
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
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.
Value Type
If Value Changes
1726
18.11.2014
SENSOR SETTINGS
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.
SSH SPECIFIC
Connection Timeout
(Sec.)
Define a timeout for the connection. This is the the time the
sensor waits to establish a connection to the host. You should
keep this value as low as possible. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
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). 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:
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 settings, but define a different port number
below.
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
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.
18.11.2014
1727
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1728
18.11.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
18.11.2014
1729
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1730
18.11.2014
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 sensor 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. 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
1731
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1732
18.11.2014
More
Knowledge Base: Is there a shell script example for PRTG's SSH Script Sensor?
http://kb.paessler.com/en/topic/39513
Information about custom scripts and executables
Applicat ion Programming Int erface (API) Definit ion
Addit ional Sensor Ty pes (Cust om Sensors)
2571
2217
Knowledge Base: What is the Mutex Name in PRTG's EXE/Script Sensor's settings?
http://kb.paessler.com/en/topic/6673
Knowledge Base: How and Where Does PRTG Store its Data?
http://kb.paessler.com/en/topic/463
Knowledge Base: How can I test if parameters are correctly transmitted to my script when
using an EXE/Script sensor?
http://kb.paessler.com/en/topic/11283
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
1733
2498
section.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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.
Tags
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).
19.09.2014
1735
SENSOR SETTINGS
Script
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
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.
EXE Result
Define what will be done with the results the executable file gives
back. Choose between:
Discard EX E result : Do not store the requested web page.
Writ e EX E result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received from the script to the
"Logs (Sensors)" directory (on the Master node, if in a cluster).
This is for debugging purposes. The file will be overridden with
each scanning interval. For information on how to find the folder
used for storage, please see Dat a St orage 2611 section.
SSH SPECIFIC
Connection Timeout
(Sec.)
Define a timeout for the connection. This is the the time the
sensor waits to establish a connection to the host. You should
keep this value as low as possible. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
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). The maximum value
is 60 seconds (1 minute). Please enter an integer value.
1736
19.09.2014
SSH SPECIFIC
SSH Port
Define which port this sensor uses for the SSH connection.
Choose between:
Inherit port number from parent device (default ): Use the
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 settings, but define a different port number
below.
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
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
Chart Type
19.09.2014
1737
SENSOR DISPLAY
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).
Stack Unit
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.
1738
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1739
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1740
19.09.2014
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 sensor 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. 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 .
19.09.2014
1741
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1742
19.09.2014
More
Information about custom scripts and executables
Applicat ion Programming Int erface (API) Definit ion
Addit ional Sensor Ty pes (Cust om Sensors)
2571
2217
Knowledge Base: What is the Mutex Name in PRTG's EXE/Script Sensor's settings?
http://kb.paessler.com/en/topic/6673
Knowledge Base: How and Where Does PRTG Store its Data?
http://kb.paessler.com/en/topic/463
Knowledge Base: How can I test if parameters are correctly transmitted to my script when
using an EXE/Script sensor?
http://kb.paessler.com/en/topic/11283
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1743
2498
section.
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 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the disks 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.
1744
19.09.2014
Tags
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).
Shows the name of the disk that this sensor monitors. Once a
sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew.
SSH SPECIFIC
Connection Timeout
(Sec.)
Define a timeout for the connection. This is the the time the
sensor waits to establish a connection to the host. You should
keep this value as low as possible. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
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). 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:
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.
19.09.2014
1745
SSH SPECIFIC
Ent er cust om port number: Do not use the port number from
the parent device settings, but define a different port number
below.
Use Port Number
This field is only visible if you 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
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
Chart Type
Stack Unit
1746
19.09.2014
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.
19.09.2014
1747
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1748
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1749
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 sensor 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. 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 .
1750
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1751
More
Knowledge Base: How and Where Does PRTG Store its Data?
http://kb.paessler.com/en/topic/463
Knowledge Base: Settings on ESXi 5 host when monitoring via SSH VMware ESX(i) Disk Sensor
http://kb.paessler.com/en/topic/32603
Knowledge Base: Why do I need root credentials when monitoring VMware hosts via SSH?
http://kb.paessler.com/en/topic/33763
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
For more general information about settings, please see Object Set t ings
1752
141
section.
19.09.2014
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.
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.
18.11.2014
1753
Tags
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).
SSL SPECIFIC
Timeout (Sec.)
Enter a timeout in seconds for the port connect. If the reply takes
longer than this value defines, PRTG aborts the request and shows
a corresponding error message. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
Port
SENSOR DISPLAY
Primary Channel
Chart Type
1754
18.11.2014
SENSOR DISPLAY
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).
Stack Unit
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.
18.11.2014
1755
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1756
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1757
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 sensor 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. 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 .
1758
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
1759
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.
Sensor Settings
On the sensor's details page, click on the Set t ings tab to change settings.
1760
19.09.2014
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.
Tags
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).
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
recommend using the default value.
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
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 .
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 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 .
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 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
1762
19.09.2014
SENSOR DISPLAY
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).
Stack Unit
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.
19.09.2014
1763
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1764
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1765
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 sensor 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. 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 .
1766
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
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.
Recommended for normal use cases.
On: Write log files for all data received.
Note: Use with caution! When enabled, huge data files can be
created. Please use for a short time and for debugging purposes
only.
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]
source[10.0.23.50]
source[10.0.23.10-50]
source[10.0.23.10/255]
facilit y
[number]
facility[2]
facility[5-7]
facility[5] OR facility[6]
severit y
[number]
severity[4]
severity[1-3]
severity[1] AND severity
[2]
1768
19.09.2014
host name
[text]
hostname
[www.example.com]
t ag[text]
tag[su]
appname
[text]
appname[myproc]
procid
[text]
procid[1860]
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]
data
[exampleSDID@1234]
dat a
[id,param]
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!
19.09.2014
1769
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: What placeholders can I use with PRTG?
http://kb.paessler.com/en/topic/373
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
For more general information about settings, please see Object Set t ings
1770
141
section.
19.09.2014
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.
Tags
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).
26.09.2014
1771
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1772
26.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
26.09.2014
1773
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1774
26.09.2014
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
For more general information about settings, please see Object Set t ings
26.09.2014
141
section.
1775
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.
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.
Tags
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).
SENSOR SPECIFIC
Timeout (Sec.)
Port
Enter the number of the port the TFTP service is running on. The
sensor connects to this port. Please enter an integer value.
1776
19.09.2014
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.
Please enter a string.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
1777
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1778
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1779
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 sensor 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. 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 .
1780
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1781
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
For more general information about settings, please see Object Set t ings
1782
141
section.
19.09.2014
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.
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.
Tags
18.11.2014
1783
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).
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
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
Chart Type
1784
18.11.2014
SENSOR DISPLAY
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).
Stack Unit
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.
18.11.2014
1785
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1786
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1787
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 sensor 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. 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 .
1788
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
1789
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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.
Tags
1790
19.09.2014
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).
CONTAINER SETTINGS
Env ID
Name
OS
Description
Powered Off
Containers
SENSOR DISPLAY
Primary Channel
19.09.2014
1791
SENSOR DISPLAY
Chart Type
Stack Unit
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.
1792
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1793
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1794
19.09.2014
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 sensor 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. 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 .
19.09.2014
1795
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
1796
141
section.
19.09.2014
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
CONTAINER SETTINGS
Container
Select all containers for which you want to create a sensor. You
see a list with the names of all items which are available to monitor.
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.
Tags
19.09.2014
1797
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).
CONTAINER SETTINGS
Env ID
Name
OS
Description
Powered Off
Containers
SENSOR DISPLAY
Primary Channel
1798
19.09.2014
SENSOR DISPLAY
Chart Type
Stack Unit
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.
19.09.2014
1799
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1800
19.09.2014
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 sensor 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. 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 .
19.09.2014
1801
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
1802
141
section.
19.09.2014
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 ESX servers, PRTG will create one sensor for each hardware element 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:
Select the hardware elements you want to add a sensor for. You
see a list with the names of all items which are available to monitor.
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.
19.09.2014
1803
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).
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
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.
1804
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
1805
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1806
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1807
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 sensor 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. 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 .
1808
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1809
1810
26.09.2014
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Select the host server 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.
Tags
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).
26.09.2014
1811
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1812
26.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
26.09.2014
1813
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1814
26.09.2014
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 sensor 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. 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 .
26.09.2014
1815
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: How can I increase the connection limit on VMware systems?
http://kb.paessler.com/en/topic/30643
Knowledge Base: Monitoring ESXi 5.1 and higher: Handshake Failure on Windows XP/Server
2003
http://kb.paessler.com/en/topic/59173
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
1816
26.09.2014
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
For more general information about settings, please see Object Set t ings
26.09.2014
141
section.
1817
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.
1818
26.09.2014
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.
Tags
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).
SENSOR DISPLAY
Primary Channel
Chart Type
26.09.2014
1819
SENSOR DISPLAY
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).
Stack Unit
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.
1820
26.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
26.09.2014
1821
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1822
26.09.2014
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 sensor 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. 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 .
26.09.2014
1823
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: How can I increase the connection limit on VMware systems?
http://kb.paessler.com/en/topic/30643
Knowledge Base: Monitoring ESXi 5.1 and higher: Handshake Failure on Windows XP/Server
2003
http://kb.paessler.com/en/topic/59173
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
1824
26.09.2014
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
For more general information about settings, please see Object Set t ings
26.09.2014
141
section.
1825
1826
26.09.2014
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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
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.
Tags
26.09.2014
1827
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).
Handling of "Powered
off" VM
SENSOR DISPLAY
Primary Channel
Chart Type
1828
26.09.2014
SENSOR DISPLAY
Stack Unit
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.
26.09.2014
1829
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1830
26.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
26.09.2014
1831
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 sensor 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. 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 .
1832
26.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: How can I increase the connection limit on VMware systems?
http://kb.paessler.com/en/topic/30643
Knowledge Base: Monitoring ESXi 5.1 and higher: Handshake Failure on Windows XP/Server
2003
http://kb.paessler.com/en/topic/59173
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
26.09.2014
1833
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
For more general information about settings, please see Object Set t ings
1834
141
section.
26.09.2014
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.
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.
Tags
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).
CU STOM QU ER Y SPECIFIC
Namespace
19.09.2014
Enter the namespace for the query. Default value is root /cimv2.
1835
CU STOM QU ER Y SPECIFIC
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
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
Chart Type
1836
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
1837
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1838
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1839
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 sensor 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. 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 .
1840
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
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
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
For more general information about settings, please see Object Set t ings
1842
141
section.
19.09.2014
2495
19.09.2014
1843
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.
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.
Tags
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).
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
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
1845
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1846
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1847
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 sensor 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. 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 .
1848
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1849
More
Knowledge Base: My Windows sensors do not work when using direct Performance Counter
access. What can I do?
http://kb.paessler.com/en/topic/47263
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
For more general information about settings, please see Object Set t ings
1850
141
section.
19.09.2014
2495
19.09.2014
1851
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
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.
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.
Tags
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).
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.
1852
19.09.2014
DEBU G OPTIONS
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received from the sensor to the
"Logs (Sensor)" directory (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
Chart Type
Stack Unit
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.
19.09.2014
1853
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1854
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1855
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 sensor 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. 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 .
1856
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1857
More
Knowledge Base: My Windows sensors do not work when using direct Performance Counter
access. What can I do?
http://kb.paessler.com/en/topic/47263
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
For more general information about settings, please see Object Set t ings
1858
141
section.
19.09.2014
2495
19.09.2014
1859
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
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.
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.
Tags
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).
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.
1860
19.09.2014
DEBU G OPTIONS
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received from the sensor to the
"Logs (Sensor)" directory (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
Chart Type
Stack Unit
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.
19.09.2014
1861
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1862
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1863
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 sensor 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. 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 .
1864
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
1865
More
Knowledge Base: My Windows sensors do not work when using direct Performance Counter
access. What can I do?
http://kb.paessler.com/en/topic/47263
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
For more general information about settings, please see Object Set t ings
1866
141
section.
19.09.2014
2495
19.09.2014
1867
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
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
Tags
1868
19.09.2014
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).
Shows the name of the web service instance that this sensor
monitors. Once a sensor is created, you cannot change this value.
It is shown for reference purposes only. If you need to change
this, please add the sensor anew.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
19.09.2014
1869
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.
1870
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1871
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1872
19.09.2014
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 sensor 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. 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 .
19.09.2014
1873
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1874
19.09.2014
More
Knowledge Base: My Windows sensors do not work when using direct Performance Counter
access. What can I do?
http://kb.paessler.com/en/topic/47263
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1875
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.
1876
26.09.2014
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.
Tags
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).
SENSOR SETTINGS
If Value Changes
Define what this sensor will do when the sensor value changes.
You can choose between:
Ignore changes (default ): The sensor takes no action on
change.
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever the sensor value changes.
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.
26.09.2014
1877
DEBU G OPTIONS
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received from the sensor to the
"Logs (Sensor)" directory (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
Chart Type
Stack Unit
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.
1878
26.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
26.09.2014
1879
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1880
26.09.2014
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 sensor 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. 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 .
26.09.2014
1881
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: How do I enable the Remote Registry Service on a Windows PC?
http://kb.paessler.com/en/topic/15543
Knowledge Base: Fixing a Protocol Error Appearing With Windows Last Update Sensor
http://kb.paessler.com/en/topic/41113
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
1882
26.09.2014
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
For more general information about settings, please see Object Set t ings
26.09.2014
141
section.
1883
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.
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.
1884
19.09.2014
Tags
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).
SENSOR SETTINGS
User Filter (optional)
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
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.
19.09.2014
1885
SENSOR SETTINGS
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever the sensor value changes.
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
Chart Type
1886
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
1887
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1888
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1889
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 sensor 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. 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 .
1890
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1891
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
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
SENSOR SETTINGS
Message Queue
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. If there are no message queues available, you will
see a corresponding message.
Note: Sub-queues are not supported by this sensor.
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.
18.11.2014
1893
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).
SENSOR SETTINGS
Message Queue
Shows the name of the queue that this sensor monitors. Once a
sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew.
Shows the type of the queue that this sensor monitors. Once a
sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew.
If Value Changes
Define what this sensor will do when the sensor value changes.
You can choose between:
Ignore changes (default ): The sensor takes no action on
change.
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever the sensor value changes.
1894
18.11.2014
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
Chart Type
Stack Unit
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.
18.11.2014
1895
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1896
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1897
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 sensor 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. 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 .
1898
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: How do I activate Message Queuing in my Windows installation?
http://kb.paessler.com/en/topic/25963
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.
18.11.2014
1899
Others
For more general information about settings, please see Object Set t ings
1900
141
section.
18.11.2014
2495
26.09.2014
1901
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.
For devices with multiple network cards, PRTG creates one sensor for each interface you
select in the Add Sensor dialog. The settings you make in this dialog are valid for all of the
sensors that are created.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Network Interface
Select the network card(s) 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.
Tags
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).
1902
26.09.2014
SENSOR SPECIFIC
Selected Interface
Shows the name of the network card that this sensor monitors.
Once a sensor is created, you cannot change this value. It is
shown for reference purposes only. If you need to change this,
please add the sensor anew.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
26.09.2014
1903
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1904
26.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
26.09.2014
1905
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 sensor 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. 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 .
1906
26.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
26.09.2014
1907
More
Knowledge Base: My Windows sensors do not work when using direct Performance Counter
access. What can I do?
http://kb.paessler.com/en/topic/47263
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
For more general information about settings, please see Object Set t ings
1908
141
section.
26.09.2014
2495
19.09.2014
1909
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
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.
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.
Tags
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).
SENSOR DISPLAY
Primary Channel
Chart Type
1910
19.09.2014
SENSOR DISPLAY
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).
Stack Unit
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.
19.09.2014
1911
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1912
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1913
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 sensor 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. 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 .
1914
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My Windows sensors do not work when using direct Performance Counter
access. What can I do?
http://kb.paessler.com/en/topic/47263
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.
19.09.2014
1915
Others
For more general information about settings, please see Object Set t ings
1916
141
section.
19.09.2014
2495
19.09.2014
1917
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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:').
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.
Tags
1918
19.09.2014
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).
These fields show the parameters that are used to query data for
this sensor from the target 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.
WMI Class
Counter
Time Stamp
Time Frequency
Counter Type
Sensor Result
Define what will be done with the result of the sensor. Choose
between:
Discard sensor result : Do not store the results.
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received to the "Logs (System)"
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.
SENSOR DISPLAY
Primary Channel
19.09.2014
1919
SENSOR DISPLAY
Chart Type
Stack Unit
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.
1920
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1921
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1922
19.09.2014
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 sensor 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. 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 .
19.09.2014
1923
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
1924
19.09.2014
More
Knowledge Base: My Windows sensors do not work when using direct Performance Counter
access. What can I do?
http://kb.paessler.com/en/topic/47263
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1925
2338
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.
1926
18.11.2014
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 print queues, PRTG will add a sensor for each task 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
Print Queue
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. 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
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.
Tags
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).
18.11.2014
1927
SENSOR SETTINGS
Print Queue
Advanced Status
Option
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
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
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
Chart Type
Stack Unit
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.
18.11.2014
1929
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1930
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1931
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 sensor 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. 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 .
1932
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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.
18.11.2014
1933
Others
For more general information about settings, please see Object Set t ings
1934
141
section.
18.11.2014
2495
18.11.2014
1935
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.
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.
Tags
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).
1936
18.11.2014
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
Stack Unit
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.
18.11.2014
1937
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1938
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1939
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 sensor 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. 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 .
1940
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
1941
More
Knowledge Base: My Windows sensors do not work when using direct Performance Counter
access. What can I do?
http://kb.paessler.com/en/topic/47263
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
For more general information about settings, please see Object Set t ings
1942
141
section.
18.11.2014
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.
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.
19.09.2014
1943
Tags
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).
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.
Define the method that you want to use for the search string.
Choose between:
Plain Text : Search for a simple string.
Regular Expression: Search using a regular expression. For
more details, see Regular Expressions 2587 section.
19.09.2014
1945
Define the method you want to use for the search string. Choose
between:
Plain Text : Search for a simple string.
Regular Expression: Search using a regular expression. For
more details, see Regular Expressions 2587 section.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1946
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1947
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1948
19.09.2014
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 sensor 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. 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 .
19.09.2014
1949
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
How do I discern 32-bit registry values vs. 64-bit registry values?
http://kb.paessler.com/en/topic/25513
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.
1950
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1951
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
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 scheduled tasks, PRTG creates one sensor for each task 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
Task Name
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. 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,
please add the sensor anew.
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.
18.11.2014
1953
Tags
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).
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
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.
If Value Changes
Define what this sensor will do when the sensor value changes.
You can choose between:
Ignore changes (default ): The sensor takes no action on
change.
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever the sensor value changes.
DEBU G OPTIONS
Sensor Result
1954
Define what PRTG will do with the result of the sensor. Choose
between:
18.11.2014
DEBU G OPTIONS
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
Chart Type
Stack Unit
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.
18.11.2014
1955
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1956
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1957
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 sensor 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. 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 .
1958
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
1959
More
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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
For more general information about settings, please see Object Set t ings
1960
141
section.
18.11.2014
2495
19.09.2014
1961
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.
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.
Tags
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).
SENSOR DISPLAY
Primary Channel
Chart Type
1962
19.09.2014
SENSOR DISPLAY
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).
Stack Unit
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.
19.09.2014
1963
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1964
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
1965
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 sensor 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. 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 .
1966
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My Windows sensors do not work when using direct Performance Counter
access. What can I do?
http://kb.paessler.com/en/topic/47263
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.
19.09.2014
1967
Others
For more general information about settings, please see Object Set t ings
1968
141
section.
19.09.2014
1971
18.11.2014
1969
680
section below.
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.
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.
Tags
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).
SENSOR DISPLAY
Primary Channel
Chart Type
1970
18.11.2014
SENSOR DISPLAY
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).
Stack Unit
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.
18.11.2014
1971
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
1972
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
1973
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 sensor 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. 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 .
1974
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: How do I enable and use remote commands in Windows PowerShell?
http://kb.paessler.com/en/topic/44453
Knowledge Base: My Powershell sensor returns an error message. What can I do?
http://kb.paessler.com/en/topic/59473
Knowledge Base: "No Logon Servers Available" when Using PowerShell Sensors
http://kb.paessler.com/en/topic/59745
Knowledge Base: How can I increase memory for Remote PowerShell?
http://kb.paessler.com/en/topic/61922
Knowledge Base: Which .NET version does PRTG require?
18.11.2014
1975
http://kb.paessler.com/en/topic/60543
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
For more general information about settings, please see Object Set t ings
1976
141
section.
18.11.2014
2495
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
CU STOM QU ER Y SPECIFIC
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
CU STOM QU ER Y SPECIFIC
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
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.
Tags
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).
CU STOM QU ER Y SPECIFIC
Namespace
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
is shown for reference purposes only. If you need to change this,
please add the sensor anew.
1978
18.11.2014
CU STOM QU ER Y SPECIFIC
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>
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 <#PH2> or leave the field empty.
Placeholder <#PH3>
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 <#PH3> or leave the field empty.
If Value Changes
Define what this sensor will do when the sensor value changes.
You can choose between:
Ignore changes (default ): The sensor takes no action on
change.
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever the sensor value changes.
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
Division
SENSOR DISPLAY
Primary Channel
Chart Type
18.11.2014
1979
SENSOR DISPLAY
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).
Stack Unit
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.
1980
18.11.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
18.11.2014
1981
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1982
18.11.2014
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 sensor 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. 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
1983
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Addit ional Sensor Ty pes (Cust om Sensors)
2217
1984
18.11.2014
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
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
1985
2495
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
CU STOM QU ER Y SPECIFIC
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
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.
Tags
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).
CU STOM QU ER Y SPECIFIC
Namespace
WQL File
Shows the name of the file that this sensor is using. 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.
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>
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 <#PH2> or leave the field empty.
Placeholder <#PH3>
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 <#PH3> or leave the field empty.
19.09.2014
1987
CU STOM QU ER Y SPECIFIC
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
sensor will be set to an error state. Please enter a string or leave
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
sensor will be set to an error state. Please enter a string or leave
the field empty.
1988
19.09.2014
CU STOM QU ER Y SPECIFIC
Regular Expression: Treat the search pattern as a Regular
Expression 2587 .
Maximum Length of
String
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
Index of Capturing
Group
Decimal Separator
Thousands Separator
Sensor Result
Define what will be done with the results the sensor receives.
Choose between:
Discard sensor result : Do not store the results.
19.09.2014
1989
CU STOM QU ER Y SPECIFIC
Writ e sensor result t o disk (Filename: "Result of Sensor
(ID].t xt "): Store the last result received to the "Logs (Sensors)"
directory (on the Master node, if in a cluster). This is for
debugging purposes. The file will be overridden with each
scanning interval. For information on how to find the folder used
for storage, please see Dat a St orage 2611 section.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
1990
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
1991
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
1992
19.09.2014
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 sensor 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. 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 .
19.09.2014
1993
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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"
Group 2 contains "3.49"
Group 3 contains "3.555"
Group 4 contains "3.90"
Please keep in mind this note about index and capturing groups when using number
extraction.
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
1995
2495
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.
If you select more than one log file, PRTG will create one sensor for each selection. 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:
The Windows event log provides several different log files. 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.
1996
19.09.2014
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.
Tags
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).
Shows the Windows log file that this sensor monitors. Once a
sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew.
Sensor Result
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.
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
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.
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:
Off: Do not filter by event ID.
On: Enable filtering by 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
this option, this sensor processes only messages that match the
defined value. Choose between:
Off: Do not filter by event category.
On: Enable filtering by event category.
1998
19.09.2014
Filter all received events for a certain event user. If you enable this
option, this sensor processes only messages that match the
defined value. Choose between:
Off: Do not filter by event user.
On: Enable filtering by event user.
Filter by Computer
Filter all received events for a certain event computer. If you enable
this option, this sensor processes only messages that match the
defined value. Choose between:
Off: Do not filter by event computer.
On: Enable filtering by event computer.
Filter by Message
Filter all received events for a certain event message. If you enable
this option, this sensor processes only messages that match the
defined value. Choose between:
Off: Do not filter by event message.
On: Enable filtering by event message.
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
Stack Unit
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.
2000
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
2001
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
2002
19.09.2014
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 sensor 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. 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 .
19.09.2014
2003
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
Knowledge Base: My Event Log sensor ignores changes in the event log. What can I do?
http://kb.paessler.com/en/topic/59803
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
2004
19.09.2014
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
2005
2495
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 an Exchange Server, PRTG will create one sensor for each performance
counter 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:
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
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 might be able to select aspects regarding:
SMTP Server: Queue Lengths
2006
19.09.2014
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.
Tags
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).
19.09.2014
2007
These fields show the parameters that are used to query data for
this sensor from the target 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.
WMI Class
Counter
Time Stamp
Time Frequency
Counter Type
Sensor Result
Define what will be done with the result of the sensor. Choose
between:
Discard sensor result : Do not store the results.
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received to the "Logs (System)"
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.
SENSOR DISPLAY
Primary Channel
Chart Type
2008
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
2009
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
2010
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
2011
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 sensor 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. 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 .
2012
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
2013
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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
For more general information about settings, please see Object Set t ings
2014
141
section.
19.09.2014
2495
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
19.09.2014
2015
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.
Tags
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).
2016
These fields show the parameters that are used to query data for
this sensor from the target 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.
19.09.2014
Define what will be done with the result of the sensor. Choose
between:
Discard sensor result : Do not store the results.
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received to the "Logs (System)"
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.
SENSOR DISPLAY
Primary Channel
Chart Type
19.09.2014
2017
SENSOR DISPLAY
Stack Unit
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.
2018
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
2019
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
2020
19.09.2014
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 sensor 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. 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 .
19.09.2014
2021
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
2022
19.09.2014
More
Knowledge Base: Types of Transport Queues in Microsoft Exchange
http://kb.paessler.com/en/topic/55413
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
2023
2495
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.
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.
Tags
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).
2024
19.09.2014
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
changes. You can choose between:
Ignore changes (default ): The sensor takes no action on
change.
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that the timestamp has changed. In
combination with a Change Trigger, you can use this mechanism
to trigger a notification 2227 whenever the timestamp changes.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
19.09.2014
2025
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.
2026
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
2027
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
2028
19.09.2014
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 sensor 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. 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 .
19.09.2014
2029
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
2030
19.09.2014
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
2031
2495
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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.
2032
19.09.2014
Tags
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).
19.09.2014
2033
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!
This field is only visible if you enable percentage limit check above.
Specify an upper limit in percent for a Warning status. If the free
disk space of one of your drives overruns this percent value, the
sensor switches to Warning. Please enter an integer value or leave
the field empty.
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!
This field is only visible if you enable percentage limit check above.
Specify a lower limit in percent for a Warning status. If the free disk
space of one of your drives undercuts this percent value, the
sensor switches to warning. Please enter an integer value or leave
the field empty.
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!
This field is only visible if you enable percentage limit check above.
Specify a lower limit in percent for a Down status. If the free disk
space of one of your drives undercuts this percent value, the
sensor switches to Down. Please enter an integer value or leave
the field empty.
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!
2034
19.09.2014
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.
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 (byte
size channels). Additional fields appear below. The sensor enters
a Warning or Down status when free space limits are undercut
or overrun.
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.
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!
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 Warning. 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!
19.09.2014
This field is only visible if you enable byte limit check above. Specify
a lower limit. Use the same unit as shown by the free bytes
channels of this sensor (by default this is MByte). If the free disk
space of one of your drives undercuts this bytes value, the sensor
switches to Warning. Please enter an integer value or leave the
field empty.
2035
This field is only visible if you enable byte limit check above. Specify
a lower limit. Use the same unit as shown by the free bytes
channels of this sensor (by default this is MByte). If the free disk
space of one of your drives undercuts this bytes value, the sensor
switches to Down. Please enter an integer value or leave the field
empty.
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!
Alarm on Missing/
Removed Disk
SENSOR DISPLAY
Primary Channel
Chart Type
2036
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
2037
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
2038
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
2039
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 sensor 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. 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 .
2040
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
2041
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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
For more general information about settings, please see Object Set t ings
2042
141
section.
19.09.2014
2495
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 the health of a disk, PRTG will create one sensor for each IDE device you
choose. The settings you make in this dialog are valid for all of the sensors that are created.
19.09.2014
2043
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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. . The items shown in the list are specific to the
parent device you create the sensor on.
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.
Tags
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).
SMAR T SPECIFIC
Serial No.
2044
19.09.2014
SMAR T SPECIFIC
Size (GB)
Name
Timeout (sec)
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
19.09.2014
2045
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.
2046
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
2047
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
2048
19.09.2014
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 sensor 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. 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 .
19.09.2014
2049
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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.
2050
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
2051
2495
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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.
2052
19.09.2014
Tags
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).
These fields show the parameters that are used to query data for
this sensor from the target 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.
WMI Class
Counter
Time Stamp
Time Frequency
Counter Type
Sensor Result
Define what will be done with the result of the sensor. Choose
between:
Discard sensor result : Do not store the results.
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received to the "Logs (System)"
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
2053
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
2054
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
2055
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
2056
19.09.2014
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 sensor 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. 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 .
19.09.2014
2057
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
2058
19.09.2014
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
2059
2495
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.
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.
Tags
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).
2060
19.09.2014
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
Stack Unit
19.09.2014
2061
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.
2062
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
2063
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
2064
19.09.2014
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 sensor 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. 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 .
19.09.2014
2065
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
2066
19.09.2014
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
2067
More
Knowledge Base: Why does my WMI Microsoft SQL Server 2005 Sensor not work anymore?
http://kb.paessler.com/en/topic/44713
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.
Logins
Logouts
Full Scans
2068
19.09.2014
Database Pages
Stolen Pages
Connection Memory
(KB)
Lock Requests
Deadlocks
Average amount of wait time (in milliseconds) for each lock request
that resulted in a wait.
19.09.2014
2069
SQL Compilations
SQL Re-Compilations
Note: This sensor can only be added to a device (computer) running a Microsoft SQL database.
For this sensor type credentials for Windows systems must be defined for the device you want
to use the sensor on.
Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high
impact on the system performance! Try to stay below 200 WMI sensors per probe 77 . Above
this number, please consider using multiple Remot e Probes 2589 for load balancing.
For a general introduction to the technology behind WMI, please see Monit oring via WMI
section.
2495
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
2070
19.09.2014
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: Display name and service name are provided as returned by
the SQL server.
Enter the version of the SQL server. Usually, you can keep the
default value.
19.09.2014
2071
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.
Tags
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).
Name
Shows the name of the server instance that this sensor monitors.
Once a sensor is created, you cannot change this value. It is
shown for reference purposes only. If you need to change this,
please add the sensor anew.
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
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
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
Chart Type
19.09.2014
2073
SENSOR DISPLAY
Stack Unit
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.
2074
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
2075
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
2076
19.09.2014
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 sensor 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. 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 .
19.09.2014
2077
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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.
2078
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
2079
Logins
Logouts
Full Scans
Page Splits
Database Pages
Stolen Pages
Connection Memory
(KB)
2080
19.09.2014
Lock Requests
Deadlocks
Average amount of wait time (in milliseconds) for each lock request
that resulted in a wait.
Batch Requests
SQL Compilations
SQL Re-Compilations
Note: This sensor can only be added to a device (computer) running a Microsoft SQL database.
For this sensor type credentials for Windows systems must be defined for the device you want
to use the sensor on.
Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high
impact on the system performance! Try to stay below 200 WMI sensors per probe 77 . Above
this number, please consider using multiple Remot e Probes 2589 for load balancing.
For a general introduction to the technology behind WMI, please see Monit oring via WMI
section.
19.09.2014
2495
2081
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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: Display name and service name are provided as returned by
the SQL server.
Enter the version of the SQL server. Usually, you can keep the
default value.
2082
19.09.2014
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.
Tags
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).
19.09.2014
2083
Name
Shows the name of the server instance that this sensor monitors.
Once a sensor is created, you cannot change this value. It is
shown for reference purposes only. If you need to change this,
please add the sensor anew.
Select whether PRTG selects the name of the WMI class used for
monitoring automatically. Choose between:
Aut omat ic: Choose WMI class automatically. We recommend this
setting.
Manual: Manually enter a WMI class name. Use this if your server
instance returns an error code in automatic mode.
WMI Class
This field is only shown if you enable manual WMI class selection
above. This setting is intended for experienced users only. Enter
the WMI class name that the sensor uses for monitoring your
server instance.
Sensor Result
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.
2084
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
2085
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
2086
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
2087
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 sensor 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. 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 .
2088
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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.
19.09.2014
2089
Others
For more general information about settings, please see Object Set t ings
2090
141
section.
19.09.2014
Logins
Logouts
Full Scans
Page Splits
Database Pages
Stolen Pages
Connection Memory
(KB)
19.09.2014
2091
Lock Requests
Deadlocks
Average amount of wait time (in milliseconds) for each lock request
that resulted in a wait.
Batch Requests
SQL Compilations
SQL Re-Compilations
Note: This sensor can only be added to a device (computer) running a Microsoft SQL database.
For this sensor type credentials for Windows systems must be defined for the device you want
to use the sensor on.
Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high
impact on the system performance! Try to stay below 200 WMI sensors per probe 77 . Above
this number, please consider using multiple Remot e Probes 2589 for load balancing.
For a general introduction to the technology behind WMI, please see Monit oring via WMI
section.
2092
2495
19.09.2014
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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: Display name and service name are provided as returned by
the SQL server.
Enter the version of the SQL server. Usually, you can keep the
default value.
19.09.2014
2093
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.
Tags
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).
2094
19.09.2014
Name
Shows the name of the server instance that this sensor monitors.
Once a sensor is created, you cannot change this value. It is
shown for reference purposes only. If you need to change this,
please add the sensor anew.
Select whether PRTG selects the name of the WMI class used for
monitoring automatically. Choose between:
Aut omat ic: Choose WMI class automatically. We recommend this
setting.
Manual: Manually enter a WMI class name. Use this if your server
instance returns an error code in automatic mode.
WMI Class
This field is only shown if you enable manual WMI class selection
above. This setting is intended for experienced users only. Enter
the WMI class name that the sensor uses for monitoring your
server instance.
Sensor Result
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.
19.09.2014
2095
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
2096
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
2097
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
2098
19.09.2014
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 sensor 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. 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 .
19.09.2014
2099
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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.
2100
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
2101
Logins
Logouts
Full Scans
Page Splits
Database Pages
Stolen Pages
Connection Memory
(KB)
2102
26.09.2014
Lock Requests
Deadlocks
Average amount of wait time (in milliseconds) for each lock request
that resulted in a wait.
Batch Requests
SQL Compilations
SQL Re-Compilations
Note: This sensor can only be added to a device (computer) running a Microsoft SQL database.
For this sensor type credentials for Windows systems must be defined for the device you want
to use the sensor on.
Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high
impact on the system performance! Try to stay below 200 WMI sensors per probe 77 . Above
this number, please consider using multiple Remot e Probes 2589 for load balancing.
For a general introduction to the technology behind WMI, please see Monit oring via WMI
section.
26.09.2014
2495
2103
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.
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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: Display name and service name are provided as returned by
the SQL server.
Enter the version of the SQL server. Usually, you can keep the
default value.
2104
26.09.2014
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.
Tags
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).
26.09.2014
2105
Name
Shows the name of the server instance that this sensor monitors.
Once a sensor is created, you cannot change this value. It is
shown for reference purposes only. If you need to change this,
please add the sensor anew.
Select whether PRTG selects the name of the WMI class used for
monitoring automatically. Choose between:
Aut omat ic: Choose WMI class automatically. We recommend this
setting.
Manual: Manually enter a WMI class name. Use this if your server
instance returns an error code in automatic mode.
WMI Class
This field is only shown if you enable manual WMI class selection
above. This setting is intended for experienced users only. Enter
the WMI class name that the sensor uses for monitoring your
server instance.
Sensor Result
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.
2106
26.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
26.09.2014
2107
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
2108
26.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
26.09.2014
2109
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 sensor 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. 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 .
2110
26.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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.
26.09.2014
2111
Others
For more general information about settings, please see Object Set t ings
2112
141
section.
26.09.2014
2495
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.
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.
Tags
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).
19.09.2014
2113
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
than this value the request is aborted and an error message is
triggered. Please enter an integer value. The maximum is 300.
Enter the packet size in bytes for the Ping. You can choose any
value between 1 and 10000. Please enter an integer value. We
recommend using the default value.
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
2114
19.09.2014
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.
19.09.2014
2115
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
2116
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
2117
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 sensor 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. 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 .
2118
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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.
19.09.2014
2119
Others
For more general information about settings, please see Object Set t ings
2120
141
section.
19.09.2014
St at us Code
Unknown
Down
Down
Warning
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)!
This sensor type uses lookups to determine the status values of some sensor channels. For
details, please see section Define Lookups 2579 .
For this sensor type credentials for Windows systems must be defined for the device you want
to use the sensor on.
Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high
impact on the system performance! Try to stay below 200 WMI sensors per probe 77 . Above
this number, please consider using multiple Remot e Probes 2589 for load balancing.
For a general introduction to the technology behind WMI, please see Monit oring via WMI
section.
2495
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.
19.09.2014
2121
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
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
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.
Tags
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).
2122
19.09.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
2123
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
2124
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
2125
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 sensor 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. 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 .
2126
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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.
19.09.2014
2127
Others
For more general information about settings, please see Object Set t ings
2128
141
section.
19.09.2014
2495
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.
To monitor Windows services, PRTG creates one sensor for each service you select in the Add
Sensor dialog.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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. 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
On the sensor's details page, click on the Set t ings tab to change settings.
18.11.2014
2129
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.
Tags
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).
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:
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.
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
Description
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
Chart Type
18.11.2014
2131
SENSOR DISPLAY
Stack Unit
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.
2132
18.11.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
18.11.2014
2133
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
2134
18.11.2014
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 sensor 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. 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
2135
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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.
2136
18.11.2014
Others
For more general information about settings, please see Object Set t ings
18.11.2014
141
section.
2137
2495
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.
If you select more than one share, PRTG will create one sensor for each share you select. 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:
Select the shares 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: 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
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.
2138
19.09.2014
Tags
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).
TypeID
Degraded
19.09.2014
2139
Pred Fail
Starting
Stopping
Service
Stressed
Nonrecover
NoContact
LostComm
SENSOR DISPLAY
Primary Channel
Chart Type
2140
19.09.2014
SENSOR DISPLAY
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).
Stack Unit
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.
19.09.2014
2141
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
2142
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
2143
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 sensor 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. 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 .
2144
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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.
19.09.2014
2145
Others
For more general information about settings, please see Object Set t ings
2146
141
section.
19.09.2014
2495
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.
If you select more than one SharePoint process, 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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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.
19.09.2014
2147
Tags
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).
SENSOR DISPLAY
Primary Channel
Chart Type
2148
19.09.2014
SENSOR DISPLAY
Stack Unit
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.
19.09.2014
2149
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
2150
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
2151
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 sensor 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. 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 .
2152
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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
2153
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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
For more general information about settings, please see Object Set t ings
2154
141
section.
19.09.2014
2495
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.
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.
19.09.2014
2155
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).
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
2156
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
2157
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
2158
19.09.2014
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 sensor 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. 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 .
19.09.2014
2159
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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.
2160
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
2161
2495
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.
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.
2162
19.09.2014
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).
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
19.09.2014
2163
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
2164
19.09.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
19.09.2014
2165
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 sensor 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. 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 .
2166
19.09.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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.
19.09.2014
2167
Others
For more general information about settings, please see Object Set t ings
2168
141
section.
19.09.2014
2495
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.
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.
Tags
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).
19.09.2014
2169
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
2170
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
2171
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
2172
19.09.2014
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 sensor 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. 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 .
19.09.2014
2173
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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.
2174
19.09.2014
Others
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
2175
2495
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.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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
On the sensor's details page, click on the Set t ings tab to change settings.
2176
19.09.2014
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.
Tags
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).
These fields show the parameters that are used to query data for
this sensor from the target 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.
WMI Class
Counter
Time Stamp
Time Frequency
Counter Type
Sensor Result
Define what will be done with the result of the sensor. Choose
between:
Discard sensor result : Do not store the results.
19.09.2014
2177
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
2178
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
2179
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
2180
19.09.2014
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 sensor 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. 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 .
19.09.2014
2181
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
2182
19.09.2014
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
2183
2495
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.
For devices with multiple volumes, PRTG creates one sensor for each volume you select. 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:
Select the volume(s) 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.
2184
19.09.2014
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.
Tags
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).
Drive Type
Shows the type of the disk drive that this sensor monitors. Once a
sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew.
ID Selection
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
Stack Unit
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.
2186
19.09.2014
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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
2187
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
2188
19.09.2014
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 sensor 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. 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 .
19.09.2014
2189
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
2190
19.09.2014
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
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
For more general information about settings, please see Object Set t ings
19.09.2014
141
section.
2191
2495
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 fragmentation on volumes, PRTG will create one sensor for each volume
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:
2192
18.11.2014
Select one or more volumes 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.
Tags
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).
18.11.2014
2193
Drive Type
Shows the type of the disk drive that this sensor monitors. Once a
sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew.
ID Selection
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
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.
2194
18.11.2014
SENSOR DISPLAY
Primary Channel
Chart Type
Stack Unit
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.
18.11.2014
2195
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
2196
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
2197
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 sensor 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. 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 .
2198
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
2199
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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
For more general information about settings, please see Object Set t ings
2200
141
section.
18.11.2014
2495
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.
18.11.2014
2201
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.
Tags
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).
SENSOR SETTINGS
If Value Changes
Define what this sensor will do when the sensor value changes.
You can choose between:
Ignore changes (default ): The sensor takes no action on
change.
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever the sensor value changes.
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.
2202
18.11.2014
DEBU G OPTIONS
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received from the sensor to the
"Logs (Sensor)" directory (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
Chart Type
Stack Unit
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.
18.11.2014
2203
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
2204
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
2205
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 sensor 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. 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 .
2206
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
More
My WMI sensors don't work. What can I do?
http://kb.paessler.com/en/topic/1043
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
18.11.2014
2207
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
For more general information about settings, please see Object Set t ings
2208
141
section.
18.11.2014
18.11.2014
2209
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.
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.
Tags
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).
SENSOR SETTINGS
WSUS Server Port
Define the port where the WSUS server service is running on.
Default value is 8530. Please enter an integer value.
Use SSL
2210
18.11.2014
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
Chart Type
Stack Unit
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.
18.11.2014
2211
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.
Set sensor t o "warning" for 3 int ervals, t hen set t o "down":
The sensor will only show an error status after four failed
requests in a row.
Set sensor t o "warning" for 4 int ervals, t hen set t o "down":
The sensor will only show an error status after five failed
requests in a row.
Set sensor t o "warning" for 5 int ervals, t hen set t o "down":
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.
2212
18.11.2014
Maintenance Window
Maintenance Begins At
Maintenance End At
Dependency Type
18.11.2014
2213
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 sensor 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. 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 .
2214
18.11.2014
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
18.11.2014
2215
More
Knowledge Base: Which .NET version does PRTG require?
http://kb.paessler.com/en/topic/60543
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
For more general information about settings, please see Object Set t ings
2216
141
section.
18.11.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 9 Additional Sensor Types (Custom Sensors)
6.9
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
494
1724
2571
1977
Additionally, some types of SQL sensors execute script files with SQL queries:
Microsoft SQL v2 Sensor
My SQL v2 Sensor
804
833
894
1001
19.09.2014
2217
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 9 Additional Sensor Types (Custom Sensors)
483
and
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 9 Additional Sensor Types (Custom Sensors)
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
More
For the other sensor types that work out-of-the-box, please see
List of Available Sensor Ty pes
305
Knowledge Base: How can I test if parameters are correctly transmitted to my script when
using an EXE/Script sensor?
http://kb.paessler.com/en/topic/11283
304
2217
2220
19.09.2014
305
2227
2219
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 10 Sensor Channels Settings
6.10
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 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
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 10 Sensor Channels Settings
19.09.2014
2221
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 10 Sensor Channels Settings
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.
Please enter a string.
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
Display
Line Color
Color (#rrggbb)
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
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 10 Sensor Channels Settings
Line Width
Value Mode
Decimal Places
2226
Spike Filter
19.09.2014
2223
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 10 Sensor Channels Settings
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
integer value or leave the field empty.
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
integer value or leave the field empty.
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.
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
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 10 Sensor Channels Settings
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.
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
leave the field empty.
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
leave the field empty.
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.
19.09.2014
2225
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 10 Sensor Channels Settings
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?
http://kb.paessler.com/en/topic/60238
304
2217
2220
2226
305
2227
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 11 Sensor Notifications Settings
6.11
The status or the data of a sensor can trigger notifications. Using this mechanism, you can
configure external alerting tailored to you needs.
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
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 11 Sensor Notifications Settings
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.
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
2230
2232
2228
2234
2235
19.11.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 11 Sensor Notifications Settings
You can create all notification triggers by forming sentences in "natural language". There are
different options available for every type.
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).
...perform [...]
19.11.2014
2229
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 11 Sensor Notifications Settings
STATE TR IGGER
...perform [...]
Save
Cancel
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
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 11 Sensor Notifications Settings
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
enter an integer value.
[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
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 11 Sensor Notifications Settings
SPEED TR IGGER
..for at least [...]
seconds
...perform [...]
Save
Cancel
Note: No escalation notification and no repeat are available for this trigger type.
VOLU ME TR IGGER
When [...] channel
2232
From the drop down menu, select the channel whose data PRTG
considers for this 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.
19.11.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 11 Sensor Notifications Settings
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
enter an integer value.
[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 [...]
Save
Cancel
Note: No escalation notification, no repeat, and no notification when condition clears are
available for this trigger type.
19.11.2014
2233
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 11 Sensor Notifications Settings
From the drop down menu, select the channel whose data PRTG
considers for this 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:
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.
...perform [...]
2234
19.11.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 11 Sensor Notifications Settings
Save
Cancel
Note: No escalation notification and no repeat are available for this trigger type.
CHANGE TR IGGER
When sensor changes
perform [...]
Note: There are no other options available for this trigger type.
304
2217
2220
19.11.2014
305
2227
2235
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 11 Sensor Notifications Settings
2236
141
19.11.2014
Part 7
Ajax Web InterfaceAdvanced Procedures
19.09.2014
2237
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 more advanced procedures in the Ajax Graphical User
Interface (GUI).
2240
Arrange Object s
Clone Object
Mult i-Edit
2245
2246
2248
Report s
Maps
Set up
2238
2256
2258
2253
2263
2275
2291
2311
2327
19.09.2014
100
192
Related Topics
Ent erprise Console
2430
19.09.2014
2482
2239
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.
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
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
Type
Toplist is based on
Period (Minutes)
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.
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.
Please enter an integer value.
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!
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
2244
2500
19.09.2014
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.
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.
19.09.2014
2245
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
2246
19.09.2014
Enter a name for the cloned object. By default, the old name is
filled in, proceeded by Clone of.
New IP Address/DNS
Name
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!
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
Creat e Device Templat e
Manage Device Tree
19.09.2014
2253
226
2247
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
2248
19.09.2014
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.
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.
19.09.2014
2249
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.
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
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
Working wit h Table List s
19.09.2014
155
2251
2252
226
19.09.2014
7.5
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
19.09.2014
2253
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
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.
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!
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.
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)
Related Topics
Clone Object
2246
19.09.2014
226
2255
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
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
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.
19.09.2014
2257
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
100
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:
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
Flag
Flag Color
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
Orange
Unusual
Green
Up
Blue
Paused
Black (Grey)
Unknown
Note: For detailed information about sensor states, please see Sensor St at es
19.09.2014
121
section.
2261
More
Knowledge Base: Which provider should I use for PRTG's "Geo Maps" feature?
http://kb.paessler.com/en/topic/34603
Knowledge Base: Which domains and ports does the GeoMaps feature use?
http://kb.paessler.com/en/topic/35823
Knowledge Base: Why does my street not appear on the Geo Map shown in PRTG?
http://kb.paessler.com/en/topic/35653
Knowledge Base: How do I get a Google Maps API key for use in PRTG?
http://kb.paessler.com/en/topic/32363
Knowledge Base: Which limitations apply when using the Google Maps API in PRTG?
http://kb.paessler.com/en/topic/7913
Knowledge Base: How can I change the way markers look like in PRTG's geo maps?
http://kb.paessler.com/en/topic/43153
Knowledge Base: How can I track geo data of my Mobile Probe device?
http://kb.paessler.com/en/topic/59647
2262
19.09.2014
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
2340
2341
2342
2343
2344
2345
2345
2346
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
Notifications Setup
Overall, you have to go through four steps to use notifications with PRTG. Please go through
all of them for a first setup:
1. Check and set up the Not ificat ion Delivery settings. This tells PRTG how to send
messages.
For detailed information, see Sy st em Administ rat ionNot ificat ion Delivery 2372 .
2. Check and set up Notification Contacts 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 .
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, 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
Video Tutorial: There is a video available on the Paessler video tutorials page.
http://www.paessler.com/support/video_tutorials/notification-and-trigger
Knowledge Base: What placeholders can I use with PRTG?
http://kb.paessler.com/en/topic/373
Knowledge Base: Notifications based on priorities
http://kb.paessler.com/en/topic/31243
18.11.2014
2265
7.8.1
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.
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
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
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.
2266
2349
18.11.2014
2273
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
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
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.
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
2270
18.11.2014
18.11.2014
2271
175
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
2274
18.11.2014
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
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
Select Library
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
2278
2282
19.09.2014
2284
2290
2277
7.9.1
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.
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.
In this section:
St ep 1: Add Library
2278
2279
2279
2280
2284
section.
2278
19.09.2014
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.
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".
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
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
7.9.2
M anagement
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.
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.
2282
19.09.2014
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.
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
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
7.9.3
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.
Tags
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
18.11.2014
Filter By Status
18.11.2014
2285
Select Tags
Filter By Priority
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
2286
18.11.2014
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.
Tags
18.11.2014
2287
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 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.
Read: Users in this group can see the object and review its
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.
You can create new user groups in the Sy st em Administ rat ion
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 .
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.
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
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
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.
2288
18.11.2014
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.
Delete
You can delete the entire library any time by clicking on the trash symbol on the right.
18.11.2014
2289
7.9.4
Context M enus
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.
2290
19.09.2014
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
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.
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.
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
2295
2298
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
Up to 40 days
Any
40 to 500 days
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
Review Monit oring Dat a
Hist oric Dat a Report s
2294
124
133
18.11.2014
18.11.2014
2295
90
2602
by default.
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!
2296
18.11.2014
18.11.2014
2297
Report Tabs
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.
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
Date Range
Start Date
2298
19.09.2014
R U N R EPOR T "[Name]"
End Date
Quick Range
PR OCESSING OPTIONS
File Format and
Delivery
Compression
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?
http://kb.paessler.com/en/topic/11863
Knowledge Base: Why is there missing data in historical data reports?
http://kb.paessler.com/en/topic/61382
2300
19.09.2014
Report Tabs
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.
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.
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
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
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
SCHEDU LE
Report Schedule
18.11.2014
2303
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
Specify Day
Specify Date
Scheduled Processing
2304
18.11.2014
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
Compression
PER IOD
Reported Period
Define the type of period you want to create a report for. Choose
between:
Day
18.11.2014
2305
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
Week Period
Month Period
Year Period
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
Define if percentiles
between:
2615
Percentile Average
(seconds)
Percentile Mode
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
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 Save button to store your settings. If you change tabs or use the main menu, all
changes to the settings will be lost!
2308
18.11.2014
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
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.
More
Knowledge Base: Can I change the number of PDFs created by a report?
http://kb.paessler.com/en/topic/11863
Knowledge Base: How do I modify PRTG's report templates?
http://kb.paessler.com/en/topic/263
Knowledge Base: How can I show full channel names below report graphs?
http://kb.paessler.com/en/topic/58913
Calculat ing Percent iles
2310
2615
18.11.2014
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.
In this section:
Int roduct ion
St art Maps
2311
2312
Maps Overview
Maps Rot at ion
2312
2313
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
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
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.
2314
2317
19.09.2014
2323
2313
2314
2315
2315
2314
2323
section (Settings).
19.09.2014
2317
section.
19.09.2014
2315
While showing a map, the single map items will be refreshed in the refresh interval defined for
this map.
2316
19.09.2014
2317
2317
2318
2319
2320
2320
2321
2321
2321
2321
18.11.2014
2317
Map Designer
2318
18.11.2014
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
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).
2320
18.11.2014
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?
http://kb.paessler.com/en/topic/19483
Knowledge Base: How can I add or edit map objects used for PRTG's maps?
http://kb.paessler.com/en/topic/1703
18.11.2014
2321
Knowledge Base: Which audible notifications are available in PRTG? Can I change the default
sound?
http://kb.paessler.com/en/topic/26303
Knowledge Base: Where can I find custom map objects and other map customizations?
http://kb.paessler.com/en/topic/61263
2322
18.11.2014
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.
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
MAP LAYOU T
Map Width
Map Height
Automatic Scaling
Background Picture
Background Image
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
18.11.2014
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
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 Save button to store your settings. If you change tabs or use the main menu, all
changes to the settings will be lost!
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
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.
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 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 .
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.
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
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.
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.
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?
http://kb.paessler.com/en/topic/10283
Dat a Report ing
2326
94
18.11.2014
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.
PRTG Status
PRTG St at usSy st em St at us
PRTG St at usClust er St at us
2401
2416
2418
2411
Account Settings
Account Set t ingsMy Account
2329
2334
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
2379
2385
2390
2372
2396
2394
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
My Ac c ount Settings
My Account Settings
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.
19.09.2014
2329
U SER ACCOU NT
Login Name
Display Name
Enter a name for the user for display purposes. This will not be
used for login.
Email Address
Timezone
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
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.
2330
19.09.2014
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.
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
19.09.2014
2331
ACCOU NT CONTR OL
Account Type
Allow Acknowledge
Alarms
Primary Group
Status
2332
19.09.2014
ACCOU NT CONTR OL
Note: This setting cannot be changed for the default administrator
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
for your information only and cannot be changed here.
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
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.
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.
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!
More
Knowledge Base: Which audible notifications are available in PRTG? Can I change the default
sound?
http://kb.paessler.com/en/topic/26303
19.09.2014
2333
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 .
2334
18.11.2014
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 .
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.
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.
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.
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.
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.
18.11.2014
2335
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
automatically inherited 90 .
Status
Schedule
Postpone
2336
18.11.2014
Gather Notifications
For (Minutes)
18.11.2014
2337
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.
2339
Push Notification
2340
SMS/Pager Message
2341
2343
2344
2345
2345
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
18.11.2014
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
Format
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: 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 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
Message
18.11.2014
2341
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
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
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
Syslog Port
Facility
Message
18.11.2014
2343
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
SNMP Port
Community String
Enter a code that can help you identify the purpose of the trap.
Default value is 0. Please enter an integer value.
Message ID
This ID helps you identify the origin of the trap. For example, enter
1.3.6.1.4.1.32446.1.1.1
Message
Agent IP
Define the IP address of the agent. Leave this field empty to use
the IP address of your PRTG web server.
2344
18.11.2014
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
Note: Regardless of the Not ificat ion Summarizat ion method chosen above, PRTG sends
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
Username
Password
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.
Location
ARN
Subject
Message
2346
18.11.2014
ASSIGN TICKET
Note: Regardless of the Not ificat ion Summarizat ion method chosen above, PRTG sends
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
Select the user resp. user group to which PRTG assigns the
notification ticket.
Subject
Content
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!
Others
For information about the comments and history tabs, please see Object Set t ings
141
section.
More
Applicat ion Programming Int erface (API) Definit ion
2571
18.11.2014
2347
http://kb.paessler.com/en/topic/373
Knowledge Base: Documentation of SNMP Traps Sent by PRTG
http://kb.paessler.com/en/topic/1133
Knowledge Base: How can PRTG send instant messages to Jabber, ICQ, MSN, Yahoo, etc., using
external software?
http://kb.paessler.com/en/topic/14803
Knowledge Base: Which audible notifications are available in PRTG? Can I change the default
sound?
http://kb.paessler.com/en/topic/26303
Knowledge Base: How can I send push notifications with PRTG?
http://kb.paessler.com/en/topic/60892
2348
18.11.2014
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 .
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
18.11.2014
2263
section.
2349
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?
http://kb.paessler.com/en/topic/60892
SetupTopics
Account Set t ingsMy Account
2329
2334
2349
2353
2357
2367
2379
2385
2390
2394
2401
2416
2418
2421
2423
18.11.2014
2396
2411
PRTG St at usClust er St at us
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
2352
2536
2560
18.11.2014
Sc hedules Settings
Schedules Settings
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.
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
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.
Click on the Add new schedule button or click on the name of an existing notification to edit.
BASIC SETTINGS
Schedule Name
Edit Mode
2354
19.09.2014
BASIC SETTINGS
Time Table
Period List
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.
19.09.2014
2355
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!
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
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
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
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
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
19.09.2014
2359
2360
19.09.2014
19.09.2014
2361
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)
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.
240 Values: This corresponds to a live graph covering a time
span of four hours if a 1 minute scanning interval is set.
480 Values: This corresponds to a live graph covering a time
span of eight hours if a 1 minute scanning interval is set.
960 Values: This corresponds to a live graph covering a time
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
GR APH SETTINGS: SELECT FOR HOW MANY DAYS HISTOR IC DATA R EMAINS
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
By default, this is the 30 day s graph in the web interface. You can
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.
20 day s wit h 1 hour averages: Results in 480 values.
30 day s wit h 1 hour averages: Results in 720 values.
30 day s wit h 6 hour averages: Results in 120 values. Uses
least RAM memory. We recommend this setting for installations
with 10,000 sensors or more.
40 day s wit h 1 hour averages: Results in 960 values.
40 day s wit h 6 hour averages: Results in 160 values.
60 day s wit h 1 hour averages: Results in 1440 values. Uses
most RAM memory.
60 day s wit h 6 hour averages: Results in 240 values.
Graph 3
By default, this is the 365 day s graph in the web interface. You can
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
least RAM memory. We recommend this setting for installations
with 10,000 sensors or more.
200 day s wit h 1 day averages: Results in 200 values.
2364
19.09.2014
GR APH SETTINGS: SELECT FOR HOW MANY DAYS HISTOR IC DATA R EMAINS
ACCESSIBLE
365 day s wit h 1 day averages: Results in 365 values.
400 day s wit h 1 day averages: Results in 400 values.
750 day s wit h 1 day averages: Results in 750 values. Uses
most RAM memory.
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!
More
Knowledge Base: What placeholders can I use with PRTG?
http://kb.paessler.com/en/topic/373
Knowledge Base: How can I speed up PRTGespecially for large installations?
http://kb.paessler.com/en/topic/2733
Knowledge Base: Which provider should I use for PRTG's "Geo Maps" feature?
http://kb.paessler.com/en/topic/34603
Knowledge Base: Which domains and ports does the GeoMaps feature use?
http://kb.paessler.com/en/topic/35823
Knowledge Base: How do I get a Google Maps API key for use in PRTG?
http://kb.paessler.com/en/topic/32363
Knowledge Base: Which limitations apply when using the Google Maps API in PRTG?
http://kb.paessler.com/en/topic/7913
Knowledge Base: How and where does PRTG store its data?
http://kb.paessler.com/en/topic/463
Paessler Blog: Version 12 of PRTG introduces "Continuous Rollout"
http://www.paessler.com/blog/2012/04/25/
Knowledge Base: Enterprise Console connection failure error in content: What can I do?
19.09.2014
2365
http://kb.paessler.com/en/topic/60923
Knowledge Base: How can I integrate Google Analytics in PRTG?
http://kb.paessler.com/en/topic/61406
2366
19.09.2014
Monitoring Settings
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.
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
Logging
2368
20.11.2014
20.11.2014
2369
AU TO-DISCOVER Y SETTINGS
Run Discovery at
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!
2370
20.11.2014
More
Knowledge Base: How can I speed up PRTGespecially for large installations?
http://kb.paessler.com/en/topic/2733
Knowledge Base: How and where does PRTG store its data?
http://kb.paessler.com/en/topic/463
20.11.2014
2371
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 .
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.
2372
19.09.2014
EMAIL OPTIONS
Email Templates
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).
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).
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.
This field is only visible if SMTP relay server is enabled above. Enter
the IP address or DNS name of the SMTP relay server.
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
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.
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.
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
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
Maximum Length of
Text
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).
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!
More
Knowledge Base: How can I send SMS text message notifications via a modem or a mobile
phone with PRTG?
http://kb.paessler.com/en/topic/393
Knowledge Base: Why do I get a connection timeout message when sending SMS via bulksms?
http://kb.paessler.com/en/topic/12253
Knowledge Base: Which URLs does PRTG use for its preconfigured SMS providers?
http://kb.paessler.com/en/topic/13123
Knowledge Base: How do I send SMS with PRTG using a Clickatell account?
http://kb.paessler.com/en/topic/34213
Knowledge Base: How can PRTG send instant messages to Jabber, ICQ, MSN, Yahoo, etc., using
external software?
http://kb.paessler.com/en/topic/14803
Knowledge Base: Can GMail / Google Apps be used for SMTP relay?
http://kb.paessler.com/en/topic/2823
Knowledge Base: How can I enable Notification Delivery Logging?
19.09.2014
2377
http://kb.paessler.com/en/topic/55363
2378
19.09.2014
Proxy Server
Port
26.09.2014
2379
Password
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
2380
26.09.2014
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
26.09.2014
2381
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.
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.
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
2382
26.09.2014
Access Password
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.
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.
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
Configuration AutoBackups
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.
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!
More
Define IP Ranges
2578
Knowledge Base: Where can I find PRTG Mini Probes which are ready to use?
http://kb.paessler.com/en/topic/61215
2384
26.09.2014
U SER ACCOU NT
Login Name
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
Timezone
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
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.
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
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.
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
19.09.2014
2387
ACCOU NT CONTR OL
Account Type
Allow Acknowledge
Alarms
Primary Group
Status
2388
19.09.2014
ACCOU NT CONTR OL
Note: This setting cannot be changed for the default administrator
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
for your information only and cannot be changed here.
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
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.
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.
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!
More
Knowledge Base: Which audible notifications are available in PRTG? Can I change the default
sound?
http://kb.paessler.com/en/topic/26303
19.09.2014
2389
2390
19.09.2014
U SER GR OU P SETTINGS
User Group Name
Administrative Rights
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.
19.09.2014
2391
U SER GR OU P SETTINGS
New User Type
Allowed Sensors
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.
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
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
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.
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.
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!
19.09.2014
2393
2416
to
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.
Cluster Settings
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.
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.
Node ID
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.
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.
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!
2394
19.09.2014
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
2396
19.09.2014
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.
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
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 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
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
instructions on the screen.
Note: If you want to schedule an automatic restart of Windows
services for both core server and probe service, you can do this in
the respective Probe Set t ings 259 .
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.
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
SetupTopics
Account Set t ingsMy Account
2329
2334
2349
2353
2357
2367
2379
2385
2390
2394
2401
2416
2418
2421
2423
19.09.2014
2396
2411
PRTG St at usClust er St at us
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:
PRTG Administ rat or on Core Server Sy st em
2537
2400
2536
2560
19.09.2014
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.
Auto-Update Status
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.
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
information for the system of the cluster node you're currently
logged in to.
18.11.2014
2401
Browser
Shows the name and user agent string of the browser you're
currently viewing this page with.
2329
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
Current Activation
Stamp
Software Maintenance
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 .
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
2403
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
BACKGR OU ND TASKS
Historic Data
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
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
244
configured.
Groups
262
in your configuration.
Devices
Sensors
User Groups
Users
Notifications
Schedules
Maps
Libraries
Reports
18.11.2014
2385
284
304
in your configuration.
in your configuration.
2390
in your configuration.
configured.
2291
2353
2334
configured.
configured.
2311
in your installation.
2275
in your installation.
in your installation.
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
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]"
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
the cluster node you're currently logged in to.
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
the cluster node you're currently logged in to.
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.
Incoming Probe
Connection Binding
Incoming Probe
Connection IPs
18.11.2014
2407
SYSTEM SETTINGS
Incoming Probe
Connection Port
DataPath
Shows the time that has passed since the PRTG web server was
started.
Page Views
Geo Maps
Shows the total number of geo maps shown on this core server.
HTTP Requests
2408
18.11.2014
Shows for how many (percent) of the HTTP requests above the
page delivery took longer than 500, 1,000, or 5,000 milliseconds.
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
Probe/Core Message
Count
Configuration
Requests Sent
Configuration
Requests Deleted
Configuration
Requests With
Response
18.11.2014
2409
More
Paessler Website: Detailed System Requirements for PRTG Network Monitor
http://www.paessler.com/prtg/detailed-requirements
Knowledge Base: How can I speed up PRTGespecially for large installations?
http://kb.paessler.com/en/topic/2733
2410
18.11.2014
Status
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.
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
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.
Installation Time
Release Channel
19.09.2014
2413
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!
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
More 2415 section below.
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?
http://kb.paessler.com/en/topic/32513
Knowledge Base: Which information does PRTG send back to Paessler?
http://kb.paessler.com/en/topic/28103
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
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
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
2418
2419
2419
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.
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.
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
Current Activation
Stamp
Software Maintenance
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.
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
2421
2421
2421
2421
2422
Desktop Notifications
2422
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
Desktop Notifications
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
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.
19.09.2014
2423
Clic k on 'Alway s Show Notific ations' to enbale Firefox Desktop Notific ations
2424
19.09.2014
18.11.2014
2425
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!
18.11.2014
2427
Part 8
Enterprise Console
19.09.2014
2429
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.
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
2430
2462
for
19.09.2014
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
Password
2431
for common issues with the Enterprise Console and their solutions.
More
Knowledge Base: Problems with the Enterprise Console: What can I do?
http://kb.paessler.com/en/topic/60091
Knowledge Base: Enterprise Console connection failure error in content: What can I do?
http://kb.paessler.com/en/topic/60923
The following sections introduce the features and concepts of the Enterprise Console:
19.09.2014
2431
Enterprise ConsoleTopics
First St art
2433
2434
2437
2462
2465
2471
2478
2479
Related Topics
Ajax Web Int erfaceBasic Procedures
100
2432
192
2238
2482
19.09.2014
8.1
First Start
This section helps you start the Enterprise Console for the first time.
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.
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
8.2
General Layout
The main layout of the Enterprise Console (EC in short form) program consists of different
elements which this section describes.
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
underneath.
2436
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
Server Selection
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.
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
8.3
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.
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
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.
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
2438
18.11.2014
2471
18.11.2014
2439
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 ).
2440
2441
18.11.2014
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 .
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.
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 .
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.
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
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
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
262
284
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
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
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.
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.
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.
2444
18.11.2014
8.3.2
Libraries
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.
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.
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
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
2446
2278
18.11.2014
8.3.3
Sensors
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.
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.
18.11.2014
2447
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.
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.
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
8.3.4
Alarms
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.
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
18.11.2014
2449
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:
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
8.3.5
M aps
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.
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
2478
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
2452
2314
18.11.2014
8.3.6
Reports
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.
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
18.11.2014
184
to
2453
2454
2295
18.11.2014
8.3.7
Logs
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.
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.
18.11.2014
2455
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 .
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.
2456
18.11.2014
8.3.8
Tickets
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.
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
18.11.2014
2457
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.
For details about working with PRTG's ticket system, please see section Ticket s
web interface.
2458
148
for PRTG's
18.11.2014
8.3.9
Setup
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.
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
2329
2334
2353
18.11.2014
2357
2459
Monit oring
2367
2379
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
2418
2421
2421
2421
Support :
Cont act Support
2460
2425
18.11.2014
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
18.11.2014
2461
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.
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.
2462
18.11.2014
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 .
2464
18.11.2014
8.5
Options
2471
You can choose from these options on the left hand side:
System
2465
SystemAlerting
Device Tools
2466
2467
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.
18.11.2014
2465
SystemAlerting
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.
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
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.
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
%value
%type
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.
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
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.
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
8.6
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
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
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.
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.
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 .
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 such a group. For detailed
instruction, please see section Aut o-Discovery 194 .
Add Device...
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 device to the selected
probe or group. For detailed instructions, please see Add a
Device 215 .
2472
18.11.2014
EDIT
Add Sensor...
Creat e Device
Templat e...
Acknowledge Alarm...
Delet e
Clone...
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
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.
Priorit y /Favorit e
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 .
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
Find Duplicat es
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 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 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 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.
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
2258
in the
Shortcut: Ctrl+G
Show News Feed
Next Viewpoint
Previous Viewpoint
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 Cont act Support 2425 dialog box to leave feedback or to
ask for support by sending a support bundle.
About ...
2430
36
See Also
Short cut s Overview
18.11.2014
2479
2477
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 .
2478
18.11.2014
8.8
Shortcuts Overview
2465
2465
18.11.2014
2479
See Also
Windows Menu St ruct ure
2480
2471
18.11.2014
Part 9
Other User Interfaces
19.09.2014
2481
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.
2483
2486
Related Topics
Ajax Web Int erfaceBasic Procedures
100
2482
192
2238
2430
19.09.2014
9.1
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.
Login Screen
After loading the web interface, the login screen is shown.
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.
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 .
19.09.2014
19.09.2014
2485
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
Maps on iPad
2486
18.11.2014
Note: Push notifications are currently not supported with this app.
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?
http://kb.paessler.com/en/topic/60042
Knowledge Base: How can I use push notifications with PRTG?
http://kb.paessler.com/en/topic/60892
2488
18.11.2014
Part 10
Sensor Technologies
19.09.2014
2489
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
2495
2498
2502
2505
2507
2512
2514
2515
2524
2490
2500
2526
19.09.2014
10.1
Monitoring via Simple Network Management Protocol (SNMP) is the most basic method of
gathering bandwidth and network usage data.
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.
18.11.2014
2491
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.
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?
http://kb.paessler.com/en/topic/653
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: My SNMP sensors don't work. What can I do?
http://kb.paessler.com/en/topic/46863
Knowledge Base: The interface numbers on my switch keep changing. What can I do?
http://kb.paessler.com/en/topic/62217
2494
18.11.2014
10.2
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.
19.09.2014
2495
More
Knowledge Base: General introduction to WMI and PRTG
http://kb.paessler.com/en/topic/1043
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!
http://www.paessler.com/blog/2010/09/22/
19.09.2014
2497
10.3
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.
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
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)?
http://kb.paessler.com/en/topic/6733
Knowledge Base: How can I use private keys for my SSH sensors with PRTG?
http://kb.paessler.com/en/topic/32883
Knowledge Base: How do I enable SSH on my Mac OS X system?
http://kb.paessler.com/en/topic/33113
19.09.2014
2499
10.4
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
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.
2500
19.09.2014
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.
907
916
More
Tool: Paessler Card Packet Counter: Shows short term statistics about the network data
packets passing a local network card.
http://www.paessler.com/tools/
Knowledge Base: How can I change the default groups and channels for xFlow and Packet
Sniffer sensors?
http://kb.paessler.com/en/topic/60203
19.09.2014
2501
10.5
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.
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.
2502
19.09.2014
846
865
875
741
856
751
1094
1103
770
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
probe only, not on a cluster probe.
More
Knowledge Base: Can I add custom channels to standard Packet Sniffer and NetFlow sensors?
http://kb.paessler.com/en/topic/2143
Knowledge Base: What filter rules can be used for custom Packet Sniffing or xFlow (NetFlow/
sFlow) sensors?
http://kb.paessler.com/en/topic/483
Knowledge Base: How do the channel definitions for custom Packet Sniffing or xFlow
(NetFlow/sFlow) sensors work?
http://kb.paessler.com/en/topic/473
19.09.2014
2503
Knowledge Base: Do you have any configuration tips for Cisco routers and PRTG?
http://kb.paessler.com/en/topic/563
Knowledge Base: Is it possible to monitor Cisco ASA Firewalls using Netflow 9 and PRTG?
http://kb.paessler.com/en/topic/633
Knowledge Base: How to monitor Cisco ASA Firewalls using NetFlow 9 and PRTG?
http://kb.paessler.com/en/topic/1423
Knowledge Base: How can I change the default groups and channels for xFlow and Packet
Sniffer sensors?
http://kb.paessler.com/en/topic/60203
Tools: NetFlow Generator and NetFlow Tester
http://www.paessler.com/tools/
2504
19.09.2014
10.6
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
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?
http://kb.paessler.com/en/topic/923
2506
19.09.2014
10.7
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).
19.09.2014
2507
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.
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).
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
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
Very good
10
Good
20
Adequate
30
Limiting case
45
55
More
Knowledge Base: Where can I find more information about Cisco IP SLAs, VoIP, and QoS?
http://kb.paessler.com/en/topic/11093
Knowledge Base: How does PRTG calculate the MOS score for QoS sensors?
http://kb.paessler.com/en/topic/59491
Knowledge Base: How can I monitor QoS roundtrips without using remote probes?
http://kb.paessler.com/en/topic/61176
19.09.2014
2511
10.8
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:
SMTP&POP3 Round Trip Sensor
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.
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
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).
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.
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
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
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.
2514
19.09.2014
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.
2516
19.09.2014
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.
19.09.2014
2517
1803
1818
1810
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
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.
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.
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.
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.
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?
http://kb.paessler.com/en/topic/49193
2522
19.09.2014
Sensor TechnologiesTopics
Monit oring via SNMP
2491
2495
2498
2502
2505
2507
2512
2514
2515
2524
19.09.2014
2500
2526
2523
833
2524
804
1001
894
18.11.2014
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.
2080
2091
2102
18.11.2014
2525
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
2528
2529
2530
2526
2527
2531
26.09.2014
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
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
2611
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
2530
26.09.2014
26.09.2014
2531
More
Knowledge Base: What placeholders can I use with PRTG?
http://kb.paessler.com/en/topic/373
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
2532
26.09.2014
Sensor TechnologiesTopics
Monit oring via SNMP
2491
2495
2498
2502
2505
2507
2512
2514
2515
2524
26.09.2014
2500
2526
2533
Part 11
PRTG Administrator Tool
19.09.2014
2535
11
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.
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
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
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
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
Web Server
Edit IPs, ports, access methods, and language for the Ajax
interfaces.
100
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.
2538
19.09.2014
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
Expert Configuration:
SSL Encryption
19.09.2014
2539
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
2540
19.09.2014
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
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.
19.09.2014
2541
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
Probe Connections
Port
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
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
CLU STER
Cluster Settings
19.09.2014
2543
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
CLU STER
Cluster Mode Actions
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
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
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.
We recommend using the default value.
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.
19.09.2014
2545
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
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.
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.
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.
After confirming your settings you will be asked to restart Windows services. Please do so in
order for your changes to take effect.
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.
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.
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.
Please make sure you use the same settings on all nodes in your cluster.
After confirming your settings you will be asked to restart Windows services. Please do so in
order for your changes to take effect.
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
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
After confirming your settings you will be asked to restart Windows services. Please do so in
order for your changes to take effect.
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
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
Login Name
Password
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
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
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.
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.
19.09.2014
2549
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
PR OBE SETTINGS
Name of Probe
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.
2550
19.09.2014
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
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
If you enter an access key for a remote probe, enter it in this field
again to assure correctness.
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.
19.09.2014
2551
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
Outgoing IPv6
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
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
Open the PRTG Network Monitor data directory on your hard disk
drive to access all log files which PRTG creates.
Send Logs to
Paessler...
The About section shows information about the version of installed PRTG programs and
copyright.
19.09.2014
2427
in
2553
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
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.
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.
2554
19.09.2014
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
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
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.
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
19.09.2014
2555
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
If you enter an access key for a remote probe, enter it in this field
again to assure correctness.
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.
2556
19.09.2014
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
Outgoing IPv6
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.
Open the PRTG Network Monitor data directory on your hard disk
drive to access all log files which PRTG creates.
Send Logs to
Paessler...
19.09.2014
2557
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
The About section shows information about the version of installed PRTG programs and
copyright.
2427
in
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.
Enter your valid email address. You can provide any of your
addresses; however, recommended and default is the email
address of your PRTG account.
2558
19.09.2014
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
Configuration
Click on the Send button to start data upload. Ensure that FTP and HTTP connections are
allowed on this machine.
19.09.2014
2559
Part 11: PRTG Administrator Tool | 2 PRTG Administrator on Remote Probe Systems
11.2
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:
Probe Settings for Core Connection
Probe Settings for Monitoring
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.
2560
19.09.2014
Part 11: PRTG Administrator Tool | 2 PRTG Administrator on Remote Probe Systems
PR OBE SETTINGS
Name of Probe
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.
19.09.2014
2561
Part 11: PRTG Administrator Tool | 2 PRTG Administrator on Remote Probe Systems
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
If you enter an access key for a remote probe, enter it in this field
again to assure correctness.
2562
Define the data folder to which PRTG will store configuration and
monitoring data. Click on the ... button to choose another folder
on your system.
19.09.2014
Part 11: PRTG Administrator Tool | 2 PRTG Administrator on Remote Probe Systems
Outgoing IPv6
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 .
19.09.2014
2563
Part 11: PRTG Administrator Tool | 2 PRTG Administrator on Remote Probe Systems
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.
Open the PRTG Network Monitor data directory on your hard disk
drive to access all log files which PRTG creates.
Send Logs to
Paessler...
The About section shows information about the version of installed PRTG programs and
copyright.
2564
2427
in
19.09.2014
Part 11: PRTG Administrator Tool | 2 PRTG Administrator on Remote Probe Systems
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.
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.
19.09.2014
2565
Part 11: PRTG Administrator Tool | 2 PRTG Administrator on Remote Probe Systems
Click on the Send button to start data upload. Ensure that FTP and HTTP connections are
allowed on this machine.
2566
19.09.2014
Part 12
Advanced Topics
19.09.2014
2567
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
2602
2611
2568
2576
2613
2615
19.09.2014
12.1
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.
100
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.
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
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.
2570
19.09.2014
12.2
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.
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?
http://kb.paessler.com/en/topic/60130
Knowledge Base: Where can I find PRTG Mini Probes which are ready to use?
http://kb.paessler.com/en/topic/61215
19.09.2014
2571
Part 12: Advanced Topics | 3 Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors
12.3
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]
2574
below)
2574
below)
2574
below)
Port
any number
SourceIP
Possible values: IP address or DNS name (see Valid Data Formats
SourcePort
any number
Dest inat ionIP
Possible values: IP address or DNS name (see Valid Data Formats
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)
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
Part 12: Advanced Topics | 3 Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors
TrafficClass
IPv6 Traffic Class (corresponds to TOS used with IPv4)
FlowLabel
IPv6 Flow Label
19.09.2014
2573
Part 12: Advanced Topics | 3 Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors
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)
Possible values: IP address or DNS name (see Valid Data Formats
2574
below)
VLAN
"VLAN" values represent a VLAN identifier (any number).
SourceVLAN
"VLAN" values represent a VLAN identifier (any number).
Dest inat ionVLAN
"VLAN" values represent a VLAN identifier (any number).
2574
19.09.2014
Part 12: Advanced Topics | 3 Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors
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
Channel Definit ions for xFlow, IPFIX , and Packet Sniffer Sensors
Monit oring Bandwidt h via Packet Sniffing
Monit oring Bandwidt h via Flows
2576
2500
2502
Knowledge Base: How can I change the default groups and channels for xFlow and Packet
Sniffer sensors?
http://kb.paessler.com/en/topic/60203
19.09.2014
2575
Part 12: Advanced Topics | 4 Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors
12.4
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])
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
Filt er Rules for xFlow, IPFIX , and Packet Sniffer Sensors
Monit oring Bandwidt h via Packet Sniffing
Monit oring Bandwidt h via Flows
2572
2500
2502
More
Knowledge Base: Can I add custom channels to standard Packet Sniffer and NetFlow sensors?
http://kb.paessler.com/en/topic/2143
19.09.2014
2577
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
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.
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"?>
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
Toner Okay
Up
Toner Low
Warning
Down
</Lookups>
</ValueLookup>
19.09.2014
2581
Element
Descript ion
<?xml>
content
<ValueLookup>
contentValueLookup
</ValueLookup>
<Lookups>
contentLookups
</Lookups>
<SingleInt >
status text
</SingleInt >
<Bit Field>
status text
</Bit Field>
<Range>
status text
</Range>
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.
2585
19.09.2014
2583
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".
2584
19.09.2014
Lookup Ty pe
Descript ion
Sy nt ax
SingleInt
value="int"
BitField
Range
from="int" to="int"
Uses an inter range from-t o
to define a lookup for several
status values.
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.
483
494
1243
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
More
Wikipedia: Masks (computing)
http://en.wikipedia.org/wiki/Bit_mask
2586
19.09.2014
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.
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).*
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
12.8
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.
2589
2592
2597
More
Video Tutorial: Core Server and Remote Probes
http://www.paessler.com/support/video_tutorials/distributed_monitoring
2588
19.09.2014
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.
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
Video Tutorial: There is a video available on the Paessler video tutorials page.
http://www.paessler.com/support/video_tutorials
19.09.2014
2591
2592
2592
2594
2594
2595
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.
When you are done, click Save to save your settings. The core server process must be
restarted so that the changes take effect.
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.
For detailed information about these settings, please see Sy st em Administ rat ionCore &
Probes 2379 section.
19.09.2014
2593
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
Please make sure that this user account has administration rights on the target computer.
168
2594
19.09.2014
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!
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 .
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
2597
2599
2599
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.
19.09.2014
2597
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.
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.
For detailed information about these settings, please see Sy st em Administ rat ionCore &
Probes 2379 section.
2598
19.09.2014
2536
will be started
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
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
12.9
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.
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.
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
jFlow V5
770
751
780
NetFlow V5
846
856
NetFlow V9
865
875
Packet Sniffer
sFlow
1094
907
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's the Clustering Feature in PRTG?
http://kb.paessler.com/en/topic/6403
Knowledge Base: What are the bandwidth requirements for running a PRTG Cluster?
http://kb.paessler.com/en/topic/8223
Knowledge Base: What is a Failover Master and how does it behave?
http://kb.paessler.com/en/topic/7663
Knowledge Base: I need help with my PRTG cluster configuration. Where do I find step-by-step
instructions?
http://kb.paessler.com/en/topic/41913
Knowledge Base: PRTG Cluster: How do I convert a (temporary) Failover Master node to be the
Primary Master node?
http://kb.paessler.com/en/topic/34853
2604
18.11.2014
51
2542
20.11.2014
2605
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.
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.
We recommend using the default value.
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.
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.
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.
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.
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.
20.11.2014
2607
After confirming your settings you will be asked to restart Windows services. Please do so in
order for your changes to take effect.
102
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.
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.
2608
20.11.2014
2416
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.
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?
http://kb.paessler.com/en/topic/41903
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
2602
2611
2610
2576
2613
2615
20.11.2014
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.
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
More
Knowledge Base: How and where does PRTG store its data?
http://kb.paessler.com/en/topic/463
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 ).
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?
http://kb.paessler.com/en/topic/273
Knowledge Base: How can I use a trusted SSL certificate with the PRTG web interface?
http://kb.paessler.com/en/topic/283
2614
18.11.2014
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?
http://kb.paessler.com/en/topic/9563
18.11.2014
2615
Part 13
Appendix
19.09.2014
2617
13
Appendix
2619
2623
2618
2626
2627
19.09.2014
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 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 .
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
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
2624
19.09.2014
19.09.2014
2625
13.3
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.
http://www.paessler.com/support/video_tutorials
2626
19.09.2014
13.4
Legal Notices
19.09.2014
2627
2628
30.12.1899