PRTG Network Monitor 9 User Manual

PRTG Network Monitor 9 User Manual
© 2011 Paessler AG
All rights reserved. No parts of this work may be reproduced in any form or by any means—graphic,
electronic, or mechanical, including photocopying, recording, taping, or information storage and
retrieval systems—without the written permission of the publisher.
Products that are referred to in this document may be either trademarks and/or registered trademarks
of the respective owners. The publisher and the author make no claim to these trademarks.
While every precaution has been taken in the preparation of this document, the publisher and the
author assume no responsibility for errors or omissions, or for damages resulting from the use of
information contained in this document or from the use of programs and source code that may
accompany it. In no event shall the publisher and the author be liable for any loss of profit or any
other commercial damage caused or alleged to have been caused directly or indirectly by this
document.
Printed: November 2011 in Nuremberg
Contents
Table of Contents
12
Part I Welcome to PRTG Network Monitor
1
2
3
4
5
About this Document
Key Features
New in Version 9
Available Licenses
System Requirements
Detailed System Requirements
13
14
15
16
18
20
28
Part II Quick Start Guide
1
2
ONE—Download, Installation, and First Login
TWO—Auto-Discover Your Network
30
33
38
Part III Installing the Software
1
2
3
4
5
6
7
8
9
Download PRTG
Update From Previous Versions to V9
Install a PRTG Core Server
Setup Wizard
Welcome Wizard
Install a PRTG Cluster
Enter a License Key
Activate the Product
Install a PRTG Remote Probe
Install the Enterprise Console
Uninstall PRTG Products
39
41
44
45
48
56
59
62
64
69
74
78
Part IV Understanding Basic Concepts
1
2
3
4
5
6
7
8
9
10
11
Architecture
Clustering
Object Hierarchy
Inheritance of Settings
Tags
Dependencies
Scheduling
Notifying
Data Reporting
User Access Rights
IPv6
79
82
83
87
89
90
91
92
93
94
95
98
Part V Ajax Web Interface—Basic Procedures
1
2
Login
SSL Certificate Warning
100
103
3
Contents
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
General Layout
Sensor States
Review Monitoring Data
Object Settings
Alarms
Logs
Historic Data Reports
ToDos
Working with Table Lists
Object Selector
Priority and Favorites
Pause
Context Menus
Hover Popup
Main Menu Structure
106
112
115
118
120
122
124
128
130
132
134
135
136
144
145
156
Part VI Ajax Web Interface—Device and Sensor Setup
1
2
3
4
5
6
7
8
4
Auto-Discovery
Create Objects Manually
Add a Group
Add a Device
Add a Sensor
Manage Device Tree
Root Group Settings
Probe Settings
Group Settings
Device Settings
Sensor Settings
List of Available Sensor Types
Active Directory Replication Errors Sensor
ADO SQL Sensor
Amazon CloudWatch Sensor
Cisco IP SLA Sensor
Cluster Probe Health Sensor
Core/Probe Health Sensor
DHCP Sensor
DNS Sensor
Event Log (Windows API) Sensor
EXE/Script Sensor
EXE/Script Advanced Sensor
File Sensor
File Content Sensor
Folder Sensor
FTP Sensor
FTP Server File Count Sensor
HDD Health Sensor
HTTP Sensor
HTTP Advanced Sensor
158
169
170
175
182
183
185
196
207
222
236
237
247
253
260
266
271
275
279
283
288
294
301
308
314
320
326
331
337
342
348
Contents
HTTP Content Sensor
HTTP Full Web Page Sensor
HTTP SSL Certificate Expiry Sensor
HTTP Transaction Sensor
HTTP XML/REST Value Sensor
Hyper-V Host Server Sensor
Hyper-V Virtual Machine Sensor
Hyper-V Virtual Network Adapter Sensor
Hyper-V Virtual Storage Device Sensor
IMAP Sensor
INI File Content Check Sensor
IP on DNS Blacklist Sensor
jFlow V5 Sensor
jFlow V5 (Custom) Sensor
LDAP Sensor
Microsoft SQL Sensor
MySQL Sensor
NetFlow V5 Sensor
NetFlow V5 (Custom) Sensor
NetFlow V9 Sensor
NetFlow V9 (Custom) Sensor
Oracle SQL Sensor
Packet Sniffer Sensor
Packet Sniffer (Custom) Sensor
Ping Sensor
Ping Jitter Sensor
Pingdom Sensor
POP3 Sensor
POP3 Email Count Sensor
Port Sensor
QoS (Quality of Service) One Way Sensor
QoS (Quality of Service) Round Trip Sensor
RADIUS Sensor
RDP (Remote Desktop) Sensor
Sensor Factory Sensor
sFlow Sensor
sFlow (Custom) Sensor
Share Disk Free Sensor
SMTP Sensor
SMTP&IMAP Round Trip Sensor
SMTP&POP3 Round Trip Sensor
SNMP APC Hardware Sensor
SNMP Custom Sensor
SNMP Custom String Sensor
SNMP Dell Hardware Sensor
SNMP HP LaserJet Hardware Sensor
SNMP Library Sensor
SNMP Linux Disk Free Sensor
SNMP Linux Load Average Sensor
SNMP Linux Meminfo Sensor
SNMP System Uptime Sensor
357
364
369
374
382
389
393
399
405
409
414
420
425
432
439
443
450
456
463
470
477
484
490
497
503
509
514
519
525
531
537
542
547
552
556
569
576
582
588
594
601
608
613
619
625
630
635
643
648
653
658
5
Contents
9
6
SNMP Traffic Sensor
SNMP Trap Receiver Sensor
SNTP Sensor
SSH Disk Free Sensor
SSH INodes Free Sensor
SSH Load Average Sensor
SSH Meminfo Sensor
SSH VMWare ESX(i) Disk Sensor
Syslog Receiver Sensor
TFTP Sensor
Traceroute Hop Count Sensor
Virtuozzo Container Disk Sensor
Virtuozzo Container Network Sensor
VMware Host Hardware (WBEM)
VMware Host Server (SOAP) Sensor
VMware Virtual Machine (SOAP) Sensor
WBEM Custom Sensor
Windows Last Update Sensor
Windows Logged In Users Sensor
Windows MSMQ Queue Length Sensor
Windows Print Queue Sensor
Windows Registry Sensor
Windows Scheduled Task Sensor
WMI CPU Load Sensor
WMI Custom Sensor
WMI Event Log Sensor
WMI Exchange Server Sensor
WMI File Sensor
WMI Free Disk Space (Multi Drive) Sensor
WMI IIS 6.0 SMTP Received Sensor
WMI IIS 6.0 SMTP Sent Sensor
WMI Logical Disk Sensor
WMI Memory Sensor
WMI Microsoft SQL Server 2005 Sensor
WMI Microsoft SQL Server 2008 Sensor
WMI Network Card Sensor
WMI Pagefile Sensor
WMI Physical Disk Sensor
WMI Process Sensor
WMI Security Center Sensor
WMI Service Sensor
WMI Share Sensor
WMI System Uptime Sensor
WMI Terminal Services (Windows 2008) Sensor
WMI Terminal Services (Windows XP/Vista/2003) Sensor
WMI Vital System Data (V2) Sensor
WMI Volume Sensor
WMI Windows Version Sensor
WSUS Statistics Sensor
Xen Virtual Machine Sensor
Additional Sensor Types (Custom Sensors)
662
669
675
679
684
690
695
700
705
711
716
720
725
730
735
739
745
750
755
760
766
771
778
785
790
797
804
811
817
825
830
835
841
846
851
856
862
866
872
877
882
887
893
897
901
905
911
917
923
930
935
Contents
10
11
Sensor Channels Settings
Sensor Notifications Settings
938
943
954
Part VII Ajax Web Interface—Advanced Procedures
1
2
3
4
5
6
7
8
9
10
11
12
13
Toplists
Arrange Objects
Clone Object
Multi-Edit Lists
Create Device Template
Compare Sensors
Show Dependencies
Geo Maps
Notifications
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 Settings—My Account
Account Settings—Notifications
Account Settings—Schedules
System Administration—System and Website
System Administration—Notification Delivery
System Administration—Probes
System Administration—Cluster
System Administration—User Accounts
System Administration—User Groups
PRTG Status—System Status
PRTG Status—Auto Update
Downloads
955
960
962
964
969
971
973
975
978
980
983
986
988
992
993
996
999
1002
1010
1013
1015
1022
1026
1028
1032
1041
1044
1051
1056
1058
1060
1064
1066
1068
1070
1074
Part VIII Enterprise Console
1
2
3
First Start
General Layout
Menu Tabs and Page Content
Devices
Libraries
Sensors
Alarms
1076
1078
1081
1082
1088
1090
1092
7
Contents
4
5
6
7
8
Maps
Reports
Logs
ToDos
Setup
Search Results
PRTG Servers
Options
Windows Menu Structure
Context Menus
Shortcuts Overview
1094
1095
1096
1098
1100
1102
1103
1106
1112
1116
1117
1120
Part IX Other User Interfaces
1
2
HTML GUI (Low bandwidth)
Smartphone Apps
1121
1125
1128
Part X Sensor Technologies
1
2
3
4
5
6
7
Monitoring via SNMP
Monitoring via WMI
Monitoring Bandwidth via Packet Sniffing
Monitoring Bandwidth via Flows
Bandwidth Monitoring Comparison
Monitoring Quality of Service
Monitoring Email Round Trip
1129
1133
1135
1138
1141
1144
1148
1152
Part XI System Administration Tools
1
2
PRTG Server Administrator
PRTG Probe Administrator
1153
1170
1182
Part XII Advanced Topics
1
2
3
4
5
6
7
8
9
Active Directory Integration
Application Programming Interface (API) Definition
Filter Rules for xFlow and Packet Sniffer Sensors
Channel Definitions for xFlow and Packet Sniffer Sensors
Define IP Ranges
Regular Expressions
Add Remote Probe
Remote Probes and Multiple Probes
Remote Probe Setup
Data Storage
Calculating Percentiles
1183
1185
1186
1189
1191
1192
1193
1194
1197
1202
1203
1206
Part XIII Appendix
1
2
3
4
8
Glossary
List of Abbreviations
Support and Troubleshooting
Legal Notices
1207
1211
1213
1214
Contents
Index
1215
9
Part I: Welcome to PRTG Network Monitor
Part I
Welcome to PRTG Network Monitor
2011-08-12
11
Part I: Welcome to PRTG Network Monitor
1
Welcome to PRTG Network Monitor
Welcome to PRTG Network Monitor! You've chosen an easy-to-use software product that
comes with a powerful set of features to monitor your entire network.
Why Network Monitoring is Important
Today, most businesses rely on a computer and network infrastructure for internet, internal
management, telephone and email. A complex set of servers and network equipment is
required to ensure that business data flows seamlessly between employees, offices, and
customers. The economical success of an organization is tightly connected with the flow of
data.
The computer network's reliability, speed, and efficiency are crucial for businesses to be
successful. But, like all other technical objects, network devices may fail from time to
time—potentially causing trouble and loss of sales, no matter what migration efforts have
been made up-front.
Network administrators need to take three key steps to maintain network uptime, reliability
and speed:
1. Set up a well-planned network with reliable components.
2. Create recovery plans for the event of device failure.
3. Monitor their network to know about failures as they build up or actually happen.
PRTG Network Monitor, the software described in this document, is a complete solution for
monitoring small, medium, and large networks.
Monitoring Networks with PRTG Network Monitor
PRTG Network Monitor is a powerful network monitoring application for Windows-based
systems. It is suitable for small, medium, and large networks and capable of LAN, WAN,
WLAN and VPN monitoring. You can also monitor real or virtual web, mail, and file servers,
Linux systems, Windows clients, routers, and many more. It monitors network availability and
bandwidth usage as well as various other network parameters such as quality of service,
memory load and CPU usages. It provides system administrators with live readings and
periodical usage trends to optimize the efficiency, layout and setup of leased lines, routers,
firewalls, servers and other network components.
The software is easy to set up and use and monitors a network using Simple Network
Management Protocol (SNMP), Windows Management Instrumentation (WMI), packet sniffer,
Cisco NetFlow (as well as sFlow and jFlow) and many other industry standard protocols. It
runs on a Windows-based machine in your network for 24-hours every day. PRTG Network
Monitor constantly records the network usage parameters and the availability of network
systems. The recorded data is stored in an internal database for later analysis.
12
2011-08-12
Part I: Welcome to PRTG Network Monitor
1.1
About this Document
This document introduces you to the system concepts of PRTG Network Monitor 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 Start Guide
detailed instructions, see the other sections.
2010-08-26
28
section. For more
13
Part I: Welcome to PRTG Network Monitor
1.2
Key Features
PRTG monitors your network and requires no third party software.
What PRTG Can Be Used For
§ Monitor and alert for uptimes/downtimes or slow servers.
§ Monitor and account bandwidth and network device usage.
§ Monitor system usage (CPU loads, free memory, free disk space etc.).
§ Classify network traffic by source/destination and content.
§ Discover unusual, suspicious or malicious activity with devices or users.
§ Measure QoS and VoIP parameters and control service level agreements (SLA).
§ Discover and assess network devices.
§ Monitor fail-safe using a failover cluster setup.
What PRTG Includes
The PRTG installer contains all modules and software necessary to run the monitoring system
without the need for third party modules, including:
§ Paessler's own fast and efficient database system to store the raw monitoring results as
well as logs, Toplists, and ToDos (outperforms SQL servers for monitoring data).
§ Built-in web server with HTTP and HTTPS support for the user interface.
§ Mail server for automatic email delivery.
§ Report generator to create reports in HTML or Portable Document Format (PDF).
§ Graphics engine for user-friendly charts.
§ Network analysis module to automatically discover devices and sensors.
§ An Application Programming Interface (API) allows users to program their own features.
PRTG Network Monitor can support thousands of sensors and can optionally work with
multiple remote probes to monitor multiple sites or network segments from one central core
installation. You can also configure fail-safe monitoring using a cluster installation.
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. Attractive licensing packages from freeware (up to 10 sensors) to enterprise
level (with thousands of sensors) make sure that every user finds the proper solution.
14
2011-08-08
Part I: Welcome to PRTG Network Monitor
1.3
New in Version 9
PRTG V9 comes with a lot of new features, making comprehensive network monitoring even
easier. Changes and new features include:
§ "Libraries" and Improved Tree Display
§ The new Enterprise Console 1074
§ Monitoring of IPv6 Networks
§ New Add Sensor
182
Dialog
§ Added "Hardware" Sensor Types
237
§ New Monitoring Features, such as QoS (Quality of Service) Round Trip Sensor 542 , SSH
VMWare ESX(i) Disk Sensor 700 , WMI Physical Disk Sensor 866 , Hyper-V Virtual Network
Adapter Sensor 399 , Windows Registry Sensor 771 , etc.
§ Updated Ajax web interface
98
§ User Management using Active Directory 1183
§ Improved Auto-Discovery
158
§ Automatic software update 1068 for your PRTG servers
More
For detailed information, please see the PRTG Network Monitor 9 Version History
§ http://www.paessler.com/prtg/prtg9history
2011-09-19
15
Part I: Welcome to PRTG Network Monitor
1.4
Available Licenses
There are four different PRTG flavors available.
Freeware Edition
The Freeware Edition is a good solution to get started with PRTG, or for private use:
§ May be used for free for personal and commercial use.
§ Can monitor up to 10 sensors.
§ Supports all available sensor types.
§ Shortest available monitoring interval is one minute.
Starter Edition
The Starter Edition has all the features of the Freeware Edition, but it supports up to 20
sensors. By entering a Starter Edition key, you can extend your Freeware Edition. For detailed
information, see More 17 section below.
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 (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 afterwards).
As default after installation, the Trial Edition runs with the functionality of the Freeware
Edition only when no license key is entered. Free trial license keys see More 17 section
below.
Commercial Editions
There are several licenses of PRTG Network Monitor available to suit the demands of smaller,
as well as larger customers and organizations:
§ Can monitor maximum number of sensors (from 100 to unlimited).
§ Supports all available sensor types.
16
2011-09-01
Part I: Welcome to PRTG Network Monitor
§ Shortest available monitoring interval is one second (a minimum interval of 10 seconds is
recommended).
For more information about available commercial licenses, please see More
17
section below.
More
Knowledge Base: What is the PRTG Starter Edition license?
§ http://www.paessler.com/knowledgebase/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
2011-09-01
17
Part I: Welcome to PRTG Network Monitor
1.5
System Requirements
In order to install and work with PRTG Network Monitor you need:
§ 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 installations, use
systems with similar performance.
§ Operating system Microsoft Windows XP, Windows 2003 SP1 or later, Windows 2008 R2, or
Windows 7 (32-bit or 64-bit). You can also use Windows Vista or 2008 R1, but we
recommend not to use these systems, as there are known performance issues related to
them.
§ Web browser to access the web interface (Google Chrome is recommended; Firefox 4 or
later, and Internet Explorer 9 were also tested).
Planning an Installation With Hundreds of Sensors or More?
As a rule of thumb an average PC/server built in the year 2007 or later should be able to
monitor 1,000 sensors with ease. Some exceptions apply for version 3 of Simple Network
Management Protocol (SNMP), Windows Management Instrumentation (WMI) and packet
sniffer. The maximum number of sensors you can monitor with one installation of PRTG
mainly depends on the monitoring technology and the monitoring intervals you use:
§ SNMP V1 and V2, Ping, Port, and HTTP
These sensor types are recommended for scenarios with thousands of sensors. With these
technologies up to 30,000 sensors are possible.
§ SNMP V3
You will be able to monitor between 60 and 6,000 SNMP V3 sensors with an interval of 60
seconds (depending on request times in your network).
§ WMI
Try to keep the number of WMI sensors per probe below 120 sensors (with 60s interval), or
600 sensors (with 300s interval).
§ xFlow (NetFlow, sFlow)
Monitoring the maximum number of sensors depends on the traffic pattern, the number of
xFlow packets per second received by the PRTG probe, as well as the performance of the
probe system (see site planner tool linked in the More 19 section below).
§ Packet Sniffer
These sensors create the highest CPU load on the probe system. This technology is only
recommended for monitoring of low traffic connections (<50 Mbit/s steady stream). When
traffic is often over 10 Mbit/s a dedicated remote probe 1193 should be used.
To overcome any limitations mentioned above you should distribute the sensors over two
remote probes 1193 or more. For detailed information please use the site planner tool to plan
large installations. See More 19 section below.
18
2011-10-12
Part I: Welcome to PRTG Network Monitor
For more information please see the Detailed System Requirements
20
section.
More
Paessler website: Paessler PRTG Site Planner Tool
§ http://media.paessler.com/publicimages/prtgsiteplanner.htm
Knowledge Base: How can I speed up PRTG—especially for large installations?
§ http://www.paessler.com/knowledgebase/en/topic/2733
2011-10-12
19
Part I: Welcome to PRTG Network Monitor
1.5.1 Detailed System Requirements
This section lists different aspects of system requirements for PRTG:
§ Supported Operating Systems
§ Hardware Requirements
§ Sample Configurations
20
21
21
§ Running PRTG on Virtual Machines
§ Web Browser Requirements
23
23
§ Requirements for Monitored Devices
§ Requirements for the Windows GUI
§ Requirements for HTML GUI
24
24
§ Requirements for Smart Phones
§ More
24
24
25
Supported Operating Systems
The 32-bit and 64-bit versions of the following operating systems are officially supported for
PRTG Core Service and Probe Service (Intel x86/x64 architectures only):
§ Microsoft Windows XP SP2 or later
§ Microsoft Windows Server 2003 SP1 or later
§ Microsoft Windows Vista*
§ Microsoft Windows Server 2008*
§ Microsoft Windows Server 2008 R2
§ Microsoft Windows 7
* For performance reasons, we recommend to not use Windows Vista or 2008 R1, especially
when monitoring via Windows Management Instrumentation (WMI). Using these operating
systems you will only be able to use a limited number of WMI sensors! For detailed
information please see More 25 section below.
Some sensor types need the Microsoft .NET Framework to be installed on the computer
running the PRTG probe: Either on the local system (on every node, if in a cluster), or on the
system running a remote probe 1194 . Depending on the sensor type, the required version is 2.0
or 3.0.
20
2011-10-12
Part I: Welcome to PRTG Network Monitor
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 8 (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).
§ Internet connection
An internet connection is required for license activation (via HTTP or email).
There are also non-hardware dependent limitations for some sensor types, e.g. WMI and
SNMP V3 sensors. These limitations can be overcome by distributing the sensors across
multiple remote probes 1193 . 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 25 section below.
Sample Configurations
The sample configurations in the table below will give you an overview of the hardware
requirements for PRTG, based on your configuration.
2011-10-12
21
Part I: Welcome to PRTG Network Monitor
Large Installation
A
Large Installation
B
Netbook
Installation
System
DELL Alienware
DELL PowerEdge
2900 III
DELL Inspiron Mini
10
CPU
Intel Core2
Quad-Core
2.6 GHz
Intel Xeon
Quad-Core
1.87 GHz
Intel Atom Z520
1.33 GHz
16 GB
1 GB
RAM
8 GB
Operating System
Windows 7 64-Bit
Windows 2003
64-Bit
Windows XP 32-Bit
Sensors
20,000 SNMP
100 Other
20,000 SNMP
600 SNMP
750 WMI
400 switches à 48
ports
400 switches à 48
ports
24 switches à 25
ports
+ 30 Windows
server
Scanning Interval
1 minute
1 minute
5 minutes
Number of Probes
4
1
1
Average CPU Load
While Monitoring*
3%
20 %
35 %
Average CPU Load
While Generating
Reports*
20 %
30 %
85 %
Average Memory Used
3 GB
3.5 GB
260 MB
Average Data Written
to Disk Per Year
800 GB
800 GB
55 GB
550 kbit/s
150 kbit/s
Installation
Corresponds To
Average Network Load 80 kbit/s
22
2011-10-12
Part I: Welcome to PRTG Network Monitor
* CPU load is higher while users are accessing the web interface.
Running PRTG on Virtual Machines
PRTG core server as well as PRTG probe can be run on virtualized platforms. The following
platforms were tested successfully:
VM Technology
Client OS
VMware ESX/ESXi (version 3.5 and VSphere
4)
Windows XP, Windows 2003 SP1 or later
(32/64 bit), Windows Vista, Windows 7
(32/64 bit), Windows 2008 (32/64 bit)
VMware Server 2.0
Windows XP, Windows 2003 SP1 or later
(32/64 bit), Windows 2008
XEN Server 5.0
Windows XP
Parallels Virtuozzo Containers
Windows 2003 Server SP1 or later (32/64
bit)
Cloud Hosting Platforms (Amazon EC2,
TheRackspaceCloud, and others)
Windows Server 2003 SP1 or later, Windows
Server 2008
Note: When monitoring more than 1,000 sensors we recommend to use dedicated real
hardware instead of a virtual machine. In our experience, this improves performance a lot.
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 simply not working efficiently for a monitoring
software and can therefore lead to massive performance issues.
Web Browser Requirements
The following browsers are officially supported by the PRTG web interface (in order of
performance and reliability):
§ Google Chrome 10 or later (recommended)
§ Mozilla Firefox 4 or later
§ Microsoft Internet Explorer 9
Note: Microsoft Internet Explorer versions 8 and earlier as well as mobile browsers cannot
display the full featured Ajax web interface 98 . Using these browsers, you can access the
feature-limited HTML web interface 1121 , which does not require CSS or Javascript capability.
2011-10-12
23
Part I: Welcome to PRTG Network Monitor
PRTG's web interface makes heavy use of Javascript and AJAX. We found that for some
functions Chrome is up to 10 times faster than Internet Explorer, and 3 to 5 times faster than
Firefox.
Internet Explorer version 8 or higher has to be installed on the system running a PRTG probe,
so PRTG's HTTP Full Web Page Sensor 364 sensor can work correctly.
Requirements for Monitored Devices
§ SNMP monitoring
The monitored device(s) must be equipped with SNMP Version 1, 2c or 3 (i.e. a
SNMP-compatible software must be installed on the device). SNMP must be enabled on the
device and the machine running PRTG must be granted access to the SNMP interface.
§ WMI monitoring
In order to use WMI (Windows Management Instrumentation) monitoring you will need a
Windows network. For client PCs monitored with WMI only Windows XP and later are
officially supported (XP, 2003, Vista, 2008, etc.). Windows 2000 is not officially supported.
Please do not use Windows Vista or Windows 2008 R1 for WMI monitoring (they both have
WMI performance issues).
§ xFlow (NetFlow, sFlow) monitoring
The device must be configured to send NetFlow data packets (NetFlow version 5 or 9) or
sFlow packets (version 5) to the machine running the PRTG probe.
§ Packet Sniffer monitoring
Only data packets passing the local machine's network card can be analyzed. Switches with
so-called 'monitoring ports' are necessary for network-wide monitoring in switched
networks.
Requirements for the Enterprise Console
The optional PRTG Enterprise Console 1074 runs under all Windows versions XP or later. It has
a built-in webkit browser engine and requires no specific browser installed on the system.
Requirements for HTML GUI
The feature-limited HTML web interface is optimized for low bandwidth and mobile access. It
has been designed for and tested with iOS (iPhone, iPad), Android, Blackberry, Windows
Mobile, Opera Mini, and even Internet Explorer 5/6/7/8.
Requirements for Smart Phones
The optional smart phone apps for iOS require firmware 3.0 (or later). For Android devices,
OS 2.1 through 3.0 are recommended. For more information, please see Smart Phone Apps
1125 . The 'Mini HTML 1121 ' interface can be used on most phones with a browser. We
successfully tested it on Symbian, Blackberry, Windows, Android, and iOS devices.
24
2011-10-12
Part I: Welcome to PRTG Network Monitor
More
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/
Paessler Website: Paessler PRTG Site Planner Tool
§ http://media.paessler.com/publicimages/prtgsiteplanner.htm
Knowledge Base: How can I speed up PRTG—especially for large installations?
§ http://www.paessler.com/knowledgebase/en/topic/2733
2011-10-12
25
Part II: Quick Start Guide
Part II
Quick Start Guide
2011-09-22
27
Part II: Quick Start Guide
2
Quick Start Guide
Welcome to PRTG Network Monitor! This section will support you with a quick start into
PRTG, so you can start monitoring your network out-of-the box!
Setting up monitoring for your network is easy! Please see the following quick steps:
§ ONE—Download and Installation
30
§ TWO—Auto-Discover Your Network
33
Welcome Screen
More
This quick start guide is available as a separate document, and also in different languages.
Please click on the following links to open the respective PDF files.
English: Getting Started with PRTG
§ http://download.paessler.com/download/prtg9manual_qen.pdf
German: Loslegen mit PRTG
§ http://download.paessler.com/download/prtg9manual_qde.pdf
Spanish: Iniciar con PRTG
§ http://download.paessler.com/download/prtg9manual_qes.pdf
French: Mise en route de PRTG
28
2011-09-22
Part II: Quick Start Guide
§ http://download.paessler.com/download/prtg9manual_qfr.pdf
2011-09-22
29
Part II: Quick Start Guide
2.1
ONE—Download, Installation, and First Login
Simply download and install your version of PRTG.
Download
On the Paessler website, you find two different installers for PRTG, a public download for the
Freeware and Trial editions, and another download for the commercial editions (which is only
available for paying customers).
PRTG Download at Paessler Website
Downloading the Freeware Edition or Trial Edition
Please download the latest publicly available file from the Paessler website. When
downloading the Trial Edition, you can also request a trial key there:
§ http://www.paessler.com/prtg/download
30
2011-10-07
Part II: Quick Start Guide
Downloading the Commercial Editions
Downloads and updates are free to customers with an active maintenance contract. Please
log into the Paessler website to get the latest download. You can also find your license key
there:
§ http://www.paessler.com/login
If you do not have an active maintenance contract, please contact sales@paessler.com.
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 welcome wizard
will appear.
Welcome Wizard
Welcome Wizard
Should you have questions while in the welcome wizard, please click on the blue question
mark ? symbol in the upper right corner to load a help page in your browser.
2011-10-07
31
Part II: Quick Start Guide
§ Step 1: Choose the type of Edition you want to install. For Trial Edition, Starter Edition, or
Commercial Edition, provide your License Key information (not necessary for Freeware
Edition).
§ Step 2: In the Essential Settings, enter a valid email address and leave the Standalone
Mode setting.
At the end of the welcome wizard some basic information about PRTG is displayed. Please
read the provided information carefully, as it will ease your work with PRTG easily. Finally, a
browser window is opened showing the PRTG login screen at the core server's IP address.
Login
Please make sure you use a supported web browser when logging in to PRTG. We recommend
using Google Chrome 10 or Mozilla Firefox 4 (or later versions). Only with a supported
browser can you use the AJAX GUI (All features) option. If you see this option grayed out
(for example, with Internet Explorer 8), please change your browser and open the URL again.
PRTG Login Screen
§ Leave the Login Name and Password fields empty.
§ Choose the AJAX GUI (All features) option.
§ Click on the Default Login button to login.
32
2011-10-07
Part II: Quick Start Guide
2.2
TWO—Auto-Discover Your Network
Click on the Home button in main menu. The welcome screen is shown.
Welcome Screen
Click on Network Auto-Discovery to automatically scan in your network. PRTG will try to
detect all attached devices automatically in just two steps. For video instructions, please see
the More 35 section below.
Auto-Discovery—Step 1
In the first step, the tree with all probes and groups of your setup is shown.
Add Auto-Discovery Group Assistent Step 1
§ Choose Local probe from the device tree.
2011-09-21
33
Part II: Quick Start Guide
§ Click the Continue button.
Auto-Discovery—Step 2
In the second step, some additional information about your network is required.
Add Auto-Discovery Group Assistant Step 2
§ With the IP Selection Method, choose whether you want to enter a Class C base IP with
start/end (IPv4), a List of individual IPs (IPv4), IP and Subnet (IPv4), or an IP with octet
range (IPv4). If you want to discover an IPv6 network, you can provide a list using the List
of individual IPs (IPv6) option. All of these methods result in a number of IP addresses
that will be scanned during the auto-discovery process. Based on your selection above,
different setting fields are available.
§ We recommend you leave the Class C base IP option. 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 values for IPv4 Range Start and End, PRTG
will automatically complete the IP base and scan all IP addresses ending in .1 to .254.
34
2011-09-21
Part II: Quick Start Guide
§ If available, provide credentials for Windows Systems, Linux Systems, VMware/XEN
Servers, and for SNMP Devices. You can show the respective settings by removing the
check mark symbol at the beginning of the respective line. Find more information in the
Auto-Discovery 158 section.
§ Keep the default values for all other settings.
§ Click the Continue button.
Ready
PRTG will now start discovering your network in the background, adding devices and sensors
automatically. Meanwhile, you can get familiar with the Ajax web interface.
Auto-Discovery in Progress
The first steps are taken. Usually, the auto-discovery function has already detected most of
the devices in your network. There are also sensors on the local Probe Device, monitoring
the computer PRTG is installed on. In the welcome screen, click on Review Results to view
the device tree with all devices.
As next step, we recommend going through the following sections:
§ Ajax Web Interface
98
§ Understanding the Basic Concepts
§ Root Group Settings
78
185
§ Device and Sensor Setup
156
More
Video Tutorial: There is a video available on the Paessler video tutorials page.
§ http://www.paessler.com/support/video_tutorials
2011-09-21
35
Part III: Installing the Software
Part III
Installing the Software
2011-08-09
37
Part III: Installing the Software
3
Installing the Software
This section describes how to download and install your PRTG product.
PRTG Setup
Please see the following sections for more information.
Installing the Software—Topics
§ Download
39
§ Upgrade From Previous Versions to V8
§ Install a PRTG Core Server
§ Install a PRTG Cluster
§ Enter a License Key
44
56
59
§ Activate the Product
62
§ Install a PRTG Remote Probe
64
§ Install the Enterprise Console
§ Uninstall
38
41
69
74
2011-08-09
Part III: Installing the Software
3.1
Download PRTG
On the Paessler website, you find two different installers for PRTG, a public download for the
Freeware and Trial editions, and another download for the commercial editions (which is only
available for paying customers).
PRTG Download at Paessler Website
Downloading the Freeware Edition or Trial Edition
Please download the latest publicly available file from the Paessler website. When
downloading the Trial Edition, you can also request a trial key there:
§ http://www.paessler.com/prtg/download
2011-09-21
39
Part III: Installing the Software
Downloading the Commercial Editions
Downloads and updates are free to customers with an active maintenance contract. Please
log into the Paessler website to get the latest download. You can also find your license key
there:
§ http://www.paessler.com/login
If you do not have an active maintenance contract, please contact sales@paessler.com.
40
2011-09-21
Part III: Installing the Software
3.2
Update From Previous Versions to V9
If you already have installed a previous software version, there are several possibilities for
you.
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 42 section below.
Update From Older 9.x Versions
If you have been running PRTG Network monitor with an earlier 9.x version number, simply
install 44 the latest version on top of the previous version. Your configuration will be kept. If
you have configured PRTG as a cluster, you only have to install an update on any node server
(master or failover). The new version will then be deployed to the cluster automatically. Note:
We recommend you always have a proper backup of your monitoring data.
Update From PRTG Network Monitor 7 or 8
If you are using PRTG 7 or 8 now, your configuration will be kept when installing PRTG 9 in
Standalone Mode or when installing a Master Node. There are only a few things you should
consider.
Note: If you're running PRTG 7 we recommend you first update to the latest PRTG 8 version
as an intermediate step, in order to make sure all data is carried over correctly. Please
contact technical support 1213 to obtain a download link for PRTG 8. In any case we
recommend you always keep a proper backup of your configuration and monitoring data.
Updating from PRTG 7 or 8 to PRTG 9
§ Packet Sniffer (Content) sensors are not supported any more. Existing sensors of this type
will automatically be switched to Packet Sniffer (Header) sensors after the update. As a
benefit, you can now also sniff IPv6 traffic.
§ Internet Explorer 8 is no longer supported for access to the PRTG Ajax web interface.
§ You may experience a slow Enterprise Console 1074 (former 'Windows GUI') due to different
reasons. For detailed information, please see the knowledge base article linked in the More
42 section below.
§ When installing a failover node on top of an existing stand-alone PRTG 7, 8, or 9
installation, the configuration cannot be kept and is written to a backup folder. Then, the
new cluster configuration is received from the master node of the cluster. As all nodes
work with the same configuration, a failover node's old configuration and monitoring data
can no longer be used. If you want to keep a configuration of PRTG 7, please install the
master node on top of the old installation and use other servers for the failover node
installations.
2011-11-24
41
Part III: Installing the Software
§ The SNMP sensors in PRTG 9 now use the IPv4 Outgoing IP set for the probe service (this
setting was formerly ignored by those sensors, using the auto setting instead). If you
experience failing sensors, please check the setting in the PRTG Probe Administrator 1172 .
For detailed information please see More 42 section below.
§ 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 PRTG 9. For detailed
information please see More 42 section below.
§ Probe core and probe now require: SP1 (or later) on Windows 2003, and SP2 (or later) on
Windows XP.
§ 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.
Updating from PRTG 7 to PRTG 9
§ 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 PRTG 9 if
they do not fully apply to the API definition 1185 .
Update From Older PRTG Products
For all other predecessor products, a direct data import into version 9 is not possible.
If you have been using IPCheck 5 or PRTG Traffic Grapher 6, please perform a clean
installation of PRTG 9 and set up your configuration anew. Using PRTG's Auto-Discovery 158
is the easiest way to quickly configure a monitoring of your entire network. Please see Quick
Start Guide 28 section for more information.
More
Knowledge Base: How do I backup all data and configuration of my PRTG installation?
§ http://www.paessler.com/knowledgebase/en/topic/523
Knowledge Base: Why is the Enterprise Console so slow?
42
2011-11-24
Part III: Installing the Software
§ http://www.paessler.com/knowledgebase/en/topic/25413
Knowledge Base: Some of my SNMP sensors do not work after updating from PRTG 8 to PRTG
9
§ http://www.paessler.com/knowledgebase/en/topic/25663
Knowledge Base: Probe Service or Core Service stop working after updating from PRTG 8 to
PRTG 9
§ http://www.paessler.com/knowledgebase/en/topic/25463
Knowledge Base: How and where does PRTG store its data?
§ http://www.paessler.com/knowledgebase/en/topic/463
Knowledge Base: Can I update from PRTG Traffic Grapher or IP Check 5 to PRTG 9?
§ http://www.paessler.com/knowledgebase/en/topic/26553
Knowledge Base: How do I Import Data from PRTG Traffic Grapher 6 or IPCheck Server
Monitor 5 in PRTG Network Monitor?
§ http://www.paessler.com/knowledgebase/en/topic/253
2011-11-24
43
Part III: Installing the Software
3.3
Install a PRTG Core Server
Installing PRTG is easy. The setup process will guide you through both installation and
welcome wizard.
PRTG Installation
§ Setup Wizard
45
§ Welcome Wizard
44
48
2011-04-21
Part III: Installing the Software
3.3.1 Setup Wizard
Installing the software is similar to other Windows-based applications. To install the
application please run the installation setup program from the ZIP file that you have
downloaded.
Windows User Account Control Confirmation Request
Confirm the question of the Windows User Account Control with Yes to allow the program to
install. The usual software installation wizard will guide you through the installation process.
Setup Language Selection
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.
2011-08-22
45
Part III: Installing the Software
Setup Wizard Start Screen
Please click Next to walk through the wizard.
Setup Wizard License Agreement
After accepting the license agreement, you can choose the folder you wish to install the
software in. We recommend using the default value.
46
2011-08-22
Part III: Installing the Software
Setup Wizard Destination Location
As soon as you click Next, the necessary files will be copied to your disk.
Setup Wizard Installing
After installation, the Welcome Wizard
first time.
2011-08-22
48
is shown if you're installing a major version for the
47
Part III: Installing the Software
3.3.2 Welcome Wizard
Directly after installation, a welcome wizard appears. Note: When updating an existing PRTG
Commercial Edition in version 8 or 9 with a (newer) version of PRTG 9, this wizard is not
shown.
Follow the welcome wizard by clicking on the Next button. To load a web page with extended
help, click on the blue question mark ? symbol in the upper right corner any time.
Select Edition
In the first step, a dialog appears, asking for the edition you would like to install. Please
select the proper option. When selecting Trial Edition, Starter Edition, or Commercial Edition,
please enter license information, too.
Welcome Wizard Edition and License Selection
Use the Freeware Edition
§ Use PRTG for free without a time limit
§ Monitoring is limited to 10 sensors and a minimum scanning interval of one minute
§ No registration is needed to use PRTG as Freeware!
Run the Free Trial Edition or the Starter Edition
48
2011-09-27
Part III: Installing the Software
§ Test PRTG for 30 days with unlimited access to the software
§ You can monitor with an unlimited number of sensors
§ You need to register at Paessler with your name and email address, so we can send you a
free trial key
§ After the trial period, PRTG will automatically change to a freeware edition
§ Note: If you have received a special Starter Edition key for extended freeware monitoring
with 20 sensors, please choose this option (see More 54 section below). There is not timely
limitation with a Starter Edition key.
Purchase or Register a Commercial Edition
§ Please choose this option to enter a license key that you have already purchased. If you do
not yet have a commercial license key, you can go to the Paessler web shop now by
following the buy a license link.
§ This option is only available if you have downloaded the commercial installer. You cannot
use a commercial key with the freeware- or trial installer. In order to download the
commercial installer, please log in to your Paessler customer account.
§ Enter a license key and monitor your network with the number of sensors you have
chosen.
Enter License Information
If you selected Trial Edition or Commercial Edition before, enter your license information.
2011-09-27
49
Part III: Installing the Software
Welcome Wizard Enter License Information
Please enter both Name and Key exactly as stated in the email received from Paessler. We
recommend using copy&paste to avoid typing mistakes.
Essential Settings
In the next step, please define important essential settings. PRTG pre-configures all other
settings for you so you only have to enter your email address and select a setup mode.
50
2011-09-27
Part III: Installing the Software
Welcome Wizard Essential Settings
Essential Settings—Email Address
§ Enter a valid administrator's email address.
§ By default, PRTG will send notifications and important messages to this address.
Essential Settings—How do you want to run PRTG?
PRTG offers single failover clustering in all licenses—even using the Freeware edition. For
detailed instructions, please see Install a PRTG Cluster 56 section.
Please select if you want to configure PRTG for a cluster.
Run PRTG in "Standalone Mode"
§ Run one instance of PRTG as a standalone solution.
§ If you are not sure what to choose, take this option. You can integrate a PRTG installation
in standalone mode into a cluster later on.
§ Monitoring and alerting is performed by one single PRTG installation only.
Run PRTG in "Cluster Mode"
§ Run several PRTG installations combined in a cluster.
§ Select this option for a high-available monitoring solution.
2011-09-27
51
Part III: Installing the Software
§ Two or more PRTG installations work together in one cluster and act as one monitoring
system.
§ Automatic failover: One PRTG installation takes over monitoring and alerting seamlessly in
case the other installation fails or the server is restarted.
§ Multi-location monitoring: You also have the option to monitor your network from different
locations by setting up geographically distributed installations.
§ For detailed instructions please see Install a PRTG Cluster
56
section.
Cluster Settings
This screen only appears if you have chosen to set up a PRTG cluster. Please select whether
you want this PRTG installation to be the master node or a failover node. For detailed
instructions please see Install a PRTG Cluster 56 section.
Welcome Wizard Cluster Settings
Cluster Settings—Install a Master Node
§ Make this PRTG installation the master node of your cluster.
§ Choose this option if you are about to make the first installation in your cluster.
§ The master node usually controls your whole cluster.
§ There may only be one master node in a PRTG cluster. Please do not install several master
nodes, as they won't be able to connect to each other. Instead, use failover nodes for all
other installations in your cluster.
52
2011-09-27
Part III: Installing the Software
Cluster Access Control
§ Cluster Access Key: For safety reasons, a node can only connect to the cluster with a
cluster access key. With the setup of the master node you will define a new key for the
cluster here. The access key is already pre-defined; you can leave the default value.
§ Cluster Port: All communication in the cluster is directed through the cluster port. It is
already pre-defined; you can leave the default value.
§ Please make sure the security settings in your network allow communication between all
nodes on the defined port.
§ Save both cluster access key and cluster port in a text file for later use; you will need them
in the cluster settings for each failover node later.
Cluster Settings—Install a Failover Node
§ Make this PRTG installation a failover node in the cluster.
§ Choose this option if you have already set up a master node and want to add a failover
node to your cluster.
§ There may be several failover nodes in one cluster—provided that you have the appropriate
license.
Cluster Access Control
§ Cluster Access Key: For safety reasons, a node can only connect to the cluster with a
cluster access key. For a failover node, please enter the existing key you have defined while
setting up the master node.
§ Cluster Port: All communication in the cluster is directed through the cluster port. It must
be the same port defined for the master node.
§ Please make sure the security settings in your network allow communication between all
nodes on the defined port.
§ If unknown, you can look up cluster access key and cluster port in the PRTG Server
Administrator program (Cluster tab) on the server your master node is running on.
Join an Existing Cluster Automatically
§ This will add the failover node to the master node's settings automatically.
§ Master: Enter the IP address or DNS name of the master node in order to join the cluster
automatically.
§ If you enter nothing here, you'll have to add the master node's IP address or DNS name
later in the PRTG Server Administrator program on the server the failover node is running
on. For more information, please see Step 3 and following of 10 Steps to Set Up a PRTG
Cluster—Scenario 3 (see More 54 section below).
2011-09-27
53
Part III: Installing the Software
§ Important: After joining, you must confirm the new node in the master node's settings in
order for the failover node to connect to the master node! For more information, please
see Step 7 and following of 10 Steps to Set Up a PRTG Cluster—Scenario 3 (see More 54
section below).
Introductory Information about PRTG
In the next four screens, some basic information about PRTG is shown. Please read the
information carefully as it will help you setting up a good PRTG configuration.
Ready to Load the Browser
At the end, click on Next to open a browser window and log in to the web interface
100
.
More
Knowledge Base: What is the PRTG Starter Edition license?
§ http://www.paessler.com/knowledgebase/en/topic/8063
Knowledge Base: How can I establish a secure web interface connection to PRTG?
§ http://www.paessler.com/knowledgebase/en/topic/273
Knowledge Base: PRTG blocks port 80 although I'm using SSL on port 443. How to free port
80?
§ http://www.paessler.com/knowledgebase/en/topic/5373
54
2011-09-27
Part III: Installing the Software
Knowledge Base: How do I set up a cluster in PRTG 8?
§ http://www.paessler.com/knowledgebase/en/topic/6143
Knowledge Base: 10 Steps to Set Up a Cluster—Scenario 3
§ http://www.paessler.com/knowledgebase/en/topic/6923
2011-09-27
55
Part III: Installing the Software
3.4
Install a PRTG Cluster
PRTG offers single failover clustering in all licenses—even using the freeware edition. A
single failover cluster consists of two servers ("Node 1" and "Node 2"), each of them running
one installation of PRTG. They are connected to each other and exchange configuration and
monitoring data.
Illustration of a Single Failover Cluster
For setting up a cluster you need two or more (virtual) servers and there is one core
installation 44 process necessary on each of them—with different options selected for each
type of node. In return, you benefit from seamless high-available monitoring with automatic
failover and/or multi-location monitoring.
In a cluster, you can install:
§ 1 Master 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 to 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.
Start with setting up your master node. You can install additional failover nodes in a second
step.
Before Getting Started
Configuring a cluster with one failover node is the most common way to set up a seamless
network monitoring with PRTG. You will need two servers running any Windows version
(XP/2003 or later); your servers can be real hardware or virtual machines.
Please make sure the following:
§ Your servers must be up and running
§ Your servers must be similar in regard to the system performance and speed (CPU, RAM
memory, etc.)
56
2011-08-22
Part III: Installing the Software
§ We recommend installing PRTG on dedicated 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 mail
§ 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.
The Three Scenarios
There are different starting points for setting up a cluster. Each of them requires different
instructions. Please see the following Knowledge Base articles.
Scenario 1: You do not have a PRTG 9 installation yet
Make a fresh installation of two PRTG version 9 servers as a cluster or integrate one existing
PRTG version 7 or 8 server into a cluster of two PRTG version 9 installations.
§ http://www.paessler.com/knowledgebase/en/topic/6903
Scenario 2: You’ve set up one PRTG 9 installation in single mode already
Integrate an existing PRTG version 9 server into a failover cluster with two PRTG version 9
installations.
§ http://www.paessler.com/knowledgebase/en/topic/6913
Scenario 3: You've set up two PRTG 9 installations already, each running in single mode
Combine two existing PRTG version 9 servers into one failover cluster. The cluster will take
over the configuration of one server (the future master server); the configuration of the other
server (the future failover node) will be discarded.
§ http://www.paessler.com/knowledgebase/en/topic/6923
More
Knowledge Base: How do I set up a cluster in PRTG 8?
§ http://www.paessler.com/knowledgebase/en/topic/6143
2011-08-22
57
Part III: Installing the Software
Knowledge Base: What's the Clustering Feature in PRTG 8?
§ http://www.paessler.com/knowledgebase/en/topic/6403
Knowledge Base: What is a Failover Master and how does it behave?
§ http://www.paessler.com/knowledgebase/en/topic/7663
Knowledge Base: PRTG 8 Cluster: How do I convert a (temporary) Failover Master node to be
the Primary Master node?
§ http://www.paessler.com/knowledgebase/en/topic/8053
58
2011-08-22
Part III: Installing the Software
3.5
Enter a License Key
A license key for PRTG Network Monitor consists of the license name and a license key, which
is a string that contains 70 characters and numbers. This information is usually sent to
customers via email.
Example of license information
License Name: John Q. Public
License Key: 0223515-FFSEJC-ZHGRDFM-UR1CS8-U73FGK-G645F2-YVF1DD-H8323ND11HG9-M2DRG
You can either enter the license key during the installation process or you can select the Use
the Freeware Edition option. When installing as Freeware, you can use the PRTG Server
Administrator Windows program to enter a license key later. Your Freeware version will then
be converted to a trial or commercial version (only possible if commercial installer is used).
Note: You do not need to enter a license key if you want to use the freeware edition only.
Please check first if you have installed the proper edition and then enter the license key.
Step 1: Make Sure You Have Installed the Correct Edition
There are two different installers available for PRTG (see Download
39
section):
· The publicly available installer only contains the Freeware, Starter and Trial Editions. It
does not accept any commercial license keys.
· The Commercial installer is only available for download to paying customers.
The Commercial Installer must be installed to run the commercial editions of PRTG Network
Monitor. If you have purchased a license key for PRTG you must download and install
the latest Commercial Installer from the Paessler website in order to apply your license
key. You can install a commercial version "on top" of an existing Trial Edition in order to
maintain your configuration and monitoring data.
Step 2: Enter the License Key in the PRTG Server Administrator
Please start the PRTG Server Administrator program from the Windows Start Menu. In the
program, select the License tab.
Start Menu Icon
2011-08-19
59
Part III: Installing the Software
To use a PRTG license with this installation of PRTG, please enter the license information you
have received from Paessler via email. To avoid typing errors, please copy and paste both
the License Name and the License Key from the email. Both must be transferred exactly as
shown in the email.
PRTG Server Administrator License Tab
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 Edition field you will see an accepted licence key.
Click on the Ok button to save and confirm to restart the core server service by clicking on
the Yes button.
60
2011-08-19
Part III: Installing the Software
PRTG Server Administrator Confirm Service Restart
2011-08-19
61
Part III: Installing the Software
3.6
Activate the Product
PRTG tries to activate your license automatically via the internet on first start up. Only if
PRTG cannot connect to the internet directly, the web interface will display a Software
Activation Required notice.
Software Activation Information Box
You have to run through the product activation process once in order 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 will temporarily
revert to the Freeware Edition (with a maximum of 10 sensors) until you activate. Login to the
PRTG web interface 100 to activate.
Activate via Internet
In the PRTG web interface, choose Setup | PRTG Status | Activation Status from the main
menu.
License Activation Status
Click on the button Start Activation Now to start product activation. PRTG will now connect
with Paessler license server to check your license. A few seconds later you should see
Activation OK in the License Activation Status.
Note: The PRTG core server need a direct internet connection to activate. Proxy connections
are not supported for activation. In case activation fails, you can activate via email.
Activate via Email
In the PRTG Web Interface, choose Setup | PRTG Status | Activation Status from the main
menu.
62
2011-10-11
Part III: Installing the Software
If there is no internet connection available, you can activate PRTG via email. To do so, first
click on the Start Activation Now button. You will then see Last message about activation:
Activation failed in the License Activation Status.
§ Once the activation via internet fails, the activation via email is available.
§ Click on the Start Activation per EMail tab. You will see an Activation Request Code.
§ Copy it and send it to the email address shown.
§ Within two business days you will receive an email reply from Paessler, containing an
activation code.
§ Once you've received this email, go the Finalize Activation per EMail tab and copy the
activation code into the according field. Note: Please make sure you only copy the code
itself and nothing else from the email.
§ Click on Confirm Activation.
A few seconds later you should see Activation OK in the License Activation Status.
2011-10-11
63
Part III: Installing the Software
3.7
Install a PRTG Remote Probe
The local probe is already included in a PRTG core server installation 44 . You can install
additional remote probes on other computers in order to take load from the system running
the core installation or to extend monitoring to distributed networks. Note: You cannot
install a remote probe on a system already running a PRTG core installation.
Download Remote Probe Installer from the Web Interface
The remote probe version has to fit the PRTG core server version you will connect to. In order
download your setup program to the computer you want to install it on, please connect to
the Ajax web interface 100 . On the login screen 100 , enter login name and password and from
the main menu, select Setup | Downloads | Remote Probe Installer. Click on the Download:
Remote Probe Installer button. You browser will show a download dialog. Save the setup
program to your local hard disk drive.
Install Remote Probe
Please execute the setup program you've just downloaded.
Windows User Account Control Confirmation Request
Confirm the question of the Windows User Account Control with Yes to allow the program to
install. The usual software installation wizard will guide you through the installation process.
Setup Language Selection
64
2011-08-19
Part III: Installing the Software
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.
Remote Probe Setup Wizard Welcome Screen
Please click Next to walk through the wizard.
Setup Wizard License Agreement
After accepting the license agreement, you can choose the folder you wish to install the
software in. We recommend using the default value.
2011-08-19
65
Part III: Installing the Software
Setup Wizard Destination Location
As soon as you click Next, the necessary files will be copied to your disk.
Windows GUI Setup Wizard Install
The PRTG Probe Administrator is shown. Please enter the correct settings in order to connect
with your PRTG core installation. See Remote Probe Setup 1197 section for more information.
Click Ok to continue.
66
2011-08-19
Part III: Installing the Software
Probe Settings in PRTG Probe Administrator
When asked if you want to start the probe service, confirm with Yes. The installation is
completed.
PRTG Probe Administrator Start Service Request
After installation, click Finish.
2011-08-19
67
Part III: Installing the Software
Remote Probe Setup Wizard Finish
Your remote probe is now installed on this computer as Windows service.
More
After you click the Finish button, the PRTG Probe Administrator is shown, allowing you to
configure connections. Please see section Remote Probe Setup 1197 for more information on
how to connect the remote probe with your PRTG core server installation.
68
2011-08-19
Part III: Installing the Software
3.8
Install the Enterprise Console
The Windows GUI Enterprise Console is already included in a PRTG core server installation
You can install additional Enterprise Consoles on other computers.
44
.
Download Windows GUI Enterprise Console from the Web Interface
The version of the Enterprise Console has to fit exactly the PRTG core server version you will
connect to. From the computer you want to install the Enterprise Console on, please connect
to the Ajax 98 web interface. On the login screen 100 of the web interface, enter login name
and password and select the Enterprise Console (Download for Windows) option. You
browser will show a download dialog. Save the setup program to the local hard disk drive.
Install Windows GUI
Please execute the setup program you've just downloaded.
Windows User Account Control Confirmation Request
Confirm the question of the Windows User Account Control with Yes to allow the program to
install. The usual software installation wizard will guide you through the installation process.
Setup Language Selection
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.
2011-08-26
69
Part III: Installing the Software
Windows GUI Setup Wizard Welcome Screen
Please click Next to walk through the wizard.
Setup Wizard License Agreement
After accepting the license agreement, you can choose the folder you wish to install the
software in. We recommend using the default value.
70
2011-08-26
Part III: Installing the Software
Setup Wizard Destination Location
Select which icons will be created. We recommend using the default value.
Windows GUI Setup Wizard Additional Tasks
As soon as you click Next, the necessary files will be copied to your disk.
2011-08-26
71
Part III: Installing the Software
Windows GUI Setup Wizard Install
After installation, click Finish to start the Windows GUI.
Windows GUI Setup Wizard Finish
More
Please see section Windows GUI 1074 for more information on how to use this Graphical User
Interface (GUI).
72
2011-08-26
Part III: Installing the Software
2011-08-26
73
Part III: Installing the Software
3.9
Uninstall PRTG Products
The uninstall process has six steps—regardless of if you are uninstalling an entire PRTG
Network Monitor installation, a single Windows GUI 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 Uninstall PRTG Network Monitor icon, the
Uninstall PRTG Windows GUI icon, or the Uninstall PRTG Remote Probe icon, or open your
Windows Control Panel and choose the respective entry in the Programs section. Depending
on the installed products, not all uninstall programs are available.
Start Menu Icons
Step 2
If asked, confirm the question of the Windows User Account Control with Yes to allow the
program to uninstall. The usual software uninstall wizard will guide you through the uninstall
process.
Windows User Account Control Request
Step 3
Confirm the removal of the software by clicking the Yes button.
74
2011-10-11
Part III: Installing the Software
Uninstall PRTG Network Monitor Step 1
Step 4
Wait while the software is being removed.
Uninstall PRTG Network Monitor Step 2
Step 5
Confirm a system restart by clicking the Yes button.
2011-10-11
75
Part III: Installing the Software
Uninstall PRTG Network Monitor Step 3
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 Network Monitor program folder
as well as the Paessler\PRTG Network Monitor folder in your data path. For more
information where data is stored see Data Storage 1202 section.
76
2011-10-11
Part IV: Understanding Basic Concepts
Part IV
Understanding Basic Concepts
2011-05-17
77
Part IV: Understanding Basic Concepts
4
Understanding Basic Concepts
There are a number of basic concepts that lay the foundation for the functionality and ease
of use of the PRTG Network Monitor. We have made using our software as easy as possible.
Nevertheless, there are some basic principles we would like to explain to you. Please read
this section carefully to make it easier for you to understand how best to use the software.
Understanding Basic Concepts—Topics
§ Architecture
§ Clustering
79
82
§ Object Hierarchy
83
§ Inheritance of Settings
§ Tags
89
§ Dependencies
§ Scheduling
§ Notifying
90
91
92
§ Data Reporting
93
§ User Access Rights
78
87
94
2011-05-17
Part IV: Understanding Basic Concepts
4.1
Architecture
PRTG Network Monitor consists of different parts which can be divided into three main
categories: System parts, control interfaces and basic administration interfaces.
Type
Part of PRTG
Core Server 79
This is the central part of a PRTG installation and includes data
storage, web server, report engine, a notification system, and
more.
System Parts
Probe(s) 80
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.
Ajax Web Interface 98
The Ajax-based web interface is used for configuration of devices
and sensors, as well as the review of monitoring results. Also
system administration and user management are configured here.
User Interfaces
Enterprise Console 1074
A native Windows application (former Windows GUI) as alternative
to the web interface to manage your monitoring. With the
Enterprise Console, you can connect to different independent
PRTG core server installations and review data at a glance!
Smart Phone Apps 1125
Monitor your network on the go with PRTG and the smart phone
apps for iOS and Android.
System Administration
Programs
PRTG Server Administrator 1153
Used to configure basic core server settings, such as
administrator login, web server IPs and port, probe connection
settings, cluster mode, system language, and more.
PRTG Probe Administrator 1170
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
2011-09-27
79
Part IV: Understanding Basic Concepts
§ 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, the current master node is responsible for all of these tasks.
The built-in, fast and secure web server (no additional IIS or Apache is required) supports
HTTP as well as secure HTTPS (via SSL). It serves the web interface when accessed with a
browser and also answers PRTG Application Programming Interface (API) calls (e.g. 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, the sensors created on a device perform the actual monitoring. 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.
PRTG Core Server and Local Probe Monitoring a Local Area Network
80
2011-09-27
Part IV: Understanding Basic Concepts
The actual monitoring is performed by PRTG probe processes which run on one or more
computers. During installation the so-called Local Probe is automatically created by the
system. In a single-probe installation—which is the default setup—all monitoring is
performed by the local probe.
The PRTG core server inside the corporate LAN (bottom right) 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 82 , a cluster probe runs on all nodes. There is an additional so-called
Cluster 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 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 Core/
Probe Health, Cluster Probe Health, Disk Free, and a bandwidth sensor for all installed
network cards. We recommend keeping these sensors, but you can optionally remove all
except the Health 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 sensor's
channels 115 for details.
Additional so-called Remote 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 Remote Probes and Multiple Probes 1193 section. For a video on this please see
More 167 section below.
More
Video Tutorial: There is a video available on the Paessler video tutorials page.
§ http://www.paessler.com/support/video_tutorials
2011-09-27
81
Part IV: Understanding Basic Concepts
4.2
Clustering
A PRTG Cluster consists of two or more installations of PRTG 44 that work together to form a
high availability monitoring system. The objective is to reach true 100% uptime for the
monitoring tool. Using clustering 56 , 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 upgrade for the operating system or PRTG itself.
How a PRTG Cluster Works
A PRTG cluster consists of one Primary Master Node and one or more Failover Nodes. Each
node is simply a full installation of PRTG which could perform the whole monitoring and
alerting on its own. Nodes are connected to each other using two TCP/IP connections. They
communicate in both directions and a single node only needs to connect to one other node
to integrate into the cluster.
During normal operation the Primary Master is used to configure devices and sensors (using
the web interface 98 or Windows GUI 1074 ). The master automatically distributes the
configuration to all other nodes in real time. All nodes are permanently monitoring the
network according to this common configuration and each node stores its results into its
own database. This way also the storage of monitoring results is distributed among the
cluster (the downside of this concept is that monitoring traffic and load on the network is
multiplied by the number of cluster nodes, but this should not be a problem for most usage
scenarios). The user can review the monitoring results by logging into the web interface of
any of the cluster nodes in read only mode. As the monitoring configuration is centrally
managed, it can only be changed on the master node, though.
All devices created on the Cluster Probe are monitored by all nodes in the cluster, so data
from different perspective is available and monitoring for these devices always continues,
also if one of the nodes fails. In case the Primary Master fails, one of the Failover Nodes
takes over the master role and controls the cluster until the master node is back. This
ensures a fail-safe monitoring with gapless data.
If downtimes or threshold breaches are discovered by one or more nodes only one
installation, either the Primary Master or the Failover Master, will send out notifications (via
email, SMS text message, etc.). So, the administrator will not be flooded with notifications
from all cluster nodes in the event of failures.
More
Knowledge Base: What's the Clustering Feature in PRTG 8?
§ http://www.paessler.com/knowledgebase/en/topic/6403
82
2011-08-25
Part IV: Understanding Basic Concepts
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 below it (see section Inheritance of Settings
87 ).
Object Hiearchy in PRTG
2011-09-27
83
Part IV: Understanding Basic Concepts
Root Group
The Root group is the topmost instance in PRTG. It contains all other objects in your setup.
Using the inheritance 87 mechanism, we recommend adjusting the default settings for the
Root group 185 in order for all other objects to inherit them. This makes configuration easier
later on.
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 Multiple Probes and Remote Probes
1193 ). In a cluster, there is an additional Cluster Probe running on all nodes. Devices on the
cluster probe are monitored by all nodes of the cluster, so data from different perspective is
available and monitoring for these devices always continues, also 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
2011-09-27
Part IV: Understanding Basic Concepts
PRTG Device Tree View
Device
To each probe or group, you can add Devices that you want to monitor. Each device in your
PRTG configuration represents a real hardware 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
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.
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
2011-09-27
85
Part IV: Understanding Basic Concepts
§ CPU load of a device
§ Memory load of a device
§ Traffic of one network card
§ One NetFlow device
§ 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:
§ Downtime for a device
§ Traffic in of a bandwidth device (e.g. a router)
§ Traffic out of a bandwidth device (e.g. a router)
§ Traffic sum of a bandwidth device (e.g. a router)
§ WWW traffic of a NetFlow device
§ Mail traffic of a NetFlow device
§ Other traffic of a NetFlow device
§ CPU Load of a device
§ Loading time of a web page
§ Download Bandwidth of a web page
§ Time to first byte of a web page
§ Response time of a Ping request to a device
§ Response time of a Remote Desktop service
§ etc.
86
2011-09-27
Part IV: Understanding Basic Concepts
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 easy—especially for large monitoring setups—certain settings are inherited from the
overlying level. For example, you can change the monitoring interval for all sensors by
editing the interval setting of the topmost Root group (unless no other setting is defined
below).
Settings are Inherited to Child Objects
You can override this inheritance on any level of the hierarchy by setting a different value for
a specific probe, group, device, or sensor. All objects below will inherit these new settings;
not the ones from levels above.
Settings that are inherited among all objects include:
§ Monitoring interval
§ Notification triggers
§ Authentication settings for several systems
§ Compatibility settings (for certain types of sensors)
§ Channel and unit configuration
§ User access rights
§ Tags
89
§ 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 Abc from Xyz. As an
example, the screenshot below shows Windows systems credentials settings after removing
the check mark symbol.
Credentials for Windows Systems
2011-05-17
87
Part IV: Understanding Basic Concepts
Default Values Set in Root Group
For all settings (except passwords) PRTG already includes a set of default values so you can
get started with the software immediately. For example, the following settings will be
inherited by all sensors from the Root group:
§ Default monitoring interval of one minute
§ SNMP version 1 with community string set to public (default values for most devices)
§ Dependency type Use parent
§ etc.
You may need to change some of the default entries as you become used to the interface.
However, these settings should initially suffice for most situations.
Before sensor setup, please review the Root group's settings and set the default values to
suit your setup, including necessary credentials for all kinds of systems in your network you
want to monitor (Windows, Linux, virtual servers, etc.). See section Root Group Settings 185
for more details.
88
2011-05-17
Part IV: Understanding Basic Concepts
4.5
Tags
For every object in your PRTG setup, you can not only name objects, but also define tags in
an object's settings 118 to additionally mark an object as a member of certain categories.
Although there are tags predefined when adding objects 169 you are totally free in the way
you add tags. For example, you could mark all of the bandwidth sensors that are especially
important for you with a tag bandwidth_important. Later, you can view lists of objects with
certain tags, or choose sensors by tag when creating reports 993 . A clever arrangement of
tags can save you a lot of time later. Note: You can change tags for several objects at a time
using the multi-edit 964 function.
Tags Are Inherited
The tags in an object's settings are automatically inherited 87 to all other objects further
down in the hierarchy. So, for example, a device with the tag myExampleTag will
automatically and invisibly inherit this tag to all sensors created on it. This will not be visible
in the sensor's tag settings, but the sensors will appear in the list whenever you search for
myExampleTag. This is useful, for example, when adding sensors by tag in reports 993
settings. This way, to configure your setup for fetching all sensors on a device by tag, you do
not have to tag every single sensor, but it's enough to tag the device. Inheritance for tags
cannot be disabled.
2011-05-17
89
Part IV: Understanding Basic Concepts
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 158 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.
For more information about the dependency settings, please see the settings of the
respective object 118 you want to set a dependency for.
Related Topics
§ Show Dependencies
90
973
2011-05-17
Part IV: Understanding Basic Concepts
4.7
Scheduling
Using schedules, monitoring of an object can be paused 135 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 92 . 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 Settings—Schedules 1041 section.
2011-05-17
91
Part IV: Understanding Basic Concepts
4.8
Notifying
PRTG keeps the administrator or others 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 breach, or similar situations, it can send a notification.
Notifications use various methods by which you can be notified (e.g. email, SMS, pager
message and others). After creating notifications in the system settings, you can select them
on the setting pages for a group, a device, and a sensor. See Notifications 978 section for
more details.
Limits
In a sensor channel's settings 938 you can set limits to change the status of the sensor when
certain limits are breached. This way, you can set e.g. a traffic sensor, which is 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 alarm list shows all sensors that are currently in a Down, Down (Partial), 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 120
section for more details.
Logs
In the Log 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 122 section for more
information.
ToDos
The ToDos list shows items with important system information or action steps to take for the
administrator. Every ToDo should be viewed and acknowledged. Per default, an email is sent
to the administrator for every new ToDo that is created by the system. See ToDos 128 section
for more information.
92
2011-05-17
Part IV: Understanding Basic Concepts
4.9
Data Reporting
With reports you can analyze and review monitoring data for specific time spans. There are
several ways to create data reports in PRTG.
View Historic Data
To get a report for a single sensor, there is a function included to review historic data in
PRTG. It allows you to generate reports and charts for a single sensor's data. See Historic
Data Reports 124 section for more information.
Generate Reports
You can use the sophisticated reports machine included in PRTG to create exhaustive reports
for all monitoring data. See Reports 993 section for more information.
Exporting Data Using the API
You can also export all monitoring raw data to XML or CSV files and generate your own
reports using any third party software. See Using the PRTG API (Application Programming
Interface) 1185 section for more information.
Making Data Available
You can make monitoring data available to others using a special read only user (see User
Access Rights 94 section), or you can create public or semi-public HTML pages with
monitoring data using the Maps feature. See Maps 1010 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 Downloads 1071 section.
More
§ Data Storage 1202
2011-10-11
93
Part IV: Understanding Basic Concepts
4.10 User Access Rights
The default administrator can use the PRTG installation as the only user or can create an
unlimited number of users. Users are organized using an unlimited number of groups (which
also control their security settings). All access rights are defined on group level in the
settings of each object in your PRTG device tree.
There are administrator users, read/write users, and read only users. With these tools, you
can create a rights management that allows you to specify exactly what users will be able to
see and edit. All the security settings as well as further rights management are conducted via
the user groups. This means that group membership controls what a user may do and which
objects he/she sees when logged in. The actual rights for each object can be defined in an
object's settings. There, you can define different rights for each user group. Again, these
settings are inherited.
For more information about defining rights, please see the following sections:
§ System Administration—User Accounts 1060
§ System Administration—User Groups 1064
You can define access rights for each user group in the settings of a probe, group, device, or
sensor. For more information, please see Object Settings 118 section.
For information about connecting PRTG to an existing Active Directory, please see Active
Directory Integration 1183 .
94
2011-09-14
Part IV: Understanding Basic Concepts
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
Settings 222 of each device. Depending on the setting, the sensors created on this device will
use the respective protocol.
In the Outgoing IP Settings of the PRTG Probe Administrator 1172 you can additionally
choose which IPv6 address will be used for outgoing monitoring requests. Note: There is the
same option for IPv4, too.
2011-10-04
95
Part V: Ajax Web Interface—Basic Procedures
Part V
Ajax Web Interface—Basic Procedures
2011-09-14
97
Part V: Ajax Web Interface—Basic Procedures
5
Ajax Web Interface—Basic Procedures
The Ajax-based web interface is your access to PRTG. It is used to configure devices and
sensors, and to set up notifications, as well as review monitoring results and create reports.
This web interface is highly interactive and uses Asynchronous Java Script and XML (AJAX) to
deliver a powerful and easy-to-use user experience. While the user is logged in 100 , the data
on the screen is permanently refreshed (via Ajax calls) so it always shows the current
monitoring results (refresh interval and method can be set 1060 by the user).
The following sections introduce the features and concepts of the Ajax Graphical User
Interface (GUI).
98
2011-09-14
Part V: Ajax Web Interface—Basic Procedures
Ajax Web Interface—Basic Procedures—Topics
§ Login
100
§ General Layout
§ Sensor States
106
112
§ Review Monitoring Data
§ Historic Data Reports
§ Object Settings
§ Alarms
§ Logs
115
124
118
120
122
§ ToDos
128
§ Working with Table Lists
§ Object Selector
132
§ Priority and Favorites
§ Pause
130
134
135
§ Context Menus
136
§ Main Menu Structure
145
Other Ajax Web Interface Sections
§ Ajax Web Interface—Device and Sensor Setup
§ Ajax Web Interface—Advanced Procedures
156
954
Related Topics
§ Enterprise Console 1074
§ Other User Interfaces 1120
2011-09-14
99
Part V: Ajax Web Interface—Basic Procedures
5.1
Login
Once the PRTG core server is installed 44 , 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 Server
Administrator 1153 Windows application on the system PRTG core server is installed on.
Especially when accessing PRTG from the internet you should use an SSL encryped
connection. You can easily switch to SSL using the Yes, switch to SSL button shown on the
welcome screen.
Loading the Web Interface
In a web browser window, please enter the IP address or URL of the system PRTG is installed
on. When using a cluster, please connect to the primary master node. You can also double
click on the PRTG Network Monitor icon on the desktop of the system PRTG is installed on.
Desktop Icon
If you see a certificate warning in your browser, you can usually just confirm it. For more
information please see SSL Certificate Warning 103 .
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 1060 with administrator rights
or with more restricted privileges.
Additionally, there are different GUI versions available.
100
2011-09-19
Part V: Ajax Web Interface—Basic Procedures
PRTG Login Screen
Login as Default Administrator (First Time Login)
When logging in for the first time, login name and password for the default administrator
login are both prtgadmin. You can leave the login name and password fields empty and
click on the Default Login button to log in with these credentials.
Note: After login you should change the default password. To do so, go to Setup | Account
Settings | My Account and specify a new password.
Note: If locked out of the web interface, you can change the credentials for this default user
account any time in the PRTG Server Administrator 1164 Windows application.
Login as PRTG User
If you have received user credentials from your administrator, please enter them here to
login. Also, when using other administrator credentials, please enter them here.
Choose GUI version
Depending on the used browser, different Graphical User Interface (GUI) options are shown:
§ AJAX GUI (All features): The standard interface. We recommend using it whenever
possible. It offers full functionality. Use Google Chrome or Mozilla Firefox for best
performance. In some browsers, the Ajax option is not shown (e.g. not in IE 8 and earlier).
Although you can login using Internet Explorer 9, this interface might not be fully
compatible with Internet Explorer! When using IE 9, please set the security level at least to
Default level Medium-high and make sure you do not use the Compatibility View! For
detailed information, please see More 102 section below.
2011-09-19
101
Part V: Ajax Web Interface—Basic Procedures
§ HTML GUI (Low bandwidth): The HTML GUI (Low bandwidth) 1121 interface is optimized for
slow network connections. 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 (e.g. when using IE8 and earlier).
§ Enterprise Console (Download): Option to download the native Windows interface to the
desktop (former Windows GUI). It has to be installed 1074 on the client computer before use.
The Enterprise Console 1074 provides full functionality; however, for some functions the Ajax
GUI is opened. As an additional feature, the Enterprise Console can view data of several
independent PRTG core installations in a single application. Note: Also when downloading
the Enterprise Console, login name and password (or a Default Login) are required!
Note: Only Google Chrome and Mozilla Firefox are fully compatible with the Ajax GUI. For
more information about Internet Explorer support, please see More 102 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://www.paessler.com/knowledgebase/en/topic/7633
Knowledge Base: How can I access the AJAX web interface of PRTG 8 with Internet Explorer 8?
§ http://www.paessler.com/knowledgebase/en/topic/9483
102
2011-09-19
Part V: Ajax Web Interface—Basic Procedures
5.2
SSL Certificate Warning
If you use PRTG outside your internal LAN, especially when using it on the internet, you
should switch the internal web server to use SSL. After doing so, your browser will show a
certificate warning, as the certificate that comes with PRTG cannot be signed by a valid
authority. Anyway, the connection to your PRTG web server will be secured via SSL, and you
can confirm the claimed security risk. For more information on secure browser connections,
please see the More 102 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
103
103
§ Internet Explorer
§ Other
104
105
Google Chrome
In Google Chrome, click on Proceed anyway every time you call the web interface.
Security Warning in Google Chrome Browser
Mozilla Firefox
In Mozilla Firefox, click on I Understand the Risks and then on the Add Exception... button
. In the appearing window, leave the check mark for Permanently store this exception and
finally click on the Confirm Security Exception button.
2011-08-15
103
Part V: Ajax Web Interface—Basic Procedures
Security Warning in Mozilla Firefox
You only have to go through this procedure once for every Firefox browser and PRTG core
server.
Internet Explorer
In Internet Explorer, click on Continue to this website (not recommended) every time you
call the web interface.
104
2011-08-15
Part V: Ajax Web Interface—Basic Procedures
Security Warning in Internet Explorer
Other
For other browsers, the procedures to confirm the certificate will be similar to the ones
described above.
More
Knowledge Base: Why don't I get an SSL connection to the PRTG web interface?
§ http://www.paessler.com/knowledgebase/en/topic/11813
Knowledge Base: How can I establish a secure web interface connection to PRTG?
§ http://www.paessler.com/knowledgebase/en/topic/273
Knowledge Base: How can I use a trusted SSL certificate with the PRTG web interface?
§ http://www.paessler.com/knowledgebase/en/topic/283
2011-08-15
105
Part V: Ajax Web Interface—Basic Procedures
5.3
General Layout
After logging into the web interface, you will see PRTG's welcome page as default. This page
helps you to add sensors manually, perform an automatic network search, review results,
download the Enterprise Console or smart phone applications, and get further help and
support.
Welcome Screen
Tree View Layout
Click on the Review Results option to display the tree-like device view which will be a
starting point for everyday use.
106
2011-09-21
Part V: Ajax Web Interface—Basic Procedures
PRTG Device Tree View
From top to bottom, the main layout consists of:
§ The global header area
quick search box.
108
with the main menu at the top, the global status bar, and a
§ The page header bar 109 with the page heading containing the name of the current object,
the tabs bar which leads to the content of the current object, and the object's status bar.
§ The page content 110 with information about the current object and all other objects
underneath in the tree hierarchy.
Simply click on an object to see more details about it. In the page heading of the page header
bar 109 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
§ 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).
2011-09-21
107
Part V: Ajax Web Interface—Basic Procedures
These six navigation paths put PRTG's complete functionality at your fingertips. Quite likely
you are already familiar with these techniques from many other websites and web-based user
interfaces.
In the following, the different areas of the web interface are described.
Global Header Area
PRTG's Cluster Info, Main Menu, and Global Status Bar
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 System Administrator 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:
§ Blue Cluster Information Bar
This element is only visible when running PRTG in a cluster. 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 Cluster Status 1066 . 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.
§ Grey Main Menu Bar
Navigating through the web interface is performed using the main menu. Please take a few
minutes to familiarize yourself with all menu items and sub-items. A detailed description
can be found in the Main Menu Structure 145 section.
§ Icons Refresh, Help Center, Logout
With the icons on the right you can reload the current page, open the help center or log the
current user out.
§ 'Breadcrumbs'
Below the main menu, there is always a path shown, leading to the homepage. Use it to go
back to where you came from. It can also help you to orient yourself in case you get lost.
§ White Search Box
To search for any monitoring object, simply enter the name, part of the name, an IP
address, a DNS name or a tag in the search box on the right and hit the enter key. A web
page with all items that fit the search term will be returned—even displaying online help
articles.
108
2011-09-21
Part V: Ajax Web Interface—Basic Procedures
§ Blue Help Box ("Roller Blind")
A context sensitive help text for every page is displayed in the blue roller blind on the
right. There is a ribbon hanging down: Click on the x symbol to roll up the blind and on
the question mark ? symbol to pull it down.
§ Buttons New Alarms, New Log Entries, ToDo(s)
These buttons show the number of new alarms or new log entries since last user login as
well as the number of ToDo(s) that wait to be acknowledged. Click on the respective button
to view the Alarms 120 , Logs 122 , or ToDos 128 .
§ Global Sensor State 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 States 112 section.
Page Header Bar
In the page header under the global header area, you see the name of the current object and
the page content underneath. When displaying a group, aggregated sensor states are shown
in a sensor bar and there is an option to change the tree view.
Note: This documentation refers to the PRTG System Administrator 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.
PRTG Page Header Bar with Heading, Tabs, Group Status Icons, and Tree View Selection
The page header and tabs area consists of the following parts:
§ Page Heading
The first line displays the kind of the current object and the name as page heading. In the
screenshot above, it is the Root group (which contains all objects of your configuration).
§ Tabs
Using the tabs you can navigate to various sub-pages of an object, showing monitoring
data or changing settings. For more information, please see sections Review Sensor Data 115
and Change Device and Sensor Settings 118 .
§ Context Buttons
On the right side there are icons to pause or delete this object, or to add another object. By
clicking on the arrow, you can open the context menu for the currently displayed object
with even more options. For more information, please see Context Menus 136 section.
2011-09-21
109
Part V: Ajax Web Interface—Basic Procedures
§ Sensor Status Bar
This element is only visible when viewing a probe or a group. It is not available when
viewing a device's or sensor's details. The sensor status bar shows the aggregated status
of all sensors for the current object, divided into different sensor states. They show the
number of sensors in the respective state. For example, you can see how many sensors are
in Up, Down, or Warning state. For a detailed description of sensor states, please see
Sensor States 112 section. You can hide sensors that are in a certain state by removing the
check mark symbol in front of the respective sensor symbol. To show them again, re-add
the check mark.
§ Device Tree Zoom
This element is only visible when viewing a probe or a group. It is not available when
viewing a device's or sensor's details. You can select how much space is used to show
devices and sensors. In four steps, you can switch from a very condensed view (small circle)
up to an extra large view (big circle).
§ 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.
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 Health Sensor 275 , 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 Health sensor. In a cluster installation, PRTG also creates a Cluster Probe Device with
a Cluster Probe Health Sensor 271 that monitors the cluster's system health.
For more details about page contents, please see the following sections:
§ Review Monitoring Data
§ Historic Data Reports
§ Object Settings
124
118
§ Compare Sensors
110
115
971
2011-09-21
Part V: Ajax Web Interface—Basic Procedures
More
Knowledge Base: How can I change the width of the devices and group "boxes" shown in the
PRTG 9 device tree?
§ http://www.paessler.com/knowledgebase/en/topic/24963
2011-09-21
111
Part V: Ajax Web Interface—Basic Procedures
5.4
Sensor States
The sensors are the 'heart' of your PRTG installation. With sensors, you can monitor different
aspects of your devices. Using a simple color code, they always show you what is going on
with your devices.
The color of a sensor always shows it's current status. Following, you find a list of states a
sensor can show.
112
2011-11-03
Part V: Ajax Web Interface—Basic Procedures
Sensor
2011-11-03
Color
Status Name
Meaning
Red
Down
PRTG is not able to reach the device or the
sensor has reached an error state. Please see
Sensor Warning and Down Behavior 114 below
for more information. Another reason for this
state can be a down limit set in a sensor's
Sensor Channels Settings 938 .
Red/Green
Down (Partial)
In a cluster, at least one node reports this
sensor as Down, while at least one other node
reports the same sensor as Up.
Bright-Red
Down
(Acknowledged)
The sensor is Down and the status was
acknowledged by a PRTG user, applying the
Acknowledge Alarm function. This can be
helpful to mark that an alarm has already been
attended to. For acknowledged alarms no
more notifications 978 are sent. To set this
sensor status, right-click on a sensor in a
Down status and from the context menu 136 ,
select Acknowledge Alarm.... Then enter a
comment and click OK.
Yellow
Warning
There was an error reading the sensor, but
PRTG will try again. The sensor may soon
change to a down status. Please see Sensor
Warning and Down Behavior 114 below for
more information. Another reason for this state
can be a warning limit set in a sensor's Sensor
Channels Settings 938 .
Green
Up
The last check was okay and the sensor
receives data.
Blue
Paused
The sensor is currently paused (for a certain
time, or unlimitedly).
Orange
Unusual
The sensor reports unusual values for this
weekday and time of day. The unusual
detection is based on the historic average data
and can be set in the system administration 1044
.
Black (Gray)
Unknown
The sensor has not been checked yet by PRTG
or there is an error in (network)
communication, likely on the probe system. If
sensors show this state persistently, a PRTG
restart may be necessary.
113
Part V: Ajax Web Interface—Basic Procedures
Sensor Warning and Down Behavior
The Down status symbolizes that something is wrong with a monitored device. There can be
various reasons for a down status, e.g. an interruption in the physical connection to the
device, an internet connection outage, or simply a crashed server.
After a failed request, PRTG tries to reach the device again before setting a sensor to Down
state (this is true for almost all types of sensors):
1. If a request to a device fails for the first time, the sensor is set to Warning state. PRTG
repeats the request and tries to re-scan the device immediately.
2. If also the second request fails, the sensor is set to Down state until the device is
reachable again. PRTG tries to reach the device with every scanning interval.
This procedure gives devices and services the chance to recover from a momentary overload
and prevents false alarms. Still, you are informed promptly about any failures occurring.
Note: The described behavior does not apply to a Warning or Down status that is activated
due to a warning or down limit set in a sensor's Sensor Channels Settings 938 .
114
2011-11-03
Part V: Ajax Web Interface—Basic Procedures
5.5
Review Monitoring Data
Pages of probes, groups, device, and sensors have a tab-like interface. Using the tabs you
can navigate through various sub-pages of an object in order to show your network's status,
view monitoring results, or change settings.
Tabs Bar on Sensor Pages
Overview
The Overview tab shows an overview of the currently selected object and of its sensors. The
pages share a common layout, but include different elements, depending on the kind of
object you're looking at:
§ For probes and groups, the Overview tab shows a tree with devices and sensors, as well as
summary graphs for different time spans of the current probe or group.
§ 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.
§ 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.
Device Overview Tab for Probe Device with Overview, Sensor Table, GeoMap, and Mini Graphs
Live Data and Data By x Days
Select one of the tabs Live Data (available for sensors only), 2 days, 30 days, or 365 days to
display an object's monitoring data live (sensors only), or for different time spans and in
more or less detail. Note: The days mentioned here are the default setting. You can change
the detail of the different graphs any time in the PRTG System Administrator program. See
section PRTG Server Administrator 1161 (Memory Usage) for more details.
2011-09-06
115
Part V: Ajax Web Interface—Basic Procedures
Group 2 Days Tab for Root Group with Group Graph and Sensor Mini Graphs
For probes, groups, and devices, each of the tabs shows a summary graph for the current
object and mini graphs (2 days) for all sensors on this object, as well as a data table for the
current object. There are never more than 50 mini graphs displayed for performance reasons.
Sensor Live Data Tab for a Traffic Sensor With Cluster Member Selection Bar
For sensors, the tabs show a graph and data table of the selected sensor. When viewing data
of a sensor running on a cluster probe, you can additionally select if you want to show the
data of all nodes, or of one specific node only. Please use the Select Cluster Member bar
below the tabs. Note: Multi-node graphs are never displayed filled here, but with single lines
only. However, historic data reports can have filled multi-node graphs.
Next to every graph, you will find two small icons. Using them, you can do the following:
116
2011-09-06
Part V: Ajax Web Interface—Basic Procedures
§ Download the graph: This will show a PNG file of the graph in a new browser window. You
can then save or copy it for later use.
§ Zoom graph in new window: This will open a larger version of the graph in a new browser
window.
Toplists
The Toplists tab is available for xFlow and Packet Sniffer sensors
Toplists 955 .
237
only. Please see section
Historic Data
The Historic Data tab is available for sensors only. Please see section Historic Data Reports
124 .
Sensors Lists
Viewing lists of sensors is a great way to keep an eye on your network's status, as 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; there is a sensor cross reference, and many more.
Sensor lists are available from the main menu. Click the Sensors entry to show a table list of
all sensors. In the table list 130 appearing, you can re-sort the items by clicking on the
column's header items. Hover to show other menu options. For detailed information about
the available options, please see Main Menu Structure 147 (Sensors) section.
Alarms
The Alarms tab is not available for sensors, but for probes, groups, and devices only. Please
see section Alarms 120 .
Log
Please see section Logs
122
.
Related Topics
§ Object Settings
118
§ Compare Sensors
2011-09-06
971
117
Part V: Ajax Web Interface—Basic Procedures
5.6
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.
Tabs Bar on Sensor Pages
Device Tree Management
The Management tab is available when viewing probes or groups. After clicking this tab you
can move devices and sensors right within the tree view. If moving is not possible the web
interface will start a clone process automatically.
For more information, please see Manage Device Tree
183
section.
General Settings
In the Settings 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:
§ Probe Settings
196
§ Group Settings
207
§ Device Settings
222
§ Sensor Settings
236
Note: The available setting options are different for each sensor, but always the same for
probes, groups, and devices.
Notifications Settings
In the Notifications 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 Notifications Settings
943
section.
Channels Settings
The Channels tab is available for sensors only. In the channel settings you can define how
the data from the sensor's different channels are to be displayed in graphs and tables.
Additionally, the channel data can affect the sensor's status. Use the limit settings to achieve
this.
118
2011-09-07
Part V: Ajax Web Interface—Basic Procedures
For more information, please see Sensor Channels Settings
938
section.
Comments
In the Comments 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 History 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.
Related Topics
§ General Layout
106
§ Review Monitoring Data
§ Toplists
2011-09-07
115
955
119
Part V: Ajax Web Interface—Basic Procedures
5.7
Alarms
The Alarm list shows all sensors that are currently in a Down, Down (Partial), Down
(Acknowledged), Warning, or Unusual status. Sensors in other states (e.g. Up, Paused, or
Unknown) do not appear here. This is useful to keep track of all irregularities in your
network.
In the table list, you can re-sort the items by clicking on the column's header items.
Alarms List
There are two possibilities to call the alarms list: Either you click on the Alarms tab on the
detail page of a probe, group, or device (not available for sensors), or you choose the Alarms
entry in the main menu.
Alarms (Object Tab)
Pages of probes, groups, device, and sensors have a tab-like interface. Using the tabs you
can navigate through various sub-pages of an object in order to show your network's status,
view monitoring results, or change settings.
Tabs Bar on Object Pages
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 (Partial), 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 149 . The tab is not available on a
sensor's detail page.
Alarms (Main Menu)
Click the Alarms entry from the main menu 149 to show a table list of all sensors in your
configuration that currently show a Down, Down (Partial), Down (Acknowledged), Warning,
or Unusual status. Hover the Alarms entry and select another option to only show a subset
of sensors in certain states. Choose between:
120
2011-10-12
Part V: Ajax Web Interface—Basic Procedures
§ All
Shows a list of all sensors that currently show a Down, Down (Partial), Down
(Acknowledged), Warning, or Unusual status.
§ Errors only
Shows a list of all sensors that currently show a Down, Down (Partial), or Down
(Acknowledged) status.
§ Warnings only
Shows a list of all sensors that currently show a Warning status.
§ Unusuals only
Shows a list of all sensors that currently show an Unusual status.
Acknowledge Alarm
An acknowledged alarm will not show up in the alarms list any more and will not trigger 943
any more notifications 978 . In order to acknowledge an alarm, right-click on the respective
sensor in a Down status that causes the alarm, and from the context menu 136 , select
Acknowledge Alarm.... Enter a comment that will be displayed next to the sensor's status
and click OK.
More
Knowledge Base: Which audible notifications are available in PRTG 9? Can I change the
default sound?
§ http://www.paessler.com/knowledgebase/en/topic/26303
2011-10-12
121
Part V: Ajax Web Interface—Basic Procedures
5.8
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 with Table Lists 130 section for more information.
Logs List
There are two possibilities to call the logs list: Either you click on the Log tab on the detail
page of a probe, group, device, or sensor, or you choose the Logs entry in the main menu.
Log (Object Tab)
Pages of probes, groups, device, and sensors have a tab-like interface. Using the tabs you
can navigate through various sub-pages of an object in order to show your network's status,
view monitoring results, or change settings.
Tabs Bar on Object Pages
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 subset of the entries available via the Logs | All option in main menu 150
.
Logs (Main Menu)
Click the Logs entry from the main menu 150 to show a table list of all log entries in your
configuration. Hover the Logs entry and select another option to only show a subset of
entries for certain objects for certain kind of entries. Choose between:
§ All
Show log information for all objects in your configuration, newest first.
§ By Group ›
Show 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.
122
2010-11-09
Part V: Ajax Web Interface—Basic Procedures
§ Status Changes ›
Show 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 Status field only. Select
between Up & Down (shows entries with either Up or Down in the Status field), Down,
Warning, Unusual, Up, Paused/Resumed (shows entries with either Paused or Resumed
in the Status field), or Acknowledged Alarms.
§ System Events ›
Show log information regarding certain system event types only. Hover to show other menu
items. Select between the following event types: Probe Related, Cluster Related, AutoDiscovery, Notifications, or Status Messages.
2010-11-09
123
Part V: Ajax Web Interface—Basic Procedures
5.9
Historic Data Reports
For quick reporting on monitoring data, use historic data reports as an alternative to the
exhaustive reports 993 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 Historic Data tab on a sensor's detail page, or you choose Sensors | View Historic Data
from the main menu.
Historic Data (Sensor Tab)
Pages of probes, groups, device, and sensors have a tab-like interface. Using the tabs you
can navigate through various sub-pages of an object in order to show your network's status,
view monitoring results, or change settings.
Tabs Bar on Sensor Pages
The Historic Data tab is available for sensors only (not for probes, groups, or devices). When
calling the historic data reports via this tab, there is no sensor selection available, as you've
already determined which sensor you would like to create a report for.
Historic Data Tab of a Ping Sensor
Historic Monitoring Data (Sensors Menu)
When calling the historic data reports via the View Historic Data entry from the Sensors
entry in the main menu, an additional option is available, enabling you to choose the sensor
you want to create a report for.
124
2011-09-07
Part V: Ajax Web Interface—Basic Procedures
View Historic Data Function Called From Main Menu
Historic Data Reports Settings
Review or Download Historic Sensor Data
Sensor
This field is only visible if you called this function via the main
menu. Select the sensor you would like to create the report for:
Click on the reading-glass symbol to open the object selector. For
more information, please see section Object Selector 132 .
Start
Enter the start date and time of the data you want to review.
End
Enter the end date and time of the data you want to review.
Quick Range
In this section several links are provided for a faster selection of
start and end date. Click on any of these links to change the Start
and End values above. Choose between:
§ 1 Day, 2 Days, 7 Days, or 14 Days: Set the date range to the
respective day(s) and use the current time of day.
§ Today, Yesterday, Last Week, Last Month, 2 Months, 6
Months, 12 Months: Set the date range to the last matching
period, starting 00:00, ending 23:59.
2011-09-07
125
Part V: Ajax Web Interface—Basic Procedures
Review or Download Historic Sensor Data
Average Interval
With this option, you can activate and set up averaging. Select an
interval for which the average value should be calculated. You can
choose between No Interval (no averaging will be performed), a
few seconds, minutes, hours, or a whole day (24 Hours). A smaller
interval will result 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
Automatic Averaging 127 below.
Cluster Node
This field is only visible if the sensor is running on a cluster
probe.Select the cluster node's data that will be used for the
report. Choose between:
§ All nodes: Include the data of all cluster nodes in the report.
§ [Several specific nodes]: Use a specific node's data for the
report. The nodes shown are specific to your setup.
File Format
Select the output format for the report. Choose between:
§ HTML web page: Display the result directly as HTML web page.
This is also a good option to check results before exporting to
another file format.
§ XML file: Export the data as Extensible Markup Language (XML)
file. Usually, you browser will show a download dialog.
§ CSV file: Export the data as Comma Seperated Values (CSV) file,
for example, for import in Microsoft Excel. Usually, you browser
will show a download dialog.
Include Percentiles
Percentile Results
Select if percentiles will be shown in the report. Choose between:
§ Off: No percentiles will be calculated.
§ On: Percentiles will be enabled in the report. In the overview
table, additional values will be displayed with averages/sums for
each sensor channel. Please define additional settings below.
For more information about percentiles, please see section
Calculating Percentiles 1203 .
Percentile
126
This field is only visible if percentile results are enabled above.
Enter which percentile you would like to calculate. Please enter an
integer value.
2011-09-07
Part V: Ajax Web Interface—Basic Procedures
Include Percentiles
Percentile Average
This field is only visible if percentile results are enabled above.
Enter the averaging interval in seconds that will be used for
percentile calculation. Please enter an integer value.
Percentile Mode
This field is only visible if percentile results are enabled above.
Choose between:
§ Discrete: Chooses the next smaller discrete value.
§ Continuous: Interpolates between discrete values.
Click on Start to start the generation of a historic data report.
Automatic Averaging
For performance reasons, PRTG automatically averages monitoring data when calculating
data for large time spans. Data is then averaged regardless of the selected average interval.
Time Span in Report
Minimum Level of Detail (Average
Interval)
Up to 40 days
Any
40 to 500 days
60 minutes/1 hour or larger
A report for a time span of more than 500 days is not possible. If you try to set a larger time
span, it will be reduced to 365 days automatically.
Related Topics
§ Review Monitoring Data
§ Reports
2011-09-07
115
993
127
Part V: Ajax Web Interface—Basic Procedures
5.10 ToDos
The ToDos list shows items with important system information or action steps to take for the
administrator.
New ToDos are created when:
§ A new device or sensor has been created by the auto-discovery process and should be
acknowledged by the user
§ 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, etc.
ToDos List
Every ToDo should be viewed and acknowledged. By default, an email is sent to the
administrator for every new ToDo that is created by the system. This can be changed in the
system administration 1044 (Email Options).
ToDos (Main Menu)
Click to show all ToDos with important system information or action steps to take for the
administrator. In the table list appearing, you can filter the items by using the respective
options 130 . Hover to show other menu items. Choose between:
§ All
Shows all ToDos with important system information for the administrator.
§ Open ToDos
Shows all open ToDos, filtered by certain system event types. Hover to show other menu
items. Select between the following event types: Report Related, Auto-Discovery Related,
Probe Related, Cluster Related, System Errors, and New Software Version.
§ Acknowledged ToDos
Shows all already acknowledged ToDos, filtered by certain system event types. Hover to
show other menu items. Select between the following event types: Report Related, AutoDiscovery Related, Probe Related, Cluster Related, System Errors, and New Software
Version.
128
2010-11-09
Part V: Ajax Web Interface—Basic Procedures
§ Acknowledge all ToDos
This option acknowledges all open ToDos. A warning popup is shown, asking you to
confirm this action.
2010-11-09
129
Part V: Ajax Web Interface—Basic Procedures
5.11 Working with Table Lists
Throughout the web interface often you will see table lists of items, e.g. sensor or device
lists. Table lists are also available in the Overview tab of Libraries 980 , Maps 1010 , Reports 993 ,
Notifications 978 , and Schedules 1041 , as well as in Logs 122 and ToDos 128 . All these provide
common functionality.
Example of a Table List
130
2011-10-21
Part V: Ajax Web Interface—Basic Procedures
Feature
Display
What it does
Paging
The content of a table is displayed on several
pages. Click on the arrow symbols at the
beginning or the end of a list to view other
pages, or to jump to the beginning or the end
of the list.
New window
Click on the window symbol at the beginning or
the end of a list to open the table in a new
window.
Date Range
When viewing log lists (not available in other
lists), hover the Date Range option at the
beginning of the list to select the time span you
want to show log entries for. Choose between
Today, Yesterday, and several other time
spans. Choose Unlimited to disable this filter
again.
Item Count
Hover the Item Count option at the beginning
of the list to select how many rows are shown
on each page. Choose between 50, 100, and
500.
Sorting
Click on the column headers to sort lists by the
respective column. You can click on all blue
words to sort, for example, by Status, Last
Value, Priority, and more. The available options
vary depending on the type of list.
Show XML
Click on the XML option at the end of a list to
download the current page in XML format. Your
browser will usually show a download dialog.
Related Topics
§ Multi-Edit Lists
2011-10-21
964
131
Part V: Ajax Web Interface—Basic Procedures
5.12 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.
Object Selector
Step 1: Navigate Device Tree
On the left hand side, you see a device tree specific to your setup. In the Select using Device
Tree tab you can browse the device tree. Click on an object to view its details on the right
hand side.
Click on the By Name/Group/Device/Tag tab to search for objects by sensor name, group
name, device name, or by tag. Select the kind of object you want to search for and enter a
few letters into the Search String box. This may be a substring only. The resulting objects
will be displayed on the right side immediately. Hover an object on the right side to view its
parent. Choose between the following search methods:
§ By Name: Search for all object names. Shows matching probes, groups, devices, and
sensors.
§ By Group: Search for probe and group names. Shows matching groups and all devices and
sensors for which a matching probe or group is the direct parent device.
§ By Device: Search for device names. Shows matching devices and all sensors for which a
matching device is the parent device.
§ By Tag: Search for tags. Shows all matching objects. Tags can be inherited. See Tags
section for more details.
132
89
2011-10-11
Part V: Ajax Web Interface—Basic Procedures
Step 2: Select an Object
If you have selected a device on the left hand side, you will see the sensors on this device
here, on the right hand side. For sensors, also the sensor type is shown.
Select an object and click on the OK button.
2011-10-11
133
Part V: Ajax Web Interface—Basic Procedures
5.13 Priority and Favorites
You can set priorities for all objects in your setup as well as mark devices or sensors as
favorites. Both settings affect how your objects will be displayed. Note: Settings for priority
and favorites are stored for the entire installation; they are not user specific.
Priority for All Objects
The priority setting will affect in which order your objects will be displayed when viewing
lists. Objects with a higher priority are listed first, others underneath, depending on their
own priority.
To change priority settings, right click on an object to open the context menu 136 and select
Priority. You can now choose between 5 stars ***** (top priority) and one star * (lowest
priority). By default, all objects are set to medium priority (3 stars ***).
Priority Context Menu
Favorites for Devices and Sensors
To call a list of all your favorite devices or sensors, select Devices | Favorite Devices or
Sensors | Favorite Sensors from the main menu. These lists are sorted by priority as well.
You can mark any device or sensor as favorite to add it to the favorite list. Right click on it to
open the context menu 136 . Select Priority/Favorite | Add to Favorites. A small flag symbol
will be added next to the object's name.
Priority/Favorites Context Menu
134
2011-10-11
Part V: Ajax Web Interface—Basic Procedures
5.14 Pause
While a sensor is paused, it will not collect any monitoring data, will not change its status 112
, and will not trigger any notifications 92 . You can pause monitoring for every object by
selecting Pause from the context menu 136 of a probe, a group, a device, or a sensor. All
sensors on this object will then be paused. You can choose Pause Indefinitely, or select a
time after which monitoring will be resumed automatically, such as 5 or 15 minutes, 1 or 3
hours, 1 day, or Until a certain date.
Note: When selecting the Pause symbol from an object's hover popup
multi-edit 964 , the object(s) will be paused indefinitely until resumed.
144
or while using
When selecting a pause option, you are prompted to enter a message. This will be shown in
the status message of the object as long as it is paused. Confirm with OK to pause the
object; click Cancel to not pause it.
PRTG Pause Message Prompt
Inheritance and Resume
If you pause monitoring for an object in the device tree 106 , all child objects underneath will
be paused as well. For example, when pausing a group, all sensors on all devices in it will
also be paused. Once an object is paused, you can resume monitoring any time by selecting
Resume from the context menu 136 . However, you cannot resume monitoring for single child
objects that are paused by a parent object, but only for the object you originally set to
pause. Note: Also after a restart of PRTG, a pause status will be kept.
2011-08-25
135
Part V: Ajax Web Interface—Basic Procedures
5.15 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 145 or the hover popup 144 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 while rightclicking. You will then see your browser's instead of the PRTG menu.
The content of the PRTG context menu varies, depending on the type of object you have
selected. Please see the following screen shots for an overview of the available options:
§ Probe Context Menu
136
§ Group Context Menu
138
§ Device Context Menu
140
§ Sensor Context Menu
142
Probe Context Menu
Context Menu
136
2011-09-28
Part V: Ajax Web Interface—Basic Procedures
Edit ›
Context Menu
Move ›
Context Menu
Pause ›
Context Menu
Priority ›
Context Menu
2011-09-28
137
Part V: Ajax Web Interface—Basic Procedures
Historic Data ›
Context Menu
Group Context Menu
Note: The context menu of the Root group is special and differs from the other groups'
menu.
Context Menu
Edit ›
Context Menu
138
2011-09-28
Part V: Ajax Web Interface—Basic Procedures
Move ›
Context Menu
Pause ›
Context Menu
Priority ›
Context Menu
Historic Data ›
Context Menu
2011-09-28
139
Part V: Ajax Web Interface—Basic Procedures
Device Context Menu
Context Menu
Edit ›
Context Menu
Move ›
Context Menu
140
2011-09-28
Part V: Ajax Web Interface—Basic Procedures
Pause ›
Context Menu
Priority/Favorite ›
Context Menu
Historic Data ›
Context Menu
Device Tools ›
Context Menu
2011-09-28
141
Part V: Ajax Web Interface—Basic Procedures
Sensor Context Menu
Context Menu
Edit ›
Context Menu
Acknowledge Alarm ›
Move ›
Context Menu
142
2011-09-28
Part V: Ajax Web Interface—Basic Procedures
Pause ›
Context Menu
Priority/Favorite ›
Context Menu
Historic Data ›
Context Menu
2011-09-28
143
Part V: Ajax Web Interface—Basic Procedures
5.16 Hover Popup
Whenever you rest the mouse pointer for a second over an object's icon in the device tree 106 ,
a hover popup window will appear, showing details about this object. It contains information
from the object's overview tab 115 , as well as several graphs. The exact information provided
depends on the kind of object you are hovering.
Hover Menu Example: Ping Sensor
Note: The hover popup does only appear if your browser is the currently focused window on
your desktop. It disappears with every (automatic) page refresh. Hover popups are only
available for definite objects, not for cumulated sensor icons showing names like 12 Sensors
or similar.
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 136 which is shown when right-clicking it.
144
2011-08-25
Part V: Ajax Web Interface—Basic Procedures
5.17 Main Menu Structure
Using the main menu, you can access all functions of PRTG. Following, the most important
menu items are described. Often, you can either click on an item directly, or hover it to show
more items.
Note: This documentation refers to the PRTG System Administrator 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
145
§ Devices
146
§ Libraries
§ Sensors
§ Alarms
§ Maps
147
149
150
§ Reports
§ Logs
147
150
150
§ ToDos
§ Setup
151
151
§ Refresh (Arrows Symbol)
§ Help Center (? Symbol)
§ Logout (Off Symbol)
§ Search Box
152
152
153
153
Home
Click to open the user's homepage. The default setting is PRTG's welcome page. The
homepage can be changed in the user's account settings 1028 . Hover to show other menu
items.
§ Dashboard 1 – Dashboard 4
The dashboards provide different preset overviews with the status of your sensors. Choose
the one that fits your needs. Dashboard 4 is optimized for mobile access. It is opened in a
new window and includes no navigation in order to provide as much space as possible.
Note: Dashboards are not customizable. You can create your own overview pages using
the Maps 1010 feature.
2011-09-27
145
Part V: Ajax Web Interface—Basic Procedures
§ Switch Cluster Node ›
This option is only available if PRTG runs in Clustering 82 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 and you will leave the current node and connect to the other.
§ Sitemap
The sitemap 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 to HTML Interface
This switches to the HTML GUI 1121 optimized for low bandwidth and mobile devices. Less
scripting is used for more compatibility. However, this is a read-only interface.
§ Welcome to PRTG
Shows the welcome screen which leads you to the major sections of the web interface.
§ Make This My Homepage
Change the page that is loaded when you click on the Home button in the main menu.
Select this menu item on any page and its URL will be set as the current user's homepage
immediately. This setting is user sensitive. The default homepage is /welcome.htm. You
can change this setting any time by clicking on this menu item again, or by changing the
Homepage URL in the My Account 1028 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.
§ Group View ›
Shows 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 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 ›
Shows 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 Favorite Devices to show a list of all
devices marked as Favorite 134 . Note: To mark any device as a favorite device, select
Priority/Favorite | Toggle Favorite from its context menu. 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. In
the table list 130 appearing, you can re-sort the items by clicking on the column's header
items.
§ Dependencies ›
Shows an overview of the dependencies configured for the objects in your setup. Hover the
menu item 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.
146
2011-09-27
Part V: Ajax Web Interface—Basic Procedures
§ Add Group
Start an assistant which guides you through the process of adding a new group to your
setup. For more information, please see section Create Objects Manually 169 . Tip: You can
create new groups much faster by choosing Add Group... from a probe's or group's context
menu!
§ Add Auto-Discovery Group
Start an assistant which guides you through the process of adding a new auto-discovery
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 the Auto-Discovery 158 Tip: You can create new
groups much faster by choosing Add Auto-Discovery Group... from a probe's or group's
context menu!
§ Add Device
Start an assistant which guides you through the process of adding a new device to an
existing group. During the process, you can choose if PRTG should run an auto-discover for
the new device in order to add sensors automatically. For more information, please see
section Create Objects Manually 169 . Tip: You can create new devices much faster by
choosing Add Device... from a group's context menu!
Libraries
Click to call the Libraries feature where you can view or add custom views of your network's
status and monitoring data. For more information, please see Libraries 980 section. Hover to
show other menu items.
§ All
Calls the Libraries feature where you can view or add custom device tree views of your
network's status and monitoring data.
§ Add Library
Lets you directly add
983
a new library.
§ Select Library ›
Show existing libraries. Hover to show other menu items. Follow the menu path (it is
specific to your setup) to select a library.
Sensors
Click to show a table list of all sensors. In the table list appearing, you can re-sort the items
by clicking on the column's header items. Hover to show other menu items.
2011-09-27
147
Part V: Ajax Web Interface—Basic Procedures
§ All
Shows a table list of all sensors. In the table list appearing, you can re-sort the items by
clicking on the column's header items.
§ Add Sensor
Start an assistant which guides you through the process of adding a new sensor to an
existing device. For more information, please see section Add a Sensor 182 . During the
process, you can also choose to create a new device. This will bring you to the "Add Device"
assistant you can call from the "Devices" menu directly.
§ Favorite Sensors
Shows a table list of all sensors marked as Favorite 134 . Note: To mark any sensor as a
favorite sensor, select Priority/Favorite | Add to Favorites from its context menu.
§ Top 10 Lists ›
This is an option to show a dashboard view with different Top 10 lists regarding best/
worst uptime, Ping, bandwidth usage, website response times, memory usage, and system
uptime. Click to show Top 10 lists out of all sensors. Hover to show other menu items.
Follow the menu path (it is specific to your setup) to view Top 10 lists out of a specific
probe or group only. Note: The sensors will be selected by default tags.
§ By Current Value ›
This is an option to show a filtered sensor list. Hover to show other menu items. Follow the
menu path to view table lists 130 of Fastest or Slowest Ping, Port, Webpages, IMAP/
POP3/SMTP, or FTP sensors as well as Most Used or Least Used Bandwidth, CPU, Disk,
or Memory sensors. Note: The sensors will be selected by default tags.
§ By Current Status ›
This is an option to show a filtered sensor list. Hover to show other menu items. Follow the
menu path to view table lists 917 of all sensors in a certain state. Select between status Up,
Warning, Down, Down (Partial), Down (Acknowledged), Unusual, Paused, and Unknown
. For more information about sensor states, please see Sensor States 112 section.
§ By Uptime/Downtime ›
This is an option to show a filtered sensor list. Hover to show other menu items. Follow the
menu path to view table lists 130 of all sensors sorted by their up- or downtime. Select
between Best Uptime (%), Highest Uptime (Time), Worst Downtime (%), and Highest
Downtime (Time).
§ By Group ›
This is an option to show a filtered sensor list. Hover to show other menu items. Follow the
menu path (it is specific to your setup) to view a sensor table list 130 of a specific probe or
group only.
148
2011-09-27
Part V: Ajax Web Interface—Basic Procedures
§ By Type ›
This is an option to show a filtered sensor list. Hover to show other menu items. Follow the
menu path (it is specific to your setup) to view a sensor table list 130 containing only
sensors of one specific sensor type.
§ By Tag ›
This is an option to show a filtered sensor list. Hover to show other menu items. Follow the
alphabetical menu path (it is specific to your setup) to see available tags. Select a tag view
a table list 130 containing only sensors marked with this tag.
§ Cross Reference ›
The cross reference shows information about all sensors including the set interval, access
rights, notification trigger settings, schedule, and dependency. Click to show a sensor
cross reference for all sensors. Hover to show other menu items. Follow the menu path (it
is specific to your setup) to view cross reference information for sensors in a specific probe
or group only.
§ Compare Sensors
Calls a function to compare graphs of two monitoring objects. For more information, please
see Compare Sensors 971 section.
§ View Historic Data
Calls a function for quick generation of sensor data reports. For more information, please
see Historic Data Reports 124 section.
Alarms
Click to show a all sensors that currently show a Down, Down (Partial), Warning, or
Unusual status. In the table list 130 appearing, you can re-sort the items by clicking on the
column's header items. Hover to show other menu items.
§ All
Shows a list of all sensors that currently show a Down, Down (Partial), Down
(Acknowledged), Warning, or Unusual status.
§ Errors only
Shows a list of all sensors that currently show a Down, Down (Partial), or Down
(Acknowledged) status.
§ Warnings only
Shows a list of all sensors that currently show a Warning status.
§ Unusuals only
Shows a list of all sensors that currently show an Unusual status.
2011-09-27
149
Part V: Ajax Web Interface—Basic Procedures
Maps
Click to call the Maps feature where you can view or add custom views of your network's
status and monitoring data. For more information, please see Maps 1010 section. Hover to
show other menu items.
§ All
Calls the Maps feature where you can view or add custom views of your network's status
and monitoring data.
§ Add Map
Lets you directly add 1013 a new map.
§ Select Map ›
Show existing maps. Hover to show other menu items. Follow the menu path (it is specific
to your setup) to select a map.
Reports
Click to call the Reports feature where you can view or add reports of your monitoring data.
For more information, please see Reports 993 section. Hover to show other menu items.
§ All
Calls the Reports feature where you can view or add reports of your monitoring data.
§ Add Report
Lets you directly add a new report.
§ Select Report ›
Show existing reports. Hover to show other menu items. Follow the menu path (it is
specific to your setup) to select a report.
Logs
Click to show log information for all objects in your configuration, newest first. In the table
list 130 appearing, you can filter the items by using the respective options 130 . Hover to show
other menu items. For more information, please see Logs 122 section.
§ All
Show log information for all objects in your configuration, newest first.
§ By Group ›
Show 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.
150
2011-09-27
Part V: Ajax Web Interface—Basic Procedures
§ Status Changes ›
Show 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 Status field only. Select
between Up & Down (shows entries with either Up or Down in the Status field), Down,
Warning, Unusual, Up, Paused/Resumed (shows entries with either Paused or Resumed
in the Status field), or Acknowledged Alarms.
§ System Events ›
Show log information regarding certain system event types only. Hover to show other menu
items. Select between the following event types: Probe Related, Cluster Related, AutoDiscovery, Notifications, or Status Messages.
ToDos
Click to show all ToDos with important system information or action steps to take for the
administrator. Every ToDo should be viewed and acknowledged. In the table list 130
appearing, you can filter the items by using the respective options 130 . Hover to show other
menu items. For more information, please see ToDos 128 section.
§ All
Shows all ToDos with important system information for the administrator.
§ Open ToDos
Shows all open ToDos, filtered by certain system event types. Hover to show other menu
items. Select between the following event types: Report Related, Auto-Discovery Related,
Probe Related, Cluster Related, System Errors, and New Software Version.
§ Acknowledged ToDos
Shows all already acknowledged ToDos, filtered by certain system event types. Hover to
show other menu items. Select between the following event types: Report Related, AutoDiscovery Related, Probe Related, Cluster Related, System Errors, and New Software
Version.
§ Acknowledge all ToDos
This option acknowledges all open ToDos. A warning popup is shown, asking you to
confirm this action.
Setup
Click to show the setup page. Hover to show other menu items. For more information, please
see Setup 1026 section.
2011-09-27
151
Part V: Ajax Web Interface—Basic Procedures
§ Overview
Shows the setup page.
§ Account Settings ›
Hover to show menu items of the account settings. Select between: My Account 1028 ,
Notifications 1032 , and Schedules 1041 .
§ System Administration ›
Hover to show menu items of the system administration settings. Select between: System
& Website 1044 , Notification Delivery 1051 , Probes 1056 , Cluster 1058 , User Accounts 1060 , and
User Groups 1064 .
§ PRTG Status ›
Hover to show menu items of the PRTG status. Select between: System Status 1066 , Cluster
Status 1066 , and Activation Status 1067 .
§ Downloads
Shows additional downloads for PRTG. Select between: PRTG Enterprise Console 1070 , Apps
for iOS & Android 1070 , Remote Probe Installer 1070 , and PRTG Add-Ons 1070 .
§ PRTG API
Show the API 1185 documentation for your installation.
§ Software Auto-Update
Show the update status 1068 of your PRTG installation. On this page, you can also download
and install available updates.
§ Enter License Key
Shows help on how to enter a license key
59
.
Refresh (Arrows Symbol)
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. During the refresh process, this symbol flashes.
Help Center (? Symbol)
Shows the help center which supports you if you have any questions regarding your PRTG
setup.
152
2011-09-27
Part V: Ajax Web Interface—Basic Procedures
Logout (Off Symbol)
Logs out the current user and shows the login screen
100
.
Search Box
Use the search box to find objects and reports, and other items by name or tag, or to search
for help.
Context Menu
Additionally, there is a context menu
open it.
2011-09-27
136
available for every object. Right-click on an object to
153
Part VI: Ajax Web Interface—Device and Sensor Setup
Part VI
Ajax Web Interface—Device and Sensor Setup
2010-11-09
155
Part VI: Ajax Web Interface—Device and Sensor Setup
6
Ajax Web Interface—Device and Sensor
Setup
The Ajax-based web interface is your access to PRTG. It is used to configure devices and
sensors, and to set up notifications, as well as review monitoring results and create reports.
This web interface is highly interactive and uses Asynchronous Java Script and XML (AJAX) to
deliver a powerful and easy-to-use user experience. While the user is logged in 100 , the data
on the screen is permanently refreshed (via Ajax calls) so it always shows the current
monitoring results (refresh interval and method can be set 1060 by the user).
The following sections introduce device and sensor setup in the Ajax Graphical User Interface
(GUI).
156
2010-11-09
Part VI: Ajax Web Interface—Device and Sensor Setup
Ajax Web Interface—Device and Sensor Setup—Topics
§ Auto-Discovery
158
§ Create Objects Manually
§ Manage Device Tree
183
§ Root Group Settings
185
§ Probe Settings
169
196
§ Group Settings
207
§ Device Settings
222
§ Sensor Settings
236
—List of Available Sensor Types
§ Sensor Channels Settings
237
938
§ Sensor Notifications Settings
943
Other Ajax Web Interface Sections
§ Ajax Web Interface—Basic Procedures
98
§ Ajax Web Interface—Advanced Procedures
954
Related Topics
§ Enterprise Console 1074
§ Other User Interfaces 1120
2010-11-09
157
Part VI: Ajax Web Interface—Device and Sensor Setup
6.1
Auto-Discovery
PRTG's auto-discovery function is a great way to automatically create a sophisticated and
concise set of sensors for your complete network. It is mainly suitable for LAN discovery
since it involves a lot of SNMP and WMI. For video instructions, please see the More 167
section below.
For a quick start auto-discovery, please see TWO—Auto-Discover Your Network
33
section.
How Auto-Discovery Works
PRTG's auto-discovery process has three stages:
· Step 1
Scanning a network segment for devices using Ping (for groups only).
· Step 2
Assessing the device type for all devices discovered in Step 1 (using SNMP, WMI and other
protocols).
· Step 3a
Creating sensor sets that match the discovered device types of step 2. This is done based
on built-in device templates with recommended sensors for many device types.
Step 3b (optional)
Creating sensor sets using user created device templates (see Create Device Template
section).
969
The auto-discovery can be used on a group level for a range of IP addresses, or for individual
devices 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 ToDos 128 are created (which are usually
mailed to the system administrator).
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 Systems, Linux (SSH/WBEM)
Systems, VMware/XEN Servers, and SNMP Devices in order to fully exploit the power of
this feature. We recommend defining these in the Root group settings 185 .
· 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.
158
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
· 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 167 section below.
Run Auto-Discovery Now
You can run an auto-discovery any time for a group or a device. To do so, right-click on the
respective object and from the context menu, select Run Auto-Discovery. PRTG will
immediately start searching for new objects it can add. If used for a group, PRTG will add
devices and sensors, if found. If used for a device, it will add new sensors, if found.
Note: The auto-discovery will also re-add devices or sensors you have manually deleted. If
you do not want this, please create objects manually 169 only.
Creating an Auto-Discovery Group
There are several ways to start auto-discovery:
§ On the welcome screen
106
, click on the Perform Network Auto-Discovery option
§ or select Devices | Add Auto-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 Auto-Discovery
Group... in the context menu 136 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 System Administrator 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.
2011-10-25
159
Part VI: Ajax Web Interface—Device and Sensor Setup
Add Auto-Discovery Group Assistant Step 2
§ Step 1
Please choose a probe or group you want to add the new group to. Click on Continue.
§ Step 2
Add auto-discovery settings as described below.
Add Auto-Discovery Group Settings
Group Name and Tags
160
Group Name
Enter a meaningful name to identify the group. The name will be
shown by default in the devices tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group objects and use tag-filtered views later on. Tags
are not case sensitive. We recommend using the default value.
You can add additional tags to it, if you like. Tags are
automatically inherited 89 .
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
Group Type
Sensor Management
Select the method for automatic network discovery. Choose
between:
§ Automatic device identification (standard, recommended):
Detect mainly based on Ping, SNMP, and WMI. This option
should work fine for most installations.
§ Automatic device identification (detailed, may create many
sensors): Detect in a more detailed way and create more
sensors. This option uses all standard device templates for
auto-discovery. It is suitable for small network segments and
whenever you want to monitor the maximum number of sensors
available.
§ Automatic sensor creation using specific device template(s):
Manually define the device templates used for auto-discovery.
From the list below, select one or more templates.
Device Template(s)
This option is only available if using specific device templates is
enabled above. Choose one or more device templates from the list
by adding a check mark in front of the respective template name.
Choose from:
§ Cisco Device (Generic)
§ DNS Server
§ FTP Server
§ Generic Device (PING only)
§ Generic Device (SNMP-enabled)
§ Generic Device (SNMP-enabled, Detailed)
§ HTTP Web Server
§ Hyper V Host Server
§ Linux/UNIX Device (SNMP or SSH enabled)
§ LocalhostRDP
§ Mail Server (Generic)
§ Mail Server (MS Exchange 2003)
§ Mail Server (MS Exchange 2007)
§ Misc. Details
§ Printer (HP)
§ Server (Compaq/HP agents)
§ Switch (Cisco Catalyst)
2011-10-25
161
Part VI: Ajax Web Interface—Device and Sensor Setup
§ Switch (Cisco IOS Based)
§ Switch (HP Procurve)
§ UNIX/Linux Device
§ UPS (APC)
§ VMware ESX Server
§ Windows (Detailed via WMI)
§ Windows (via WMI)
§ Windows IIS (via SNMP)
§ XEN Server
Discovery Schedule
Define when the auto-discovery will be run. Choose between:
· Once: Perform auto-discovery only once. New devices and
sensors will be added once. You can run auto-discovery
manually any time using an object's context menu 136 .
· Hourly: Perform auto-discovery for new devices and sensors
every 60 minutes. Note: Please use this option with caution!
Frequently executed auto-discoveries might cause performance
issues, especially when large network segments are scanned
every hour.
· Daily: Perform auto-discovery for new devices and sensors every
24 hours. The first auto-discovery will run immediately, all other
discoveries will start on the time defined in the Auto-Discovery
Settings section of the System Administration—System and
Website 1044 settings.
· Weekly: Perform auto-discovery for new devices and sensors
every 7 days. The first auto-discovery will run immediately, all
other discoveries will start on the time defined in the
Auto-Discovery Settings section of the System
Administration—System and Website 1044 settings.
IP Selection Method
Define how you want to define the IP range for auto-discovery.
Choose between:
§ Class C base IP with start/end: Define a class C address
range.
§ List of individual IPs: Enter individual IP addresses.
§ IP and subnet: Enter an IP address and subnet mask.
§ IP with octet range: Enter an IP address range for every IP octet
individually. With this, you can define very customizable IP
ranges.
162
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
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.
IP Base
This field is only visible if Class C network detection is selected
above. Enter a class C network as IP base for the auto-discovery.
Enter the first three octets of an IPv4 IP address, for example,
192.168.0
IP Range Start
This field is only visible if Class C network detection is selected
above. Enter the IP octet of the class C network specified above
from which PRTG will start the auto-discovery. This will complete
the IP base above to an IPv4 address. For example, enter 1 to
discover from 192.168.0.1.
IP Range End
This field is only visible if Class C network detection is selected
above. Enter the IP octet of the class C network specified above at
which PRTG will stop the auto-discovery. This will complete the IP
base above to an IPv4 address. For example, enter 254 to discover
up to 192.168.0.254.
IP List
This field is only visible if the IP list option is selected above. Enter
a list of IP addresses which the auto-discovery will scan. Enter
each address in a separate line.
IP and Subnet
This field is only visible if the IP and subnet option is selected
above. Enter an expression in the format address/subnet, e.g.
192.168.3.0/255.255.255.0. You can also use the short form like
192.168.3.0/24 in this example. PRTG will scan the complete host
range (without network and broadcast address) defined by the IP
address and the subnet mask.
IP with Octet Range
This field is only visible if the octet range option is selected
above. Enter an expression in the format a1.a2.a3.a4, where a1,
a2, a3, and a4 are each a number between 0-255, or a range with
two numbers and a hyphen like 1-127. All permutations of all
ranges are calculated, e.g. 10.0.1-10.1-100 results in 1,000
addresses that PRTG will scan during auto-discovery.
Name Resolution
Define how newly discovered devices will be monitored. This only
affects new devices. The setting for existing devices will be kept.
Choose between:
· Use DNS / WMI / SNMP names (recommended): Monitor newly
discovered devices via their DNS, WMI, or SNMP names (if
available).
· Use IP addresses: Monitor newly discovered devices via their IP
address.
We recommend using the default value.
2011-10-25
163
Part VI: Ajax Web Interface—Device and Sensor Setup
Device Rescan
Define if you want to rescan known devices. Choose between:
· Skip auto-discovery for known devices/IPs (recommended):
Do not re-scan known devices or IP addresses, but only scan for
new devices/IPs when auto-discovering. This can avoid
re-creation of manually deleted sensors. PRTG will also avoid
adding devices that are already included elsewhere in your
configuration, e.g. in other groups.
· Perform auto-discovery for known devices/IPs: Re-scan
known devices and IP addresses with every auto-discovery. This
will re-create manually deleted sensors on existing devices.
We recommend using the default value.
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 185 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!
Credentials for Windows Systems
Domain or Computer
Name
Define the authority for Windows access. This is used for Windows
Management Instrumentation (WMI) and other sensors. If using a
Windows local user account, please enter the computer name
here. If using a Windows domain user account, please enter the
domain name here.
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.
Credentials for Linux (SSH/WBEM) Systems
Username
Enter a login name for the Linux access via SSH and WBEM.
Usually, you will use credentials with administrator privileges.
Login
Define which authentication method will be used for login. Choose
between:
§ Login via Password: Provide a password for login. Enter below.
164
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for Linux (SSH/WBEM) Systems
§ Login via Private Key: Provide a private key for authentication.
Paste below.
Password
This field is only visible if password login is selected above. Enter
a password for the Linux access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Private Key
This field is only visible if private key login is selected above.
Paste a private key into the field. 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 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 automatically (port 5988 or 5989): Use one of the
standard ports, depending on whether unencrypted or
encrypted connection is chosen above.
· Set manually: Use a custom port. Define below.
WBEM Port
This setting is only visible if manual port selection is enabled
above. Enter the WBEM port number.
Credentials for VMware/XEN Servers
User
Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password
Enter a password for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
VMware Protocol
Choose between:
· HTTPS (recommended): Use an SSL-encrypted connection to
VMware and XEN servers.
· HTTP: Use an unencrypted connection to VMware and XEN
servers.
2011-10-25
165
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for SNMP Devices
SNMP Version
Select the SNMP version that will be used for device connection.
Choose between:
· v1: Use the simple standard v1 protocol for SNMP connections.
This protocol only offers clear-text data transmission, but it is
usually supported by all devices.
· v2c: Use the more advanced v2c protocol for SNMP connections.
Data is still transferred as clear-text, but it supports 64-bit
counters.
· v3: Use the latest v3 protocol for SNMP connections. It provides
secure authentication and data encryption.
Note for SNMP v3: Due to internal limitations you can only
monitor a limited number of sensors per second using SNMP v3.
The limit is somewhere between 1 and 50 sensors per second
(depending on the SNMP latency of your network). This means that
using an interval of 60 seconds you are limited to between 60 and
3000 SNMP v3 sensors for each probe. If you experience an
increased "Interval Delay" or "Open Requests" reading of the probe
health sensor you need to distribute the load over multiple
probes. SNMP v1 and v2 do not have this limitation.
Community String
This setting is only visible if SNMP version v1 or v2c are enabled
above. Enter the community string of your devices. This is a kind
of "clear-text password" used for simple authentication. We
recommend using the default value.
Authentication Type
This setting is only visible if SNMP version v3 is enabled above.
Choose between:
· MD5: Use Message-Digest Algorithm 5 (MD5) for authentication.
· SHA: Use Secure Hash Algorithm (SHA) for authentication.
Your device must be set to the same value.
166
User
This setting is only visible if SNMP version v3 is enabled above.
Enter a username for secure authentication. Your device must be
set to the same value.
Password
This setting is only visible if SNMP version v3 is enabled above.
Enter a password for secure authentication. Your device must be
set to the same value.
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for SNMP Devices
Data Encryption Key
(DES)
This setting is only visible if SNMP version v3 is enabled above.
Enter a Data Encryption Standard (DES) key here. If you provide a
key in this field, SNMP data packets will be enrypted using the DES
encryption algorithm, providing increased security. Your device
must be set to the same value. Note: If the key entered in this
field does not match the key configured in the target SNMP device
you will not get an error message! Please enter a string or leave
the field empty.
SNMP Port
Enter the port used for SNMP communication. We recommend
using the default value.
SNMP Timeout (sec.)
Enter a timeout in seconds for the request. If the reply takes
longer than this value the request is aborted and an error
message is triggered.
Click on the Continue button to store your settings. If you change tabs or use the main
menu, all changes to the settings will be lost!
Auto-Discovery in Progress
While auto-discovery is running you may experience a lower system performance as usual,
because PRTG works in the background 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 minutes... from the context menu 136 . Monitoring will be paused for 5 minutes, and
auto-discovery tasks will be shut down.
Related Topics
§ Create Device Template
969
More
Video Tutorial: There is a video available on the Paessler video tutorials page.
§ http://www.paessler.com/support/video_tutorials
2011-10-25
167
Part VI: Ajax Web Interface—Device and Sensor Setup
Knowledge Base: Why can automatic auto-discoveries evoke performance issues?
§ http://www.paessler.com/knowledgebase/en/topic/14423
Knowledge Base: Why are sensors missing in my auto-created device template?
§ http://www.paessler.com/knowledgebase/en/topic/5853
168
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
6.2
Create Objects Manually
We recommend using the auto-discovery 158 function to create a basic monitoring setup for
your network. Afterwards, you can manually create devices that could not be discovered, or
arrange 960 detected devices in groups.
The procedure depends on the kind of object you want to add. Choose between:
§ Add a Remote Probe
§ Add a Group
169
170
§ Add a Device
175
§ Add a Sensor
182
Add a Remote Probe
Please see Multiple Probes and Remote Probes 1193 section for more information.
2011-01-24
169
Part VI: Ajax Web Interface—Device and Sensor Setup
6.2.1 Add a Group
Note: This documentation refers to the PRTG System Administrator 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 group, 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 136 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.
§ Step 1
Please choose a probe or group you want to add the new group to. Click on Continue.
Add Group Assistant Step 2
§ Step 2
Add group settings as described below.
Add Group Settings
Group Name and Tags
170
Group Name
Enter a meaningful name to identify the group. The name will be
shown by default in the devices tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group objects and use tag-filtered views later on. Tags
are not case sensitive. We recommend using the default value.
You can add additional tags to it, if you like. Tags are
automatically inherited 89 .
2011-01-24
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for Windows Systems
Domain or Computer
Name
Define the authority for Windows access. This is used for Windows
Management Instrumentation (WMI) and other sensors. If using a
Windows local user account, please enter the computer name
here. If using a Windows domain user account, please enter the
domain name here.
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.
Credentials for Linux (SSH/WBEM) Systems
Username
Enter a login name for the Linux access via SSH and WBEM.
Usually, you will use credentials with administrator privileges.
Login
Define which authentication method will be used for login. Choose
between:
§ Login via Password: Provide a password for login. Enter below.
§ Login via Private Key: Provide a private key for authentication.
Paste below.
Password
This field is only visible if password login is selected above. Enter
a password for the Linux access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Private Key
This field is only visible if private key login is selected above.
Paste a private key into the field. 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 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
2011-01-24
Define the port that will be used for WBEM. This setting is only
relevant when using WBEM sensors. Choose between:
171
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for Linux (SSH/WBEM) Systems
· Set automatically (port 5988 or 5989): Use one of the
standard ports, depending on whether unencrypted or
encrypted connection is chosen above.
· Set manually: Use a custom port. Define below.
WBEM Port
This setting is only visible if manual port selection is enabled
above. Enter the WBEM port number.
Credentials for VMware/XEN Servers
User
Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password
Enter a password for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
VMware Protocol
Choose between:
· HTTPS (recommended): Use an SSL-encrypted connection to
VMware and XEN servers.
· HTTP: Use an unencrypted connection to VMware and XEN
servers.
Credentials for SNMP Devices
SNMP Version
Select the SNMP version that will be used for device connection.
Choose between:
· v1: Use the simple standard v1 protocol for SNMP connections.
This protocol only offers clear-text data transmission, but it is
usually supported by all devices.
· v2c: Use the more advanced v2c protocol for SNMP connections.
Data is still transferred as clear-text, but it supports 64-bit
counters.
· v3: Use the latest v3 protocol for SNMP connections. It provides
secure authentication and data encryption.
172
2011-01-24
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for SNMP Devices
Note for SNMP v3: Due to internal limitations you can only
monitor a limited number of sensors per second using SNMP v3.
The limit is somewhere between 1 and 50 sensors per second
(depending on the SNMP latency of your network). This means that
using an interval of 60 seconds you are limited to between 60 and
3000 SNMP v3 sensors for each probe. If you experience an
increased "Interval Delay" or "Open Requests" reading of the probe
health sensor you need to distribute the load over multiple
probes. SNMP v1 and v2 do not have this limitation.
Community String
This setting is only visible if SNMP version v1 or v2c are enabled
above. Enter the community string of your devices. This is a kind
of "clear-text password" used for simple authentication. We
recommend using the default value.
Authentication Type
This setting is only visible if SNMP version v3 is enabled above.
Choose between:
· MD5: Use Message-Digest Algorithm 5 (MD5) for authentication.
· SHA: Use Secure Hash Algorithm (SHA) for authentication.
Your device must be set to the same value.
2011-01-24
User
This setting is only visible if SNMP version v3 is enabled above.
Enter a username for secure authentication. Your device must be
set to the same value.
Password
This setting is only visible if SNMP version v3 is enabled above.
Enter a password for secure authentication. Your device must be
set to the same value.
Data Encryption Key
(DES)
This setting is only visible if SNMP version v3 is enabled above.
Enter a Data Encryption Standard (DES) key here. If you provide a
key in this field, SNMP data packets will be enrypted using the DES
encryption algorithm, providing increased security. Your device
must be set to the same value. Note: If the key entered in this
field does not match the key configured in the target SNMP device
you will not get an error message! Please enter a string or leave
the field empty.
SNMP Port
Enter the port used for SNMP communication. We recommend
using the default value.
SNMP Timeout (sec.)
Enter a timeout in seconds for the request. If the reply takes
longer than this value the request is aborted and an error
message is triggered.
173
Part VI: Ajax Web Interface—Device and Sensor Setup
Click on the Continue button to store your settings. If you change tabs or use the main
menu, all changes to the settings will be lost!
174
2011-01-24
Part VI: Ajax Web Interface—Device and Sensor Setup
6.2.2 Add a Device
Note: This documentation refers to the PRTG System Administrator 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 136 of a group to which you want to add the new device. This will skip step 1
and lead you directly to step 2.
§ Step 1
Please choose a group you want to add the new device to. Click on Continue.
Add Device Assistant Step 2
§ Step 2
Add device settings as described below.
Add Device Settings
Device Name an Address
2011-10-11
Device Name
Enter a meaningful name to identify the device. The name will be
shown by default in the device tree and in all alarms.
IP Version
Define which IP protocol PRTG will use to connect to this device.
The setting is valid for all sensors created on this device. Choose
between:
175
Part VI: Ajax Web Interface—Device and Sensor Setup
Device Name an Address
§ Connect using IPv4: Use IP version 4 for all requests to this
device.
§ Connect using IPv6: Use IP version 6 for all requests to this
device.
IP Address/DNS Name
Enter the IP address (either v4 or v6, depending on your selection
above) or DNS name for the device. Most sensors created on this
device will inherit this setting and they will try to connect to this
address for monitoring. Note: There are some sensor types that
still have their own setting for IP address/DNS name. Those
sensors will use their own settings.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Tags are
automatically inherited 89 .
Device Icon
Choose a device icon from the list. It will be shown in the device
tree.
Device Type
Sensor Management
Select which type of auto-discovery you would like to perform for
this device. Choose between:
§ Manual (no auto-discovery): Do not auto-discover any sensors,
but only add sensors manually.
§ Automatic device identification (standard, recommended):
Use a small set of auto-discovery templates. This will scan your
LAN and usually create a view standard sensors on your device.
§ Automatic device identification (detailed, may create many
sensors: Use an extended set of auto-discovery templates. This
will scan your LAN and usually create many sensors on your
device.
§ Automatic sensor creation using specific device templates:
Use specific auto-discovery templates only. Please select
templates below. This will scan your LAN and add sensors
defined in the template.
Discovery Schedule
This option is only visible if one of the auto-discovery options is
selected above. Define when the auto-discovery will be run.
Choose between:
§ Once: Perform auto-discovery only once. For existing devices,
this will initiate a one-time sensor update for the current device.
176
2011-10-11
Part VI: Ajax Web Interface—Device and Sensor Setup
Device Type
§ Hourly: Perform auto-discovery for new sensors every hour.
§ Daily: Perform auto-discovery for new sensors every day.
§ Weekly: Perform auto-discovery for new sensors every week.
Device Template(s)
This option is only visible if using specific device templates (last
option) is enabled above. Please choose one or more templates by
adding a check mark in front of the respective template name.
These will be used for auto-discovery on the current device.
Choose from:
§ Cisco Device (Generic)
§ DNS Server
§ FTP Server
§ Generic Device (PING only)
§ Generic Device (SNMP-enabled)
§ Generic Device (SNMP-enabled, Detailed)
§ HTTP Web Server
§ Hyper V Host Server
§ Linux/UNIX Device (SNMP or SSH enabled)
§ Mail Server (Generic)
§ Mail Server (MS Exchange)
§ NTP Server
§ Printer (HP)
§ RDP Server
§ Server (Compaq/HP agents)
§ Switch (Cisco Catalyst)
§ Switch (Cisco IOS Based)
§ Switch (HP Procurve)
§ UNIX/Linux Device
§ UPS (APC)
§ Virtuozzo Server
§ VMware ESX Server
§ Windows (Detailed via WMI)
§ Windows (via WMI)
2011-10-11
177
Part VI: Ajax Web Interface—Device and Sensor Setup
Device Type
§ Windows IIS (via SNMP)
§ XEN Server
Credentials for Windows Systems
Domain or Computer
Name
Define the authority for Windows access. This is used for Windows
Management Instrumentation (WMI) and other sensors. If using a
Windows local user account, please enter the computer name
here. If using a Windows domain user account, please enter the
domain name here.
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.
Credentials for Linux (SSH/WBEM) Systems
Username
Enter a login name for the Linux access via SSH and WBEM.
Usually, you will use credentials with administrator privileges.
Login
Define which authentication method will be used for login. Choose
between:
§ Login via Password: Provide a password for login. Enter below.
§ Login via Private Key: Provide a private key for authentication.
Paste below.
Password
This field is only visible if password login is selected above. Enter
a password for the Linux access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Private Key
This field is only visible if private key login is selected above.
Paste a private key into the field. 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 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.
178
2011-10-11
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for Linux (SSH/WBEM) Systems
· 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 automatically (port 5988 or 5989): Use one of the
standard ports, depending on whether unencrypted or
encrypted connection is chosen above.
· Set manually: Use a custom port. Define below.
WBEM Port
This setting is only visible if manual port selection is enabled
above. Enter the WBEM port number.
Credentials for VMware/XEN Servers
User
Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password
Enter a password for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
VMware Protocol
Choose between:
· HTTPS (recommended): Use an SSL-encrypted connection to
VMware and XEN servers.
· HTTP: Use an unencrypted connection to VMware and XEN
servers.
Credentials for SNMP Devices
SNMP Version
Select the SNMP version that will be used for device connection.
Choose between:
· v1: Use the simple standard v1 protocol for SNMP connections.
This protocol only offers clear-text data transmission, but it is
usually supported by all devices.
· v2c: Use the more advanced v2c protocol for SNMP connections.
Data is still transferred as clear-text, but it supports 64-bit
counters.
· v3: Use the latest v3 protocol for SNMP connections. It provides
secure authentication and data encryption.
2011-10-11
179
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for SNMP Devices
Note for SNMP v3: Due to internal limitations you can only
monitor a limited number of sensors per second using SNMP v3.
The limit is somewhere between 1 and 50 sensors per second
(depending on the SNMP latency of your network). This means that
using an interval of 60 seconds you are limited to between 60 and
3000 SNMP v3 sensors for each probe. If you experience an
increased "Interval Delay" or "Open Requests" reading of the probe
health sensor you need to distribute the load over multiple
probes. SNMP v1 and v2 do not have this limitation.
Community String
This setting is only visible if SNMP version v1 or v2c are enabled
above. Enter the community string of your devices. This is a kind
of "clear-text password" used for simple authentication. We
recommend using the default value.
Authentication Type
This setting is only visible if SNMP version v3 is enabled above.
Choose between:
· MD5: Use Message-Digest Algorithm 5 (MD5) for authentication.
· SHA: Use Secure Hash Algorithm (SHA) for authentication.
Your device must be set to the same value.
180
User
This setting is only visible if SNMP version v3 is enabled above.
Enter a username for secure authentication. Your device must be
set to the same value.
Password
This setting is only visible if SNMP version v3 is enabled above.
Enter a password for secure authentication. Your device must be
set to the same value.
Data Encryption Key
(DES)
This setting is only visible if SNMP version v3 is enabled above.
Enter a Data Encryption Standard (DES) key here. If you provide a
key in this field, SNMP data packets will be enrypted using the DES
encryption algorithm, providing increased security. Your device
must be set to the same value. Note: If the key entered in this
field does not match the key configured in the target SNMP device
you will not get an error message! Please enter a string or leave
the field empty.
SNMP Port
Enter the port used for SNMP communication. We recommend
using the default value.
SNMP Timeout (sec.)
Enter a timeout in seconds for the request. If the reply takes
longer than this value the request is aborted and an error
message is triggered.
2011-10-11
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Click on the Continue button to store your settings. If you change tabs or use the main
menu, all changes to the settings will be lost!
2011-10-11
181
Part VI: Ajax Web Interface—Device and Sensor Setup
6.2.3 Add a Sensor
Note: This documentation refers to the PRTG System Administrator 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.
There are different ways to manually add a sensor to an existing device.
§ On the welcome screen
106
, click on the Add Sensors Manually option
§ or 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 136 of a device to which you want to add the new sensor. This
will skip step 1 and lead you directly to step 2.
§ Step 1
Please select Add sensor to an existing device and choose a device you want to add the
new sensor to. Click on Continue.
Add Sensor Assistant
§ Step 2
The Add sensor assistant is shown (see screenshot above). Select a sensor you want to add
and enter the needed settings. For more information, please see the manual section of the
respective sensor. See List of Available Sensor Types 237 section to find detailed
information about every sensor.
182
2011-10-06
Part VI: Ajax Web Interface—Device and Sensor Setup
6.3
Manage Device Tree
While viewing the device tree (or parts of it), click on the Management tab to enter a
different tree view which shows your devices and sensors is a less colorful way. While in this
view you can move monitoring objects using drag&drop in your browser window. 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 grey 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 grey shade will show the future position. After dropping the sensor on a
new device, the web interface will ask for a New Sensor Name. This gives you the choice to
confirm the clone process with Ok or to Cancel. 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 118 and resume 135 monitoring.
Note: You cannot clone 'fixed' objects, such as the root group or a probe device.
Note: In order to clone entire groups or devices, please use the Clone Object
accessible via the objects' Context Menu 136 .
962
functionality
Drag&Drop a Group or Device
§ Within the same probe or group, drag any group or device and move it up or down in the
device tree. A small red arrow will appear, showing the future position. When dropping, the
group or device will be moved to this position and existing probes, groups, and devices will
be lined up underneath. This is a very easy way to reposition your groups or devices.
§ Drag any group or device from one probe or group and drop it on another probe or group.
A small red arrow will appear, showing the future position. When dropping, the group or
device will be moved to the new probe or group. Existing groups and devices will be lined
up underneath. This is a very easy way to change the probe a group or device is part of, or
to add groups or devices to other groups.
Note: The Local Probe and Remote Probes cannot be moved.
2011-09-27
183
Part VI: Ajax Web Interface—Device and Sensor Setup
Related Topics
For other ways to arrange objects, please see
§ Arrange Objects
960
§ Create Device Template
§ Clone Object
184
969
962
2011-09-27
Part VI: Ajax Web Interface—Device and Sensor Setup
6.4
Root Group Settings
On the Root group's overview page, click on the Settings tab to change settings.
The Root Group is Special
The Root group is the highest instance in the object hierarchy of your PRTG setup and
parent to all other objects. Therefore all objects inherit settings from the Root group. If you
define important settings on this high level, work will be easier later on. So, before you create
your own sensors, it is a good idea to review the Root group's settings to ensure they suit
your network. There are already reasonable presets made with installation.
Note: If necessary, you can override every setting for every single child object later. To do so,
simply disable the respective Inherit option of an object.
Root Group Settings
The following settings are available in the Settings tab. As you may not need all of these,
just regard those settings you really need, ignoring the others. All settings you define here
can easily be inherited to all other objects in your setup.
Note: This documentation refers to the PRTG System Administrator 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 Group Settings
Group Name
Enter a meaningful name to identify the group. The name will be
shown by default in the devices tree and in all alarms.
Status
Define if monitoring for this group is started or paused. Choose
between:
· Started: Monitor this group.
· Paused: Pause monitoring for this group. All sensors on all
devices in this group will be paused until this setting is changed
again.
2011-08-12
185
Part VI: Ajax Web Interface—Device and Sensor Setup
Location
Location (for geo
maps)
When using geo maps using Google's API 975 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 112 (green - yellow orange - red). You can enter a full postal address, city and country
only, or latitude and longitude. 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.
Credentials for Windows Systems
Domain or Computer
Name
Define the authority for Windows access. This is used for Windows
Management Instrumentation (WMI) and other sensors. If using a
Windows local user account, please enter the computer name
here. If using a Windows domain user account, please enter the
domain name here.
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.
Credentials for Linux (SSH/WBEM) Systems
Username
Enter a login name for the Linux access via SSH and WBEM.
Usually, you will use credentials with administrator privileges.
Login
Define which authentication method will be used for login. Choose
between:
§ Login via Password: Provide a password for login. Enter below.
§ Login via Private Key: Provide a private key for authentication.
Paste below.
186
Password
This field is only visible if password login is selected above. Enter
a password for the Linux access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Private Key
This field is only visible if private key login is selected above.
Paste a private key into the field. 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!
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for Linux (SSH/WBEM) Systems
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 automatically (port 5988 or 5989): Use one of the
standard ports, depending on whether unencrypted or
encrypted connection is chosen above.
· Set manually: Use a custom port. Define below.
WBEM Port
This setting is only visible if manual port selection is enabled
above. Enter the WBEM port number.
Credentials for VMware/XEN Servers
User
Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password
Enter a password for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
VMware Protocol
Choose between:
· HTTPS (recommended): Use an SSL-encrypted connection to
VMware and XEN servers.
· HTTP: Use an unencrypted connection to VMware and XEN
servers.
Credentials for SNMP Devices
SNMP Version
Select the SNMP version that will be used for device connection.
Choose between:
· v1: Use the simple standard v1 protocol for SNMP connections.
This protocol only offers clear-text data transmission, but it is
usually supported by all devices.
· v2c: Use the more advanced v2c protocol for SNMP connections.
Data is still transferred as clear-text, but it supports 64-bit
counters.
2011-08-12
187
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for SNMP Devices
· v3: Use the latest v3 protocol for SNMP connections. It provides
secure authentication and data encryption.
Note for SNMP v3: Due to internal limitations you can only
monitor a limited number of sensors per second using SNMP v3.
The limit is somewhere between 1 and 50 sensors per second
(depending on the SNMP latency of your network). This means that
using an interval of 60 seconds you are limited to between 60 and
3000 SNMP v3 sensors for each probe. If you experience an
increased "Interval Delay" or "Open Requests" reading of the probe
health sensor you need to distribute the load over multiple
probes. SNMP v1 and v2 do not have this limitation.
Community String
This setting is only visible if SNMP version v1 or v2c are enabled
above. Enter the community string of your devices. This is a kind
of "clear-text password" used for simple authentication. We
recommend using the default value.
Authentication Type
This setting is only visible if SNMP version v3 is enabled above.
Choose between:
· MD5: Use Message-Digest Algorithm 5 (MD5) for authentication.
· SHA: Use Secure Hash Algorithm (SHA) for authentication.
Your device must be set to the same value.
188
User
This setting is only visible if SNMP version v3 is enabled above.
Enter a username for secure authentication. Your device must be
set to the same value.
Password
This setting is only visible if SNMP version v3 is enabled above.
Enter a password for secure authentication. Your device must be
set to the same value.
Data Encryption Key
(DES)
This setting is only visible if SNMP version v3 is enabled above.
Enter a Data Encryption Standard (DES) key here. If you provide a
key in this field, SNMP data packets will be enrypted using the DES
encryption algorithm, providing increased security. Your device
must be set to the same value. Note: If the key entered in this
field does not match the key configured in the target SNMP device
you will not get an error message! Please enter a string or leave
the field empty.
SNMP Port
Enter the port used for SNMP communication. We recommend
using the default value.
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for SNMP Devices
SNMP Timeout (sec.)
Enter a timeout in seconds for the request. If the reply takes
longer than this value the request is aborted and an error
message is triggered.
WMI Compatibility Options
When experiencing problems while monitoring via Windows Management Instrumentation
(WMI) sensors, you can set some compatibility options for trouble shooting.
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 interval (recommended): Use a default of
one and a half times the scanning interval set for the sensor
(see below in this settings).
· Set manually: Enter a timeout value manually.
We recommend using the default value. Only if you experience
ongoing timeout errors, try increasing the timeout value.
Timeout value (sec.)
This field is only visible if manually timeout method is selected
above. Specify the time the sensor will wait for the return of its
WMI query before aborting with an error message. Please enter an
integer value.
RPC server port
Specify the port which WMI uses for DCOM communication. We
recommend using the default value. Only if you change this port
on your system(s), please change it here.
SNMP Compatibility Options
When experiencing problems while monitoring via Simple Network Management Protocol
(SNMP) sensors, you can set some compatibility options for trouble shooting.
SNMP Delay (ms)
Add a time in milliseconds that will be waited between two SNMP
requests. This can help increase device compatibility. Please enter
an integer value. We recommend using the default value. If you
experience SNMP connection failures, please increase it.
Failed Requests
Define if an SNMP sensor will try again after a request fails.
· Retry (recommended): Try again if an SNMP request fails. This
can help prevent false error messages due to temporary timeout
failures.
2011-08-12
189
Part VI: Ajax Web Interface—Device and Sensor Setup
SNMP Compatibility Options
· Do not retry: Do not retry if an SNMP request fails. With this
setting enabled an SNMP sensor will be put to error state earlier.
Overflow Values
Define how PRTG will handle overflow values. Some devices do not
handle internal buffer overflows correctly. This can cause false
peaks.
· Ignore overflow values (recommended): Ignore overflow
values and do not include them in the monitoring data.
· Handle overflow values as valid results: 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 delta sensors (recommended): Ignore
zero values and do not include them in the monitoring data.
· Handle zero values as valid results for delta 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
Define which kind of traffic counters PRTG will search for on a
device.
· Use 64-bit counters if available (recommended): The interface
scan will use 64-bit traffic counters, if available. This can avoid
buffer overflows in the devices.
· Use 32-bit counters only: The interface scan will always use
32-bit traffic counters, even if 64-bit counters are available. This
can lead to more reliable monitoring for some devices.
We recommend using the default value. If you experience
problems, change this option.
Request Mode
Define which kind of request method PRTG uses for SNMP
sensors.
· Use multi 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.
190
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
SNMP Compatibility Options
We recommend using the default value. If you experience
problems, change this option.
Port Name Template
Define how the name of SNMP sensors created on a device will be
put together. Enter a template using several variables. When
adding new sensors, PRTG scans the interface for available
counters at certain OIDs. At each OID usually several fields are
available with interface descriptions. They are different for every
device/OID. PRTG will use the information in these fields to name
the sensors. If a field is empty or not available, an empty string is
added to the name. As default, ([port]) [ifalias] is set as port
name template, which will create a name such as (001) Ethernet1,
for example. You can use any field names available at a certain
OID of your device, among which are:
· [port]
· [ifalias]
· [ifname]
· [ifindex]
· [ifdescr]
Combine them as you like to obtain suitable sensor names. See
the More section below for more information about SNMP sensor
names.
Port Name Update
Define how PRTG will react if you change port names in your
physical device (e.g. a switch or router). Choose between:
§ Keep port names (use this if you edit the names in PRTG):
Do not automatically adjust sensor names. This is the best
option if you want to change names in PRTG manually.
§ Automatic sensor name update if name changes in device: If
PRTG detects changes of port names in your physical device it
will try to automatically adjust sensor names accordingly. For
detailed information please see More section below.
Port Identification
Define which field will be used for SNMP interface identification.
Choose between:
§ Use ifAlias (recommended): For most devices ifAlias is the best
field to get unique interface names.
§ Use ifDescr: Use this option if the port order of your device
changes after a reboot, and there is no ifAlias field available. For
example, this is the best option for Cisco ASA devices. Note:
When using this option it is important that your device returns
unique interface names in the ifDescr field.
2011-08-12
191
Part VI: Ajax Web Interface—Device and Sensor Setup
SNMP Compatibility Options
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.
HTTP Proxy Settings
HTTP Proxy Settings
The proxy settings determine how a sensor connects to a given
URL. You can enter data for a proxy server that will be used when
connecting via HTTP or HTTPS.
Name
Enter the IP address or DNS name of the proxy server to use. If
you leave this field empty, no proxy will be used.
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
If the proxy requires authentication, enter the username for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Password
If the proxy requires authentication, enter the password for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Scanning Interval
Scanning Interval
192
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current object if its parent object is in a
Down status, or if it is paused by another dependency.
§ Select object: Pause the current object if its parent object is in
a Down status, or if it is paused by another dependency.
Additionally, pause the current object if a specific other object
in the device tree is in a Down status, or if it is paused by
another dependency. Select below.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-08-12
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current object will be
dependent on.
193
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
Unusual Detection
Unusual Detection
194
Define if unusual detection is enabled for sensors. You can set the
behavior of unusual detection in the system settings.
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
Unusual Detection
· Enabled: Enable unusual detection. Sensors will turn to orange
color if unusual activity is detected.
· Disabled: Disable unusual detection. To not use the orange
sensor color.
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
Notifications tab to change sensor notification triggers. The defined triggers will be
inherited down to sensor level. For detailed information, please see Sensor Notifications
Settings 943 section.
Others
For more general information about settings, please see Object Settings
118
section.
More
Knowledge Base: How does PRTG compute CPU Index, Traffic Index and Response Time
Index?
§ http://www.paessler.com/knowledgebase/en/topic/313
Knowledge Base: How can I add my own device icons for use in the PRTG web interface?
§ http://www.paessler.com/knowledgebase/en/topic/7313
Knowledge Base: How can I change the defaults for names automatically generated for new
SNMP sensors?
§ http://www.paessler.com/knowledgebase/en/topic/7363
Knowledge Base: Automatically update port name and number for SNMP Traffic sensors when
the device changes them
§ http://www.paessler.com/knowledgebase/en/topic/25893
2011-08-12
195
Part VI: Ajax Web Interface—Device and Sensor Setup
6.5
Probe Settings
On a probe's overview page, click on the Settings tab to change settings.
Add Remote Probe
You can add additional remote probes to your setup to extend you monitoring to networks
that are not directly reachable by your PRTG core installation or cluster.
See Add Remote Probe 1193 section for more details.
Probe Settings
The following settings are available in the Settings 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 185 group, so you can
inherit them to all other objects further down in the tree hierarchy.
Note: This documentation refers to the PRTG System Administrator 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 Probe Settings
Probe Name
Enter a meaningful name to identify the probe. The name will be
shown by default in the devices tree and in all alarms.
Status
Choose if monitoring for this probe is started or paused.
· Started: Monitor this probe.
· Paused: Pause monitoring for this probe. All sensors on all
devices on this probe will be paused until this setting is
changed again.
196
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group objects and use tag-filtered views later on. Tags
are not case sensitive. We recommend using the default value.
You can add additional tags to it, if you like.
Priority
Select a priority for the 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).
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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 975 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 112 (green - yellow orange - red). You can enter a full postal address, city and country
only, or latitude and longitude. 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.
Credentials for Windows Systems
Domain or Computer
Name
Define the authority for Windows access. This is used for Windows
Management Instrumentation (WMI) and other sensors. If using a
Windows local user account, please enter the computer name
here. If using a Windows domain user account, please enter the
domain name here.
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.
Credentials for Linux (SSH/WBEM) Systems
Username
Enter a login name for the Linux access via SSH and WBEM.
Usually, you will use credentials with administrator privileges.
Login
Define which authentication method will be used for login. Choose
between:
§ Login via Password: Provide a password for login. Enter below.
§ Login via Private Key: Provide a private key for authentication.
Paste below.
2011-08-12
197
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for Linux (SSH/WBEM) Systems
Password
This field is only visible if password login is selected above. Enter
a password for the Linux access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Private Key
This field is only visible if private key login is selected above.
Paste a private key into the field. 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 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 automatically (port 5988 or 5989): Use one of the
standard ports, depending on whether unencrypted or
encrypted connection is chosen above.
· Set manually: Use a custom port. Define below.
WBEM Port
This setting is only visible if manual port selection is enabled
above. Enter the WBEM port number.
Credentials for VMware/XEN Servers
User
Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password
Enter a password for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
VMware Protocol
Choose between:
· HTTPS (recommended): Use an SSL-encrypted connection to
VMware and XEN servers.
· HTTP: Use an unencrypted connection to VMware and XEN
servers.
198
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for SNMP Devices
SNMP Version
Select the SNMP version that will be used for device connection.
Choose between:
· v1: Use the simple standard v1 protocol for SNMP connections.
This protocol only offers clear-text data transmission, but it is
usually supported by all devices.
· v2c: Use the more advanced v2c protocol for SNMP connections.
Data is still transferred as clear-text, but it supports 64-bit
counters.
· v3: Use the latest v3 protocol for SNMP connections. It provides
secure authentication and data encryption.
Note for SNMP v3: Due to internal limitations you can only
monitor a limited number of sensors per second using SNMP v3.
The limit is somewhere between 1 and 50 sensors per second
(depending on the SNMP latency of your network). This means that
using an interval of 60 seconds you are limited to between 60 and
3000 SNMP v3 sensors for each probe. If you experience an
increased "Interval Delay" or "Open Requests" reading of the probe
health sensor you need to distribute the load over multiple
probes. SNMP v1 and v2 do not have this limitation.
Community String
This setting is only visible if SNMP version v1 or v2c are enabled
above. Enter the community string of your devices. This is a kind
of "clear-text password" used for simple authentication. We
recommend using the default value.
Authentication Type
This setting is only visible if SNMP version v3 is enabled above.
Choose between:
· MD5: Use Message-Digest Algorithm 5 (MD5) for authentication.
· SHA: Use Secure Hash Algorithm (SHA) for authentication.
Your device must be set to the same value.
2011-08-12
User
This setting is only visible if SNMP version v3 is enabled above.
Enter a username for secure authentication. Your device must be
set to the same value.
Password
This setting is only visible if SNMP version v3 is enabled above.
Enter a password for secure authentication. Your device must be
set to the same value.
199
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for SNMP Devices
Data Encryption Key
(DES)
This setting is only visible if SNMP version v3 is enabled above.
Enter a Data Encryption Standard (DES) key here. If you provide a
key in this field, SNMP data packets will be enrypted using the DES
encryption algorithm, providing increased security. Your device
must be set to the same value. Note: If the key entered in this
field does not match the key configured in the target SNMP device
you will not get an error message! Please enter a string or leave
the field empty.
SNMP Port
Enter the port used for SNMP communication. We recommend
using the default value.
SNMP Timeout (sec.)
Enter a timeout in seconds for the request. If the reply takes
longer than this value the request is aborted and an error
message is triggered.
WMI Compatibility Options
When experiencing problems while monitoring via Windows Management Instrumentation
(WMI) sensors, you can set some compatibility options for trouble shooting.
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 interval (recommended): Use a default of
one and a half times the scanning interval set for the sensor
(see below in this settings).
· Set manually: Enter a timeout value manually.
We recommend using the default value. Only if you experience
ongoing timeout errors, try increasing the timeout value.
Timeout value (sec.)
This field is only visible if manually timeout method is selected
above. Specify the time the sensor will wait for the return of its
WMI query before aborting with an error message. Please enter an
integer value.
RPC server port
Specify the port which WMI uses for DCOM communication. We
recommend using the default value. Only if you change this port
on your system(s), please change it here.
SNMP Compatibility Options
When experiencing problems while monitoring via Simple Network Management Protocol
(SNMP) sensors, you can set some compatibility options for trouble shooting.
200
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
SNMP Compatibility Options
SNMP Delay (ms)
Add a time in milliseconds that will be waited between two SNMP
requests. This can help increase device compatibility. Please enter
an integer value. We recommend using the default value. If you
experience SNMP connection failures, please increase it.
Failed Requests
Define if an SNMP sensor will try again after a request fails.
· Retry (recommended): Try again if an SNMP request fails. This
can help prevent false error messages due to temporary timeout
failures.
· Do not retry: Do not retry if an SNMP request fails. With this
setting enabled an SNMP sensor will be put to error state earlier.
Overflow Values
Define how PRTG will handle overflow values. Some devices do not
handle internal buffer overflows correctly. This can cause false
peaks.
· Ignore overflow values (recommended): Ignore overflow
values and do not include them in the monitoring data.
· Handle overflow values as valid results: 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 delta sensors (recommended): Ignore
zero values and do not include them in the monitoring data.
· Handle zero values as valid results for delta 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
Define which kind of traffic counters PRTG will search for on a
device.
· Use 64-bit counters if available (recommended): The interface
scan will use 64-bit traffic counters, if available. This can avoid
buffer overflows in the devices.
· Use 32-bit counters only: The interface scan will always use
32-bit traffic counters, even if 64-bit counters are available. This
can lead to more reliable monitoring for some devices.
We recommend using the default value. If you experience
problems, change this option.
2011-08-12
201
Part VI: Ajax Web Interface—Device and Sensor Setup
SNMP Compatibility Options
Request Mode
Define which kind of request method PRTG uses for SNMP
sensors.
· Use multi 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.
Port Name Template
Define how the name of SNMP sensors created on a device will be
put together. Enter a template using several variables. When
adding new sensors, PRTG scans the interface for available
counters at certain OIDs. At each OID usually several fields are
available with interface descriptions. They are different for every
device/OID. PRTG will use the information in these fields to name
the sensors. If a field is empty or not available, an empty string is
added to the name. As default, ([port]) [ifalias] is set as port
name template, which will create a name such as (001) Ethernet1,
for example. You can use any field names available at a certain
OID of your device, among which are:
· [port]
· [ifalias]
· [ifname]
· [ifindex]
· [ifdescr]
Combine them as you like to obtain suitable sensor names. See
the More section below for more information about SNMP sensor
names.
Port Name Update
Define how PRTG will react if you change port names in your
physical device (e.g. a switch or router). Choose between:
§ Keep port names (use this if you edit the names in PRTG):
Do not automatically adjust sensor names. This is the best
option if you want to change names in PRTG manually.
§ Automatic sensor name update 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
202
Define which field will be used for SNMP interface identification.
Choose between:
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
SNMP Compatibility Options
§ Use ifAlias (recommended): For most devices ifAlias is the best
field to get unique interface names.
§ Use ifDescr: Use this option if the port order of your device
changes after a reboot, and there is no ifAlias field available. For
example, this is the best option for Cisco ASA devices. Note:
When using this option it is important that your device returns
unique interface names in the ifDescr field.
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.
HTTP Proxy Settings
HTTP Proxy Settings
The proxy settings determine how a sensor connects to a given
URL. You can enter data for a proxy server that will be used when
connecting via HTTP or HTTPS.
Name
Enter the IP address or DNS name of the proxy server to use. If
you leave this field empty, no proxy will be used.
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
If the proxy requires authentication, enter the username for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Password
If the proxy requires authentication, enter the password for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Scanning Interval
Scanning Interval
2011-08-12
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
203
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current object if its parent object is in a
Down status, or if it is paused by another dependency.
§ Select object: Pause the current object if its parent object is in
a Down status, or if it is paused by another dependency.
Additionally, pause the current object if a specific other object
in the device tree is in a Down status, or if it is paused by
another dependency. Select below.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
204
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current object will be
dependent on.
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
Unusual Detection
Unusual Detection
2011-08-12
Define if unusual detection is enabled for sensors. You can set the
behavior of unusual detection in the system settings.
205
Part VI: Ajax Web Interface—Device and Sensor Setup
Unusual Detection
· Enabled: Enable unusual detection. Sensors will turn to orange
color if unusual activity is detected.
· Disabled: Disable unusual detection. To not use the orange
sensor color.
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
Notifications tab to change sensor notification triggers. The defined triggers will be
inherited down to sensor level. For detailed information, please see Sensor Notifications
Settings 943 section.
Others
For more general information about settings, please see Object Settings
118
section.
More
Knowledge Base: How does PRTG compute CPU Index, Traffic Index and Response Time
Index?
§ http://www.paessler.com/knowledgebase/en/topic/313
Knowledge Base: How can I add my own device icons for use in the PRTG web interface?
§ http://www.paessler.com/knowledgebase/en/topic/7313
Knowledge Base: How can I change the defaults for names automatically generated for new
SNMP sensors?
§ http://www.paessler.com/knowledgebase/en/topic/7363
Knowledge Base: Automatically update port name and number for SNMP Traffic sensors when
the device changes them
§ http://www.paessler.com/knowledgebase/en/topic/25893
206
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
6.6
Group Settings
On a group's overview page, click on the Settings 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 Status option is not available in this
step.
You can change all settings in the group's Settings tab later.
Group Settings
The following settings are available in the Settings 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 185 group, so you can
inherit them to all other objects further down in the tree hierarchy.
Note: This documentation refers to the PRTG System Administrator 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 Group Settings
Group Name
Enter a meaningful name to identify the group. The name will be
shown by default in the devices tree and in all alarms.
Status
Choose if monitoring for this group is started or paused.
· Started: Monitor this group.
· Paused: Pause monitoring for this group. All sensors on all
devices in this group will be paused until this setting is changed
again.
Tags
2011-08-12
Enter one or more tags, separated by space or comma. You can
use tags to group objects and use tag-filtered views later on. Tags
are not case sensitive. We recommend using the default value.
You can add additional tags to it, if you like.
207
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Group 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).
Group Type
Sensor Management
Select which type of auto-discovery you would like to perform for
this group. Choose between:
· Manual (no auto-discovery): Do not auto-discover any sensors,
but only add sensors manually.
· Automatic device identification (standard, recommended):
Use a small set of auto-discovery templates. This will scan your
LAN and usually create a view standard sensors on your device.
· Automatic device identification (detailed, may create many
sensors: Use an extended set of auto-discovery templates. This
will scan your LAN and usually create many sensors on your
device.
· Automatic sensor creation using specific device templates:
Use specific auto-discovery templates only. Please select
templates below. This will scan your LAN and add sensors
defined in the template.
Device Template(s)
This option is only available if using specific device templates is
enabled above. Choose one or more device templates from the list
by adding a check mark in front of the respective template name.
Choose from:
§ Cisco Device (Generic)
§ DNS Server
§ FTP Server
§ Generic Device (PING only)
§ Generic Device (SNMP-enabled)
§ Generic Device (SNMP-enabled, Detailed)
§ HTTP Web Server
§ Hyper V Host Server
§ Linux/UNIX Device (SNMP or SSH enabled)
§ LocalhostRDP
§ Mail Server (Generic)
208
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
§ Mail Server (MS Exchange 2003)
§ Mail Server (MS Exchange 2007)
§ Misc. Details
§ Printer (HP)
§ Server (Compaq/HP agents)
§ Switch (Cisco Catalyst)
§ Switch (Cisco IOS Based)
§ Switch (HP Procurve)
§ UNIX/Linux Device
§ UPS (APC)
§ VMware ESX Server
§ Windows (Detailed via WMI)
§ Windows (via WMI)
§ Windows IIS (via SNMP)
§ XEN Server
Discovery Schedule
Define when the auto-discovery will be run. Choose between:
· Once: Perform auto-discovery only once. New devices and
sensors will be added once. You can run auto-discovery
manually any time using an object's context menu 136 .
· Hourly: Perform auto-discovery for new devices and sensors
every 60 minutes. Note: Please use this option with caution!
Frequently executed auto-discoveries might cause performance
issues, especially when large network segments are scanned
every hour.
· Daily: Perform auto-discovery for new devices and sensors every
24 hours. The first auto-discovery will run immediately, all other
discoveries will start on the time defined in the Auto-Discovery
Settings section of the System Administration—System and
Website 1044 settings.
· Weekly: Perform auto-discovery for new devices and sensors
every 7 days. The first auto-discovery will run immediately, all
other discoveries will start on the time defined in the
Auto-Discovery Settings section of the System
Administration—System and Website 1044 settings.
IP Selection Method
Define how you want to define the IP range for auto-discovery.
Choose between:
§ Class C base IP with start/end: Define a class C address
range.
2011-08-12
209
Part VI: Ajax Web Interface—Device and Sensor Setup
§ List of individual IPs: Enter individual IP addresses.
§ IP and subnet: Enter an IP address and subnet mask.
§ IP with octet range: Enter an IP address range for every IP octet
individually. With this, you can define very customizable IP
ranges.
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.
210
IP Base
This field is only visible if Class C network detection is selected
above. Enter a class C network as IP base for the auto-discovery.
Enter the first three octets of an IPv4 IP address, for example,
192.168.0
IP Range Start
This field is only visible if Class C network detection is selected
above. Enter the IP octet of the class C network specified above
from which PRTG will start the auto-discovery. This will complete
the IP base above to an IPv4 address. For example, enter 1 to
discover from 192.168.0.1.
IP Range End
This field is only visible if Class C network detection is selected
above. Enter the IP octet of the class C network specified above at
which PRTG will stop the auto-discovery. This will complete the IP
base above to an IPv4 address. For example, enter 254 to discover
up to 192.168.0.254.
IP List
This field is only visible if the IP list option is selected above. Enter
a list of IP addresses which the auto-discovery will scan. Enter
each address in a separate line.
IP and Subnet
This field is only visible if the IP and subnet option is selected
above. Enter an expression in the format address/subnet, e.g.
192.168.3.0/255.255.255.0. You can also use the short form like
192.168.3.0/24 in this example. PRTG will scan the complete host
range (without network and broadcast address) defined by the IP
address and the subnet mask.
IP with Octet Range
This field is only visible if the octet range option is selected
above. Enter an expression in the format a1.a2.a3.a4, where a1,
a2, a3, and a4 are each a number between 0-255, or a range with
two numbers and a hyphen like 1-127. All permutations of all
ranges are calculated, e.g. 10.0.1-10.1-100 results in 1,000
addresses that PRTG will scan during auto-discovery.
Name Resolution
Define how newly discovered devices will be monitored. This only
affects new devices. The setting for existing devices will be kept.
Choose between:
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
· Use DNS / WMI / SNMP names (recommended): Monitor newly
discovered devices via their DNS, WMI, or SNMP names (if
available).
· Use IP addresses: Monitor newly discovered devices via their IP
address.
We recommend using the default value.
Device Rescan
Define if you want to rescan known devices. Choose between:
· Skip auto-discovery for known devices/IPs (recommended):
Do not re-scan known devices or IP addresses, but only scan for
new devices/IPs when auto-discovering. This can avoid
re-creation of manually deleted sensors. PRTG will also avoid
adding devices that are already included elsewhere in your
configuration, e.g. in other groups.
· Perform auto-discovery for known devices/IPs: Re-scan
known devices and IP addresses with every auto-discovery. This
will re-create manually deleted sensors on existing devices.
We recommend using the default value.
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 185 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 975 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 112 (green - yellow orange - red). You can enter a full postal address, city and country
only, or latitude and longitude. 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.
Credentials for Windows Systems
Domain or Computer
Name
2011-08-12
Define the authority for Windows access. This is used for Windows
Management Instrumentation (WMI) and other sensors. If using a
Windows local user account, please enter the computer name
here. If using a Windows domain user account, please enter the
domain name here.
211
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for Windows Systems
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.
Credentials for Linux (SSH/WBEM) Systems
Username
Enter a login name for the Linux access via SSH and WBEM.
Usually, you will use credentials with administrator privileges.
Login
Define which authentication method will be used for login. Choose
between:
§ Login via Password: Provide a password for login. Enter below.
§ Login via Private Key: Provide a private key for authentication.
Paste below.
Password
This field is only visible if password login is selected above. Enter
a password for the Linux access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Private Key
This field is only visible if private key login is selected above.
Paste a private key into the field. 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 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 automatically (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
212
This setting is only visible if manual port selection is enabled
above. Enter the WBEM port number.
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for VMware/XEN Servers
User
Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password
Enter a password for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
VMware Protocol
Choose between:
· HTTPS (recommended): Use an SSL-encrypted connection to
VMware and XEN servers.
· HTTP: Use an unencrypted connection to VMware and XEN
servers.
Credentials for SNMP Devices
SNMP Version
Select the SNMP version that will be used for device connection.
Choose between:
· v1: Use the simple standard v1 protocol for SNMP connections.
This protocol only offers clear-text data transmission, but it is
usually supported by all devices.
· v2c: Use the more advanced v2c protocol for SNMP connections.
Data is still transferred as clear-text, but it supports 64-bit
counters.
· v3: Use the latest v3 protocol for SNMP connections. It provides
secure authentication and data encryption.
Note for SNMP v3: Due to internal limitations you can only
monitor a limited number of sensors per second using SNMP v3.
The limit is somewhere between 1 and 50 sensors per second
(depending on the SNMP latency of your network). This means that
using an interval of 60 seconds you are limited to between 60 and
3000 SNMP v3 sensors for each probe. If you experience an
increased "Interval Delay" or "Open Requests" reading of the probe
health sensor you need to distribute the load over multiple
probes. SNMP v1 and v2 do not have this limitation.
Community String
This setting is only visible if SNMP version v1 or v2c are enabled
above. Enter the community string of your devices. This is a kind
of "clear-text password" used for simple authentication. We
recommend using the default value.
Authentication Type
This setting is only visible if SNMP version v3 is enabled above.
Choose between:
· MD5: Use Message-Digest Algorithm 5 (MD5) for authentication.
2011-08-12
213
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for SNMP Devices
· SHA: Use Secure Hash Algorithm (SHA) for authentication.
Your device must be set to the same value.
User
This setting is only visible if SNMP version v3 is enabled above.
Enter a username for secure authentication. Your device must be
set to the same value.
Password
This setting is only visible if SNMP version v3 is enabled above.
Enter a password for secure authentication. Your device must be
set to the same value.
Data Encryption Key
(DES)
This setting is only visible if SNMP version v3 is enabled above.
Enter a Data Encryption Standard (DES) key here. If you provide a
key in this field, SNMP data packets will be enrypted using the DES
encryption algorithm, providing increased security. Your device
must be set to the same value. Note: If the key entered in this
field does not match the key configured in the target SNMP device
you will not get an error message! Please enter a string or leave
the field empty.
SNMP Port
Enter the port used for SNMP communication. We recommend
using the default value.
SNMP Timeout (sec.)
Enter a timeout in seconds for the request. If the reply takes
longer than this value the request is aborted and an error
message is triggered.
WMI Compatibility Options
When experiencing problems while monitoring via Windows Management Instrumentation
(WMI) sensors, you can set some compatibility options for trouble shooting.
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 interval (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.
214
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
WMI Compatibility Options
Timeout value (sec.)
This field is only visible if manually timeout method is selected
above. Specify the time the sensor will wait for the return of its
WMI query before aborting with an error message. Please enter an
integer value.
RPC server port
Specify the port which WMI uses for DCOM communication. We
recommend using the default value. Only if you change this port
on your system(s), please change it here.
SNMP Compatibility Options
When experiencing problems while monitoring via Simple Network Management Protocol
(SNMP) sensors, you can set some compatibility options for trouble shooting.
SNMP Delay (ms)
Add a time in milliseconds that will be waited between two SNMP
requests. This can help increase device compatibility. Please enter
an integer value. We recommend using the default value. If you
experience SNMP connection failures, please increase it.
Failed Requests
Define if an SNMP sensor will try again after a request fails.
· Retry (recommended): Try again if an SNMP request fails. This
can help prevent false error messages due to temporary timeout
failures.
· Do not retry: Do not retry if an SNMP request fails. With this
setting enabled an SNMP sensor will be put to error state earlier.
Overflow Values
Define how PRTG will handle overflow values. Some devices do not
handle internal buffer overflows correctly. This can cause false
peaks.
· Ignore overflow values (recommended): Ignore overflow
values and do not include them in the monitoring data.
· Handle overflow values as valid results: 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 delta sensors (recommended): Ignore
zero values and do not include them in the monitoring data.
2011-08-12
215
Part VI: Ajax Web Interface—Device and Sensor Setup
SNMP Compatibility Options
· Handle zero values as valid results for delta 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
Define which kind of traffic counters PRTG will search for on a
device.
· Use 64-bit counters if available (recommended): The interface
scan will use 64-bit traffic counters, if available. This can avoid
buffer overflows in the devices.
· Use 32-bit counters only: The interface scan will always use
32-bit traffic counters, even if 64-bit counters are available. This
can lead to more reliable monitoring for some devices.
We recommend using the default value. If you experience
problems, change this option.
Request Mode
Define which kind of request method PRTG uses for SNMP
sensors.
· Use multi 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.
Port Name Template
Define how the name of SNMP sensors created on a device will be
put together. Enter a template using several variables. When
adding new sensors, PRTG scans the interface for available
counters at certain OIDs. At each OID usually several fields are
available with interface descriptions. They are different for every
device/OID. PRTG will use the information in these fields to name
the sensors. If a field is empty or not available, an empty string is
added to the name. As default, ([port]) [ifalias] is set as port
name template, which will create a name such as (001) Ethernet1,
for example. You can use any field names available at a certain
OID of your device, among which are:
· [port]
· [ifalias]
· [ifname]
· [ifindex]
216
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
SNMP Compatibility Options
· [ifdescr]
Combine them as you like to obtain suitable sensor names. See
the More section below for more information about SNMP sensor
names.
Port Name Update
Define how PRTG will react if you change port names in your
physical device (e.g. a switch or router). Choose between:
§ Keep port names (use this if you edit the names in PRTG):
Do not automatically adjust sensor names. This is the best
option if you want to change names in PRTG manually.
§ Automatic sensor name update if name changes in device: If
PRTG detects changes of port names in your physical device it
will try to automatically adjust sensor names accordingly. For
detailed information please see More section below.
Port Identification
Define which field will be used for SNMP interface identification.
Choose between:
§ Use ifAlias (recommended): For most devices ifAlias is the best
field to get unique interface names.
§ Use ifDescr: Use this option if the port order of your device
changes after a reboot, and there is no ifAlias field available. For
example, this is the best option for Cisco ASA devices. Note:
When using this option it is important that your device returns
unique interface names in the ifDescr field.
2011-08-12
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.
217
Part VI: Ajax Web Interface—Device and Sensor Setup
HTTP Proxy Settings
HTTP Proxy Settings
The proxy settings determine how a sensor connects to a given
URL. You can enter data for a proxy server that will be used when
connecting via HTTP or HTTPS.
Name
Enter the IP address or DNS name of the proxy server to use. If
you leave this field empty, no proxy will be used.
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
If the proxy requires authentication, enter the username for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Password
If the proxy requires authentication, enter the password for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Scanning Interval
Scanning Interval
218
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current object if its parent object is in a
Down status, or if it is paused by another dependency.
§ Select object: Pause the current object if its parent object is in
a Down status, or if it is paused by another dependency.
Additionally, pause the current object if a specific other object
in the device tree is in a Down status, or if it is paused by
another dependency. Select below.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-08-12
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current object will be
dependent on.
219
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
Unusual Detection
Unusual Detection
220
Define if unusual detection is enabled for sensors. You can set the
behavior of unusual detection in the system settings.
2011-08-12
Part VI: Ajax Web Interface—Device and Sensor Setup
Unusual Detection
· Enabled: Enable unusual detection. Sensors will turn to orange
color if unusual activity is detected.
· Disabled: Disable unusual detection. To not use the orange
sensor color.
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
Notifications tab to change sensor notification triggers. The defined triggers will be
inherited down to sensor level. For detailed information, please see Sensor Notifications
Settings 943 section.
Others
For more general information about settings, please see Object Settings
118
section.
More
Knowledge Base: How does PRTG compute CPU Index, Traffic Index and Response Time
Index?
§ http://www.paessler.com/knowledgebase/en/topic/313
Knowledge Base: How can I add my own device icons for use in the PRTG web interface?
§ http://www.paessler.com/knowledgebase/en/topic/7313
Knowledge Base: How can I change the defaults for names automatically generated for new
SNMP sensors?
§ http://www.paessler.com/knowledgebase/en/topic/7363
Knowledge Base: Automatically update port name and number for SNMP Traffic sensors when
the device changes them
§ http://www.paessler.com/knowledgebase/en/topic/25893
2011-08-12
221
Part VI: Ajax Web Interface—Device and Sensor Setup
6.7
Device Settings
On a device's details page, click on the Settings 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 Status option is not available in this
step.
You can change all settings in the device's Settings tab later.
Device Settings
The following settings are available in the Settings 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 185 group, so you can
inherit them to all other objects further down in the tree hierarchy.
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 Multi-Edit Lists 964 section.
Note: This documentation refers to the PRTG System Administrator 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 Device Settings
Device Name
Enter a meaningful name to identify the device. The name will be
shown by default in the device tree and in all alarms.
Status
Choose if monitoring for this device is started or paused.
§ Started: Monitor this device.
§ Paused: Pause monitoring for this device. All sensors on it will
be paused until this setting is changed again.
IP Version
Define which IP protocol PRTG will use to connect to this device.
The setting is valid for all sensors created on this device. Choose
between:
§ Connect using IPv4: Use IP version 4 for all requests to this
device.
222
2011-10-21
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Device Settings
§ Connect using IPv6: Use IP version 6 for all requests to this
device.
IP Address/DNS Name
Enter the IP address (either v4 or v6, depending on your selection
above) or DNS name for the device. Most sensors created on this
device will inherit this setting and they will try to connect to this
address for monitoring. (However, some sensor types still have
their own setting for IP address/DNS name.)
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like.
Priority
Select a priority for the sensor. This setting determines where the
sensor will be placed in sensor lists. Top priority will be at the top
of a list. You can choose from one star (low priority) to five stars
(top priority).
Additional Device Information
Device Icon
Choose a device icon from the list. It will be shown in the device
tree. For information on how to add your custom icons, please see
the link in the More 235 section below.
Service URL
Specify a URL you would like to open directly when choosing
Device Tools | Go To Service URL from the device's context
menu 140 . For example, you can configure this option to call the
address http://www.example.com/service.html. Enter a valid URL
or leave the field empty.
Device Type
Sensor Management
Select which type of auto-discovery you would like to perform for
this device. Choose between:
§ Manual (no auto-discovery): Do not auto-discover any sensors,
but only add sensors manually.
§ Automatic device identification (standard, recommended):
Use a small set of auto-discovery templates. This will scan your
LAN and usually create a view standard sensors on your device.
2011-10-21
223
Part VI: Ajax Web Interface—Device and Sensor Setup
Device Type
§ Automatic device identification (detailed, may create many
sensors: Use an extended set of auto-discovery templates. This
will scan your LAN and usually create many sensors on your
device.
§ Automatic sensor creation using specific device templates:
Use specific auto-discovery templates only. Please select
templates below. This will scan your LAN and add sensors
defined in the template.
Discovery Schedule
This option is only visible if one of the auto-discovery options is
selected above. Define when the auto-discovery will be run.
Choose between:
§ Once: Perform auto-discovery only once. For existing devices,
this will initiate a one-time sensor update for the current device.
§ Hourly: Perform auto-discovery for new sensors every hour.
§ Daily: Perform auto-discovery for new sensors every day.
§ Weekly: Perform auto-discovery for new sensors every week.
Device Template(s)
This option is only visible if using specific device templates (last
option) is enabled above. Please choose one or more templates by
adding a check mark in front of the respective template name.
These will be used for auto-discovery on the current device.
Choose from:
§ Cisco Device (Generic)
§ DNS Server
§ FTP Server
§ Generic Device (PING only)
§ Generic Device (SNMP-enabled)
§ Generic Device (SNMP-enabled, Detailed)
§ HTTP Web Server
§ Hyper V Host Server
§ Linux/UNIX Device (SNMP or SSH enabled)
§ Mail Server (Generic)
§ Mail Server (MS Exchange)
§ NTP Server
§ Printer (HP)
§ RDP Server
224
2011-10-21
Part VI: Ajax Web Interface—Device and Sensor Setup
Device Type
§ Server (Compaq/HP agents)
§ Switch (Cisco Catalyst)
§ Switch (Cisco IOS Based)
§ Switch (HP Procurve)
§ UNIX/Linux Device
§ UPS (APC)
§ Virtuozzo Server
§ VMware ESX Server
§ Windows (Detailed via WMI)
§ Windows (via WMI)
§ Windows IIS (via SNMP)
§ XEN Server
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 185 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 975 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 112 (green - yellow orange - red). You can enter a full postal address, city and country
only, or latitude and longitude. 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.
Credentials for Windows Systems
Domain or Computer
Name
2011-10-21
Define the authority for Windows access. This is used for Windows
Management Instrumentation (WMI) and other sensors. If using a
Windows local user account, please enter the computer name
here. If using a Windows domain user account, please enter the
domain name here.
225
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for Windows Systems
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.
Credentials for Linux (SSH/WBEM) Systems
Username
Enter a login name for the Linux access via SSH and WBEM.
Usually, you will use credentials with administrator privileges.
Login
Define which authentication method will be used for login. Choose
between:
§ Login via Password: Provide a password for login. Enter below.
§ Login via Private Key: Provide a private key for authentication.
Paste below.
Password
This field is only visible if password login is selected above. Enter
a password for the Linux access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Private Key
This field is only visible if private key login is selected above.
Paste a private key into the field. 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 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 automatically (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
226
This setting is only visible if manual port selection is enabled
above. Enter the WBEM port number.
2011-10-21
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for VMware/XEN Servers
User
Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password
Enter a password for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
VMware Protocol
Choose between:
· HTTPS (recommended): Use an SSL-encrypted connection to
VMware and XEN servers.
· HTTP: Use an unencrypted connection to VMware and XEN
servers.
Credentials for SNMP Devices
SNMP Version
Select the SNMP version that will be used for device connection.
Choose between:
· v1: Use the simple standard v1 protocol for SNMP connections.
This protocol only offers clear-text data transmission, but it is
usually supported by all devices.
· v2c: Use the more advanced v2c protocol for SNMP connections.
Data is still transferred as clear-text, but it supports 64-bit
counters.
· v3: Use the latest v3 protocol for SNMP connections. It provides
secure authentication and data encryption.
Note for SNMP v3: Due to internal limitations you can only
monitor a limited number of sensors per second using SNMP v3.
The limit is somewhere between 1 and 50 sensors per second
(depending on the SNMP latency of your network). This means that
using an interval of 60 seconds you are limited to between 60 and
3000 SNMP v3 sensors for each probe. If you experience an
increased "Interval Delay" or "Open Requests" reading of the probe
health sensor you need to distribute the load over multiple
probes. SNMP v1 and v2 do not have this limitation.
Community String
This setting is only visible if SNMP version v1 or v2c are enabled
above. Enter the community string of your devices. This is a kind
of "clear-text password" used for simple authentication. We
recommend using the default value.
Authentication Type
This setting is only visible if SNMP version v3 is enabled above.
Choose between:
· MD5: Use Message-Digest Algorithm 5 (MD5) for authentication.
2011-10-21
227
Part VI: Ajax Web Interface—Device and Sensor Setup
Credentials for SNMP Devices
· SHA: Use Secure Hash Algorithm (SHA) for authentication.
Your device must be set to the same value.
User
This setting is only visible if SNMP version v3 is enabled above.
Enter a username for secure authentication. Your device must be
set to the same value.
Password
This setting is only visible if SNMP version v3 is enabled above.
Enter a password for secure authentication. Your device must be
set to the same value.
Data Encryption Key
(DES)
This setting is only visible if SNMP version v3 is enabled above.
Enter a Data Encryption Standard (DES) key here. If you provide a
key in this field, SNMP data packets will be enrypted using the DES
encryption algorithm, providing increased security. Your device
must be set to the same value. Note: If the key entered in this
field does not match the key configured in the target SNMP device
you will not get an error message! Please enter a string or leave
the field empty.
SNMP Port
Enter the port used for SNMP communication. We recommend
using the default value.
SNMP Timeout (sec.)
Enter a timeout in seconds for the request. If the reply takes
longer than this value the request is aborted and an error
message is triggered.
WMI Compatibility Options
When experiencing problems while monitoring via Windows Management Instrumentation
(WMI) sensors, you can set some compatibility options for trouble shooting.
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 interval (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.
228
2011-10-21
Part VI: Ajax Web Interface—Device and Sensor Setup
WMI Compatibility Options
Timeout value (sec.)
This field is only visible if manually timeout method is selected
above. Specify the time the sensor will wait for the return of its
WMI query before aborting with an error message. Please enter an
integer value.
RPC server port
Specify the port which WMI uses for DCOM communication. We
recommend using the default value. Only if you change this port
on your system(s), please change it here.
SNMP Compatibility Options
When experiencing problems while monitoring via Simple Network Management Protocol
(SNMP) sensors, you can set some compatibility options for trouble shooting.
SNMP Delay (ms)
Add a time in milliseconds that will be waited between two SNMP
requests. This can help increase device compatibility. Please enter
an integer value. We recommend using the default value. If you
experience SNMP connection failures, please increase it.
Failed Requests
Define if an SNMP sensor will try again after a request fails.
· Retry (recommended): Try again if an SNMP request fails. This
can help prevent false error messages due to temporary timeout
failures.
· Do not retry: Do not retry if an SNMP request fails. With this
setting enabled an SNMP sensor will be put to error state earlier.
Overflow Values
Define how PRTG will handle overflow values. Some devices do not
handle internal buffer overflows correctly. This can cause false
peaks.
· Ignore overflow values (recommended): Ignore overflow
values and do not include them in the monitoring data.
· Handle overflow values as valid results: 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 delta sensors (recommended): Ignore
zero values and do not include them in the monitoring data.
2011-10-21
229
Part VI: Ajax Web Interface—Device and Sensor Setup
SNMP Compatibility Options
· Handle zero values as valid results for delta 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
Define which kind of traffic counters PRTG will search for on a
device.
· Use 64-bit counters if available (recommended): The interface
scan will use 64-bit traffic counters, if available. This can avoid
buffer overflows in the devices.
· Use 32-bit counters only: The interface scan will always use
32-bit traffic counters, even if 64-bit counters are available. This
can lead to more reliable monitoring for some devices.
We recommend using the default value. If you experience
problems, change this option.
Request Mode
Define which kind of request method PRTG uses for SNMP
sensors.
· Use multi 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.
Port Name Template
Define how the name of SNMP sensors created on a device will be
put together. Enter a template using several variables. When
adding new sensors, PRTG scans the interface for available
counters at certain OIDs. At each OID usually several fields are
available with interface descriptions. They are different for every
device/OID. PRTG will use the information in these fields to name
the sensors. If a field is empty or not available, an empty string is
added to the name. As default, ([port]) [ifalias] is set as port
name template, which will create a name such as (001) Ethernet1,
for example. You can use any field names available at a certain
OID of your device, among which are:
· [port]
· [ifalias]
· [ifname]
· [ifindex]
230
2011-10-21
Part VI: Ajax Web Interface—Device and Sensor Setup
SNMP Compatibility Options
· [ifdescr]
Combine them as you like to obtain suitable sensor names. See
the More section below for more information about SNMP sensor
names.
Port Name Update
Define how PRTG will react if you change port names in your
physical device (e.g. a switch or router). Choose between:
§ Keep port names (use this if you edit the names in PRTG):
Do not automatically adjust sensor names. This is the best
option if you want to change names in PRTG manually.
§ Automatic sensor name update if name changes in device: If
PRTG detects changes of port names in your physical device it
will try to automatically adjust sensor names accordingly. For
detailed information please see More section below.
Port Identification
Define which field will be used for SNMP interface identification.
Choose between:
§ Use ifAlias (recommended): For most devices ifAlias is the best
field to get unique interface names.
§ Use ifDescr: Use this option if the port order of your device
changes after a reboot, and there is no ifAlias field available. For
example, this is the best option for Cisco ASA devices. Note:
When using this option it is important that your device returns
unique interface names in the ifDescr field.
2011-10-21
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.
231
Part VI: Ajax Web Interface—Device and Sensor Setup
HTTP Proxy Settings
HTTP Proxy Settings
The proxy settings determine how a sensor connects to a given
URL. You can enter data for a proxy server that will be used when
connecting via HTTP or HTTPS.
Name
Enter the IP address or DNS name of the proxy server to use. If
you leave this field empty, no proxy will be used.
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
If the proxy requires authentication, enter the username for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Password
If the proxy requires authentication, enter the password for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Scanning Interval
Scanning Interval
232
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-21
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current object if its parent object is in a
Down status, or if it is paused by another dependency.
§ Select object: Pause the current object if its parent object is in
a Down status, or if it is paused by another dependency.
Additionally, pause the current object if a specific other object
in the device tree is in a Down status, or if it is paused by
another dependency. Select below.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-21
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current object will be
dependent on.
233
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
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!
234
2011-10-21
Part VI: Ajax Web Interface—Device and Sensor Setup
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
Notifications tab to change sensor notification triggers. The defined triggers will be
inherited down to sensor level. For detailed information, please see Sensor Notifications
Settings 943 section.
Others
For more general information about settings, please see Object Settings
118
section.
More
Knowledge Base: How does PRTG compute CPU Index, Traffic Index and Response Time
Index?
§ http://www.paessler.com/knowledgebase/en/topic/313
Knowledge Base: How can I add my own device icons for use in the PRTG web interface?
§ http://www.paessler.com/knowledgebase/en/topic/7313
Knowledge Base: How can I change the defaults for names automatically generated for new
SNMP sensors?
§ http://www.paessler.com/knowledgebase/en/topic/7363
Knowledge Base: Automatically update port name and number for SNMP Traffic sensors when
the device changes them
§ http://www.paessler.com/knowledgebase/en/topic/25893
2011-10-21
235
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8
Sensor Settings
There are more than 110 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’re
familiar with the interface, you will probably enter the first letters of a sensor type's name
into the Search field in the upper left corner and get to a sensor even faster.
Available Sensor Types
There is a dedicated manual section for every sensor with details about the available
settings. For more information, please see List of Available Sensors 237 section.
For sensor settings, there is also multi-edit available. This enables you to change properties
of many sensors at a time. For more details, please see Multi-Edit Lists 964 section.
Sensor Settings Overview
For information about sensor settings, please see the following sections:
· Sensor Settings
236
· List of Available Sensor Types
237
· Additional Sensor Types (Custom Sensors)
· Sensor Channels Settings
938
· Sensor Notifications Settings
236
935
943
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.1 List of Available Sensor Types
This chapter simply lists all available sensors, arranged both by different categories and in
alphabetical order. Note: In the Add a Sensor 182 assistant, PRTG offers you various options
to filter for fitting sensor types easily.
§ Common Sensors
237
§ Bandwidth Monitoring Sensors
§ Web Servers (HTTP) Sensors
§ SNMP Sensors
237
238
238
§ Windows/WMI Sensors
239
§ Linux/Unix/OS X Sensors
§ Virtual Servers Sensors
§ Mail Servers Sensors
240
240
240
§ SQL Database Servers Sensors
§ File Servers Sensors
241
§ Various Servers Sensors
§ VoIP and QoS Sensors
§ Hardware Sensors
§ Custom Sensors
241
241
242
242
242
§ All Sensors in Alphabetical Order
§ More
243
246
Common Sensors
§ HTTP Sensor
342
§ Ping Sensor
503
§ Port Sensor
531
§ SNMP Traffic Sensor
662
§ WMI Network Card Sensor
856
Bandwidth Monitoring Sensors
§ List of Available Sensor Types
§ jFlow V5 Sensor
425
§ jFlow V5 (Custom) Sensor
2011-11-15
237
432
237
Part VI: Ajax Web Interface—Device and Sensor Setup
§ NetFlow V5 Sensor
456
§ NetFlow V5 (Custom) Sensor
§ NetFlow V9 Sensor
463
470
§ NetFlow V9 (Custom) Sensor
§ Packet Sniffer Sensor
477
490
§ Packet Sniffer (Custom) Sensor
§ sFlow Sensor
497
569
§ sFlow (Custom) Sensor
§ SNMP Library Sensor
§ SNMP Traffic Sensor
576
635
662
§ WMI Network Card Sensor
856
Web Servers (HTTP) Sensors
§ HTTP Sensor
342
§ HTTP Advanced Sensor
§ HTTP Content Sensor
348
357
§ HTTP Full Web Page Sensor
364
§ HTTP SSL Certificate Expiry Sensor
§ HTTP Transaction Sensor
369
374
§ HTTP XML/REST Value Sensor
382
SNMP Sensors
§ SNMP APC Hardware Sensor
§ SNMP Custom Sensor
608
613
§ SNMP Custom String Sensor
619
§ SNMP Dell Hardware Sensor
625
§ SNMP HP LaserJet Hardware Sensor
§ SNMP Library Sensor
635
§ SNMP Linux Disk Free Sensor
643
§ SNMP Linux Load Average Sensor
§ SNMP Linux Meminfo Sensor
653
§ SNMP System Uptime Sensor
658
§ SNMP Traffic Sensor
648
662
§ SNMP Trap Receiver Sensor
238
630
669
2011-11-15
Part VI: Ajax Web Interface—Device and Sensor Setup
Windows/WMI Sensors
§ Active Directory Replication Errors Sensor
§ Event Log (Windows API) Sensor
§ Windows Last Update Sensor
288
750
§ Windows Logged In Users Sensor
755
§ Windows MSMQ Queue Length Sensor
§ Windows Print Queue Sensor
§ Windows Registry Sensor
§ WMI Custom Sensor
771
778
785
790
§ WMI Event Log Sensor
797
§ WMI Exchange Server Sensor
§ WMI File Sensor
760
766
§ Windows Scheduled Task Sensor
§ WMI CPU Load Sensor
247
804
811
§ WMI Free Disk Space (Multi Drive) Sensor
§ WMI IIS 6.0 SMTP Received Sensor
§ WMI IIS 6.0 SMTP Sent Sensor
§ WMI Logical Disk Sensor
§ WMI Memory Sensor
825
830
835
841
§ WMI Microsoft SQL Server 2005 Sensor
846
§ WMI Microsoft SQL Server 2008 Sensor
851
§ WMI Network Card Sensor
§ WMI Pagefile Sensor
856
862
§ WMI Physical Disk Sensor
§ WMI Process Sensor
866
872
§ WMI Security Center Sensor
§ WMI Service Sensor
§ WMI Share Sensor
817
877
882
887
§ WMI System Uptime Sensor
893
§ WMI Terminal Services (Windows 2008) Sensor
897
§ WMI Terminal Services (Windows XP/Vista/2003) Sensor
§ WMI Vital System Data (V2) Sensor
§ WMI Volume Sensor
2011-11-15
901
905
911
239
Part VI: Ajax Web Interface—Device and Sensor Setup
§ WMI Windows Version Sensor
§ WSUS Statistics Sensor
917
923
Linux/Unix/OS X Sensors
§ List of Available Sensor Types
§ SNMP Linux Disk Free Sensor
237
643
§ SNMP Linux Load Average Sensor
§ SNMP Linux Meminfo Sensor
§ SSH Disk Free Sensor
653
679
§ SSH INodes Free Sensor
684
§ SSH Load Average Sensor
§ WBEM Custom Sensor
648
690
745
Virtual Servers Sensors
§ Amazon CloudWatch Sensor
§ Hyper-V Host Server Sensor
260
389
§ Hyper-V Virtual Machine Sensor
393
§ Hyper-V Virtual Network Adapter Sensor
§ Hyper-V Virtual Storage Device Sensor
§ SSH VMWare ESX(i) Disk Sensor
720
§ Virtuozzo Container Network Sensor
725
730
§ VMware Host Server (SOAP) Sensor
735
§ VMware Virtual Machine (SOAP) Sensor
§ Xen Virtual Machine Sensor
405
700
§ Virtuozzo Container Disk Sensor
§ VMware Host Hardware (WBEM)
399
739
930
Mail Servers Sensors
§ IMAP Sensor
409
§ IP on DNS Blacklist Sensor
§ POP3 Sensor
519
§ POP3 Email Count Sensor
§ SMTP Sensor
420
525
588
§ SMTP&IMAP Round Trip Sensor
240
594
2011-11-15
Part VI: Ajax Web Interface—Device and Sensor Setup
§ SMTP&POP3 Round Trip Sensor
§ WMI Exchange Server Sensor
601
804
§ WMI IIS 6.0 SMTP Received Sensor
§ WMI IIS 6.0 SMTP Sent Sensor
825
830
SQL Database Servers Sensors
§ ADO SQL Sensor
253
§ Microsoft SQL Sensor
§ MySQL Sensor
443
450
§ Oracle SQL Sensor
484
§ WMI Microsoft SQL Server 2005 Sensor
846
§ WMI Microsoft SQL Server 2008 Sensor
851
File Servers Sensors
§ File Sensor
308
§ File Content Sensor
§ Folder Sensor
§ FTP Sensor
314
320
326
§ FTP Server File Count Sensor
331
§ INI File Content Check Sensor
§ Share Disk Free Sensor
§ TFTP Sensor
414
582
711
§ WMI File Sensor
811
§ WMI Free Disk Space (Multi Drive) Sensor
§ WMI Volume Sensor
817
911
Various Servers Sensors
§ DHCP Sensor
§ DNS Sensor
279
283
§ HDD Health Sensor
§ LDAP Sensor
§ Ping Sensor
439
503
§ Ping Jitter Sensor
§ Pingdom Sensor
2011-11-15
337
509
514
241
Part VI: Ajax Web Interface—Device and Sensor Setup
§ Port Sensor
531
§ RADIUS Sensor
547
§ RDP (Remote Desktop) Sensor
§ SNMP Trap Receiver Sensor
§ SNTP Sensor
552
669
675
§ Syslog Receiver Sensor
705
§ Traceroute Hop Count Sensor
716
VoIP and QoS Sensors
§ Cisco IP SLA Sensor
266
§ QoS (Quality of Service) One Way Sensor
537
§ QoS (Quality of Service) Round Trip Sensor
542
Hardware Parameter Sensors
§ HDD Health Sensor
337
§ SNMP APC Hardware Sensor
608
§ SNMP Dell Hardware Sensor
625
§ SNMP HP LaserJet Hardware Sensor
§ SNMP Library Sensor
630
635
Custom Sensors
§ EXE/Script Sensor
294
§ EXE/Script Advanced Sensor
§ jFlow V5 (Custom) Sensor
301
432
§ NetFlow V5 (Custom) Sensor
463
§ NetFlow V9 (Custom) Sensor
477
§ Packet Sniffer (Custom) Sensor
§ Pingdom Sensor
514
§ Sensor Factory Sensor
556
§ sFlow (Custom) Sensor
§ SNMP Custom Sensor
576
613
§ SNMP Custom String Sensor
§ WBEM Custom Sensor
§ WMI Custom Sensor
242
497
619
745
790
2011-11-15
Part VI: Ajax Web Interface—Device and Sensor Setup
All Sensors in Alphabetical Order
§ Active Directory Replication Errors Sensor
§ ADO SQL Sensor
253
§ Amazon CloudWatch Sensor
§ Cisco IP SLA Sensor
260
266
§ Cluster Probe Health Sensor
§ Core/Probe Health Sensor
§ DHCP Sensor
§ DNS Sensor
271
275
279
283
§ Event Log (Windows API) Sensor
§ EXE/Script Sensor
301
308
§ File Content Sensor
§ Folder Sensor
§ FTP Sensor
288
294
§ EXE/Script Advanced Sensor
§ File Sensor
314
320
326
§ FTP Server File Count Sensor
§ HDD Health Sensor
§ HTTP Sensor
331
337
342
§ HTTP Advanced Sensor
§ HTTP Content Sensor
348
357
§ HTTP Full Web Page Sensor
364
§ HTTP SSL Certificate Expiry Sensor
§ HTTP Transaction Sensor
369
374
§ HTTP XML/REST Value Sensor
§ Hyper-V Host Server Sensor
382
389
§ Hyper-V Virtual Machine Sensor
393
§ Hyper-V Virtual Network Adapter Sensor
§ Hyper-V Virtual Storage Device Sensor
§ IMAP Sensor
399
405
409
§ INI File Content Check Sensor
§ IP on DNS Blacklist Sensor
§ jFlow V5 Sensor
2011-11-15
247
414
420
425
243
Part VI: Ajax Web Interface—Device and Sensor Setup
§ jFlow V5 (Custom) Sensor
§ LDAP Sensor
432
439
§ Microsoft SQL Sensor
§ MySQL Sensor
443
450
§ NetFlow V5 Sensor
456
§ NetFlow V5 (Custom) Sensor
§ NetFlow V9 Sensor
470
§ NetFlow V9 (Custom) Sensor
§ Oracle SQL Sensor
463
477
484
§ Packet Sniffer Sensor
490
§ Packet Sniffer (Custom) Sensor
§ Ping Sensor
503
§ Ping Jitter Sensor
§ Pingdom Sensor
§ POP3 Sensor
509
514
519
§ POP3 Email Count Sensor
§ Port Sensor
497
525
531
§ QoS (Quality of Service) One Way Sensor
537
§ QoS (Quality of Service) Round Trip Sensor
§ RADIUS Sensor
547
§ RDP (Remote Desktop) Sensor
§ Sensor Factory Sensor
§ sFlow Sensor
552
556
569
§ sFlow (Custom) Sensor
576
§ Share Disk Free Sensor
582
§ SMTP Sensor
588
§ SMTP&IMAP Round Trip Sensor
594
§ SMTP&POP3 Round Trip Sensor
601
§ SNMP APC Hardware Sensor
§ SNMP Custom Sensor
608
613
§ SNMP Custom String Sensor
619
§ SNMP Dell Hardware Sensor
625
§ SNMP HP LaserJet Hardware Sensor
244
542
630
2011-11-15
Part VI: Ajax Web Interface—Device and Sensor Setup
§ SNMP Library Sensor
635
§ SNMP Linux Disk Free Sensor
643
§ SNMP Linux Load Average Sensor
§ SNMP Linux Meminfo Sensor
653
§ SNMP System Uptime Sensor
658
§ SNMP Traffic Sensor
662
§ SNMP Trap Receiver Sensor
§ SNTP Sensor
669
675
§ SSH Disk Free Sensor
679
§ SSH INodes Free Sensor
684
§ SSH Load Average Sensor
§ SSH Meminfo Sensor
690
695
§ SSH VMWare ESX(i) Disk Sensor
§ Syslog Receiver Sensor
§ TFTP Sensor
648
700
705
711
§ Traceroute Hop Count Sensor
716
§ Virtuozzo Container Disk Sensor
720
§ Virtuozzo Container Network Sensor
§ VMware Host Hardware (WBEM)
725
730
§ VMware Host Server (SOAP) Sensor
735
§ VMware Virtual Machine (SOAP) Sensor
§ WBEM Custom Sensor
745
§ Windows Last Update Sensor
750
§ Windows Logged In Users Sensor
755
§ Windows MSMQ Queue Length Sensor
§ Windows Print Queue Sensor
§ Windows Registry Sensor
§ WMI Custom Sensor
771
785
797
§ WMI Exchange Server Sensor
2011-11-15
778
790
§ WMI Event Log Sensor
§ WMI File Sensor
760
766
§ Windows Scheduled Task Sensor
§ WMI CPU Load Sensor
739
804
811
245
Part VI: Ajax Web Interface—Device and Sensor Setup
§ WMI Free Disk Space (Multi Drive) Sensor
§ WMI IIS 6.0 SMTP Received Sensor
§ WMI IIS 6.0 SMTP Sent Sensor
§ WMI Logical Disk Sensor
§ WMI Memory Sensor
825
830
835
841
§ WMI Microsoft SQL Server 2005 Sensor
846
§ WMI Microsoft SQL Server 2008 Sensor
851
§ WMI Network Card Sensor
§ WMI Pagefile Sensor
856
862
§ WMI Physical Disk Sensor
§ WMI Process Sensor
866
872
§ WMI Security Center Sensor
§ WMI Service Sensor
§ WMI Share Sensor
817
877
882
887
§ WMI System Uptime Sensor
893
§ WMI Terminal Services (Windows 2008) Sensor
897
§ WMI Terminal Services (Windows XP/Vista/2003) Sensor
§ WMI Vital System Data (V2) Sensor
§ WMI Volume Sensor
901
905
911
§ WMI Windows Version Sensor
§ WSUS Statistics Sensor
917
923
§ Xen Virtual Machine Sensor
930
More
Did not find what you're looking for? Have a look into the Additional Sensor Types (Custom
Sensors) 935 section.
246
2011-11-15
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.2 Active Directory Replication Errors Sensor
The Active Directory Replication Errors sensor uses its parent device's Windows credentials to
find the first domain controller of the domain and retrieves a list of all available domain
controllers. It then compares the returned lists and reports the number of errors found.
Please make sure you enter valid domain credentials in the parent device's settings.
Requirement: .NET Framework
This sensor type requires the Microsoft .NET Framework to be installed on the computer
running the PRTG probe: Either on the local system (on every node, if in a cluster), or on the
system running the remote probe 1194 . If the framework is missing, you cannot create this
sensor.
Required .NET version: 2.0.
Requirement: Windows Credentials
For this sensor type, Windows credentials must be defined for the device you want to use the
sensor on. In the parent device's Credentials for Windows Systems settings, please prefer
using Windows domain credentials. Note: If you use local credentials, please make sure the
same Windows user account (with same username and password) exists on both the system
running the PRTG probe and the target computer. Otherwise the sensor cannot connect
correctly.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
2011-10-21
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
247
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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
Timeout (sec.)
Define a timeout in seconds for the entire process. If the reply
takes longer than this value the request is aborted and an error
message is triggered. Please enter an integer value.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
248
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
2011-10-21
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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.
Scanning Interval
Scanning Interval
2011-10-21
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
249
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
250
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-21
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
2011-10-21
251
Part VI: Ajax Web Interface—Device and Sensor Setup
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
252
118
section.
2011-10-21
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.3 ADO SQL Sensor
The ADO SQL sensor monitors a database using an ActiveX Data Objects (ADO) connection. It
connects to the server and shows the response time. Additionally, it can read the number of
records and a value.
Note: For security reasons, you can only create a sensor on a device for which Windows
Credentials have been defined. With these credentials, the PRTG probe must be able to
connect to the Windows domain. If you don't enter valid credentials, you will get an Access
denied error message when scanning. For detailed information, please see More 258 section
below.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-17
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
253
Part VI: Ajax Web Interface—Device and Sensor Setup
ADO Specific Data
Connectionstring
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
258 section below.
Data
SQL-Expression
Enter the SQL expression that will be queried from the database.
For example, such an expression could be: SELECT AVG(UnitPrice)
FROM Products. Note: When a cursor is returned (i.e. with a
SELECT statement), only the first row of data will be processed.
Postprocessing
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 string 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.
§ Monitor 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 943 whenever a sensor value changes.
Condition "Warning"
This field is only visible if numeric results is enabled above. Define
a condition of the returned numeric SQL result set that will set the
sensor to a Warning status. Choose between:
§ none: Do not set the sensor to Warning status for any
condition.
§ equals: Result set must be the same as the value provided
below.
§ is above: Result set must be above the value provided below.
§ lower than: Result set must be below the value provided below.
§ does not equal: Result set must be unequal to the value
provided below.
254
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Note: This threshold check the SQL result set only. You can set
additional thresholds in the sensor's channel settings 938 .
Value
This field is only visible if numeric results is enabled above. Enter
a value of the returned numeric SQL result set that will set the
sensor into a Warning status. Please enter an integer or float
value.
Condition "Down"
This field is only visible if numeric results is enabled above. Define
a condition of the returned numeric SQL result set that will set the
sensor to a Down status. Choose between:
§ none: Do not set the sensor to Down status for any condition.
§ equals: Result set must be the same as the value provided
below.
§ is above: Result set must be above the value provided below.
§ lower than: Result set must be below the value provided below.
§ does not equal: Result set must be unequal to the value
provided below.
Note: This threshold check the SQL result set only. You can set
additional thresholds in the sensor's channel settings 938 .
Value
This field is only visible if numeric results is enabled above. Enter
a value of the returned numeric SQL result set that will set the
sensor to a Down status. Please enter an integer value.
Response must
include
This field is only visible if string results is enabled above. Enter a
string that must be part of the returned SQL string. If it is not, the
sensor will be set to an error state. Please enter a string or leave
the field empty.
Response must not
include
This field is only visible if string results is enabled above. Enter a
string that must not be part of the returned SQL string. If it is, the
sensor will be set to an error state. Please enter a string or leave
the field empty.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
2011-10-17
255
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
256
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
257
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
More
Knowledge Base: Monitoring (Almost) Any SQL Server Through ADO with PRTG Network
Monitor
§ http://www.paessler.com/knowledgebase/en/topic/2053
Knowledge Base: How do I correctly configure credentials for ADO SQL sensors?
§ http://www.paessler.com/knowledgebase/en/topic/13103
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
258
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-17
118
section.
259
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.4 Amazon CloudWatch Sensor
The Amazon CloudWatch sensor monitors performance of an Amazon EC2 computing
instance using Amazon CloudWatch. The sensor shows CPU uitilization, 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 e.g. using Amazon's AWS console).
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
260
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Amazon CloudWatch Specific
Timeout
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.
Period (Interval)
Define in what granularity you want to receive datapoints from
CloudWatch. Choose between:
· 1 Minute
· 2 Minutes
· 5 Minutes
· 10 Minutes
AWS Access Key ID
Enter your access key. You can obtain in from aws.amazon.com.
AWS Secret Access Key
Enter your secret access key. You can obtain in from
aws.amazon.com.
Instance
Enter the ID of the instance this sensor will monitor.
Region
Select the region in which the instance to be monitored is
running. Choose between:
· US-West (USA)
· US-East (USA)
· EU-West (Europe)
· AP-Southeast (Asia Pacific)
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
2011-10-17
261
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
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.
262
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
263
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
264
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-17
118
section.
265
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.5 Cisco IP SLA Sensor
The Cisco IP SLA sensor monitors Voice over IP (VoIP) network parameters using IP Service
Level Agreement (SLA) from Cisco via Simple Network Management Protocol (SNMP). It shows
different aspects provided by the queried device.
For a general introduction to the technology behind Quality of Service monitoring, please
see Monitoring Quality of Service 1144 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings 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
A list of possible SLA types is shown. The list options depend on
the configuration of the queried device. If you're missing a type
here, please check your device's configuration. To add an SLA type
to your monitoring, add a check mark in front of the respective
line. For each selection one SLA sensor will be created. They are
named automatically. PRTG can support the following operations:
§ echo
§ pathEcho
§ fileIO
§ script
§ udpEcho
§ tcpConnect
§ http
§ dns
§ jitter
§ dlsw
§ dhcp
§ ftp
§ path-jitter *
266
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
IP SLA Specific
Note: Packet Loss values are summarized, but have no explicit
channel for Source-->Destination or Destination-->Source values
* Available for PRTG v8.3 or later
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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)
These fields show SLA specific settings provided by the queried
SLA device. Once a sensor is created this value cannot be
changed. It is shown for reference purposes only. If you need to
change this, please add the sensor anew.
Owner
Frequency
2011-10-17
267
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
268
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
269
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
270
118
section.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.6 Cluster Probe Health Sensor
The Cluster Probe Health sensor is a system device indicating PRTG's own system health
status. It is created automatically with a PRTG cluster installation and cannot be deleted. It
measures various internal system parameters of the cluster system and the probe's internal
processes and then computes a resulting value. Frequent or repeated health values below
100 % should be investigated, please check the sensor's channels for details.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
2011-10-17
271
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
272
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
2011-10-17
273
Part VI: Ajax Web Interface—Device and Sensor Setup
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
274
118
section.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.7 Core/Probe Health Sensor
The Core/Probe Health sensor is a system device indicating PRTG's own system health status.
It is created automatically with your PRTG installation and cannot be deleted. It measures
various internal system parameters of the probe system hardware and the probe's internal
processes and then computes a resulting value. Frequent or repeated health values below
100 % should be investigated, please check the sensor's channels for details.
For detailed information on the different channels, please activate the help box when in the
sensor's Overview tab. A box will appear at the end of the page, explaining the meaning of
the different channels.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
2011-10-17
275
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
276
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
2011-10-17
277
Part VI: Ajax Web Interface—Device and Sensor Setup
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
278
118
section.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.8 DHCP Sensor
The DHCP sensor monitors a Dynamic Host Configuration Protocol (DHCP) server. It sends a
broadcast message to the network and waits for a DHCP server to respond. If a server
responds the sensor shows both the address of the server and the offered IP in the sensor's
Message field. The sensor's channels include response time (msec) and the lease time given
by the server.
This sensor can be set up on a Probe Device only!
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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
Timeout (sec)
2011-10-17
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.
279
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
280
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
281
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
282
118
section.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.9 DNS Sensor
The DNS sensor monitors a Domain Name Service (DNS) server. It resolves a domain name
and compares it to a given IP address. The sensor shows the response time and goes to an
error state if the DNS server does not resolve a given domain name correctly.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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)
2011-10-31
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.
283
Part VI: Ajax Web Interface—Device and Sensor Setup
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 will 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)
§ Authoritative name server (NS)
§ Start of a zone of authority marker (SOA)
§ Domain name pointer (PTR)
§ Mail exchange (MX)
§ Canonical name for an alias (CNAME)
Check Result
Define if the result received from the DNS server will be checked.
Choose between:
§ Ignore result: Any valid answer of the DNS server will be
accepted by the sensor.
§ Check result: Check if the response contains certain strings.
Define below.
Value
This field is only visible if result checking is enabled above. Enter
elements that must be contained in the response of the DNS
server. Enter each entry in one line. At least one of the elements
must be contained in the received result. If none of the element
matches the response, the sensor will show a red Down status.
For example, you can enter an IP address here if your Domain
field contains a host name. Only if the host name is resolved to
the correct IP address your sensor will show a green Up status.
Write Result
Define what will be done with the results the sensor receives.
Choose between:
§ Discard sensor result: Do not store the results.
284
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
DNS Specific
§ Write sensor result to disk (Filename: "Result of Sensor
(ID].txt"): 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 Data Storage 1202 section.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-31
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
285
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
286
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-31
118
section.
287
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.10 Event Log (Windows API) Sensor
The Event Log (Windows API) sensor monitors Event Log entries using Windows Application
Programming Interface (API). It shows the number of new records per second (speed).
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Windows API Event Log specific
Log file
Specify the log file the sensor will monitor. The Windows event log
provides several different log files. A drop down list specific to
your system is shown. Please select a log file from the list. Choose
between:
· Application
· System
· Security
· Directory Service
· DNS Server
· File Replication Service
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
288
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
Filter Event Log Entries
Filter by Source
Filter all received events for a certain event source. If enabled,
only messages matching the defined value will be considered by
the sensor. Choose between:
· Off: Do not filter by event source.
· On: Enable filtering by event source.
Match String (Event
Source)
This field is only visible if filtering is enabled above. Enter a
source from which the events are to come from. Only events from
a source matching this string will be regarded, others ignored.
You can also 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. Please
enter a string.
Filter by ID
Filter all received events for a certain event ID. If enabled, only
messages matching the defined value(s) will be considered by the
sensor. Choose between:
· Off: Do not filter by event ID.
· On: Enable filtering by event ID.
2011-10-17
Match Value (Event ID)
This field is only visible if filtering is enabled above. Enter one or
more event IDs (comma separated) from which the events are to
come from. 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 enabled,
only messages matching the defined value will be considered by
the sensor. Choose between:
289
Part VI: Ajax Web Interface—Device and Sensor Setup
Filter Event Log Entries
· Off: Do not filter by event category.
· On: Enable filtering by event category.
Match String (Event
Category)
This field is only visible if filtering is enabled above. Enter a
category which the events are to have. Only events with a category
matching this string will be regarded. You can also 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 %N% for any event
category containing the character N. Please enter a string.
Filter by Event User
Filter all received events for a certain event user. If enabled, only
messages matching the defined value will be considered by the
sensor. Choose between:
· Off: Do not filter by event user.
· On: Enable filtering by event user.
Match String (Event
User)
This field is only visible if filtering is enabled above. Enter a user
name which the event are to be assigned to. Only events with a
user name matching this string will be regarded. You can also 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 A% for
any user name starting with the character A. Please enter a string.
Filter by Event
Computer
Filter all received events for a certain event computer. If enabled,
only messages matching the defined value will be considered by
the sensor. Choose between:
· Off: Do not filter by event computer.
· On: Enable filtering by event computer.
Match String (Event
Computer)
This field is only visible if filtering is enabled above. Enter a
computer name which the events are to be assigned to. Only
events with a computer name matching this string will be
regarded. You can also 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. Please enter a
string.
Filter by Event
Message
Filter all received events for a certain event message. If enabled,
only messages matching the defined value will be considered by
the sensor. Choose between:
· Off: Do not filter by event message.
· On: Enable filtering by event message.
290
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Filter Event Log Entries
Match String (Event
Message)
This field is only visible if filtering is enabled above. Enter a
message which the event must contain. Only events with a
message matching this string will be regarded. 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 here. Please enter a string.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
291
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
292
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-17
118
section.
293
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.11 EXE/Script Sensor
The EXE/Script sensor runs an executable file (EXE, DLL) or a script (batch file, VBScript,
Powershell) on the computer running the local or remote probe. This option is provided as
part of PRTG's Application Programming Interface (API). The sensor shows the execution
time, and can show one value returned by the executable file or script (in one channel only).
For details about the return value format please see the Application Programming Interface
(API) definition linked in the More 299 section below.
Note: The executable or script file must be stored on the system of the probe the sensor is
created on: If used on a remote probe, the file must be stored on the system running the
remote probe. In a cluster setup, please copy the file to every cluster node.
Note: If you want to execute a custom Windows Management Instrumentation Query
Language (WQL) script, please use the WMI Custom Sensor 790 .
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
294
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Settings
EXE/Script
Select an executable file from the list. It will be executed with
every scanning interval. In this list, files in the corresponding
/Custom Sensors/EXE sub-directory of the probe system's PRTG
installation are shown. In order for the files to appear in this list,
please store them into this folder. Store files ending in BAT, CMD,
DLL, EXE, PS1, and VBS. In order for the sensor to show the right
status, your files must use the right format for the returned
values. For detailed information on how to build custom sensors,
please see the API documentation (Application Programming
Interface (API) Definition 1185 ).
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 Cluster Probe, please
copy your files to every cluster node installation.
Parameters
If your executable or script file catches command line parameters,
you can define them here. Placeholders can be used as well. For a
full list of all placeholders please see the API documentation (
Application Programming Interface (API) Definition 1185 ). Please
enter a string or leave the field empty.
Environment
Choose if PRTG's command line parameters will also be available
as environment parameters.
§ Default Environment: Do not provide PRTG placeholders'
values in the environment. Choose this secure option if you're
not sure.
§ Set placeholders as environment values: From within your
executable or script, the values of PRTG's command line
parameters will be available via environment variables. For
example, you can then read and use the current host value of
the PRTG device this EXE/script sensor is created on from within
your script. This option can mean a security risk, because also
credentials are provided in several variables. For a full list of all
available variables please see the API documentation (
Application Programming Interface (API) Definition 1185 ).
Security Context
Define the Windows user account that will be used to run the
executable or script file. Choose between:
· Use security context 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).
2011-10-17
295
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Settings
· Use Windows credentials 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 299 section below. Please enter a string or leave the field
empty.
Timeout (sec.)
Enter a timeout in seconds for the request. If the reply takes
longer than this value the external process is killed and an error
message is triggered.
Value Type
Define what kind of values your executable or script file gives
back. Choose between:
· Integer: 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.
The sensor cannot handle string values. Once a sensor is created
this value cannot be changed. It is shown for reference purposes
only. If you need to change this, please add the sensor anew.
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.
If Value Changes
Define what shall be done in case the value of this sensor
changes. You can choose between:
· Ignore changes (default): No action will be taken on change.
· Trigger 'On Change' notification: 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 943 whenever the sensor
value changes.
296
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Settings
EXE Result
Define what will be done with the result the executable file gives
back. Choose between:
· Discard EXE result: Do not store the requested web page.
· Write EXE result to disk (Filename: "Result of Sensor
[ID].txt"): Store the last result received from the script 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 More 299 section below.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
2011-10-17
297
Part VI: Ajax Web Interface—Device and Sensor Setup
Scanning Interval
Scanning Interval
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
298
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
More
Information about custom scripts and executables
§ Application Programming Interface (API) Definition 1185
2011-10-17
299
Part VI: Ajax Web Interface—Device and Sensor Setup
§ Additional Sensor Types (Custom Sensors)
935
Paessler Knowledge Base: What is the Mutex Name in PRTG's EXE/Script Sensor's settings?
§ http://www.paessler.com/knowledgebase/en/topic/6673
Paessler Knowledge Base: How and Where Does PRTG Store its Data?
§ http://www.paessler.com/knowledgebase/en/topic/463
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
300
118
section.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.12 EXE/Script Advanced Sensor
The EXE/Script Advanced sensor runs an executable file (EXE, DLL) or a script (batch file,
VBScript, Powershell) on the computer running the local or remote probe. This option is
provided as part of PRTG's Application Programming Interface (API). The sensor shows the
execution time, and can show values returned by the executable file or script in multiple
channels. The return value of this sensor must be valid XML. For details about the return
value format please see the Application Programming Interface (API) definition linked in the
More 306 section below.
Note: The executable or script file must be stored on the system of the probe the sensor is
created on: If used on a remote probe, the file must be stored on the system running the
remote probe. In a cluster setup, please copy the file to every cluster node.
Note: If you want to execute a custom Windows Management Instrumentation Query
Language (WQL) script, please use the WMI Custom Sensor 790 .
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-17
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
301
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Settings
EXE/Script
Select an executable file from the list. It will be executed with
every scanning interval. In this list, files in the corresponding
/Custom Sensors/EXEXML sub-directory of the probe system's
PRTG installation are shown. In order for the files to appear in this
list, please store them into this folder. Store files ending in BAT,
CMD, DLL, EXE, PS1, and VBS. In order for the sensor to show the
right status, your files must use the right format for the returned
values. For detailed information on how to build custom sensors,
please see the API documentation (Application Programming
Interface (API) Definition 1185 ).
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 Cluster Probe, please
copy your files to every cluster node installation.
Parameters
If your executable or script file catches command line parameters,
you can define them here. Placeholders can be used as well. For a
full list of all placeholders please see the API documentation (
Application Programming Interface (API) Definition 1185 ). Please
enter a string or leave the field empty.
Environment
Choose if PRTG's command line parameters will also be available
as environment parameters.
§ Default Environment: Do not provide PRTG placeholders'
values in the environment. Choose this secure option if you're
not sure.
§ Set placeholders as environment values: From within your
executable or script, the values of PRTG's command line
parameters will be available via environment variables. For
example, you can then read and use the current host value of
the PRTG device this EXE/script sensor is created on from within
your script. This option can mean a security risk, because also
credentials are provided in several variables. For a full list of all
available variables please see the API documentation (
Application Programming Interface (API) Definition 1185 ).
Security Context
Define the Windows user account that will be used to run the
executable or script file. Choose between:
· Use security context 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).
302
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Settings
· Use Windows credentials 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 306 section below. Please enter a string or leave the field
empty.
Timeout (sec.)
Enter a timeout in seconds for the request. If the reply takes
longer than this value the external process is killed and an error
message is triggered.
EXE Result
Define what will be done with the results the executable file gives
back. Choose between:
· Discard EXE result: Do not store the requested web page.
· Write EXE result to disk (Filename: "Result of Sensor
[ID].txt"): Store the last result received from the script 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 More 306 section below.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
2011-10-17
303
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Note: The Stack 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 (Application Programming Interface (API) Definition 1185 ).
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 185 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.
Scanning Interval
Scanning Interval
304
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
305
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
More
Information about custom scripts and executables
§ Application Programming Interface (API) Definition 1185
306
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
§ Additional Sensor Types (Custom Sensors)
935
Paessler Knowledge Base: What is the Mutex Name in PRTG's EXE/Script Sensor's settings?
§ http://www.paessler.com/knowledgebase/en/topic/6673
Paessler Knowledge Base: How and Where Does PRTG Store its Data?
§ http://www.paessler.com/knowledgebase/en/topic/463
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-17
118
section.
307
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.13 File Sensor
The File sensor monitors a folder using Server Message Block (SMB). You can monitor file
content and file time stamp changes. It shows the file size, and a last modified value in days
and hours.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
308
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
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.
Monitor File Content
Specify if the sensor will send a change notification when the
content of the file changes (based on a checksum). Choose
between:
§ Ignore changes: No action will be taken on change.
§ Trigger 'change' notification: 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 943 whenever the sensor value changes.
Monitor File Time
Stamp
Specify if the sensor will send a change notification when the
content of the file's time stamp changes. Choose between:
§ Ignore changes: No action will be taken on change.
§ Trigger 'change' notification: 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 943 whenever the sensor value changes.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
2011-11-22
309
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
310
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-11-22
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
311
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
More
Knowledge Base: What can I do if PRTG doesn't succeed with monitoring a share? PE029
PE032
312
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
§ http://www.paessler.com/knowledgebase/en/topic/513
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-11-22
118
section.
313
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.14 File Content Sensor
The File Content sensor checks a text file for certain strings and returns the line number of
the last match and the number of total matches. Additionally, matching lines are quoted in
the sensor message field.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
314
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Settings
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.
Search Method
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:
§ Simple string search: Search for a simple string.
§ Regular Expression: Search using a regular expression. For
more details, see Regular Expressions 1192 section.
Warning Behaviour
Define under which condition the sensor will show a Warning
status. Choose between:
§ Goto warning state when string is not found: The sensor will
show a Warning status if there is no match. Otherwise it will
remain in Up status.
§ Goto warning state when string is found: The sensor will
show a Warning status if there is a match. Otherwise it will
remain in Up status.
If Value Changes
Define what shall 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' notification: 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 943 whenever the sensor value changes.
2011-11-22
315
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
316
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-11-22
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
317
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
318
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-11-22
118
section.
319
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.15 Folder Sensor
The Folder sensor monitors a folder using Server Message Block (SMB). You can monitor file
changes and file ages. It shows the folder size and file count as well as the oldest and newest
file value in days and hours.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
320
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
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
Specify if subfolders will be included in the monitoring. Choose
between:
· Do not recurse sub-folders: Only monitor the folder specified
above; do not monitor its subfolders.
· Monitor the folder and its sub-folders (use with caution!):
Monitor the folder specified above and all of its subfolders.
Note: Recursing sub-folders in large directories with a high
number of branches may evoke timeout errors or performance
issues.
Monitor Folder
Changes
Specify if the sensor will send a change notification when the
content of the folder changes. Choose between:
· Ignore changes: Changes to the folder will not trigger a change
notification.
· Trigger 'On Change' notification: The sensor will trigger a
change notification if a file changes its timestamp or filename,
or if there are new or deleted files.
Check of File Ages
Specify if the sensor will monitor the folder for certain file ages.
Choose between:
· Don't check: Do not check for the age of the files in the
specified folder(s).
· Show Warning if older: Set the sensor to warning status if one
of the files in the specified folder is older than...
· Show Error if older: Set the sensor to error status if one of the
files in the specified folder is older than...
· Show Warning if younger: Set the sensor to warning status if
one of the files in the specified folder is younger than...
· Show Error if younger: Set the sensor to error status if one of
the files in the specified folder is younger than...
File Age Limit
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.
File Age Limit Unit
This field is only visible if a file age check is enabled above.
Specify the unit for the file age below. Choose between:
2011-11-22
· In days: You will enter a number of days below.
321
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
322
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-11-22
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
323
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
More
Knowledge Base: What can I do if PRTG doesn't succeed with monitoring a share? PE029
PE032
324
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
§ http://www.paessler.com/knowledgebase/en/topic/513
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-11-22
118
section.
325
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.16 FTP Sensor
The FTP sensor monitors file servers using File Transfer Protocol (FTP) and FTP over SSL
(FTPS). It shows the response time.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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)
326
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.
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Specific
Port
Enter the number of the port the sensor will try to connect to. For
non-secure connections usually port 21 is used; usually port 990
for implicit secure connections. Please enter an integer value. We
recommend using the default value. If you do not get a
connection, please try another port number.
FTP Mode
Specify which ftp mode will be used for the connection. Choose
between:
· Use active mode
· Use passive mode
We recommend using the default value. If you do not get a
connection, please try the passive mode.
Authentication
Username
Enter a username for the FTP login. Please enter a string or leave
the field empty.
Password
Enter a password for the FTP login. Please enter a string or leave
the field empty.
TLS
(Transport-Level-Securi
ty)
Specifiy if an encryption will be used for the connection. Choose
between:
· Don't use SSL (Basic FTP, recommended)
· Use SSL (FTP over SSL/FTPS)
In most cases, you will use basic FTP without encryption.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
2011-10-27
327
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
328
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-27
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
329
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
330
118
section.
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.17 FTP Server File Count Sensor
The FTP Server File Count sensor logs in to an FTP server and returns the number of files
available in the directory listing.
Requirement: .NET Framework
This sensor type requires the Microsoft .NET Framework to be installed on the computer
running the PRTG probe: Either on the local system (on every node, if in a cluster), or on the
system running the remote probe 1194 . If the framework is missing, you cannot create this
sensor.
Required .NET version: 2.0.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings 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 returned values will be
shown. This is for display purposes only. Please enter a string.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
2011-10-27
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
331
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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
FTP URL
Enter the URL to check (this sensor does not use the IP
Address/DNS value of the parent device).
Username
Define the username for the login. Please enter a string.
Password
Define the password for the login. Please enter a string.
If Value Changes
Define what shall 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' notification: 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 943 whenever the sensor value changes.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
332
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-27
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
333
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
334
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
2011-10-27
335
Part VI: Ajax Web Interface—Device and Sensor Setup
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
336
118
section.
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.18 HDD Health Sensor
Monitors the health of IDE disk drives using Self-Monitoring, Analysis, and Reporting
Technology (S.M.A.R.T./SMART). This is built into most modern IDE hard disk drives.
It can show the following channels: Temperature, Read Error Rate, Throughput Performance,
Spin-Up Time, Start/Stop Count, Reallocated Sectors Count, Power On Count, Spin Retry
Count, Recalibration Retries, Device Power Cycle Count, Soft Read Error Rate, High Fly Writes
(WDC), Reallocation Event Count, Current Pending Sector Count, Uncorrectable Sector Count,
Off-Track Error Rate, and Downtime.
This sensor can be set up on a Probe Device only!
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
SMART Specific
IDE Devices
Please select one or more hard disks from the list by adding a
check mark in front of the respective line. For every HDD one
sensor will be created. Names are chosen automatically and can
be changed later in the sensor's settings. The items shown in the
list are specific to the probe system you're creating the sensor
on.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
2011-10-17
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
337
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
SMART Specific
Serial No.
Shows the serial number of the monitored disk. Once a sensor is
created this value cannot be changed. It is shown for reference
purposes only. If you need to change this, please add the sensor
anew.
Name
Shows the name of the monitored disk. Once a sensor is created
this value cannot be changed. It is shown for reference purposes
only. If you need to change this, please add the sensor anew.
Size (GB)
Shows the size in Gigabyte of the monitored disk. Once a sensor
is created this value cannot be changed. It is shown for reference
purposes only. If you need to change this, please add the sensor
anew.
Temperature threshold Shows the temperature threshold value stored in the monitored
disk. Once a sensor is created this value cannot be changed. It is
shown for reference purposes only. If you need to change this,
please add the sensor anew.
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.
Sensor Display
Primary Channel
338
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
339
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
340
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-17
118
section.
341
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.19 HTTP Sensor
The HTTP sensor monitors a web server using Hypertext Transfer Protocol (HTTP). It shows
the loading time. This is the easiest way to monitor if a website (or a specific website
element) is reachable.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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.)
342
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.
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
HTTP Specific
URL
Please enter the URL the sensor will connect to. This address can
be independent from the IP address/DNS name setting of the
device this sensor is created on. 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 replacements which allows you to use the parent device's IP
address/DNS name setting as part of the URL. For more
information, please see section Smart URL Replacement below.
Request Method
The request method determines how the given URL is requested.
· GET: Request the website directly, like browsing the web. We
recommend using this setting for a simple check of a web page.
· POST: Send post form data to the URL. If this setting is chosen,
you must enter the data that will be sent in the Postdata field
below.
· HEAD: Only request the HTTP header from the server; without
the actual web page. Although this saves bandwidth since less
data is transferred, it is not recommended because the
measured request time is not the one experienced by your users
and you might not be notified for slow results or timeouts.
Postdata
This field is only active when POST is selected in the Request
Method setting above. Please enter the data part for the post
request here. Note: No XML is allowed here!
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 drop down
menu. Choose between:
§ SSL V2
§ SSL V2 or V3: This is the default setting.
§ SSL V3
§ TLS V1
Sensor Display
2011-10-25
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
343
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
HTTP Proxy Settings
344
HTTP Proxy Settings
The proxy settings determine how a sensor connects to a given
URL. You can enter data for a proxy server that will be used when
connecting via HTTP or HTTPS.
Name
Enter the IP address or DNS name of the proxy server to use. If
you leave this field empty, no proxy will be used.
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
If the proxy requires authentication, enter the username for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Password
If the proxy requires authentication, enter the password for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
Scanning Interval
Scanning Interval
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-25
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
345
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Smart URL Replacement
Instead of entering a complete address in the URL field of an HTTP sensor, you can merely
enter the protocol followed by colon and three slashes (that means you can enter either
http:/// or https:/// or even a simple slash / as equivalent for http:///). PRTG will then fill in
the parent device's IP address or DNS name in front of the third slash automatically.
Whether this results in a valid URL or not, depends on the IP address or DNS name of the
device where this HTTP sensor is created on. In combination with cloning devices, the smart
URL replacement makes it easy to create many like devices.
For example, if you create a device with DNS name www.example.com and you put a HTTP
sensor on it with the value https:/// in the URL field, PRTG will automatically create the URL
https://www.example.com/ from that. Similarly, if you create a HTTP sensor on the same
device using the value /help in the URL field, PRTG will automatically create and monitor the
URL http://www.example.com/help
Note: Smart URL replacement does not work for sensors running on the "Probe Device".)
346
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-25
118
section.
347
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.20 HTTP Advanced Sensor
The HTTP Advanced sensor monitors the source code of a web page using Hypertext Transfer
Protocol (HTTP). It supports authentication, content checks, and other advanced parameters.
It shows the loading time, bytes received, download bandwidth (speed), and time to first
byte.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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.)
348
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.
2011-11-23
Part VI: Ajax Web Interface—Device and Sensor Setup
HTTP Specific
URL
Please enter the URL the sensor will connect to. This address can
be independent from the IP address/DNS name setting of the
device this sensor is created on. 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 replacements which allows you to use the parent device's IP
address/DNS name setting as part of the URL. For more
information, please see section Smart URL Replacement below.
Request Method
The request method determines how the given URL is requested.
· GET: Request the website directly, like browsing the web. We
recommend using this setting for a simple check of a web page.
· POST: Send post form data to the URL. If this setting is chosen,
you must enter the data that will be sent in the Postdata field
below.
· HEAD: Only request the HTTP header from the server; without
the actual web page. Although this saves bandwidth since less
data is transferred, it is not recommended because the
measured request time is not the one experienced by your users
and you might not be notified for slow results or timeouts.
Postdata
This field is only active when POST is selected in the Request
Method setting above. Please enter the data part for the post
request here. Note: No XML is allowed here!
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 drop down
menu. Choose between:
§ SSL V2
§ SSL V2 or V3: This is the default setting.
§ SSL V3
§ TLS V1
Advanced Sensor Data
Protocol Version
Define the HTTP protocol version that will be used when
connecting to the URL. Choose between:
§ HTTP 1.0
§ HTTP 1.1: This is the default setting.
2011-11-23
349
Part VI: Ajax Web Interface—Device and Sensor Setup
Advanced Sensor Data
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 String: Do not enter a specific user agent,
use default setting. This is: Mozilla/5.0 (compatible; PRTG
Network Monitor (www.paessler.com); Windows)
§ Use a Custom String: Use a custom user agent. Define below.
Custom User Agent
This field is only visible if custom user agent is enabled above.
Enter a string which will be used as user agent when connecting
to the URL specified above.
Content Changes
Define what will be done in case the content of the monitored web
page (element) changes. You can choose between:
· Ignore changes: No action will be taken on change.
· Trigger 'change' notification: 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 943 whenever the web page
content changes.
Check For Existing Key Define whether the the result at the configured URL will be
Words (Positive)
checked for keywords. Choose between:
§ Disable: Do not search for keywords.
§ Enable key word check (positive): In the result returned at the
URL, check if a key word exists.
Response Must Include This field is only visible if keyword checking is enabled above.
Define which string must be part of the source code at the given
URL. You can either enter plain text or a Regular Expression 1192 .
If the data does not include the search pattern, the sensor will be
set to an error state. Please enter a string.
For Key Word Search
Use
Define in which format you have entered the search expression in
the field above.
§ Plain Text: Search for the string as plain text. The characters *
and ? work here as placeholder, whereas * stands for no or any
number of characters and ? stands for exactly one character (as
known from Windows search). This behavior cannot be disabled,
so the literal search for these characters is not possible with
plain text search.
§ Regular Expression: Treat the search pattern as a Regular
Expression 1192 .
350
2011-11-23
Part VI: Ajax Web Interface—Device and Sensor Setup
Advanced Sensor Data
Check For Existing Key Define whether the the result at the configured URL will be
Words (Negative)
checked for keywords. Choose between:
§ Disable: Do not search for keywords.
§ Enable key word check (negative): In the result returned at
the URL, check if a key word does not exist.
Response must not
include
This field is only visible if keyword checking is enabled above.
Define which string must not be part of the source code at the
given URL. You can either enter plain text or a Regular
Expression 1192 . If the data does include this string, the sensor will
be set to an error state. Please enter a string.
For Key Word Search
Use
Define in which format you have entered the search expression in
the field above.
§ Plain Text: Search for the string as plain text. The characters *
and ? work here as placeholder, whereas * stands for no or any
number of characters and ? stands for exactly one character (as
known from Windows search). This behavior cannot be disabled,
so the literal search for these characters is not possible with
plain text search.
§ Regular Expression: Treat the search pattern as a Regular
Expression 1192 .
Limit Download (kb)
Enter a maximum amount of data that will be transferred per
every single request. If you set content checks, please be aware
that only the content downloaded up to this limit can be checked
for search expressions.
Result Handling
Define what will be done with the web page loaded at the given
URL. Choose between:
· Discard HTML result: Do not store the requested web page.
· Store latest HTML result: Store the last result of the requested
web page to the "Logs (System)" 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 Data Storage 1202 section.
2011-11-23
351
Part VI: Ajax Web Interface—Device and Sensor Setup
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.
Authentication
Authentication
Define if the web page at the configured URL need authentication.
Choose between:
§ No authentication needed
§ Web page need authentication
User
This field is only visible if authentication is enabled above. Enter a
username. Please enter a string.
Password
This field is only visible if authentication is enabled above. Enter a
password. Please enter a string.
Authentication Method This field is only visible if authentication is enabled above. Please
select the authentication method the given URL is protected with.
Choose between:
· Basic access authentication (HTTP): Use simple HTTP
authentication. This is the default setting and suitable for most
cases.
· Windows NT LAN Manager (NTLM): Use the Microsoft NTLM
protocol for authentication. This is sometimes used in Intranets
for single sign-on.
We recommend using the default value.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
352
2011-11-23
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
HTTP Proxy Settings
2011-11-23
HTTP Proxy Settings
The proxy settings determine how a sensor connects to a given
URL. You can enter data for a proxy server that will be used when
connecting via HTTP or HTTPS.
Name
Enter the IP address or DNS name of the proxy server to use. If
you leave this field empty, no proxy will be used.
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
If the proxy requires authentication, enter the username for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Password
If the proxy requires authentication, enter the password for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
353
Part VI: Ajax Web Interface—Device and Sensor Setup
Scanning Interval
Scanning Interval
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
354
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-11-23
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
2011-11-23
355
Part VI: Ajax Web Interface—Device and Sensor Setup
Smart URL Replacement
Instead of entering a complete address in the URL field of an HTTP sensor, you can merely
enter the protocol followed by colon and three slashes (that means you can enter either
http:/// or https:/// or even a simple slash / as equivalent for http:///). PRTG will then fill in
the parent device's IP address or DNS name in front of the third slash automatically.
Whether this results in a valid URL or not, depends on the IP address or DNS name of the
device where this HTTP sensor is created on. In combination with cloning devices, the smart
URL replacement makes it easy to create many like devices.
For example, if you create a device with DNS name www.example.com and you put a HTTP
sensor on it with the value https:/// in the URL field, PRTG will automatically create the URL
https://www.example.com/ from that. Similarly, if you create a HTTP sensor on the same
device using the value /help in the URL field, PRTG will automatically create and monitor the
URL http://www.example.com/help
Note: Smart URL replacement does not work for sensors running on the "Probe Device".)
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
356
118
section.
2011-11-23
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.21 HTTP Content Sensor
The HTTP Content sensor monitors a numerical value returned by a Hypertext Transfer
Protocol (HTTP) request. In the returned HTML page, each value must be placed between
square brackets [ ].
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings 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:
§ Integer: 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 Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
2011-10-25
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
357
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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.
Script URL
Please enter the URL the sensor will connect to. This address can
be independent from the IP address/DNS name setting of the
device this sensor is created on. PRTG uses a smart URL
replacements 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 this value cannot be changed. It is shown for reference
purposes only. If you need to change this, please add the sensor
anew.
SSL Method
This setting is only relevant when using a https protocol in the
Script URL. Select the SSL method that will be used when
connecting to the URL. We recommend using the default value.
Only if you experience connection problems, try another setting.
Advanced Sensor Data
Content changes
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.
358
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
Advanced Sensor Data
· Trigger 'change' notification: 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 943 whenever the web page
content changes.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
2011-10-25
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
359
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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.
HTTP Proxy Settings
360
HTTP Proxy Settings
The proxy settings determine how a sensor connects to a given
URL. You can enter data for a proxy server that will be used when
connecting via HTTP or HTTPS.
Name
Enter the IP address or DNS name of the proxy server to use. If
you leave this field empty, no proxy will be used.
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
If the proxy requires authentication, enter the username for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Password
If the proxy requires authentication, enter the password for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
Scanning Interval
Scanning Interval
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-25
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
361
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Smart URL Replacement
Instead of entering a complete address in the URL field of an HTTP sensor, you can merely
enter the protocol followed by colon and three slashes (that means you can enter either
http:/// or https:/// or even a simple slash / as equivalent for http:///). PRTG will then fill in
the parent device's IP address or DNS name in front of the third slash automatically.
Whether this results in a valid URL or not, depends on the IP address or DNS name of the
device where this HTTP sensor is created on. In combination with cloning devices, the smart
URL replacement makes it easy to create many like devices.
For example, if you create a device with DNS name www.example.com and you put a HTTP
sensor on it with the value https:/// in the URL field, PRTG will automatically create the URL
https://www.example.com/ from that. Similarly, if you create a HTTP sensor on the same
device using the value /help in the URL field, PRTG will automatically create and monitor the
URL http://www.example.com/help
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?
362
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
· http://www.paessler.com/knowledgebase/en/topic/4
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-25
118
section.
363
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.22 HTTP Full Web Page Sensor
The HTTP Full Web Page sensor monitors the full download time of a web page including
images etc. In the background, it opens the web page in Internet Explorer to perform the
measurement. Links are not followed. The sensor shows the loading time of the full page.
Note: Be careful with this sensor, as it can generate considerable internet traffic if used with
a low scanning interval!
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
Full Page Download Settings
Timeout (sec.)
364
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.
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
Full Page Download Settings
URL
Please enter the URL the sensor will load. This address can be
independent from the IP address/DNS name setting of the device
this sensor is created on. PRTG uses a smart URL replacements
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.
Note: The specified web page is loaded in the background in an instance of Internet Explorer.
Therefore, the same Internet Explorer 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). 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). We recommend installing Internet Explorer 8 or higher on the system running the
PRTG probe.
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 185 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.
Scanning Interval
Scanning Interval
2011-10-25
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
365
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
366
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Smart URL Replacement
Instead of entering a complete address in the URL field of an HTTP sensor, you can merely
enter the protocol followed by colon and three slashes (that means you can enter either
http:/// or https:/// or even a simple slash / as equivalent for http:///). PRTG will then fill in
the parent device's IP address or DNS name in front of the third slash automatically.
Whether this results in a valid URL or not, depends on the IP address or DNS name of the
device where this HTTP sensor is created on. In combination with cloning devices, the smart
URL replacement makes it easy to create many like devices.
For example, if you create a device with DNS name www.example.com and you put a HTTP
sensor on it with the value https:/// in the URL field, PRTG will automatically create the URL
https://www.example.com/ from that. Similarly, if you create a HTTP sensor on the same
device using the value /help in the URL field, PRTG will automatically create and monitor the
URL http://www.example.com/help
Note: Smart URL replacement does not work for sensors running on the "Probe Device".)
2011-10-25
367
Part VI: Ajax Web Interface—Device and Sensor Setup
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
368
118
section.
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.23 HTTP SSL Certificate Expiry Sensor
The HTTP SSL Certificate Expiry Sensor checks a specific https-URL and returns the number of
days remaining until the site's SSL certificate expires. It shows a Warning when only 60 days
are left, and an Error status when only 30 days are remaining until the certificate expires.
Requirement: .NET Framework
This sensor type requires the Microsoft .NET Framework to be installed on the computer
running the PRTG probe: Either on the local system (on every node, if in a cluster), or on the
system running the remote probe 1194 . If the framework is missing, you cannot create this
sensor.
Required .NET version: 2.0.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-25
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
369
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Settings
URL
Enter the URL to check (this sensor does not use the IP
Address/DNS value of the parent device).
Force SSL V3
Define if you want to allow SSL V3 only for connections to the URL
configured above. Choose between:
§ No
§ Yes
HTTP Proxy Settings
HTTP Proxy Settings
The proxy settings determine how a sensor connects to a given
URL. You can enter data for a proxy server that will be used when
connecting via HTTP or HTTPS.
Name
Enter the IP address or DNS name of the proxy server to use. If
you leave this field empty, no proxy will be used.
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
If the proxy requires authentication, enter the username for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Password
If the proxy requires authentication, enter the password for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
370
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-25
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
371
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
372
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-25
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-25
118
section.
373
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.24 HTTP Transaction Sensor
The HTTP Transaction sensor monitors an interactive website, such as an web shop, by
performing a transaction using a set of Hypertext Transfer Protocol (HTTP) URLs. The sensor
monitors whether logins or shopping carts work properly. It returns the loading time.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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
374
Timeout (sec.)
Enter a timeout in seconds for all HTTP requests. If the complete
transaction takes longer than this value the request is aborted
and an error message is triggered.
Single URL Timeout
(seconds)
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.
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
HTTP 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 drop down
menu. Choose between:
§ SSL V2
§ SSL V2 or V3: This is the default setting.
§ SSL V3
§ TLS V1
Advanced Sensor Data
Limit Download (kb)
Enter a maximum amount of data that will be transferred per
every single request. If you set content checks below, please be
aware that only the content downloaded within this limit can be
checked for certain search expressions.
Cookie Management
Select if cookies will be used for the transaction. Choose between:
· Use cookies (recommended): Allow cookies to be set and read
during the transaction cycle.
· Ignore cookies: Do not allow cookies. Use this option if you
want to test the transaction without the use of cookies.
We recommend using the default value.
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.
· Store latest HTML result: Store the last result of the requested
web page to the "Logs (System)" 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 Data Storage 1202 section.
Authentication
Authentication
Define if the web page at the configured URL need authentication.
Choose between:
§ No authentication needed
§ Web page need authentication
2011-10-31
375
Part VI: Ajax Web Interface—Device and Sensor Setup
Authentication
User
This field is only visible if authentication is enabled above. Enter a
username. Please enter a string.
Password
This field is only visible if authentication is enabled above. Enter a
password. Please enter a string.
Authentication Method This field is only visible if authentication is enabled above. Please
select the authentication method the given URL is protected with.
Choose between:
· Basic access authentication (HTTP): Use simple HTTP
authentication. This is the default setting and suitable for most
cases.
· Windows NT LAN Manager (NTLM): Use the Microsoft NTLM
protocol for authentication. This is sometimes used in Intranets
for single sign-on.
We recommend using the default value.
Transaction URL
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 112 . Using
this mechanism you can set up an extended monitoring with multiple URLs. Please enter
settings for at least one transaction URL. You can use as many steps as needed and disable
the other steps.
Transaction Step #x
This setting is available for URL #2 through #10. Define if you
want to use this step for your transaction check. Choose between:
§ Disable step #x: Do not use this step. Choose this option if you
do not need all 10 steps for your transaction check.
§ Enable step #x: Enable this step. Further options will be
viewed, as described below.
URL
Please enter the URL the sensor will connect to. This address can
be independent from the IP address/DNS name setting of the
device this sensor is created on. PRTG uses a smart URL
replacements which allows you to use the parent device's IP
address/DNS name setting as part of the URL. For more
information, please see section Smart URL Replacement below.
Request Method
The request method determines how the given URL is requested.
· GET: Request the website directly, like browsing the web. We
recommend using this setting for a simple check of a web page.
376
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
Transaction URL
· POST: Send post form data to the URL. If this setting is chosen,
you must enter the data that will be sent in the Postdata field
below.
· HEAD: Only request the HTTP header from the server; without
the actual web page. Although this saves bandwidth since less
data is transferred, it is not recommended because the
measured request time is not the one experienced by your users
and you might not be notified for slow results or timeouts.
Postdata
This field is only active when POST is selected in the Request
Method setting above. Please enter the data part for the post
request here. Note: No XML is allowed here!
Check For Existing Key Define whether the the result at the configured URL will be
Words (Positive)
checked for keywords. Choose between:
§ Disable: Do not search for keywords.
§ Enable key word check (positive): In the result returned at the
URL, check if a key word exists.
Response must
include
Define which string must be part of the web at the given URL. If
the data does not include this string, the sensor will be set to an
error state. Please enter a string. Note: Only simple text search is
available here. The characters * and ? work here as placeholder,
whereas * stands for no or any number of characters and ? stands
for exactly one character (as known from Windows search). This
behavior cannot be disabled, so the literal search for these
characters is not possible.
Check For Existing Key Define whether the the result at the configured URL will be
Words (Negative)
checked for keywords. Choose between:
§ Disable: Do not search for keywords.
§ Enable key word check (negative): In the result returned at
the URL, check if a key word does not exist.
Response must not
include
2011-10-31
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.
377
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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.
HTTP Proxy Settings
HTTP Proxy Settings
The proxy settings determine how a sensor connects to a given
URL. You can enter data for a proxy server that will be used when
connecting via HTTP or HTTPS.
Name
Enter the IP address or DNS name of the proxy server to use. If
you leave this field empty, no proxy will be used.
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
If the proxy requires authentication, enter the username for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Password
If the proxy requires authentication, enter the password for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Scanning Interval
Scanning Interval
378
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-31
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
379
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Smart URL Replacement
Instead of entering a complete address in the URL field of an HTTP sensor, you can merely
enter the protocol followed by colon and three slashes (that means you can enter either
http:/// or https:/// or even a simple slash / as equivalent for http:///). PRTG will then fill in
the parent device's IP address or DNS name in front of the third slash automatically.
Whether this results in a valid URL or not, depends on the IP address or DNS name of the
device where this HTTP sensor is created on. In combination with cloning devices, the smart
URL replacement makes it easy to create many like devices.
For example, if you create a device with DNS name www.example.com and you put a HTTP
sensor on it with the value https:/// in the URL field, PRTG will automatically create the URL
https://www.example.com/ from that. Similarly, if you create a HTTP sensor on the same
device using the value /help in the URL field, PRTG will automatically create and monitor the
URL http://www.example.com/help
Note: Smart URL replacement does not work for sensors running on the "Probe Device".)
More
Knowledge Base: Configuration Tips for HTTP Transaction Sensors needed
380
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
§ http://www.paessler.com/knowledgebase/en/topic/443
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-31
118
section.
381
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.25 HTTP XML/REST Value Sensor
The HTTP XML/REST Value sensor retrieves an XML file from a given URL and parses it. It can
return the values of specific nodes.
Requirement: .NET Framework
This sensor type requires the Microsoft .NET Framework to be installed on the computer
running the PRTG probe: Either on the local system (on every node, if in a cluster), or on the
system running the remote probe 1194 . If the framework is missing, you cannot create this
sensor.
Required .NET version: 2.0.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
382
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-10-21
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Settings
URL
Enter the URL that returns the XML file (this sensor does not use
the IP Address/DNS value of the parent device).
XML Node (and
optional property)
Enter the name of the node this sensor will check, or enter a node
name and a property name to check a property value. Note: XPath
is allowed here. This enables you, for example, to read values of
arrays from XML files. For example, use array[@name='myName']
to read all 'array' elements which have a 'name' attribute equal to
'myName'. For further documentation about XPath please see
More 382 section below.
HTTP Username
If the URL requires authentication, enter the username. Please
enter a string or leave the field empty.
HTTP Password
If the URL requires authentication, enter the password. Please
enter a string or leave the field empty.
Sensor Value
Choose between:
§ Use the value of the selected XML node: Return the value
found at the specified XML node. If this is non-numeric, this will
return 0.
§ Use the number of occurrences of the selected XML node or
its children/siblings: Return the number of occurrences found.
Characters to Remove
Optionally enter a string which will be removed from the returned
XML value. Use this to remove any unwanted characters from the
result, e.g. a thousands separator from numeric values. Please
enter a string or leave the field empty.
Custom Message
Optionally enter a custom sensor message. Use %1 as a
placeholder to automatically fill in the returned XML value. Please
enter a string or leave the field empty.
Force SSL V3
Define if you only want to allow SSL V3 connections to the URL
defined above. Choose between:
§ No
§ Yes
If Value Changes
Define what shall be done in case the value of this sensor
changes. You can choose between:
· Ignore changes (default): No action will be taken on change.
2011-10-21
383
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Settings
· Trigger 'change' notification: 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 943 whenever the sensor value changes.
Results
Define what will be done with the results given back. Choose
between:
· Discard result: Do not store the requested web page.
· Write result to disk (Filename: "Result of Sensor [ID].txt"):
Store the last result received from 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 More 299 section below.
Unit String
Enter a string that will be added to the values as a unit
description. This is for display purposes only.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
384
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
2011-10-21
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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.
Scanning Interval
Scanning Interval
2011-10-21
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
385
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
386
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-21
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
More
How can I use XPath with PRTG's XML/Rest Value Sensor?
2011-10-21
387
Part VI: Ajax Web Interface—Device and Sensor Setup
§ http://www.paessler.com/knowledgebase/en/topic/26393
HTTP XML/REST Value Sensor shows protocol voilation. What can I do?
§ http://www.paessler.com/knowledgebase/en/topic/26793
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
388
118
section.
2011-10-21
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.26 Hyper-V Host Server Sensor
The Hyper-V Host Server sensor monitors a Microsoft Hyper-V host server. It shows CPU
usage in percent of guests, hypervisor, and total, as well as host health critical values,
deposited pages, and network traffic. Note: The parent device for this sensor must be a
Windows Server running Hyper-V.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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
2011-10-13
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
389
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
390
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-13
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-13
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
391
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
392
118
section.
2011-10-13
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.27 Hyper-V Virtual Machine Sensor
The Hyper-V Virtual Machine sensor monitors a virtual machine running on a Microsoft
Hyper-V host server. It shows CPU usage in percent of guests, hypervisor, and total, as well
as disk read and write values, per second. Note: The parent device for this sensor must be a
Hyper-V server.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Virtual Machine Settings
Virtual Machine
You see a list of all virtual machines (VMs) available on the host
server on this device, including the ones that are not running. All
VMs are listed with name and a description. Please choose one or
more services by adding a check mark in front of the respective
line. For each VM one sensor will be created. 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 397 section below.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
2011-10-17
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
393
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
Virtual Machine Settings
GUID
Shows the Globally Unique Identifier (GUID) of the virtual machine
monitored by this sensor. Once a sensor is created this value
cannot be changed. It is shown for reference purposes only. If you
need to change this, please add the sensor anew.
Name
Shows the name of the virtual machine monitored by this sensor.
Once a sensor is created this value cannot be changed. It is shown
for reference purposes only. If you need to change this, please
add the sensor anew.
Name
Shows the name of the host server. Once a sensor is created this
value cannot be changed. It is shown for reference purposes only.
If you need to change this, please add the sensor anew.
Powered Off VMs
Choose how the sensor will react to a virtual machine that is
powered off. Please choose between:
· Alarm when powered off (default): The sensor will change to a
down status if the virtual machine is powered off.
· Ignore powered off state: The sensor will not change to a
down status if the virtual machine is powered off; it will report
zero values instead.
Sensor Display
Primary Channel
394
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
395
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
396
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
More
Knowledge Base: Why don't my Hyper-V Virtual Machine / Network Adapter Sensor work after
changing names?
§ http://www.paessler.com/knowledgebase/en/topic/15533
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
2011-10-17
397
Part VI: Ajax Web Interface—Device and Sensor Setup
Others
For more general information about settings, please see Object Settings
398
118
section.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.28 Hyper-V Virtual Network Adapter Sensor
The Hyper-V Network Adapter sensor monitors virtual network adapters running on a
Microsoft Hyper-V host server. It shows sent and received bytes, packets, broadcast packets,
directed packets, and multicast packets, per second. Note: The parent device for this sensor
must be a Hyper-V server.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Virtual Machine Settings
Hyper-V Virtual
Network Adapter
You see a list of all virtual network adapters available on the host
server on this device. All adapters are listed with their name.
Please choose one or more by adding a check mark in front of the
respective line. For each adapter one sensor will be created. Note:
We recommend to not rename virtual machines once you've 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 397 section below.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
2011-10-17
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
399
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
Hyper-V Virtual Network Adapter Settings
Virtual Network
Adapter
Shows the name of the virtual network adapter monitored by this
sensor. Once a sensor is created this value cannot be changed. It
is shown for reference purposes only. If you need to change this,
please add the sensor anew.
Sensor Result
Define what will be done with the results the sensor receives.
Choose between:
§ Discard sensor result: Do not store the results.
§ Write sensor result to disk (Filename: "Result of Sensor
(ID].txt"): 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 Data Storage 1202 section.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
400
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
401
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
402
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
More
Knowledge Base: Why don't my Hyper-V Virtual Machine / Network Adapter Sensor work after
changing names?
§ http://www.paessler.com/knowledgebase/en/topic/15533
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
2011-10-17
403
Part VI: Ajax Web Interface—Device and Sensor Setup
Others
For more general information about settings, please see Object Settings
404
118
section.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.29 Hyper-V Virtual Storage Device Sensor
The Hyper-V Virtual Storage sensor monitors a virtual storage device running on a Microsoft
Hyper-V host server. It shows read and write values in second, and the number of errors.
Note: The parent device for this sensor must be a Hyper-V server.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
Hyper-V Virtual Storage Device Settings
Hyper-V Virtual
Storage Device
You see a list of all virtual storage devices available on the host
server on this device. Please choose one or more devices by
adding a check mark in front of the respective line. For each
storage device one sensor will be created.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-17
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
405
Part VI: Ajax Web Interface—Device and Sensor Setup
Hyper-V Virtual Storage Device Settings
Virtual Storage Device
Shows the unique name of the device monitored by this sensor.
Once a sensor is created this value cannot be changed. It is shown
for reference purposes only. If you need to change this, please
add the sensor anew.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
406
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
407
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
408
118
section.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.30 IMAP Sensor
The IMAP sensor monitors a mail server using Internet Message Access Protocol (IMAP) and
shows the server's response time.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
IMAP Specific
Timeout (sec.)
2011-10-17
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.
409
Part VI: Ajax Web Interface—Device and Sensor Setup
IMAP Specific
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.
Authentication
Authentication Type
Select the kind of authentication for the IMAP connection. Choose
between:
· Username/Password: Authenticate at the IMAP server via
username and password.
· Simple Authentication and Security Layer (SASL): Use a
secure connection for the authentication at the IMAP server.
Username
Enter a username for IMAP authentication. Please enter a string.
Password
Enter a password for IMAP authentication. Please enter a string.
TLS (Transport-Level
Security)
Choose if a secure connection via TLS/SSL will be used. Choose
between
· Don't use
· Use
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
410
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
411
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
412
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-17
118
section.
413
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.31 INI File Content Check Sensor
The INI File Content Check sensor reads an *.ini file. It indicates if the file exists and if a
specified section and field are found. The sensor returns the field's integer value (or -1 if the
field does not contain an integer). It will show a Warning status if a section or field is not
found, and a Down status if the file could not be opened.
For this sensor type, Windows credentials must be defined for the device you want to use the
sensor on.
Requirement: Windows Credentials
For this sensor type, Windows credentials must be defined for the device you want to use the
sensor on. In the parent device's Credentials for Windows Systems settings, please prefer
using Windows domain credentials. Note: If you use local credentials, please make sure the
same Windows user account (with same username and password) exists on both the system
running the PRTG probe and the target computer. Otherwise the sensor cannot connect
correctly.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
414
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
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
INI Filename
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 shall 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' notification: 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 943 whenever the sensor value changes.
Sensor Display
Primary Channel
2011-11-22
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
415
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
416
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-11-22
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
417
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
418
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-11-22
118
section.
419
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.32 IP on DNS Blacklist Sensor
The IP on DNS Blacklist sensor checks if the IP address of its parent device is listed on
specific blacklist servers and returns the number of hits found. If a DNS name is used as the
parent device's hostname, PRTG will resolve it to an IP address first.
During normal operation, there should be 0 hits and the sensor should show a green Up
status. If the IP address is found by at least one of the blacklist servers, the sensor changes
to a red Down status.
Requirement: .NET Framework
This sensor type requires the Microsoft .NET Framework to be installed on the computer
running the PRTG probe: Either on the local system (on every node, if in a cluster), or on the
system running the remote probe 1194 . If the framework is missing, you cannot create this
sensor.
Required .NET version: 2.0.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
420
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
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. If left empty, PRTG will
automatically use all of the following servers:
sbl-xbl.spamhaus.org, bl.spamcop.net, dnsbl.njabl.org,
list.dsbl.org, multihop.dsbl.org, list.dsbl.org and
multihop.dsbl.org
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.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
2011-10-31
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
421
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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.
Scanning Interval
Scanning Interval
422
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-31
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
423
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
424
118
section.
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.33 jFlow V5 Sensor
The jFlow V5 sensor receives traffic data from a jFlow V5 compatible device and shows the
traffic by type. On your hardware device, please make sure it matches jFlow V5 and disable
any sampling option! There are several filter options available to divide traffic into different
channels.
Note: In order for the sensor to work, jFlow export of the respective version must be enabled
on the device. The device must send the flow data stream to the IP address of the PRTG
probe system on which the sensor is set up (either a local or remote probe). The sensor does
not support sampling, so please disable sampling in your jFlow device!
For a general introduction to the technology behind flow monitoring, please see Monitoring
Bandwidth via Flows 1138 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-17
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
425
Part VI: Ajax Web Interface—Device and Sensor Setup
jFlow V5 Specific Settings
Receive jFlow Packets
on UDP Port
Enter the UDP port number on which the flow packets are
received. It must match the one you have configured in the jFlow
export options of your hardware router device. Please enter an
integer value. Please use a different port for each jFlow device, as
traffic is distinguished by port, not by IP address! Note: When
configuring export, please make sure you select the appropriate
jFlow version for this sensor.
Receive jFlow Packets
on IP
Select the IP address(es) on which PRTG listens to jFlow packets.
The list of IP addresses shown here is specific to your setup. To
select an IP address, add a check mark in front of the respective
line. The IP address selected here must match the one configured
in the jFlow export options of your hardware router device. Note:
When configuring export, please make sure you select the
appropriate jFlow version for this sensor.
Active Flow Timeout
(Minutes)
Enter a time span in minutes after which new flow data must be
received. If the timeout is reached and no new data is received,
the sensor may switch to an Unknown status. Please enter an
integer value. We recommend setting this one minute longer than
the respective timeout configured in your hardware router device.
Note: If you set this value too low, flow information might get lost!
Log Stream Data to
Disk (for Debugging)
Define if the probe will write a log file of the stream and packet
data to disk. Choose between:
§ None (recommended): Do not write additional log files.
Recommended for normal use cases.
§ Only for the 'Other' channel: Only write log files of data that is
not filtered otherwise and therefore accounted to the default
Other channel.
§ All stream data: Write log files for all data received.
Note: Use with caution! When enabled, huge data files can be
created. Please use for a short time and for debugging purposes
only.
Channel Configuration
Channel Selection
Define the categories the traffic will be accounted 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.
426
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Channel Configuration
§ Remote Control: Traffic caused by remote control applications,
such as RDP, SSH, Telnet, VNC.
§ Infrastructure: Traffic caused by network services, such as
DHCP, DNS, Ident, ICMP, SNMP.
§ NetBIOS: Traffic caused by NetBIOS communication.
§ Other Protocols: 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 traffic will be divided. For
each group, choose between:
§ No: Do not account traffic of this group in an own channel. All
traffic of this group will be accounted to the default channel
named Other.
§ Yes: Count all traffic of this group and summarize it into one
channel.
§ Detail: Count all traffic of this group and further divide it into
different channels. The traffic will appear in several channels as
shown in the Content 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 analyse.
Filtering
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
Filter Rules for xFlow and Packet Sniffer Sensors 1186 section.
Exclude Filter
First, the filters defined in the Include Filter field are considered.
From this subset, you can explicitly exclude traffic, using the
same syntax. For detailed information, please see Filter Rules for
xFlow and Packet Sniffer Sensors 1186 section.
Sensor Display
2011-10-17
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
427
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Primary Toplist
Primary Toplist
Define which will be your primary toplist. It will be shown in maps
and initially when selecting the Toplists tab. Choose from:
§ Top Talkers
§ Top Connections
§ Top Protocols
§ [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 185 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.
Scanning Interval
Scanning Interval
428
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
429
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
430
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Toplists
For all xFlow and packet sniffer sensors, there is a Toplists tab available. Using toplists, you
can review traffic data of small time periods in great detail. For more information, please see
Toplists 955 section.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
118
section.
Related Topics
§ Filter Rules for xFlow and Packet Sniffer Sensors 1186
§ Channel Defintions for xFlow and Packet Sniffer Sensors 1189
2011-10-17
431
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.34 jFlow V5 (Custom) Sensor
The jFlow V5 (Custom) sensor receives traffic data from a jFlow V5 compatible device and
shows the traffic by type. On your hardware device, please make sure it matches jFlow V5
and disable any sampling option! In this custom sensor, you can define your own channel
definitions to divide traffic into different channels.
Note: In order for the sensor to work, jFlow export of the respective version must be enabled
on the device. The device must send the flow data stream to the IP address of the PRTG
probe system on which the sensor is set up (either a local or remote probe). The sensor does
not support sampling, so please disable sampling in your jFlow device!
For a general introduction to the technology behind flow monitoring, please see Monitoring
Bandwidth via Flows 1138 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
432
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
jFlow Specific Settings
Receive jFlow Packets
on UDP Port
Enter the UDP port number on which the flow packets are
received. It must match the one configured in the jFlow export
options of your hardware router device. Please enter an integer
value. Please use a different port for each jFlow device, as traffic is
distinguished by port, not by IP address! Note: When configuring
export, please make sure you select the appropriate jFlow version
for this sensor.
Receive jFlow Packets
on IP
Select the IP address(es) on which PRTG listens to jFlow packets.
The list of IP addresses shown here is specific to your setup. To
select an IP address, add a check mark in front of the respective
line. The IP address selected here must match the one configured
in the jFlow export options of your hardware router device. Note:
When configuring export, please make sure you select the
appropriate jFlow version for this sensor.
Active Flow Timeout
(Minutes)
Enter a time span in minutes after which new flow data must be
received. If the timeout is reached and no new data is received,
the sensor may switch to an Unknown status. Please enter an
integer value. We recommend setting this one minute longer than
the respective timeout configured in your hardware router device.
Note: If you set this value too low, flow information might get lost!
Channel Definition
Please enter a channel definition to divide the traffic into different
channels. Write each definition in one line. For detailed
information, please see Channel Defintions for xFlow and
Packet Sniffer Sensors 1189 section. All traffic for which no channel
is defined will be accounted to the default channel named Other.
Note: Extensive use of many filters can cause load problems on
your probe system. We recommend defining specific, well-chosen
filters for the data you really want to analyse.
Log Stream Data to
Disk (for Debugging)
Define if the probe will write a log file of the stream and packet
data to disk. Choose between:
§ None (recommended): Do not write additional log files.
Recommended for normal use cases.
§ Only for the 'Other' channel: Only write log files of data that is
not filtered otherwise and therefore accounted to the default
Other channel.
§ All stream data: 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.
2011-10-17
433
Part VI: Ajax Web Interface—Device and Sensor Setup
Filtering
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
Filter Rules for xFlow and Packet Sniffer Sensors 1186 section.
Exclude Filter
First, the filters defined in the Include Filter field are considered.
From this subset, you can explicitly exclude traffic, using the
same syntax. For detailed information, please see Filter Rules for
xFlow and Packet Sniffer Sensors 1186 section.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Primary Toplist
Primary Toplist
Define which will be your primary toplist. It will be shown in maps
and initially when selecting the Toplists tab. Choose from:
§ Top Talkers
§ Top Connections
§ Top Protocols
§ [Any custom toplists you have added]
434
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
435
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
436
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
2011-10-17
437
Part VI: Ajax Web Interface—Device and Sensor Setup
Toplists
For all xFlow and packet sniffer sensors, there is a Toplists tab available. Using toplists, you
can review traffic data of small time periods in great detail. For more information, please see
section
§ Toplists
955
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
118
section.
Related Topics
§ Filter Rules for xFlow and Packet Sniffer Sensors 1186
§ Channel Defintions for xFlow and Packet Sniffer Sensors 1189
438
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.35 LDAP Sensor
The LDAP sensor monitors directory services using Lightweight Directory Access Protocol
(LDAP), connecting to the server trying a "bind". It shows the response time. If the server
does not respond or authentication fails, an error message will be triggered.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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
2011-10-17
Enter the LDAP port number, usually port 389 for unencrypted
connections. Please enter an integer value.
439
Part VI: Ajax Web Interface—Device and Sensor Setup
LDAP Specific
Distinguished Name
Enter the distinguished name (DN) you want to authenticate to the
LDAP server. Usually, this is the information for the user you want
to authenticate with. For example, use the format cn=Manager,
dc=my-domain,dc=com for a DN on an OpenLDAP server.
Passwort
Enter the password for the entered Distinguished Name.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
440
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Scanning Interval
Scanning Interval
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
441
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
442
118
section.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.36 Microsoft SQL Sensor
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 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-17
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
443
Part VI: Ajax Web Interface—Device and Sensor Setup
SQL-Server Specific Data
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.
Instance
Enter the SQL server instance's name if you want to connect to a
"named instance". For example, such an instance's name could be
SQLEXPRESS. Note: Sometimes you will see connection strings like
SQLSERVER\SQLINSTANCE in database clients. The first part is the
server name configured under the general server settings. The
second part refers to the instance name mentioned above. Never
enter this complete string in this PRTG form, merely provide the
second part (without the backslash). Please enter a string or leave
the field empty.
Port
Define the port for the SQL connection. Choose between:
§ Automatic: Automatically choose the right port.
§ Manual: Use a specific port. Define below. Standard value is
1433.
Port
This field is only visible if manual port selection is enabled above.
Define the port number for the SQL connection. Please enter an
integer value.
Database
Database
Enter the name of the SQL database the sensor will connect to. For
example, such a database's name could be Northwind
Authentication
Define the kind of authentication used for the connection to the
database. Choose between:
§ SQL Server: Use credentials specific to the SQL server. Please
enter them below.
§ Windows Authentication: 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
444
This field is only visible if SQL server authentication is enabled
above. Enter the user name that will be used for the database
connection.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Database
Password
This field is only visible if SQL server authentication is enabled
above. Enter the password that will be used for the database
connection.
Data
SQL-Expression
Enter the SQL expression that will be queried from the database.
For example, such an expression could be: SELECT ProductName
FROM Northwind.dbo.Products. Note: When a cursor is returned
(i.e. with a SELECT statement), only the first row of data will be
processed.
Postprocessing
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 string 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.
§ Monitor 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 943 whenever a sensor value changes.
Condition "Warning"
This field is only visible if numeric results is enabled above. Define
a condition of the returned numeric SQL result set that will set the
sensor to a Warning status. Choose between:
§ none: Do not set the sensor to Warning status for any
condition.
§ equals: Result set must be the same as the value provided
below.
§ is above: Result set must be above the value provided below.
§ lower than: Result set must be below the value provided below.
§ does not equal: Result set must be unequal to the value
provided below.
Note: This threshold check the SQL result set only. You can set
additional thresholds in the sensor's channel settings 938 .
2011-10-17
445
Part VI: Ajax Web Interface—Device and Sensor Setup
Value
This field is only visible if numeric results is enabled above. Enter
a value of the returned numeric SQL result set that will set the
sensor into a Warning status. Please enter an integer or float
value.
Condition "Down"
This field is only visible if numeric results is enabled above. Define
a condition of the returned numeric SQL result set that will set the
sensor to a Down status. Choose between:
§ none: Do not set the sensor to Down status for any condition.
§ equals: Result set must be the same as the value provided
below.
§ is above: Result set must be above the value provided below.
§ lower than: Result set must be below the value provided below.
§ does not equal: Result set must be unequal to the value
provided below.
Note: This threshold check the SQL result set only. You can set
additional thresholds in the sensor's channel settings 938 .
Value
This field is only visible if numeric results is enabled above. Enter
a value of the returned numeric SQL result set that will set the
sensor to a Down status. Please enter an integer value.
Response must
include
This field is only visible if string results is enabled above. Enter a
string that must be part of the returned SQL string. If it is not, the
sensor will be set to an error state. Please enter a string or leave
the field empty.
Response must not
include
This field is only visible if string results is enabled above. Enter a
string that must not be part of the returned SQL string. If it is, the
sensor will be set to an error state. Please enter a string or leave
the field empty.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
446
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
447
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
448
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-17
118
section.
449
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.37 MySQL Sensor
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 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
MySQL Server Specific Data
Port
Define the port for the SQL connection. Choose between:
§ Automatic: Automatically choose the right port.
§ Manual: Use a specific port. Define below. Standard value is
3306.
450
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
MySQL Server Specific Data
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.
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
Enter the SQL expression that will be queried from the database.
For example, such an expression could be: SELECT AVG(UnitPrice)
FROM Products. Note: When a cursor is returned (i.e. with a
SELECT statement), only the first row of data will be processed.
Postprocessing
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 string 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.
§ Monitor 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 943 whenever a sensor value changes.
2011-10-17
451
Part VI: Ajax Web Interface—Device and Sensor Setup
Condition "Warning"
This field is only visible if numeric results is enabled above. Define
a condition of the returned numeric SQL result set that will set the
sensor to a Warning status. Choose between:
§ none: Do not set the sensor to Warning status for any
condition.
§ equals: Result set must be the same as the value provided
below.
§ is above: Result set must be above the value provided below.
§ lower than: Result set must be below the value provided below.
§ does not equal: Result set must be unequal to the value
provided below.
Note: This threshold check the SQL result set only. You can set
additional thresholds in the sensor's channel settings 938 .
Value
This field is only visible if numeric results is enabled above. Enter
a value of the returned numeric SQL result set that will set the
sensor into a Warning status. Please enter an integer or float
value.
Condition "Down"
This field is only visible if numeric results is enabled above. Define
a condition of the returned numeric SQL result set that will set the
sensor to a Down status. Choose between:
§ none: Do not set the sensor to Down status for any condition.
§ equals: Result set must be the same as the value provided
below.
§ is above: Result set must be above the value provided below.
§ lower than: Result set must be below the value provided below.
§ does not equal: Result set must be unequal to the value
provided below.
Note: This threshold check the SQL result set only. You can set
additional thresholds in the sensor's channel settings 938 .
452
Value
This field is only visible if numeric results is enabled above. Enter
a value of the returned numeric SQL result set that will set the
sensor to a Down status. Please enter an integer value.
Response must
include
This field is only visible if string results is enabled above. Enter a
string that must be part of the returned SQL string. If it is not, the
sensor will be set to an error state. Please enter a string or leave
the field empty.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Response must not
include
This field is only visible if string results is enabled above. Enter a
string that must not be part of the returned SQL string. If it is, the
sensor will be set to an error state. Please enter a string or leave
the field empty.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Note: For this sensor type, no port number can be set.
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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
453
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
454
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-17
118
section.
455
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.38 NetFlow V5 Sensor
The NetFlow V5 sensor receives traffic data from a NetFlow V5 compatible device and shows
the traffic by type. Please make sure the sensor matches the NetFlow version your device is
exporting! There are several filter options available to divide traffic into different channels.
Note: In order for the sensor to work, NetFlow export of the respective version must be
enabled on the device. The device must send the flow data stream to the IP address of the
PRTG probe system on which the sensor is set up (either a local or remote probe).
For a general introduction to the technology behind flow monitoring, please see Monitoring
Bandwidth via Flows 1138 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
456
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
NetFlow Specific Settings
Receive NetFlow
Packets on UDP Port
Enter the UDP port number on which the flow packets are
received. It must match the one you have configured in the
NetFlow export options of your hardware router device. Please
enter an integer value. Please use a different port for each
NetFlow device, as traffic is distinguished by port, not by IP
address! Note: When configuring export, please make sure you
select the appropriate NetFlow version for this sensor.
Receive NetFlow
Packets on IP
Select the IP address(es) on which PRTG listens to NetFlow
packets. The list of IP addresses shown here is specific to your
setup. To select an IP address, add a check mark in front of the
respective line. The IP address selected here must match the one
configured in the NetFlow export options of your hardware router
device. Note: When configuring export, please make sure you
select the appropriate NetFlow version for this sensor.
Active Flow Timeout
(Minutes)
Enter a time span in minutes after which new flow data must be
received. If the timeout is reached and no new data is received,
the sensor may switch to an Unknown status. Please enter an
integer value. We recommend setting this one minute longer than
the respective timeout configured in your hardware router device.
Note: If you set this value too low, flow information might get lost!
Log Stream Data to
Disk (for Debugging)
Define if the probe will write a log file of the stream and packet
data to disk. Choose between:
§ None (recommended): Do not write additional log files.
Recommended for normal use cases.
§ Only for the 'Other' channel: Only write log files of data that is
not filtered otherwise and therefore accounted to the default
Other channel.
§ All stream data: Write log files for all data received.
Note: Use with caution! When enabled, huge data files can be
created. Please use for a short time and for debugging purposes
only.
Channel Configuration
Channel Selection
Define the categories the traffic will be accounted 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.
2011-10-17
457
Part VI: Ajax Web Interface—Device and Sensor Setup
Channel Configuration
§ Remote Control: Traffic caused by remote control applications,
such as RDP, SSH, Telnet, VNC.
§ Infrastructure: Traffic caused by network services, such as
DHCP, DNS, Ident, ICMP, SNMP.
§ NetBIOS: Traffic caused by NetBIOS communication.
§ Other Protocols: 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 traffic will be divided. For
each group, choose between:
§ No: Do not account traffic of this group in an own channel. All
traffic of this group will be accounted to the default channel
named Other.
§ Yes: Count all traffic of this group and summarize it into one
channel.
§ Detail: Count all traffic of this group and further divide it into
different channels. The traffic will appear in several channels as
shown in the Content 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 analyse.
Filtering
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
Filter Rules for xFlow and Packet Sniffer Sensors 1186 section.
Exclude Filter
First, the filters defined in the Include Filter field are considered.
From this subset, you can explicitly exclude traffic, using the
same syntax. For detailed information, please see Filter Rules for
xFlow and Packet Sniffer Sensors 1186 section.
Sensor Display
458
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Primary Toplist
Primary Toplist
Define which will be your primary toplist. It will be shown in maps
and initially when selecting the Toplists tab. Choose from:
§ Top Talkers
§ Top Connections
§ Top Protocols
§ [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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
459
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
460
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
2011-10-17
461
Part VI: Ajax Web Interface—Device and Sensor Setup
Toplists
For all xFlow and packet sniffer sensors, there is a Toplists tab available. Using toplists, you
can review traffic data of small time periods in great detail. For more information, please see
Toplists 955 section.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
118
section.
Related Topics
§ Filter Rules for xFlow and Packet Sniffer Sensors 1186
§ Channel Defintions for xFlow and Packet Sniffer Sensors 1189
462
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.39 NetFlow V5 (Custom) Sensor
The NetFlow V5 (Custom) sensor receives traffic data from a NetFlow V5 compatible device
and shows the traffic by type. Please make sure the sensor matches the NetFlow version your
device is exporting! In this custom sensor, you can define your own channel definitions to
divide traffic into different channels.
Note: In order for the sensor to work, NetFlow export of the respective version must be
enabled on the device. The device must send the flow data stream to the IP address of the
PRTG probe system on which the sensor is set up (either a local or remote probe).
For a general introduction to the technology behind flow monitoring, please see Monitoring
Bandwidth via Flows 1138 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-17
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
463
Part VI: Ajax Web Interface—Device and Sensor Setup
NetFlow Specific Settings
Receive NetFlow
Packets on UDP Port
Enter the UDP port number on which the flow packets are
received. It must match the one configured in the NetFlow export
options of your hardware router device. Please enter an integer
value. Please use a different port for each NetFlow device, as
traffic is distinguished by port, not by IP address! Note: When
configuring export, please make sure you select the appropriate
NetFlow version for this sensor.
Receive NetFlow
Packets on IP
Select the IP address(es) on which PRTG listens to NetFlow
packets. The list of IP addresses shown here is specific to your
setup. To select an IP address, add a check mark in front of the
respective line. The IP address selected here must match the one
configured in the NetFlow export options of your hardware router
device. Note: When configuring export, please make sure you
select the appropriate NetFlow version for this sensor.
Active Flow Timeout
(Minutes)
Enter a time span in minutes after which new flow data must be
received. If the timeout is reached and no new data is received,
the sensor may switch to an Unknown status. Please enter an
integer value. We recommend setting this one minute longer than
the respective timeout configured in your hardware router device.
Note: If you set this value too low, flow information might get lost!
Channel Definition
Please enter a channel definition to divide the traffic into different
channels. Write each definition in one line. For detailed
information, please see Channel Defintions for xFlow and
Packet Sniffer Sensors 1189 section. All traffic for which no channel
is defined will be accounted to the default channel named Other.
Note: Extensive use of many filters can cause load problems on
your probe system. We recommend defining specific, well-chosen
filters for the data you really want to analyse.
Log Stream Data to
Disk (for Debugging)
Define if the probe will write a log file of the stream and packet
data to disk. Choose between:
§ None (recommended): Do not write additional log files.
Recommended for normal use cases.
§ Only for the 'Other' channel: Only write log files of data that is
not filtered otherwise and therefore accounted to the default
Other channel.
§ All stream data: 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.
464
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Filtering
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
Filter Rules for xFlow and Packet Sniffer Sensors 1186 section.
Exclude Filter
First, the filters defined in the Include Filter field are considered.
From this subset, you can explicitly exclude traffic, using the
same syntax. For detailed information, please see Filter Rules for
xFlow and Packet Sniffer Sensors 1186 section.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Primary Toplist
Primary Toplist
Define which will be your primary toplist. It will be shown in maps
and initially when selecting the Toplists tab. Choose from:
§ Top Talkers
§ Top Connections
§ Top Protocols
§ [Any custom toplists you have added]
2011-10-17
465
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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.
Scanning Interval
Scanning Interval
466
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
467
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
468
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Toplists
For all xFlow and packet sniffer sensors, there is a Toplists tab available. Using toplists, you
can review traffic data of small time periods in great detail. For more information, please see
section
§ Toplists
955
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
118
section.
Related Topics
§ Filter Rules for xFlow and Packet Sniffer Sensors 1186
§ Channel Defintions for xFlow and Packet Sniffer Sensors 1189
2011-10-17
469
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.40 NetFlow V9 Sensor
The NetFlow V9 sensor receives traffic data from a NetFlow V9 compatible device and shows
the traffic by type. Please make sure the sensor matches the NetFlow version your device is
exporting! There are several filter options available to divide traffic into different channels.
Note: In order for the sensor to work, NetFlow export of the respective version must be
enabled on the device. The device must send the flow data stream to the IP address of the
PRTG probe system on which the sensor is set up (either a local or remote probe).
For a general introduction to the technology behind flow monitoring, please see Monitoring
Bandwidth via Flows 1138 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
470
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
NetFlow Specific Settings
Receive NetFlow
Packets on UDP Port
Enter the UDP port number on which the flow packets are
received. It must match the one you have configured in the
NetFlow export options of your hardware router device. Please
enter an integer value. Please use a different port for each
NetFlow device, as traffic is distinguished by port, not by IP
address! Note: When configuring export, please make sure you
select the appropriate NetFlow version for this sensor.
Receive NetFlow
Packets on IP
Select the IP address(es) on which PRTG listens to NetFlow
packets. The list of IP addresses shown here is specific to your
setup. To select an IP address, add a check mark in front of the
respective line. The IP address selected here must match the one
configured in the NetFlow export options of your hardware router
device. Note: When configuring export, please make sure you
select the appropriate NetFlow version for this sensor.
Active Flow Timeout
(Minutes)
Enter a time span in minutes after which new flow data must be
received. If the timeout is reached and no new data is received,
the sensor may switch to an Unknown status. Please enter an
integer value. We recommend setting this one minute longer than
the respective timeout configured in your hardware router device.
Note: If you set this value too low, flow information might get lost!
Log Stream Data to
Disk (for Debugging)
Define if the probe will write a log file of the stream and packet
data to disk. Choose between:
§ None (recommended): Do not write additional log files.
Recommended for normal use cases.
§ Only for the 'Other' channel: Only write log files of data that is
not filtered otherwise and therefore accounted to the default
Other channel.
§ All stream data: Write log files for all data received.
Note: Use with caution! When enabled, huge data files can be
created. Please use for a short time and for debugging purposes
only.
Channel Configuration
Channel Selection
Define the categories the traffic will be accounted 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.
2011-10-17
471
Part VI: Ajax Web Interface—Device and Sensor Setup
Channel Configuration
§ Remote Control: Traffic caused by remote control applications,
such as RDP, SSH, Telnet, VNC.
§ Infrastructure: Traffic caused by network services, such as
DHCP, DNS, Ident, ICMP, SNMP.
§ NetBIOS: Traffic caused by NetBIOS communication.
§ Other Protocols: 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 traffic will be divided. For
each group, choose between:
§ No: Do not account traffic of this group in an own channel. All
traffic of this group will be accounted to the default channel
named Other.
§ Yes: Count all traffic of this group and summarize it into one
channel.
§ Detail: Count all traffic of this group and further divide it into
different channels. The traffic will appear in several channels as
shown in the Content 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 analyse.
Filtering
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
Filter Rules for xFlow and Packet Sniffer Sensors 1186 section.
Exclude Filter
First, the filters defined in the Include Filter field are considered.
From this subset, you can explicitly exclude traffic, using the
same syntax. For detailed information, please see Filter Rules for
xFlow and Packet Sniffer Sensors 1186 section.
Sensor Display
472
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Primary Toplist
Primary Toplist
Define which will be your primary toplist. It will be shown in maps
and initially when selecting the Toplists tab. Choose from:
§ Top Talkers
§ Top Connections
§ Top Protocols
§ [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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
473
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
474
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
2011-10-17
475
Part VI: Ajax Web Interface—Device and Sensor Setup
Toplists
For all xFlow and packet sniffer sensors, there is a Toplists tab available. Using toplists, you
can review traffic data of small time periods in great detail. For more information, please see
Toplists 955 section.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
118
section.
Related Topics
§ Filter Rules for xFlow and Packet Sniffer Sensors 1186
§ Channel Defintions for xFlow and Packet Sniffer Sensors 1189
476
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.41 NetFlow V9 (Custom) Sensor
The NetFlow V9 (Custom) sensor receives traffic data from a NetFlow V9 compatible device
and shows the traffic by type. Please make sure the sensor matches the NetFlow version your
device is exporting! In this custom sensor, you can define your own channel definitions to
divide traffic into different channels.
Note: In order for the sensor to work, NetFlow export of the respective version must be
enabled on the device. The device must send the flow data stream to the IP address of the
PRTG probe system on which the sensor is set up (either a local or remote probe).
For a general introduction to the technology behind flow monitoring, please see Monitoring
Bandwidth via Flows 1138 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-17
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
477
Part VI: Ajax Web Interface—Device and Sensor Setup
NetFlow Specific Settings
Receive NetFlow
Packets on UDP Port
Enter the UDP port number on which the flow packets are
received. It must match the one configured in the NetFlow export
options of your hardware router device. Please enter an integer
value. Please use a different port for each NetFlow device, as
traffic is distinguished by port, not by IP address! Note: When
configuring export, please make sure you select the appropriate
NetFlow version for this sensor.
Receive NetFlow
Packets on IP
Select the IP address(es) on which PRTG listens to NetFlow
packets. The list of IP addresses shown here is specific to your
setup. To select an IP address, add a check mark in front of the
respective line. The IP address selected here must match the one
configured in the NetFlow export options of your hardware router
device. Note: When configuring export, please make sure you
select the appropriate NetFlow version for this sensor.
Active Flow Timeout
(Minutes)
Enter a time span in minutes after which new flow data must be
received. If the timeout is reached and no new data is received,
the sensor may switch to an Unknown status. Please enter an
integer value. We recommend setting this one minute longer than
the respective timeout configured in your hardware router device.
Note: If you set this value too low, flow information might get lost!
Channel Definition
Please enter a channel definition to divide the traffic into different
channels. Write each definition in one line. For detailed
information, please see Channel Defintions for xFlow and
Packet Sniffer Sensors 1189 section. All traffic for which no channel
is defined will be accounted to the default channel named Other.
Note: Extensive use of many filters can cause load problems on
your probe system. We recommend defining specific, well-chosen
filters for the data you really want to analyse.
Log Stream Data to
Disk (for Debugging)
Define if the probe will write a log file of the stream and packet
data to disk. Choose between:
§ None (recommended): Do not write additional log files.
Recommended for normal use cases.
§ Only for the 'Other' channel: Only write log files of data that is
not filtered otherwise and therefore accounted to the default
Other channel.
§ All stream data: 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.
478
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Filtering
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
Filter Rules for xFlow and Packet Sniffer Sensors 1186 section.
Exclude Filter
First, the filters defined in the Include Filter field are considered.
From this subset, you can explicitly exclude traffic, using the
same syntax. For detailed information, please see Filter Rules for
xFlow and Packet Sniffer Sensors 1186 section.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Primary Toplist
Primary Toplist
Define which will be your primary toplist. It will be shown in maps
and initially when selecting the Toplists tab. Choose from:
§ Top Talkers
§ Top Connections
§ Top Protocols
§ [Any custom toplists you have added]
2011-10-17
479
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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.
Scanning Interval
Scanning Interval
480
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
481
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
482
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Toplists
For all xFlow and packet sniffer sensors, there is a Toplists tab available. Using toplists, you
can review traffic data of small time periods in great detail. For more information, please see
section
§ Toplists
955
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
118
section.
Related Topics
§ Filter Rules for xFlow and Packet Sniffer Sensors 1186
§ Channel Defintions for xFlow and Packet Sniffer Sensors 1189
2011-10-17
483
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.42 Oracle SQL Sensor
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 query—if configured—have 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.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
484
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-11-07
Part VI: Ajax Web Interface—Device and Sensor Setup
Oracle Specific Data
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.
Port
Enter the port number that will be used for the connection.
Default value is 1521. Please enter an integer value.
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 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.
Data
SQL-Expression
Enter the SQL expression that will be queried from the database.
For example, such an expression could be: SELECT sum(salary)
FROM hr.employees. Note: When a cursor is returned (i.e. with a
SELECT statement), only the first row of data will be processed.
Postprocessing
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 string 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.
§ Monitor 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 943 whenever a sensor value changes.
Condition "Warning"
2011-11-07
This field is only visible if numeric results is enabled above. Define
a condition of the returned numeric SQL result set that will set the
sensor to a Warning status. Choose between:
485
Part VI: Ajax Web Interface—Device and Sensor Setup
§ none: Do not set the sensor to Warning status for any
condition.
§ equals: Result set must be the same as the value provided
below.
§ is above: Result set must be above the value provided below.
§ lower than: Result set must be below the value provided below.
§ does not equal: Result set must be unequal to the value
provided below.
Note: This threshold check the SQL result set only. You can set
additional thresholds in the sensor's channel settings 938 .
Value
This field is only visible if numeric results is enabled above. Enter
a value of the returned numeric SQL result set that will set the
sensor into a Warning status. Please enter an integer or float
value.
Condition "Down"
This field is only visible if numeric results is enabled above. Define
a condition of the returned numeric SQL result set that will set the
sensor to a Down status. Choose between:
§ none: Do not set the sensor to Down status for any condition.
§ equals: Result set must be the same as the value provided
below.
§ is above: Result set must be above the value provided below.
§ lower than: Result set must be below the value provided below.
§ does not equal: Result set must be unequal to the value
provided below.
Note: This threshold check the SQL result set only. You can set
additional thresholds in the sensor's channel settings 938 .
486
Value
This field is only visible if numeric results is enabled above. Enter
a value of the returned numeric SQL result set that will set the
sensor to a Down status. Please enter an integer value.
Response must
include
This field is only visible if string results is enabled above. Enter a
string that must be part of the returned SQL string. If it is not, the
sensor will be set to an error state. Please enter a string or leave
the field empty.
Response must not
include
This field is only visible if string results is enabled above. Enter a
string that must not be part of the returned SQL string. If it is, the
sensor will be set to an error state. Please enter a string or leave
the field empty.
2011-11-07
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-11-07
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
487
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
488
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-11-07
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-11-07
118
section.
489
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.43 Packet Sniffer Sensor
Monitors the headers of data packets passing a local network card using built-in packet
sniffer. You can choose from predefined channels. Only header traffic will be analyzed.
Note: This sensor can be set up on a Probe Device only! By default, you can only monitor
traffic passing the PRTG probe system on which's Probe Device the sensor is set up (either a
local or remote probe). To monitor other traffic in your network, you can configure a
monitoring port (if available) to which the switch sends a copy of all traffic. You can then
physically connect this port to a network card of the computer the PRTG probe (either local or
remote probe) is running on. This way, PRTG will be able to analyze the complete traffic that
passes through the switch. This feature of your hardware may be called Switched Port
Analyzer (SPAN), port mirroring, or port monitoring.
For a general introduction to the technology behind packet sniffing, please see Monitoring
Bandwidth via Packet Sniffing 1135 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
490
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sniffer specific
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
Filter Rules for xFlow and Packet Sniffer Sensors 1186 section.
Exclude Filter
First, the filters defined in the Include Filter field are considered.
From this subset, you can explicitly exclude traffic, using the
same syntax. For detailed information, please see Filter Rules for
xFlow and Packet Sniffer Sensors 1186 section.
Network Adapters
Define the network adapters that will be monitored by the sensor.
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.
Log Stream Data to
Disk (for Debugging)
Define if the probe will write a log file of the stream and packet
data to disk. Choose between:
§ None (recommended): Do not write additional log files.
Recommended for normal use cases.
§ Only for the 'Other' channel: Only write log files of data that is
not filtered otherwise and therefore accounted to the default
Other channel.
§ All stream data: Write log files for all data received.
Note: Use with caution! When enabled, huge data files can be
created. Please use for a short time and for debugging purposes
only.
Channel Configuration
Channel Selection
Define the categories the traffic will be accounted 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.
§ Remote Control: Traffic caused by remote control applications,
such as RDP, SSH, Telnet, VNC.
§ Infrastructure: Traffic caused by network services, such as
DHCP, DNS, Ident, ICMP, SNMP.
§ NetBIOS: Traffic caused by NetBIOS communication.
2011-10-17
491
Part VI: Ajax Web Interface—Device and Sensor Setup
Channel Configuration
§ Other Protocols: 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 traffic will be divided. For
each group, choose between:
§ No: Do not account traffic of this group in an own channel. All
traffic of this group will be accounted to the default channel
named Other.
§ Yes: Count all traffic of this group and summarize it into one
channel.
§ Detail: Count all traffic of this group and further divide it into
different channels. The traffic will appear in several channels as
shown in the Content 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 analyse.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
492
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Primary Toplist
Primary Toplist
Define which will be your primary toplist. It will be shown in maps
and initially when selecting the Toplists tab. Choose from:
§ Top Talkers
§ Top Connections
§ Top Protocols
§ [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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
493
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
494
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
2011-10-17
495
Part VI: Ajax Web Interface—Device and Sensor Setup
Toplists
For all xFlow and packet sniffer sensors, there is a Toplists tab available. Using toplists, you
can review traffic data of small time periods in great detail. For more information, please see
Toplists 955 section.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
118
section.
Related Topics
§ Filter Rules for xFlow and Packet Sniffer Sensors 1186
§ Channel Defintions for xFlow and Packet Sniffer Sensors 1189
496
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.44 Packet Sniffer (Custom) Sensor
Monitors the headers of data packets passing a local network card using built-in packet
sniffer. You can define your own channels. There are no predefined channels for this sensor
type. Only header traffic will be analyzed.
Note: This sensor can be set up on a Probe Device only! By default, you can only monitor
traffic passing the PRTG probe system on which's Probe Device the sensor is set up (either a
local or remote probe).To monitor other traffic in your network, you can configure a
monitoring port (if available) to which the switch sends a copy of all traffic. You can then
physically connect this port to a network card of the computer the PRTG probe (either local or
remote probe) is running on. This way, PRTG will be able to analyze the complete traffic that
passes through the switch. This feature of your hardware may be called Switched Port
Analyzer (SPAN), port mirroring, or port monitoring.
For a general introduction to the technology behind packet sniffing, please see Monitoring
Bandwidth via Packet Sniffing 1135 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-17
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
497
Part VI: Ajax Web Interface—Device and Sensor Setup
Sniffer specific
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
Filter Rules for xFlow and Packet Sniffer Sensors 1186 section.
Exclude Filter
First, the filters defined in the Include Filter field are considered.
From this subset, you can explicitly exclude traffic, using the
same syntax. For detailed information, please see Filter Rules for
xFlow and Packet Sniffer Sensors 1186 section.
Channel Definition
Please enter a channel definition to divide the traffic into different
channels. Write each definition in one line. For detailed
information, please see Channel Defintions for xFlow and
Packet Sniffer Sensors 1189 section. All traffic for which no channel
is defined will be accounted to the default channel named Other.
Note: Extensive use of many filters can cause load problems on
your probe system. We recommend defining specific, well-chosen
filters for the data you really want to analyse.
Network Adapters
Define the network adapters that will be monitored by the sensor.
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.
Log Stream Data to
Disk (for Debugging)
Define if the probe will write a log file of the stream and packet
data to disk. Choose between:
§ None (recommended): Do not write additional log files.
Recommended for normal use cases.
§ Only for the 'Other' channel: Only write log files of data that is
not filtered otherwise and therefore accounted to the default
Other channel.
§ All stream data: 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
498
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Primary Toplist
Primary Toplist
Define which will be your primary toplist. It will be shown in maps
and initially when selecting the Toplists tab. Choose from:
§ Top Talkers
§ Top Connections
§ Top Protocols
§ [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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
499
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
500
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
2011-10-17
501
Part VI: Ajax Web Interface—Device and Sensor Setup
Toplists
For all xFlow and packet sniffer sensors, there is a Toplists tab available. Using toplists, you
can review traffic data of small time periods in great detail. For more information, please see
Toplists 955 section.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
118
section.
Related Topics
§ Filter Rules for xFlow and Packet Sniffer Sensors 1186
§ Channel Defintions for xFlow and Packet Sniffer Sensors 1189
502
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.45 Ping Sensor
The Ping sensor performs one or more Pings to monitor the availability of a device. When
using more than one Ping per interval, it also measures minimum and maximum Ping time as
well as packet loss in percent.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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 (seconds)
2011-10-31
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.
503
Part VI: Ajax Web Interface—Device and Sensor Setup
Ping Settings
Packet Size (Bytes)
Enter the packet size in bytes for the Ping. You can choose any
value between 1 and 10000. We recommend using the default
value.
Ping Method
Define the kind of Ping check that will be performed. Choose
between:
§ Send one single Ping: With each scanning interval, send a
single Ping only. A sensor in this setting will show the Ping time
only. This setting is good for simply availability monitoring.
§ Send multiple Ping request: With each scanning interval, send
multiple Pings in a row. A sensor in this setting will also show
minimum and maximum Ping time as well as packet loss (in
percent). This setting is good if you want to create reports
about average Ping times out of a series of ping requests. Note:
When using multiple request, all of them have to get lost in
order for the sensor to switch to a Down status. For example, if
there is only one Ping request answered in a series of five, the
sensor will still show a green Up status.
Ping Count
This field is only visible if sending multiple Pings is enabled
above. Enter the number of Pings that are sent in a row for one
interval. Please enter an integer value.
Ping Delay (in ms)
This field is only visible if sending multiple Pings is enabled
above. Enter the time in milliseconds PRTG has to wait between
two Ping requests. Please enter an integer value. Note: Increase
the value if the target device drops Ping packets due to
denial-of-service (DOS) suspicion.
Auto Acknowledge
You can define that a Down status of this sensor will be
acknowledged 121 automatically.
§ Show "Down" status on error (default): Do not automatically
acknowledge an alarm if this sensor changes to a Down status.
§ Show "Down (Acknowledged)" status on error: Automatically
acknowledge an alarm. If this sensor changes to a Down status,
it will automatically change to Down (Acknowledged). Note:
The sensor will also go through a Down status, so any sensor
state triggers 943 using this will still provoke notifications, as
configured.
504
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-31
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
505
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
506
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
More
Knowledge Base: How to create/customize statistical PING sensor?
§ http://www.paessler.com/knowledgebase/en/topic/1873
Knowledge Base: Can I create an inverse Ping sensor?
§ http://www.paessler.com/knowledgebase/en/topic/10203
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
2011-10-31
507
Part VI: Ajax Web Interface—Device and Sensor Setup
Others
For more general information about settings, please see Object Settings
508
118
section.
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.46 Ping Jitter Sensor
The Ping Jitter sensor sends a series of Pings to the given URI to determine the statistical
jitter. The Real Time Jitter value is updated every time a packet is received using the formula
described in RFC 1889:
Jitter = Jitter + ( abs( ElapsedTime – OldElapsedTime ) – Jitter ) / 16
The Statistical Jitter value is calculated on the first x packets received using the statistical
variance formula:
Jitter Statistical = SquareRootOf( SumOf( ( ElapsedTime[i] – Average) ^ 2 ) /
( ReceivedPacketCount – 1 ) )
Requirement: .NET Framework
This sensor type requires the Microsoft .NET Framework to be installed on the computer
running the PRTG probe: Either on the local system (on every node, if in a cluster), or on the
system running the remote probe 1194 . If the framework is missing, you cannot create this
sensor.
Required .NET version: 2.0.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
2011-10-27
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
509
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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 will be sent. Please enter an
integer value.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
510
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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.
Scanning Interval
Scanning Interval
2011-10-27
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
511
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
512
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-27
118
section.
513
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.47 Pingdom Sensor
The Pingdom sensor queries an account at Pingdom.com and retrieves values for one "check"
configured in the respective Pingdom account. With every scanning interval, the sensor will
always catch the last value available in the "detailed check log" of your Pingdom account.
Requirement: .NET Framework
This sensor type requires the Microsoft .NET Framework to be installed on the computer
running the PRTG probe: Either on the local system (on every node, if in a cluster), or on the
system running the remote probe 1194 . If the framework is missing, you cannot create this
sensor.
Required .NET version: 2.0.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
514
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
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
Please enter the username of the Pingdom account you want to
query. Please enter a string.
Password
Please enter the password of the Pingdom account you want to
query. Please enter a string.
If Value Changes
Define what shall be done in case the value of this sensor
changes. You can choose between:
· Ignore changes (default): No action will be taken on change.
· Trigger 'change' notification: 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 943 whenever the sensor value changes.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
2011-10-17
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
515
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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.
Scanning Interval
Scanning Interval
516
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 . Note: Please make sure you select
the same scanning interval you configured for the "check" in your
Pingdom account. Only if the intervals match PRTG can catch
every measurement from your "check".
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
517
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
518
118
section.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.48 POP3 Sensor
The POP3 sensor monitors a mail server using Post Office Protocol version 3 (POP3). It shows
the response time of the server.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-27
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
519
Part VI: Ajax Web Interface—Device and Sensor Setup
Pop3 Specific
Timeout
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.
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.
Security
Specifiy if an encryption will be used for the connection. Choose
between:
§ Encrypt data using Transport-Level Security (TLS)
§ No encryption (use plain text)
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
520
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
Pop3 Authorisation
POP3 Authentication
Type
Select the kind of authentication for the POP3 connection. Choose
between:
· Without Login: Monitor the connection to the POP3 server only.
· Username and Password: Log into the POP3 server with user
name and password (simple login, non-secure).
· 128-bit MD5 hash value (APOP): Send the password in an
encrypted form using APOP. This option must be supported by
the POP3 server you're connecting to.
Username
This field is only visible if an option with login is selected above.
Enter a username for POP3 authentication. Please enter a string.
Password
This field is only visible if an option with login is selected above.
Enter a password for POP3 authentication. Please enter a string.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
2011-10-27
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
521
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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.
Scanning Interval
Scanning Interval
522
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-27
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
523
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
524
118
section.
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.49 POP3 Email Count Sensor
The POP3 Email Count sensor connects to a POP3 email account and returns the number of
emails stored in it. Additionally, you can filter by to or from address, or by subject, to only
count mails matching the search pattern.
Requirement: .NET Framework
This sensor type requires the Microsoft .NET Framework to be installed on the computer
running the PRTG probe: Either on the local system (on every node, if in a cluster), or on the
system running the remote probe 1194 . If the framework is missing, you cannot create this
sensor.
Required .NET version: 2.0.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-27
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
525
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Settings
Username
Define the username of the POP3 account you want to log into.
Note: As POP3 server, this sensor will use the parent device's IP
Address/DNS Name value.
Password
Define the passwort for the POP3 account. Note: As POP3 server,
this sensor will use the parent device's IP Address/DNS Name
value.
Mailserver POP3 Port
Define the port number the POP3 server is running at. Please
enter an integer value. Note: As POP3 server, this sensor will use
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 will use the parent device's
hostname.
Filter To Address
Optionally define a To address. Only mails containing this will be
counted by the sensor. Please enter a string or leave the field
empty.
Filter From Address
Optionally define a From address. Only mails containing this will
be counted by the sensor. Please enter a string or leave the field
empty.
Filter Subject Content
Optionally define an email Subject. Only mails containing this will
be counted by the sensor. Please enter a string or leave the field
empty.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
526
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-27
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
527
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
528
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
2011-10-27
529
Part VI: Ajax Web Interface—Device and Sensor Setup
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
530
118
section.
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.50 Port Sensor
The Port sensor monitors a network service by connecting to its port. It tries to connect to
the specified TCP/IP port number of a device and waits for the request to be accepted.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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
2011-11-15
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
Enter the number of the port the sensor will try to connect to.
Please enter an integer value.
531
Part VI: Ajax Web Interface—Device and Sensor Setup
Advanced Sensor Settings
Command
Define whether a command will be sent after the port is opened.
Choose between:
§ Don't send command: Only check if a connection to the port is
possible.
§ Send command: Open a Telnet session to the respective port
and send the command.
Command
This field is only visible if sending a command is enabled above.
Enter a command that will be sent in Telnet session to the
respective port. You cannot use line breaks, but a simple Telnet
command in a single line only. Please enter a string.
Response
Define if the response received will be further processed. Choose
between:
§ Ignore response: Do not check the response.
§ Check response code (integer): Check if the response matches
a defined response code. Define below.
§ Check response text: Check if the response matches a defined
response text. Define below.
Allowed Code
This field is only visible if response code check is enabled above.
Enter a code that must be returned. If it does not match the
sensor will be set to a Down status. Please enter an integer value.
Check For Existing
Keywords (Positive)
This setting is only visible if text processing is activated above.
Check if a certain keyword is part of the received value. If there is
no match, the sensor will show a "Down" status.
§ Disable: Do not check for positive keywords.
§ Enable keyword check (positive): Check if a certain keyword
exists in the received value. Define below.
Text Must Include
This setting is only visible if keyword check is activated above.
Enter a search string that must be contained in the returned
value.
For Keyword Search
Use
Define the method you want to provide the search string with.
Choose between:
§ Plain Text: Search for a simple string.
§ Regular Expression: Search using a regular expression. For
more details, see Regular Expressions 1192 section.
532
2011-11-15
Part VI: Ajax Web Interface—Device and Sensor Setup
Check For Existing
Keywords (Positive)
This setting is only visible if text processing is activated above.
Check if a certain keyword is part of the received value. If there is
no match, the sensor will show a "Down" status.
§ Disable: Do not check for positive keywords.
§ Enable keyword check (positive): Check if a certain keyword
exists in the received value. Define below.
Check For Existing
Keywords (Negative)
This setting is only visible if text processing is activated above.
Check if a certain keyword is not part of the received value. If
there is a match, the sensor will show a "Down" status.
§ Disable: Do not check for negative keywords.
§ Enable keyword check (negative): Check if a certain keyword
does not exist in the received value. Define below.
Text Must Not Include
This setting is only visible if keyword check is activated above.
Enter a search string that must not be contained in the returned
value.
For Keyword Search
Use
Define the method you want to provide the search string with.
Choose between:
§ Plain Text: Search for a simple string.
§ Regular Expression: Search using a regular expression. For
more details, see Regular Expressions 1192 section.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
2011-11-15
533
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
534
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-11-15
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-11-15
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
535
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
536
118
section.
2011-11-15
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.51 QoS (Quality of Service) One Way Sensor
The QoS (Quality of Service) One Way sensor monitors parameters regarding the quality of a
network connection between two probes, which is important, for example, when using Voice
over IP (VoIP) over this connection. The sensor sends a series of UDP packets from the parent
probe to another probe and measures packet loss, jitter, Packet Delay Variation (PDV), etc.
Note: In order for this sensor to work, there has to be at least one remote probe 1193
configured in your setup. The sensor can be created on the Probe Device of either a local or
remote probe.
For a general introduction to the technology behind Quality of Service monitoring, please
see Monitoring Quality of Service 1144 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-17
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
537
Part VI: Ajax Web Interface—Device and Sensor Setup
Quality of Service Measurement
538
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.
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 1193 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 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 port on which the UDP packets are sent. 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 the system running
the target probe.
Number of Packets
Define how many packets are sent for each scanning interval. We
recommend using 1000. Please enter an integer value.
Size of Packets (Bytes)
Define the size in bytes of the packets sent. We recommend
using 172. Please enter an integer value.
Time between packets
(ms)
Define the size in milliseconds that will be waited between two
packets. We recommend using 20. Please enter an integer value.
DSCP
Enter a Differentiated Services Code Point (DSCP) to mark the
traffic sent by this sensor. This is useful for Class of Service (CoS)
measurements. Enter a value between 0 and 64. Note: This setting
may be ignored on Windows systems prior to Vista. You can check
the PRTG Probe Log file in your PRTG data directory to see if the
traffic control API has been initialized.
802.1p
Enter an IEEE 802.1p priority class to mark the traffic sent by this
sensor. This is useful for Class of Service (CoS) measurements.
Enter a value between 0 and 7. Note: This setting may be ignored
on Windows systems prior to Vista. You can check the PRTG Probe
Log file in your PRTG data directory to see if the traffic control API
has been initialized.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
539
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
540
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-17
118
section.
541
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.52 QoS (Quality of Service) Round Trip Sensor
The QoS (Quality of Service) Round Trip sensor monitors parameters regarding the quality of
a network connection between two probes, which is important, for example, when using
Voice over IP (VoIP) over this connection. The sensor sends a series of UDP packets from the
parent probe to another probe. Then, the traffic is sent back to the original probe. The
sensor measures packet loss, jitter, Packet Delay Variation (PDV), etc.
Note: In order for this sensor to work, there has to be at least one remote probe 1193
configured in your setup. The sensor can be created on the Probe Device of either a local or
remote probe.
For a general introduction to the technology behind Quality of Service monitoring, please
see Monitoring Quality of Service 1144 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
542
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-10-26
Part VI: Ajax Web Interface—Device and Sensor Setup
Quality of Service Measurement
2011-10-26
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.
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 1193 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 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 port on which the UDP packets are sent. 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 the system running
the target probe.
Number of Packets
Define how many packets are sent for each scanning interval. We
recommend using 1000. Please enter an integer value.
Size of Packets (Bytes)
Define the size in bytes of the packets sent. We recommend
using 172. Please enter an integer value.
Time between packets
(ms)
Define the size in milliseconds that will be waited between two
packets. We recommend using 20. Please enter an integer value.
DSCP
Enter a Differentiated Services Code Point (DSCP) to mark the
traffic sent by this sensor. This is useful for Class of Service (CoS)
measurements. Enter a value between 0 and 64. Note: This setting
may be ignored on Windows systems prior to Vista. You can check
the PRTG Probe Log file in your PRTG data directory to see if the
traffic control API has been initialized.
802.1p
Enter an IEEE 802.1p priority class to mark the traffic sent by this
sensor. This is useful for Class of Service (CoS) measurements.
Enter a value between 0 and 7. Note: This setting may be ignored
on Windows systems prior to Vista. You can check the PRTG Probe
Log file in your PRTG data directory to see if the traffic control API
has been initialized.
543
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
544
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-26
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-26
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
545
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
546
118
section.
2011-10-26
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.53 RADIUS Sensor
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, it will show an error.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-17
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
547
Part VI: Ajax Web Interface—Device and Sensor Setup
Radius 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.
User
Define the user name used for authentication at the server. Please
enter a string.
Password
Define the password used for authentication at the server. Please
enter a string.
Secret
Define the shared secret used for authentication at the server.
Please enter a string.
Port
Enter the port number used for connection to the server. Default
value is 1812. Please enter an integer value.
NAS IP Address
Define a valid NAS IP address or leave the field empty.
NAS-Identifier
Enter a NAS identifier. Please enter a string or leave the field
empty.
Use Chap
Add a check mark if you want to use the challenge handshake
authentication protocol.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
548
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
549
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
550
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-17
118
section.
551
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.54 RDP (Remote Desktop) Sensor
The RDP (Remote Desktop) Sensor monitors remote desktop services (RDP, Terminal Services
Client).
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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
552
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.
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.
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-27
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
553
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
554
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-27
118
section.
555
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.55 Sensor Factory Sensor
The Sensor Factory sensor is a powerful tool that allows you to create your own sensor with
channels based on data from other sensors. You can define one or more channels using
formulas that combine monitoring results from other sensors.
Samples for usage are:
· Show single channels of one or more sensors in one graph.
· Use the data from single channels of one or more sensors to calculate new values (for
example, you can subtract, multiply, and divide).
· Create graphs with data from other sensor channels and add horizontal lines at specific
vertical positions.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
556
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Factory Specific Settings
Channel Definition
Enter a channel definition for the sensor. Using a specific syntax,
you can refer to data from channels of other sensors here. You
can also calculate values. Enter one channel definition for each
new channel you want to add to this sensor. Please see section
Define Sensor Channels 560 below.
Error Handling
Define the sensor's behavior if one of the sensors defined above is
in an error state. In this case, you can set the sensor factory
sensor either to error or to warning state. Choose between:
· Factory sensor shows error state when one or more source
sensors are in error state: If at least one sensor used in a
channel definition is in a Down status, the factory sensor will
show a Down status as well until all referred sensors leave this
status. While the factory sensor is down it will still show data of
all available sensor channels.
· Factory sensor shows warning state when one or more
source sensors are in error state: If at least one sensor used
in a channel definition is in a Down status, the factory sensor
will show a Warning status until all referred sensors leave the
Down status.
· Use custom formula: Define the status of the factory sensor by
adding a status definition in the field below.
Status Definition
This field is only visible if custom formula is enabled 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 Status 566 below.
If a Sensor Has No
Data
Choose how this Sensor Factory sensor will react in case a sensor
referred to in the channel definition does not provide any data (for
example, because it is paused or does not exist). Choose between:
§ Do not calculate factory channels that use the sensor: For
channels that are defined using one or more sensor(s) that
deliver no data, no data will be shown. Additionally, the sensor
will show a Warning state.
§ Calculate the factory channels and use zero as source value:
If a sensor used in a channel definition does not deliver any
data, zero values will be filled in instead. The channel will be
calculated and shown using these values.
2011-10-31
557
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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.
Scanning Interval
Scanning Interval
558
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-31
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
559
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Define Sensor Channels
The channels of a Sensor Factory sensor are controlled by the Channel Definition text field.
Using a special syntax you can refer to other sensor channels, calculate values, and add
horizontal lines. You can define factory sensor channels using data from any other sensor's
channels on your PRTG core server.
560
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
Example
You see a definition of two factory sensor channels, both using 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 Health channel (ID 0) of
the Core/Probe Health 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 > 1.
§ <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 it is
not provided a fitting unit string is selected automatically (recommended).
§ <formula> contains the formula to calculate the factory sensor's channel. For the formula,
you can use the following functions: channel() 562 , min() 563 , max() 563 , avg() 563 , or percent
() 564 .
Define Sensor Channels—Formula Calculations
Within a formula the following elements are allowed to perform calculations with the values
that are returned by one or more functions:
§ Basic operations: + (add), - (substract), * (multiply), / (divide)
Example: 3 + 5 * 2
§ Brackets: ( )
Example: 3 * (2 + 6)
§ Compare: = (equal), <> (not equal), > (greater), < (less), >= (greater or equal), <= (less or
equal)
If the compare is true the value is 10,000; if false the value is 0. For delta sensors the
speed is compared.
2011-10-31
561
Part VI: Ajax Web Interface—Device and Sensor Setup
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 will result in a factory sensor showing a calculation with values
from two channels (channel IDs -1 and 1) of two traffic sensors (sensor IDs 2001 and 1004
). The returned values will be 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() Function 564 to make sure you obtain the expected values!
There are calculations you cannot do:
· You cannot add/subtract a delta from a gauge channel (and vice versa).
· You cannot multiply two delta channels.
· You cannot compare a delta with a gauge channel.
· You cannot use a channel of (another) Sensor Factory sensor channel in the formula.
Define Sensor Channels—channel() Function
The channel() function allows to read the data from a channel of a different sensor. The
syntax is:
channel(<sensorId>,<channelId>)
The parameters are:
§ <sensorId> is the ID of the sensor. It is displayed on the sensor details page, in the
Overview tab behind the sensor name.
§ <channelId> is the ID of the sensor channel. It is displayed on the sensor details page, in
the Channels tab for each channel behind the channel name.
562
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
Example
channel(2001,2)
This function reads the data from channel ID 2 of the sensor with the ID 2001.
#1:Sample
channel(2001,2)
This full channel definition reads the data from channel ID 2 of the sensor with the ID 2001
and displays it in the first factory sensor channel (#1), without any additional calculations.
Define Sensor Channels—min() and max() Functions
The min() and max() functions return the minimum or maximum of the two values. The
syntax is:
min(<a>,<b>)
max(<a>,<b>)
Values for <a> and <b> are either numbers or channel()
562
functions.
Examples
min(10,5)
This function in the first line returns 5, as this is the smaller value out of 10 and 5.
min( channel(2001,1),channel(2002,1) )
This function returns the minimum of channel 1 of the sensor with ID 2001 and channel 1
of the sensor with ID 2002.
Define Sensor Channels—avg() Function
The avg() function returns the average of the two values. This equals: (a+b) / 2. The syntax
is:
avg(<a>,<b>)
Values for <a> and <b> are either numbers or channel()
2011-10-31
562
functions.
563
Part VI: Ajax Web Interface—Device and Sensor Setup
Examples
avg(20,10)
This function returns 15: (20+10) / 2 = 15.
avg( channel(2001,1),channel(2002,1) )
This function returns the average of channel 1 of the sensor with ID 2001 and channel 1 of
the sensor with ID 2002.
Define Sensor Channels—percent() Function
The percent() function calculates the percent value of two given values, for example, a
channel and a fixed value. The syntax is:
percent(<source>,<maximum>[,<unit>])
The parameters are:
§ <source> is the value the percent is calculated for. This is usually a channel()
562
function.
§ <maximum> is the limit value used for the percent calculation.
§ [<unit>] is an optional unit the maximum is provided in. You can use constants with this
function (see Constants 566 section below for a list). This can be used for gauge (e.g. Ping
sensors) or delta (e.g. traffic sensors). If no unit is provided 1 will be used. Note: As unit
string % will be added automatically.
PRTG will calculate: <source> / <maximum> * <unit> * 100
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 will result in a factory sensor showing two channels of a traffic
sensor (sensor ID 2001): Traffic in (channel ID 0) and traffic out (channel ID 1). The values
will be displayed as % of maximum bandwidth (100 kilobit/second).
#1:Ping %
percent(channel(2002,0),200)
This full channel definition will result in a factory sensor showing the Ping Time channel
(channel ID 0) of a Ping sensor (sensor ID 2002). The values will be displayed as a
percentage of 200 ms.
564
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
Define Sensor Channels—Horizontal Lines
You can add lines to the graph using a formula without channel() function. Use a fixed value
instead. The syntax is:
#<id>:<name>[<unit>]
<value>
The parameters are:
§ <id> is the ID of the factory sensor's channel and must be a unique number > 1. Although
a horizontal line will not be shown as a channel, the ID has to be unique.
§ <name> is the name of the factory sensor's channel. When used here it will not be
displayed in graphs and tables, but can be used as a comment to describe the nature of
the line.
§ [<unit>] is an optional unit description (e.g. kbit/s). If it is not provided the line is applied
automatically to the scale of the first factory sensor channel. If your factory sensor uses
different units you should provide a unit to make sure the line is added for the right scale.
Please enter the unit exactly as shown in your graphs' legend. If you enter a unit that does
not yet exist in your graph, a new scale will be added automatically.
§ <value> contains a number defining where the line will be shown in the graph.
Examples
#5:Line at 100ms [ms]
100
This channel definition will result in graph showing a horizontal line at the value of 100 on
the ms scale.
#6:Line at 2 Mbit/s [kbit/s]
2000
This channel definition will result in graph showing 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 will result in a factory sensor showing the Ping Time channel
(channel ID 0) of a Ping sensor (sensor ID 2002). Additionally, the sensor's graphs will show
a horizontal line at 120 ms.
2011-10-31
565
Part VI: Ajax Web Interface—Device and Sensor Setup
Define Sensor Channels—Constants
The following constants are defined and can be used in calculations:
§ one = 1
§ kilo = 1000
§ mega = 1000 * kilo
§ giga = 1000 * mega
§ tera = 1000 * giga
§ byte = 1
§ kilobyte = 1024
§ megabyte = 1024 * kilobyte
§ gigabyte = 1024 * megabyte
§ terabyte = 1024 * gigabyte
§ bit = 1/8
§ kilobit = kilo / 8
§ megabit = mega / 8
§ gigabit = giga / 8
§ terabit = tera / 8
Define Sensor Status—status() Function
The status of a Sensor Factory sensor can be controlled by the Status Definition text field, if
the custom formula option is enabled in the Sensor Settings 556 . Using a special syntax you
can define when the factory sensor will change to a Down status. In all other cases the
sensor will be in an Up status. The syntax is:
status(sensorID) <boolean> status(sensorID)
The parameters are:
§ <sensorId> is the ID of the sensor you want to check the status of. The ID is displayed on
the sensor details page, in the Overview tab behind the sensor name.
§ <boolean> is one of the Boolean operators AND, OR, or NOT. If the resulting expression
is true, the factory sensor will change to a Down status.
566
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
Examples
status(2031) AND status(2044)
This will change the factory sensor to a Down status if both sensors, with IDs 2031 and
2044, are Down. Otherwise the factory sensor will show an Up status.
status(2031) OR status(2044)
This will change 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 will show an Up status.
status(2031) NOT status(2044)
This will change 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 will
show an Upstatus.
( status(2031) AND status(2044) ) OR status(2051)
This will change 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 will show 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 compare is 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.
Understanding this, more complex formulas are possible.
2011-10-31
567
Part VI: Ajax Web Interface—Device and Sensor Setup
Example
( status(1031) + status(1032) + status(1033) + status(1034) ) >= 20000
This will change 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 will show an Up
status.
Note: The status() function may also be used in channel definitions 560 . Using this
functionality, it is for example possible to display the numeric status value of sensors in a
factory sensor channel.
More
Knowledge Base: Can I add sensors to Sensor Factory sensors using tags?
§ http://www.paessler.com/knowledgebase/en/topic/5143
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
568
118
section.
2011-10-31
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.56 sFlow Sensor
The sFlow sensor receives traffic data from a sFlow V5 compatible device and shows the
traffic by type. Only header traffic will be analyzed. Please make sure the device matches the
sFlow version V5! There are several filter options available to divide traffic into different
channels.
Note: In order for the sensor to work, sFlow V5 export must be enabled on the device. The
device must send the flow data stream to the IP address of the PRTG probe system on which
the sensor is set up (either a local or remote probe).
For a general introduction to the technology behind flow monitoring, please see Monitoring
Bandwidth via Flows 1138 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-17
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
569
Part VI: Ajax Web Interface—Device and Sensor Setup
sFlow Specific Settings
Receive sFlow Packets
on UDP Port
Enter the UDP port number on which the flow packets are
received. It must match the one you have configured in the sFlow
export options of your hardware router device. Default value is
6343. Please enter an integer value. Please use a different port for
each sFlow device, as traffic is distinguished by port, not by IP
address! Note: When configuring export, please make sure you
select the appropriate sFlow version 5.
Receive sFlow Packets
on IP
Select the IP address(es) on which PRTG listens to sFlow packets.
The list of IP addresses shown here is specific to your setup. To
select an IP address, add a check mark in front of the respective
line. The IP address selected here must match the one configured
in the sFlow export options of your hardware router device. Note:
When configuring export, please make sure you select the
appropriate sFlow version 5.
Channel Configuration
Channel Selection
Define the categories the traffic will be accounted 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.
§ Remote Control: Traffic caused by remote control applications,
such as RDP, SSH, Telnet, VNC.
§ Infrastructure: Traffic caused by network services, such as
DHCP, DNS, Ident, ICMP, SNMP.
§ NetBIOS: Traffic caused by NetBIOS communication.
§ Other Protocols: 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 traffic will be divided. For
each group, choose between:
§ No: Do not account traffic of this group in an own channel. All
traffic of this group will be accounted to the default channel
named Other.
§ Yes: Count all traffic of this group and summarize it into one
channel.
570
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Channel Configuration
§ Detail: Count all traffic of this group and further divide it into
different channels. The traffic will appear in several channels as
shown in the Content 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 analyse.
Filtering
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
Filter Rules for xFlow and Packet Sniffer Sensors 1186 section.
Exclude Filter
First, the filters defined in the Include Filter field are considered.
From this subset, you can explicitly exclude traffic, using the
same syntax. For detailed information, please see Filter Rules for
xFlow and Packet Sniffer Sensors 1186 section.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
2011-10-17
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
571
Part VI: Ajax Web Interface—Device and Sensor Setup
Primary Toplist
Primary Toplist
Define which will be your primary toplist. It will be shown in maps
and initially when selecting the Toplists tab. Choose from:
§ Top Talkers
§ Top Connections
§ Top Protocols
§ [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 185 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.
Scanning Interval
Scanning Interval
572
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
573
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
574
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Toplists
For all xFlow and packet sniffer sensors, there is a Toplists tab available. Using toplists, you
can review traffic data of small time periods in great detail. For more information, please see
Toplists 955 section.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
118
section.
Related Topics
§ Filter Rules for xFlow and Packet Sniffer Sensors 1186
§ Channel Defintions for xFlow and Packet Sniffer Sensors 1189
2011-10-17
575
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.57 sFlow (Custom) Sensor
The sFlow (Custom) sensor receives traffic data from a sFlow V5 compatible device and shows
the traffic by type. Please make sure the device matches the sFlow version V5! There are
several filter options available to divide traffic into different channels.
Note: In order for the sensor to work, sFlow V5 export must be enabled on the device. The
device must send the flow data stream to the IP address of the PRTG probe system on which
the sensor is set up (either a local or remote probe).
For a general introduction to the technology behind flow monitoring, please see Monitoring
Bandwidth via Flows 1138 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
576
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
sFlow Specific Settings
Receive sFlow Packets
on UDP Port
Enter the UDP port number on which the flow packets are
received. It must match the one you have configured in the sFlow
export options of your hardware router device. Default value is
6343. Please enter an integer value. Please use a different port for
each sFlow device, as traffic is distinguished by port, not by IP
address! Note: When configuring export, please make sure you
select the appropriate sFlow version 5.
Receive sFlow Packets
on IP
Select the IP address(es) on which PRTG listens to sFlow packets.
The list of IP addresses shown here is specific to your setup. To
select an IP address, add a check mark in front of the respective
line. The IP address selected here must match the one configured
in the sFlow export options of your hardware router device. Note:
When configuring export, please make sure you select the
appropriate sFlow version 5.
Channel Definition
Please enter a channel definition to divide the traffic into different
channels. Write each definition in one line. For detailed
information, please see Channel Defintions for xFlow and
Packet Sniffer Sensors 1189 section. All traffic for which no channel
is defined will be accounted to the default channel named Other.
Note: Extensive use of many filters can cause load problems on
your probe system. We recommend defining specific, well-chosen
filters for the data you really want to analyse.
Filtering
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
Filter Rules for xFlow and Packet Sniffer Sensors 1186 section.
Exclude Filter
First, the filters defined in the Include Filter field are considered.
From this subset, you can explicitly exclude traffic, using the
same syntax. For detailed information, please see Filter Rules for
xFlow and Packet Sniffer Sensors 1186 section.
Sensor Display
2011-10-17
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
577
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Primary Toplist
Primary Toplist
Define which will be your primary toplist. It will be shown in maps
and initially when selecting the Toplists tab. Choose from:
§ Top Talkers
§ Top Connections
§ Top Protocols
§ [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 185 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.
Scanning Interval
Scanning Interval
578
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
579
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
580
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Toplists
For all xFlow and packet sniffer sensors, there is a Toplists tab available. Using toplists, you
can review traffic data of small time periods in great detail. For more information, please see
Toplists 955 section.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
118
section.
Related Topics
§ Filter Rules for xFlow and Packet Sniffer Sensors 1186
§ Channel Defintions for xFlow and Packet Sniffer Sensors 1189
2011-10-17
581
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.58 Share Disk Free Sensor
The Share Disk Free sensor monitors free disk space of a share (Windows/Samba) using
Server Message Block (SMB). It shows the free space in percent and total.
Note: This sensor only works if no quotas are enabled on the target share. If there are quotas
enabled for the user account this sensor uses to connect to the share, the absolute value will
be okay, but the percentage variable will show wrong values.
Requirement: Server Service
In order to monitor shares on Windows machines, please make sure the LanmanServer
"Server" Windows service is running on the target computer.
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 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
582
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
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).
Share Configuration
Share
Enter the name of the share this sensor will monitor. Only a share
name is allowed here (for example, enter C$). Please do not enter
a complete UNC name here. The server name (\\server\) is taken
from the parent device of this sensor. Note: In order to provide
any shares under Windows, the LanmanServer "Server" Windows
service must be running on the target computer.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
2011-11-22
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
583
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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.
Scanning Interval
Scanning Interval
584
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-11-22
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
585
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
More
Knowledge Base: What can I do if PRTG doesn't succeed with monitoring a share? PE029
PE032
§ http://www.paessler.com/knowledgebase/en/topic/513
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
586
2011-11-22
Part VI: Ajax Web Interface—Device and Sensor Setup
Others
For more general information about settings, please see Object Settings
2011-11-22
118
section.
587
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.59 SMTP Sensor
The SMTP sensor monitors a mail server using Simple Mail Transfer Protocol (SMTP) and
shows the server's response time. 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 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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)
588
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.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
SMTP specific
Port
Enter the number of the port that will be used 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)
Select if the SMTP connection will be secured via SSL. Choose
between:
· Don't use: Do not use encryption for the SMTP connection.
· Use: Connect to the SMTP server using the SSL method selected
below.
SSL-Method
This field is only visible if security is enabled above. Select the SSL
method that will be used when connecting to the server. We
recommend using the default value. Only if you experience
connection problems, try another setting. Choose between:
§ SSL V2
§ SSL V2 or V3
§ SSL V3
§ TLS V1
Authentication
Type
Select the kind of authentication for the SMTP connection. Choose
between:
· None: Do not use any authentication method.
· Username/Password: Authenticate at the SMTP server via
username and password.
2011-10-17
Username
This field is only visible if SMTP authentication is enabled above.
Enter a username for SMTP authentication. Please enter a string.
Password
This field is only visible if SMTP authentication is enabled above.
Enter a password for SMTP authentication. Please enter a string.
589
Part VI: Ajax Web Interface—Device and Sensor Setup
Monitoring
Send Mail
Define if an email will be sent when connecting to the SMTP
server. Choose between:
· None: Do not send an email, just connect to the SMTP server.
· Send Mail: Send an email through the SMTP server. If there is an
error when sending mail, an error message will be triggered and
the sensor will be put in a down state.
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.
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.
Topic
Specify which subject will be used in the sent emails. Please enter
a string or leave the field empty.
Content
Specify which body will be used in the sent emails. Please enter a
string or leave the field empty.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
590
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
591
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
592
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-17
118
section.
593
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.60 SMTP&IMAP Round Trip Sensor
SMTP&IMAP Round Trip sensor monitors the time it takes for an email to reach an Internet
Message Access Protocol (IMAP) mailbox after being sent using Simple Mail Transfer Protocol
(SMTP). It sends an email to the parent device via SMTP and then checks an IMAP mailbox
until the email comes in. The sensor shows the response time of SMTP and IMAP server, and
the sum of both.
Note: Please use dedicated email accounts with this sensor type. If you use more sensors of
this type, please make sure that each sensor uses its own email accounts.
For a general introduction to the technology behind round trip monitoring, please see
Monitoring Email Round Trip 1148 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings 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 Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
594
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Email Settings
2011-10-17
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.
595
Part VI: Ajax Web Interface—Device and Sensor Setup
Step 1: Send email to parent device using SMTP
In this step, you configure how emails will be sent. As SMTP server, the sensor uses the
IP-Address/DNS Name property's value of the device it is added on.
Port
Enter the number of the port that will be used to send an email via
SMTP. Please enter an integer value. For non-secure connections
usually port 25 is used; usually port 465 or 587 for SSL
connections. The actual setting depends on the server you are
connecting to. Please enter an integer value. We recommend using
the default value. If you do not get a connection, please try
another port number.
Timeout for SMTP
Connection (sec)
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.
SMTP Authentication
Type
Select the kind of authentication for the SMTP connection. Choose
between:
· None: Do not use any authentication method.
· Username/Password: Authenticate at the SMTP server via
username and password.
Username
This field is only visible if SMTP authentication is enabled above.
Enter a username for SMTP authentication. Please enter a string.
Password
This field is only visible if SMTP authentication is enabled above.
Enter a password for SMTP authentication. Please enter a string.
TLS (Transport-Level
Security)
Select if the SMTP connection will be secured via SSL. Choose
between:
· Don't use: Do not use encryption for the SMTP connection.
· Use: Connect to the SMTP server using the SSL method selected
below.
SSL-Method
This field is only visible if security is enabled above. Select the SSL
method that will be used when connecting to the server. We
recommend using the default value. Only if you experience
connection problems, try another setting. Choose between:
§ SSL V2
§ SSL V2 or V3
§ SSL V3
§ TLS V1
596
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Step 2: Check an IMAP mailbox until email arrives
In this step, you configure how the sent emails will be received.
IP-Address/DNS Name
Specify the IMAP server. Enter a valid IP address or DNS name.
Mailbox
Specify the IMAP Mailbox (resp. "IMAP folder") you want to check.
Please enter the IMAP mailbox/folder name.
Port
Specify the port that will be used for the IMAP connection. For
non-secure connections usually port 143 is used; usually port 993
for SSL connections. The actual setting depends on the server you
are connecting to. Please enter an integer value. We recommend
using the default value. If you do not get a connection, please try
another port number.
TLS (Transport-Level
Security)
Select if the IMAP connection will be secured via SSL. Choose
between:
· Don't use: Do not use encryption for the SMTP connection.
· Use: Connect to the SMTP server using the SSL method selected
below.
SSL-Method
This field is only visible when TLS is enabled above. Select the SSL
method that will be used when connecting to the IMAP server. We
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.
Maximum Trip Time
(sec)
Enter the number of seconds an email may take to arrive in the
IMAP mailbox. PRTG will repeatedly check the mailbox in the
interval specified above until the email arrives. If it does not arrive
within the maximum trip time, an error message will be triggered
for the sensor. Please enter an integer value.
IMAP Authentication
Type
Select the kind of authentication for the IMAP connection. Choose
between:
· Username and Password (simple)
· Simple Authentication and Security Layer (SASL)
2011-10-17
Username
Enter a username for IMAP authentication. Please enter a string.
Password
Enter a username for IMAP authentication. Please enter a string.
597
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
598
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
599
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
600
118
section.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.61 SMTP&POP3 Round Trip Sensor
SMTP&POP3 Round Trip sensor monitors the time it takes for an email to reach an Post Office
Protocol version 3 (POP3) mailbox after being sent using Simple Mail Transfer Protocol
(SMTP). It sends an email to the parent device via SMTP and then checks a POP3 mailbox until
the email comes in. The sensor shows the response time of SMTP and POP3 server, and the
sum of both.
Note: Please use dedicated email accounts with this sensor type. If you use more sensors of
this type, please make sure that each sensor uses its own email accounts.
For a general introduction to the technology behind round trip monitoring, please see
Monitoring Email Round Trip 1148 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings 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 Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-27
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
601
Part VI: Ajax Web Interface—Device and Sensor Setup
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.
Step 1: Send email to parent device using SMTP
In this step, you configure how emails will be sent. As SMTP server, the sensor uses the
IP-Address/DNS Name property's value of the device it is added on.
Port
Enter the number of the port that will be used to send an email via
SMTP. Please enter an integer value. For non-secure connections
usually port 25 is used; usually port 465 or 587 for SSL
connections. The actual setting depends on the server you are
connecting to. Please enter an integer value. We recommend using
the default value. If you do not get a connection, please try
another port number.
Timeout for SMTP
Connection (sec)
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)
Select if the SMTP connection will be secured via SSL. Choose
between:
· Don't use: Do not use encryption for the SMTP connection.
· Use: Connect to the SMTP server using the SSL method selected
below.
SSL-Method
This field is only visible if security is enabled above. Select the SSL
method that will be used when connecting to the server. We
recommend using the default value. Only if you experience
connection problems, try another setting. Choose between:
§ SSL V2
§ SSL V2 or V3
§ SSL V3
§ TLS V1
602
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
SMTP Authentication
Type
Select the kind of authentication for the SMTP connection. Choose
between:
· None: Do not use any authentication method.
· Username/Password: Authenticate at the SMTP server via
username and password.
2011-10-27
Username
This field is only visible if SMTP authentication is enabled above.
Enter a username for SMTP authentication. Please enter a string.
Password
This field is only visible if SMTP authentication is enabled above.
Enter a password for SMTP authentication. Please enter a string.
603
Part VI: Ajax Web Interface—Device and Sensor Setup
Step 2: Check a POP3 mailbox until email arrives
In this step, you configure how the sent emails will be received.
IP-Address/DNS Name
Specify the POP3 server. Enter a valid IP address or DNS name.
Port
Specify the port that will be used for the POP3 connection. For
non-secure connections usually port 110 is used; usually port 995
for SSL connections. The actual setting depends on the server you
are connecting to. Please enter an integer value. We recommend
using the default value. If you do not get a connection, please try
another port number.
TLS (Transport-Level
Security)
Select if the POP3 connection will be secured via SSL. Choose
between:
· Don't use: Do not use encryption for the SMTP connection.
· Use: Connect to the SMTP server using the SSL method selected
below.
SSL-Method
This field is only visible when TLS is enabled above. Select the SSL
method that will be used when connecting to the IMAP server. We
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.
Maximum Trip Time
(sec)
Enter the number of seconds an email may take to arrive in the
IMAP mailbox. PRTG will repeatedly check the mailbox in the
interval specified above until the email arrives. If it does not arrive
within the maximum trip time, an error message will be triggered
for the sensor. Please enter an integer value.
POP3 Authentication
Type
Select the kind of authentication for the POP3 connection. Choose
between:
· Without Login: Monitor the connection to the POP3 server only.
· Username and Password: Log into the POP3 server with user
name and password (simple login, non-secure).
· 128-bit MD5 hash value (APOP): Send the password in an
encrypted form using APOP. This option must be supported by
the POP3 server you're connecting to.
604
Username
This field is only visible if an option with login is selected above.
Enter a username for POP3 authentication. Please enter a string.
Password
This field is only visible if an option with login is selected above.
Enter a username for POP3 authentication. Please enter a string.
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
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 185 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.
Scanning Interval
Scanning Interval
2011-10-27
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
605
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
606
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-27
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-27
118
section.
607
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.62 SNMP APC Hardware Sensor
The SNMP APC Hardware sensor monitors performance counters on an APC UPS device using
Simple Network Management Protocol (SNMP).
For a general introduction to the technology behind SNMP, please see Monitoring via SNMP
1129 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings 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 UPS Specific
Library OIDs
Select the performance counters you want to add a sensor for. A
list of available counters for your device is shown with category
and name. Please choose one or more by adding a check mark in
front of the respective line. For each counter one sensor will be
created.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
608
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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 UPS Specific
Selected Interface
Shows the name of the interface (performance counter) monitored
by this sensor. Once a sensor is created this value cannot be
changed. It is shown for reference purposes only. If you need to
change this, please add the sensor anew.
Unit String
Define the unit of the numerical data that 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 shall 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' notification: 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 943 whenever the sensor value changes.
Sensor Display
Primary Channel
2011-10-17
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
609
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
610
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
611
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
612
118
section.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.63 SNMP Custom Sensor
Monitors a numerical value returned by a specific OID using Simple Network Management
Protocol (SNMP).
For a general introduction to the technology behind SNMP, please see Monitoring via SNMP
1129 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
OID values
Channel Name
Enter a name for the channel the results at the given OID will be
will shown in. You can change this value later in the sensor's
channel settings 938 .
Value Type
Select how the results at the given OID will be handled. Choose
between:
§ Gauge (unsigned Integer): For integer values, such as 10 or
120.
§ Gauge (signed integer): For integer values, such as -12 or 120.
§ Gauge (float): For float values, such as -5.80 or 8.23.
§ Delta (Counter): For counter values. PRTG will calculate the
difference between the last and the current value.
Once a sensor is created this value cannot be changed. 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 Settings 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.
2011-10-28
613
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
OID values
OID value
Enter the OID of the SNMP object you want to receive numerical
data from.
Unit String
Define the unit of the numerical data that will be received at the
given OID. Please enter a string.
Value Type
Shows the value type of the numerical data that will be received at
the given OID.Once a sensor is created this value cannot be
changed. 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 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 shall be done in case the value of this sensor
changes. You can choose between:
· Ignore changes (default): No action will be taken on change.
· Trigger 'On Change' notification: 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 943 whenever the sensor
value changes.
614
2011-10-28
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-28
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
615
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
616
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-28
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channel Unit Configuration
Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Note: Custom channel types can be set on sensor level only.
More
Knowledge Base: How do I find out what OID I need to use for a custom sensor?
2011-10-28
617
Part VI: Ajax Web Interface—Device and Sensor Setup
§ http://www.paessler.com/knowledgebase/en/topic/903
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
618
118
section.
2011-10-28
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.64 SNMP Custom String Sensor
The SNMP Custom String sensor monitors a string returned by a specific OID using Simple
Network Management Protocol (SNMP).
For a general introduction to the technology behind SNMP, please see Monitoring via SNMP
1129 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings tab
later.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
2011-10-28
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
619
Part VI: Ajax Web Interface—Device and Sensor Setup
OID values
OID value
Enter the OID of the SNMP object you want to receive a string
from.
If value changes
Define what shall be done in case the value of this sensor
changes. You can choose between:
· Ignore changes (default): No action will be taken on change.
· Trigger 'On Change' notification: 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 943 whenever the sensor
value changes.
Response must
include
Define which string must be part of the data that will be received
from the SNMP object at the given OID. If the data does not
include this string, the sensor will be set to an error state. Please
enter a string value or leave the field empty.
Response must not
include
Define which string must not be part of the data that will be
received from the SNMP object at the given OID. If the data does
include this string, the sensor will be set to an error state. Please
enter a string value or leave the field empty.
Minimum length of
string
Define the minimum length of the string that will be received from
the SNMP object at the given OID. If the length is less than this
value, the sensor will be set to an error state. Please enter an
integer value or leave the field empty.
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 length is greater
than this value, the sensor will be set to an error state. Please
enter an integer value or leave the field empty.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
620
2011-10-28
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-28
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
621
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
622
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-28
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
More
Knowledge Base: How do I find out what OID I need to use for a custom sensor?
§ http://www.paessler.com/knowledgebase/en/topic/903
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
2011-10-28
623
Part VI: Ajax Web Interface—Device and Sensor Setup
Others
For more general information about settings, please see Object Settings
624
118
section.
2011-10-28
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.65 SNMP Dell Hardware Sensor
The SNMP Dell Hardware sensor monitors performance counters on a Dell hardware device
using Simple Network Management Protocol (SNMP).
For a general introduction to the technology behind SNMP, please see Monitoring via SNMP
1129 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings 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:
Dell Hardware Specific
Library OIDs
Select the performance counters you want to add a sensor for. A
list of available counters for your device is shown with category
and name. Please choose one or more by adding a check mark in
front of the respective line. For each counter one sensor will be
created.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
2011-10-17
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
625
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
Dell Hardware Specific
Selected Interface
Shows the name of the interface (performance counter) monitored
by this sensor. Once a sensor is created this value cannot be
changed. It is shown for reference purposes only. If you need to
change this, please add the sensor anew.
Unit String
Define the unit of the numerical data that 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 shall 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' notification: 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 943 whenever the sensor value changes.
Sensor Display
Primary Channel
626
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
2011-10-17
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
627
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
628
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
2011-10-17
118
section.
629
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.66 SNMP HP LaserJet Hardware Sensor
The SNMP HP LaserJet Hardware sensor monitors performance counters on a HP LaserJet
hardware device using Simple Network Management Protocol (SNMP).
For a general introduction to the technology behind SNMP, please see Monitoring via SNMP
1129 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 182 . 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 Settings 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:
Dell Hardware Specific
Library OIDs
Select the performance counters you want to add a sensor for. A
list of available counters for your device is shown with category
and name:
§ Toner/Status
§ Paper/Status
§ Jam/Status
Please choose one or more by adding a check mark in front of the
respective line. For each counter one sensor will be created.
Sensor Settings
On the sensor's details page, click on the Settings 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.
630
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
Sensor Name
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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).
HP LaserJet Specific
Selected Interface
Shows the name of the interface (performance counter) monitored
by this sensor. Once a sensor is created this value cannot be
changed. It is shown for reference purposes only. If you need to
change this, please add the sensor anew.
If Value Changes
Define what shall 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' notification: 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 943 whenever the sensor value changes.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
2011-10-17
631
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
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 185 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.
Scanning Interval
Scanning Interval
632
The scanning interval determines the time the sensor waits
between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 1044 .
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Schedules and Dependencies
Schedule
Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 1032 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Dependency Type
Define a dependency type. Dependencies can be used to pause
monitoring for an object depending on the status of another. You
can choose between:
§ Use parent: Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another
dependency.
§ Select object: Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
§ Master object for parent: Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulate
Error Status from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused.
Dependency
2011-10-17
This field is only visible if the select object option is enabled
above. Click on the reading-glass symbol and use the object
selector 132 to choose an object on which the current sensor will
be dependent on.
633
Part VI: Ajax Web Interface—Device and Sensor Setup
Inherit Access Rights
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:
· Inherited: 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.
· Write: 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 System
Administration—User Groups 1064 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
rights to inherited option.
Channels
Click on the Channels tab to change display settings, spike filter, and limits. For detailed
information, please see Sensor Channels Settings 938 section.
Notifications
Click on the Notifications tab to change notification triggers. For detailed information,
please see Sensor Notifications Settings 943 section.
Others
For more general information about settings, please see Object Settings
634
118
section.
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
6.8.67 SNMP Library Sensor
The SNMP Library sensor monitors a device using Simple Network Management Protocol
(SNMP) in combination with a compiled Management Information Base (MIB) library file. This
provides extended monitoring beyond other the SNMP sensors of PRTG.
In order to monitor any SNMP capable device, you can download the manufacturer's MIB files
for these devices, convert them to the Paessler oidlib format and import them into PRTG. To
make your monitoring setup as convienient as possible, PRTG is delivered with pre-compiled
oidlib library files that already contain the Object Identifier (OID) of SNMP counters for the
most common devices in a network.
For a general introduction to the technology behind SNMP, please see Monitoring via SNMP
1129 section.
Add Sensor
Manually add 182 a new sensor to an SNMP device and 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 sub-directory of your PRTG installation
directory—both the ones delivered with PRTG and your own files. For details about directory
paths, please see Data Storage 1202 .
List of SNMP Default Library Files
The file names in the list indicate the potential purpose. Select a name that appears
appropriate for your device 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 an error
message saying that no available interfaces were found on this device. If you see this
message, please hit the Go back and retry button and try with another file. If counters were
found for your device, you will see the sensor's settings.
2011-10-17
635
Part VI: Ajax Web Interface—Device and Sensor Setup
Default OIDLIB Files Overview
The following files are delivered with PRTG and allow to extend your SNMP monitoring for
many devices. Please be aware that not all devices and/or parameters may be supported by
the libraries.
§ APC UPS.oidlib
Can be used to monitor uninterruptible power supplies (UPS) from APC American Power
Conversion Corp.
§ Basic Linux Library (UCD-SNMP-MIB).oidlib
Can be used to monitor basic system parameters on Linux systems, such as memory, disk
and swap, CPU, etc.
§ cisco-interfaces.oidlib
Can be used to monitor Cisco specific parameters.
§ cisco-queue.oidlib
Can be used to monitor Cisco specific parameters.
§ Dell Storage Management.oidlib
Can be used to monitor Dell storage devices. Possible parameters include disk arrays,
battery and power supply, fan and temperature, virtual disk, etc.
§ Dell Systems Management Instrumentation.oidlib
Can be used to monitor the hardware of Dell systems. Possible parameters include
ACPower and battery, alerts, base board, Bios, BMC, chassis, COO, cooling, event log,
firmware, IDE, keyboard, memory, port, network, processor, SCSI, system, temperature,
USB, UUID, etc.
§ Linux SNMP (AX BGP DisMan EtherLike Host).oidlib
Can be used to monitor different aspects of Linux systems. Note: This file can find a very
large number of possible interfaces. It may take a few seconds until the selection table is
shown.
§ Linux SNMP (Framework Proxy Noti v2).oidlib
Can be used to monitor different aspects of Linux systems. Note: This file can find a very
large number of possible interfaces. It may take a few seconds until the selection table is
shown.
§ Linux SNMP (IP Net SNMP Noti OSPF RMON SMUX).oidlib
Can be used to monitor different aspects of Linux systems. Note: This file can find a very
large number of possible interfaces. It may take a few seconds until the selection table is
shown.
§ Linux SNMP (Source TCP UCD UDP).oidlib
Can be used to monitor different aspects of Linux systems. Note: This file can find a very
large number of possible interfaces. It may take a few seconds until the selection table is
shown.
636
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
§ Paessler Common OID Library.oidlib
Can be used to monitor many common hardware devices.
Import MIB Files
Additionally you can create your own oidlib files by importing your device manufacturers' MIB
files, using a the free Paessler MIB Importer. Simply convert your mib files and save the
resulting oidlib files to the \snmplibs sub-folder of your PRTG program directory. For details
about directory paths, please see Data Storage 1202 . For more information and download of
MIB Importer, please see the link in the More 641 section below.
SNMP Library Sensor—Add Sensor Settings
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
SNMP Library Specific
Library
This shows the path to the oidlib file selected before. Once a
sensor is created this value cannot be changed. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew.
Library-OIDs
Select the aspects of the device you want to monitor. A list
specific to your setup is shown. It contains all counters found in
the chosen library that match your device. Select one or more
items by adding a check mark in front of the respective line. For
each selection one sensor will be created when you click the
Continue button.
Sensor Settings
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS
Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings
Sensor Name
2011-10-17
Enter a meaningful name to identify the sensor. The name will be
shown by default in the device tree and in all alarms.
637
Part VI: Ajax Web Interface—Device and Sensor Setup
Basic Sensor Settings
Tags
Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on.
Tags are not case sensitive. We recommend using the default
value. You can add additional tags to it, if you like. Other tags are
automatically inherited 89 from objects further up in the device
tree. Those are not visible here.
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 Library Specific
Selected Interface
Shows the interface monitored by this sensor. Once a sensor is
created this value cannot be changed. It is shown for reference
purposes only. If you need to change this, please add the sensor
anew.
Unit String
Enter a string describing the unit of the returned values. This is
for display purposes only. 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, or
leave the field empty.
Division
If you want to divide the received data by a certain value, enter
the divisor here. Please enter an integer or float value, or leave the
field empty.
Sensor Display
Primary Channel
Select a channel from the list to define it as the primary channel.
In the device tree, the last value of the primary channel will always
be displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Chart Type
Define how different channels will be shown for this sensor.
§ Show channels independently (default): Show an own graph
for each channel.
638
2011-10-17
Part VI: Ajax Web Interface—Device and Sensor Setup
Sensor Display
§ Stack channels on top of each other: 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 Settings 938 settings).
Stack Unit
This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the sele