PRTG Manual

PRTG Net work Monit or User Manual 2013 Paessler AG All rights reserved.
. No parts of this work may be reproduced in any form or by any meansgraphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systemswithout the written permission of the publisher. Products that are referred to in this document may be either trademarks and/or registered trademarks of the respective owners. The publisher and the author make no claim to these trademarks. While every precaution has been taken in the preparation of this document, the publisher and the author assume no responsibility for errors or omissions, or for damages resulting from the use of information contained in this document or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or indirectly by this document. Printed: Oktober 2013 in Nuremberg
Contents
Table of Contents
Part 1 Welcome to PRTG Network M onitor
1 2 3 4 5 About this Document Key Features New in This Version Available Licenses System Requirements Detailed System Requirements 13 14 16 17 19 21
12
Part 2 Quick Start Guide

1 ONEDownload, Installation, and First Login 2 TWOUsing the Configuration Guru 29 32
28
Part 3 Installing the Software

1 2 3 4 5 6 7 8 9 Download PRTG Update From Previous Versions Install a PRTG Core Server Install a PRTG Cluster Enter a License Key Activate the Product Install a PRTG Remote Probe Install the Enterprise Console Uninstall PRTG Products 41 43 47 52 53 56 58 63 67
40
Part 4 Understanding Basic Concepts

1 2 3 4 5 6 7 8 9 10 11 Architecture and User Interfaces Clustering Object Hierarchy Inheritance of Settings Tags Dependencies Scheduling Notifying Data Reporting User Access Rights IPv6 73 76 78 82 84 85 86 87 88 89 92
72
Part 5 Ajax Web InterfaceBasic Procedures

1 Login 2 SSL Certificate Warning 3 General Layout 96 99 102
94
Contents
4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Sensor States Review Monitoring Data Compare Sensors Historic Data Reports Similar Sensors Object Settings Alarms Logs ToDos Working with Table Lists Object Selector Priority and Favorites Pause Context Menus Hover Popup Main Menu Structure
115 118 123 126 130 133 135 137 139 141 143 145 147 148 164 165
Part 6 Ajax Web InterfaceDevice and Sensor Setup

1 Auto-Discovery 2 Create Objects Manually Add a Group Add a Device Add a Sensor 3 Manage Device Tree 4 Root Group Settings 5 Probe Settings 6 Group Settings 7 Device Settings 8 Sensor Settings List of Available Sensor Types Active Directory Replication Errors Sensor ADO SQL Sensor Amazon CloudWatch Sensor AVM FRITZ!Box WAN Interface Sensor Cisco IP SLA Sensor Citrix XenServer Host Sensor Citrix XenServer Virtual Machine Sensor Cluster Probe Health Sensor Core Health Sensor Dell PowerVault MDi Sensor DHCP Sensor DNS Sensor Enterprise Virtual Array Sensor Event Log (Windows API) Sensor Exchange Backup (Powershell) Sensor Exchange Database (Powershell) Sensor Exchange Mailbox (Powershell) Sensor Exchange Mail Queue (Powershell) Sensor 4 181 193 194 200 209 211 213 227 242 261 278 279 295 301 308 316 322 328 334 340 344 348 354 361 367 374 381 388 395 402
180
Contents
Exchange Public Folder (Powershell) Sensor EXE/Script Sensor EXE/Script Advanced Sensor File Sensor File Content Sensor Folder Sensor FTP Sensor FTP Server File Count Sensor Google Analytics Sensor HTTP Sensor HTTP Advanced Sensor HTTP Apache ModStatus PerfStats Sensor HTTP Apache ModStatus Totals Sensor HTTP Content Sensor HTTP Full Web Page Sensor HTTP SSL Certificate Expiry Sensor HTTP Transaction Sensor HTTP XML/REST Value Sensor Hyper-V Cluster Shared Volume Disk Free Sensor Hyper-V Host Server Sensor Hyper-V Virtual Machine Sensor Hyper-V Virtual Network Adapter Sensor Hyper-V Virtual Storage Device Sensor IMAP Sensor INI File Content Check Sensor IP on DNS Blacklist Sensor IPFIX Sensor IPFIX (Custom) Sensor 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 Passive Application Performance Sensor PerfCounter Custom Sensor PerfCounter IIS Application Pool Sensor Ping Sensor Ping Jitter Sensor Pingdom Sensor POP3 Sensor POP3 Email Count Sensor Port Sensor Port Range Sensor Probe Health Sensor
408 415 424 432 438 444 450 456 462 469 476 488 495 502 511 518 524 533 544 551 557 564 571 577 588 594 600 608 616 624 632 637 645 652 660 668 676 684 692 699 706 712 719 726 732 737 743 749 755 762 767 5
Contents
QoS (Quality of Service) One Way Sensor QoS (Quality of Service) Round Trip Sensor RADIUS Sensor RDP (Remote Desktop) Sensor SCVMM Host Sensor SCVMM Virtual Machine Sensor Sensor Factory Sensor sFlow Sensor sFlow (Custom) Sensor SFTP Secure File Transfer Protocol Sensor Share Disk Free Sensor SIP Options Ping Sensor SMTP Sensor SMTP&IMAP Round Trip Sensor SMTP&POP3 Round Trip Sensor SNMP APC Hardware Sensor SNMP Cisco ADSL Sensor SNMP Cisco ASA VPN Connections Sensor SNMP Cisco ASA VPN Traffic Sensor SNMP Cisco CBQoS Sensor SNMP Cisco System Health Sensor SNMP CPU Load Sensor SNMP Custom Sensor SNMP Custom String Sensor SNMP Dell Hardware Sensor SNMP Dell PowerEdge Physical Disk Sensor SNMP Dell PowerEdge System Health Sensor SNMP Disk Free Sensor SNMP GSA System Health Sensor SNMP Hardware Status Sensor SNMP HP LaserJet Hardware Sensor SNMP HP ProLiant Logical Disk Sensor SNMP HP ProLiant Memory Controller Sensor SNMP HP ProLiant Network Interface Sensor SNMP HP ProLiant Physical Disk Sensor SNMP HP ProLiant System Health Sensor SNMP IBM System X Logical Disk Sensor SNMP IBM System X Physical Disk Sensor SNMP IBM System X Physical Memory Sensor SNMP IBM System X System Health Sensor SNMP Library Sensor SNMP Linux Disk Free Sensor SNMP Linux Load Average Sensor SNMP Linux Meminfo Sensor SNMP Linux Physical Disk Sensor SNMP Memory Sensor SNMP NetApp Disk Free Sensor SNMP NetApp Enclosure Sensor SNMP NetApp I/O Sensor SNMP NetApp License Sensor SNMP NetApp Network Interface Sensor 6
771 777 783 788 793 800 807 822 830 838 844 850 856 862 870 877 883 888 893 898 903 909 914 921 929 935 941 947 953 958 963 969 975 981 987 993 999 1005 1011 1017 1023 1031 1039 1044 1049 1057 1063 1069 1075 1081 1087
Contents
SNMP NetApp System Health Sensor SNMP Poseidon Environment Sensor SNMP QNAP Logical Disk Sensor SNMP QNAP Physical Disk Sensor SNMP QNAP System Health Sensor SNMP RMON Sensor SNMP SonicWALL System Health Sensor SNMP SonicWALL VPN Traffic Sensor SNMP Synology Logical Disk Sensor SNMP Synology Physical Disk Sensor SNMP Synology System Health Sensor SNMP System Uptime Sensor SNMP Traffic Sensor SNMP Trap Receiver Sensor SNTP Sensor SSH Disk Free Sensor SSH INodes Free Sensor SSH Load Average Sensor SSH Meminfo Sensor SSH Remote Ping Sensor SSH Script Sensor SSH Script Advanced Sensor SSH VMWare ESX(i) Disk Sensor Syslog Receiver Sensor System Health Sensor TFTP Sensor Traceroute Hop Count Sensor Virtuozzo Container Disk Sensor Virtuozzo Container Network Sensor VMware Host Hardware (WBEM) Sensor VMware Host Hardware Status (SOAP) Sensor VMware Host Performance (SOAP) Sensor VMware Virtual Machine (SOAP) Sensor WBEM Custom Sensor Windows CPU Load Sensor Windows IIS 6.0 SMTP Received Sensor Windows IIS 6.0 SMTP Sent Sensor Windows IIS Application Sensor Windows Last Update Sensor Windows Logged In Users Sensor Windows MSMQ Queue Length Sensor Windows Network Card Sensor Windows Pagefile Sensor Windows Physical Disk Sensor Windows Print Queue Sensor Windows Registry Sensor Windows Scheduled Task Sensor Windows System Uptime Sensor Windows Updates Status (Powershell) Sensor WMI Custom Sensor WMI Custom String Sensor
1093 1099 1104 1109 1115 1120 1126 1131 1137 1142 1147 1152 1157 1164 1170 1175 1184 1190 1196 1202 1209 1218 1226 1232 1239 1243 1249 1254 1260 1266 1272 1278 1284 1291 1297 1303 1309 1315 1322 1328 1334 1341 1348 1354 1361 1367 1375 1382 1388 1394 1401 7
Contents
WMI Event Log Sensor WMI Exchange Server Sensor WMI Exchange Transport Queue Sensor WMI File Sensor WMI Free Disk Space (Multi Drive) Sensor WMI HDD Health Sensor WMI Logical Disk Sensor WMI Memory Sensor WMI Microsoft SQL Server 2005 Sensor (Deprecated) WMI Microsoft SQL Server 2008 Sensor WMI Microsoft SQL Server 2012 Sensor WMI Process Sensor WMI Remote Ping Sensor WMI Security Center Sensor WMI Service Sensor WMI Share Sensor WMI SharePoint Process Sensor WMI Terminal Services (Windows 2008) Sensor WMI Terminal Services (Windows XP/Vista/2003) Sensor WMI UTC Time Sensor WMI Vital System Data (V2) Sensor WMI Volume Sensor WMI Windows Version Sensor WSUS Statistics Sensor 9 Additional Sensor Types (Custom Sensors) 10 Sensor Channels Settings 11 Sensor Notifications Settings
1410 1417 1424 1431 1437 1445 1451 1457 1462 1471 1479 1487 1493 1498 1504 1510 1517 1523 1528 1533 1538 1544 1550 1556 1563 1566 1573
Part 7 Ajax Web InterfaceAdvanced Procedures

Toplists Arrange Objects Clone Object Multi-Edit Create Device Template Geo Maps Notifications Setting Up Notifications Based on Sensor Limits: Example 8 Libraries Libraries Step By Step Management Libraries and Node Settings Context Menus 9 Reports Reports Step By Step View and Run Reports Reports Settings 10 Maps Maps Step By Step Maps Designer 8 1 2 3 4 5 6 7 1586 1591 1592 1595 1600 1603 1609 1611 1619 1622 1626 1629 1635 1636 1639 1642 1645 1655 1658 1660
1584
Contents
Maps Settings 11 Setup Account SettingsMy Account Account SettingsNotifications Account SettingsSchedules System AdministrationSystem and Website System AdministrationNotification Delivery System AdministrationProbes System AdministrationCluster System AdministrationUser Accounts System AdministrationUser Groups System AdministrationAdministrative Tools PRTG StatusSystem Status PRTG StatusAuto-Update PRTG StatusCluster Status PRTG StatusActivation Status Optional Downloads and Add-Ons Chrome Desktop Notifications SupportContact Support
1667 1671 1673 1678 1687 1691 1702 1707 1709 1710 1715 1719 1723 1732 1735 1736 1737 1739 1741
Part 8 Enterprise Console

1 First Start 2 General Layout 3 Menu Tabs and Page Content Devices Libraries Sensors Alarms Maps Reports Logs ToDos Setup Search Results 4 PRTG Servers 5 Options 6 Windows Menu Structure 7 Context Menus 8 Shortcuts Overview 1746 1747 1751 1752 1759 1761 1763 1765 1767 1769 1771 1773 1775 1776 1779 1786 1791 1792
1744
Part 9 Other User Interfaces

1 Mobile Web GUI 2 Smartphone Apps 1797 1801
1796
Part 10 Sensor Technologies

1 2 3 4 Monitoring via SNMP Monitoring via WMI Monitoring via SSH Monitoring Bandwidth via Packet Sniffing 1809 1813 1816 1818
1808
Contents
5 6 7 8 9 10 11
Monitoring Bandwidth via Flows Bandwidth Monitoring Comparison Monitoring Quality of Service and VoIP Monitoring Email Round Trip Monitoring Backups Monitoring Virtual Environments Monitoring Databases
1820 1823 1825 1829 1831 1832 1833
Part 11 Sy stem Administration Tools

1 PRTG Server Administrator 2 PRTG Probe Administrator 1837 1857
1836
Part 12 Advanced Topics

1 2 3 4 5 6 7 8 Active Directory Integration Application Programming Interface (API) Definition Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors Define IP Ranges Define Lookups Regular Expressions Add Remote Probe Remote Probes and Multiple Probes Remote Probe Quick Setup Remote Probe Setup Using Installer Failover Cluster Configuration Failover Cluster Step by Step Data Storage Using Your Own SSL Certificate with PRTG's Web Server Calculating Percentiles 1869 1871 1872 1876 1878 1879 1886 1887 1888 1891 1896 1902 1905 1912 1914 1916
1868
9 10 11 12
Part 13 Appendix
1 2 3 4 Glossary List of Abbreviations Support and Troubleshooting Legal Notices 1919 1923 1926 1927
1918
Index
1929
10
Part 1
Welcome to PRTG Network Monitor
19.07.2013
11
Part 1: Welcome to PRTG Network Monitor |
Welcome to PRTG Network Monitor

Welcome to PRTG Network Monitor! You have chosen an easy-to-use software product that comes with a powerful set of features to monitor your entire network.
Why Network Monitoring is Important

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

PRTG Network Monitor is a powerful network monitoring application for Windows-based systems. It is suitable for small, medium, and large networks and capable of LAN, WAN, WLAN, and VPN monitoring. You can also monitor physical or virtual web, mail, and file servers, Linux systems, Windows clients, routers, and many more. PRTG monitors network availability and bandwidth usage, as well as various other network parameters such as quality of service, memory load, and CPU usages. It provides system administrators with live readings and periodical usage trends to optimize the efficiency, layout, and setup of leased lines, routers, firewalls, servers, and other network components. The software is easy to set up and use and monitors a network using Simple Network Management Protocol (SNMP), Windows Management Instrumentation (WMI), packet sniffer, Cisco NetFlow (as well as 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
19.07.2013
Part 1: Welcome to PRTG Network Monitor | 1 About this Document
1.1
About this Document

This document introduces you to the system concepts of PRTG Net work Monit or and explains how to set up the software to achieve the best monitoring results. You will learn how to plan your monitoring setup, how to set up your devices and sensors, dependencies, reports, notifications, maps, user accounts, and clustering for fail-safe monitoring. This document is also meant as a reference for all available settings. Short contextual help is already provided within the Ajax web interface; in this manual you often get some more help regarding the different options available. This document does not explain monitoring protocols and file formats in-depth. Also, the use of the Application Programming Interface (API) built into PRTG is only briefly addressed. Whenever possible, hyperlinks to more detailed resources are provided, such as articles in the Paessler Knowledge Base. To start using PRTG right away, please see the Quick St art Guide detailed instructions, see the other sections.
28
section. For more
19.07.2013
13
Part 1: Welcome to PRTG Network Monitor | 2 Key Features
1.2
Key Features
PRTG Network Monitor monitors your network and requires no third party software. Conducting a quick ad-hoc download, you do not need to fill web forms and will not have any registration hassles. The installation process requires only a few minutes, as well as the first configuration which is mainly done automatically. The initial setup is achieved by an interactive guidance by the software.
What PRTG Can Be Used For

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

The PRTG installer contains all modules and software necessary to run the monitoring system without the need for third party modules, including: High performance: PRTG's own fast and efficient database system to store the raw monitoring results as well as logs, Toplists, and ToDos (outperforms SQL servers for monitoring data), accessible through Application Programming Interface (API). You can distribute high loads over multiple probes. Low system requirements: an average PC from the year 2007 is sufficient and even a netbook can monitor over thousand sensors.
14
19.07.2013
Part 1: Welcome to PRTG Network Monitor | 2 Key Features
High security standards: SSL encryption for connections and web server, and multiple user accounts with shared and private sensors, as well as rights management, and many more. Built-inSSL secured web server with HTTP and HTTPS support for the user interface. Fast web interface, works as Single Page Application (SPA) to avoid time-extensive reloading of the page. Mail server for automatic email delivery. Flexible alerting including nine notification technologies, for example, email, SMS, syslog and SNMP trap, HTTP request, event log, Amazon SNS, executing scripts, etc. including various triggers, for example, status alerts, limit alerts, threshold alerts, multiple condition alerts, escalation alerts. including dependencies to avoid alarms floods, acknowledging alarms to avoid further notifications for this alarm, and alert scheduling. In-depth report generator to create reports on-the-fly as well as scheduled reports in HTML or Portable Document Format (PDF). Many report templates are available by default. Graphics engine for user-friendly live and historic data charts. Network analysis module to automatically discover network devices and sensors. Distributed monitoring to monitor several networks in different locations. Special features for Managed Service Provider (MSP) to monitor customer networks and increase the quality of service. Data publishing with real time dashboardsprivate and publicincluding live performance and status information. You can design these maps as you like with many different objects, as well as you can integrate external custom objects. Different languages like English, German, Spanish, French, Portuguese, Dutch, Czech, Japanese, and Simplified Chinese. Customizations: The PRTG Application Programming Interface (API) allows you to program your own features and to customize and re-brand PRTG's web interface to your needs. In addition, you can create custom sensors, notifications, and device templates. PRTG Network Monitor supports monitoring up to 20,000 thousand sensors per installation. It can optionally work with multiple remote probes to monitor multiple sites or network segments from one central core installation, and to distribute high loads. You can also configure fail-safe monitoring using a cluster installation to perform automatic failovers. Single failover installations are allowed with every PRTG license. The software is based on Paessler's reliable monitoring technology, which has been constantly improved since 1997 and is already used by more than 150,000 users around the world every day. An outstanding support ensures that your inquiries are answered within one business day in order to ensure best possible network monitoring. 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.
19.07.2013
15
Part 1: Welcome to PRTG Network Monitor | 3 New in This Version
1.3
New in This Version

With ongoing continuous development and rollout, we constantly extend and improve on the functionalities provided by PRTG. Instead of delivering just a few versions distributed over the year with massive changes in every version, PRTG is automatically and seamlessly enhanced with new features and fixesfast and with high quality. There are three release channels for PRTG: St able: best tested version of PRTG for live systems; updated about once or twice a month; for usage on live systems Preview: offering the latest features and fixes; updated about once a week; consider this version as "beta", thus, do not use this version on live systems you have to depend on! Canary : providing "nightly builds"; updated very often; not tested extensively; never use on live systems you have to depend on! Because of these three channels, you can choose either maximum stability, earlier access to new features, or a mixture of both. For an overview of all most recent changes in the current version, please visit the version history on our website. Please see the More 16 section below for more information.
More
Paessler website: PRTG Network Monitor Version History http://www.paessler.com/prtg/history Paessler blog: Version 12 of PRTG introduces "Continuous Rollout" http://www.paessler.com/blog/2012/04/25/
16
19.07.2013
Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses
1.4
Available Licenses
There are four different PRTG flavors available.
Freeware Edition
The Freeware Edition is a good solution to get started with PRTG, or for private use: 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. Note: If you want to use the Freeware Edition, please first install the Trial Edit ion 17 and get a free trial key. After the trial period has ended, your Trial Edition will automatically revert into a Freeware Edition.
Special Edition
The Special Edition has all the features of the Freeware Edition, plus it supports up to 30 sensors. By entering a Special Edition key, you can extend your Freeware Edition. For detailed information, see More 18 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 (not officially supported; a minimum interval of 10 seconds is recommended). Temporary license key must be requested from Paessler's website. Trial period limited to 30 days (automatically reverts to Freeware Edition afterwards). With each license one single failover cluster setup 76 , consisting of two nodes, is included. Cluster installations with two and three failover nodes will require one additional trial license key; a cluster installation with four failover nodes will require two additional trial license keys. After the trial period has ended, a Trial Edition will revert into a Freeware Edition, allowing you to monitor up to 10 sensors for free.
19.07.2013
17
Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses
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. Shortest available monitoring interval is one second (not officially supported; a minimum interval of 10 seconds is recommended). With each license one single failover cluster setup 76 , consisting of two nodes, is included. Cluster installations with two and three failover nodes will require one additional license of the same size; a cluster installation with four failover nodes will require two additional licenses of the same size. For more information about available commercial licenses, please see More
18
section below.
More
Knowledge Base: What is the PRTG Special 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
18
19.07.2013
Part 1: Welcome to PRTG Network Monitor | 5 System Requirements
1.5
System Requirements
In order to install and work with PRTG Network Monitor, you need to meet the following requirements: A PC server or virtual machine with roughly the CPU performance of an average PC built in the year 2007 or later and minimum 1024 RAM memory. For cluster installations, use systems with similar performance. Operating system Microsoft Windows XP, Windows 2003 SP1 or later, Windows 2008 R2, Windows 7, 8, or Server 2012 (all 32-bit or 64-bit). You can also use Windows Vista or 2008 R1, but we recommend not using these systems, because there are known performance issues related to them. Web browser to access the web interface. The following browsers are supported: Google Chrome 27 or later (recommended) Mozilla Firefox 21 or later Microsoft Internet Explorer 9 or 10
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 20,000 sensors are possible. SNMP V3 You will be able to monitor about 5,000 SNMP V3 sensors with an interval of 60 seconds on a common two core computer, and about 10,000 sensors on a four core system (the main limiting factor is your CPU power). WMI Try to keep the number of WMI sensors per probe below 120 sensors (with 60s interval), or 600 sensors (with 300s interval). xFlow (Net Flow, 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 20 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 1887 should be used.
08.10.2013
19
Part 1: Welcome to PRTG Network Monitor | 5 System Requirements
VMware Monit oring Monitoring of VMware is limited to about 20 sensors at a 60 seconds monitoring interval, or 100 sensors at a 5 minutes interval. These limitations issue from the VMware platform. A registry hack is available to boost this to 150 sensors at a 5 minutes interval (this will require a change in the ESX/vCenter configuration). For details please see More 20 section below. To overcome any limitations mentioned above you should distribute the sensors over two remote probes 1887 or more. For detailed information please use the site planner tool to plan large installations. See More 20 section below. We recommend using a dedicated physical machine to run both the PRTG core server and PRTG remote probes. For more information please see the Det ailed Sy st em Requirement s 21 section.
More
Updat e From Previous Versions
43
Knowledge Base: Planning Large Installations of PRTG Network Monitor http://www.paessler.com/knowledgebase/en/topic/26383 Knowledge Base: Paessler PRTG Site Planner Tool http://www.paessler.com/knowledgebase/en/topic/41373 Knowledge Base: How can I speed up PRTGespecially for large installations? http://www.paessler.com/knowledgebase/en/topic/2733 Knowledge Base: Increasing Maximum Connections for VMware Sensors http://www.paessler.com/knowledgebase/en/topic/30643 Knowledge Base: Checklist for Running PRTG on VMware http://www.paessler.com/knowledgebase/en/topic/49193
20
08.10.2013
Part 1: Welcome to PRTG Network Monitor | 5 System Requirements 1 Detailed System Requirements
1.5.1
Detailed Sy stem Requirements

This section lists different aspects of system requirements for PRTG. Please consider these requirements in order to avoid issues while network monitoring. Support ed Operat ing Sy st ems Hardware Requirement s Sample Configurat ions
22 21
22 24
Running PRTG on Virt ual Machines Web Browser Requirement s Screen Resolut ion
25 24
Requirement s for Monit ored Devices Requirement s for t he Windows GUI Requirement s for Mobile Web GUI Requirement s for Smart Phones More
26 26 25
25
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 Microsoft Windows 8 Microsoft Windows Server 2012** * For performance reasons, we do not recommend using Windows Vista or Windows Server 2008 R1, especially when monitoring via Windows Management Instrumentation (WMI). Using these operating systems, you will only be able to add a limited number of WMI sensors! For detailed information, please see More 26 section below. If you need to use Windows Server 2008 R1, we strongly recommend installing Service Pack 2 (SP2). ** Windows Server 2012 in Core mode is not officially supported. The version (32-bit or 64-bit) of the PRTG Core Server depends on the version of your operating system. The 64-bit version of the PRTG Core Server will be installed if
11.10.2013
21
the operating system is a 64-bit Windows system, and the system provides 6GB RAM or more. Otherwise the 32-bit version of the PRTG Core Server will be installed. We recommend you to provide Microsoft .NET Framework versions 3.5 and 4.0 (with latest updates) on all systems running a PRTG probe. Note: Version 4.0 is imperatively needed for monitoring VMware and XenServer virtual environments. More details: Some sensor types need the Microsoft .NET Framework to be installed on the computer running the PRTG probe. This is either on the local system (on every node, if on a cluster probe), or on the system running a remote probe 1888 . Depending on the sensor type, the required versions are 2.0, 3.0, or 4.0. Note: According to the Microsoft website, .NET version 3.5 contains versions 2.0 SP1 and 3.0 SP1. Version 4.0 is not downward compatible, but must be installed side-by-side to older version(s), if required. For best performance of hybrid sensors using Windows Performance Counters and Windows Management Instrumentation (WMI), we recommend Windows 2008 R2 or higher on the computer running the PRTG probe: This is either on the local system (on every node, if on a cluster probe), or on the system running a remote probe 1888 .
Hardware Requirements
Hardware requirements for PRTG Core Service and Probe Service mainly depend on the sensor types and intervals used. The following values are provided as reference for common usage scenarios of PRTG (based on a default sensor interval of 60 seconds). CPU An average PC built in 2007 can easily monitor 1,000 sensors (see sensor type specific notes below). PRTG supports native x86 architectures. RAM memory Minimum requirement: 1024 MB RAM. You will need about 150 KB of RAM per sensor. Hard Disk Drive You will need about 200 KB of disk space per sensor per day (for sensors with 60 second interval). Int ernet connect ion An internet connection is required for license activation (via HTTP or email). There are also non-hardware dependent limitations for some sensor types, for example, WMI and SNMP V3 sensors. These limitations can be overcome by distributing the sensors across multiple remote probes 1887 . 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 26 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.
22
11.10.2013
Large Inst allat ion A
Large Inst allat ion B Net book Inst allat ion DELL PowerEdge 2900 III Intel Xeon QuadCore 1.87 GHz 16 GB Windows 2003 64Bit 20,000 SNMP DELL Inspiron Mini 10 Intel Atom Z520 1.33 GHz
Sy st em
DELL Alienware Intel Core2 QuadCore 2.6 GHz 8 GB
CPU
RAM
1 GB
Operat ing Sy st em
Windows 7 64-Bit 20,000 SNMP 100 Other 400 switches 48 ports
Windows XP 32-Bit 600 SNMP 750 WMI 24 switches 25 ports + 30 Windows server 5 minutes
Sensors
Inst allat ion Corresponds To
400 switches 48 ports
Scanning Int erval
1 minute
1 minute
Number of Probes
Average CPU Load While Monit oring*
3%
20 %
35 %
Average CPU Load While Generat ing Report s*
20 %
30 %
85 %
Average Memory Used
3 GB
3.5 GB
260 MB
Average Dat a Writ t en t o Disk Per Year
800 GB
800 GB
55 GB
Average Net work Load 80 kbit/s
550 kbit/s
150 kbit/s
* CPU load is higher while users are accessing the web interface.
11.10.2013
23
Running PRTG on Virtual Machines

PRTG core server as well as PRTG probe can be run on virtualized platforms. The following platforms were tested successfully:
Virt ual Host Technology VMware ESX/ESXi versions 3.5, 4.0, or 5.0
Client OS Windows XP, Windows 2003 SP1 or later (32/64 bit), Windows Vista, Windows 7 (32/64 bit), Windows 2008 (32/64 bit) Windows XP, Windows 2003 SP1 or later (32/64 bit), Windows 2008 Windows XP, Windows 2003 SP1 or later (32/64 bit), Windows 2008 Windows 2003 Server SP1 or later (32/64 bit), Windows 2008 Server Windows Server 2003 SP1 or later, Windows Server 2008
VMware Server 2.0
XEN Server 5.0
Parallels Virtuozzo Containers
Cloud Hosting Platforms (Amazon EC2, TheRackspaceCloud, and others)
Important notice: We recommend using a dedicated physical machine to run both the PRTG core server and PRTG remote probes. If you run PRTG on a virtual machine, we strongly recommend to stay below 2,000 sensors for performance reasons. Unfortunately, we cannot offer technical support regarding performance and stability problems for PRTG installations on virtual machines that run with more than 5,000 sensors. In this case, please migrate PRTG to one or more, preferably physical, machines. Note: When running PRTG on a virtual machine, do not use dynamic resource allocation, but please make sure that full resources are available to the virtual machine at any time. In our experience, dynamic resource allocation is not working efficiently for a monitoring software and can therefore lead to massive performance issues. Please see also section More
26
regarding running PRTG on VMware.
Web Browser Requirements

The following browsers are officially supported by the PRTG web interface (in order of performance and reliability): Google Chrome 27 or later (recommended) Mozilla Firefox 21 or later
24
11.10.2013
Microsoft Internet Explorer 9 or 10 Note: Internet Explorer 8 or earlier and Opera Browser as well as mobile browsers cannot display the full featured Ajax web int erface 94 . Using these browsers, you can access the feature-limited Mobile Web GUI 1797 , which does not require CSS or Javascript capability. 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.
Screen Resolution
A screen resolution of at least 1024x768 pixels is sufficient for most functions of PRTG. However, we recommend a screen resolution of 1200x800 or higher.
Requirements for Monitored Devices

SNMP monit oring The monitored device(s) must be equipped with SNMP Version 1, 2c, or 3 (i.e., a SNMPcompatible software must be installed on the device). SNMP must be enabled on the device and the machine running PRTG must be granted access to the SNMP interface. WMI monit oring In order to use WMI (Windows Management Instrumentation) monitoring, you will need a Windows network. For client PCs monitored with WMI, only 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 (Net Flow, sFlow) monit oring 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 monit oring Only data packets passing the local machine's network card can be analyzed. Switches with so-called 'monitoring ports' are necessary for network-wide monitoring in switched networks.
Requirements for the Enterprise Console

The optional PRTG Ent erprise Console 1744 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 Mobile Web GUI

The feature-limited mobile web interface is optimized for low bandwidth and mobile access. It has been designed for and tested with iOS (iPhone, iPad), Android, Blackberry, Windows Mobile, Opera Mini, and even Internet Explorer 8 or earlier and Opera Browser.
11.10.2013
25
Requirements for Smart Phones

The optional smart phone apps for iOS require firmware 3.0 (or later). For Android devices, the app "PRTG for Android" requires Android OS 4.0 or later (version 4.1 or later recommended), as well as PRTG Network Monitor 13.1 or later. For more information, please see Smart Phone Apps 1801 . The 'Mobile Web GUI 1797 ' interface can be used on most phones with a browser. We successfully tested it on Symbian, Blackberry, Windows, Android, and iOS devices.
More
Updat e From Previous Versions
43
Paessler 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://www.paessler.com/knowledgebase/en/topic/41373 Knowledge Base: How can I speed up PRTGespecially for large installations? http://www.paessler.com/knowledgebase/en/topic/2733 Knowledge Base: My WMI sensors don't work. What can I do? http://www.paessler.com/knowledgebase/en/topic/1043 Knowledge Base: Frequent Questions about xFlow, Packet Sniffing, Traffic Monitoring and Cisco http://www.paessler.com/knowledgebase/en/topic/3733 Knowledge Base: My SNMP sensors don't work. What can I do? http://www.paessler.com/knowledgebase/en/topic/46863 Knowledge Base: Checklist for Running PRTG on VMware http://www.paessler.com/knowledgebase/en/topic/49193
26
11.10.2013
Part 2
Quick Start Guide
27.11.2012
27
Part 2: Quick Start Guide |
Quick Start Guide

Welcome to PRTG Network Monitor! This section will support you with a quick start into PRTG, so you can start monitoring your network right away!
Welc ome Sc reen
Setting up monitoring for your network is easy! Please see the following quick steps.
Quick Start GuideTopics

ONEDownload, Inst allat ion, and First Login TWOUsing t he Configurat ion Guru
32 29
28
27.11.2012
Part 2: Quick Start Guide | 1 ONEDownload, Installation, and First Login
2.1
ONEDownload, Installation, and First Login

Simply download and install your version of PRTG. For video tutorials with PRTG basics, please see section More 31 below.
Download
On the Paessler website, you find two different installers for PRTG, a public download for the Freeware, Special, and Trial editions, and another download for the commercial editions (which is only available for paying customers).
PRTG Download at Paessler Website
03.05.2013
29
Downloading the Freeware, Special, or Trial Edition

Please download the latest publicly available file from the Paessler website. You can also request a trial key there, which must be entered during installation: ht t p://www.paessler.com/prt g/download Note: Every Freeware installation will start as a Trial version, giving you an unlimited number of sensors for 30 days. After the trial period has expired, your installation will automatically revert to a Freeware edition with 10 sensors. Note: A Special Edition is an extended Freeware version. If you meet certain requirements you can receive a Special Edition key from us which gives you an extended number of sensors for free. For details, please see: http://www.paessler.com/prtg/download#30sensors
Downloading the Commercial Edition

Downloads and updates are free to customers with an active maintenance contract. Please log into the Paessler website to get the latest download. You can also find your license key there, which must be entered during installation: ht t p://www.paessler.com/login If you do not have an active maintenance contract, please contact sales@paessler.com. Note: Once installed, you will usually use the Soft ware Aut o-Updat e 1732 function of PRTG to download and install new versions. This will further ease the process of installing updates.
Installation
Please double click the setup file on the computer that will be your PRTG server. Follow the installation wizard and install the software. At the end of the installation, a browser window will be opened automatically, and it will connect to the PRTG web interface, showing the Configurat ion Guru. Please make sure you load the web interface with one of the compatible browsers Google Chrome 27 or later (recommended), Mozilla Firefox 21 or later, or Microsoft Internet Explorer 9 or 10.
30
03.05.2013
Note: Due to scripting incompatibilities, you cannot use the PRTG Ajax web interface with Internet Explorer 8 or earlier and Opera Browser. If you cannot access the Configurat ion Guru, please open the URL of the PRTG web interface in another browser.
Login
If everything works fine, you will not see the login screen on first startup. Only when switching browsers you will have to log in.
PRTG Login Sc reen
Leave the Login Name and Password fields empty. Choose the AJAX Web GUI (All feat ures, opt imized for deskt op access) option. Click on the Default Login button to login. Please make sure you use a supported web browser when logging in to PRTG. Please use Google Chrome 27 or later (recommended) or Mozilla Firefox 21 or later. Only with a supported browser you can use the AJAX Web GUI (All feat ures, opt imized for deskt op access) option. If you see this option grayed out (for example, with Internet Explorer 8 or earlier and Opera Browser), please change your browser and open the URL again. Please see the next step for more information about Using t he Configurat ion Guru
32 .
More
Video Tutorials for PRTG Network Monitor: http://www.paessler.com/support/video_tutorials
03.05.2013
31
Part 2: Quick Start Guide | 2 TWOUsing the Configuration Guru
2.2
TWOUsing the Configuration Guru

For a new inst allat ion, t he Configurat ion Guru will be shown aut omat ically aft er each login. It will reappear unt il y ou eit her ran t hrough it complet ely , or skipped it . In order t o open it at any t ime, please click t he Run Configurat ion Guru but t on on t he Home screen. Note: When using the Ent erprise Console Configurat ion Guru from the main menu.
1744
, please start the Guru by selecting Help | Run
Ajax Web GUI Welc ome Sc reen
By answering about ten simple questions, this assistant will guide you through an initial setup and pre-configure an essential monitoring of your network including important devices, servers, and websites. You can later edit this automatically created monitoring.
32
03.05.2013
Configuration Guru Start Sc reen
The steps to go are: Enable SSL Encry pt ion

34 34
Configure Administ rat or Account Ent er Windows/WMI Credent ials Ent er SNMP Credent ials
35 34
Ent er VMware/X enServer Credent ials
35 36
Ent er Linux/Solaris/Mac OS Credent ials Monit or Your Int ernet Connect ion Monit or LAN Servers
36 37 36
Monit or Websit es/Online Shops Monit or Cloud Services

37 37
Discover a Net work Segment You Are Done!

38
Click on the St art Guru button to start. You can skip a step at any time by clicking on the Skip button.
03.05.2013
33
Enable SSL Encryption

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

By default, PRTG uses the administrator account with login name prt gadmin and password prt gadmin. For security reasons you should at least change the password. Please enter credentials and email address for the administrator account. Click the Save & Next button to apply your settings, or click the Skip button to skip this step. Both buttons will take you to the next step.
Enter Windows/WMI Credentials

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

In order to monitor your hardware (router, switches, etc.), Simple Network Management Protocol (SNMP) is the most common protocol used. Usually, all SNMP-enabled devices use the same settings by default: SNMP version 1, community string public, SNMP port 161). You only need to change values here if the SNMP-enabled devices in your network use other settings. Choose between: No : You SNMP-enabled devices use the default configuration. If you're not sure, choose this option. Yes: Choose this option to enter your own SNMP credentials and settings. More settings will appear. Choose the SNMP version, enter the community string and SNMP port number, and define a time out for SNMP connections.
PRTG will store these credentials in the Root 213 group of your device tree. All SNMP-based devices will automatically inherit and use them for monitoring. You can discontinue Inherit ance of Set t ings 82 at any level, entering other credentials instead. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section. Click the Save & Next button to apply your settings, or click the Skip button to skip this step. Both buttons will take you to the next step.
Enter VMware/XenServer Credentials

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

If you have systems running on Linux, Solaris, or Mac OS X, PRTG can monitor them as well. To do so, please enter root access credentials for those systems. Choose between: No : PRTG will not monitor devices via SSH/WBEM. You can later add those credentials. Yes: Please enter SSH/WBEM credentials. You can either provide username and password, or paste a private key. For WBEM access, please also define protocol and port.
PRTG will store these credentials in the Root 213 group of your device tree. All SSH/WBEMbased devices will automatically inherit and use them for monitoring. You can discontinue Inherit ance of Set t ings 82 at any level, entering other credentials instead. For a general introduction to SSH monitoring, please see Monit oring via SSH
1816
section.
Monitor Your Internet Connection

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

PRTG can monitor your AD domain controllers, Exchange or other mail servers as well as additional servers in your network. PRTG will try to automatically detect and pre-populate the respective fields with the correct IP addresses. Please review and/or enter the entries for your Active Directory domain controllers and mail servers. Enter each IP address/DNS name in one line. PRTG will create a new device for each entry and run an auto-discovery to set up sensors. In the background, auto-discovery will start immediately after you confirm this step.
36
03.05.2013
Monitor Websites/Online Shops

PRTG can monitor your website and online shop using http. Simply enter the URLs you want to monitor, each in one line. PRTG will create a new device for all of your websites, with one sensor for each URL. Click the Save & Next button to apply your settings, or click the Skip button to skip this step. Both buttons will take you to the next step.
Monitor Cloud Services

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

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

While you were busy using the guru, PRTG has already created devices and sensors for you. There are first monitoring values available, too. Click on the OK! Let me view my new sensors! button to view the device tree. In order to get familiar with the PRTG web interface, we recommend you proceed with section General Lay out 102 of the web interface, or with General Lay out 1747 of the Enterprise Console.
38
03.05.2013
Part 3
Installing the Software
27.11.2012
39
Part 3: Installing the Software |
Installing the Software

This section describes how to download and install your PRTG product.
PRTG Setup
Please see the following sections for more information.
Installing the SoftwareTopics

Download PRTG
41 43
Updat e From Previous Versions Inst all a PRTG Core Server Inst all a PRTG Clust er Ent er a License Key
53 56 58 52 47
Act ivat e t he Product
Inst all a PRTG Remot e Probe
Inst all t he Ent erprise Console Uninst all PRTG Product s

67
63
40
27.11.2012
Part 3: Installing the Software | 1 Download PRTG
3.1
Download PRTG
On the Paessler website, you find two different installers for PRTG, a public download for the Freeware, Special, and Trial editions, and another download for the commercial editions (which is only available for paying customers).
PRTG Download at Paessler Website
Downloading the Freeware, Special, or Trial Edition

Please download the latest publicly available file from the Paessler website. You can also request a trial key there, which must be entered during installation: ht t p://www.paessler.com/prt g/download
27.11.2012
41
Part 3: Installing the Software | 1 Download PRTG
Note: Every Freeware installation will start as a Trial version, giving you an unlimited number of sensors for 30 days. After the trial period has expired, your installation will automatically revert to a Freeware edition with 10 sensors. Note: A Special Edition is an extended Freeware version. If you meet certain requirements you can receive a Special Edition key from us which gives you an extended number of sensors for free. For details, please see: http://www.paessler.com/prtg/download#30sensors
Downloading the Commercial Edition

Downloads and updates are free to customers with an active maintenance contract. Please log into the Paessler website to get the latest download. You can also find your license key there, which must be entered during installation: ht t p://www.paessler.com/login If you do not have an active maintenance contract, please contact sales@paessler.com. Note: Once installed, you will usually use the Soft ware Aut o-Updat e 1732 function of PRTG to download and install new versions. This will further ease the process of installing updates.
42
27.11.2012
Part 3: Installing the Software | 2 Update From Previous Versions
3.2
Update From Previous Versions

If you already have installed a previous software version, there are several things you should consider before updating to PRTG version 13. 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 45 section below.
Update From PRTG Network Monitor 12 or 13

If you have been running PRTG Network monitor with version 12 or 13, simply install 47 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.
Web Interface Customizations as of PRTG Network Monitor 13.2.3

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

If you are using PRTG 9 now, your configuration will be kept when installing PRTG 13 in St andalone Mode or when installing a Mast er Node. There are only a few things you should consider. Discont inued Sensors: Existing instances of the following sensor types will stop working as of PRTG V12 and must be replaced with their successor sensor types! - VMware Host Server (SOAP) - VMware Virt ual Machine (SOAP) - X en Virt ual Machine If your configuration contains these sensor types, they will stop monitoring after upgrading to version 13. We recommend you pause them to keep their . In order to continue monitoring, please add the sensors anew (e.g. using the auto-discovery). Please inst all .NET 4.0: We strongly recommend installing .NET 4.0 on systems that run the core server (and the remote probes, if you use those). Otherwise the following features will not work: VMware 284 auto-discovery and monitoring, Citrix XenServer 328 auto-discovery and monitoring, SIP Options Ping Sensor 850 , Windows Last Update Sensor 1322 . Changed Geo Maps Provider: When you update to PRTG 13 the provider for geographical maps will automatically be switched from Google Maps to MapQuest (using Open Street Map data).
13.06.2013
43
Windows 2000 Not Support ed: Since PRTG 7 we do not officially support Windows 2000 systems any more. This means, PRTG cannot be installed on systems running Windows 2000, and you cannot officially monitor Windows 2000 systems (for example, via WMI). However, if you could successfully monitor your Windows 2000 systems with PRTG 9, this might actually not be possible any more with PRTG 13. Especially the WMI Service Sensor 1504 will show an error message when monitoring Windows 2000 systems under PRTG 13. For a work around, please see More 45 section below.
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 13 in St andalone Mode or when installing a Mast er Node. There are only a few things you should consider. Note: If you're running PRTG 7 or 8 we recommend you first update to the latest PRTG 8 version as an intermediate step, in order to make sure all data is carried over correctly. Please contact technical support 1926 to obtain a download link for PRTG 8. In any case we recommend you always keep a proper backup of your configuration and monitoring data. Updat ing from PRTG 7 or 8 t o PRTG 13 Packet Sniffer (Content) sensors are not supported any more. Existing sensors of this type will automatically be switched to Packet Sniffer (Header) sensors after the update. As a benefit, you can now also sniff IPv6 traffic. Internet Explorer 8 is no longer supported for access to the PRTG Ajax web interface or to the mobile web GUI. You may experience a slow Enterprise Console 1744 (former 'Windows GUI') due to different reasons. For detailed information, please see the knowledge base article linked in the More 45 section below. When installing a failover node on top of an existing stand-alone PRTG 7, 8, 9, 12, or 13 installation, the configuration cannot be kept and is written to a backup folder. Then, the new cluster configuration is received from the master node of the cluster. As all nodes work with the same configuration, a failover node's old configuration and monitoring data can no longer be used. If you want to keep a configuration of PRTG 7, please install the master node on top of the old installation and use other servers for the failover node installations. Since PRTG 9 the SNMP sensors use the IPv4 Out going IP set for the probe service (this setting was formerly ignored by those sensors, using the aut o setting instead). If you experience failing sensors, please check the setting in the PRTG Probe Administrator 1859 . For detailed information please see More 45 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 13. For detailed information please see More 45 section below.
44
13.06.2013
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. Updat ing from PRTG 7 t o PRTG 13 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 13 if they do not fully apply to the API definition 1871 .
Update From Older PRTG Products

For all other predecessor products, a direct data import into the current version is not possible. If you have been using IPCheck 5 or PRTG Traffic Grapher 6, please perform a clean installation of PRTG 13 and set up your configuration anew. Using PRTG's Aut o-Discovery 181 is the easiest way to quickly configure a monitoring of your entire network. Please see Quick St art 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: What about my web interface customizations as of PRTG 13.2.3? http://www.paessler.com/knowledgebase/en/topic/44703 Knowledge Base: How can I monitor a Windows service on Windows 2000? http://www.paessler.com/knowledgebase/en/topic/36483 Knowledge Base: Why is the Enterprise Console so slow? http://www.paessler.com/knowledgebase/en/topic/25413
13.06.2013
45
Knowledge Base: Some of my SNMP sensors do not work after updating from PRTG 8 to PRTG 9 or later 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 or later 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 the current PRTG version? 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
46
13.06.2013
Part 3: Installing the Software | 3 Install a PRTG Core Server
3.3
Install a PRTG Core Server

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

Only if you entered incorrect license information before you will be asked to enter a correct license name and key.
Welc ome Wizard Enter Lic ense Information
Please enter both Name and Key exactly as stated in the email received from Paessler. We recommend using copy&paste to avoid typing mistakes. For details, please see Ent er a License Key 53 .
More
Knowledge Base: What is the PRTG Special 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
27.11.2012
51
Part 3: Installing the Software | 4 Install a PRTG Cluster
3.4
Install a PRTG Cluster

PRTG offers single failover clustering in all licenseseven using the freeware edition. A single failover cluster consists of two servers ("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. You can run a cluster with up to 5 nodes.
Illustration of a Single Failov er Cluster
For detailed information, please see Failover Clust er Configurat ion
1902
More
Knowledge Base: What's the Clustering Feature in PRTG? http://www.paessler.com/knowledgebase/en/topic/6403
52
27.11.2012
Part 3: Installing the Software | 5 Enter a License Key
3.5
Enter a License Key

A license key for PRTG Network Monitor consists of the license name and a license key. The key is a string consisting of approx. 70 characters.
Your Personal License Information

You should have received license name and key via email. This is either the information for a Trial or a Commercial Edition.
Example of License Informat ion License Name: John Q. Public License Key: 0223515-FFSEJC-ZHGRDFM-UR1CS8-U73FGK-G645F2-YVF1DD-H8323ND11HG9-M2DRG
During the setup process you will be asked to enter your license information. Please use copy&paste to fill out the form in the dialog shown by the installer. Trial/Freeware license key : When entering a Trial license key you can experience unlimited functionality of PRTG during the trial period. Your installation will automatically switch to a Freeware Edition afterwards. In details how to get your free Trial installer, please see Download PRTG 41 section. Commercial license key : This key can only be entered if you install the Commercial Edition of PRTG, available for download in the customer service center. See Download PRTG 42 section for details. Your installation will allow the number of sensors according to your license.
Change License Key

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

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

Please start the PRTG Server Administ rat or program from the Windows Start Menu. In the program, select the License tab.
Start M enu Ic on
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.
54
27.11.2012
PRTG Serv er Administrator Lic ense 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 Edit ion field you will see an accepted license key. Click on the Ok button to save and confirm to restart the core server service by clicking on the Yes button.
PRTG Serv er Administrator Confirm Serv ic e Restart
27.11.2012
55
Part 3: Installing the Software | 6 Activate the Product
3.6
Activate the Product

PRTG tries to activate your license automatically via the internet on first start up. Only if PRTG cannot connect to the internet directly, the web interface will display a Soft ware Act ivat ion Required notice.
Software Ac tiv ation 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 96 to activate.
Activate via Internet

In the PRTG web interface, choose Set up | PRTG St at us | Act ivat ion St at us from the main menu.
Lic ense Ac tiv ation Status
Click on the button St art Act ivat ion Now to start product activation. PRTG will now connect with the Paessler license server to check your license (via SSL on port 443). A few seconds later you should see Act ivat ion OK in the License Activation Status. Note: The PRTG core server needs an internet connection on port 443 to activate. If a proxy connection is needed, please configure it in the Sy st em Administ rat ionSy st em and Websit e 1698 settings. Please see More 57 section for details about activation servers. In case activation fails, you can activate via email.
Activate via Email

In the PRTG Web Interface, choose Set up | PRTG St at us | Act ivat ion St at us from the main menu. If there is no internet connection available, you can activate PRTG via email. To do so, first click on the St art Act ivat ion Now button. You will then see Last message about act ivat ion: Act ivat ion failed in the License Activation Status.
56
07.02.2013
Part 3: Installing the Software | 6 Activate the Product
Once the activation via internet fails, the activation via email is available. Click on the St art Act ivat ion per EMail tab. You will see an Act ivat ion Request Code. Copy it and send it to the email address shown. Within two business days you will receive an email reply from Paessler, containing an activation code. Once you've received this email, go the Finalize Act ivat ion per EMail tab and copy the activation code into the according field. Note: Please make sure you only copy the code itself and nothing else from the email. Also, please omit the "Activation Code Start/End" markers. Click on Confirm Act ivat ion. A few seconds later you should see Act ivat ion OK in the License Activation Status.
More
Knowledge Base: Which servers does PRTG connect to for Software Auto-Update and for Activation? http://www.paessler.com/knowledgebase/en/topic/32513
07.02.2013
57
Part 3: Installing the Software | 7 Install a PRTG Remote Probe
3.7
Install a PRTG Remote Probe

The local probe is already included in a PRTG core server installation 47 . 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 96 . On the login screen 96 , enter login name and password and from the main menu, select Set up | Downloads | Remot e Probe Inst aller. Click on the Download: Remot e Probe Inst aller 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.
58
27.11.2012
Remote Probe Setup Wizard Welc ome Sc reen
After accepting the license agreement, you can choose the folder you wish to install the software in. We recommend using the default value.
27.11.2012
59
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 Remot e Probe Set up 1896 section for more information. Click Ok to continue.
60
27.11.2012
Probe Settings in PRTG Probe Administrator
When asked if you want to start the probe service, confirm with Yes. The installation is completed.
PRTG Probe Administrator Start Serv ic e Request
After installation, click Finish.
27.11.2012
61
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 Remot e Probe Set up 1896 for more information on how to connect the remote probe with your PRTG core server installation.
62
27.11.2012
Part 3: Installing the Software | 8 Install the Enterprise Console
3.8
Install the Enterprise Console

The Enterprise Console is already included in a PRTG core server installation additional Enterprise Consoles on other computers.
47 .
You can install
Download Enterprise Console from the Web Interface

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

Please execute the setup program you just have downloaded.
03.05.2013
63
Windows GUI Setup Wizard Welc ome Sc reen
After accepting the license agreement, you can choose the folder you wish to install the software in. We recommend using the default value.
64
03.05.2013
Select which icons will be created. We recommend using the default value.
Windows GUI Setup Wizard Additional Tasks
03.05.2013
65
Windows GUI Setup Wizard Install
After installation, click Finish to start the Enterprise Console.
Windows GUI Setup Wizard Finish
More
Please see section Ent erprise Console User Interface (GUI).
1744
for more information on how to use this Graphical
66
03.05.2013
Part 3: Installing the Software | 9 Uninstall PRTG Products
3.9
Uninstall PRTG Products

The uninstall process has six stepsregardless of if you are uninstalling an entire PRTG Network Monitor installation, a single 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 Uninst all PRTG Net work Monit or icon, the Uninst all PRTG Ent erprise Console icon, or the Uninst all PRTG Remot e Probe icon, or open your Windows Control Panel and choose the respective entry in the Programs section. Depending on the installed products, not all uninstall programs are available.
Start Menu Ic ons
Step 2
If asked, confirm the question of the Windows User Account Control with Yes to allow the program to uninstall. The usual software uninstall wizard will guide you through the uninstall process.
Windows User Ac c ount Control Request
Step 3
Confirm the removal of the software by clicking the Yes button.
03.05.2013
67
Uninstall PRTG Network Monitor Step 1
Step 4
Wait while the software is being removed.
Step 5
Confirm a system restart by clicking the Yes button.
68
03.05.2013
Step 6
After system restart, the software is removed. However, there are still custom data in the PRTG program folder left. If you have uninstalled an entire PRTG Network Monitor installation or a remote probe installation, your monitoring data is still stored on the system. To completely remove all PRTG data, please delete the PRTG Net work Monit or program folder as well as the Paessler\PRTG Net work Monit or folder in your data path. For more information where data is stored see Dat a St orage 1912 section.
More
Knowledge Base: Can we remotely and silently Uninstall a Remote Probe? http://www.paessler.com/knowledgebase/en/topic/27383
03.05.2013
69
Part 4
Understanding Basic Concepts
27.11.2012
71
Part 4: Understanding Basic Concepts |
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 ConceptsTopics

Archit ect ure and User Int erfaces Clust ering
76 78 82 73
Object Hierarchy
Inherit ance of Set t ings Tags

84 85
Dependencies Scheduling Not ify ing

86
87 88 89
Dat a Report ing
User Access Right s IPv6

92
72
27.11.2012
Part 4: Understanding Basic Concepts | 1 Architecture and User Interfaces
4.1
Architecture and User Interfaces

PRTG Network Monitor consists of different parts which can be divided into three main categories: System parts, control interfaces and basic administration interfaces.
Ty pe System Parts
Part of PRTG Core Server 74 This is the central part of a PRTG installation and includes data storage, web server, report engine, a notification system, and more. Probe(s) 74 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.
User Interfaces
Ajax Web Int erface 94 The Ajax-based web interface is used for configuration of devices and sensors, as well as the review of monitoring results. Also system administration and user management are configured here. Ent erprise Console 1744 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! Mobile Web GUI 1797 A read-only interface optimized for mobile access to your PRTG installation. View latest states, tables, and graphs. Using jQuery Mobile, this interface is compatible with almost all mobile devices available on the market. Smart Phone Apps 1801 Monitor your network on the go with PRTG and the smart phone apps for iOS and Android. PRTG Server Administ rat or 1837 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 Administ rat or 1857 Used to configure basic probe settings such as name of the probe, IP and server connection settings, and more.
System Administration Programs
07.02.2013
73
Core Server
The core server is the heart of your PRTG system and performs the following processes: Configuration management for object monitoring Management and configuration of the connected probes Cluster management Database for monitoring results Notification management including a mail server for email delivery Report generator and scheduler User account management Data purging (culling data that is older than 365 days, for example) Web server and API server In a cluster, 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 Serv er and Loc al Probe Monitoring a Loc al Area Network
74
07.02.2013
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 installationwhich is the default setupall 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 76 , a cluster probe runs on all nodes. There is an additional so-called Clust er Probe. All devices created on it are monitored by all nodes in the cluster, so data from different perspectives is available and monitoring for these devices always continues, also if one of the nodes fails. PRTG automatically monitors system health of its own core server and of each probe 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 Healt h, Clust er Probe Healt h, Disk Free, and a bandwidth sensor for all installed network cards. We recommend keeping these sensors, but you can optionally remove all except the Healt h sensors. They measure various internal system parameters of the probe system hardware and the probe's internal processes and then computes a resulting value. Frequent or repeated values below 100% should be investigated. Please check the sensor's channels 118 for details. Additional so-called Remot e Probes can be created by the user in order to achieve monitoring of multiple locations, or for several other scenarios. They are using SSL-secured connections to the core and allow to securely monitor services and systems inside remote networks which are not openly accessible, or secured by firewalls. For more information please see Remot e Probes and Mult iple Probes 1887 section. For a video on this please see More 192 section below.
More
Video Tutorial: There is a video available on the Paessler video tutorials page. http://www.paessler.com/support/video_tutorials
07.02.2013
75
Part 4: Understanding Basic Concepts | 2 Clustering
4.2
Clustering
A PRTG Cluster consists of two or more installations of PRTG 47 that work together to form a high availability monitoring system. The objective is to reach true 100% uptime for the monitoring tool. Using clustering 1902 , the uptime will no longer be degraded by failing connections because of an internet outage at a PRTG server's location, failing hardware, or because of downtime due to a software update for the operating system or PRTG itself.
How a PRTG Cluster Works

A PRTG cluster consists of one Primary Mast er Node and one or more Failover Nodes. Each node is simply a full installation of PRTG which could perform the whole monitoring and alerting on its own. Nodes are connected to each other using two TCP/IP connections. They communicate in both directions and a single node only needs to connect to one other node to integrate into the cluster. During normal operation the Primary Mast er is used to configure devices and sensors (using the web interface 94 or Windows GUI 1744 ). 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. By default, all devices created on the Clust er Probe are monitored by all nodes in the cluster, so data from different perspective is available and monitoring for these devices always continues, also if one of the nodes fails. In case the Primary Mast er fails, one of the Failover Nodes takes over the master role and controls the cluster until the master node is back. This ensures a fail-safe monitoring with gapless data. Note: During the outage of a node, it will not be able to collect monitoring data. The data of this single node will show gaps. However, monitoring data for this time span is still available on the other node(s). There is no functionality to actually fill in other nodes' data into those gaps. If downtimes or threshold breaches are discovered by one or more nodes only one installation, either the Primary Master or the Failover Master, will send out notifications (via email, SMS text message, etc.). So, the administrator will not be flooded with notifications from all cluster nodes in the event of failures.
Set Up a PRTG Cluster

For detailed information, please see Failover Clust er Configurat ion
1902
More
Knowledge Base: What's the Clustering Feature in PRTG? http://www.paessler.com/knowledgebase/en/topic/6403
76
27.11.2012
Part 4: Understanding Basic Concepts | 2 Clustering
27.11.2012
77
Part 4: Understanding Basic Concepts | 3 Object Hierarchy
4.3
Object Hierarchy
All objects in a PRTG monitoring configuration are arranged in a tree-like hierarchy to create an easy to navigate list and to give the user the possibility to arrange them in groups that monitor similar devices, services, or same locations. The hierarchical order described is also used to define common settings for larger groups of objects, for example settings of the Root group apply by default to all other objects below it (see section Inherit ance of Set t ings 82 ).
Objec t Hiearc hy in PRTG
Root Group
The Root group is the topmost instance in PRTG. It contains all other objects in your setup. Using the inheritance 82 mechanism, we recommend adjusting the default settings for the Root group 213 in order for all other objects to inherit them. This makes configuration easier later on.
78
19.07.2013
Probe
Each group (except the Root group) is part of a Probe. This is the platform on which the monitoring takes place. All objects configured below a probe will be monitored via that probe. Every PRTG core installation automatically installs a Local Probe service. You can add additional probes and remote probes to your configuration to include remote devices from outside your network into the monitoring (see section Mult iple Probes and Remot e Probes 1887 ). In a cluster, there is an additional Clust er Probe running on all nodes. Devices on the cluster probe are monitored by all nodes of the cluster, so data from 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.
PRTG Dev ic e Tree View
Device
To each probe or group, you can add Devices that you want to monitor. Each device in your PRTG configuration represents a real hardware or virtual device in your network. These can be, for example: Web or file server
19.07.2013
79
Client computer (Windows, Linux, or Mac OS) Router or network switch Almost every device in your network that has its own IP address Note: Sometimes you may want to add the same device in PRTG several times, in order to get a better overview when using many sensors for a very detailed monitoring, or to use different device settings for different groups of sensors. In PRTG you can simply add multiple devices with the same IP address or DNS name. The sensors on all of these PRTG devices will then query the same real hardware device in your network. PRTG additionally adds a so called Probe Device to the local probe. This is an internal system device. It has access to the computer on which the probe is running on and monitors its health parameters with several sensors running on it.
Sensor
On each device you can create a number of Sensors. Every sensor monitors one single aspect of a device. This can be, for example: One network service like SMTP, FTP, HTTP, etc. One network switch port's traffic CPU load of a device Memory load of a device Traffic on one network card One NetFlow device System health of a device Other content (for example, of databases, mails, HTTP, XML, files, etc.) etc.
Channel
Every sensor has a number of Channels through which it receives the different data streams. The available channels depend on the type of sensor. One sensor channel can contain, for example: Downt ime 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 t raffic of a NetFlow device Mail t raffic of a NetFlow device
80
19.07.2013
Ot her t raffic of a NetFlow device CPU Load of a device Loading t ime of a web page Download Bandwidt h of a web page Time t o first by t e of a web page Response t ime of a Ping request to a device Response t ime of a Remote Desktop service etc.
19.07.2013
81
Part 4: Understanding Basic Concepts | 4 Inheritance of Settings
4.4
Inheritance of Settings
The hierarchical tree 78 is not only used to group sensors for organizational reasons, there is also an important aspect involved that we call inheritance. To ensure administration is quick and easyespecially for large monitoring setupscertain settings are inherited from the overlying level. For example, you can change the monitoring interval for all sensors by editing the interval setting of the topmost Root group (unless no other setting is defined below).
Settings are Inherited to Child Objects

You can override this inheritance on any level of the hierarchy by setting a different value for a specific probe, group, device, or sensor. All objects below will inherit these new settings; 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
84
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 X y z. As an example, the screenshot below shows Windows systems credentials settings after removing the check mark symbol.
Credentials for Windows Sy stems
82
19.07.2013
Part 4: Understanding Basic Concepts | 4 Inheritance of Settings
Default Values Set in Root Group

For all settings (except passwords) PRTG already includes a set of default values so you can get started with the software immediately. For example, the following settings will be inherited by all sensors from the Root group: Default monitoring interval of one minute SNMP version 1 with community string set to public (default values for most devices) Dependency type Use parent etc. You may need to change some of the default entries as you become used to the interface. However, these settings 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 Set t ings
213
for more details.
Inheritance of Notification Triggers

If you add notification triggers on probe, group, or devices level, these will also be inherited to all sensors underneath, unless you interrupt inheritance. See section Sensor Not ificat ions Set t ings
1573
for details.
19.07.2013
83
Part 4: Understanding Basic Concepts | 5 Tags
4.5
Tags
For every object in your PRTG setup, you cannot only name objects, but also define tags in an object's settings 133 to additionally mark an object as a member of certain categories. Although there are tags predefined when adding objects 193 you are totally free in the way you add tags. For example, you can mark all of the bandwidth sensors which 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 1636 . A clever arrangement of tags can save you a lot of time at some point. Note: You can change tags for several objects at a time using the multi-edit 1595 function.
Tags Are Inherited

The tags in an object's settings are automatically inherited 82 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 1636 settings. This way, to configure your setup for fetching all sensors on a device by tag, you do not have to tag every single sensor, but it is enough to tag the device. Inheritance for tags cannot be disabled.
84
19.07.2013
Part 4: Understanding Basic Concepts | 6 Dependencies
4.6
Dependencies
Using dependencies you can pause sensor monitoring based on the status of another sensor in order to avoid false alarms and incorrect downtime recording. A dependency stops the monitoring of one sensor or a set of sensors as soon as a specific sensor is not in an Up status. This means, for example, you can stop monitoring remote network services when the corresponding firewall is down due to connection problems. When using the auto-discovery 181 function, the Ping sensor on a device is by default set as the master object for this device. This means that monitoring for the entire device is paused if the Ping sensor is in a Down status. Usually, it does not make sense to monitor other aspects of a device with other sensors, while the Ping sensor indicates that the device is not even reachable. In order to view a list of all dependencies or only selected dependencies, choose Devices | Dependencies from the main menu 166 . For more information about the dependency settings, please see the settings of the respective object 133 you want to set a dependency for.
19.07.2013
85
Part 4: Understanding Basic Concepts | 7 Scheduling
4.7
Scheduling
Using schedules, monitoring of an object can be paused 147 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 87 . With schedules you can limit the monitoring time automatically. You can also pause monitoring for planned system maintenance time spans to avoid false alarms. You can apply different schedules to every object. They are also used for reports and notifications. Schedules are user account specific. To change the default pre-defined schedules or to add your own schedule, please see Account Set t ingsSchedules 1687 section. Note: If you use failover clustering with nodes in different timezones, scheduling applies at the local time of each node. For more information, please see section Failover Clust er Configurat ionBefore Get t ing St art ed 1902 .
86
08.10.2013
Part 4: Understanding Basic Concepts | 8 Notifying
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 Not ificat ions 1609 section for more details.
Limits
In a sensor channel's settings 1566 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 (Part ial), 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 135 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 137 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 139 section for more information.
27.11.2012
87
Part 4: Understanding Basic Concepts | 9 Data Reporting
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 Hist oric Dat a Report s 126 section for more information.
Generate Reports
You can use the sophisticated reports machine included in PRTG to create exhaustive reports for all monitoring data. See Report s 1636 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 t he PRTG API (Applicat ion Programming Int erface) 1871 section for more information.
Making Data Available

You can make monitoring data available to others using a special read only user (see User Access Right s 89 section), or you can create public or semi-public HTML pages with monitoring data using the Maps feature. See Maps 1655 section for more information.
Bill Customers
You can also create custom billing reports based on PRTG's monitoring data, using the open source Billing Tool for PRTG. For details and download, please see More 88 section below.
More
Dat a St orage
1912
Paessler Website: Billing Tool http://www.paessler.com/tools/billingtool
88
13.06.2013
Part 4: Understanding Basic Concepts | 10 User Access Rights
4.10
User Access Rights

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

The following classes of access rights for objects are available in hierarchical order as they can be given to user groups (lowest rights to highest rights): None: The object will not be displayed to the users of the group; no logs, no ToDos, no alarms regarding this object will appear. Read: Only monitoring results can be seen. Writ e: Reviewing monitoring results and editing settings is allowed. In addition, objects can be added to and deleted from the device tree. Full: Reviewing monitoring results, editing settings, and editing access rights is allowed. In addition, objects can be added to and deleted from the device tree. Admin right s: If a user group has administrator rights, all options are available, including creating users, creating user groups, and deleting objects from the device tree. Access restrictions to objects cannot be set for this type of user group.
08.10.2013
89
Note: Access rights that are defined locally on an object, for example, on a device, override inherited 82 rights. On a certain object, the highest directly set access right applies for a user group. If there is no access right set directly on an object, the next higher object level will be checked for access rights. This process is repeated until defined access rights are found to be inherited or there is no higher object level.
Different Ac c ess Rights for a Firewall in the Dev ic e Tree Depending on User Groups
Please see the table below which user rights apply when. Column headings show access rights of user groups for objects in the device tree; line headings show the type of user. Note: Users are either in PRTG user groups or in Active Directory Domain user groups. They cannot be in both. We recommend to use only one type of user group (either PRTG or Active Directory) to minimize your administration effort. PRTG User Group PRTG User Group Domain User Group Domain User Group Read Access Read/Writ e Access PRTG User Read Only Domain User Read Only Read-only rights Read-only rights PRTG User Group PRTG Sy st em Domain User Administ rat or Group Domain Administ rat or Full Access
Read-only rights
Admin rights
90
08.10.2013
PRTG User Read/ Read-only rights Writ e Domain User Read/Writ e
Read/write rights Full access
Admin rights
Users in an administ rat or group have always administrator access rights, no matter of the access rights of an object. Read-only users have just read rights, no matter of the access rights of their group, except for users which are members of an administrator group. Read/writ e users in a group with full access to an object have full access rights to this object only. If a user is in more than one group, access rights of the user group with the highest right s apply . Administrator rights can only be given via the administrator group. For more information about defining access rights, please see the following sections: Sy st em Administ rat ionUser Account s Sy st em Administ rat ionUser Groups
1715 1710
For information about connecting PRTG to an existing Active Directory, please see Act ive Direct ory Int egrat ion 1869 .
08.10.2013
91
Part 4: Understanding Basic Concepts | 11 IPv6
4.11
IPv6
PRTG supports the IPv6 protocol for most sensor types. You can define whether data from your network is queried via IPv4 or IPv6: For each device in PRTG you can select whether PRTG will connect to it using either IPv4 or IPv6. This is a simple selection in the Device Set t ings 261 of each device. Depending on the setting, the sensors created on this device will use the respective protocol. In the Out going IP Set t ings of the PRTG Probe Administ rat or 1859 you can additionally choose which IPv6 address will be used for outgoing monitoring requests. Note: There is the same option for IPv4, too.
92
27.11.2012
Part 5
Ajax Web InterfaceBasic Procedures
29.11.2012
93
Part 5: Ajax Web InterfaceBasic Procedures |
Ajax Web InterfaceBasic 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 96 , 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 1710 by the user). The following sections introduce the features and concepts of the Ajax Graphical User Interface (GUI).
94
29.11.2012
Part 5: Ajax Web InterfaceBasic Procedures |
Ajax Web InterfaceBasic ProceduresTopics

Login
96 99
SSL Cert ificat e Warning General Lay out Sensor St at es

102
115
Review Monit oring Dat a Compare Sensors

123
118
Hist oric Dat a Report s Similar Sensors

130
126
Object Set t ings Alarms Logs

137 135
133
ToDos
139
Working wit h Table List s Object Select or

143
141
Priorit y and Favorit es Pause

147
145
Cont ext Menus Hover Popup

164
148
Main Menu St ruct ure
165
Other Ajax Web Interface Sections

Ajax Web Int erfaceDevice and Sensor Set up Ajax Web Int erfaceAdvanced Procedures
1584
180
Related Topics
Ent erprise Console
1744
Ot her User Int erfaces
1796
29.11.2012
95
Part 5: Ajax Web InterfaceBasic Procedures | 1 Login
5.1
Login
Once the PRTG core server is installed 47 , 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 1837 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, swit ch t o SSL button shown on the welcome screen.
Loading the Web Interface

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

When logging in for the first time, login name and password for the default administrator login are both prt gadmin. You can leave the login name and password fields empty and click on the Default Login button to log in using these default credentials. Note: After login you should change the default password. To do so, go to Set up | Account Set t ings | My Account and specify a new password. 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 1850 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 Web GUI (All feat ures, opt imized for deskt op access): The standard interface. We recommend using it whenever possible. It offers full functionality. Use Google Chrome 27 or later (recommended) or Mozilla Firefox 21 or later for best performance. In some browsers, the Ajax option is not shown (e.g. not in Internet Explorer 8 or earlier and Opera Browser).
03.05.2013
97
Note: Although you can login using Microsoft Internet Explorer 9 or 10, this interface might not be fully compatible with Internet Explorer! When using Microsoft Internet Explorer 9 or 10, please set the security level at least to Default level Medium-high and make sure you do not use the Compat ibilit y View! For detailed information, please see More 98 section below. Mobile Web GUI (Limit ed funct ionalit y , opt imized for mobile access): The Mobile Web GUI 1797 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 Internet Explorer 8 or earlier and Opera Browser). Ent erprise Console & Mobile Apps (for Windows, iOS, Android): Option to download the native Windows interface to the desktop (former Windows GUI). It has to be installed 1744 on the client computer before use. The Enterprise Console 1744 provides full functionality; however, for some functions the Ajax Web GUI is opened. As an additional feature, the Enterprise Console can view data of several independent PRTG core installations in a single application. You can also access iTunes store or Android market here, in order to download the PRTG apps on your mobile device. Note: Also when using this download option, login name and password (or a Default Login) are required! Note: Only Google Chrome 27 or later (recommended) and Mozilla Firefox 21 or later are fully compatible with the Ajax Web GUI. For more information about Internet Explorer support, please see More 98 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 with Internet Explorer 9 or IE10? http://www.paessler.com/knowledgebase/en/topic/46893
98
03.05.2013
Part 5: Ajax Web InterfaceBasic Procedures | 2 SSL Certificate Warning
5.2
SSL Certificate Warning

If you use PRTG outside your internal LAN, especially when 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 98 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
99
99
100
Internet Explorer Other

101
Google Chrome
In Google Chrome, click on Proceed any way every time you call the web interface.
Sec urity Warning in Google Chrome Browser
Mozilla Firefox
In Mozilla Firefox, click on I Underst and t he Risks and then on the Add Except ion... button. In the appearing window, leave the check mark for Permanent ly st ore t his except ion and finally click on the Confirm Securit y Except ion button.
27.11.2012
99
Sec urity Warning in Mozilla Firefox
You only have to go through this procedure once for every Firefox browser and PRTG core server.
Internet Explorer
In Int ernet Explorer, click on Cont inue t o t his websit e (not recommended) every time you call the web interface.
Sec urity Warning in Internet Explorer
100
27.11.2012
Other
For other browsers, the procedures to confirm the certificate will be similar to the ones described above.
More
Using Your Own SSL Cert ificat e
1914
Knowledge Base: Why don't I get an SSL connection to the PRTG web interface? http://www.paessler.com/knowledgebase/en/topic/11813
27.11.2012
101
Part 5: Ajax Web InterfaceBasic Procedures | 3 General Layout
5.3
General Layout
Once you've run through the Configurat ion Guru 32 you will see PRTG's welcome page as default after you log in to the web interface. This page helps you to re-run the configuration guru, add sensors manually, perform an automatic network search, review results, download the Enterprise Console or smart phone applications, and get further help and support.
Welc ome Sc reen
Tree View Layout

Click on the Review Result s option to display the tree-like device view which will be a starting point for everyday use.
102
07.02.2013
PRTG Dev ic e Tree
From top to bottom, the main layout consists of:
07.02.2013
103
Screen Number
Part
Descript ion
Global Header Area 105
This element contains the main menu at the top, the global status bar, and a quick search box.
Page Header Bar

107
This element contains the page heading with the name of the current object, the tabs bar which leads to the content of the current object, and the object's status bar.
Device Tree View 109
This selection is part of the page header bar. Using the provided options you can define how your device tree is displayed.
Page Content
113
This element contains 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 107 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). 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.
104
07.02.2013
Global Header Area
PRTG's Cluster Info, Main Menu, Breadc umbs, 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 Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default. The global header area consists of the following parts:
07.02.2013
105
Screen Number
Part
Descript ion
Gray 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 Clust er St at us 1735 . 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.
Blue Main Menu Bar
Navigating through the web interface is performed using the main menu. Please take a few minutes to familiarize yourself with all menu items and sub-items. A detailed description can be found in the Main Menu St ruct ure 165 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. If you click on a 'breadcrumb' item to open a drop-down menu showing all available object on the same level. Enter a view letters to search for a name, or select an object directly. For example, you can use this to directly access all other sensors or a device, the other devices within a group, another group on the same probe, or other probes in your root group.
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 returnedeven displaying online help articles.
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 These buttons show the number of new alarms or new log Alarms, New Log entries since last user login as well as the number of ToDo(s) Entries, ToDo(s) that wait to be acknowledged (only if there are any; in the example screenshot there are only new ToDo(s)). Click on the respective button to view the Alarms 135 , Logs 137 , or ToDos 139 .
07.02.2013
106
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
Page Header Bar

In the page header under the global header area, you see the name of the current object and the page content underneath. When displaying a group, aggregated sensor states are shown in a sensor bar and there is an option to change the tree view. Furthermore, various information about the current object is reported here. Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default.
PRTG Page Header Bar with Heading, Tabs, Group Status Ic ons, and Dev ic e Tree View Selec tion
The page header and tabs area consists of the following parts:
07.02.2013
107
Screen Number
Part
Descript ion
Page Heading
This line displays the kind of the current object and the name as page heading. In the screenshot above, it is a group which is called Firewalls, Swit ches, Rout er. Here you also can add the current object to favorites by clicking on the flag, as well as you can define the object's priority by clicking on one of the five stars. For details, please see section Priorit y and Favorit es 145 .
Object Path
For groups, devices, and sensors the path in the device tree to the current object is shown (in the screenshot the path is Local Probe Firewall, Switches, Router). If the current object is the root group, Root will be displayed.
Tabs
Using the tabs you can navigate to various sub-pages of an object, showing monitoring data or changing settings. For more information, please see sections Review Sensor Dat a and Change Device and Sensor Set t ings 133 .
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 Cont ext Menus 148 section.
Object Status
This element indicates the current status of the selected object.
Sensor Status Bar
This element is visible when viewing a probe, a group (including Root ), or a device. It is not available when viewing a sensor's details. The sensor status bar shows the aggregated status of all sensors for the current object, divided into different sensor states. They show the number of sensors in the respective state. For example, you can see how many sensors are in Up, Down, or Warning state. For a detailed description of sensor states, please see Sensor St at es 115 section. You can hide sensors that are in a certain state by removing the check mark symbol in front of the respective sensor symbol. To show them again, re-add the check mark.
Tree Search
108 8 Device Tree View
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.
07.02.2013
This element is only visible when viewing a probe or a group. It is not available when viewing a device's or sensor's details. For
Switch Device Tree View

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

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

There are two additional options to the simple tree views which enable you to display the status of all sensors of your entire installation in a single overview. Click on one of the icons to change the view: Tree Map View (6) The tree map view tiles all devices of your entire installation into one square, arranged by the groups you put them into. Each device changes color dynamically to reflect the overall status of the sensors on the device. You can also adjust the size of the squares: either depending on a device's priority, or depending on the number of sensors on a device, or depending on both. For this concern, add a check mark under the point Size by : in front of Sensors and/or Priorit y in the page header bar (see the mark in the screenshot below).
07.02.2013
109
PRTG Tree Map View
Sunburst View (5) The sunburst view shows your entire installation in one circle diagram. The groups are represented as inner circles, and all devices contained within a group are shown as 'cake slices' attached to the outside of a circle element.
110
07.02.2013
PRTG Sunburst View
For both views: Colors A device (or group) element can have different colors, depending on the states of the sensors running on this device or group (see Sensor St at es 115 ) 115 . A more severe status is regarded more important and wins the color battle. For example, if a device currently has sensors in the states Up (green), Paused (blue), and Warning (yellow), the according device tile in this view would be yellow, indicating that at least one sensor on this device is in Warning status. If there are any red Down sensors, the according device tile will turn red. Following, all possible states in both views are listed ordered by their hierarchy:
07.02.2013
111
Flag
Flag Color Red
Object St at us Down
Meaning At least one sensor of this object shows a red Down status. Hover an object's name to view the total number of alarms concerning this object. At least one sensor of this object is Down and the status was acknowledged by a PRTG user, applying the Acknowledge Alarm function. The Down states of all sensors of this object have to be acknowledgedif at least one sensor is unacknowledged down, this object will be displayed as Down. At least one sensor of this object shows a yellow Warning status. There is no sensor in a Down or Down (Acknowledged) status concerning this object. At least one sensor of this object shows an orange Unusual status. There is no sensor in a Down, Down (Acknowledged), or Warning status concerning this object. All sensors of this object are in a green Up status. There is no sensor in a Down, Down (Acknowledged), Warning , Paused, or Unusual status concerning this object. All sensors of this object show a blue Paused status. There is no sensor in a Down, Down (Acknowledged), Warning , Unusual, or Up status concerning this object. All sensors of this object have an Unknown status. There is no sensor in a Down, Down (Acknowledged), Warning , Unusual, Paused, or Up status concerning this object.
Bright-Red
Down (Acknowledged)
Yellow
Warning
Orange
Unusual
Green
Up
Blue
Paused
Black (Grey)
Unknown
Size by Sensors / Size by Priorit y You can adjust the size of the different squares. They can be calculated by the number of sensors running on a device or within a group, or by the sensors' priority (see Priorit y and Favorit es 145 ), or both. Use the check boxes in the page header bar (see the mark in the tree map view screenshot) to change view immediately, then use the setting that suits best for your needs.
112
07.02.2013
Page Content
The page content of the general layout varies dependent on the selected object. It shows information about the current object and all other objects underneath in the tree hierarchy. The deeper down in the hierarchy you select an object, the more detailed is the displayed information. By default, a Probe Device is created in the device tree on the local probe. It represents the probe system running with your PRTG installation. PRTG automatically monitors the system health of the core server and each probe in order to discover overloading situations that may distort monitoring results. To monitor the system status of the probe computer, PRTG automatically creates a few sensors. These include a Core/Probe Healt h Sensor, a WMI sensor that measures disk usage, and a bandwidth sensor for all installed network cards. It is recommended to keep these sensors, but you can optionally remove all except the Core/ Probe Healt h sensor. In a cluster installation, PRTG also creates a Clust er Probe Device with a Clust er Probe Healt h Sensor 340 that monitors the cluster's system health. You can add (or remove) a device or sensor to favorites by one click on the respective flag displayed with an object (please see the marks in the screenshot below).
One-Clic k Adding to Fav orites in the Dev ic e Tree
Another one-click option for adding/removing favorites or setting the priority for a selected device or sensor is given in the page header bar 107 right to the object name (please see screen number 1 in that subsection). Simply click on the flag for favorites or on a star for priority.
One-Clic k Fav orite and Priority in the Page Header Bar
A black flag means that the respective object is a favorite already; clicking on the black flag will remove the object from favorites. A gray flag indicates that it is not a favorite yet. Please see also Priorit y and Favorit es 145 for this concern. For more details about page contents, please see the following sections: Review Monit oring Dat a Hist oric Dat a Report s Object Set t ings
133 126 118
Compare Sensors
123
07.02.2013
113
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
114
07.02.2013
Part 5: Ajax Web InterfaceBasic Procedures | 4 Sensor States
5.4
Sensor States
In PRTG's device tree you usually create several sensors on each 'device 261 '. With sensors, you can monitor different aspects of your devices. Using a simple color code, they always show you what is going on in your network. The color of a sensor always shows its current status. Following, you find a list of states a sensor can show. This list also reflects the hierarchy of states whenever summarized sensor states are shown (in the device tree 102 , or on geo maps 1603 ) : the higher a status is in the hierarchy, the higher will be its priority in displaying sensor states. For example, if all the sensors of a specific device are Up, but one of its sensors reached a Down status, then the overall status of this device will be Down as well (for example, displayed red in the Tree Map View 109 ), as this state is hierarchically higher. Note: Down and Down (Part ial) states are hierarchically equal.
Sensor
Color Red
St at us Name Down
Meaning 1. PRTG is not able to reach the device or the sensor has reached an error state. Please see Sensor Warning and Down Behavior 116 below for more information. Note: By design, a sensor does not record any data in its channels while it shows this status. 2. Another reason for this state can be an error limit set in a sensor's Sensor Channels Set t ings 1566 , or an error status due to a sensor Lookup 1879 . Note: In this case, the sensor continues to record data in all sensor channels although the sensor shows an error.
Red/Green Down (Part ial)
In a cluster, at least one node reports this sensor as Down, while at least one other node reports the same sensor as Up. 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 1609 are sent. To set this sensor status, right-click on a sensor in a Down status and from the context menu 148 , select Acknowledge Alarm... . Then enter a comment and click OK.
Bright-Red
Down (Acknowledged)
07.02.2013
115
Sensor
Color Yellow
St at us Name Warning
Meaning 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 116 below for more information. Another reason for this state can be a warning limit set in a sensor's Sensor Channels Set t ings 1566 . The sensor reports unusual values for this weekday and time of day. The unusual detection is based on the historic average data and can be configured or disabled in the system administration 1696 . You can also disable unusual detection for certain groups only (see Group Set t ings 258 ). The last check was okay and the sensor receives data. The sensor is currently paused (for a certain time, or unlimitedly). 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. For extended trouble shooting please see More 117 section below.
Orange
Unusual
Green
Up
Blue
Paused
Black (Gray)
Unknown
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 a crashed server. After a failed request, PRTG tries to reach the device again before setting a sensor to Down status (this is true for almost all types of sensors): 1. If a request to a device fails for the first time, the sensor is set to Warning status. PRTG repeats the request and tries to re-scan the device immediately. 2. If also the second request fails, the sensor is set to Down status 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.
116
07.02.2013
Note: The behavior described above does not apply to a Warning or Down status that is activated due to a warning or error limit set in a sensor's Sensor Channels Set t ings 1566 .
More
Knowledge Base: What to check if sensors are black (gray)? http://www.paessler.com/knowledgebase/en/topic/25643
07.02.2013
117
Part 5: Ajax Web InterfaceBasic Procedures | 5 Review Monitoring Data
5.5
Review Monitoring Data

Pages of probes, groups, device, and sensors have a tab-like interface. Using the tabs you can navigate through various sub-pages of an object in order to show your network's status, view monitoring results, or change settings.
Tabs Bar on Sensor Pages
Overview
The Overview tab shows an overview of the currently selected object and of its sensors. The pages share a common layout, but include different elements, depending on the kind of object you're looking at: For probes and groups, the Overview tab shows a tree with devices and sensors, a GeoMap, 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, colored gauges representing high priority sensors, as well as a list of all sensors on this device. In order to display gauges representing sensors, corresponding sensors need to be tagged with 4 stars (****) or 5 stars (*****) in the priority settings 145 . 5 stars sensors will be represented with bigger gauges than 4 stars sensors. For sensors, the Overview tab shows sensor details, current status, a GeoMap, colored gauges representing the last value of all sensor channels (the primary channel in biggest size), sensor graphs for different time spans, a table with all sensor channels, as well as similar sensors 130 showing correlations. Note: For sensors using lookups 1879 , we recommend staying below 120 lookup values in the primary channel to get expressive gauges. For sensors with a priority of 4 stars, the upper limit is around 40 lookup values.
118
08.10.2013
Dev ic e Ov erv iew Tab with Ov erv iew, High Priority Sensors as Gauges, Sensor Table, Geo Map, and Mini Graphs
Toplists
Toplist s are available for xFlow and Packet Sniffer sensors 279 only. Toplist graphs are displayed right on the sensor overview page. Please see section Toplist s 1586 .
Live Data and Data By x Days

Select one of the tabs Live Dat a (available for sensors only), 2 day s, 30 day s, or 365 day s to display an object's monitoring data live (sensors only), or for different time spans and in more or less detail. Note: The days mentioned here 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 Administ rat or 1847 (Memory Usage) for more details.
2 Day s Tab of a Firewall with Dev ic e Graph and Sensor Mini Graphs
08.10.2013
119
Live Data and Data By x DaysProbes, Groups, and Devices

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

For sensors, the tabs show a graph and data table of the selected sensor. When viewing data of a sensor running on a cluster probe, you can additionally select if you want to show the data of all nodes, or of one specific node only. Please use the Select Clust er Member bar below the tabs. Note: Multi-node graphs are never displayed filled here, but with single lines only. However, historic data reports can have filled multi-node graphs. While viewing a sensor graph you can hide single sensor channels individually. Simply remove the check mark symbol in front of a channel name underneath the graph, and the according channel's line will disappear. You can also Show all or Hide all channels by clicking on the buttons besides the channel names. The graph view will be reset immediately. Next to every graph, you will find two small icons. Using them, you can do the following: Download t he graph: This will show a PNG or SVG file of the graph in a new browser window. You can then save or copy it for later use. Zoom graph in new window: This will open a larger version of the graph in a new browser window.
Historic Data
The Hist oric Dat a tab is available for sensors only. Please see section Hist oric Dat a Report s 126 .
08.10.2013
121
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 141 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 St ruct ure 168 (Sensors) section.
Alarms
The Alarms tab is not available for sensors, but for probes, groups, and devices only. Please see section Alarms 135 .
Log
Please see section Logs
137
Related Topics
Object Set t ings
133
Compare Sensors
123
122
08.10.2013
Part 5: Ajax Web InterfaceBasic Procedures | 6 Compare Sensors
5.6
Compare Sensors
This function allows you to visually compare the graphs of two or more specific objects. The selected graphs will be shown next to each other so you can have a look at all of them at the same time. To open the page to compare graphs of several monitoring objects, from the main menu, choose Sensors | Compare Sensors. Select how many sensors you want to compare.
PRTG Main Menu: Compare Sensors
Once you have chosen the number of sensors that will be compared, an assistant will open where you can define your desired sensors and the time span shown in the graphs.
07.02.2013
123
Compare Graphs of Two Sensors With 30 Day s Interv al
Compare Sensors Settings

Opt ions Time Span Specify the time span for which you want to show the graphs for. Choose between: 2 day s 30 day s 365 day s
124
07.02.2013
Dat a Comparison Select the objects you want to show a graph for. Click on Please click here t o edit ! to open the Object Select or 143 . There will appear as many selection screens as you have defined before.
Selec tion of Objec ts to be Compared
The graphs will be shown immediately after object selection.
Related Topics
If you want to create a sensor that combines the data of different other sensors, please see Sensor Fact ory Sensor
807
07.02.2013
125
Part 5: Ajax Web InterfaceBasic Procedures | 7 Historic Data Reports
5.7
Historic Data Reports

For quick reporting on monitoring data, use historic data reports as an alternative to the exhaustive reports 1636 function. You can view a report of the historic data for each single sensor, on demand. Additionally, you can also export this data and download it to your computer for further processing in external applications. There are two possibilities to call the function for historic data reports: Either you click on the Hist oric Dat a tab on a sensor's detail page, or you choose Sensors | View Hist oric Dat a from the main menu 168 .
Historic Data (Sensor Tab)

The Hist oric Dat a 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
126
13.06.2013
Historic Monitoring Data (Sensors Menu)

When calling the historic data reports via the View Hist oric Dat a 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.
View Historic Data Func tion Called From Main Menu
Historic Data Reports Settings

Review or Download Hist oric Sensor Dat a 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 Select or 143 . Enter the start date and time of the data you want to review. Use the date time picker to enter the date and time. Enter the end date and time of the data you want to review. Use the date time picker to enter the date and time. 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 St art and End values above. Choose between:
Start
End
Quick Range
13.06.2013
127
Review or Download Hist oric Sensor Dat a 1 Day , 2 Day s, 7 Day s, or 14 Day s: Set the date range to the respective day(s) and use the current time of day. Today , Yest erday , Last Week (Mo-Su), Last Week (Su-Sa), Last Mont h, 2 Mont hs, 6 Mont hs, 12 Mont hs: Set the date range to the last matching period, starting 00:00, ending 23:59. 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 Int erval (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 Aut omat ic Averaging 129 below. 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. X ML 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.
Cluster Node
Include Percent iles 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.
128
13.06.2013
Include Percent iles For more information about percentiles, please see section Calculat ing Percent iles 1916 . Percentile This field is only visible if percentile results are enabled above. Enter which percentile you would like to calculate. Please enter an integer value. 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. This field is only visible if percentile results are enabled above. Choose between: Discret e: Chooses the next smaller discrete value. Cont inuous: Interpolates between discrete values.
Percentile Average
Percentile Mode
Click on St art to start the generation of a historic data report. Note: Data reporting is limited to 5 requests per minute.
Automatic Averaging
For performance reasons, PRTG automatically averages monitoring data when calculating data for large time spans. Data is then averaged regardless of the selected average interval.
Time Span in Report Up to 40 days 40 to 500 days
Minimum Level of Det ail (Average Int erval) Any 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 Monit oring Dat a Report s
1636
118
13.06.2013
129
Part 5: Ajax Web InterfaceBasic Procedures | 8 Similar Sensors
5.8
Similar Sensors
With PRTG you can detect relationships between different components in your network. This function is called similar sensors analysis, a heuristic calculation showing similar behavior of your sensors. The analysis is completely automated and sensor type agnostic. It is based on mathematics and fuzzy logic. This feature will help you to find interconnections in your network you were not aware of and optimizes your sensor usage by tracking redundant monitoring of some aspects of your system. You can adjust the depth of similar sensors analysis in Sy st em Administ rat ionSy st em and Websit e 1697 . You can toggle on/off similarity analysis on group basis in the settings of an object (probes, groups, devices) in the device tree. There are two possibilities to view similar sensors: Each sensor's overview page contains a similar sensors section. PRTG lists channels there which show similarities to channels of the current sensor. In addition, you can call a similar sensors overview page via Sensors | Similar Sensors Overview from the main menu 168 .
Similar Sensors (Sensor Overview Tab)

On the overview tab of a sensor, PRTG lists channels which show similarities to channels of the currently selected sensor. The table will be empty if PRTG detects no similarities regarding the selected sensor.
130
08.10.2013
Similar Sensors Sec tion on a Sensor's Ov erv iew Tab
The similar sensors section provides the following information:
Similar Sensors Similarity Shows a measurement of similarity between two channels in percent. Shows a channel of the currently selected sensor. Shows a channel of another sensor similar to a channel of the currently selected sensor (the one in the "Channel" column in the same row).
Channel Similar Channel
Similar Sensors Overview (Sensors Menu)

This page shows the results of the similar sensors analysis from the entire monitoring database. PRTG will list all channels with similarities to another one here.
08.10.2013
131
Similar Sensors Ov erv iew
You can sort the list by clicking on the column headers. The similar sensors overview page provides the following information:
Similar Sensors Overview Original Channel Shows channels to which other channels are compared. Clicking on the column header sorts the list according to the order on the device tree in ascending or descending order. Shows a measurement of similarity between two channels in percent. Clicking on the column header sorts the list according to the similarities in ascending or descending order. Shows a channel compared to the original channel. Clicking on the column header sorts the list according to the order on the device tree in ascending or descending order. Define how many channel similarities are shown on this page. Choose between 50, 100, or 500.
Similarity
Similar Channel
Item Count
132
08.10.2013
Part 5: Ajax Web InterfaceBasic Procedures | 9 Object Settings
5.9
Object Settings
Device Tree Management

The Management tab is available when viewing probes or groups. After clicking this tab you can move devices and sensors right within the tree view. If moving is not possible the web interface will start a clone process automatically. For more information, please see Manage Device Tree
211
section.
General Settings
In the Set t ings tab you can define all settings of the current object. The available options vary, depending on the kind of object you're changing. Please see the following sections for information about the respective object types: Probe Set t ings Group Set t ings Device Set t ings Sensor Set t ings
227
242
261
278
Note: The available setting options are different for each sensor, but always the same for probes, groups, and devices.
Notifications Settings
In the Not ificat ions tab notification triggers can be set for every object. When using these settings for a probe, group, or device, they will be inherited to all sensors on these objects. Available notification trigger options are the same for all objects. For more information, please see Sensor Not ificat ions Set t ings
1573
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. For more information, please see Sensor Channels Set t ings
1566
section.
27.11.2012
133
Part 5: Ajax Web InterfaceBasic Procedures | 9 Object Settings
Comments
In the Comment s tab you can enter free text for each object. This can be used for documentation purposes or to leave information for other users.
History
In the Hist ory tab all changes in the settings of an object are logged with a timestamp, the PRTG user which conducted the change, and a message. The history log keeps the last 100 entries.
Related Topics
General Lay out
102
Review Monit oring Dat a Toplist s

1586
118
134
27.11.2012
Part 5: Ajax Web InterfaceBasic Procedures | 10 Alarms
5.10
Alarms
The Alarm list shows all sensors that are currently in a Down, Down (Part ial), 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)

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

Click the Alarms entry from the main menu 171 to show a table list of all sensors in your configuration that currently show a Down, Down (Part ial), Down (Acknowledged), Warning , or Unusual status. You can also show these sensors as gauges. Hover the Alarms entry and select another option to only show a subset of sensors in certain states. Choose between: All Shows a list of all sensors which currently show a Down, Down (Part ial), Down (Acknowledged), Warning , or Unusual status. Show as Gauges Shows the gauges of all sensors which currently show a Down, Down (Part ial), Down (Acknowledged), Warning , or Unusual status. The size of the sensor gauges corresponds to their respective priority. Errors only Shows a list of all sensors which currently show a Down, Down (Part ial), or Down (Acknowledged) status. Warnings only Shows a list of all sensors which currently show a Warning status. Unusuals only Shows a list of all sensors which currently show an Unusual status.
Acknowledge Alarm
An acknowledged alarm will show up in the alarms list as "acknowledged" (see Sensor St at es 115 ) and will not trigger 1573 any more notifications 1609 . Note: If the alarm condition clears, the sensor will usually return into an Up status immediately with the next sensor scan. In order to acknowledge an alarm, right-click on a sensor and choose Acknowledge Alarm... from the context menu, enter a message and click the OK button. The message will appear in the sensor's last message value. You can choose between: Acknowledge Indefinit ely ... , acknowledge For 5 Minut es... , For 15 Minut es... , For 1 Hour... , For 3 Hours... , For 1 Day ... , or Unt il... . If you choose Unt il... a popup window will appear where you can define a date. If the alarm condition still exists after this date, the sensor will show a Down status again. Only users 1710 with write access rights may acknowledge alarms. Read-only users can be given the right to acknowledge alarms, too.
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
136
19.07.2013
Part 5: Ajax Web InterfaceBasic Procedures | 11 Logs
5.11
Logs
The Logs list shows all past activities and events of your PRTG monitoring setup. This is useful to keep track of all important activities and, for example, to check whether messages were sent, etc. In a typical setup, a huge amount of data is produced here. As the activity of every single object is minuted, you can use this data to check exactly if your setup works as expected. To support you when viewing the log files, there are several filters available. Please see Working wit h Table List s 141 section for more information.
List with Log Entries
There are two possibilities to call the logs list: Either you click on the Log tab on the detail page of a probe, group, device, or sensor, or you choose the Logs entry in the main menu.
Log (Object Tab)

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

Click the Logs entry from the main menu 173 to show a table list of all system log entries in your configuration. Hover the Logs entry and select another option to only show a subset of entries for certain objects for certain kind of entries. Choose between:
08.10.2013
137
Part 5: Ajax Web InterfaceBasic Procedures | 11 Logs
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. St at us 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 St at us field only. Select between Up & Down (shows entries with either Up or Down in the St at us field), Down, Warning , Unusual, Up, Paused/Resumed (shows entries with either Paused or Resumed in the St at us field), or Acknowledged Alarms. Sy st em Event s Show log information regarding certain system event types only. Hover to show other menu items. Select between the following event types: Probe Relat ed, Clust er Relat ed, Aut oDiscovery , Not ificat ions, or St at us Messages.
138
08.10.2013
Part 5: Ajax Web InterfaceBasic Procedures | 12 ToDos
5.12
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 1691 (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 141 . Hover to show other menu items. Choose between: All Open ToDos 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 Relat ed Aut o-Discovery Relat ed Probe Relat ed
27.11.2012
139
Part 5: Ajax Web InterfaceBasic Procedures | 12 ToDos
Clust er Relat ed Sy st em Errors New Soft ware Version Open and Acknowledged ToDos Shows all already acknowledged ToDos as well as all open ToDos, filtered by certain system event types. Hover to show other menu items. You can select the same filter types as under Open ToDos. Acknowledge all ToDos This option acknowledges all open ToDos. A warning popup is shown, asking you to confirm this action.
140
27.11.2012
Part 5: Ajax Web InterfaceBasic Procedures | 13 Working with Table Lists
5.13
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 1619 , Maps 1655 , Report s 1636 , Not ificat ions 1609 , and Schedules 1687 , as well as in Logs 137 and ToDos 139 . All these provide common functionality.
Example of a Table List
27.11.2012
141
Part 5: Ajax Web InterfaceBasic Procedures | 13 Working with Table Lists
Feat ure Paging
Display
What it does 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. Click on the window symbol at the beginning or the end of a list to open the table in a new window. When viewing log lists (not available in other lists), hover the Dat e Range option at the beginning of the list to select the time span you want to show log entries for. Choose between Today , Yest erday , and several other time spans. Choose Unlimit ed to disable this filter again. Hover the It em Count option at the beginning of the list to select how many rows are shown on each page. Choose between 50, 100, and 500. Click on the column headers to sort lists by the respective column. You can click on all blue words to sort, for example, by St at us, Last Value, Priorit y , and more. The available options vary depending on the type of list. Click on the X ML option at the end of a list to download the current page in XML format. Your browser will usually show a download dialog.
New window
Date Range
Item Count
Sorting
Show XML
Related Topics
Mult i-Edit List s
1595
142
27.11.2012
Part 5: Ajax Web InterfaceBasic Procedures | 14 Object Selector
5.14
Object Selector
For some functions, the object selector is shown. It enables you to browse all objects in your configuration and select an object in two steps.
Objec t Selec tor
Step 1: Navigate Device Tree

On the left hand side, you see a device tree specific to your setup. 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 St ring 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.
84
27.11.2012
143
Part 5: Ajax Web InterfaceBasic Procedures | 14 Object Selector
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.
144
27.11.2012
Part 5: Ajax Web InterfaceBasic Procedures | 15 Priority and Favorites
5.15
Priority and Favorites

You can set priorities for all objects in your setup as well as 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 148 and select Priorit y . 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 ***).
Context Menu: Priority
Favorites for Devices and Sensors

To call a list of all your favorite devices or sensors, select Devices | Favorit e Devices or Sensors | Favorit e Sensors from the main menu. These lists are sorted by priority as well. You can mark any device or sensor as favorite to add it to the favorite list. Right click on it to open the context menu 148 . Select Priorit y /Favorit e | Add t o Favorit es. A small flag symbol will be added next to the object's name.
Context Menu: Priority /Fav orites (Add)
To remove an object from the favorites list, select Priorit y /Favorit e | Remove from Favorit es from the context menu 148 .
07.02.2013
145
Part 5: Ajax Web InterfaceBasic Procedures | 15 Priority and Favorites
Context Menu: Priority /Fav orites (Remov e)
There is also the option to add a device or sensor to favorites by one click in the device tree. Just click on the small flag symbol right to the respective object name for this concern. If the flag is black, the specific object is already a favorite; clicking anew on the flag will remove it from favorites and the flag will turn gray again.
One-Clic k Adding to Fav orites in the Dev ic e Tree
Priority and Favorites in the Page Header Bar

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

If you pause monitoring for an object in the device tree 102 , 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 148 . 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.
27.11.2012
147
Part 5: Ajax Web InterfaceBasic Procedures | 17 Context Menus
5.17
Context Menus
Right-click on an object to view a context menu with many options for direct access to monitoring data and functions. You can also access many of the functionalities via the main menu 165 or the hover popup 164 window. However, using the context menus is the easier way in most cases. Note: In order to view your browser's context menu, hold down the Ctrl key (Chrome) or the Shift key (Firefox) while right-clicking. You will then see your browser's instead of the PRTG menu. This is not possible with Internet Explorer. The content of the PRTG context menu varies, depending on the type of object you have selected. Please see the following sub sections for an overview of the available options. Probe Cont ext Menu Group Cont ext Menu Device Cont ext Menu Sensor Cont ext Menu
148
151
156
160
Probe Context Menu
Context Menu
Check Now This will perform an immediate scan for the selected probe. The data for all devices and sensors in the object hierarchy 78 underneath will be queried.
148
08.10.2013
Det ails... This will show the details of the selected probe, such as its status, the groups on the selected probe, and an overview about the sensor states on the selected probe. Edit The edit menu will appear.
Context Menu Edit
Edit Set t ings... This will open the Probe Set t ings Edit Not ificat ions... This will open the Not ificat ions
227
tab.
1609
tab.
89
Edit Access Right s... This will open a popup to edit access rights
Edit Rename... This will open a popup to edit the name of the selected probe. Edit Management ... This will open the management
211
tab.
Add Group... This will open an assistant which guides you through the process of adding a new group to the selected probe. For detailed instructions, please see Add a Group 194 . Add Aut o-Discovery Group... This will open an assistant which guides you through the process of adding a new autodiscovery group to your setup. PRTG will create a new group and run an auto-discovery in your network in order to add devices and sensors for these devices automatically. For more information, please see section Using t he Aut o-Discovery 181 . Add Device... This will open an assistant which guides you through adding a new device to the selected probe. For detailed instructions, please see Add a Device 200 . Sort Alphabet ically This will sort direct children (groups and devices) of the selected probe in alphabetical order. The ordering will be stored in the monitoring configuration and cannot be revoked. Delet e... This will delete the selected probe. You will be asked for confirmation before anything is actually deleted. Move The move menu will appear.
08.10.2013
149
Context Menu Mov e
This will move the selected probe. Choose between Move Top: This will move the probe to the top of the mother node (here the root group). Move Up: This will move the probe one entry up under the root group. Move Down: This will move the probe one entry down under the root group. Move Bot t om: This will move the probe to the bottom of the root group. Move Management ... : This will open the management Pause The pause menu will appear.
211
tab.
Context Menu Pause
If the probe is already in a paused state, Resume will appear in the context menu instead of Pause .
Context Menu Paused
You can pause and resume monitoring on the selected probe. The monitoring for all sensors in the object hierarchy 78 underneath will be paused resp. resumed. You can choose between: Pause Indefinit ely ... , pause For 5 Minut es... , For 15 Minut es... , For 1 Hour... , For 3 Hours... , For 1 Day ... , or Pause Unt il... . If you choose Pause Unt il... a popup window will appear where you can define a date. Monitoring will be resumed after this date. You can directly add a One-t ime maint enance window to pause monitoring during a planned downtime. In the appearing window, use the date time picker to enter the start date and time of the maintenance window, as well as the end time, for the selected object.
150
08.10.2013
Priorit y The priority menu will appear.
Context Menu Priority
Define the priority of the selected probe. For details, please see Priorit y and Favorit es 145 . Hist oric Dat a The historic data menu will appear.
Context Menu Historic Data
Depending on what time interval you choose, Last 2 day s... , Last 30 day s... , or Last 365 day s... , the Hist oric Dat a Report s 126 tab for the specified interval will be opened. Hist oric Dat a Creat e Report ... will open an assistant to add a report. For details, please see Report s St ep by St ep 1639 . Send Link by email You can send the link to the selected probe by email. This will open a new email using your system's standard email client. It will contain a direct link to the selected probe's details page.
Group Context Menu

Note: The context menu of the Root group is special and differs from the other groups' menu.
08.10.2013
151
Context Menu
Check Now This will perform an immediate scan for the selected group. The data for all devices and sensors in the object hierarchy 78 underneath will be queried. Det ails... This will show the details of the selected group, such as its status, the devices on the selected group, and an overview about the sensor states on the selected group. Edit The edit menu will appear.
Context Menu Edit
Set t ings... This will open the Group Set t ings Not ificat ions... This will open the Not ificat ions
242
tab.
1609
tab.
89
Access Right s... This will open a popup to edit access rights
152
08.10.2013
Rename... This will open a popup to edit the name of the selected group. Management ... This will open the management
211
tab.
Add Group... This will open an assistant which guides you through the process of adding a new group to the selected group. For detailed instructions, please see Add a Group 194 . Add Aut o-Discovery Group... This will open an assistant which guides you through the process of adding a new autodiscovery group to your setup. PRTG will create a new group and run an auto-discovery in your network in order to add devices and sensors for these devices automatically. For more information, please see section Using t he Aut o-Discovery 181 . Add Device... This will open an assistant which guides you through adding a new device to the selected group. For detailed instructions, please see Add a Device 200 . Run Aut o-Discovery If you select this option, an automatic search is started, adding new sensors to the selected group. The search is running in the background. If found, you will see new sensors after a few minutes automatically. For more information, please see Aut o-Discovery 182 (Run Aut oDiscovery Now). Sort Alphabet ically This will sort direct children (devices and other groups) of the selected group in alphabetical order. The ordering will be stored in the monitoring configuration and cannot be revoked. Delet e... This will delete the selected group. You will be asked for confirmation before anything is actually deleted. Clone This will open an assistant which guides you through cloning the selected group. For detailed instructions, please see Clone Object 1592 . Move The move menu will appear.
Context Menu Mov e
This will move the selected group. Choose between Move Top: This will move the group to the top of the mother node (here usually a probe or another group). Move Up: This will move the group one entry up under the mother node.
08.10.2013
153
Move Down: This will move the group one entry down under the mother node. Move Bot t om: This will move the group to the bottom of the mother node. Move To Ot her Group: This will move the group to another group. An assistant will appear in this case with information about the selected group and the subobjects which also will be moved. Please choose a target group from the list. Move Management ... : This will open the management Pause The pause menu will appear.
211
tab.
Context Menu Pause
If the group is already in a paused state, Resume will appear in the context menu instead of Pause .
Context Menu Paused
You can pause and resume monitoring on the selected group. The monitoring for all sensors in the object hierarchy 78 underneath will be paused resp. resumed. You can choose between: Pause Indefinit ely ... , pause For 5 Minut es... , For 15 Minut es... , For 1 Hour... , For 3 Hours... , For 1 Day ... , or Pause Unt il... . If you choose Pause Unt il... a popup window will appear where you can define a date. Monitoring will be resumed after this date. You can directly add a One-t ime maint enance window to pause monitoring during a planned downtime. In the appearing window, use the date time picker to enter the start date and time of the maintenance window, as well as the end time, for the selected object. Priorit y The priority menu will appear.
154
08.10.2013
Context Menu Priority
Define the priority of the selected group. For details, please see Priorit y and Favorit es 145 . Hist oric Dat a The historic data menu will appear.
Depending on what time interval you choose, Last 2 day s... , Last 30 day s... , or Last 365 day s... , the Hist oric Dat a Report s 126 tab for the specified interval will be opened. Hist oric Dat a Creat e Report ... will open an assistant to add a report. For details, please see Report s St ep by St ep 1639 . Send Link by email You can send the link to the selected group by email. This will open a new email using your system's standard email client. It will contain a direct link to the selected probe's details page.
08.10.2013
155
Device Context Menu
Dev ic e Context Menu
Check Now This will perform an immediate scan for the selected device. The data for all sensors in the object hierarchy 78 underneath will be queried. Det ails... This will show the details of the selected device, such as its status and the sensor states on the selected device. Edit The edit menu will appear.
Context Menu Edit
Set t ings... This will open the Device Set t ings Not ificat ions... This will open the Not ificat ions
261
tab.
1609
tab.
89
Access Right s... This will open a popup to edit access rights 156
.
08.10.2013
Rename... This will open a popup to edit the name of the selected device. Add Sensor... This will open an assistant which guides you through adding a new sensor to the selected device. For detailed instructions, please see Add a Sensor 209 . Run Aut o-Discovery If you select this option, an automatic search is started, adding new sensors to the selected device. The search is running in the background. If found, you will see new sensors after a few minutes automatically. For more information, please see Aut o-Discovery 182 (Run Aut oDiscovery Now). Creat e Device Templat e... This will open an assistant which guides you through creating a new device template; this will then be available in auto-discovery 181 . For detailed instructions, please see Creat e Device Templat e 1600 . Sort Alphabet ically This will sort direct children (sensors) of the selected device in alphabetical order. The ordering will be stored in the monitoring configuration and cannot be revoked. Delet e... This will delete the selected device. You will be asked for confirmation before anything is actually deleted. Clone This will open an assistant which guides you through cloning the selected device. For detailed instructions, please see Clone Object 1592 . Move The move menu will appear.
Context Menu Mov e
This will move the selected device. Choose between Move Top: This will move the device to the top of the mother node (here usually a group or a probe). Move Up: This will move the device one entry up under the mother node. Move Down: This will move the device one entry down under the mother node. Move Bot t om: This will move the device to the bottom of the mother node. Move To Ot her Group: This will move the device to another group. An assistant will appear in this case with information about the selected device and the subobjects which also will be moved. Please choose a target group from the list.
08.10.2013
157
Pause The pause menu will appear.
Context Menu Pause
If the device is already in a paused state, Resume will appear in the context menu instead of Pause .
Context Menu Paused
You can pause and resume monitoring on the selected device. The monitoring for all sensors in the object hierarchy 78 underneath will be paused resp. resumed. You can choose between: Pause Indefinit ely ... , pause For 5 Minut es... , For 15 Minut es... , For 1 Hour... , For 3 Hours... , For 1 Day ... , or Pause Unt il... . If you choose Pause Unt il... a popup window will appear where you can define a date. Monitoring will be resumed after this date. You can directly add a One-t ime maint enance window to pause monitoring during a planned downtime. In the appearing window, use the date time picker to enter the start date and time of the maintenance window, as well as the end time, for the selected object. Priorit y /Favorit e The priority/favorite menu will appear.
Context Menu Priority /Fav orite
Define the priority of the selected device, or add resp. remove the device to resp. from the favorites. For details, please see Priorit y and Favorit es 145 . Hist oric Dat a The historic data menu will appear.
158
08.10.2013
Depending on what time interval you choose, Last 2 day s... , Last 30 day s... , or Last 365 day s... , the Hist oric Dat a Report s 126 tab for the specified interval will be opened. Hist oric Dat a Creat e Report ... will open an assistant to add a report. For details, please see Report s St ep by St ep 1639 . Device Tools The device tools menu will appear.
Context Menu Dev ic e Tools
Go To Service URL... This will open the service page you have defined in the Device Set t ings
261
New window wit h HTTP... This will open a new browser window with Hypertext Transfer Protocol (HTTP) and the IP address / DNS name of the device. New window wit h HTTPS... This will open a new browser window with Hypertext Transfer Protocol Secure (HTTPS) and the IP address / DNS name of the device. New window wit h FTP... This will open a new browser window with File Transfer Protocol (FTP) and the IP address / DNS name of the device. Remot e Deskt op... This will download a .rdp file. When you execute the file remote desktop will start with the IP address / DNS name of the device. Note: In Firefox you have to use mstsc.exe (Microsoft Terminal Service) to open the file. Tracerout e... This will start a traceroute on the selected device. PRTG will display the route and measure transit delays of packets across the IP network. Inst all Remot e Probe... This will open an assistant to install a Remot e Probe of PRTG on this device. For more details, please see Remot e Probe Quick Inst all 1891 .
08.10.2013
159
Find Duplicat es... Search in your PRTG configuration for devices with the same IP address or DNS name as the selected device. A window with the results will appear, either showing existing duplicates or a message indicating that there are no duplicates. Send Link by email You can send the link to the selected device by email. This will open a new email using your system's standard email client. It will contain a direct link to the selected probe's details page.
Sensor Context Menu
Context Menu
Check Now This will perform an immediate scan for the selected sensor. Det ails... This will show the details of the selected sensor, such as its status and channels. Edit The edit menu will appear.
Context Menu Edit
Set t ings... This will open the Sensor Set t ings Not ificat ions... This will open the Not ificat ions
1609
278
tab.
tab.
160
08.10.2013
Channels... This will open the Channels tab. Access Right s... This will open a popup to edit access rights
89
Rename... This will open a popup to edit the name of the selected device. Acknowledge Alarm This option is available only in the sensor context menu when a sensor in a Down or Down (Part ial) status is selected.
Context Menu Ac knowledge Alarm
You can acknowledge an alarm for the selected sensor. An acknowledged alarm will show up in the alarms list as "acknowledged" (see Sensor St at es 115 ) and will not trigger 1573 any more notifications 1609 . You can choose between: Acknowledge Indefinit ely ... , acknowledge For 5 Minut es... , For 15 Minut es... , For 1 Hour... , For 3 Hours... , For 1 Day ... , or Unt il... . If you choose Unt il... a popup window will appear where you can define a date. If the alarm condition still exists after this date, the sensor will show a Down status again. Note: If the alarm condition clears, the sensor will usually return into an Up status immediately with the next sensor scan. For details about acknowledging an alarm, please see Alarms 136 section. Delet e... This will delete the selected sensor. You will be asked for confirmation before anything is actually deleted. Clone This will open an assistant which guides you through cloning the selected sensor. For detailed instructions, please see Clone Object 1592 . Move The move menu will appear.
08.10.2013
161
Context Menu Mov e
This will move the selected sensor. Choose between Move Top: This will move the sensor to the top of the mother node (here a device). Move Up: This will move the sensor one entry up under the device. Move Down: This will move the sensor one entry down under the device. Move Bot t om: This will move the sensor to the bottom of the device. Pause The pause menu will appear.
Context Menu Pause
If the sensor is already in a paused state, Resume will appear in the context menu instead of Pause .
Context Menu Paused
You can pause and resume monitoring on the selected sensor. You can choose between: Pause Indefinit ely ... , pause For 5 Minut es... , For 15 Minut es... , For 1 Hour... , For 3 Hours... , For 1 Day ... , or Pause Unt il... . If you choose Pause Unt il... a popup window will appear where you can define a date. Monitoring will be resumed after this date. You can directly add a One-t ime maint enance window to pause monitoring during a planned downtime. In the appearing window, use the date time picker to enter the start date and time of the maintenance window, as well as the end time, for the selected object. Simulat e Error St at us This will set the selected sensor to a simulated error state. As for the paused state, Resume will appear in the context menu if a the selected sensor is already in a simulated error state. 162
08.10.2013
Priorit y /Favorit e The priority/feature menu will appear.
Context Menu Priority /Fav orite
Define the priority of the selected sensor. For details, please see Priorit y and Favorit es 145 . Hist oric Dat a The historic data menu will appear.
Depending on what time interval you choose, Last 2 day s... , Last 30 day s... , or Last 365 day s... , the Hist oric Dat a Report s 126 tab for the specified interval will be opened. Hist oric Dat a Creat e Report ... will open an assistant to add a report. For details, please see Report s St ep by St ep 1639 . Send Link by email You can send the link to the selected sensor by email. This will open a new email using your system's standard email client. It will contain a direct link to the selected probe's details page.
08.10.2013
163
Part 5: Ajax Web InterfaceBasic Procedures | 18 Hover Popup
5.18
Hover Popup
Whenever you rest the mouse pointer for a second over an object's icon in the device tree 102 , a hover popup window will appear, showing details about this object. It contains information from the object's overview tab 118 , as well as several graphs. The exact information provided depends on the kind of object you are hovering.
Hov er Menu Example: VMware 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 148 which is shown when right-clicking it.
164
27.11.2012
Part 5: Ajax Web InterfaceBasic Procedures | 19 Main Menu Structure
5.19
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.
PRTG Main Menu
Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default. The following menu items are available: Home
165
Devices Libraries Sensors Alarms Maps
166
168
168
171
172
Reports Logs
173
172
ToDos Setup
174
174
Refresh (Arrows Symbol) Help Center (? Symbol) Logout (Off Symbol) Search Box
177 177 176
176
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 1673 . Hover to show other menu items.
08.10.2013
165
PRTG Main Menu: Home
Dashboard 1 Dashboard 3 The dashboards provide different preset overviews with the status of your sensors. Choose the one that fits your needs. Note: Dashboards are not customizable. You can create your own overview pages using the Maps 1655 feature. Swit ch Clust er Node This option is only available if PRTG runs in Clust ering 76 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, showing the same page there. Sit emap 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 t o Mobile Web GUI This switches to the Mobile Web GUI 1797 optimized for low bandwidth and mobile devices. Less scripting is used for more compatibility. However, this is a read-only interface. Welcome t o PRTG Shows the welcome screen which leads you to the major sections of the web interface. Configurat ion Guru This will open the Configurat ion Guru welcome page. For details about the guru, please see section Using t he Configurat ion Guru 32 . 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 1673 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.
166
08.10.2013
PRTG Main Menu: Dev ic es
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 Favorit e Devices to show a list of all devices marked as Favorit e 145 . Note: 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 141 appearing, you can re-sort the items by clicking on the column's header items. Favorit e Devices Shows a table list of all devices marked as Favorit e 145 . Note: To mark any device as a favorite device, select Priorit y /Favorit e | Add t o Favorit es from its context menu or click on the small flag on a device's details page. Dependencies Shows an overview list of the dependencies configured for the objects in your setup. Hover the menu item to show other menu items. Choose between Select ed Dependencies and Mast er Dependencies to view a list of all dependencies or explicit ones. Follow the menu path (it is specific to your setup) to view dependencies of the objects in a specific probe or group only. Add Group Start an assistant which guides you through the process of adding a new group to your setup. For more information, please see section Creat e Object s Manually 193 . Tip: You can create new groups much faster by choosing Add Group... from a probe's or group's context menu! Add Aut o-Discovery Group 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 t he Aut o-Discovery 181 Tip: You can create new groups much faster by choosing Add Aut o-Discovery Group... from a probe's or group's context menu!
08.10.2013
167
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 Creat e Object s Manually 193 . 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 1619 section. Hover to show other menu items.
PRTG Main Menu: Libraries
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
1622
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. Note: In the column Last Value only the last value of the sensor's primary channel will be shown.
168
08.10.2013
PRTG Main Menu: Sensors
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. Note: In the column Last Value only the last value of the sensor's primary channel will be shown. 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 209 . 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. Favorit e Sensors Shows a table list of all sensors marked as Favorit e 145 . Note: To mark any sensor as a favorite sensor, select Priorit y /Favorit e | Add t o Favorit es from its context menu or click on the small flag on a device's details page. Top 10 List s 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 141 of Fast est or Slowest sensors regarding Ping Port
08.10.2013
169
Webpages IMAP/POP3/SMTP FTP as well as Most Used or Least Used sensors regarding Bandwidt h CPU Disk Memory Note: The sensors will be selected by default tags. By Current St at us This is an option to show a filtered sensor list. Hover to show other menu items. Follow the menu path to view table lists 1550 of all sensors in a certain state. Select between status Up Warning Down Down (Part ial) Down (Acknowledged) Unusual Paused Unknown For more information about sensor states, please see Sensor St at es
115
section.
By Upt ime/Downt ime This is an option to show a filtered sensor list. Hover to show other menu items. Follow the menu path to view table lists 141 of all sensors sorted by their up- or downtime. Select between Best Upt ime (%) Highest Upt ime (Time) Worst Downt ime (%) Highest Downt ime (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 141 of a specific probe or group only. By Ty pe 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 view a sensor table list 141 containing only sensors of one specific sensor type.
170
08.10.2013
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 141 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, or to view them by type or tag. Compare Sensors Calls a function to compare graphs of two or more monitoring objects. Hover to show other menu items. Follow the menu path to open an assistant for comparing several monitoring objects. For more information, please see Compare Sensors 123 section. View Hist oric Dat a Calls a function for quick generation of sensor data reports. For more information, please see Hist oric Dat a Report s 126 section. Similar Sensors Overview Calls an overview page listing similar sensors. For more information, please see Similar Sensors 130 section.
Alarms
Click to show a all sensors that currently show a Down, Down (Part ial), Warning , or Unusual status. In the table list 141 appearing, you can re-sort the items by clicking on the column's header items. If you select Show as Gauges, the sensor gauges will be displayed in a size corresponding to their priority. Hover to show other menu items.
PRTG Main Menu: Alarms
All Shows a list of all sensors which currently show a Down, Down (Part ial), Down (Acknowledged), Warning , or Unusual status. Show as Gauges Shows the gauges of all sensors which currently show a Down, Down (Part ial), Down (Acknowledged), Warning , or Unusual status. The size of the sensor gauges corresponds to their respective priority. Errors only Shows a list of all sensors which currently show a Down, Down (Part ial), or Down (Acknowledged) status.
08.10.2013
171
Warnings only Shows a list of all sensors which currently show a Warning status. Unusuals only Shows a list of all sensors which currently show an Unusual status.
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 1655 section. Hover to show other menu items.
PRTG Main Menu: Maps
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
1658
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 Report s 1636 section. Hover to show other menu items.
PRTG Main Menu: Reports
All Calls the Reports feature where you can view or add reports of your monitoring data.
172
08.10.2013
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 141 appearing, you can filter the items by using the respective options 141 . Hover to show other menu items. For more information, please see Logs 137 section.
PRTG Main Menu: Logs
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. St at us 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 St at us field only. Select between Up & Down (shows entries with either Up or Down in the St at us field), Down, Warning , Unusual, Up, Paused/Resumed (shows entries with either Paused or Resumed in the St at us field), or Acknowledged Alarms. Sy st em Event s Show log information regarding certain system event types only. Hover to show other menu items. Select between the following event types: Probe Relat ed, Clust er Relat ed, Aut oDiscovery , Not ificat ions, or St at us Messages.
08.10.2013
173
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 141 appearing, you can filter the items by using the respective options 141 . Hover to show other menu items. For more information, please see ToDos 139 section.
PRTG Main Menu: ToDo(s)
All Open ToDos 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 Relat ed Aut o-Discovery Relat ed Probe Relat ed Clust er Relat ed Sy st em Errors New Soft ware Version Open and Acknowledged ToDos Shows all already acknowledged ToDos as well as all open ToDos, filtered by certain system event types. Hover to show other menu items. You can select the same filter types as under Open ToDos. 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 Set up 1671 section.
174
08.10.2013
PRTG Main Menu: Setup
Overview Shows the setup page
1671
Account Set t ings Hover to show menu items of the account settings. Choose from: My Account
1673
Not ificat ions Schedules

1687
1678
Sy st em Administ rat ion Hover to show menu items of the system administration settings. Choose from: Sy st em & Websit e
1691
Not ificat ion Delivery Probes Clust er

1707
1702
1709
User Account s User Groups

1715
1710
Administ rat ive Tools
1719
Downloads / Add-Ons Shows additional downloads for PRTG. Choose from: PRTG Ent erprise Console Apps for iOS & Android Remot e Probe Inst aller PRTG Add-Ons
1737 1737
1737
1737
PRTG Billing Tool
1738
Chrome Deskt op Not ificat ions
1739
Ent er License Key Shows help on how to Ent er a License Key
53 .
08.10.2013
175
PRTG St at us Hover to show menu items of the PRTG status. Choose from: Sy st em St at us Clust er St at us
1723
1735
Act ivat ion St at us
1736
Soft ware Aut o-Updat e Shows the Soft ware Aut o-Updat e 1732 status of your PRTG installation. On this page, you can also download and install available updates. PRTG API Shows documentation about the Applicat ion Programming Int erface (API) Definit ion for your installation. Cont act Support Calls the Cont act Paessler Support / Send Your Feedback t o Paessler page.
1871
1741
Refresh (Arrows Symbol)
PRTG Main Menu: Refresh Button
Click this symbol to refresh all elements on the current page to display current data. Unlike the reload function of your browser, this merely refreshes the single page elements, not the whole page. During the refresh process, this symbol flashes.
Help Center (? Symbol)
PRTG Main Menu: Help Button
Shows the help center which supports you if you have any questions regarding your PRTG setup.
176
08.10.2013
Logout (Off Symbol)
PRTG Main Menu: Logout Button
Logs out the current user and shows the login screen
96
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 are Cont ext Menus open it.
148
available for all objects. Right-click on an object to
08.10.2013
177
Part 6
Ajax Web InterfaceDevice and Sensor Setup
27.11.2012
179
Part 6: Ajax Web InterfaceDevice and Sensor Setup |
Ajax Web InterfaceDevice 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 96 , 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 1710 by the user). The following sections introduce device and sensor setup in the Ajax Graphical User Interface (GUI).
Ajax Web InterfaceDevice and Sensor SetupTopics

Aut o-Discovery
181
Creat e Object s Manually Manage Device Tree Root Group Set t ings Probe Set t ings Group Set t ings Device Set t ings Sensor Set t ings
227 211
193
213
242
261
278
List of Available Sensor Ty pes

1566
279
Sensor Channels Set t ings
Sensor Not ificat ions Set t ings
1573

Ajax Web Int erfaceBasic Procedures
94
1584
Ajax Web Int erfaceAdvanced Procedures
Related Topics
Ent erprise Console
1744
1796
180
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 1 Auto-Discovery
6.1
Auto-Discovery
PRTG's auto-discovery function is a great way to automatically create a sophisticated and concise set of sensors for your complete network. It is mainly suitable for LAN discovery since it involves a lot of SNMP and WMI. For video instructions, please see the More 192 section below. For a quick start auto-discovery, please see TWOUsing t he Configurat ion Guru
32
section.
How Auto-Discovery Works

PRTG's auto-discovery process has three stages: St ep 1 Scanning a network segment for devices using Ping (for groups only). St ep 2 Assessing the device type for all devices discovered in Step 1 (using SNMP, WMI and other protocols). St ep 3a Creating sensor sets that match the discovered device types of step 2. This is done based on built-in device templates with recommended sensors for many device types. St ep 3b (opt ional) Creating sensor sets using user created device templates (see Creat e Device Templat e section).
1600
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 139 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 Sy st ems, Linux (SSH/WBEM) Sy st ems, VMware/X EN Servers, and SNMP Devices in order to fully exploit the power of this feature. We recommend defining these in the Root group settings 213 . 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.
07.02.2013
181
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 192 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 Aut o-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 193 only.
Creating an Auto-Discovery Group

There are several ways to start auto-discovery: On the welcome screen
102
, click on the Perform Net work Aut o-Discovery option
or select Devices | Add Aut o-Discovery Group from the main menu. To start an automatic detection of devices and sensors in your network an assistant will appear, leading you through two steps. For faster setup, you can select Add Aut o-Discovery Group... in the context menu 148 of a probe or group to which you want to add the new group. This will skip step 1 and lead you directly to step 2. Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default.
182
07.02.2013
Add Auto-Disc ov ery Group Assistant Step 2
St ep 1 Please choose a probe or group you want to add the new group to. Click on Cont inue. St ep 2 Add auto-discovery settings as described below.
Add Auto-Discovery Group Settings

Group Name and Tags Group Name Enter a meaningful name to identify the group. The name will be shown by default in the devices tree and in all alarms.
07.02.2013
183
Group Name and Tags 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 84 .
Group Ty pe Sensor Management Select the method for automatic network discovery. Choose between: Aut omat ic device ident ificat ion (st andard, recommended): Detect mainly based on Ping, SNMP, and WMI. This option should work fine for most installations. Aut omat ic device ident ificat ion (det ailed, may creat e many sensors): Detect in a more detailed way and create more sensors. This option uses all standard device templates for autodiscovery. It is suitable for small network segments and whenever you want to monitor the maximum number of sensors available. Aut omat ic sensor creat ion using specific device t emplat e(s): Manually define the device templates used for 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, Det ailed) HTTP Web Server Hy per V Host Server Linux/UNIX Device (SNMP or SSH enabled) Localhost RDP Mail Server (Generic) Mail Server (MS Exchange 2003)
184
07.02.2013
Mail Server (MS Exchange 2007) Misc. Det ails Print er (HP) Server (Compaq/HP agent s) Swit ch (Cisco Cat aly st ) Swit ch (Cisco IOS Based) Swit ch (HP Procurve) UNIX /Linux Device UPS (APC) VMware ESX Server Windows (Det ailed via WMI) Windows (via WMI) Windows IIS (via SNMP) X EN 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 148 . Hourly : Perform auto-discovery for new devices and sensors every 60 minutes. Note: Please use this option with caution! Frequently executed auto-discoveries might cause performance issues, especially when large network segments are scanned every hour. Daily : Perform auto-discovery for new devices and sensors every 24 hours. The first auto-discovery will run immediately, all other discoveries will start on the time defined in the Aut o-Discovery Set t ings section of the Sy st em Administ rat ionSy st em and Websit e 1691 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 Aut oDiscovery Set t ings section of the Sy st em Administ rat ion Sy st em and Websit e 1691 settings. IP Selection Method Define how you want to define the IP range for auto-discovery. Choose between: Class C base IP wit h st art /end (IPv4): Define an IPv4 class C address range. List of individual IPs and DNS names (IPv4): Enter a list of individual IPv4 addresses or DNS names.
07.02.2013
185
IP and subnet (IPv4): Enter an IPv4 address and subnet mask. IP wit h oct et range (IPv4): Enter an IPv4 address range for every IP octet individually. With this, you can define very customizable IP ranges. List of individual IPs and DNS names (IPv6): Enter a list of individual IPv6 addresses or DNS names. Use comput ers from t he act ive direct ory (maximum 1000 comput ers): Search in the active directory for computers to perform auto-discovery. Note: 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 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. 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. 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. 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. 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.
IP Range Start
IP Range End
IP List
IP and Subnet
IP with Octet Range
186
07.02.2013
Organizational Unit
This field is only visible if active directory is selected above. Enter an organizational unit (OU) to restrict the active directory search to computers which are part of this OU. Just enter the name of the OU without any other term (i.e., without "OU" in front). If you leave this field empty, there will not be any restriction. If you have sub-OUs, too, please consider the correct syntax in the format Y,OU=X : OUs that are part of another OU have to be listed together with their parent(s). Enter the sub-OU followed by ,OU= and the name of the parent OU. For example, assuming that the organizational unit 'Y' is part of the OU named 'X'. Then the syntax would be Y,OU=X. For three OUs 'X', 'Y' part of 'X', and 'Z' part of 'Y', the syntax would be Z,OU=Y,OU=X. Note that the order is important, sub-OUs have to be listed left of its according parents!
Name Resolution
Define how newly discovered devices will be monitored. This only affects new devices. The setting for existing devices will be kept. Choose between: Use DNS / WMI / SNMP names (recommended): Monitor newly discovered devices via their DNS, WMI, or SNMP names (if available). Use IP addresses: Monitor newly discovered devices via their IP address. We recommend using the default value.
Device Rescan
Define if you want to rescan known devices. Choose between: Skip aut o-discovery for known devices/IPs (recommended): Do not re-scan known devices or IP addresses, but only scan for new devices/IPs when auto-discovering. This can avoid recreation of manually deleted sensors. PRTG will also avoid adding devices that are already included elsewhere in your configuration, e.g. in other groups. Perform aut o-discovery for known devices/IPs: Re-scan known devices and IP addresses with every auto-discovery. This will re-create manually deleted sensors on existing devices. 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 213 group's settings. To change a setting for this object, 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!
07.02.2013
187
Credent ials for Windows Sy st ems Domain or Computer Name Define the authority for Windows access. This is used for Windows Management Instrumentation (WMI) and other Windows sensors. If you want to use a Windows local user account on the target device, please enter the computer name here. If you want to use a Windows domain user account (recommended), please enter the (Active Directory) domain name here. If not explicitly defined, PRTG will automatically add a prefix in order to use the NT LAN Manager (NTLM) protocol. Please do not leave this field empty. Enter the username for Windows access. Usually, you will use credentials with administrator privileges. Enter the password for Windows access. Usually, you will use credentials with administrator privileges.
Username
Password
Credent ials for Linux/Solaris/Mac OS (SSH/WBEM) Sy st ems Username Enter a login name for the access via SSH and WBEM. Usually, you will use credentials with administrator privileges. Define which authentication method will be used for login. Choose between: Login via Password: Provide a password for login. Enter below. Login via Privat e Key : Provide a private key for authentication. Note: PRTG can only handle keys in OpenSSH format which are not encrypted. You cannot use password protected keys here. In the text field, please paste the entire private key, including the "BEGIN" and "END" lines. Please make sure the according public key is provided on the target machine. For details, please see Monit oring via SSH 1816 . 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. This field is only visible if private key login is selected above. Paste a private key into the field (OpenSSH format, unencrypted). Usually, you will use credentials with administrator privileges. Note: If you do not insert a private key for the first time, but change the private key, you need to restart your PRTG core server service in order for the private key change to take effect! For details, please see Monit oring via SSH 1816 .
Login
Private Key
For WBEM Use Protocol Define the protocol that will be used for WBEM. This setting is only relevant when using WBEM sensors. Choose between:
188
07.02.2013
Credent ials for Linux/Solaris/Mac OS (SSH/WBEM) Sy st ems HTTP: Use an unencrypted connection for WBEM. HTTPS : Use an SSL-encrypted connection for WBEM. For WBEM Use Port Define the port that will be used for WBEM. This setting is only relevant when using WBEM sensors. Choose between: Set aut omat ically (port 5988 or 5989): Use one of the standard ports, depending on whether unencrypted or encrypted connection is chosen above. Set manually : Use a custom port. Define below. WBEM Port This setting is only visible if manual port selection is enabled above. Enter the WBEM port number. Define the port number which will be used for SSH connections. Note: By default, this setting is automatically used for all SSH sensors 284 , unless you define a different port number in the sensor settings. Define with which rights the command will be executed on the target system. Choose between: Run t he command as t he user connect ing (default ): Use the rights of the user who establishes the SSH connection. Run t he command as anot her user using 'sudo': Use the rights of another user, for example, the administrator. Run t he command as anot her user using 'su': Use the rights of another target user. Target Username This field is only visible if sudo or su is enabled above. Enter a username to run the specified command as another user than root. If you leave this field empty, the command will be run as root. Ensure that you set the Linux password even you use a public/ private key for authentication. This is not necessary if the user is allowed to execute the command without a password. This field is only visible if su is enabled above. Enter the password for the specified target user.
SSH Port
SSH Rights Elevation
Password Target User
Credent ials for VMware/X enServer User Enter a login name for access to VMware and XEN servers. Usually, you will use credentials with administrator privileges.
07.02.2013
189
Credent ials for VMware/X enServer Password Enter a password for access to VMware and XEN servers. Usually, you will use credentials with administrator privileges. Define the protocol used for the connection to VMware and XenServer. Choose between: HTTPS (recommended): Use an SSL-encrypted connection to VMware and XenServers. HTTP: Use an unencrypted connection to VMware and XenServers.
VMware Protocol
Credent ials 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. This setting is only visible if SNMP version v3 is enabled above. Choose between: MD5: Use Message-Digest Algorithm 5 (MD5) for authentication. SHA: Use Secure Hash Algorithm (SHA) for authentication. The chosen type has to match the authentication type of your device.
Authentication Type
190
07.02.2013
Credent ials for SNMP Devices Note: If you do not want to use authentication, but you need SNMP v3, for example, because your device requires context, you can leave the field password empty. In this case, SNMP_SEC_LEVEL_NOAUTH will be used and authentication will be deactivated entirely. User This setting is only visible if SNMP version v3 is enabled above. Enter a username for secure authentication. This value has to match the username of your device. This setting is only visible if SNMP version v3 is enabled above. Enter a password for secure authentication. This value has to match the password of your device. This setting is only visible if SNMP version v3 is enabled above. Select an encryption type. Choose between: DES : Use Data Encryption Standard (DES) as encryption algorithm. AES : Use Advanced Encryption Standard (AES) as encryption algorithm. The chosen type has to match the encryption type of your device. Data Encryption Key This setting is only visible if SNMP version v3 is enabled above. Enter an encryption key here. If you provide a key in this field, SNMP data packets will be encrypted using the encryption algorithm selected above, providing increased security. The provided key here has to match the encryption key of your device. Note: If the key entered in this field does not match the key configured in the target SNMP device, you will not get an error message! Please enter a string or leave the field empty. This setting is only visible if SNMP version v3 is enabled above. Enter a context name only if it is required by the configuration of the device. Context is a collection of management information accessible by an SNMP device. Please enter a string. Enter the port used for SNMP communication. We recommend using the default value. 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.
Password
Encryption Type
Context Name
SNMP Port
SNMP Timeout (sec.)
Click on the Cont inue button to store your settings. If you change tabs or use the main menu, all changes to the settings will be lost!
07.02.2013
191
Auto-Discovery in Progress
While auto-discovery is running you may experience a lower system performance as usual, because PRTG works in the background in order to discover your network. Depending on the IP ranges defined (up to 65,536 addresses) , the discovery may run up to several days before complete. You can review the status of the discovery process as follows: In the device tree, behind the group or device name, you will see a percentage value showing the progress of auto-discovery. During auto-discovery, the web interface will display a box in the lower right corner, showing the number of active auto-discovery tasks. In order to stop a running auto-discovery, right-click the group or device, and select Pause | For 5 minut es... from the context menu 148 . Monitoring will be paused for 5 minutes, and auto-discovery tasks will be shut down.
Related Topics
Creat e Device Templat e
1600
More
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
192
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
6.2
Create Objects Manually

We recommend using the auto-discovery 181 function to create a basic monitoring setup for your network. Afterwards, you can manually create devices that could not be discovered, or arrange 1591 detected devices in groups. The procedure depends on the kind of object you want to add. Choose between: Add a Group Add a Device Add a Sensor
194
200
209
Add a Remote Probe

Please see Mult iple Probes and Remot e Probes
1887
section for more information.
27.11.2012
193
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually 1 Add a Group
6.2.1
Add a Group
Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default. 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 148 of a probe or group to which you want to add the new group. This will skip step 1 and lead you directly to step 2. St ep 1 Please choose a probe or group you want to add the new group to. Click on Cont inue.
Add Group Assistant Step 2
St ep 2 Add group settings as described below.
194
19.07.2013
Add Group Settings

Group Name and Tags Group Name Enter a meaningful name to identify the group. The name will be shown by default in the devices tree and in all alarms. 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 84 .
Tags
Username
Password
Credent ials for Linux/Solaris/Mac OS (SSH/WBEM) Sy st ems Username Enter a login name for the access via SSH and WBEM. Usually, you will use credentials with administrator privileges. Define which authentication method will be used for login. Choose between: Login via Password: Provide a password for login. Enter below.
Login
19.07.2013
195
Credent ials for Linux/Solaris/Mac OS (SSH/WBEM) Sy st ems Login via Privat e Key : Provide a private key for authentication. Note: PRTG can only handle keys in OpenSSH format which are not encrypted. You cannot use password protected keys here. In the text field, please paste the entire private key, including the "BEGIN" and "END" lines. Please make sure the according public key is provided on the target machine. For details, please see Monit oring via SSH 1816 . 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. This field is only visible if private key login is selected above. Paste a private key into the field (OpenSSH format, unencrypted). Usually, you will use credentials with administrator privileges. Note: If you do not insert a private key for the first time, but change the private key, you need to restart your PRTG core server service in order for the private key change to take effect! For details, please see Monit oring via SSH 1816 .
Private Key
For WBEM Use Protocol Define the protocol that will be used for WBEM. This setting is only relevant when using WBEM sensors. Choose between: HTTP: Use an unencrypted connection for WBEM. HTTPS : Use an SSL-encrypted connection for WBEM. For WBEM Use Port Define the port that will be used for WBEM. This setting is only relevant when using WBEM sensors. Choose between: Set aut omat ically (port 5988 or 5989): Use one of the standard ports, depending on whether unencrypted or encrypted connection is chosen above. Set manually : Use a custom port. Define below. WBEM Port This setting is only visible if manual port selection is enabled above. Enter the WBEM port number. Define the port number which will be used for SSH connections. Note: By default, this setting is automatically used for all SSH sensors 284 , unless you define a different port number in the sensor settings. Define with which rights the command will be executed on the target system. Choose between: Run t he command as t he user connect ing (default ): Use the rights of the user who establishes the SSH connection.
SSH Port
196
19.07.2013
Credent ials for Linux/Solaris/Mac OS (SSH/WBEM) Sy st ems Run t he command as anot her user using 'sudo': Use the rights of another user, for example, the administrator. Run t he command as anot her user using 'su': Use the rights of another target user. Target Username This field is only visible if sudo or su is enabled above. Enter a username to run the specified command as another user than root. If you leave this field empty, the command will be run as root. Ensure that you set the Linux password even you use a public/ private key for authentication. This is not necessary if the user is allowed to execute the command without a password. This field is only visible if su is enabled above. Enter the password for the specified target user.
Credent ials for VMware/X enServer User Enter a login name for access to VMware and XEN servers. Usually, you will use credentials with administrator privileges. Enter a password for access to VMware and XEN servers. Usually, you will use credentials with administrator privileges. Define the protocol used for the connection to VMware and XenServer. Choose between: HTTPS (recommended): Use an SSL-encrypted connection to VMware and XenServers. HTTP: Use an unencrypted connection to VMware and XenServers.
Password
VMware Protocol
Credent ials 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.
19.07.2013
197
Credent ials 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. This setting is only visible if SNMP version v3 is enabled above. Choose between: MD5: Use Message-Digest Algorithm 5 (MD5) for authentication. SHA: Use Secure Hash Algorithm (SHA) for authentication. The chosen type has to match the authentication type of your device. Note: If you do not want to use authentication, but you need SNMP v3, for example, because your device requires context, you can leave the field password empty. In this case, SNMP_SEC_LEVEL_NOAUTH will be used and authentication will be deactivated entirely. User This setting is only visible if SNMP version v3 is enabled above. Enter a username for secure authentication. This value has to match the username of your device. This setting is only visible if SNMP version v3 is enabled above. Enter a password for secure authentication. This value has to match the password of your device. This setting is only visible if SNMP version v3 is enabled above. Select an encryption type. Choose between: DES : Use Data Encryption Standard (DES) as encryption algorithm. AES : Use Advanced Encryption Standard (AES) as encryption algorithm. The chosen type has to match the encryption type of your device.
Authentication Type
Password
Encryption Type
198
19.07.2013
Credent ials for SNMP Devices Data Encryption Key This setting is only visible if SNMP version v3 is enabled above. Enter an encryption key here. If you provide a key in this field, SNMP data packets will be encrypted using the encryption algorithm selected above, providing increased security. The provided key here has to match the encryption key of your device. Note: If the key entered in this field does not match the key configured in the target SNMP device, you will not get an error message! Please enter a string or leave the field empty. This setting is only visible if SNMP version v3 is enabled above. Enter a context name only if it is required by the configuration of the device. Context is a collection of management information accessible by an SNMP device. Please enter a string. Enter the port used for SNMP communication. We recommend using the default value. 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.
Context Name
SNMP Port
SNMP Timeout (sec.)
19.07.2013
199
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually 2 Add a Device
6.2.2
Add a Device
Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default. To manually add a device, select Devices | Add Device from the main menu. An assistant will appear, leading you through two steps. For faster setup, you can select Add Device... in the context menu 148 of a group to which you want to add the new device. This will skip step 1 and lead you directly to step 2. St ep 1 Please choose a group you want to add the new device to. Click on Cont inue.
Add Dev ic e Assistant Step 2
St ep 2 Add device settings as described below.
200
19.07.2013
Add Device Settings

Device Name an Address 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. Define which IP protocol PRTG will use to connect to this device. The setting is valid for all sensors created on this device. Choose between: Connect using IPv4: Use IP version 4 for all requests to this device. Connect using IPv6: Use IP version 6 for all requests to this device. IP Address/DNS Name Enter the IP address (either v4 or v6, depending on your selection above) or DNS name for the device. Most sensors created on this device will inherit this setting and they will try to connect to this address for monitoring. Note: There are some sensor types that still have their own setting for IP address/DNS name. Those sensors will use their own settings. 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 84 . Choose a device icon from the list. It will be shown in the device tree.
IP Version
Tags
Device Icon
Device Ty pe Sensor Management Select which type of auto-discovery you would like to perform for this device. Choose between: Manual (no aut o-discovery ): Do not auto-discover any sensors, but only add sensors manually. Aut omat ic device ident ificat ion (st andard, recommended): Use a small set of auto-discovery templates. This will scan your LAN and usually create a view standard sensors on your device. Aut omat ic device ident ificat ion (det ailed, may creat e many sensors: Use an extended set of auto-discovery templates. This will scan your LAN and usually create many sensors on your device.
19.07.2013
201
Device Ty pe Aut omat ic sensor creat ion using specific device t emplat es: Use specific auto-discovery templates only. Please select templates below. This will scan your LAN and add sensors defined in the template. Discovery Schedule This option is only visible if one of the auto-discovery options is selected above. Define when the auto-discovery will be run. Choose between: Once: Perform auto-discovery only once. For existing devices, this will initiate a one-time sensor update for the current device. Hourly : Perform auto-discovery for new sensors every hour. 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, Det ailed) HTTP Web Server Hy per V Host Server Linux/UNIX Device (SNMP or SSH enabled) Mail Server (Generic) Mail Server (MS Exchange) NTP Server Print er (HP) RDP Server Server (Compaq/HP agent s) Swit ch (Cisco Cat aly st ) Swit ch (Cisco IOS Based)
202
19.07.2013
Device Ty pe Swit ch (HP Procurve) UNIX /Linux Device UPS (APC) Virt uozzo Server VMware ESX Server Windows (Det ailed via WMI) Windows (via WMI) Windows IIS (via SNMP) X EN Server
Username
Password
Login
19.07.2013
203
Private Key
SSH Port
204
19.07.2013
Password
VMware Protocol
19.07.2013
205
Authentication Type
Password
Encryption Type
206
19.07.2013
Context Name
SNMP Port
SNMP Timeout (sec.)
19.07.2013
207
Access Right s User Group Access Define which user group(s) will have access to the object you're editing. A table with user groups and right is shown; it contains all user groups from your setup. For each user group you can choose from the following access rights: Inherit ed: Use the settings of the parent object. None: Users in this group cannot see or edit the object. The object does not show up in lists and in the device tree. Exception: If a child object is visible to the user, the object is visible in the device tree, though not accessible. Read: Users in this group can see the object and review its monitoring results. Writ e: Users in this group can see the object, review its monitoring results, and edit the object's settings. They cannot edit access rights settings. Full: Users in this group can see the object, review its monitoring results, edit the object's settings, and edit access rights settings. You can create new user groups in the Sy st em Administ rat ion User Groups 1715 settings. To automatically set all objects further down in the hierarchy to inherit this object's access rights, set a check mark for the Revert children's access right s t o inherit ed option. For more details about access rights, please see section User Access Right s 89 . Click on the Cont inue button to store your settings. If you change tabs or use the main menu, all changes to the settings will be lost!
208
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually 3 Add a Sensor
6.2.3
Add a Sensor
Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default. To manually add a sensor, 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 148 of a device to which you want to add the new sensor. This will skip step 1 and lead you directly to step 2. St ep 1 Please select Add sensor t o an exist ing device and choose a device you want to add the new sensor to. Click on Cont inue.
Add Sensor Assistant
19.07.2013
209
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually 3 Add a Sensor
St ep 2 The Add Sensor assistant is shown (see screenshot above). Select a sensor you want to add and enter the needed settings. You can filter the listed sensors by type, by target system, and by the used technology. You can choose one aspect per filter. Alternatively or additionally, you can use the live search by typing in a key term (or a fragment) in the Search direct ly box. For more information about a sensor type, please see the manual section of the respective sensor. See List of Available Sensor Ty pes 279 section to find detailed information about every sensor.
210
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 3 Manage Device Tree
6.3
Manage Device Tree

While viewing the device tree (or parts of it), click on the Management tab to enter a different tree view which shows your devices and sensors 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 133 and resume 147 monitoring. Note: You cannot clone 'fixed' objects, such as the root group or a probe device. You cannot clone the sensor types QoS (Qualit y of Service) One Way Sensor 771 and QoS (Qualit y of Service) Round Trip Sensor 777 . Note: In order to clone entire groups or devices, please use the Clone Object accessible via the objects' Context Menu 148 .
1592
functionality
Drag&Drop a Group or Device

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

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

1592
1600
212
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
6.4
Root Group Settings

On the Root group's overview page, click on the Set t ings tab to change settings.
The Root Group is Special

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

The following settings are available in the Set t ings tab. As you may not need all of these, just regard those settings you really need, 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 Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default.
Basic Group Set t ings 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. Define if monitoring for this group is started or paused. Choose between: St art ed: Monitor this group. Paused: Pause monitoring for this group. All sensors on all devices in this group will be paused until this setting is changed again.
Status
08.10.2013
213
Locat ion Location (for geo maps) When using geo maps using Google's API 1603 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 115 (green - yellow - orange - red). You can enter a full postal address, city and country only, or latitude and longitude. It is possible to enter any text before, between, and after the coordinates, PRTG will parse latitude and longitude automatically; for example: 49.452778 11.077778 or enter 49.452778 any 11.077778 text A minus sign (-) in the first line will hide an object from geo maps. In this case you can enter location information in line two and following. You can define a specific label for each location: enter a string denoting the label in the first line and provide geo coordinates in the second line. This object will be displayed then with the label in PRTG's geo map.
Username
Password
Login
214
08.10.2013
Private Key
SSH Port
08.10.2013
215
Password
VMware Protocol
216
08.10.2013
Authentication Type
Password
Encryption Type
08.10.2013
217
Context Name
SNMP Port
SNMP Timeout (sec.)
Windows Compat ibilit y Opt ions When experiencing problems while monitoring via Windows sensors, you can set some compatibility options for trouble shooting. Preferred Data Source Define the method Windows sensors will use to query data. This setting is valid only for hybrid sensors offering performance counter and Windows Management Instrumentation (WMI) technology. The setting will be ignored for all other sensors! Choose between: Performance Count ers and fallback t o WMI (recommended): Try to query data via performance counters. If this is not possible, establish a connection via WMI. This is the recommended setting to best balance resource usage and functionality. Performance Count ers only : Query data via performance counters only. If this is not possible, a sensor will return no data. WMI only : Query data via WMI only. If this is not possible, a sensor will return no data. Timeout Method Specify the time the sensor will wait for the return of its WMI query before aborting it with an error message. Choose between:
218
08.10.2013
Windows Compat ibilit y Opt ions Use 1.5x scanning int erval (recommended): Use a default of one and a half times the scanning interval set for the sensor (see below in this settings). Set manually : Enter a timeout value manually. We recommend using the default value. Only if you experience ongoing timeout errors, try increasing the timeout value. Timeout Value (Sec.) This field is only visible if the manual timeout method is selected above. Specify the time the sensor will wait for the return of its WMI query before aborting with an error message. Please enter an integer value.
SNMP Compat ibilit y Opt ions 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. Define if an SNMP sensor will try again after a request fails. Ret ry (recommended): Try again if an SNMP request fails. This can help prevent false error messages due to temporary timeout failures. Do not ret ry : Do not retry if an SNMP request fails. With this setting enabled an SNMP sensor will be set to error status earlier. Overflow Values Define how PRTG will handle overflow values. Some devices do not handle internal buffer overflows correctly. This can cause false peaks. Ignore overflow values (recommended): Ignore overflow values and do not include them in the monitoring data. Handle overflow values as valid result s: Regard all overflow values as regular data and include them in the monitoring data. We recommend using the default value. If you experience problems, change this option. Zero Values Define how PRTG will handle zero values. Some devices send incorrect zero values. This can cause false peaks. Ignore zero values for delt a sensors (recommended): Ignore zero values and do not include them in the monitoring data.
Failed Requests
08.10.2013
219
SNMP Compat ibilit y Opt ions Handle zero values as valid result s for delt a sensors: Regard all zero values as regular data and include them in the monitoring data. We recommend using the default value. If you experience problems, change this option. 32-bit/64-bit Counters Define which kind of traffic counters PRTG will search for on a device. Use 64-bit count ers if available (recommended): The interface scan will use 64-bit traffic counters, if available. This can avoid buffer overflows in the devices. Use 32-bit count ers only : The interface scan will always use 32bit traffic counters, even if 64-bit counters are available. This can lead to more reliable monitoring for some devices. 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 mult i get (recommended): Bundle multiple SNMP requests into one request. Use single get : Use one request for each SNMP value. This can increase compatibility with older devices. We recommend using the default value. If you experience problems, change this option. Port Name Template Define how the name of SNMP sensors created on a device will be put together. Enter a template using several variables. When adding new sensors, PRTG scans the interface for available counters at certain OIDs. At each OID usually several fields are available with interface descriptions. They are different for every device/OID. PRTG will use the information in these fields to name the sensors. If a field is empty or not available, an empty string is added to the name. As default, ([port ]) [ifalias] is set as port name template, which will create a name such as (001) Ethernet1, for example. You can use any field names available at a certain OID of your device, among which are: [port ]: The port number of the monitored interface. [ifalias]: The 'alias' name for the monitored interface as specified by a network manager, providing a non-volatile handling. [ifname]: The textual name of the monitored interface as assigned by the local device. [ifindex]: A unique value, greater than zero, for the monitored interface.
220
08.10.2013
SNMP Compat ibilit y Opt ions [ifdescr]: A textual string containing information about the monitored device or interface, for example, manufacturer, product name, version. [ifspeed]: An estimate of the monitored interface's current bandwidth (KBit/s). Combine them as you like to obtain suitable sensor names. See the More section below for more information about SNMP sensor names. Port Name Update Define how PRTG will react if you change port names in your physical device (e.g. a switch or router). Choose between: Keep port names (use t his if y ou edit t he names in PRTG): Do not automatically adjust sensor names. This is the best option if you want to change names in PRTG manually. Aut omat ic sensor name updat e if name changes in device: If PRTG detects changes of port names in your physical device, it will try to automatically adjust sensor names accordingly. For detailed information please see More section below. Port Identification Define which field will be used for SNMP interface identification. Choose between: Aut omat ic (recommended): Tries the ifAlias field first to identify an SNMP interface and then ifDescr. Note: ifName will not be tried automatically. Use ifAlias: For most devices ifAlias is the best field to get unique interface names. Use ifDescr: Use this option if the port order of your device changes after a reboot, and there is no ifAlias field available. For example, this is the best option for Cisco ASA devices. Note: When using this option it is important that your device returns unique interface names in the ifDescr field. Use ifName: You can also use this option if there is no unique ifAlias available. Note: When using this option it is important that your device returns unique interface names in the ifName field. No Port Updat e: Use this option to disable automatic port identification. 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. 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.
End Port
08.10.2013
221
SNMP Compat ibilit y Opt ions SNMP Debug Log Define if you want to create an SNMP log file for debugging purposes. This is only recommended for debugging low level SNMP issues. Choose between: No log (recommended): No SNMP debug log file will be created. Enable debug log : An SNMP log file is written to the Logs (Debug) directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Proxy Set t ings for HTTP Sensors HTTP Proxy Settings The proxy settings determine how a sensor connects to a given URL. You can enter data for a proxy server that will be used when connecting via HTTP or HTTPS. Note: This setting is valid for the monitoring only and determines the behavior of sensors. In order to change proxy settings for the core server, please see Sy st em Administ rat ionSy st em and Websit e 1698 . Enter the IP address or DNS name of the proxy server to use. If you leave this field empty, no proxy will be used. Enter the port number of the proxy. Often, port 8080 is used. Please enter an integer value. 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. 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.
Name
Port
User
Password
Scanning Int erval 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 1691 .
222
08.10.2013
Schedules, Dependencies, and Maint enance Window Schedule Select a schedule from the list. Schedules can be used to pause monitoring for a certain time span (days, hours) throughout the week. You can create new schedules and edit existing ones in the account settings 1678 . Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active. Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between: Not set (monit or cont inuously ): No maintenance window will be set. Set up a one-t ime maint enance window: Pause monitoring within a maintenance window. Maintenance Begins At This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window. This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window. , Group Settings , Device
Maintenance Window
Maintenance End At
Dependency settings are available only in Probe Settings Settings 261 , and Sensor Settings 278 .
227
242
08.10.2013
223
Access Right s User Group Access Define which user group(s) will have access to the object you're editing. A table with user groups and right is shown; it contains all user groups from your setup. For each user group you can choose from the following access rights: Inherit ed: Use the settings of the parent object. None: Users in this group cannot see or edit the object. The object does not show up in lists and in the device tree. Exception: If a child object is visible to the user, the object is visible in the device tree, though not accessible. Read: Users in this group can see the object and review its monitoring results. Writ e: Users in this group can see the object, review its monitoring results, and edit the object's settings. They cannot edit access rights settings. Full: Users in this group can see the object, review its monitoring results, edit the object's settings, and edit access rights settings. You can create new user groups in the Sy st em Administ rat ion User Groups 1715 settings. To automatically set all objects further down in the hierarchy to inherit this object's access rights, set a check mark for the Revert children's access right s t o inherit ed option. For more details about access rights, please see section User Access Right s 89 .
Channel Unit Configurat ion Channel Unit Types For each type of sensor channel, define the unit in which data is displayed. If defined on probe, group, or device level, these settings can be inherited to all sensors underneath. You can set units for the following channel types (if available): Bandwidt h Memory Disk File Cust om Note: Custom channel types can be set on sensor level only.
224
08.10.2013
Unusual Det ect ion Unusual Detection Define if unusual detection is enabled for sensors. You can configure the behavior of unusual detection, or disable it completely, in the system settings 1696 . Enabled: Enable unusual detection for this group. Sensors in this group will turn to orange color if unusual activity is detected. Disabled: Disable unusual detection for this group. Unusual values will be ignored for sensors in this group; they will not show an unusual sensor status.
Similar Sensors Det ect ion Similar Sensors Detection Define if similar sensors detection is enabled for sensors. You can configure the depth of analysis of similar sensors detection, or disable it completely, in the system settings 1697 . Enabled: Enable similar sensors detection for this group. Sensors in this group will be considered during similarity analysis. Disabled: Disable similar detection for this group. Sensors in this group will not be taken into account during similarity analysis. Click on the Save button to store your settings. If you change tabs or use the main menu, all changes to the settings will be lost!
Notifications
The status or the data of a sensor can trigger notifications. Using this mechanism, you can configure external alerting tailored to you needs. In an object's detail page, click on the Not ificat ions tab to change sensor notification triggers. The defined triggers will be inherited down to sensor level. For detailed information, please see Sensor Not ificat ions Set t ings 1573 section.
Others
For more general information about settings, please see Object Set t ings
133
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?
08.10.2013
225
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
226
08.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 5 Probe Settings
6.5
Probe Settings
On a probe's overview page, click on the Set t ings tab to change settings.
Add Remote Probe

You can add additional remote probes to your setup to extend you monitoring to networks that are not directly reachable by your PRTG core installation or cluster. See Add Remot e Probe
1887
section for more details.
Probe Settings
The following settings are available in the Set t ings tab of every probe. As you may not need all of these for every probe, just regard those settings you really need, ignoring the others. We recommend defining as many settings as possible in the Root them to all other objects further down in the tree hierarchy.
213
group, so you can inherit
Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default.
Basic Probe Set t ings 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. Choose if monitoring for this probe is started or paused. St art ed: Monitor this probe. Paused: Pause monitoring for this probe. All sensors on all devices on this probe will be paused until this setting is changed again. 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. 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).
Status
Priority
08.10.2013
227
Inherited Settings
By default, all following settings are inherited from objects higher in the hierarchy and should be changed there, if necessary. Often, best practice is to change them centrally in the Root 213 group's settings. To change a setting for this object, disable inheritance by clicking on the check mark symbol in front of the respective setting name. You will then see the options described below. Locat ion Location (for geo maps) When using geo maps using Google's API 1603 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 115 (green - yellow - orange - red). You can enter a full postal address, city and country only, or latitude and longitude. It is possible to enter any text before, between, and after the coordinates, PRTG will parse latitude and longitude automatically; for example: 49.452778 11.077778 or enter 49.452778 any 11.077778 text A minus sign (-) in the first line will hide an object from geo maps. In this case you can enter location information in line two and following. You can define a specific label for each location: enter a string denoting the label in the first line and provide geo coordinates in the second line. This object will be displayed then with the label in PRTG's geo map.
Username
Password
228
08.10.2013
Login
Private Key
For WBEM Use Protocol Define the protocol that will be used for WBEM. This setting is only relevant when using WBEM sensors. Choose between: HTTP: Use an unencrypted connection for WBEM. HTTPS : Use an SSL-encrypted connection for WBEM. For WBEM Use Port Define the port that will be used for WBEM. This setting is only relevant when using WBEM sensors. Choose between: Set aut omat ically (port 5988 or 5989): Use one of the standard ports, depending on whether unencrypted or encrypted connection is chosen above. Set manually : Use a custom port. Define below. WBEM Port This setting is only visible if manual port selection is enabled above. Enter the WBEM port number. Define the port number which will be used for SSH connections. Note: By default, this setting is automatically used for all SSH sensors 284 , unless you define a different port number in the sensor settings.
SSH Port
08.10.2013
229
Credent ials for Linux/Solaris/Mac OS (SSH/WBEM) Sy st ems SSH Rights Elevation Define with which rights the command will be executed on the target system. Choose between: Run t he command as t he user connect ing (default ): Use the rights of the user who establishes the SSH connection. Run t he command as anot her user using 'sudo': Use the rights of another user, for example, the administrator. Run t he command as anot her user using 'su': Use the rights of another target user. Target Username This field is only visible if sudo or su is enabled above. Enter a username to run the specified command as another user than root. If you leave this field empty, the command will be run as root. Ensure that you set the Linux password even you use a public/ private key for authentication. This is not necessary if the user is allowed to execute the command without a password. This field is only visible if su is enabled above. Enter the password for the specified target user.
Password
VMware Protocol
Credent ials 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.
230
08.10.2013
Credent ials for SNMP 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. This setting is only visible if SNMP version v3 is enabled above. Choose between: MD5: Use Message-Digest Algorithm 5 (MD5) for authentication. SHA: Use Secure Hash Algorithm (SHA) for authentication. The chosen type has to match the authentication type of your device. Note: If you do not want to use authentication, but you need SNMP v3, for example, because your device requires context, you can leave the field password empty. In this case, SNMP_SEC_LEVEL_NOAUTH will be used and authentication will be deactivated entirely. User This setting is only visible if SNMP version v3 is enabled above. Enter a username for secure authentication. This value has to match the username of your device. This setting is only visible if SNMP version v3 is enabled above. Enter a password for secure authentication. This value has to match the password of your device. This setting is only visible if SNMP version v3 is enabled above. Select an encryption type. Choose between: DES : Use Data Encryption Standard (DES) as encryption algorithm.
Authentication Type
Password
Encryption Type
08.10.2013
231
Credent ials for SNMP Devices AES : Use Advanced Encryption Standard (AES) as encryption algorithm. The chosen type has to match the encryption type of your device. Data Encryption Key This setting is only visible if SNMP version v3 is enabled above. Enter an encryption key here. If you provide a key in this field, SNMP data packets will be encrypted using the encryption algorithm selected above, providing increased security. The provided key here has to match the encryption key of your device. Note: If the key entered in this field does not match the key configured in the target SNMP device, you will not get an error message! Please enter a string or leave the field empty. This setting is only visible if SNMP version v3 is enabled above. Enter a context name only if it is required by the configuration of the device. Context is a collection of management information accessible by an SNMP device. Please enter a string. Enter the port used for SNMP communication. We recommend using the default value. 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.
Context Name
SNMP Port
SNMP Timeout (sec.)
Windows Compat ibilit y Opt ions When experiencing problems while monitoring via Windows sensors, you can set some compatibility options for trouble shooting. Preferred Data Source Define the method Windows sensors will use to query data. This setting is valid only for hybrid sensors offering performance counter and Windows Management Instrumentation (WMI) technology. The setting will be ignored for all other sensors! Choose between: Performance Count ers and fallback t o WMI (recommended): Try to query data via performance counters. If this is not possible, establish a connection via WMI. This is the recommended setting to best balance resource usage and functionality. Performance Count ers only : Query data via performance counters only. If this is not possible, a sensor will return no data. WMI only : Query data via WMI only. If this is not possible, a sensor will return no data.
232
08.10.2013
Windows Compat ibilit y Opt ions Timeout Method Specify the time the sensor will wait for the return of its WMI query before aborting it with an error message. Choose between: Use 1.5x scanning int erval (recommended): Use a default of one and a half times the scanning interval set for the sensor (see below in this settings). Set manually : Enter a timeout value manually. We recommend using the default value. Only if you experience ongoing timeout errors, try increasing the timeout value. Timeout Value (Sec.) This field is only visible if the manual timeout method is selected above. Specify the time the sensor will wait for the return of its WMI query before aborting with an error message. Please enter an integer value.
SNMP Compat ibilit y Opt ions 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. Define if an SNMP sensor will try again after a request fails. Ret ry (recommended): Try again if an SNMP request fails. This can help prevent false error messages due to temporary timeout failures. Do not ret ry : Do not retry if an SNMP request fails. With this setting enabled an SNMP sensor will be set to error status earlier. Overflow Values Define how PRTG will handle overflow values. Some devices do not handle internal buffer overflows correctly. This can cause false peaks. Ignore overflow values (recommended): Ignore overflow values and do not include them in the monitoring data. Handle overflow values as valid result s: Regard all overflow values as regular data and include them in the monitoring data. We recommend 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.
Failed Requests
08.10.2013
233
SNMP Compat ibilit y Opt ions Ignore zero values for delt a sensors (recommended): Ignore zero values and do not include them in the monitoring data. Handle zero values as valid result s for delt a sensors: Regard all zero values as regular data and include them in the monitoring data. We recommend using the default value. If you experience problems, change this option. 32-bit/64-bit Counters Define which kind of traffic counters PRTG will search for on a device. Use 64-bit count ers if available (recommended): The interface scan will use 64-bit traffic counters, if available. This can avoid buffer overflows in the devices. Use 32-bit count ers only : The interface scan will always use 32bit traffic counters, even if 64-bit counters are available. This can lead to more reliable monitoring for some devices. 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 mult i get (recommended): Bundle multiple SNMP requests into one request. Use single get : Use one request for each SNMP value. This can increase compatibility with older devices. We recommend using the default value. If you experience problems, change this option. Port Name Template Define how the name of SNMP sensors created on a device will be put together. Enter a template using several variables. When adding new sensors, PRTG scans the interface for available counters at certain OIDs. At each OID usually several fields are available with interface descriptions. They are different for every device/OID. PRTG will use the information in these fields to name the sensors. If a field is empty or not available, an empty string is added to the name. As default, ([port ]) [ifalias] is set as port name template, which will create a name such as (001) Ethernet1, for example. You can use any field names available at a certain OID of your device, among which are: [port ]: The port number of the monitored interface. [ifalias]: The 'alias' name for the monitored interface as specified by a network manager, providing a non-volatile handling. [ifname]: The textual name of the monitored interface as assigned by the local device.
234
08.10.2013
SNMP Compat ibilit y Opt ions [ifindex]: A unique value, greater than zero, for the monitored interface. [ifdescr]: A textual string containing information about the monitored device or interface, for example, manufacturer, product name, version. [ifspeed]: An estimate of the monitored interface's current bandwidth (KBit/s). Combine them as you like to obtain suitable sensor names. See the More section below for more information about SNMP sensor names. Port Name Update Define how PRTG will react if you change port names in your physical device (e.g. a switch or router). Choose between: Keep port names (use t his if y ou edit t he names in PRTG): Do not automatically adjust sensor names. This is the best option if you want to change names in PRTG manually. Aut omat ic sensor name updat e if name changes in device: If PRTG detects changes of port names in your physical device, it will try to automatically adjust sensor names accordingly. For detailed information please see More section below. Port Identification Define which field will be used for SNMP interface identification. Choose between: Aut omat ic (recommended): Tries the ifAlias field first to identify an SNMP interface and then ifDescr. Note: ifName will not be tried automatically. Use ifAlias: For most devices ifAlias is the best field to get unique interface names. Use ifDescr: Use this option if the port order of your device changes after a reboot, and there is no ifAlias field available. For example, this is the best option for Cisco ASA devices. Note: When using this option it is important that your device returns unique interface names in the ifDescr field. Use ifName: You can also use this option if there is no unique ifAlias available. Note: When using this option it is important that your device returns unique interface names in the ifName field. No Port Updat e: Use this option to disable automatic port identification. 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.
08.10.2013
235
SNMP Compat ibilit y Opt ions 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. Define if you want to create an SNMP log file for debugging purposes. This is only recommended for debugging low level SNMP issues. Choose between: No log (recommended): No SNMP debug log file will be created. Enable debug log : An SNMP log file is written to the Logs (Debug) directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
SNMP Debug Log
Name
Port
User
Password
236
08.10.2013
Clust er Usage Scanning Distribution This box is only visible if you're running a PRTG cluster. Sometimes you want to exclude a certain node from monitoring the sensors running on this probe, group, or device, for example, if a device is not reachable from every node configured in your cluster. In the list of cluster nodes, please select the nodes that will not be included in sensor scans. By default, this setting is inherited 82 to all objects underneath.
Schedules, Dependencies, and Maint enance Window Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings. Schedule 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 1678 . Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active. Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between: Not set (monit or cont inuously ): No maintenance window will be set. Set up a one-t ime maint enance window: Pause monitoring within a maintenance window. Maintenance Begins At This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window. This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window. 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.
Maintenance Window
Maintenance Ends At
Dependency Type
08.10.2013
237
Schedules, Dependencies, and Maint enance Window Select object : Pause the current object if its parent object is in a Down status, or if it is paused by another dependency. Additionally, pause the current object if a specific other object in the device tree is in a Down status, or if it is paused by another dependency. Select below. Note: Testing your dependencies is easy! Simply choose Simulat e Error St at us from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused. Dependency This field is only visible if the select object option is enabled above. Click on the reading-glass symbol and use the object selector 143 to choose an object on which the current object will be dependent on. Define a time span. After the master object for this dependency comes back to an Up status, monitoring of the depending objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds.
Delay (Seconds)
238
08.10.2013
08.10.2013
239
Notifications
Others
133
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?
240
08.10.2013
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
08.10.2013
241
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 6 Group Settings
6.6
Group Settings
On a group's overview page, click on the Set t ings tab to change settings.
Add Group
The Add Group dialog appears when adding a new group to a parent group. It only shows the setting fields that are imperative for creating the group. Therefore, you will not see all setting fields in this dialog. For example, the Group St at us option is not available in this step. You can change all settings in the group's Set t ings tab later.
Group Settings
The following settings are available in the Set t ings tab of every group. As you may not need all of these for every group, just regard those settings you really need, ignoring the others. Note: This documentation does not refer to the setting of the special Root group. The settings available there differ from those described here. We recommend defining as many settings as possible in the Root them to all other objects further down in the tree hierarchy.
213
Basic Group Set t ings 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. Choose if monitoring for this group is started or paused. St art ed: Monitor this group. Paused: Pause monitoring for this group. All sensors on all devices in this group will be paused until this setting is changed again. Tags 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.
Status
242
08.10.2013
Basic Group Set t ings 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 Ty pe Sensor Management Select which type of auto-discovery you would like to perform for this group. Choose between: Manual (no aut o-discovery ): Do not auto-discover any sensors, but only add sensors manually. Aut omat ic device ident ificat ion (st andard, recommended): Use a small set of auto-discovery templates. This will scan your LAN and usually create a view standard sensors on your device. Aut omat ic device ident ificat ion (det ailed, may creat e many sensors: Use an extended set of auto-discovery templates. This will scan your LAN and usually create many sensors on your device. Aut omat ic sensor creat ion using specific device t emplat es: Use specific auto-discovery templates only. Please select templates below. This will scan your LAN and add sensors defined in the template.
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, Det ailed) HTTP Web Server Hy per V Host Server Linux/UNIX Device (SNMP or SSH enabled) Localhost RDP Mail Server (Generic)
08.10.2013
243
Mail Server (MS Exchange 2003) Mail Server (MS Exchange 2007) Misc. Det ails Print er (HP) Server (Compaq/HP agent s) Swit ch (Cisco Cat aly st ) Swit ch (Cisco IOS Based) Swit ch (HP Procurve) UNIX /Linux Device UPS (APC) VMware ESX Server Windows (Det ailed via WMI) Windows (via WMI) Windows IIS (via SNMP) X EN 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 148 . Hourly : Perform auto-discovery for new devices and sensors every 60 minutes. Note: Please use this option with caution! Frequently executed auto-discoveries might cause performance issues, especially when large network segments are scanned every hour. Daily : Perform auto-discovery for new devices and sensors every 24 hours. The first auto-discovery will run immediately, all other discoveries will start on the time defined in the Aut o-Discovery Set t ings section of the Sy st em Administ rat ionSy st em and Websit e 1691 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 Aut oDiscovery Set t ings section of the Sy st em Administ rat ion Sy st em and Websit e 1691 settings. IP Selection Method Define how you want to define the IP range for auto-discovery. Choose between: Class C base IP wit h st art /end (IPv4): Define an IPv4 class C address range.
244
08.10.2013
List of individual IPs and DNS names (IPv4): Enter a list of individual IPv4 addresses or DNS names. IP and subnet (IPv4): Enter an IPv4 address and subnet mask. IP wit h oct et range (IPv4): Enter an IPv4 address range for every IP octet individually. With this, you can define very customizable IP ranges. List of individual IPs and DNS names (IPv6): Enter a list of individual IPv6 addresses or DNS names. Use comput ers from t he act ive direct ory (maximum 1000 comput ers): Search in the active directory for computers to perform auto-discovery. Note: 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 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. 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. 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. 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 Range Start
IP Range End
IP List
IP and Subnet
08.10.2013
245
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. This field is only visible if active directory is selected above. Enter an organizational unit (OU) to restrict the active directory search to computers which are part of this OU. Just enter the name of the OU without any other term (i.e., without "OU" in front). If you leave this field empty, there will not be any restriction. If you have sub-OUs, too, please consider the correct syntax in the format Y,OU=X : OUs that are part of another OU have to be listed together with their parent(s). Enter the sub-OU followed by ,OU= and the name of the parent OU. For example, assuming that the organizational unit 'Y' is part of the OU named 'X'. Then the syntax would be Y,OU=X. For three OUs 'X', 'Y' part of 'X', and 'Z' part of 'Y', the syntax would be Z,OU=Y,OU=X. Note that the order is important, sub-OUs have to be listed left of its according parents!
Organizational Unit
Name Resolution
Define how newly discovered devices will be monitored. This only affects new devices. The setting for existing devices will be kept. Choose between: Use DNS / WMI / SNMP names (recommended): Monitor newly discovered devices via their DNS, WMI, or SNMP names (if available). Use IP addresses: Monitor newly discovered devices via their IP address. We recommend using the default value.
Device Rescan
Define if you want to rescan known devices. Choose between: Skip aut o-discovery for known devices/IPs (recommended): Do not re-scan known devices or IP addresses, but only scan for new devices/IPs when auto-discovering. This can avoid recreation of manually deleted sensors. PRTG will also avoid adding devices that are already included elsewhere in your configuration, e.g. in other groups. Perform aut o-discovery for known devices/IPs: Re-scan known devices and IP addresses with every auto-discovery. This will re-create manually deleted sensors on existing devices. We recommend using the default value.
246
08.10.2013
Inherited Settings
Username
Password
08.10.2013
247
Login
Private Key
For WBEM Use Protocol Define the protocol that will be used for WBEM. This setting is only relevant when using WBEM sensors. Choose between: HTTP: Use an unencrypted connection for WBEM. HTTPS : Use an SSL-encrypted connection for WBEM. For WBEM Use Port Define the port that will be used for WBEM. This setting is only relevant when using WBEM sensors. Choose between: Set aut omat ically (port 5988 or 5989): Use one of the standard ports, depending on whether unencrypted or encrypted connection is chosen above. Set manually : Use a custom port. Define below. WBEM Port This setting is only visible if manual port selection is enabled above. Enter the WBEM port number. Define the port number which will be used for SSH connections. Note: By default, this setting is automatically used for all SSH sensors 284 , unless you define a different port number in the sensor settings.
SSH Port
248
08.10.2013
Credent ials for Linux/Solaris/Mac OS (SSH/WBEM) Sy st ems SSH Rights Elevation Define with which rights the command will be executed on the target system. Choose between: Run t he command as t he user connect ing (default ): Use the rights of the user who establishes the SSH connection. Run t he command as anot her user using 'sudo': Use the rights of another user, for example, the administrator. Run t he command as anot her user using 'su': Use the rights of another target user. Target Username This field is only visible if sudo or su is enabled above. Enter a username to run the specified command as another user than root. If you leave this field empty, the command will be run as root. Ensure that you set the Linux password even you use a public/ private key for authentication. This is not necessary if the user is allowed to execute the command without a password. This field is only visible if su is enabled above. Enter the password for the specified target user.
Password
VMware Protocol
Credent ials 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.
08.10.2013
249
Credent ials for SNMP 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. This setting is only visible if SNMP version v3 is enabled above. Choose between: MD5: Use Message-Digest Algorithm 5 (MD5) for authentication. SHA: Use Secure Hash Algorithm (SHA) for authentication. The chosen type has to match the authentication type of your device. Note: If you do not want to use authentication, but you need SNMP v3, for example, because your device requires context, you can leave the field password empty. In this case, SNMP_SEC_LEVEL_NOAUTH will be used and authentication will be deactivated entirely. User This setting is only visible if SNMP version v3 is enabled above. Enter a username for secure authentication. This value has to match the username of your device. This setting is only visible if SNMP version v3 is enabled above. Enter a password for secure authentication. This value has to match the password of your device. This setting is only visible if SNMP version v3 is enabled above. Select an encryption type. Choose between: DES : Use Data Encryption Standard (DES) as encryption algorithm.
Authentication Type
Password
Encryption Type
250
08.10.2013
Credent ials for SNMP Devices AES : Use Advanced Encryption Standard (AES) as encryption algorithm. The chosen type has to match the encryption type of your device. Data Encryption Key This setting is only visible if SNMP version v3 is enabled above. Enter an encryption key here. If you provide a key in this field, SNMP data packets will be encrypted using the encryption algorithm selected above, providing increased security. The provided key here has to match the encryption key of your device. Note: If the key entered in this field does not match the key configured in the target SNMP device, you will not get an error message! Please enter a string or leave the field empty. This setting is only visible if SNMP version v3 is enabled above. Enter a context name only if it is required by the configuration of the device. Context is a collection of management information accessible by an SNMP device. Please enter a string. Enter the port used for SNMP communication. We recommend using the default value. 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.
Context Name
SNMP Port
SNMP Timeout (sec.)
Windows Compat ibilit y Opt ions When experiencing problems while monitoring via Windows sensors, you can set some compatibility options for trouble shooting. Preferred Data Source Define the method Windows sensors will use to query data. This setting is valid only for hybrid sensors offering performance counter and Windows Management Instrumentation (WMI) technology. The setting will be ignored for all other sensors! Choose between: Performance Count ers and fallback t o WMI (recommended): Try to query data via performance counters. If this is not possible, establish a connection via WMI. This is the recommended setting to best balance resource usage and functionality. Performance Count ers only : Query data via performance counters only. If this is not possible, a sensor will return no data. WMI only : Query data via WMI only. If this is not possible, a sensor will return no data.
08.10.2013
251
Windows Compat ibilit y Opt ions Timeout Method Specify the time the sensor will wait for the return of its WMI query before aborting it with an error message. Choose between: Use 1.5x scanning int erval (recommended): Use a default of one and a half times the scanning interval set for the sensor (see below in this settings). Set manually : Enter a timeout value manually. We recommend using the default value. Only if you experience ongoing timeout errors, try increasing the timeout value. Timeout Value (Sec.) This field is only visible if the manual timeout method is selected above. Specify the time the sensor will wait for the return of its WMI query before aborting with an error message. Please enter an integer value.
SNMP Compat ibilit y Opt ions 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. Define if an SNMP sensor will try again after a request fails. Ret ry (recommended): Try again if an SNMP request fails. This can help prevent false error messages due to temporary timeout failures. Do not ret ry : Do not retry if an SNMP request fails. With this setting enabled an SNMP sensor will be set to error status earlier. Overflow Values Define how PRTG will handle overflow values. Some devices do not handle internal buffer overflows correctly. This can cause false peaks. Ignore overflow values (recommended): Ignore overflow values and do not include them in the monitoring data. Handle overflow values as valid result s: Regard all overflow values as regular data and include them in the monitoring data. We recommend 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.
Failed Requests
252
08.10.2013
SNMP Compat ibilit y Opt ions Ignore zero values for delt a sensors (recommended): Ignore zero values and do not include them in the monitoring data. Handle zero values as valid result s for delt a sensors: Regard all zero values as regular data and include them in the monitoring data. We recommend using the default value. If you experience problems, change this option. 32-bit/64-bit Counters Define which kind of traffic counters PRTG will search for on a device. Use 64-bit count ers if available (recommended): The interface scan will use 64-bit traffic counters, if available. This can avoid buffer overflows in the devices. Use 32-bit count ers only : The interface scan will always use 32bit traffic counters, even if 64-bit counters are available. This can lead to more reliable monitoring for some devices. 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 mult i get (recommended): Bundle multiple SNMP requests into one request. Use single get : Use one request for each SNMP value. This can increase compatibility with older devices. We recommend using the default value. If you experience problems, change this option. Port Name Template Define how the name of SNMP sensors created on a device will be put together. Enter a template using several variables. When adding new sensors, PRTG scans the interface for available counters at certain OIDs. At each OID usually several fields are available with interface descriptions. They are different for every device/OID. PRTG will use the information in these fields to name the sensors. If a field is empty or not available, an empty string is added to the name. As default, ([port ]) [ifalias] is set as port name template, which will create a name such as (001) Ethernet1, for example. You can use any field names available at a certain OID of your device, among which are: [port ]: The port number of the monitored interface. [ifalias]: The 'alias' name for the monitored interface as specified by a network manager, providing a non-volatile handling. [ifname]: The textual name of the monitored interface as assigned by the local device.
08.10.2013
253
SNMP Compat ibilit y Opt ions [ifindex]: A unique value, greater than zero, for the monitored interface. [ifdescr]: A textual string containing information about the monitored device or interface, for example, manufacturer, product name, version. [ifspeed]: An estimate of the monitored interface's current bandwidth (KBit/s). Combine them as you like to obtain suitable sensor names. See the More section below for more information about SNMP sensor names. Port Name Update Define how PRTG will react if you change port names in your physical device (e.g. a switch or router). Choose between: Keep port names (use t his if y ou edit t he names in PRTG): Do not automatically adjust sensor names. This is the best option if you want to change names in PRTG manually. Aut omat ic sensor name updat e if name changes in device: If PRTG detects changes of port names in your physical device, it will try to automatically adjust sensor names accordingly. For detailed information please see More section below. Port Identification Define which field will be used for SNMP interface identification. Choose between: Aut omat ic (recommended): Tries the ifAlias field first to identify an SNMP interface and then ifDescr. Note: ifName will not be tried automatically. Use ifAlias: For most devices ifAlias is the best field to get unique interface names. Use ifDescr: Use this option if the port order of your device changes after a reboot, and there is no ifAlias field available. For example, this is the best option for Cisco ASA devices. Note: When using this option it is important that your device returns unique interface names in the ifDescr field. Use ifName: You can also use this option if there is no unique ifAlias available. Note: When using this option it is important that your device returns unique interface names in the ifName field. No Port Updat e: Use this option to disable automatic port identification. 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.
254
08.10.2013
SNMP Compat ibilit y Opt ions 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. Define if you want to create an SNMP log file for debugging purposes. This is only recommended for debugging low level SNMP issues. Choose between: No log (recommended): No SNMP debug log file will be created. Enable debug log : An SNMP log file is written to the Logs (Debug) directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
SNMP Debug Log
Name
Port
User
Password
08.10.2013
255
Schedules, Dependencies, and Maint enance Window Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings. Schedule 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 1678 . Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active. Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between: Not set (monit or cont inuously ): No maintenance window will be set. Set up a one-t ime maint enance window: Pause monitoring within a maintenance window. Maintenance Begins At This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window. This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window. 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.
Maintenance Window
Maintenance Ends At
Dependency Type
256
08.10.2013
Schedules, Dependencies, and Maint enance Window Select object : Pause the current object if its parent object is in a Down status, or if it is paused by another dependency. Additionally, pause the current object if a specific other object in the device tree is in a Down status, or if it is paused by another dependency. Select below. Note: Testing your dependencies is easy! Simply choose Simulat e Error St at us from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused. Dependency This field is only visible if the select object option is enabled above. Click on the reading-glass symbol and use the object selector 143 to choose an object on which the current object will be dependent on. Define a time span. After the master object for this dependency comes back to an Up status, monitoring of the depending objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds.
Delay (Seconds)
08.10.2013
257
258
08.10.2013
Similar Sensors Det ect ion Similar Sensors Detection Define if similar sensors detection is enabled for sensors. You can configure the depth of analysis of similar sensors detection, or disable it completely, in the system settings 1697 . Enabled: Enable similar sensors detection for this group. Sensors in this group will be considered during similarity analysis. Disabled: Disable similar detection for this group. Sensors in this group will not be taken into account during similarity analysis.
Number of Sensors Limit at ion Sensor Limit This setting allows the administrator to set a limit for the maximum number of sensors in this group. Subgroups are also included. If sensors exceed this limitation, they will be paused. This is of special interest for a Managed Service Provider (MSP). Choose between: Allow unlimit ed number of sensors: Disable a limitation of the number of sensors for this group. Any number of sensors can be added to this group. Limit number of sensors in t his group: Enables a limitation of the number of sensors for this group. Only a limited number of sensors can be added to this group. Maximum Number of Sensors This field is only visible if limitation is enabled above. Define how many sensors can be added to this group. Please enter an integer value.
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!
08.10.2013
259
Notifications
Others
133
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
260
08.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 7 Device Settings
6.7
Device Settings
On a device's details page, click on the Set t ings tab to change settings.
Add Device
The Add Device dialog appears when adding a new device to a group. It only shows the setting fields that are imperative for creating the device. Therefore, you will not see all setting fields in this dialog. For example, the Device St at us option is not available in this step. You can change all settings in the device's Set t ings tab later.
Device Settings
The following settings are available in the Set t ings tab of every device. As you may not need all of these for every device, just regard those settings you really need, ignoring the others. We recommend defining as many settings as possible in the Root them to all other objects further down in the tree hierarchy.
213
For device settings, there is also multi-edit available. This enables you to change properties of many devices at a time. For more details, please see Mult i-Edit List s 1595 section. Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default.
Basic Device Set t ings 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. Choose if monitoring for this device is started or paused. St art ed: Monitor this device. Paused: Pause monitoring for this device. All sensors on it will be paused until this setting is changed again. IP Version Define which IP protocol PRTG will use to connect to this device. The setting is valid for all sensors created on this device. Choose between: 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.
Status
08.10.2013
261
Basic Device Set t ings 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.) 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. Select a priority for the sensor. This setting determines where the sensor will be placed in sensor lists. Top priority will be at the top of a list. You can choose from one star (low priority) to five stars (top priority).
Tags
Priority
Addit ional Device Informat ion 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 277 section below. Specify a URL you would like to open directly when choosing Device Tools | Go To Service URL from the device's context menu 156 . 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.
Service URL
Device Ty pe Sensor Management Select which type of auto-discovery you would like to perform for this device. Choose between: Manual (no aut o-discovery ): Do not auto-discover any sensors, but only add sensors manually. Aut omat ic device ident ificat ion (st andard, recommended): Use a small set of auto-discovery templates. This will scan your LAN and usually create a view standard sensors on your device. Aut omat ic device ident ificat ion (det ailed, may creat e many sensors: Use an extended set of auto-discovery templates. This will scan your LAN and usually create many sensors on your device.
262
08.10.2013
Device Ty pe Aut omat ic sensor creat ion using specific device t emplat es: Use specific auto-discovery templates only. Please select templates below. This will scan your LAN and add sensors defined in the template. Discovery Schedule This option is only visible if one of the auto-discovery options is selected above. Define when the auto-discovery will be run. Choose between: Once: Perform auto-discovery only once. For existing devices, this will initiate a one-time sensor update for the current device. Hourly : Perform auto-discovery for new sensors every hour. 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, Det ailed) HTTP Web Server Hy per V Host Server Linux/UNIX Device (SNMP or SSH enabled) Mail Server (Generic) Mail Server (MS Exchange) NTP Server Print er (HP) RDP Server Server (Compaq/HP agent s) Swit ch (Cisco Cat aly st ) Swit ch (Cisco IOS Based)
08.10.2013
263
Device Ty pe Swit ch (HP Procurve) UNIX /Linux Device UPS (APC) Virt uozzo Server VMware ESX Server Windows (Det ailed via WMI) Windows (via WMI) Windows IIS (via SNMP) X EN Server
Inherited Settings
264
08.10.2013
Username
Password
Login
Private Key
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.
08.10.2013
265
Credent ials for Linux/Solaris/Mac OS (SSH/WBEM) Sy st ems HTTPS : Use an SSL-encrypted connection for WBEM. For WBEM Use Port Define the port that will be used for WBEM. This setting is only relevant when using WBEM sensors. Choose between: Set aut omat ically (port 5988 or 5989): Use one of the standard ports, depending on whether unencrypted or encrypted connection is chosen above. Set manually : Use a custom port. Define below. WBEM Port This setting is only visible if manual port selection is enabled above. Enter the WBEM port number. Define the port number which will be used for SSH connections. Note: By default, this setting is automatically used for all SSH sensors 284 , unless you define a different port number in the sensor settings. Define with which rights the command will be executed on the target system. Choose between: Run t he command as t he user connect ing (default ): Use the rights of the user who establishes the SSH connection. Run t he command as anot her user using 'sudo': Use the rights of another user, for example, the administrator. Run t he command as anot her user using 'su': Use the rights of another target user. Target Username This field is only visible if sudo or su is enabled above. Enter a username to run the specified command as another user than root. If you leave this field empty, the command will be run as root. Ensure that you set the Linux password even you use a public/ private key for authentication. This is not necessary if the user is allowed to execute the command without a password. This field is only visible if su is enabled above. Enter the password for the specified target user.
SSH Port
Credent ials for VMware/X enServer User Enter a login name for access to VMware and XEN servers. Usually, you will use credentials with administrator privileges. Enter a password for access to VMware and XEN servers. Usually, you will use credentials with administrator privileges.
Password
266
08.10.2013
Credent ials for VMware/X enServer VMware Protocol Define the protocol used for the connection to VMware and XenServer. Choose between: HTTPS (recommended): Use an SSL-encrypted connection to VMware and XenServers. HTTP: Use an unencrypted connection to VMware and XenServers.
Credent ials 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. This setting is only visible if SNMP version v3 is enabled above. Choose between: MD5: Use Message-Digest Algorithm 5 (MD5) for authentication. SHA: Use Secure Hash Algorithm (SHA) for authentication. The chosen type has to match the authentication type of your device.
Authentication Type
08.10.2013
267
Credent ials for SNMP Devices Note: If you do not want to use authentication, but you need SNMP v3, for example, because your device requires context, you can leave the field password empty. In this case, SNMP_SEC_LEVEL_NOAUTH will be used and authentication will be deactivated entirely. User This setting is only visible if SNMP version v3 is enabled above. Enter a username for secure authentication. This value has to match the username of your device. This setting is only visible if SNMP version v3 is enabled above. Enter a password for secure authentication. This value has to match the password of your device. This setting is only visible if SNMP version v3 is enabled above. Select an encryption type. Choose between: DES : Use Data Encryption Standard (DES) as encryption algorithm. AES : Use Advanced Encryption Standard (AES) as encryption algorithm. The chosen type has to match the encryption type of your device. Data Encryption Key This setting is only visible if SNMP version v3 is enabled above. Enter an encryption key here. If you provide a key in this field, SNMP data packets will be encrypted using the encryption algorithm selected above, providing increased security. The provided key here has to match the encryption key of your device. Note: If the key entered in this field does not match the key configured in the target SNMP device, you will not get an error message! Please enter a string or leave the field empty. This setting is only visible if SNMP version v3 is enabled above. Enter a context name only if it is required by the configuration of the device. Context is a collection of management information accessible by an SNMP device. Please enter a string. Enter the port used for SNMP communication. We recommend using the default value. 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.
Password
Encryption Type
Context Name
SNMP Port
SNMP Timeout (sec.)
268
08.10.2013
Windows Compat ibilit y Opt ions When experiencing problems while monitoring via Windows sensors, you can set some compatibility options for trouble shooting. Preferred Data Source Define the method Windows sensors will use to query data. This setting is valid only for hybrid sensors offering performance counter and Windows Management Instrumentation (WMI) technology. The setting will be ignored for all other sensors! Choose between: Performance Count ers and fallback t o WMI (recommended): Try to query data via performance counters. If this is not possible, establish a connection via WMI. This is the recommended setting to best balance resource usage and functionality. Performance Count ers only : Query data via performance counters only. If this is not possible, a sensor will return no data. WMI only : Query data via WMI only. If this is not possible, a sensor will return no data. Timeout Method Specify the time the sensor will wait for the return of its WMI query before aborting it with an error message. Choose between: Use 1.5x scanning int erval (recommended): Use a default of one and a half times the scanning interval set for the sensor (see below in this settings). Set manually : Enter a timeout value manually. We recommend using the default value. Only if you experience ongoing timeout errors, try increasing the timeout value. Timeout Value (Sec.) This field is only visible if the manual timeout method is selected above. Specify the time the sensor will wait for the return of its WMI query before aborting with an error message. Please enter an integer value.
SNMP Compat ibilit y Opt ions 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. Define if an SNMP sensor will try again after a request fails.
Failed Requests
08.10.2013
269
SNMP Compat ibilit y Opt ions Ret ry (recommended): Try again if an SNMP request fails. This can help prevent false error messages due to temporary timeout failures. Do not ret ry : Do not retry if an SNMP request fails. With this setting enabled an SNMP sensor will be set to error status earlier. Overflow Values Define how PRTG will handle overflow values. Some devices do not handle internal buffer overflows correctly. This can cause false peaks. Ignore overflow values (recommended): Ignore overflow values and do not include them in the monitoring data. Handle overflow values as valid result s: Regard all overflow values as regular data and include them in the monitoring data. We recommend using the default value. If you experience problems, change this option. Zero Values Define how PRTG will handle zero values. Some devices send incorrect zero values. This can cause false peaks. Ignore zero values for delt a sensors (recommended): Ignore zero values and do not include them in the monitoring data. Handle zero values as valid result s for delt a sensors: Regard all zero values as regular data and include them in the monitoring data. We recommend using the default value. If you experience problems, change this option. 32-bit/64-bit Counters Define which kind of traffic counters PRTG will search for on a device. Use 64-bit count ers if available (recommended): The interface scan will use 64-bit traffic counters, if available. This can avoid buffer overflows in the devices. Use 32-bit count ers only : The interface scan will always use 32bit traffic counters, even if 64-bit counters are available. This can lead to more reliable monitoring for some devices. 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 mult i get (recommended): Bundle multiple SNMP requests into one request. Use single get : Use one request for each SNMP value. This can increase compatibility with older devices.
270
08.10.2013
SNMP Compat ibilit y Opt ions 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 ]: The port number of the monitored interface. [ifalias]: The 'alias' name for the monitored interface as specified by a network manager, providing a non-volatile handling. [ifname]: The textual name of the monitored interface as assigned by the local device. [ifindex]: A unique value, greater than zero, for the monitored interface. [ifdescr]: A textual string containing information about the monitored device or interface, for example, manufacturer, product name, version. [ifspeed]: An estimate of the monitored interface's current bandwidth (KBit/s). Combine them as you like to obtain suitable sensor names. See the More section below for more information about SNMP sensor names. Port Name Update Define how PRTG will react if you change port names in your physical device (e.g. a switch or router). Choose between: Keep port names (use t his if y ou edit t he names in PRTG): Do not automatically adjust sensor names. This is the best option if you want to change names in PRTG manually. Aut omat ic sensor name updat e if name changes in device: If PRTG detects changes of port names in your physical device, it will try to automatically adjust sensor names accordingly. For detailed information please see More section below. Port Identification Define which field will be used for SNMP interface identification. Choose between:
08.10.2013
271
SNMP Compat ibilit y Opt ions Aut omat ic (recommended): Tries the ifAlias field first to identify an SNMP interface and then ifDescr. Note: ifName will not be tried automatically. Use ifAlias: For most devices ifAlias is the best field to get unique interface names. Use ifDescr: Use this option if the port order of your device changes after a reboot, and there is no ifAlias field available. For example, this is the best option for Cisco ASA devices. Note: When using this option it is important that your device returns unique interface names in the ifDescr field. Use ifName: You can also use this option if there is no unique ifAlias available. Note: When using this option it is important that your device returns unique interface names in the ifName field. No Port Updat e: Use this option to disable automatic port identification. Start Port For SNMP Traffic sensors, define at which port number PRTG will start to create sensors. Use 0 for automatic. We recommend using the default value. 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. Define if you want to create an SNMP log file for debugging purposes. This is only recommended for debugging low level SNMP issues. Choose between: No log (recommended): No SNMP debug log file will be created. Enable debug log : An SNMP log file is written to the Logs (Debug) directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
End Port
SNMP Debug Log
272
08.10.2013
Name
Port
User
Password
Schedules, Dependencies, and Maint enance Window Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings.
08.10.2013
273
Schedules, Dependencies, and Maint enance Window Schedule Select a schedule from the list. Schedules can be used to pause monitoring for a certain time span (days, hours) throughout the week. You can create new schedules and edit existing ones in the account settings 1678 . Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active. Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between: Not set (monit or cont inuously ): No maintenance window will be set. Set up a one-t ime maint enance window: Pause monitoring within a maintenance window. Maintenance Begins At This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window. This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window. 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 Simulat e Error St at us from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused. Dependency This field is only visible if the select object option is enabled above. Click on the reading-glass symbol and use the object selector 143 to choose an object on which the current object will be dependent on.
Maintenance Window
Maintenance Ends At
Dependency Type
274
08.10.2013
Schedules, Dependencies, and Maint enance Window Delay (Seconds) Define a time span. After the master object for this dependency comes back to an Up status, monitoring of the depending objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds.
08.10.2013
275
Notifications
Others
133
section.
276
08.10.2013
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
08.10.2013
277
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings
6.8
Sensor Settings
There are more than 190 different sensor types available. In the Add Sensor dialog, all sensors are categorized into groups to help you quickly find what you need. Once youre 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 279 section. For sensor settings, there is also multi-edit available. This enables you to change properties of many sensors at a time. For more details, please see Mult i-Edit List s 1595 section.
Sensor Settings Overview

For information about sensor settings, please see the following sections: Sensor Set t ings
278
279
Addit ional Sensor Ty pes (Cust om Sensors) Sensor Channels Set t ings
1566
1563
1573
278
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 1 List of Available Sensor Types
6.8.1

This chapter lists all available sensors, arranged both by different categories and in alphabetical order. Note: In the Add a Sensor 209 assistant, PRTG offers you various options to filter for fitting sensor types easily. Common Sensors
279
Bandwidth Monitoring Sensors Web Servers (HTTP) Sensors SNMP Sensors

281 280
279
Windows WMI/Performance Counters Sensors Linux/Unix/OS X Sensors Virtual Servers Sensors Mail Servers Sensors
285 284 284
282
SQL Database Servers Sensors File Servers Sensors

285
285
Various Servers Sensors VoIP and QoS Sensors

287
286
Hardware Parameters Sensors Custom Sensors

288
287
PRTG Internal Sensors
288
All Sensors in Alphabetical Order More

294
289
Common Sensors
HTTP Sensor Ping Sensor Port Sensor
469
726
755
Port Range Sensor SNMP Traffic Sensor
762
1157
Windows Network Card Sensor
1341
Bandwidth Monitoring Sensors

AVM FRITZ!Box WAN Interface Sensor
316
11.10.2013
279
IPFIX Sensor
600
IPFIX (Custom) Sensor jFlow V5 Sensor

616
608
jFlow V5 (Custom) Sensor NetFlow V5 Sensor

652
624
NetFlow V5 (Custom) Sensor NetFlow V9 Sensor

668
660
NetFlow V9 (Custom) Sensor Packet Sniffer Sensor

692
676
Packet Sniffer (Custom) Sensor sFlow Sensor

822
699
sFlow (Custom) Sensor
830
SNMP Cisco ADSL Sensor
883
SNMP Cisco ASA VPN Traffic Sensor SNMP Library Sensor

1023
893
SNMP NetApp Network Interface Sensor SNMP RMON Sensor SNMP Traffic Sensor
1120
1087
1157
Windows Network Card Sensor
1341
Web Servers (HTTP) Sensors

Google Analytics Sensor HTTP Sensor
469 462
HTTP Advanced Sensor
476
HTTP Apache ModStatus PerfStats Sensor HTTP Apache ModStatus Totals Sensor HTTP Content Sensor
502 495
488
HTTP Full Web Page Sensor
511
HTTP SSL Certificate Expiry Sensor HTTP Transaction Sensor

524
518
HTTP XML/REST Value Sensor
533
Windows IIS Application Sensor
1315
280
11.10.2013
SNMP Sensors
SNMP APC Hardware Sensor SNMP Cisco ADSL Sensor
883 877
SNMP Cisco ASA VPN Connections Sensor SNMP Cisco ASA VPN Traffic Sensor SNMP Cisco CBQoS Sensor
898 893
888
SNMP Cisco System Health Sensor SNMP CPU Load Sensor SNMP Custom Sensor
914 909
903
SNMP Custom String Sensor SNMP Dell Hardware Sensor
921
929
SNMP Dell PowerEdge Physical Disk Sensor
935
SNMP Dell PowerEdge System Health Sensor SNMP Disk Free Sensor
947
941
SNMP GSA System Health Sensor SNMP Hardware Status Sensor

958
953
SNMP HP LaserJet Hardware Sensor
963
SNMP HP ProLiant Logical Disk Sensor
969
SNMP HP ProLiant Memory Controller Sensor SNMP HP ProLiant Network Interface Sensor SNMP HP ProLiant Physical Disk Sensor
987
975
981
SNMP HP ProLiant System Health Sensor SNMP IBM System X Logical Disk Sensor SNMP IBM System X Physical Disk Sensor
993
999
1005
SNMP IBM System X Physical Memory Sensor SNMP IBM System X System Health Sensor SNMP Library Sensor
1023 1017
1011
SNMP Linux Disk Free Sensor
1031
SNMP Linux Load Average Sensor SNMP Linux Meminfo Sensor

1044
1039
SNMP Linux Physical Disk Sensor SNMP Memory Sensor

1057
1049
SNMP NetApp Disk Free Sensor
1063
11.10.2013
281
SNMP NetApp Enclosure Sensor SNMP NetApp I/O Sensor

1075
1069
SNMP NetApp License Sensor
1081
SNMP NetApp Network Interface Sensor SNMP NetApp System Health Sensor SNMP Poseidon Environment Sensor SNMP QNAP Logical Disk Sensor SNMP QNAP Physical Disk Sensor
1104 1093
1087
1099
1109
SNMP QNAP System Health Sensor SNMP RMON Sensor

1120
1115
SNMP SonicWALL System Health Sensor SNMP SonicWALL VPN Traffic Sensor SNMP Synology Logical Disk Sensor SNMP Synology Physical Disk Sensor
1131
1126
1137
1142
SNMP Synology System Health Sensor SNMP System Uptime Sensor SNMP Traffic Sensor
1157 1152
1147
SNMP Trap Receiver Sensor
1164
Windows WMI/Performance Counters Sensors

Active Directory Replication Errors Sensor Event Log (Windows API) Sensor PerfCounter Custom Sensor
712 374 295
PerfCounter IIS Application Pool Sensor Windows CPU Load Sensor

1297
719
Windows Last Update Sensor
1322
Windows Logged In Users Sensor
1328
Windows MSMQ Queue Length Sensor Windows Print Queue Sensor Windows Registry Sensor
1367 1361
1334
Windows Scheduled Task Sensor
1375
Windows Updates Status (Powershell) Sensor WMI Custom Sensor

1394
1388
282
11.10.2013
WMI Custom String Sensor WMI Event Log Sensor

1410
1401
WMI Exchange Server Sensor
1417
WMI Exchange Transport Queue Sensor WMI File Sensor

1431
1424
WMI Free Disk Space (Multi Drive) Sensor WMI HDD Health Sensor
1445
1437
Windows IIS 6.0 SMTP Received Sensor Windows IIS 6.0 SMTP Sent Sensor WMI Logical Disk Sensor WMI Memory Sensor
1457 1451 1309
1303
WMI Microsoft SQL Server 2005 Sensor WMI Microsoft SQL Server 2008 Sensor WMI Microsoft SQL Server 2012 Sensor Windows Network Card Sensor Windows Pagefile Sensor
1348 1341
1462
1471
1479
Windows Physical Disk Sensor WMI Process Sensor

1487
1354
WMI Remote Ping Sensor
1493
WMI Security Center Sensor WMI Service Sensor WMI Share Sensor
1504
1498
1510
WMI SharePoint Process Sensor Windows System Uptime Sensor
1517
1382
WMI Terminal Services (Windows 2008) Sensor
1523
WMI Terminal Services (Windows XP/Vista/2003) Sensor WMI UTC Time Sensor
1533
1528
WMI Vital System Data (V2) Sensor WMI Volume Sensor

1544
1538
WMI Windows Version Sensor WSUS Statistics Sensor

1556
1550
11.10.2013
283
Linux/Unix/OS X Sensors
1031

1044
1039
SNMP Linux Physical Disk Sensor SSH Disk Free Sensor

1175
1049
SSH INodes Free Sensor
1184
SSH Load Average Sensor SSH Meminfo Sensor

1196
1190
SSH Remote Ping Sensor SSH Script Sensor

1209
1202
SSH Script Advanced Sensor WBEM Custom Sensor

1291
1218
Virtual Servers Sensors

Amazon CloudWatch Sensor Citrix XenServer Host Sensor
308
328
Citrix XenServer Virtual Machine Sensor Enterprise Virtual Array Sensor

367
334
Hyper-V Cluster Shared Volume Disk Free Sensor Hyper-V Host Server Sensor
551
544
Hyper-V Virtual Machine Sensor
557
Hyper-V Virtual Network Adapter Sensor Hyper-V Virtual Storage Device Sensor SCVMM Host Sensor
793 571
564
SCVMM Virtual Machine Sensor SSH VMWare ESX(i) Disk Sensor
800
1226
Virtuozzo Container Disk Sensor
1254
Virtuozzo Container Network Sensor
1260
VMware Host Hardware (WBEM) Sensor
1266
VMware Host Hardware Status (SOAP) Sensor VMware Host Performance (SOAP) Sensor
1278
1272
284
11.10.2013
VMware Virtual Machine (SOAP) Sensor
1284
Mail Servers Sensors

Exchange Backup (Powershell) Sensor
381
Exchange Database (Powershell) Sensor Exchange Mailbox (Powershell) Sensor
388
395
Exchange Mail Queue (Powershell) Sensor
402
Exchange Public Folder (Powershell) Sensor IMAP Sensor

577
408
IP on DNS Blacklist Sensor POP3 Sensor

743
594
POP3 Email Count Sensor SMTP Sensor

856
749
SMTP&IMAP Round Trip Sensor SMTP&POP3 Round Trip Sensor WMI Exchange Server Sensor
862
870
1417
WMI Exchange Transport Queue Sensor Windows IIS 6.0 SMTP Received Sensor Windows IIS 6.0 SMTP Sent Sensor
1309
1424
1303
SQL Database Servers Sensors

ADO SQL Sensor
301
Microsoft SQL Sensor MySQL Sensor

645
637
Oracle SQL Sensor
684
WMI Microsoft SQL Server 2005 Sensor WMI Microsoft SQL Server 2008 Sensor WMI Microsoft SQL Server 2012 Sensor
1462
1471
1479
File Servers Sensors

Dell PowerVault MDi Sensor File Sensor
432 348
11.10.2013
285
File Content Sensor Folder Sensor FTP Sensor

450 444
438
FTP Server File Count Sensor INI File Content Check Sensor
456
588
SFTP Secure File Transfer Protocol Sensor Share Disk Free Sensor
844
838
SNMP NetApp Disk Free Sensor SNMP NetApp Enclosure Sensor SNMP NetApp I/O Sensor
1075
1063
1069
1081
SNMP NetApp Network Interface Sensor SNMP NetApp System Health Sensor TFTP Sensor
1243 1093
1087
WMI File Sensor
1431
WMI Free Disk Space (Multi Drive) Sensor WMI Volume Sensor
1544
1437
Various Servers Sensors

DHCP Sensor DNS Sensor LDAP Sensor Ping Sensor
354
361
632
726
Ping Jitter Sensor Pingdom Sensor Port Sensor

755
732
737
Port Range Sensor RADIUS Sensor

783
762
RDP (Remote Desktop) Sensor SNMP Trap Receiver Sensor SNTP Sensor
1170 1164
788
Syslog Receiver Sensor
1232
Traceroute Hop Count Sensor
1249
286
11.10.2013
VoIP and QoS Sensors

Cisco IP SLA Sensor
322
SIP Options Ping Sensor
850
QoS (Quality of Service) One Way Sensor
771
QoS (Quality of Service) Round Trip Sensor
777
Hardware Parameter Sensors

Dell PowerVault MDi Sensor
348
Enterprise Virtual Array Sensor SNMP APC Hardware Sensor

877
367
SNMP Cisco System Health Sensor SNMP CPU Load Sensor

909
903
SNMP Dell Hardware Sensor
929
935
947
941
SNMP GSA System Health Sensor SNMP Hardware Status Sensor

958
953
963
987
975
981
SNMP HP ProLiant System Health Sensor SNMP IBM System X Physical Disk Sensor
993
1005
1023 1017
1011
SNMP Memory Sensor
1057
SNMP NetApp I/O Sensor
1075
SNMP NetApp Enclosure Sensor
1069
SNMP NetApp Network Interface Sensor SNMP NetApp System Health Sensor
1093
1087
11.10.2013
287
SNMP QNAP Physical Disk Sensor
1109
SNMP QNAP System Health Sensor
1115
SNMP SonicWALL System Health Sensor SNMP SonicWALL VPN Traffic Sensor SNMP Synology Physical Disk Sensor
1131
1126
1142
SNMP Synology System Health Sensor WMI HDD Health Sensor

1445
1147
Custom Sensors
EXE/Script Sensor
415
EXE/Script Advanced Sensor IPFIX (Custom) Sensor

608
424
jFlow V5 (Custom) Sensor
624
NetFlow V5 (Custom) Sensor NetFlow V9 (Custom) Sensor
660
676
Packet Sniffer (Custom) Sensor Pingdom Sensor

737
699
Sensor Factory Sensor sFlow (Custom) Sensor SNMP Custom Sensor
807
830
914
SNMP Custom String Sensor SSH Script Sensor

1209
921
WBEM Custom Sensor WMI Custom Sensor

1394
1291
WMI Custom String Sensor
1401
PRTG Internal Sensors

Core Health Sensor Probe Health Sensor
344
767
System Health Sensor
1239
288
11.10.2013
All Sensors in Alphabetical Order

The version numbers show when the respective sensor type was originally introduced to PRTG. Active Directory Replication Errors Sensor ADO SQL Sensor
301 295
(v8.3.0)
(v8.1.0)
308
Amazon CloudWatch Sensor
(v7)
316
AVM FRITZ!Box WAN Interface Sensor Cisco IP SLA Sensor

322
(v12.x.1)
(v7)
328
Citrix XenServer Host Sensor
(v12.x.1)
334
Citrix XenServer Virtual Machine Sensor Cluster Probe Health Sensor Core Health Sensor
344 340
(v8.1.0)
(v9.1.0)
(v9.1.0)
348
Dell PowerVault MDi Sensor DHCP Sensor DNS Sensor

354
(v12.x.1)
(v8.2.0)
361
(v7)
367
Enterprise Virtual Array Sensor
(v13.x.6) (v7)
381
Event Log (Windows API) Sensor
374
Exchange Backup (Powershell) Sensor
(v13.x.5)
388
Exchange Database (Powershell) Sensor Exchange Mailbox (Powershell) Sensor
(v13.x.5)
395
(v13.x.5)
402
Exchange Mail Queue (Powershell) Sensor
(v13.x.5) (v13.x.5)
Exchange Public Folder (Powershell) Sensor EXE/Script Sensor

415
408
(v7)
424
EXE/Script Advanced Sensor File Sensor

432
(v7)
(v7)
438
File Content Sensor Folder Sensor FTP Sensor

450 444
(v7)
(v7)
(v7)
456
FTP Server File Count Sensor Google Analytics Sensor HTTP Sensor
469 462
(v8.3.0)
(v12.x.1)
(v7)
476
HTTP Advanced Sensor
(v7)
488
HTTP Apache ModStatus PerfStats Sensor
(v12.x.3)
11.10.2013
289
HTTP Apache ModStatus Totals Sensor HTTP Content Sensor

502
495
(v12.x.3)
(v7)
511
HTTP Full Web Page Sensor
(v7)
518
HTTP SSL Certificate Expiry Sensor HTTP Transaction Sensor

524
(v8.3.0)
(v7)
533
HTTP XML/REST Value Sensor
(v8.3.0)
544
Hyper-V Cluster Shared Volume Disk Free Sensor Hyper-V Host Server Sensor
551
(v7)
(v7)
557
Hyper-V Virtual Machine Sensor
(v7)
564
Hyper-V Virtual Network Adapter Sensor Hyper-V Virtual Storage Device Sensor IMAP Sensor
577 571
(v9.1.0)
(v8.1.0)
(v7)
588
INI File Content Check Sensor IP on DNS Blacklist Sensor IPFIX Sensor
600 594
(v8.3.0)
(v8.3.0)
(v13.x.7)
608
IPFIX (Custom) Sensor jFlow V5 Sensor

616
(v13.x.7)
(v8.2.0)
624
jFlow V5 (Custom) Sensor LDAP Sensor

632
(v8.2.0)
(v8.1.0)
637
Microsoft SQL Sensor MySQL Sensor

645
(v7)
(v7)
652
NetFlow V5 Sensor
(v7)
660
NetFlow V5 (Custom) Sensor NetFlow V9 Sensor

668
(v7)
(v7)
676
NetFlow V9 (Custom) Sensor Oracle SQL Sensor

684
(v7)
(v7)
692
Packet Sniffer Sensor
(v7)
699
Packet Sniffer (Custom) Sensor
(v7)
706
Passive Application Performance Sensor PerfCounter Custom Sensor

712
(v13.x.4)
(v12.x.3)
719
PerfCounter IIS Application Pool Sensor Ping Sensor

726
(v12.x.6)
(v7)
732
Ping Jitter Sensor Pingdom Sensor 290
(v8.3.0) (v8.4.0)
737
11.10.2013
POP3 Sensor
743
(v7)
749
POP3 Email Count Sensor Port Sensor

755
(v8.3.0)
(v7)
762
Port Range Sensor
(v12.x.4) (v9.1.0)
771
Probe Health Sensor
767
QoS (Quality of Service) One Way Sensor
(v7)
777
QoS (Quality of Service) Round Trip Sensor RADIUS Sensor

783
(v9.1.0)
(v7)
788
RDP (Remote Desktop) Sensor SCVMM Host Sensor

793
(v7)
(v12.x.6)
800
SCVMM Virtual Machine Sensor Sensor Factory Sensor sFlow Sensor

822 807
(v12.x.6)
(v7)
(v7)
830
sFlow (Custom) Sensor
(v7)
838
SFTP Secure File Transfer Protocol Sensor Share Disk Free Sensor SIP Options Ping Sensor SMTP Sensor
856 844
(v12.x.6)
(v7) (v12.x.1)
850
(v7)
862
SMTP&IMAP Round Trip Sensor SMTP&POP3 Round Trip Sensor SNMP APC Hardware Sensor SNMP Cisco ADSL Sensor
883 877
(v7) (v7)
870
(v9.1.0)
(v12.x.1)
888
SNMP Cisco ASA VPN Connections Sensor SNMP Cisco ASA VPN Traffic Sensor SNMP Cisco CBQoS Sensor
898 893
(v12.x.1)
(v12.x.1)
(v13.x.5)
903
SNMP Cisco System Health Sensor SNMP CPU Load Sensor SNMP Custom Sensor
914 909
(v12.x.4)
(v12.x.4)
(v7)
921
SNMP Custom String Sensor SNMP Dell Hardware Sensor
(v9.1.0) (v7)
935
929
(v12.x.4) (v12.x.4)
947
941
(v12.x.4)
953
SNMP GSA System Health Sensor
(v13.x.5) 291
11.10.2013
SNMP Hardware Status Sensor
958
(v13.x.5)
963
(v9.1.0)
969
SNMP HP ProLiant Logical Disk Sensor
(v12.x.6)
975
987
(v12.x.6) (v12.x.4)
981
(v12.x.6) (v12.x.4) (v13.x.4) (v13.x.4)

1011
SNMP HP ProLiant System Health Sensor SNMP IBM System X Logical Disk Sensor SNMP IBM System X Physical Disk Sensor
993
999
1005
1023 1017
(v13.x.4)
(v13.x.4)
(v7)
1031
(v8.1.0)
1039

1044
(v8.1.0)
(v8.1.0)
1049
SNMP Linux Physical Disk Sensor SNMP Memory Sensor

1057
(v13.x.5)
(v12.x.4)
1063
SNMP NetApp Disk Free Sensor SNMP NetApp Enclosure Sensor SNMP NetApp I/O Sensor
1075
(v12.x.3) (v12.x.4)
1069
(v12.x.3)
1081
(v12.x.4)
1087
SNMP NetApp Network Interface Sensor SNMP NetApp System Health Sensor SNMP Poseidon Environment Sensor SNMP QNAP Logical Disk Sensor SNMP QNAP Physical Disk Sensor
1104 1093
(v12.x.3)
(v12.x.3) (v13.x.5)
1099
(v13.x.4) (v13.x.4) (v13.x.4)
1109
SNMP QNAP System Health Sensor SNMP RMON Sensor

1120
1115
(v12.x.1)
1126
SNMP SonicWALL System Health Sensor SNMP SonicWALL VPN Traffic Sensor SNMP Synology Logical Disk Sensor SNMP Synology Physical Disk Sensor
1131
(v13.x.5)
(v13.x.6) (v13.x.4) (v13.x.4) (v13.x.4)
1137
1142
SNMP Synology System Health Sensor SNMP System Uptime Sensor 292
1152
1147
(v7)
11.10.2013
SNMP Traffic Sensor
1157
(v7)
1164
SNMP Trap Receiver Sensor SNTP Sensor

1170
(v7)
(v8.1.0)
1175
SSH Disk Free Sensor
(v8.1.0)
1184
SSH INodes Free Sensor
(v8.1.1) (v8.1.0)
SSH Load Average Sensor SSH Meminfo Sensor

1196
1190
(v8.1.0)
1202
SSH Remote Ping Sensor SSH Script Sensor

1209
(v12.x.1)
(v12.x.1)
1218
SSH Script Advanced Sensor
(v12.x.6)
1226
SSH VMWare ESX(i) Disk Sensor Syslog Receiver Sensor System Health Sensor TFTP Sensor
1243 1239 1232
(v8.2.0)
(v7)
(v9.1.0)
(v8.1.0)
1249
Traceroute Hop Count Sensor
(v8.3.0)
1254
Virtuozzo Container Disk Sensor
(v8.2.1)
1260
Virtuozzo Container Network Sensor
(v8.2.1) (v8.1.0)
1272
VMware Host Hardware (WBEM) Sensor
1266
VMware Host Hardware Status (SOAP) Sensor VMware Host Performance (SOAP) Sensor VMware Virtual Machine (SOAP) Sensor WBEM Custom Sensor
1291 1284 1278
(v12.x.1)
(v12.x.1)
(v7)
(v8.1.0)
1297
Windows CPU Load Sensor
(v7)
1303
Windows IIS 6.0 SMTP Received Sensor Windows IIS 6.0 SMTP Sent Sensor Windows IIS Application Sensor Windows Last Update Sensor
1322 1315 1309
(v8.1.0)
(v8.1.0)
(v12.x.1)
(v8.3.0)
1328
Windows Logged In Users Sensor
(v8.3.0)
1334
Windows MSMQ Queue Length Sensor Windows Network Card Sensor Windows Pagefile Sensor
1348 1341
(v8.3.0)
(v7)
(v12.x.4)
1354
Windows Physical Disk Sensor Windows Print Queue Sensor Windows Registry Sensor
1367
(v9.1.0)
1361
(v8.3.0)
(v9.1.0) 293
11.10.2013
Windows Scheduled Task Sensor Windows System Uptime Sensor
1375
(v9.1.1) (v8.1.0)
1388
1382
Windows Updates Status (Powershell) Sensor WMI Custom Sensor

1394
(v13.x.6)
(v7)
1401
WMI Custom String Sensor WMI Event Log Sensor

1410
(v12.x.4)
(v7)
1417
WMI Exchange Server Sensor
(v7.1.1)
1424
WMI Exchange Transport Queue Sensor WMI File Sensor

1431
(v12.x.1)
(v7)
1437
WMI Free Disk Space (Multi Drive) Sensor WMI HDD Health Sensor WMI Logical Disk Sensor WMI Memory Sensor
1457 1445
(v7)
(v12.x.1)
1451
(v7)
1462
WMI Microsoft SQL Server 2005 Sensor WMI Microsoft SQL Server 2008 Sensor WMI Microsoft SQL Server 2012 Sensor WMI Process Sensor
1487
(v8.1.0) (v8.1.0) (v12.x.6)
1471
1479
(v7)
1493
WMI Remote Ping Sensor
(v12.x.1)
1498
WMI Security Center Sensor WMI Service Sensor WMI Share Sensor
1504
(v9)
(v7)
1510
(v8.1.0)
1517
WMI SharePoint Process Sensor
(v12.x.1)
1523
WMI Terminal Services (Windows 2008) Sensor
(v8.1.0)
1528
WMI Terminal Services (Windows XP/Vista/2003) Sensor WMI UTC Time Sensor
1533
(v8.1.0)
(v9.2.0)
1538
WMI Vital System Data (V2) Sensor WMI Volume Sensor

1544
(v7)
(v7)
1550
WMI Windows Version Sensor WSUS Statistics Sensor

1556
(v8.3.0)
(v9.1.0)
More
Did not find what you are looking for? Have a look into the Additional Sensor Types (Custom Sensors) 1563 section.
294
11.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 2 Active Directory Replication Errors Sensor
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. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.
Requirement: .NET Framework

This sensor type requires the Microsoft .NET Framework to be installed on the computer running the PRTG probe: Either on the local system (on every node, if on a cluster probe), or on the system running the remote probe 1888 . If the framework is missing, you cannot create this sensor. Note: You need to install the exact version required (a higher version will usually not work; an exception applies to .NET 3.5 which comprises .NET 2.0 and .NET 3.0). Generally, it is possible to run several .NET Framework versions on the same machine side-by-side. Please install the latest update available for the required version. Required .NET version: 2.0.
Requirement: Member of Windows Domain

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

For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. In the parent device's 264 Credent ials for Windows Sy st ems settings, please prefer using Windows domain credentials. Note: If you use local credentials, please make sure the same Windows user accounts (with same username and password) exist on both the system running the PRTG probe and the target computer. Otherwise the sensor cannot connect correctly. Note: Your Windows credentials may not contain any double quotation marks ("). If they do, this sensor will not work!
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later.
03.05.2013
295
Sensor Settings
On the sensor's details page, click on the Set t ings tab to change settings. Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Set t ings 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. 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 84 from objects further up in the device tree. Those are not visible here. Select a priority for the sensor. This setting determines where the sensor will be placed in sensor lists. Top priority will be at the top of a list. You can choose from one star (low priority) to five stars (top priority).
Tags
Priority
Sensor Set t ings Get Errors From Define whether all domain controllers or only the domain controller the sensor is logged in to will be queried. Domain controllers can always see each other, otherwise replication is not possible. The probe can be in a subnet that can only see its own domain controller and is able to retrieve a complete list of domain controllers from its own domain controller, but has no route to the other domain controllers on the list. In that case, set the option to query only the domain controller the sensor is logged in to. All domain cont rollers in t he forest : The sensor retrieves a list of all domain controllers and queries them one by one for replication errors. The output to PRTG is the total number of errors reported by all domain controllers together. Only t he domain cont roller t he sensor is logged in t o : The sensor only queries the domain controller that the sensor is logged in to.
296
03.05.2013
Sensor Display Primary Channel Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel will always be displayed underneath the sensor's name. The available options depend on what channels are available for this sensor. Note: You can set another primary channel later by clicking on the pin symbol of a channel in the sensor's overview tab. Define how different channels will be shown for this sensor. Show channels independent ly (default ): Show an own graph for each channel. St ack channels on t op of each ot her: Stack channels on top of each other to create a multi-channel graph. This will generate an easy-to-read graph which visualizes the different components of your total traffic. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 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.
Chart Type
Inherited Settings
By default, all following settings are inherited from objects higher in the hierarchy and should be changed there, if necessary. Often, best practice is to change them centrally in the Root 213 group's settings. To change a setting for this object, 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 Int erval 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 1691 .
03.05.2013
297
Schedules, Dependencies, and Maint enance Window Schedule Select a schedule from the list. Schedules can be used to monitor for a certain time span (days, hours) throughout the week. With the period list option it is also possible to pause monitoring for a specific time span. You can create new schedules and edit existing ones in the account settings 1678 . Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active. Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between: Not set (monit or cont inuously ): No maintenance window will be set. Set up a one-t ime maint enance window: Pause monitoring within a maintenance window. Maintenance Begins At This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window. This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window. 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. Mast er object for parent : Make this sensor the master object for its parent device. The sensor will influence the behavior of the device it is created on: If the sensor is in a Down status, the device will be paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor will be paused if the parent group of its parent device is in a Down status, or if it is paused by another dependency.
Maintenance Window
Maintenance End At
Dependency Type
298
03.05.2013
Schedules, Dependencies, and Maint enance Window Note: Testing your dependencies is easy! Simply choose Simulat e Error St at us from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused. Dependency This field is only visible if the select object option is enabled above. Click on the reading-glass symbol and use the object selector 143 to choose an object on which the current sensor will be dependent on. Define a time span. After the master object for this dependency comes back to an Up status, monitoring of the depending objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds. Note: This setting is not available if you choose this sensor to be the Mast er object for parent . In this case, please define delays in the parent Device Set t ings 261 or the superior Group Set t ings 242 .
Delay (Seconds)
03.05.2013
299
Edit Sensor Channels

In order to change display settings, spike filter, and limits, please switch to the sensor's Overview tab and click on the gear icon of a specific channel. For detailed information, please see Sensor Channels Set t ings 1566 section.
Notifications
Click on the Not ificat ions tab to change notification triggers. For detailed information, please see Sensor Not ificat ions Set t ings 1573 section.
Others
133
section.
300
03.05.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 3 ADO SQL Sensor
6.8.3
ADO SQL Sensor

The ADO SQL sensor monitors a database using an ActiveX Data Objects (ADO) connection. It connects to the server and shows the response time. Additionally, it can read the number of records and a value. Note: For security reasons, you can only create a sensor on a device for which Windows Credentials have been defined. With these credentials, the PRTG probe must be able to connect to the Windows domain. If you don't enter valid credentials, you will get an Access denied error message when scanning. For detailed information, please see More 307 section below.
Add Sensor
Sensor Settings
Tags
Priority
27.11.2012
301
ADO Specific Dat a 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 307 section below.
Dat a SQL Expression Enter a valid SQL statement to execute on the server. In your SELECT statement, please specify the field name explicitly. Do not use SELECT *! For example, a correct expression could be: SELECT AVG(UnitPrice) FROM Products. When a cursor is returned (i.e. with a SELECT statement), only the first row of data will be processed.
Record Count
If you want to know how many records in your database were affected by your SQL expression as defined above, you can count the number of concerned records. Choose between: Do not count number of records: Affected records will not be counted. Count number of records: The number of affected records will be counted. Note: Enabling this option might increase the execution time of this sensor.
Post-processing
If the SQL expression returns a result set, please define if you want to further process it. Choose between: Ignore result set : Do not do anything with the data returned. Process numerical result : Regard the result set returned as integer or float. You can set the sensor to Warning or Down status for specific thresholds. Define below. Process st ring result : Regard the result set returned as a string. You can set the sensor to error for certain sub-strings contained or missing. Define below. Monit or for changes: Monitor if the result set has changed since last check. The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 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:
302
27.11.2012
none: Do not set the sensor to Warning status for any condition. equals: Result set must be the same as the value provided below. is above: Result set must be above the value provided below. lower t han: Result set must be below the value provided below. does not equal: Result set must be unequal to the value provided below. Note: This threshold check the SQL result set only. You can set additional thresholds in the sensor's channel settings 1566 . 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. 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 t han: Result set must be below the value provided below. does not equal: Result set must be unequal to the value provided below. Note: This threshold check the SQL result set only. You can set additional thresholds in the sensor's channel settings 1566 . 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.
Condition "Down"
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.
27.11.2012
303
Chart Type
Inherited Settings
304
27.11.2012
Maintenance Window
Maintenance End At
Dependency Type
27.11.2012
305
Delay (Seconds)
306
27.11.2012
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

Notifications
Others
133
section.
27.11.2012
307
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 4 Amazon CloudWatch Sensor
6.8.4
Amazon CloudWatch Sensor

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

This sensor type requires the Microsoft .NET Framework to be installed on the computer running the PRTG probe: Either on the local system (on every node, if on a cluster probe), or on the system running the remote probe 1888 . If the framework is missing, you cannot create this sensor. Note: You need to install the exact version required (a higher version will usually not work; an exception applies to .NET 3.5 which comprises .NET 2.0 and .NET 3.0). Generally, it is possible to run several .NET Framework versions on the same machine side-by-side. Please install the latest update available for the required version. Required .NET version: 4.0 (with latest update).
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. PRTG will perform a meta scan before you actually add this sensor type and requires basic information for this scan in advance. Provide the requested information in the appearing window. During the scan, PRTG will recognize all items available for monitoring based on your input. The following settings differ in comparison to the sensor's settings page:
308
08.10.2013
Amazon Credent ials Region Select the region in which the instance to be monitored is running. The settings you make in this dialog are valid for all of the sensors that are created. Choose between: US East (Nort hern Virginia) US West (Oregon) US West (Nort hern California) EU (Ireland) Asia Pacific (Singapore) Asia Pacific (Toky o) Asia Pacific (Sy dney ) Sout h America (Sao Paulo) Note: The CloudWatch option must be enabled for the instance you want to monitor (you can do this e.g. using Amazon's AWS console).
Select which service instances you want to monitor. PRTG will create one sensor for each instance you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Amazon CloudWat ch Specific Service Instance Select the instances you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
08.10.2013
309
Tags
Priority
Amazon Credent ials AWS Access Key ID AWS Secret Access Key Region Enter your access key. You can obtain it from aws.amazon.com. Enter your secret access key. You can obtain it from aws.amazon.com. Shows the region your instance is located at. 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.
Amazon CloudWat ch Specific Period (Interval) Define in what granularity you want to receive datapoints from CloudWatch. Choose between: 1 Minut e 2 Minut es 5 Minut es 10 Minut es 30 Minut es 1 Hour
310
08.10.2013
Amazon CloudWat ch Specific Service Shows the service this sensor is monitoring. 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. Shows the Instance ID of the Amazon Web Services instance this sensor is monitoring. When using the "Simple Notification Service (SNS)" service, this field is not visible. Once a sensor is created this value cannot be changed. It is shown for reference purposes only. If you need to change this, please add the sensor anew. This field is only visible if you selected a "Simple Notification Service (SNS)" instance before. It shows the topic name that is monitored by this sensor. The sensor will show the number and size of messages published, and the number of notifications delivered and failed. Each sensor can monitor one topic name only. Once a sensor is created this value cannot be changed. It is shown for reference purposes only. If you need to change this, please add the sensor anew. This field is only visible if you selected a "Elastic Load Balancing (ELB)" instance before. Enter the name of the Availability Zone of your Load Balancer you want to monitor. If you leave this field empty, the average value of all zones will be taken.
Instance
Topic Name
Availability Zone
Sensor Display Primary Channel Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel will always be displayed underneath the sensor's name. The available options depend on what channels are available for this sensor. Note: You can set another primary channel later by clicking on the pin symbol of a channel in the sensor's overview tab. Define how different channels will be shown for this sensor. Show channels independent ly (default ): Show an own graph for each channel. St ack channels on t op of each ot her: Stack channels on top of each other to create a multi-channel graph. This will generate an easy-to-read graph which visualizes the different components of your total traffic. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 settings).
Chart Type
08.10.2013
311
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 213 group's settings. To change a setting for this object, disable inheritance by clicking on the check mark symbol in front of the respective setting name. You will then see the options described below. Note: For Amazon CloudWatch sensors, the scanning interval cannot be inherited. Please use the individual settings of the sensor to define the interval in which data is received. Schedules, Dependencies, and Maint enance Window Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings. Schedule Select a schedule from the list. Schedules can be used to monitor for a certain time span (days, hours) throughout the week. With the period list option it is also possible to pause monitoring for a specific time span. You can create new schedules and edit existing ones in the account settings 1678 . Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active. Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between: Not set (monit or cont inuously ): No maintenance window will be set. Set up a one-t ime maint enance window: Pause monitoring within a maintenance window. Maintenance Begins At This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window.
Maintenance Window
312
08.10.2013
Schedules, Dependencies, and Maint enance Window Maintenance End At This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window. 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. Mast er object for parent : Make this sensor the master object for its parent device. The sensor will influence the behavior of the device it is created on: If the sensor is in a Down status, the device will be paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor will be paused if the parent group of its parent device is in a Down status, or if it is paused by another dependency. Note: Testing your dependencies is easy! Simply choose Simulat e Error St at us from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused. Dependency This field is only visible if the select object option is enabled above. Click on the reading-glass symbol and use the object selector 143 to choose an object on which the current sensor will be dependent on. Define a time span. After the master object for this dependency comes back to an Up status, monitoring of the depending objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds. Note: This setting is not available if you choose this sensor to be the Mast er object for parent . In this case, please define delays in the parent Device Set t ings 261 or the superior Group Set t ings 242 .
Dependency Type
Delay (Seconds)
08.10.2013
313
More
Knowledge Base: How do I define access rights for Amazon CloudWatch queries?
314
08.10.2013
http://www.paessler.com/knowledgebase/en/topic/38083 Knowledge Base: How much does Amazon charge for using the CloudWatch API? http://www.paessler.com/knowledgebase/en/topic/37543

Notifications
Others
133
section.
08.10.2013
315
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 5 AVM FRITZ!Box WAN Interface Sensor
6.8.5
AVM FRITZ!Box WAN Interface Sensor

The AVM FRITZ!Box WAN Interface Sensor monitors the internet traffic of a FRITZ!Box internet access router from European manufacturer AVM. It returns the incoming and outgoing internet traffic. Note: There are no credentials necessary, but transmission of status information via Universal Plug and Play (UPnP) must be enabled in the network settings of your Fritz!Box. See More 320 section below for detailed information. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Add Sensor
Sensor Settings
Basic Sensor Set t ings 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.
316
07.02.2013
Basic Sensor Set t ings 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 84 from objects further up in the device tree. Those are not visible here. Select a priority for the sensor. This setting determines where the sensor will be placed in sensor lists. Top priority will be at the top of a list. You can choose from one star (low priority) to five stars (top priority).
Priority
Chart Type
Inherited Settings
By default, all following settings are inherited from objects higher in the hierarchy and should be changed there, if necessary. Often, best practice is to change them centrally in the Root 213 group's settings. To change a setting for this object, disable inheritance by clicking on the check mark symbol in front of the respective setting name. You will then see the options described below.
07.02.2013
317
Schedules, Dependencies, and Maint enance Window Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings. Schedule Select a schedule from the list. Schedules can be used to monitor for a certain time span (days, hours) throughout the week. With the period list option it is also possible to pause monitoring for a specific time span. You can create new schedules and edit existing ones in the account settings 1678 . Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active. Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between: Not set (monit or cont inuously ): No maintenance window will be set. Set up a one-t ime maint enance window: Pause monitoring within a maintenance window. Maintenance Begins At This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window. This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window. 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.
Maintenance Window
Maintenance End At
Dependency Type
318
07.02.2013
Schedules, Dependencies, and Maint enance Window 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. Mast er object for parent : Make this sensor the master object for its parent device. The sensor will influence the behavior of the device it is created on: If the sensor is in a Down status, the device will be paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor will be paused if the parent group of its parent device is in a Down status, or if it is paused by another dependency. Note: Testing your dependencies is easy! Simply choose Simulat e Error St at us from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused. Dependency This field is only visible if the select object option is enabled above. Click on the reading-glass symbol and use the object selector 143 to choose an object on which the current sensor will be dependent on. Define a time span. After the master object for this dependency comes back to an Up status, monitoring of the depending objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds. Note: This setting is not available if you choose this sensor to be the Mast er object for parent . In this case, please define delays in the parent Device Set t ings 261 or the superior Group Set t ings 242 .
Delay (Seconds)
07.02.2013
319
More
Knowledge Base: How do I activate UPnP for my Fritz!Box?
320
07.02.2013
http://www.paessler.com/knowledgebase/en/topic/38603

Notifications
Others
133
section.
07.02.2013
321
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 6 Cisco IP SLA Sensor
6.8.6
Cisco IP SLA Sensor

The Cisco IP SLA sensor monitors Voice over IP (VoIP) network parameters using IP Service Level Agreement (SLA) from Cisco via Simple Network Management Protocol (SNMP). It shows different aspects provided by the queried device. For a general introduction to the technology behind Quality of Service monitoring, please see Monit oring Qualit y of Service 1825 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
IP SLA Specific IP SLAs Select the IP SLAs you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. The list options depend on the configuration of the queried device. If you're missing a type here, please check your device's configuration. PRTG can support the following operations: echo pat hEcho fileIO script udpEcho t cpConnect ht t p dns jit t er dlsw dhcp ft p pat h-jit t er
322
07.02.2013
IP SLA Specific Note: Packet Loss values are summarized, but have no explicit channel for SourceDestination or DestinationSource values
Sensor Settings
Tags
Priority
IP SLA Specific ID Type Name (Tag) Owner Frequency 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.
07.02.2013
323
Chart Type
Inherited Settings
324
07.02.2013
Maintenance Window
Maintenance End At
Dependency Type
07.02.2013
325
Delay (Seconds)
326
07.02.2013

Notifications
Others
133
section.
07.02.2013
327
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 7 Citrix XenServer Host Sensor
6.8.7
Citrix XenServer Host Sensor

The Citrix XenServer Host Sensor monitors a Xen host server via Hypertext Transfer Protocol (HTTP). It shows CPU, memory, and network usage, as well as the number of running virtual machines and load average. Note: The parent device must be a Citrix XenServer (version 5.0 or later). For this sensor type credentials for Xen servers must be defined for the device you want to use the sensor on. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Monitoring a XenServer Pool

In a XenServer pool there is one "pool master" that manages the pool. Incoming queries on any host are automatically forwarded to the pool master. If you want to monitor your virtual machines, or host servers, simply create respective sensors on a device that represents one host server of your pool. Internal processes will make sure that monitoring will take place and continue independently from the physical host. Note: In PRTG's device tree, the sensors for virtual machines will always remain on the host you originally created it on, also if it is currently running on a different host.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. If you select more than one host, multiple sensors are created at once in the Add Sensor dialog. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
328
07.02.2013
Host Set t ings Host Select the hosts you want to add a sensor for, including the ones that are not running. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
Priority
Host Set t ings UUID Shows the Universally Unique Identifier (UUID) of the host 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. Shows the name of the host 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
07.02.2013
329
Chart Type
Inherited Settings
330
07.02.2013
Maintenance Window
Maintenance End At
Dependency Type
07.02.2013
331
Delay (Seconds)
332
07.02.2013

Notifications
Others
133
section.
07.02.2013
333
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 8 Citrix XenServer Virtual Machine Sensor
6.8.8
Citrix XenServer Virtual M achine Sensor

The Citrix XenServer Virtual Machine Sensor monitors a virtual machine on a Xen server via Hypertext Transfer Protocol (HTTP). It shows CPU usage and free memory in percent. Note: The parent device must be a Citrix XenServer (version 5.0 or later). For this sensor type credentials for Xen servers must be defined for the device you want to use the sensor on. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Monitoring a XenServer Pool

In a XenServer pool there is one "pool master" that manages the pool. Incoming queries on any host are automatically forwarded to the pool master. If you want to monitor your virtual machines, or host servers, simply create respective sensors on a device that represents one host server of your pool. Internal processes will make sure that monitoring will take place and continue independently from the physical host. Note: In PRTG's device tree, the sensors for virtual machines will always remain on the host you originally created it on, also if it is currently running on a different host.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. Note: PRTG requests a full list of all virtual machines configured on the device. Therefore, it may take a few seconds before the dialog is loaded. If you select more than one virtual machine, multiple sensors are created at once in the Add Sensor dialog. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
334
07.02.2013
Virt ual Machine Set t ings Virtual Machine Select the Virtual Machine (VM) you want to add a sensor for, including the ones that are not running. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
Priority
Virt ual Machine Set t ings UUID Shows the Universally Unique Identifier (UUID) of the virtual machine. 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. Shows the name of the virtual machine. 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
07.02.2013
335
Chart Type
Inherited Settings
336
07.02.2013
Maintenance Window
Maintenance End At
Dependency Type
07.02.2013
337
Delay (Seconds)
338
07.02.2013

Notifications
Others
133
section.
07.02.2013
339
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 9 Cluster Probe Health Sensor
6.8.9
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
Tags
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. Note: You can set another primary channel later by clicking on the pin symbol of a channel in the sensor's overview tab. Define how different channels will be shown for this sensor. Show channels independent ly (default ): Show an own graph for each channel.
Chart Type
340
27.11.2012
Sensor Display St ack channels on t op of each ot her: Stack channels on top of each other to create a multi-channel graph. This will generate an easy-to-read graph which visualizes the different components of your total traffic. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 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
27.11.2012
341
342
27.11.2012

Notifications
Others
133
section.
27.11.2012
343
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 10 Core Health Sensor
6.8.10 Core Health Sensor

The Core Health sensor monitors internal PRTG parameters. It shows the state of the PRTG core server. It is created automatically by PRTG and cannot be deleted. This sensor type checks various parameters of your PRTG core which have an impact on the stability of the system: Healt h: This index value sums up the core state into a value between 100% (healthy) and 0% (failing). Frequent or repeated health values below 100% should be investigated. CPU Load: This channel shows the current percentage CPU load. Extensive CPU load can lead to false, incomplete, and incorrect monitoring results. This value usually should stay below 50%. Handles: This is a counter for the data structures of the operating system. It is responsible for internal resource management. Repeated obviously increasing values should be investigated. Commit t ed Memory : This channel shows the amount of memory committed to the PRTG core server as reported by the memory manager. Free Page File Memory : This channel shows the amount of free page file memory currently available on the system. Page file memory is aggregated RAM and the size of page file. It is the maximum amount of memory that is available on the system to be used for all currently running processes. If it gets too low the system can crash, at least some applications will throw "Out of memory" errors. Free Phy sical Memory : This channel shows the amount of free physical memory currently available on the system. This is the RAM that is physically built-in in the computer. If it gets too low the system will become very slow and PRTG is not usable in a reasonable way anymore. It can happen that some sensors will not be displayed correctly in that case, they will appear disabled (grayed out). Free Virt ual Memory : This channel shows the accessible address space on the system for PRTG. PRTG cannot use more memory than reported here, independently from free page file and physical memory. On a 32bit OS (operating system) the maximum is 2 GB (3 GB with special settings under Windows); on a 64bit OS it is 4 GB if PRTG is running as 32bit version, and unlimited as 64bit version (only Core). If free virtual memory gets too low, PRTG will throw "Out of memory" errors or the message "not enough storage to process this command" (visible in the Core log). Threads: This channel shows the number of program parts which are currently running simultaneously. This number can increase with heavy load. The number should not exceed 100 in normal operation. This sensor can be set up on a Probe Device only!
Sensor Settings
344
03.05.2013
Tags
Priority
Chart Type
03.05.2013
345
Inherited Settings
346
03.05.2013

Notifications
Others
133
section.
03.05.2013
347
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 11 Dell PowerVault MDi Sensor
6.8.11 Dell PowerVault M Di Sensor

The Dell PowerVault MDi sensor monitors a virtual disk on a Dell PowerVault MD3000i, MD3620i, MD3000f, or MD3620f. It may work with additional models, too. This sensor can show current, maximum, and total IOs, current and maximum speed, as well as read and cache hit percentages.
Requirement: Dell Modular Disk Storage Manager

This sensor requires an installation of Dell's "Modular Disk Storage Manager" program. This has to be installed on the computer running the PRTG probe: Either on the local system (on every node, if on a cluster probe), or on the system running the remote probe 1888 . For details about setup, please see More 352 section below. Note: Please create this sensor on a device which has the SAN's IP address configured in the "IP address/DNS name" field.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. If you select more than one disk, multiple sensors are created at once in the Add Sensor dialog. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Sensor Set t ings Virtual Disks Select the disk you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
348
19.07.2013
Tags
Priority
Sensor Set t ings Virtual Disks Shows the name of the virtual disk 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.
Chart Type
19.07.2013
349
Inherited Settings
Schedules, Dependencies, and Maint enance Window Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings. Schedule Select a schedule from the list. Schedules can be used to monitor for a certain time span (days, hours) throughout the week. With the period list option it is also possible to pause monitoring for a specific time span. You can create new schedules and edit existing ones in the account settings 1678 . Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active. Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between: Not set (monit or cont inuously ): No maintenance window will be set. Set up a one-t ime maint enance window: Pause monitoring within a maintenance window.
Maintenance Window
350
19.07.2013
Schedules, Dependencies, and Maint enance Window Maintenance Begins At This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window. This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window. 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. Mast er object for parent : Make this sensor the master object for its parent device. The sensor will influence the behavior of the device it is created on: If the sensor is in a Down status, the device will be paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor will be paused if the parent group of its parent device is in a Down status, or if it is paused by another dependency. Note: Testing your dependencies is easy! Simply choose Simulat e Error St at us from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused. Dependency This field is only visible if the select object option is enabled above. Click on the reading-glass symbol and use the object selector 143 to choose an object on which the current sensor will be dependent on. Define a time span. After the master object for this dependency comes back to an Up status, monitoring of the depending objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds. Note: This setting is not available if you choose this sensor to be the Mast er object for parent . In this case, please define delays in the parent Device Set t ings 261 or the superior Group Set t ings 242 .
Maintenance End At
Dependency Type
Delay (Seconds)
19.07.2013
351
More
Where do I find the Dell PowerVault Modular Disk Storage Manager for use with my MDi SAN? http://www.paessler.com/knowledgebase/en/topic/38743

Notifications
352
19.07.2013
Others
133
section.
19.07.2013
353
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 12 DHCP Sensor
6.8.12 DHCP Sensor

The DHCP sensor monitors a Dynamic Host Configuration Protocol (DHCP) server. It sends a broadcast message to the network and waits for a DHCP server to respond. If a server responds, the sensor shows both the address of the server and the offered IP in the sensor's Message field. You can check the server's response using Regular Expressions 1886 . The sensor's channels include response time (msec) and the lease time given by the server (in days). This sensor can be set up on a Probe Device only! On sensor creation, choose the network card on the probe system which will be used to send the broadcast message.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor DHCP servers, PRTG will create one sensor for each network interface you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
DHCP Specific Specify Network Interface Select the network adapters you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
354
08.10.2013
Priority
DHCP Specific MAC Shows the MAC address of the network adapter that is used to send the broadcast message to the network. Once a sensor is created this value cannot be changed. It is shown for reference purposes only. If you need to change this, please add the sensor anew. Specify if you want to check the returned client IP with a regular expression. Choose between: Don't check: The IP will only appear in the sensor message without further processes. Check: Enter the regular expression you want to use below. Client IP Must Include This field will only appear if you chose to check the client IP above. In the response of the DHCP server, search using a regular expression. If the answer for the client IP does not contain the defined string, the sensor will change to a Down status. For example, enter 10\.0\.5\..* to make sure any answering DHCP server returns an client IP address starting with "10.0.5.". If it doesn't, the sensor will show an error. For more details, see Regular Expressions 1886 section. Leave empty to not use this field. This field will only appear if you chose to check the client IP above. In the response of the DHCP server, search using a regular expression. If the answer for the client IP contains the defined string, the sensor will change to a Down status. See example above. For more details, see Regular Expressions 1886 section. Leave empty to not use this field. Specify if you want to check the returned server IP with a regular expression. Choose between:
Client IP
Client IP Must Not Include
Server IP
08.10.2013
355
DHCP Specific Don't check: The IP will only appear in the sensor message without further processes. Check: Enter the regular expression you want to use below. Server IP Must Include This field will only appear if you chose to check the server IP above. In the response of the DHCP server, search using a regular expression. If the answer for the server IP does not contain the defined string, the sensor will change to a Down status. See example above. For more details, see Regular Expressions 1886 section. Leave empty to not use this field. This field will only appear if you chose to check the server IP above. In the response of the DHCP server, search using a regular expression. If the answer for the server IP contains the defined string, the sensor will change to a Down status. See example above. For more details, see Regular Expressions 1886 section. Leave empty to not use this field. 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. If there is more than one DHCP server in the network that may answer to the broadcast message, the sensor can receive an answer from a different DHCP server, compared to the last scan of the sensor. In this case, PRTG can write an entry to the system Logs 137 . Choose between: Ignore: Do not write a log entry if the DHCP server changes. Writ e log ent ry : Write an entry to the system Logs whenever the DHCP server changes between two sensor scans. Note: Regardless of this setting, those entries will always be added to the sensor Log . Offered IP Change If the IP address offered by the DHCP server changes between two sensor scans, PRTG can write an entry to the system Logs 137 . Choose between: Ignore: Do not write a log entry if the offered IP address changes. Writ e log ent ry : Write an entry to the system Logs whenever the DHCP server offers a different IP address compared to the last sensor scan. Note: Regardless of this setting, those entries will always be added to the sensor Log .
Server IP Must Not Include
Timeout (sec)
DHCP Server Change
356
08.10.2013
Chart Type
Inherited Settings
08.10.2013
357
Maintenance Window
Maintenance End At
Dependency Type
358
08.10.2013
Delay (Seconds)
08.10.2013
359

Notifications
Others
133
section.
360
08.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 13 DNS Sensor
6.8.13 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
Sensor Settings
Tags
Priority
DNS 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.
27.11.2012
361
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. 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. Select the type of query that should be sent to the DNS server. Choose between: Host address IPv4 (A) Host address IPv6 (AAAA) Aut horit at ive name server (NS) St art of a zone of aut horit y marker (SOA) Domain name point er (PTR) Mail exchange (MX ) Canonical name for an alias (CNAME) Check Result Define if the result received from the DNS server will be checked. Choose between: Ignore result : Any valid answer of the DNS server will be accepted by the sensor. Check result : Check if the response contains certain strings. Define below. Value This field is only visible if result checking is enabled above. Enter elements that must be contained in the response of the DNS server. Enter each entry in one line. At least one of the elements must be contained in the received result. If none of the element matches the response, the sensor will show a red Down status. For example, you can enter an IP address here if your Domain field contains a host name. Only if the host name is resolved to the correct IP address your sensor will show a green Up status. Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results.
Domain
Query Type
Write Result
362
27.11.2012
DNS Specific Writ e sensor result t o disk (Filename: "Result of Sensor (ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Chart Type
Inherited Settings
27.11.2012
363
Maintenance Window
Maintenance End At
Dependency Type
364
27.11.2012
Delay (Seconds)
27.11.2012
365

Notifications
Others
133
section.
366
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 14 Enterprise Virtual Array Sensor
6.8.14 Enterprise Virtual Array Sensor

The Enterprise Virtual Array sensor monitors an HP StorageWorks Enterprise Virtual Array (EVA) using the sssu.exe from HP Command View EVA Software. It can show the status of several EVA modules, for example, status of system, controllers, enclosures, disks, disk groups, folders, hosts, snapshots, data replication, cabinets, and many more, depending on the available measurement components. If devices have measuring tools for fans and temperature, the corresponding data will be displayed as well. For these EVA components, this sensor type can show the operational status, predicted failures, accessible media, allocation in percent, availability for VRaids in bytes, exaggerated bytes, group host access, the number of grouped and ungrouped disks, the age of snapshots, and the license status. Important notice: This sensor is an experimental sensor. Currently, it is in bet a status. The methods of operating can change at any time, as well as the available settings. Do not expect that all functions will work properly, or that this sensor works as expected at all. Be aware that this type of sensor can be removed again from PRTG at any time. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 .
Requirement: Command View

The EVA sensor needs the HP Command View EVA Software to be installed on the probe system. If you do not want to install the whole command view tool, you can alternatively use another approach. For details, please see section More 372 .
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. PRTG will perform a meta scan before you actually add this sensor type and requires basic information for this scan in advance. Provide the requested information in the appearing window. During the scan, PRTG will recognize all items available for monitoring based on your input. The following settings differ in comparison to the sensor's settings page:
EVA Credent ials Scanning Mode Specify the depth of the meta scan. Choose between: Basic : We recommend using this scanning mode. Various modules of your EVA will be available for monitoring. Full Det ail: PRTG will scan for each disk of your EVA. Every disk will be listed in the module selection.
08.10.2013
367
Select which modules you want to monitor. PRTG will create one sensor for each module you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
EVA Set t ings Modules Select the modules you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
Priority
EVA Credent ials Username Password Enter the username for the EVA. Enter the password for the EVA.
368
08.10.2013
EVA Set t ings Module Shows the monitored module. You can adjust this setting if the module was renamed or moved to another folder. This way, PRTG can find the module again and the monitoring history will not be lost. Shows further information about the monitored module. 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.
System Module Type Description Sensor Result
Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results. Writ e sensor result t o disk (Filename: "Result of Sensor [ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Chart Type
08.10.2013
369
Schedules, Dependencies, and Maint enance Window Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings. Schedule Select a schedule from the list. Schedules can be used to monitor for a certain time span (days, hours) throughout the week. With the period list option it is also possible to pause monitoring for a specific time span. You can create new schedules and edit existing ones in the account settings 1678 . Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active. Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between: Not set (monit or cont inuously ): No maintenance window will be set. Set up a one-t ime maint enance window: Pause monitoring within a maintenance window. Maintenance Begins At This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window. This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window.
Maintenance Window
Maintenance End At
370
08.10.2013
Schedules, Dependencies, and Maint enance Window Dependency Type Define a dependency type. Dependencies can be used to pause monitoring for an object depending on the status of another. You can choose between: Use parent : Pause the current 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. Mast er object for parent : Make this sensor the master object for its parent device. The sensor will influence the behavior of the device it is created on: If the sensor is in a Down status, the device will be paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor will be paused if the parent group of its parent device is in a Down status, or if it is paused by another dependency. Note: Testing your dependencies is easy! Simply choose Simulat e Error St at us from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused. Dependency This field is only visible if the select object option is enabled above. Click on the reading-glass symbol and use the object selector 143 to choose an object on which the current sensor will be dependent on. Define a time span. After the master object for this dependency comes back to an Up status, monitoring of the depending objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds. Note: This setting is not available if you choose this sensor to be the Mast er object for parent . In this case, please define delays in the parent Device Set t ings 261 or the superior Group Set t ings 242 .
Delay (Seconds)
08.10.2013
371
More
HP Command View EVA Software
372
08.10.2013
http://www8.hp.com/us/en/products/storage-software/product-detail.html?oid=471497 Knowledge Base: Do I really have to install the whole Command View on the probe to use the EVA sensor? http://www.paessler.com/knowledgebase/en/topic/55983

Notifications
Others
133
section.
08.10.2013
373
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 15 Event Log (Windows API) Sensor
6.8.15 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). Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.
Add Sensor
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: Applicat ion Sy st em Securit y Direct ory Service DNS Server File Replicat ion Service
Sensor Settings
374
07.02.2013
Priority
Filt er Event Log Ent ries 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 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. 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 all received events for a certain event category. If enabled, only messages matching the defined value will be considered by the sensor. Choose between:
Filter by ID
Filter by Category
07.02.2013
375
Filt er Event Log Ent ries 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 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 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 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.
Filter by Event User
Filter by Event Computer
Filter by Event Message
376
07.02.2013
Filt er Event Log Ent ries 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.
Chart Type
Inherited Settings
07.02.2013
377
Maintenance Window
Maintenance End At
Dependency Type
378
07.02.2013
Delay (Seconds)
07.02.2013
379

Notifications
Others
133
section.
380
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 16 Exchange Backup (Powershell) Sensor
6.8.16 Exchange Backup (Powershell) Sensor

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

This sensor type uses PowerShell commands. In order to monitor devices with this sensor, Remot e PowerShell and Remot e Exchange Management Shell have to be enabled on the server. Ensure that you have installed PowerShell 2.0 or later on your probe machine. For more information, please see section More below.
Requirement: Fully Qualified Domain Name (FQDN)

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

The user of this sensor needs elevated rights on the Exchange system. It is not sufficient to have administrator rights. Please see section More below for detailed information on rights management.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor backups of Exchange server databases, PRTG will create one sensor for each database you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
19.07.2013
381
Sensor Set t ings Exchange Databases to be monitored on this server Select the databases you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
Priority
Sensor Set t ings Database Shows the name of the monitored database. 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. Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results.
Sensor Result
382
19.07.2013
Sensor Set t ings Writ e sensor result t o disk (Filename: "Result of Sensor [ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Chart Type
Inherited Settings
19.07.2013
383
Maintenance Window
Maintenance End At
Dependency Type
384
19.07.2013
Delay (Seconds)
19.07.2013
385
More
Knowledge Base: Resolving Exchange PowerShell Sensors Issues http://www.paessler.com/knowledgebase/en/topic/54353

Notifications
386
19.07.2013
Others
133
section.
19.07.2013
387
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 17 Exchange Database (Powershell) Sensor
6.8.17 Exchange Database (Powershell) Sensor

The Exchange Database (Powershell) sensor monitors database information of an Exchange server using Remote PowerShell. It shows several states of an Exchange database, for example, its size, if the database is mounted, and if the database is recognized as valid. Note: The parent device for this sensor must be an Exchange server version 2007 or higher. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on.



Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor databases of an Exchange server, PRTG will create one sensor for each database you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
388
19.07.2013
Sensor Set t ings Exchange Databases to be monitored on this server Select the databases you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
Priority
Sensor Set t ings Database Shows the name of the monitored database. 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. Define if you want the sensor to try to remount the database automatically if it is unmounted. Choose between: Try t o remount Just report t he current reading, keep unmount ed if so
AutoRemount Database
19.07.2013
389
Sensor Set t ings Sensor Result Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results. Writ e sensor result t o disk (Filename: "Result of Sensor [ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Chart Type
Inherited Settings
390
19.07.2013
Maintenance Window
Maintenance End At
Dependency Type
19.07.2013
391
Delay (Seconds)
392
19.07.2013
More

Notifications
19.07.2013
393
Others
133
section.
394
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 18 Exchange Mailbox (Powershell) Sensor
6.8.18 Exchange M ailbox (Powershell) Sensor

The Exchange Mailbox (Powershell) sensor monitors mailboxes of an Exchange server using Remote PowerShell. It shows several states of a mailbox, for example, total size of items, the number of items, and the time of the last login. Note: The parent device for this sensor must be an Exchange server version 2007 or higher. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on.



Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor mailboxes of Exchange servers, PRTG will create one sensor for each mailbox you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
19.07.2013
395
Sensor Set t ings Mailboxes to be monitored Select the mailboxes you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
Priority
Sensor Set t ings Mailboxname Shows the name of the monitored mailbox. 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. Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results.
Sensor Result
396
19.07.2013
Chart Type
Inherited Settings
19.07.2013
397
Maintenance Window
Maintenance End At
Dependency Type
398
19.07.2013
Delay (Seconds)
19.07.2013
399
More

Notifications
400
19.07.2013
Others
133
section.
19.07.2013
401
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 19 Exchange Mail Queue (Powershell) Sensor
6.8.19 Exchange M ail Queue (Powershell) Sensor

The Exchange Mail Queue (Powershell) sensor monitors the number of items in the outgoing mail queue of an Exchange server using Remote PowerShell. It shows, for example, queued mails, retrying mails, unreachable mails, and poisonous mails. See section More 407 below for an explanation of the transport queue types. Note: The parent device for this sensor must be an Exchange server version 2007 or higher. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on.



Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor message queues of Exchange servers, PRTG will create one sensor for each role you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
402
19.07.2013
Sensor Set t ings Hub-Transport or Edge- Select the roles you want to add a sensor for. A list of all available Server items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
Priority
Sensor Set t ings Sensor Result Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results. Writ e sensor result t o disk (Filename: "Result of Sensor [ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
19.07.2013
403
Chart Type
Inherited Settings
404
19.07.2013
Maintenance Window
Maintenance End At
Dependency Type
19.07.2013
405
Delay (Seconds)
406
19.07.2013
More
Knowledge Base: Resolving Exchange PowerShell Sensors Issues http://www.paessler.com/knowledgebase/en/topic/54353 Knowledge Base: Types of Transport Queues in Microsoft Exchange http://www.paessler.com/knowledgebase/en/topic/55413

Notifications
Others
133
section.
19.07.2013
407
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 20 Exchange Public Folder (Powershell) Sensor
6.8.20 Exchange Public Folder (Powershell) Sensor

The Exchange Public Folder (Powershell) sensor monitors public folders of an Exchange server using Remote PowerShell. It shows several states of a public folder, for example, its total size, the number of items, and the time of the last access. Note: The parent device for this sensor must be an Exchange server version 2007 or higher. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on.



Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor public folders of Exchange servers, PRTG will create one sensor for each folder you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
408
19.07.2013
Sensor Set t ings Public Folder Select the folders you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
Priority
Sensor Set t ings Public Folder Shows the name of the monitored folder. 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. Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results.
Sensor Result
19.07.2013
409
Chart Type
Inherited Settings
410
19.07.2013
Maintenance Window
Maintenance End At
Dependency Type
19.07.2013
411
Delay (Seconds)
412
19.07.2013
More

Notifications
19.07.2013
413
Others
133
section.
414
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 21 EXE/Script Sensor
6.8.21 EXE/Script Sensor

The EXE/Script sensor runs an executable file (EXE, DLL) or a script (batch file, VBScript, Powershell) on the computer running the local or remote probe. This option is provided as part of PRTG's Application Programming Interface (API). The sensor shows the execution time, and can show one value returned by the executable file or script (in one channel only). For details about the return value format please see the Applicat ion Programming Int erface (API) Definit ion 1871 . Note: The executable or script file must be stored on the system of the probe the sensor is created on: If used on a remote probe, the file must be stored on the system running the remote probe. In a cluster setup, please copy the file to every cluster node. Note: If you want to execute a custom Windows Management Instrumentation Query Language (WQL) script, please use the WMI Cust om Sensor 1394 .
Add Sensor
19.07.2013
415
Sensor Set t ings Script Select an executable file from the list. It will be executed with every scanning interval. In this list, files in the corresponding /Cust om Sensors/EX E sub-directory of the probe system's PRTG program directory are shown (see Dat a St orage 1912 ). In order for the files to appear in this list, please store them into this folder. Store files ending in BAT, CMD, DLL, EXE, PS1, and VBS. In order for the sensor to show the expected values and sensor status, your files must use the right format for the returned values (in this case, value:message to standard output). The file's exitcode will determine the sensor status. For detailed information on how to build custom sensors and for the expected return format, please see the API documentation (Applicat ion Programming Int erface (API) Definit ion 1871 ). There, find detailed information the the "Custom Sensors" tab. Note: Please do not use the folder \Custom Sensors\Powershell Scripts to store your files. This remnant from previous software versions is not used any more and may usually be deleted. Note: When using custom sensors on the Clust er Probe, please copy your files to every cluster node installation. Value Type Define what kind of values your executable or script file gives back. Choose between: Int eger: An integer is expected as return value. If the script gives back a float, PRTG will display the value 0. Float : A float is expected as return value, with a dot (.) between pre-decimal position and decimal places. In this setting, the sensor will also display integer values unless they don't produce a buffer overflow. Count er: Your script returns an integer which increases. PRTG will show the difference between the values of two sensor scans. Note: A counter must return an integer; float is not supported here! Channel Name Enter a name for the channel in which the returned values will be shown. This is for display purposes only. Please enter a string. Enter a string describing the unit of the returned values. This is for display purposes only. Please enter a string.
Unit String
Sensor Settings
On the sensor's details page, click on the Set t ings tab to change settings.
416
19.07.2013
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS Name defined in the settings of the parent device the sensor is created on.
Tags
Priority
Sensor Set t ings EXE/Script Shows the executable or script file that is executed with each sensor scan, as defined on sensor creation. 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 your executable or script file catches command line parameters, you can define them here. Placeholders can be used as well. For a full list of all placeholders please see the API documentation (Applicat ion Programming Int erface (API) Definit ion 1871 ). Note: Please make sure you write the placeholders in quotes to ensure that they are working properly if their values contain blanks. Use single quotation marks ' ' with PowerShell scripts, and double quotes " " with all others. Please enter a string or leave the field empty. 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.
Parameters
Environment
19.07.2013
417
Sensor Set t ings Set placeholders as environment values: From within your executable or script, the values of PRTG's command line parameters will be available via environment variables. For example, you can then read and use the current host value of the PRTG device this EXE/script sensor is created on from within your script. This option can mean a security risk, because also credentials are provided in several variables. For a full list of all available variables please see the API documentation (Applicat ion Programming Int erface (API) Definit ion 1871 ). Security Context Define the Windows user account that will be used to run the executable or script file. Choose between: Use securit y cont ext of probe service: Run the selected file under the same Windows user account the probe is running on. By default, this is the Windows system user account (if not manually changed). Use Windows credent ials of parent device: Use the Windows user account defined in the settings of the parent device this sensor is created on. Please go to sensor's parent device's settings to change these Windows credentials. Mutex Name Define any desired mutex name for the process. All EXE/Script sensors having the same mutex name will be executed serially (not simultaneously). This is useful if you use a lot of sensors and want to avoid high resource usage caused by processes running simultaneously. For links to more information, please see the More 422 section below. Please enter a string or leave the field empty. 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. Shows the expected value type, chosen on sensor creation. 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. Note: The sensor cannot handle string values. Define what shall be done in case the value of this sensor changes. You can choose between: Ignore changes (default ): No action will be taken on change. Trigger 'On Change' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Timeout (sec.)
Value Type
If Value Changes
418
19.07.2013
Sensor Set t ings EXE Result Define what will be done with the result the executable file gives back. Choose between: Discard EX E result : Do not store the requested web page. Writ e EX E result t o disk: Store the last result received from the script with the file name "Result of Sensor [ID].txt" to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section. Writ e EX E result t o disk in case of error: Store the last result received from the script only if the sensor is in a down status. The file name is "Result of Sensor [ID].txt" in the "Logs (Sensors)" directory. Enable this option if you do not want failures to be overwritten by a following success of the script.
Chart Type
19.07.2013
419
Inherited Settings
Maintenance Window
Maintenance End At
420
19.07.2013
Delay (Seconds)
19.07.2013
421
More
Information about custom scripts and executables
422
19.07.2013
Applicat ion Programming Int erface (API) Definit ion Addit ional Sensor Ty pes (Cust om Sensors)
1563
1871
Knowledge Base: What is the Mutex Name in PRTG's EXE/Script Sensor's settings? http://www.paessler.com/knowledgebase/en/topic/6673 Knowledge Base: How and Where Does PRTG Store its Data? http://www.paessler.com/knowledgebase/en/topic/463 Knowledge Base: How can I test if parameters are correctly transmitted to my script when using an EXE/Script sensor? http://www.paessler.com/knowledgebase/en/topic/11283

Notifications
Others
133
section.
19.07.2013
423
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 22 EXE/Script Advanced Sensor
6.8.22 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 Applicat ion Programming Int erface (API) Definit ion 1871 . Note: The executable or script file must be stored on the system of the probe the sensor is created on: If used on a remote probe, the file must be stored on the system running the remote probe. In a cluster setup, please copy the file to every cluster node. Note: If you want to execute a custom Windows Management Instrumentation Query Language (WQL) script, please use the WMI Cust om Sensor 1394 .
Limited to 50 Sensor Channels

PRTG does not support more than 50 sensor channels officially. Depending on the data used with this sensor type, you might exceed the maximum number of supported sensor channels. In this case, PRTG will try to display all sensor channels. However, please be aware that you will experience limited usability and performance.
Add Sensor
Sensor Settings
Basic Sensor Set t ings 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. 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 84 from objects further up in the device tree. Those are not visible here.
Tags
424
19.07.2013
Basic Sensor Set t ings Priority Select a priority for the sensor. This setting determines where the sensor will be placed in sensor 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 Set t ings EXE/Script Select an executable file from the list. It will be executed with every scanning interval. In this list, files in the corresponding /Cust om Sensors/EX EX ML sub-directory of the probe system's PRTG program directory are shown (see Dat a St orage 1912 ). In order for the files to appear in this list, please store them into this folder. Store files ending in BAT, CMD, DLL, EXE, PS1, and VBS. In order for the sensor to show the expected values and sensor status, your files must return the expected XML format to standard output. Values and message must be embedded in the XML. For detailed information on how to build custom sensors and for the expected return format, please see the API documentation (Applicat ion Programming Int erface (API) Definit ion 1871 ). There, find detailed information the the "Custom Sensors" tab. Note: Please do not use the folder \Custom Sensors\Powershell Scripts to store your files. This remnant from previous software versions is not used any more and may usually be deleted. Note: When using custom sensors on the Clust er Probe, please copy your files to every cluster node installation. Parameters If your executable or script file catches command line parameters, you can define them here. Placeholders can be used as well. For a full list of all placeholders please see the API documentation (Applicat ion Programming Int erface (API) Definit ion 1871 ). Note: Please make sure you write the placeholders in quotes to ensure that they are working properly if their values contain blanks. Use single quotation marks ' ' with PowerShell scripts, and double quotes " " with all others. Please enter a string or leave the field empty. 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.
Environment
19.07.2013
425
Sensor Set t ings Set placeholders as environment values: From within your executable or script, the values of PRTG's command line parameters will be available via environment variables. For example, you can then read and use the current host value of the PRTG device this EXE/script sensor is created on from within your script. This option can mean a security risk, because also credentials are provided in several variables. For a full list of all available variables please see the API documentation (Applicat ion Programming Int erface (API) Definit ion 1871 ). Security Context Define the Windows user account that will be used to run the executable or script file. Choose between: Use securit y cont ext of probe service: Run the selected file under the same Windows user account the probe is running on. By default, this is the Windows system user account (if not manually changed). Use Windows credent ials of parent device: Use the Windows user account defined in the settings of the parent device this sensor is created on. Please go to sensor's parent device's settings to change these Windows credentials. Mutex Name Define any desired mutex name for the process. All EXE/Script sensors having the same mutex name will be executed serially (not simultaneously). This is useful if you use a lot of sensors and want to avoid high resource usage caused by processes running simultaneously. For links to more information, please see the More 430 section below. Please enter a string or leave the field empty. 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. Define what will be done with the results the executable file gives back. Choose between: Discard EX E result : Do not store the requested web page. Writ e EX E result t o disk: Store the last result received from the script with the file name "Result of Sensor [ID].txt" to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section. Writ e EX E result t o disk in case of error: Store the last result received from the script only if the sensor is in a down status. The file name is "Result of Sensor [ID].txt" in the "Logs (Sensors)" directory. Enable this option if you do not want failures to be overwritten by a following success of the script.
Timeout (sec.)
EXE Result
426
19.07.2013
Chart Type
Note: The St ack Unit option for stacking graphs will only work if you explicitly define the same <unit> for at least two channels. For detailed information about sensor settings please see the API documentation (Applicat ion Programming Int erface (API) Definit ion 1871 ).
Inherited Settings
19.07.2013
427
Schedules, Dependencies, and Maint enance Window Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings. Schedule Select a schedule from the list. Schedules can be used to monitor for a certain time span (days, hours) throughout the week. With the period list option it is also possible to pause monitoring for a specific time span. You can create new schedules and edit existing ones in the account settings 1678 . Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active. Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between: Not set (monit or cont inuously ): No maintenance window will be set. Set up a one-t ime maint enance window: Pause monitoring within a maintenance window. Maintenance Begins At This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window. This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window. 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.
Maintenance Window
Maintenance End At
Dependency Type
428
19.07.2013
Schedules, Dependencies, and Maint enance Window Mast er object for parent : Make this sensor the master object for its parent device. The sensor will influence the behavior of the device it is created on: If the sensor is in a Down status, the device will be paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor will be paused if the parent group of its parent device is in a Down status, or if it is paused by another dependency. Note: Testing your dependencies is easy! Simply choose Simulat e Error St at us from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused. Dependency This field is only visible if the select object option is enabled above. Click on the reading-glass symbol and use the object selector 143 to choose an object on which the current sensor will be dependent on. Define a time span. After the master object for this dependency comes back to an Up status, monitoring of the depending objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds. Note: This setting is not available if you choose this sensor to be the Mast er object for parent . In this case, please define delays in the parent Device Set t ings 261 or the superior Group Set t ings 242 .
Delay (Seconds)
19.07.2013
429
More
430
19.07.2013
1563
1871

Notifications
Others
133
section.
19.07.2013
431
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 23 File Sensor
6.8.23 File Sensor

The File sensor monitors a file located on the probe's local disk, or a file accessible via Server Message Block (SMB). You can monitor file content and file time stamp changes. The sensor shows the file size, and a last modified value in days and hours.
Add Sensor
Sensor Settings
Tags
Priority
432
07.02.2013
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. Specify when the sensor will send an alert. Choose between: File exist s: The sensor will send an alert if the file does not exist. File does not exist : The sensor will send an alert if the file exists. Monitor File Content Specify if the sensor will send a change notification when the content of the file changes (based on a checksum). Choose between: Ignore changes: No action will be taken on change. Trigger 'change' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 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' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Check If
Chart Type
07.02.2013
433
Inherited Settings
Schedules, Dependencies, and Maint enance Window Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings. Schedule Select a schedule from the list. Schedules can be used to monitor for a certain time span (days, hours) throughout the week. With the period list option it is also possible to pause monitoring for a specific time span. You can create new schedules and edit existing ones in the account settings 1678 . Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active.
434
07.02.2013
Schedules, Dependencies, and Maint enance Window Maintenance Window Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between: Not set (monit or cont inuously ): No maintenance window will be set. Set up a one-t ime maint enance window: Pause monitoring within a maintenance window. Maintenance Begins At This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window. This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window. 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. Mast er object for parent : Make this sensor the master object for its parent device. The sensor will influence the behavior of the device it is created on: If the sensor is in a Down status, the device will be paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor will be paused if the parent group of its parent device is in a Down status, or if it is paused by another dependency. Note: Testing your dependencies is easy! Simply choose Simulat e Error St at us from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused. Dependency This field is only visible if the select object option is enabled above. Click on the reading-glass symbol and use the object selector 143 to choose an object on which the current sensor will be dependent on.
Maintenance End At
Dependency Type
07.02.2013
435
Schedules, Dependencies, and Maint enance Window Delay (Seconds) Define a time span. After the master object for this dependency comes back to an Up status, monitoring of the depending objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds. Note: This setting is not available if you choose this sensor to be the Mast er object for parent . In this case, please define delays in the parent Device Set t ings 261 or the superior Group Set t ings 242 .
436
07.02.2013
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

Notifications
Others
133
section.
07.02.2013
437
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 24 File Content Sensor
6.8.24 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. Note: This sensor does not support UTF-16 encoded files! In this case, please try to use a custom sensor like the EX E/Script Sensor 415 or the EX E/Script Advanced Sensor 424 . Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.
Add Sensor
Sensor Settings
Tags
Priority
438
08.10.2013
Sensor Set t ings 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. Define the string inside the log file you would like to check for. The input is not case-sensitive. Please enter a string. 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 st ring search: Search for a simple string. Regular Expression: Search using a regular expression. For more details, see Regular Expressions 1886 section. Warning Behaviour Define under which condition the sensor will show a Warning status. Choose between: Got o warning st at e when st ring is not found: The sensor will show a Warning status if there is no match. Otherwise it will remain in Up status. Got o warning st at e when st ring is found: The sensor will show a Warning status if there is a match. Otherwise it will remain in Up status. If Value Changes Define what 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' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Search String
Search Method
08.10.2013
439
Chart Type
Inherited Settings
440
08.10.2013
Maintenance Window
Maintenance End At
Dependency Type
08.10.2013
441
Delay (Seconds)
442
08.10.2013

Notifications
Others
133
section.
08.10.2013
443
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 25 Folder Sensor
6.8.25 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
Sensor Settings
Tags
Priority
444
13.06.2013
Folder Monit or 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. Specify if subfolders will be included in the monitoring. Choose between: Do not recurse sub-folders: Only monitor the folder specified above; do not monitor its subfolders. Monit or t he folder and it s sub-folders (use wit h caut ion!): Monitor the folder specified above and all of its subfolders. Note: Recursing sub-folders in large directories with a high number of branches may evoke timeout errors or performance issues. Monitor Folder Changes 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' not ificat ion: The sensor will trigger a change notification if a file changes its timestamp or filename, or if there are new or deleted files. Check of File Ages Specify if the sensor will monitor the folder for certain file ages. Choose between: Don't check: Do not check for the age of the files in the specified folder(s). Show Warning if older: Set the sensor to warning status if one of the files in the specified folder is older than a specific time unit. Show Error if older: Set the sensor to error status if one of the files in the specified folder is older than a specific time unit. Show Warning if y ounger: Set the sensor to warning status if one of the files in the specified folder is younger than a specific time unit. Show Error if y ounger: Set the sensor to error status if one of the files in the specified folder is younger than a specific time unit. File Age Limit 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. 445 This field is only visible if a file age check is enabled above. Specify the unit for the file age value you entered above. Choose between:
Sub-Folder Recursion
13.06.2013
File Age Limit Unit
Chart Type
Inherited Settings
446
13.06.2013
Maintenance Window
Maintenance End At
Dependency Type
13.06.2013
447
Delay (Seconds)
448
13.06.2013
More

Notifications
Others
133
section.
13.06.2013
449
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 26 FTP Sensor
6.8.26 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
Sensor Settings
Tags
Priority
Sensor 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. 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.
Port
450
27.11.2012
Sensor Specific FTP Mode Specify which ftp mode will be used for the connection. Choose between: Use act ive mode Use passive mode We recommend using the default value. If you do not get a connection, please try the passive mode.
Aut hent icat ion Username Enter a username for the FTP login. Please enter a string or leave the field empty. Enter a password for the FTP login. Please enter a string or leave the field empty. 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 Result Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results. Writ e sensor result t o disk (Filename: "Result of Sensor (ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Password
TLS (Transport-LevelSecurity)
Sensor Display Primary Channel Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel will always be displayed underneath the sensor's name. The available options depend on what channels are available for this sensor. Note: You can set another primary channel later by clicking on the pin symbol of a channel in the sensor's overview tab.
27.11.2012
451
Sensor Display Chart Type Define how different channels will be shown for this sensor. Show channels independent ly (default ): Show an own graph for each channel. St ack channels on t op of each ot her: Stack channels on top of each other to create a multi-channel graph. This will generate an easy-to-read graph which visualizes the different components of your total traffic. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 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
452
27.11.2012
Maintenance End At
Dependency Type
27.11.2012
453

454
27.11.2012
Notifications
Others
133
section.
27.11.2012
455
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 27 FTP Server File Count Sensor
6.8.27 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. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Add Sensor
Sensor Set t ings 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
456
07.02.2013
Tags
Priority
Sensor Set t ings FTP URL Enter the URL to check (this sensor does not use the IP Address/ DNS value of the parent device). Define the username for the login. Please enter a string. Define the password for the login. Please enter a string. Define if only new files will be counted. Choose between: No : Always show the total number of files. Yes: Show the number of new files since the last scanning interval. Note: With the next sensor scan, any new files from the previous scan will be regarded as old. 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' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Username Password Count Only New Files
07.02.2013
457
Chart Type
Inherited Settings
458
07.02.2013
Maintenance Window
Maintenance End At
Dependency Type
07.02.2013
459
Delay (Seconds)
460
07.02.2013

Notifications
Others
133
section.
07.02.2013
461
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 28 Google Analytics Sensor
6.8.28 Google Analy tics Sensor

The Google Analytics sensor queries data from a Google Analytics account via Hypertext Transfer Protocol (HTTP). It shows the values for different metrics in different sensor channels. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Add Sensor
Sensor Settings
Tags
462
13.06.2013
Google Analy t ics Set t ings Period (Interval) Enter how often the sensor will query data. Choose between: 1 Day 2 Day s 3 Day s 1 Week Username Please enter the username of the Google Analytics account you want to query. Please enter a string. Please enter the password of the Google Analytics account you want to query. Please enter a string. Enter the 8-digits profile ID of the Google Analytics account. For help, please see More 467 section below. Enter a comma separated list with all metrics you want to query. A default set of metrics is already predefined. For help, please see More 467 section below. Define for how many days the sensor will query data. Enter 1 to query yesterday's data only, or define any number of days. Please enter an integer value. Define if the sensor will query averaged data. Select between: Use: Query averaged data. This setting only takes effect if your entered more than "1" in the Day s setting above. Data will be averaged over the number of days. Don't use: Do not query averaged data, but receive raw data.
Password
Profile ID
Metrics
Days
Average
13.06.2013
463
Chart Type
Inherited Settings
By default, all following settings are inherited from objects higher in the hierarchy and should be changed there, if necessary. Often, best practice is to change them centrally in the Root 213 group's settings. To change a setting for this object, disable inheritance by clicking on the check mark symbol in front of the respective setting name. You will then see the options described below. Note: For Google Analytics sensors, the scanning interval cannot be inherited. Please use the individual settings of the sensor to define the interval in which data is received. Schedules, Dependencies, and Maint enance Window Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings.
464
13.06.2013
Maintenance Window
Maintenance End At
Dependency Type
13.06.2013
465
Delay (Seconds)
466
13.06.2013
Name
Port
User
Password
More
Knowledge Base: Where do I find my Google Analytics profile ID? http://www.paessler.com/knowledgebase/en/topic/35363 Knowledge Base: Where do I find available Google Analytics metrics?
13.06.2013
467

Notifications
Others
133
section.
468
13.06.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 29 HTTP Sensor
6.8.29 HTTP Sensor

The HTTP sensor monitors a web server using Hypertext Transfer Protocol (HTTP). It shows the loading time. This is the easiest way to monitor if a website (or a specific website element) is reachable.
Add Sensor
Sensor Settings
Tags
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.
08.10.2013
469
HTTP Specific URL Please enter the URL the sensor will connect to. If you enter an absolute URL, this address will be independent from the IP address/DNS name setting of the device this sensor is created on. You can enter an URL leading to a webpage (to measure the page source code's loading time), or enter the URL of an image or of another page asset to measure this element's availability and loading time. PRTG uses a smart URL replacement which allows you to use the parent device's IP address/DNS name setting as part of the URL. For more information, please see section Smart URL Replacement below. The request method determines how the given URL is requested. GET: Request the website directly, like browsing the web. We recommend using this setting for a simple check of a web page. POST: Send post form data to the URL. If this setting is chosen, you must enter the data that will be sent in the Post dat a field below. HEAD: Only request the HTTP header from the server; without the actual web page. Although this saves bandwidth since less data is transferred, it is not recommended because the measured request time is not the one experienced by your users and you might not be notified for slow results or timeouts. Postdata This field is only visible when POST is selected in the Request Met hod setting above. Please enter the data part for the POST request here. Note: No XML is allowed here! This setting is only visible when POST is selected in the Request Met hod setting above. Define the content type of a POST request. Choose between: Default (applicat ion/x-www-form-urlencoded): This is the default content type used to encode the form data set for submission to the server. Cust om: If you need another content type than default, enter this content type below. Custom Content Type This field is only visible when Cust om is selected above. Define the content type which is needed, e.g., XML, JSON, HTTP.
Request Method
Content Type
SSL Specific SSL Method This setting is relevant only when using https in the URL field. We recommend using the default value. If you experience connection problems, please select another SSL method from the list. Choose between:
470
08.10.2013
SSL Specific SSL V2 SSL V2 or V3: This is the default setting. SSL V3 TLS V1 Note: Other TLS versions are not supported. Note: This sensor type implicitly supports Server Name Identification (SNI), an extension to the TLS protocol. Sensor Display Primary Channel Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel will always be displayed underneath the sensor's name. The available options depend on what channels are available for this sensor. Note: You can set another primary channel later by clicking on the pin symbol of a channel in the sensor's overview tab. Define how different channels will be shown for this sensor. Show channels independent ly (default ): Show an own graph for each channel. St ack channels on t op of each ot her: Stack channels on top of each other to create a multi-channel graph. This will generate an easy-to-read graph which visualizes the different components of your total traffic. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 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.
Chart Type
Inherited Settings
08.10.2013
471
Name
Port
User
Password
472
08.10.2013
Maintenance End At
Dependency Type
08.10.2013
473
474
08.10.2013
Smart URL Replacement

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

Notifications
Others
133
section.
08.10.2013
475
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 30 HTTP Advanced Sensor
6.8.30 HTTP Advanced Sensor

The HTTP Advanced sensor monitors the source code of a web page using Hypertext Transfer Protocol (HTTP). It supports authentication, content checks, and other advanced parameters. It shows the loading time, bytes received, download bandwidth (speed), and time to first byte.
Add Sensor
Sensor Settings
Tags
Priority
476
08.10.2013
HTTP Specific URL Please enter the URL the sensor will connect to. If you enter an absolute URL, this address will be independent from the IP address/DNS name setting of the device this sensor is created on. You can enter an URL leading to a webpage (to measure the page source code's loading time), or enter the URL of an image or of another page asset to measure this element's availability and loading time. PRTG uses a smart URL replacement which allows you to use the parent device's IP address/DNS name setting as part of the URL. For more information, please see section Smart URL Replacement below. The request method determines how the given URL is requested. GET: Request the website directly, like browsing the web. We recommend using this setting for a simple check of a web page. POST: Send post form data to the URL. If this setting is chosen, you must enter the data that will be sent in the Post dat a field below. HEAD: Only request the HTTP header from the server; without the actual web page. Although this saves bandwidth since less data is transferred, it is not recommended because the measured request time is not the one experienced by your users and you might not be notified for slow results or timeouts. Postdata This field is only visible when POST is selected in the Request Met hod setting above. Please enter the data part for the POST request here. Note: No XML is allowed here! This setting is only visible when POST is selected in the Request Met hod setting above. Define the content type of a POST request. Choose between: Default (applicat ion/x-www-form-urlencoded): This is the default content type used to encode the form data set for submission to the server. Cust om: If you need another content type than default, enter this content type below. Custom Content Type This field is only visible when Cust om is selected above. Define the content type which is needed, e.g., XML, JSON, HTTP.
Request Method
Content Type
Sensor Specific Method Used If you encounter unexpected errors with the standard method that is used to monitor an URL, try to use the compatibility mode which is based on .Net (introduced in PRTG v13.x.7). Choose between:
08.10.2013
477
Sensor Specific Use St andard Met hod (recommended): This is the default monitoring method for this sensor type. Use Compat ibilit y Mode: Try this method as an alternative for websites that do not work with the default approach. Using the compatibility mode, this sensor will execute an external exe. Thus, this method will need more resources, but it can be helpful in particular cases. Note: If you select the compatibility mode, the options for the SSL method will be slightly different. You can also check for trusted certificates. Please see below.
SSL Specific SSL Method This setting is relevant only when using https in the URL field. We recommend using the default value. If you experience connection problems, please select another SSL method from the list. Choose between: SSL V2 SSL V2 or V3: This is the default setting. SSL V3 TLS V1 Note: Other TLS versions are not supported.
SSL Specific (when using Compat ibilit y Mode) SSL Method When using the compatibility mode, the SSL specific settings are a bit different to the default SSL settings. SSL V2 is not available. You can choose between: SSL V3 TLS V1 SSL V3 or TLS V1: This is the default setting. Check SSL Certificates Specify if the certificate of the monitored URL will be checked. Choose between: Do not check used cert ificat es: This the default setting. Check if t he used cert ificat es are t rust ed: If the certificate of the server is not trusted, the sensor will go into a Down status and display a corresponding message.
478
08.10.2013
Note: This sensor type implicitly supports Server Name Identification (SNI), an extension to the TLS protocol.
Advanced Sensor Dat a Protocol Version Define the HTTP protocol version that will be used when connecting to the URL. Choose between: HTTP 1.0 HTTP 1.1: This is the default setting. User Agent Choose which user agent string will be sent by this sensor when connecting to the URL defined above. Choose between: Use PRTG's Default St ring : Do not enter a specific user agent, use default setting. Usually, this is: Mozilla/5.0 (compatible; PRTG Network Monitor (www.paessler.com); Windows) Use a Cust om St ring : Use a custom user agent. Define below. Custom User Agent This field is only visible if custom user agent is enabled above. Enter a string which will be used as user agent when connecting to the URL specified above. Define what will be done in case the content of the monitored web page (element) changes. You can choose between: Ignore changes: No action will be taken on change. Trigger 'change' not ificat ion: The sensor will send an internal message indicating that the web page content has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the web page content changes. Check For Existing Key Words (Positive) Define whether the the result at the configured URL will be checked for keywords. Choose between: Disable: Do not search for keywords. Enable key word check (posit ive): 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 1886 . 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.
Content Changes
08.10.2013
479
Advanced Sensor Dat a 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 1886 . Check For Existing Key Words (Negative) Define whether the the result at the configured URL will be checked for keywords. Choose between: Disable: Do not search for keywords. Enable key word check (negat ive): In the result returned at the URL, check if a key word does not exist. 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 1886 . If the data does include this string, the sensor will be set to an error state. Please enter a string. 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 1886 . 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. 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.
For Key Word Search Use
Result Handling
480
08.10.2013
Advanced Sensor Dat a St ore lat est HTML result : Store the last result of the requested web page to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes, especially in combination with content checks. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Note: This sensor loads the source code at the given URL. If you set up a content check, only this source code is checked for the keywords. The code is not necessarily identical to the one used to display the page when opening the same URL in a web browser, as there may be a reload configured or certain information may be inserted after loading, e.g. via Javascript. PRTG does not follow links to embedded objects nor does it execute scripts. Only the first page at the given URL is loaded and checked against the expressions configured. For debugging, please use the Result option to write the source code file to disk and look up what exactly PRTG gets when calling the URL. If the URL configured does not point to a web page, but to a binary file, for example, to an image, you usually won't check for content. Aut hent icat ion Authentication Define if the web page at the configured URL need authentication. Choose between: No aut hent icat ion needed Web page needs aut hent icat ion User This field is only visible if authentication is enabled above. Enter a username. Please enter a string. This field is only visible if authentication is enabled above. Enter a password. Please enter a string. This field is only visible if authentication is enabled above. Please select the authentication method the given URL is protected with. Choose between: Basic access aut hent icat ion (HTTP): Use simple HTTP authentication. This is the default setting and suitable for most cases. Note: This authentication method will transmit credentials as plain text! Windows NT LAN Manager (NTLM): Use the Microsoft NTLM protocol for authentication. This is sometimes used in Intranets for single sign-on. We recommend using the default value.
Password
Authentication Method
08.10.2013
481
Chart Type
Inherited Settings
482
08.10.2013
Name
Port
User
Password
08.10.2013
483
Maintenance End At
Dependency Type
484
08.10.2013
08.10.2013
485

More
Knowledge Base: Which user agent should I use in the HTTP Advanced sensor's settings? http://www.paessler.com/knowledgebase/en/topic/30593
486
08.10.2013

Notifications
Others
133
section.
08.10.2013
487
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 31 HTTP Apache ModStatus PerfStats Sensor
6.8.31 HTTP Apache M odStatus PerfStats Sensor

The HTTP Apache ModStatus PerfStats sensor monitors performance statistics of an Apache web server using mod_status over HTTP. It can show the CPU load, the uptime (in seconds), the requests per second, the bytes per request, and the number of current busy and idle worker threads of the Apache at scan time.
Add Sensor
Sensor Settings
Tags
Priority
488
08.10.2013
HTTP Specific URL Please enter the URL to the mod_status module on your Apache server; PRTG will append a "/server_status?auto" part automatically. If you enter an absolute URL, this address will be independent from the IP address/DNS name setting of the device this sensor is created on. PRTG uses a smart URL replacement which allows you to use the parent device's IP address/DNS name setting as part of the URL. For more information, please see section Smart URL Replacement below.
SSL Specific SSL Method This setting is relevant only when using https in the URL field. We recommend using the default value. If you experience connection problems, please select another SSL method from the list. Choose between: SSL V2 SSL V2 or V3: This is the default setting. SSL V3 TLS V1 Note: Other TLS versions are not supported. Note: This sensor type implicitly supports Server Name Identification (SNI), an extension to the TLS protocol. Aut hent icat ion Authentication Define if the web page at the configured URL need authentication. Choose between: No aut hent icat ion needed Web page needs aut hent icat ion User This field is only visible if authentication is enabled above. Enter a username. Please enter a string. This field is only visible if authentication is enabled above. Enter a password. Please enter a string. This field is only visible if authentication is enabled above. Please select the authentication method the given URL is protected with. Choose between:
Password
08.10.2013
489
Aut hent icat ion Basic access aut hent icat ion (HTTP): Use simple HTTP authentication. This is the default setting and suitable for most cases. Note: This authentication method will transmit credentials as plain text! Windows NT LAN Manager (NTLM): Use the Microsoft NTLM protocol for authentication. This is sometimes used in Intranets for single sign-on. We recommend using the default value.
Chart Type
Inherited Settings
490
08.10.2013
Name
Port
User
Password
08.10.2013
491
Maintenance End At
Dependency Type
492
08.10.2013
08.10.2013
493


Notifications
Others
133
section.
494
08.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 32 HTTP Apache ModStatus Totals Sensor
6.8.32 HTTP Apache M odStatus Totals Sensor

The HTTP Apache ModStatus Totals sensor monitors accesses and transfered data (in kBytes) of an Apache web server using mod_status over HTTP.
Add Sensor
Sensor Settings
Tags
Priority
08.10.2013
495
HTTP Specific URL Please enter the URL to the mod_status module on your Apache server; PRTG will append a "/server_status?auto" part automatically. If you enter an absolute URL, this address will be independent from the IP address/DNS name setting of the device this sensor is created on. PRTG uses a smart URL replacement which allows you to use the parent device's IP address/DNS name setting as part of the URL. For more information, please see section Smart URL Replacement below.
SSL Specific SSL Method This setting is relevant only when using https in the URL field. We recommend using the default value. If you experience connection problems, please select another SSL method from the list. Choose between: SSL V2 SSL V2 or V3: This is the default setting. SSL V3 TLS V1 Note: Other TLS versions are not supported. Note: This sensor type implicitly supports Server Name Identification (SNI), an extension to the TLS protocol. Aut hent icat ion Authentication Define if the web page at the configured URL need authentication. Choose between: No aut hent icat ion needed Web page needs aut hent icat ion User This field is only visible if authentication is enabled above. Enter a username. Please enter a string. This field is only visible if authentication is enabled above. Enter a password. Please enter a string. This field is only visible if authentication is enabled above. Please select the authentication method the given URL is protected with. Choose between:
Password
496
08.10.2013
Aut hent icat ion Basic access aut hent icat ion (HTTP): Use simple HTTP authentication. This is the default setting and suitable for most cases. Note: This authentication method will transmit credentials as plain text! Windows NT LAN Manager (NTLM): Use the Microsoft NTLM protocol for authentication. This is sometimes used in Intranets for single sign-on. We recommend using the default value.
Chart Type
Inherited Settings
08.10.2013
497
Name
Port
User
Password
498
08.10.2013
Maintenance End At
Dependency Type
08.10.2013
499
500
08.10.2013


Notifications
Others
133
section.
08.10.2013
501
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 33 HTTP Content Sensor
6.8.33 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 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page: HTTP Specific Value Type Define what kind of values your HTML file gives back. Choose between: Int eger: An integer is expected as return value. Float : A float is expected as return value, with a dot (.) between pre-decimal position and decimal places. In this setting, the sensor will also display integer values unless they don't produce a buffer overflow. Note: The sensor cannot handle string values. Number of Channels Define how many values your HTML file gives back. Each value will be handled in its own sensor channel. Each value must be placed between square brackets [ ]. Enter the number of bracket-value pairs that will be returned at the defined URL. Note: Do not enter a number less than the number of values returned. Otherwise you will get an error message.
Sensor Settings
502
08.10.2013
Tags
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. Please enter the URL the sensor will connect to. If you enter an absolute URL, this address will be independent from the IP address/DNS name setting of the device this sensor is created on. PRTG uses a smart URL replacement which allows you to use the parent device's IP address/DNS name setting as part of the URL. For more information, please see section Smart URL Replacement below. 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.
Script URL
Value Type
SSL Specific SSL Method This setting is relevant only when using https in the URL field. We recommend using the default value. If you experience connection problems, please select another SSL method from the list. Choose between: SSL V2 SSL V2 or V3: This is the default setting. SSL V3
08.10.2013
503
SSL Specific TLS V1 Note: Other TLS versions are not supported. Note: This sensor type implicitly supports Server Name Identification (SNI), an extension to the TLS protocol.
Advanced Sensor Dat a 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. Trigger 'change' not ificat ion: The sensor will send an internal message indicating that the web page content has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the web page content changes. Sensor Result Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results. Writ e sensor result t o disk (Filename: "Result of Sensor (ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Aut hent icat ion Authentication Define if the web page at the configured URL need authentication. Choose between: No aut hent icat ion needed Web page needs aut hent icat ion User This field is only visible if authentication is enabled above. Enter a username. Please enter a string. This field is only visible if authentication is enabled above. Enter a password. Please enter a string.
Password
504
08.10.2013
Aut hent icat ion Authentication Method This field is only visible if authentication is enabled above. Please select the authentication method the given URL is protected with. Choose between: Basic access aut hent icat ion (HTTP): Use simple HTTP authentication. This is the default setting and suitable for most cases. Note: This authentication method will transmit credentials as plain text! Windows NT LAN Manager (NTLM): Use the Microsoft NTLM protocol for authentication. This is sometimes used in Intranets for single sign-on. We recommend using the default value.
Chart Type
08.10.2013
505
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
506
08.10.2013
Name
Port
User
Password
08.10.2013
507
Maintenance End At
Dependency Type
508
08.10.2013
08.10.2013
509

More
Knowledge Base article: How can I monitor internal values of a web application with PRTG? http://www.paessler.com/knowledgebase/en/topic/4

Notifications
Others
133
section.
510
08.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 34 HTTP Full Web Page Sensor
6.8.34 HTTP Full Web Page Sensor

The HTTP Full Web Page sensor monitors the full download time of a web page including assets such as images etc. In the background, it opens the web page in a browser instance to perform the measurement. Links are not followed. The sensor shows the loading time of the full page. Note: Be careful with this sensor, as it can generate considerable internet traffic if used with a low scanning interval! Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.
Add Sensor
Sensor Settings
Tags
Priority
07.02.2013
511
Full Page Download Set t ings 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. Please enter the URL the sensor will load. If you enter an absolute URL, this address will be independent from the IP address/DNS name setting of the device this sensor is created on. PRTG uses a smart URL replacement which allows you to use the parent device's IP address/DNS name setting as part of the URL. For more information, please see section Smart URL Replacement below. Define which browser will be used to load the web page. Choose between: Chromium (recommended): Use the "WebKit" engine that is delivered with PRTG to perform the loading test. With each scanning interval, PRTG will load the URL defined above in an instance of "Chromium" and measure the time until the page is fully loaded. This is the recommended setting. Phant omJS (Headless Webkit ): Use the "PhantomJS" engine. This engine can have a high impact on your probe system's CPU and memory load, but there are additional options for result handling available (see below). Int ernet Explorer: With each scanning interval, the URL defined above is loaded in the background in an instance of Internet Explorer. PRTG uses the Internet Explorer of the system running the PRTG probe. Note: For full functionality we strongly recommend installing Internet Explorer 8 or higher on the system running the PRTG probe. The probe machine is either the local system (on every node, if on a cluster probe), or the system running the remote probe 1888 on which the sensor is created on. Note: For all browser engines, the same proxy settings are used that are configured for the Windows user account the PRTG probe is running on (this is usually the Windows local "system" user account, if not changed). Those settings are accessible via the Internet Explorer of this system. If you want to e.g. use a proxy for this full web page sensor test, please adjust the Internet Explorer's settings accordingly (on the computer running the probe; on all nodes, if in a cluster). Security Context Define the Windows user account that will be used to run the browser engine. Choose between: Use securit y cont ext of probe service (default ): Run the browser engine under the same Windows user account the probe is running on. By default, this is the local Windows "system" user account (if not manually changed).
URL
Browser Engine
512
07.02.2013
Full Page Download Set t ings Use Windows credent ials of parent device: Use the Windows user account defined in the settings of the parent device this sensor is created on. Please go to the sensor's parent device's settings to change the Windows credentials. Note: When using the Chromium browser engine above, this is the recommended setting here. Result Handling This setting is only visible if the PhantomJS engine is selected above. This browser engine can render and store screenshots of the loaded web page. Choose between: Discard loaded web page (recommended): Do not store the requested web page. St ore lat est screenshot of t he web page: Render and store the last result of the web page to the "Logs (Sensors)" directory (on the remote system, when used on a remote probe; on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. It will be named after the pattern "Fullpage of Sensor (ID).jpg". For information on how to find the folder used for storage, please see Dat a St orage 1912 section. St ore ongoing screenshot s of t he web page (use wit h caut ion!): Render and store one new screenshot of the web page with each sensor scan, and store the pictures in the "Screenshots (Fullpage Sensor)" directory (on the remote system, when used on a remote probe). For information on how to find the folder used for storage, please see Dat a St orage 1912 section. This option can be used to create a visual history of the web page. Note: Depending on the monitored website and the scanning interval of the sensor, a very high amount of data can be created! Use with care, and make sure you set appropriate data purging limits in the Sy st em Administ rat ionSy st em and Websit e 1695 settings.
Inherited Settings
07.02.2013
513
Maintenance Window
Maintenance End At
Dependency Type
514
07.02.2013
Delay (Seconds)
07.02.2013
515
More
Knowledge Base: What to do when I see a CreateUniqueTempDir() error message for my HTTP Full Webpage Sensor? http://www.paessler.com/knowledgebase/en/topic/40783

Notifications
516
07.02.2013
Others
133
section.
07.02.2013
517
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 35 HTTP SSL Certificate Expiry Sensor
6.8.35 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. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Add Sensor
Sensor Settings
Tags
518
07.02.2013
Sensor Set t ings URL Enter the absolute URL to check (this sensor does not use the IP Address/DNS value of the parent device). Define if you want to allow SSL V3 only for connections to the URL configured above. Choose between: No Yes
Force SSL V3
Name
Port
User
Password
07.02.2013
519
Chart Type
Inherited Settings
520
07.02.2013
Maintenance Window
Maintenance End At
Dependency Type
07.02.2013
521
Delay (Seconds)
522
07.02.2013

Notifications
Others
133
section.
07.02.2013
523
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 36 HTTP Transaction Sensor
6.8.36 HTTP Transaction Sensor

The HTTP Transaction sensor monitors an interactive website, such as a web shop, by performing a transaction using a set of Hypertext Transfer Protocol (HTTP) URLs. The sensor monitors whether logins or shopping carts work properly. It returns the loading time.
Add Sensor
Sensor Settings
Tags
Priority
HTTP Specific 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. 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.
Single URL Timeout (seconds)
524
08.10.2013
Sensor Specific Method Used If you encounter unexpected errors with the standard method that is used to monitor an URL, try to use the compatibility mode which is based on .Net (introduced in PRTG v13.x.7). Choose between: Use St andard Met hod (recommended): This is the default monitoring method for this sensor type. Use Compat ibilit y Mode: Try this method as an alternative for websites that do not work with the default approach. Using the compatibility mode, this sensor will execute an external exe. Thus, this method will need more resources, but it can be helpful in particular cases. Note: If you select the compatibility mode, the options for the SSL method will be slightly different. You can also check for trusted certificates. Please see below.
SSL Specific SSL Method This setting is relevant only when using https in the URL field. We recommend using the default value. If you experience connection problems, please select another SSL method from the list. Choose between: SSL V2 SSL V2 or V3: This is the default setting. SSL V3 TLS V1 Note: Other TLS versions are not supported.
SSL Specific (when using Compat ibilit y Mode) SSL Method When using the compatibility mode, the SSL specific settings are a bit different to the default SSL settings. SSL V2 is not available. You can choose between: SSL V3 TLS V1 SSL V3 or TLS V1: This is the default setting. Check SSL Certificates Specify if the certificate of the monitored URL will be checked. Choose between: Do not check used cert ificat es: This the default setting.
08.10.2013
525
SSL Specific (when using Compat ibilit y Mode) Check if t he used cert ificat es are t rust ed: If the certificate of the server is not trusted, the sensor will go into a Down status and display a corresponding message.
Note: This sensor type implicitly supports Server Name Identification (SNI), an extension to the TLS protocol.
Advanced Sensor Dat a 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. 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. St ore lat est HTML result : Store the last result of the requested web page to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes, especially in combination with content checks. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Cookie Management
Aut hent icat ion Authentication Define if the web page at the configured URL need authentication. Choose between: No aut hent icat ion needed Web page needs aut hent icat ion User This field is only visible if authentication is enabled above. Enter a username. Please enter a string.
526
08.10.2013
Aut hent icat ion Password This field is only visible if authentication is enabled above. Enter a password. Please enter a string. This field is only visible if authentication is enabled above. Please select the authentication method the given URL is protected with. Choose between: Basic access aut hent icat ion (HTTP): Use simple HTTP authentication. This is the default setting and suitable for most cases. Note: This authentication method will transmit credentials as plain text! Windows NT LAN Manager (NTLM): Use the Microsoft NTLM protocol for authentication. This is sometimes used in Intranets for single sign-on. We recommend using the default value.
Transact ion 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 115 . Using this mechanism you can set up an extended monitoring with multiple URLs. Please enter settings for at least one transaction URL. You can use as many steps as needed and disable the other steps. Transaction Step #x This setting is available for URL #2 through #10. Define if you want to use this step for your transaction check. Choose between: Disable st ep #x: Do not use this step. Choose this option if you do not need all 10 steps for your transaction check. Enable st ep #x: Enable this step. Further options will be viewed, as described below. URL Please enter the URL the sensor will connect to. If you enter an absolute URL, this address will be independent from the IP address/DNS name setting of the device this sensor is created on. PRTG uses a smart URL replacement which allows you to use the parent device's IP address/DNS name setting as part of the URL. For more information, please see section Smart URL Replacement below. 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.
Request Method
08.10.2013
527
Transact ion 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 Post dat a field below. HEAD: Only request the HTTP header from the server; without the actual web page. Although this saves bandwidth since less data is transferred, it is not recommended because the measured request time is not the one experienced by your users and you might not be notified for slow results or timeouts. Postdata This field is only active when POST is selected in the Request Met hod setting above. Please enter the data part for the post request here. Note: No XML is allowed here! Define whether the the result at the configured URL will be checked for keywords. Choose between: Disable: Do not search for keywords. Enable key word check (posit ive): 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 Words (Negative) Define whether the the result at the configured URL will be checked for keywords. Choose between: Disable: Do not search for keywords. Enable key word check (negat ive): In the result returned at the URL, check if a key word does not exist. Response must not include Define which string must not be part of the web at the given URL. If the data does include this string, the sensor will be set to an error state. Please enter a string. Note: Only simple text search is available here. The characters * and ? work here as placeholder, whereas * stands for no or any number of characters and ? stands for exactly one character (as known from Windows search). This behavior cannot be disabled, so the literal search for these characters is not possible.
Check For Existing Key Words (Positive)
528
08.10.2013
Inherited Settings
By default, all following settings are inherited from objects higher in the hierarchy and should be changed there, if necessary. Often, best practice is to change them centrally in the Root 213 group's settings. To change a setting for this object, disable inheritance by clicking on the check mark symbol in front of the respective setting name. You will then see the options described below. Proxy Set t ings for HTTP Sensors HTTP Proxy Settings The proxy settings determine how a sensor connects to a given URL. You can enter data for a proxy server that will be used when connecting via HTTP or HTTPS. Note: This setting is valid for the monitoring only and determines the behavior of sensors. In order to change proxy settings for the core server, please see Sy st em Administ rat ionSy st em and Websit e 1698 . Enter the IP address or DNS name of the proxy server to use. If you leave this field empty, no proxy will be used. Enter the port number of the proxy. Often, port 8080 is used. Please enter an integer value. 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. 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.
Name
Port
User
Password
08.10.2013
529
Maintenance Window
Maintenance End At
Dependency Type
530
08.10.2013
Delay (Seconds)
08.10.2013
531

More
Knowledge Base: Configuration Tips for HTTP Transaction Sensors needed http://www.paessler.com/knowledgebase/en/topic/443

Notifications
Others
133
section.
532
08.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 37 HTTP XML/REST Value Sensor
6.8.37 HTTP XM L/REST Value Sensor

The HTTP XML/REST Value sensor retrieves an XML file from a given URL and parses it. It can return the values of specific nodes. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.


Add Sensor
Sensor Set t ings Channel Name Enter a name for the channel which will display the value at the given URL. The name can be changed later in the Sensor Channels Set t ings 1566 .
Sensor Settings
03.05.2013
533
Tags
Priority
Sensor Set t ings URL Enter the absolute URL that returns the XML file (this sensor does not use the IP Address/DNS value of the parent device). Enter the name of the node this sensor will check, or enter a node name and a property name to check a property value. To obtain a value from nested tags, please enter the tag names separated by a slash symbol, e.g. use myTag/myTagInside as XML node value. Note: XPath syntax 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 533 section below. Note: You can also check values in JavaScript Object Notation (JSON) notation. Please see Checking JSON 540 section below. If the URL requires authentication, enter the username. Please enter a string or leave the field empty. If the URL requires authentication, enter the password. Please enter a string or leave the field empty. Choose between: Use t he value of t he select ed X ML node: Return the value found at the specified XML node. If this is non-numeric, this will return 0.
XML Node (and optional property)
HTTP Username
HTTP Password
Sensor Value
534
03.05.2013
Sensor Set t ings Use t he number of occurrences of t he select ed X ML node or it s children/siblings: Return the number of occurrences found. Define further below. Count XML Nodes This setting is only visible if the return number option is enabled above. Define which count will be returned. Choose between: Occurrences of t he select ed X ML node: Return how often the defined XML node occurs at the defined URL. Child nodes of t he select ed X ML node: Return the number of child nodes that exist below the node at the defined URL. Sibling nodes of t he select ed X ML node: Return the number of sibling nodes that exist next to the node at the defined URL. Namespaces Define whether namespaces in the XML document will be used or not. Choose between: Use Namespaces: Process the value entered in the "XML Node (and optional property)" field including possibly existing namespace information. Remove Namespaces: Ignore namespace information in the XML document and process the value entered in the "XML Node (and optional property)" field as node names only. For more information see About Namespaces Content Type in Header
541
section below.
Choose if PRTG will Include content-type="text/xml" in the header of the request sent to the URL defined above. Choose between: Enable (recommended): This works for most web servers and is the recommended setting. Disable: Only very few web servers cannot handle this contenttype and need this setting. Try this if you get an error message with the enabled option. Cust om: You can use a custom content type.
Custom Content Type
Only visible when "Custom" is enabled above. Enter a custom content type like text/xml or text/html. Only visible when using value of XML node is enabled above. 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.
Characters to Remove
03.05.2013
535
Sensor Set t ings 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. 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. Trigger 'change' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 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. Writ e result t o disk (Filename: "Result of Sensor [ID].t xt "): Store the last result received from to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see More 422 section below. Unit String Enter a string that will be added to the values as a unit description. This is for display purposes only.
Force SSL V3
Chart Type
536
03.05.2013
Inherited Settings
03.05.2013
537
Maintenance End At
Dependency Type
538
03.05.2013
03.05.2013
539
Checking JSON
With the X ML Node (and opt ional propert y ) field you can also check values that are returned in JavaScript Object Notation (JSON) notation under the defined URL.
540
03.05.2013
Example A JSON notated section may look like the following:

{ "test": "Hello World", "object": { "value": "content", "AnotherValue": "AnotherContent" }, "arraytest": [ "one", "two" ] }
Depending on your entries in the X ML Node field, the sensor will process the respective values:
Ent ry in Sensor's "X ML Node" Field (from Example Above) test object/value object/AnotherValue object arraytest[1] arraytest[2]
Processed Value (from Example Above)
Hello World content AnotherContent contentAnotherContent one two
About Namespaces
In an XML document, tags may use namespaces.
03.05.2013
541
Example A namespace notated section may look like the following:

<myNamespace:myNode> some information </myNamespace:myNode>
If you set this sensor to Use Namespaces (this is the default setting), it will expect the full node name, including the namespace information, in the X ML Node (and opt ional propert y ) field. In the example above, this would be myNamespace:myNode. If your node names are unique even without the namespace information, you can simplify the settings by setting this sensor to Remove Namespaces. The sensor will then expect the node name only in the X ML Node (and opt ional propert y ) field. In the example above, this would be myNode.
More
Knowledge Base: Is there a tool available that can help me building queries for the XML/Rest Sensor? http://www.paessler.com/knowledgebase/en/topic/48783 Knowledge Base: How do I extract values from XML nodes (with nested tags) using PRTG's XML/Rest Value Sensor? http://www.paessler.com/knowledgebase/en/topic/43223 Knowledge Base: How can I use XPath with PRTG's XML/Rest Value Sensor? http://www.paessler.com/knowledgebase/en/topic/26393 Knowledge Base: HTTP XML/REST Value Sensor shows protocol violation. What can I do? http://www.paessler.com/knowledgebase/en/topic/26793 Knowledge Base: Why does my HTTP XML/REST Value Sensor return a 404 error? http://www.paessler.com/knowledgebase/en/topic/46503

542
03.05.2013
Notifications
Others
133
section.
03.05.2013
543
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 38 Hyper-V Cluster Shared Volume Disk Free Sensor
6.8.38 Hy per-V Cluster Shared Volume Disk Free Sensor

The Hyper-V Cluster Shared Volume Disk Free sensor monitors a Microsoft Hyper-V cluster shared volume via PowerShell and shows the available disk space. Note: The parent device for this sensor must be a Windows Server running Hyper-V. Note: We recommend using System Center Virtual Machine Manager (SCVMM) as parent device, because this way PRTG will continue to monitor your virtual machines also when they change the physical host using Live Migration. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.
Requirement: Remote PowerShell

The Hyper-V Cluster Shared Volume Disk Free sensor uses PowerShell commands. In order to monitor devices with this sensor Remot e PowerShell has to be enabled. For detailed information, please see More 549 section below.
Requirement: WSFC PowerShell Interface

This sensor type needs the WSFC (Windows Server Failover Clustering) PowerShell Interface to be installed on the target machine. You can list all modules in the PowerShell console with the command Get -Module -List Available. Here FailoverClust ers has to appear. Under Windows 2008 and 2012 the interface is part of the VMM Administrator Console, or the VMM 2012 Management Console, respectively. The interface is everywhere available where the WSFC feature is installed: Windows Server 2008 R2 (SP1) Full and Core (not installed by default); Microsoft Hyper-V Server 2008 R2 (SP1); Remote Server Administration Tools (RSAT) for Windows 7 (SP1).
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor cluster disks, PRTG will create one sensor for each disk. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
544
19.07.2013
Disk Free Set t ings Disk Select the disk you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. Note: Please make sure the resource name of your disks do not contain unsupported characters, especially avoid the hash ('#') sign. We recommend to not rename resource disk name once you've set up monitoring. For detailed information, please see More 563 section below.
Sensor Settings
Tags
Priority
Disk Free Set t ings Disk Shows further information about the 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. Define what will be done in case the value of a sensor channel changes. Choose between:
If Value Changes
19.07.2013
545
Disk Free Set t ings Ignore changes: No action will be taken on change. Trigger 'change' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes. Sensor Result Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results. Writ e sensor result t o disk (Filename: "Result of Sensor [ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Chart Type
546
19.07.2013
Inherited Settings
Maintenance Window
Maintenance End At
19.07.2013
547
Delay (Seconds)
548
19.07.2013
More
Knowledge Base: How do I enable and use remote commands in Windows PowerShell?
19.07.2013
549
http://www.paessler.com/knowledgebase/en/topic/44453 Knowledge Base: Why don't my Hyper-V sensors work after changing names? http://www.paessler.com/knowledgebase/en/topic/15533

Notifications
Others
133
section.
550
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 39 Hyper-V Host Server Sensor
6.8.39 Hy per-V Host Server Sensor

The Hyper-V Host Server sensor monitors a Microsoft Hyper-V host server via Windows Performance Counters or Windows Management Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent device. It shows CPU usage in percent of guests, hypervisor, and total, as well as host health critical values, deposited pages, and network traffic. Note: The parent device for this sensor must be a Windows Server running Hyper-V. Note: We recommend using System Center Virtual Machine Manager (SCVMM) as parent device, because this way PRTG will continue to monitor your virtual machines also when they change the physical host using Live Migration. Note: By default, this sensor type uses a hybrid approach, first trying to query data via Windows Performance Counters (which needs less system resources), and using Windows Management Instrumentation (WMI) as a fallback in case Performance Counters are not available. When running in fallback mode, the sensor will re-try to connect via Performance Counters after 24 hours. The default behavior can be changed in the Windows Compat ibilit y Opt ions of the parent device's settings 268 this sensor is created on. Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813

For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. In the parent device's 264 Credent ials for Windows Sy st ems settings, please prefer using Windows domain credentials. Note: If you use local credentials, please make sure the same Windows user accounts (with same username and password) exist on both the system running the PRTG probe and the target computer. If you fail to do so, a connection via Performance Counters will not be possible. However, WMI connections may still work.
Requirement: Windows Version

In order for this sensor to work with Windows Performance Counters, please make sure a Windows version 2008 or later is installed on the computer running the PRTG probe: This is either on the local system (on every node, if on a cluster probe), or on the system running a remote probe 1888 . Note: The target system may well run on Windows 2003 or later.
07.02.2013
551
Requirement: Remote Registry Service

In order for this sensor to work with Windows Performance Counters, please make sure the Remote Registry Windows service is running on the target computer. If you fail to do so, a connection via Performance Counters will not be possible. However, WMI connections may still work. To enable the service, please log in to the respective computer and open the services manager (e.g. via services.msc). In the list, find the respective service and set its Start Type to Automatic.
Add Sensor
Sensor Settings
Tags
Priority
552
07.02.2013
Chart Type
Inherited Settings
07.02.2013
553
Maintenance Window
Maintenance End At
Dependency Type
554
07.02.2013
Delay (Seconds)
07.02.2013
555

Notifications
Others
133
section.
556
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 40 Hyper-V Virtual Machine Sensor
6.8.40 Hy per-V Virtual M achine Sensor

The Hyper-V Virtual Machine sensor monitors a virtual machine running on a Microsoft Hyper-V host server, via Windows Performance Counters or Windows Management Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent device. It shows CPU usage in percent of guests, hypervisor, and total, as well as disk read and write values, per second. Note: The parent device for this sensor must be a Hyper-V server. Note: We recommend using System Center Virtual Machine Manager (SCVMM) as parent device, because this way PRTG will continue to monitor your virtual machines also when they change the physical host using Live Migration. Note: By default, this sensor type uses a hybrid approach, first trying to query data via Windows Performance Counters (which needs less system resources), and using Windows Management Instrumentation (WMI) as a fallback in case Performance Counters are not available. When running in fallback mode, the sensor will re-try to connect via Performance Counters after 24 hours. The default behavior can be changed in the Windows Compat ibilit y Opt ions of the parent device's settings 268 this sensor is created on. Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813


07.02.2013
557

Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor virtual machines, PRTG will create one sensor for each machine. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Virt ual Machine Set t ings Virtual Machine Select the virtual machines (VMs) you want to add a sensor for, including the ones that are not running. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. Note: 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 563 section below.
Sensor Settings
558
07.02.2013
Tags
Priority
Virt ual Machine Set t ings 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. 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. 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. 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 115 status if the virtual machine is powered off. Note: While in Down status, a sensor does not record any data in all of its channels. Ignore powered off st at e: The sensor will not change to a Down status if the virtual machine is powered off; it will report zero values instead.
Name
Name
Powered Off VMs
07.02.2013
559
Chart Type
Inherited Settings
560
07.02.2013
Maintenance Window
Maintenance End At
Dependency Type
07.02.2013
561
Delay (Seconds)
562
07.02.2013
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

Notifications
Others
133
section.
07.02.2013
563
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 41 Hyper-V Virtual Network Adapter Sensor
6.8.41 Hy per-V Virtual Network Adapter Sensor

The Hyper-V Network Adapter sensor monitors virtual network adapters running on a Microsoft Hyper-V host server, via Windows Performance Counters or Windows Management Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent device. It shows sent and received bytes, packets, broadcast packets, directed packets, and multicast packets, per second. Note: The parent device for this sensor must be a Hyper-V server. Note: We recommend using System Center Virtual Machine Manager (SCVMM) as parent device, because this way PRTG will continue to monitor your virtual machines also when they change the physical host using Live Migration. Note: By default, this sensor type uses a hybrid approach, first trying to query data via Windows Performance Counters (which needs less system resources), and using Windows Management Instrumentation (WMI) as a fallback in case Performance Counters are not available. When running in fallback mode, the sensor will re-try to connect via Performance Counters after 24 hours. The default behavior can be changed in the Windows Compat ibilit y Opt ions of the parent device's settings 268 this sensor is created on. Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813


564
07.02.2013

Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor network adapters, PRTG will create one sensor for each adapter. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Virt ual Machine Set t ings Hyper-V Virtual Network Adapter Select the virtual network adapter you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. Note: 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 563 section below.
Sensor Settings
07.02.2013
565
Tags
Priority
Hy per-V Virt ual Net work Adapt er Set t ings 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. Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results. Writ e sensor result t o disk (Filename: "Result of Sensor [ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Sensor Result
Sensor Display Primary Channel Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel will always be displayed underneath the sensor's name. The available options depend on what channels are available for this sensor. Note: You can set another primary channel later by clicking on the pin symbol of a channel in the sensor's overview tab. Define how different channels will be shown for this sensor.
Chart Type
566
07.02.2013
Sensor Display Show channels independent ly (default ): Show an own graph for each channel. St ack channels on t op of each ot her: Stack channels on top of each other to create a multi-channel graph. This will generate an easy-to-read graph which visualizes the different components of your total traffic. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 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
07.02.2013
567
Maintenance End At
Dependency Type
568
07.02.2013
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
07.02.2013
569

Notifications
Others
133
section.
570
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 42 Hyper-V Virtual Storage Device Sensor
6.8.42 Hy per-V Virtual Storage Device Sensor

The Hyper-V Virtual Storage sensor monitors a virtual storage device running on a Microsoft Hyper-V host server, via Windows Performance Counters or Windows Management Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent device. It shows read and write values in second, and the number of errors. Note: The parent device for this sensor must be a Hyper-V server. Note: We recommend using System Center Virtual Machine Manager (SCVMM) as parent device, because this way PRTG will continue to monitor your virtual machines also when they change the physical host using Live Migration. Note: By default, this sensor type uses a hybrid approach, first trying to query data via Windows Performance Counters (which needs less system resources), and using Windows Management Instrumentation (WMI) as a fallback in case Performance Counters are not available. When running in fallback mode, the sensor will re-try to connect via Performance Counters after 24 hours. The default behavior can be changed in the Windows Compat ibilit y Opt ions of the parent device's settings 268 this sensor is created on. Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813


07.02.2013
571

Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor storage devices, PRTG will create one sensor for each device. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Hy per-V Virt ual St orage Device Set t ings Hyper-V Virtual Storage Select the virtual storage device you want to add a sensor for. A Device list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
572
07.02.2013
Priority
Hy per-V Virt ual St orage Device Set t ings 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.
Chart Type
07.02.2013
573
Inherited Settings
Maintenance Window
Maintenance End At
574
07.02.2013
Delay (Seconds)
07.02.2013
575

Notifications
Others
133
section.
576
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 43 IMAP Sensor
6.8.43 IM AP Sensor
The IMAP sensor monitors a mail server using Internet Message Access Protocol (IMAP) and shows the server's response time as well as the number of emails in the defined mailbox. It can also check the content of emails for certain key words. This way, you can use this sensor to monitor backup solutions via emails that are sent out by these solutions. For more information, see section More 586 . Note: If you use content checks, we recommend using a dedicated IMAP account that is only checked by PRTG. Editing existing mails in the mailbox of the monitored IMAP account can lead to false alarms or malfunctions of this sensor type. Note: This sensor type might not work properly when monitoring sub-folders of mailboxes. If it has to check subsequent emails with identical subjects, later on incoming emails might not be recognized.
Add Sensor
Sensor Settings
Tags
Priority
19.07.2013
577
IMAP Specific Timeout (sec.) Enter a timeout in seconds for the SMTP connect. If the reply takes longer than this value the request is aborted and an error message is triggered. 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.
Port
Aut hent icat ion Authentication Type Select the kind of authentication for the IMAP connection. Choose between: Username/Password: Authenticate at the IMAP server via username and password. Simple Aut hent icat ion and Securit y Lay er (SASL): Use a secure connection for the authentication at the IMAP server. Username Enter a username for IMAP authentication. Please enter a string or leave the field empty. Note: If you leave this field empty, PRTG will not attempt to log in to the mail server. The sensor will show a green Up status if the IMAP server is available. Enter a password for IMAP authentication. Please enter a string or leave the field empty. Note: If you leave this field empty, PRTG will not attempt to log in to the mail server. The sensor will show a green Up status if the IMAP server is available. This setting is only relevant if authentication is used. Choose if a secure connection via TLS/SSL will be used. Choose between: Don't use Use
Password
TLS (Transport-Level Security)
578
19.07.2013
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
Ident ify Email Process Email Content This sensor can additionally check the content of all incoming emails. Choose between: Do not check email cont ent : Only check availability of the IMAP server and check if a login is successful (if defined). Do not process any mails in the IMAP mail account. Process emails in t his mailbox: Login in to the IMAP mail account and check the mails contained there. Define further options below. Mailbox Name This field is only visible if email content processing is enabled above. Enter the name of the mailbox (e.g. the name of the IMAP folder) that will be checked. Default value is Inbox. Unless you set a last message date check below, the sensor will always look at all emails contained in the mailbox. Note: Please make sure that you do not manually edit mails in this mailbox with another mail client, as this can lead to malfunctions of this sensor's email identification. This option is only visible if email content processing is enabled above. Define if you want to check the "From" field of the emails. Choose between: Don't check: Do not check this field in emails. Check using st ring search: Check this field in emails using simple string search. Check using regular expression: Check this field in emails using a regular expression. For more information about syntax, please see Regular Expressions 1886 section. When using a search, the sensor will scan all emails from the newest to the oldest. Note: The scan will be finished with the first match! That means: After a match is found in one email, there will be no further checks performed in older emails. Search For This field is only visible if a check is enabled above. Enter a search string using the method defined above.
Identify by "From" Field
19.07.2013
579
Ident ify Email Identify by "Subject" Field This option is only visible if email content processing is enabled above. Define if you want to check the "Subject" field of the emails. Choose between: Don't check: Do not check this field in emails. Check using st ring search: Check this field in emails using simple string search. Check using regular expression: Check this field in emails using a regular expression. For more information about syntax, please see Regular Expressions 1886 section. When using a search, the sensor will scan all emails from the newest to the oldest. Note: The scan will be finished with the first match! That means: After a match is found in one email, there will be no further checks performed in older emails. Search For This field is only visible if a check is enabled above. Enter a search string using the method defined above. This option is only visible if email content processing is enabled above. Define if you want to check the mail body of the emails. Choose between: Don't check: Do not check the mail body. Check using st ring search: Check the mail body using simple string search. Check using regular expression: Check the mail body using a regular expression. For more information about syntax, please see Regular Expressions 1886 section. When using a search, the sensor will scan all emails from the newest to the oldest. Note: The scan will be finished with the first match! That means: After a match is found in one email, there will be no further checks performed in older emails. Search For This field is only visible if a check is enabled above. Enter a search string using the method defined above. This option is only visible if email content processing is enabled above. Define if you want to check all emails in the mailbox, or only mails that were received within the last x hours. Choose between: Don't check message age: Always check all emails contained in the mailbox. Check for new messages received wit hin t he last x hours: Only regard emails that were received in the last hours. Define below.
Identify by Mail Body
Check Last Message Date
580
19.07.2013
Ident ify Email Error Threshold (Hours) Enter the maximum age in hours. Only emails that are younger will be processed. If there is no matching email in the defined time span, the sensor will show a Down status. Warning Threshold (Hours) Enter the maximum age in hours. Only emails that are younger will be processed. If there is no matching email in the defined time span, the sensor will show a Warning status.
Sensor Behavior Set to Alarm This setting is only visible if email content check is enabled above. Define in which cases the sensor will show a Down status. Choose between: If subject cont ains If subject does not cont ain If mail body cont ains If mail body does not cont ain Alway s: Always set this sensor to a Down status in case any emails could be identified. Never: Never set this sensor to a Down status based on email content. Check Method This setting is only visible if an if-condition is selected above. Define how you want to check for the above condition. Choose between: St ring search: Check the mail body using simple string search. Regular expression: Check the mail body using a regular expression. For more information about syntax, please see Regular Expressions 1886 section. When using a search, the sensor will scan all emails from the newest to the oldest. Note: The scan will be finished with the first match! That means: After a match is found in one email, there will be no further checks performed in older emails. Search Text This setting is only visible if an if-condition is selected above. Enter a search string using the method defined above. This setting is only visible if an alarm condition is selected above. Define the message that will be shown in case the sensor shows a Down status.
Error Message
19.07.2013
581
Sensor Behavior Set to Warning This setting is only visible if email content check is enabled above. Define in which cases the sensor will show a Warning status. Choose between: If subject cont ains If subject does not cont ain If mail body cont ains If mail body does not cont ain Alway s: Always set this sensor to a Warning status in case any emails could be identified. Never: Never set this sensor to a Warning status based on email content. Check Method This setting is only visible if an if-condition is selected above. Define how you want to check for the above condition. Choose between: St ring search: Check the mail body using simple string search. Regular expression: Check the mail body using a regular expression. For more information about syntax, please see Regular Expressions 1886 section. When using a search, the sensor will scan all emails from the newest to the oldest. Note: The scan will be finished with the first match! That means: After a match is found in one email, there will be no further checks performed in older emails. Search Text This setting is only visible if an if-condition is selected above. Enter a search string using the method defined above. This setting is only visible if a warning condition is selected above. Define the message that will be shown in case the sensor shows a Warning status. This setting is only visible if email content check is enabled above. Define how the sensor will react if no matching emails are found in the mailbox that is being scanned. Choose between: Set sensor t o "Down" st at us Set sensor t o "Warning" st at us None: Don't do anything in this case.
Warning Message
No Matching Mail Behavior
582
19.07.2013
Sensor Behavior Message This field is only effective if a sensor change in case of no matching mail is defined above. Define the message that will be shown in case the sensor could not find any matching emails. It will be shown together with a Warning or Down status, just as defined above.
Chart Type
Inherited Settings
19.07.2013
583
Maintenance Window
Maintenance End At
Dependency Type
584
19.07.2013
Delay (Seconds)
19.07.2013
585
More
Knowledge Base: How can I monitor my backup software to be sure backup succeeded last night? http://www.paessler.com/knowledgebase/en/topic/47023

Notifications
586
19.07.2013
Others
133
section.
19.07.2013
587
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 44 INI File Content Check Sensor
6.8.44 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 credentials for Windows systems must be defined for the device you want to use the sensor on. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.
Add Sensor
Sensor Settings
Tags
Priority
588
13.06.2013
Sensor Set t ings 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. 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. 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. 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' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
INI Section
INI Field
If Value Changes
Chart Type
13.06.2013
589
Inherited Settings
590
13.06.2013
Maintenance End At
Dependency Type
13.06.2013
591
592
13.06.2013

Notifications
Others
133
section.
13.06.2013
593
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 45 IP on DNS Blacklist Sensor
6.8.45 IP on DNS Blacklist Sensor

The IP on DNS Blacklist sensor checks if the IP address of its parent device is listed on specific blacklist servers and returns the number of hits found. If a DNS name is used as the parent device's hostname, PRTG will resolve it to an IP address first. During normal operation, there should be 0 hits and the sensor should show a green Up status. If the IP address is found on at least one of the blacklist servers, the sensor changes to a yellow Warning status by default. Note: You can set additional thresholds in the sensor's Sensor Channels Set t ings 1566 , if you like. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Add Sensor
Sensor Settings
594
13.06.2013
Priority
Sensor Set t ings Blacklist Servers Define the blacklist servers that will be used for the check. You can enter a comma separated list. Default is bl.spamcop.net. For a list of servers, please see More 598 section below. Note: With each scanning interval, PRTG will query all servers in the list! We recommend you do not enter more than 10 servers to make sure the check can be completed within the scanning interval of this sensor. If you use too many blacklist servers, the sensor will show a "Timeout (code: PE018)" error message. 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.
Timeout (sec.)
Chart Type
13.06.2013
595
Inherited Settings
596
13.06.2013
Maintenance End At
Dependency Type
13.06.2013
597
More
Knowledge Base: Is there a list of anti spam black list servers? http://www.paessler.com/knowledgebase/en/topic/37633
598
13.06.2013

Notifications
Others
133
section.
13.06.2013
599
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 46 IPFIX Sensor
6.8.46 IPFIX Sensor

The IPFIX sensor receives traffic data from an IPFIX (Internet Protocol Flow Information Export) compatible device and shows traffic by type. There are several filter options available to divide traffic into different channels. Please make sure your device supports IPFIX when using this sensor. Note: In order for this sensor to work, you have to enable IPFIX export on the device. The device must send the flow data stream to the IP address of the PRTG probe system on which the sensor is set up (either a local or remote probe). This sensor type cannot be used in cluster mode. You can set it up on a local probe or remote probe only, not on a cluster probe. For a general introduction to the technology behind flow monitoring, please see Monit oring Bandwidt h via Flows 1820 section.
Add Sensor
Sensor Settings
Tags
Priority
600
08.10.2013
IPFIX Specific Set t ings Receive IPFIX Packets on UDP Port Enter the UDP port number on which the flow packets are received. It must match the one you have configured in the IPFIX export options of your hardware router device. Please enter an integer value. Enter the IP address of the sending device you want to receive the IPFIX data from. Enter an IP address to receive data from a specific device only, or leave the field empty to receive data from any device on the specified port. Select the IP address(es) on which PRTG listens to IPFIX packets. The list of IP addresses shown here is specific to your setup. To select an IP address, add a check mark in front of the respective line or in the top level box to select all. The IP address selected here must match the one configured in the IPFIX export options of your hardware router device. 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! Define if you want to use the sampling mode. This setting must accord to the setting in the flow exporter. Choose between: Off: The standard flow will be used. On: Switch into sampling mode and specify the sampling rate below. Sampling Rate This field is only visible when sampling mode is enabled above. Enter a number that matches the sampling rate in your exporter device. If the number is different, monitoring results will be incorrect. Please enter an integer value. Define if the probe will write a log file of the stream and packet data to the data folder (see Dat a St orage 1912 ). Choose between: None (recommended): Do not write additional log files. Recommended for normal use cases. Only for t he 'Ot her' channel: Only write log files of data that is not filtered otherwise and therefore accounted to the default Ot her channel. All st ream dat a: Write log files for all data received.
Sender IP
Receive IPFIX Packets on IP
Active Flow Timeout (Minutes)
Sampling Mode
Log Stream Data to Disk (for Debugging)
08.10.2013
601
IPFIX Specific Set t ings Note: Use with caution! When enabled, huge data files can be created. Please use for a short time and for debugging purposes only.
Channel Configurat ion 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. Remot e Cont rol: Traffic caused by remote control applications, such as RDP, SSH, Telnet, VNC. Infrast ruct ure: Traffic caused by network services, such as DHCP, DNS, Ident, ICMP, SNMP. Net BIOS : Traffic caused by NetBIOS communication. Ot her Prot ocols: Traffic caused by various other protocols via UDP and TCP. For each traffic group, you can select how many channels will be used for each group, i.e. how detailed 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 Ot her. Yes: Count all traffic of this group and summarize it into one channel. Det ail: Count all traffic of this group and further divide it into different channels. The traffic will appear in several channels as shown in the Cont ent column. Note: Extensive use of this option can cause load problems on your probe system. We recommend setting specific, well-chosen filters for the data you really want to analyse.
Filt ering Include Filter Define if you want to filter any traffic. If you leave this field empty, all traffic will be included. To include specific traffic only, define filters using a special syntax. For detailed information, please see Filt er Rules for xFlow, IPFIX , and Packet Sniffer Sensors 1872
602
08.10.2013
Filt ering section. Exclude Filter First, the filters defined in the Include Filt er field are considered. From this subset, you can explicitly exclude traffic, using the same syntax. For detailed information, please see Filt er Rules for xFlow, IPFIX , and Packet Sniffer Sensors 1872 section.
Chart Type
Primary Toplist Primary Toplist Define which will be your primary toplist. It will be shown in maps when adding a toplist object. Choose from: Top Talkers Top Connect ions Top Prot ocols [Any custom toplists you have added]
08.10.2013
603
Inherited Settings
Maintenance Window
Maintenance End At
604
08.10.2013
Delay (Seconds)
08.10.2013
605
606
08.10.2013
Toplists
For all flow and packet sniffer sensors there are Toplist s available on the Overview tab of a sensor's detail page. Using toplists, you can review traffic data of small time periods in great detail. For more information, please see Toplist s 1586 section.

Notifications
Others
133
section.
Related Topics
Filt er Rules for xFlow, IPFIX , and Packet Sniffer Sensors
1872
Channel Defint ions for xFlow, IPFIX , and Packet Sniffer Sensors
1876
08.10.2013
607
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 47 IPFIX (Custom) Sensor
6.8.47 IPFIX (Custom) Sensor

The IPFIX (Custom) sensor receives traffic data from an IPFIX (Internet Protocol Flow Information Export) compatible device and shows the traffic by type. In this custom sensor, you can define your own channel definitions to divide traffic into different channels. Please make sure your device supports IPFIX when using this sensor. Note: In order for this sensor to work, you have to enable IPFIX export on the device. The device must send the flow data stream to the IP address of the PRTG probe system on which the sensor is set up (either a local or remote probe). This sensor type cannot be used in cluster mode. You can set it up on a local probe or remote probe only, not on a cluster probe. For a general introduction to the technology behind flow monitoring, please see Monit oring Bandwidt h via Flows 1820 section.

Add Sensor
Sensor Settings
Tags
608
08.10.2013
IPFIX Specific Set t ings Receive IPFIX Packets on UDP Port Enter the UDP port number on which the flow packets are received. It must match the one configured in the IPFIX export options of your hardware router device. Please enter an integer value. Enter the IP address of the sending device you want to receive the IPFIX data from. Enter an IP address to receive data from a specific device only, or leave the field empty to receive data from any device on the specified port. Select the IP address(es) on which PRTG listens to IPFIX packets. The list of IP addresses shown here is specific to your setup. To select an IP address, add a check mark in front of the respective line. The IP address selected here must match the one configured in the IPFIX export options of your hardware router device. 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! Define if you want to use the sampling mode. This setting must accord to the setting in the flow exporter. Choose between: Off: The standard flow will be used. On: Switch into sampling mode and specify the sampling rate below. Sampling Rate This field is only visible when sampling mode is enabled above. Enter a number that matches the sampling rate in your device. If the number is different, monitoring results will be incorrect. Please enter an integer value.
Sender IP
Receive IPFIX Packets on IP
Sampling Mode
08.10.2013
609
IPFIX Specific Set t ings Channel Definition Please enter a channel definition to divide the traffic into different channels. Write each definition in one line. For detailed information, please see Channel Definit ions for xFlow and Packet Sniffer Sensors 1876 section. All traffic for which no channel is defined will be accounted to the default channel named Ot her. Note: Extensive use of many filters can cause load problems on your probe system. We recommend defining specific, well-chosen filters for the data you really want to analyze. Define if the probe will write a log file of the stream and packet data to the data folder (see Dat a St orage 1912 ). Choose between: None (recommended): Do not write additional log files. Recommended for normal use cases. Only for t he 'Ot her' channel: Only write log files of data that is not filtered otherwise and therefore accounted to the default Ot her channel. All st ream dat a: Write log files for all data received. Note: Use with caution! When enabled, huge data files can be created. Please use for a short time and for debugging purposes only.
Chart Type
610
08.10.2013
Filt ering Include Filter Define if you want to filter any traffic. If you leave this field empty, all traffic will be included. To include specific traffic only, define filters using a special syntax. For detailed information, please see Filt er Rules for xFlow, IPFIX , and Packet Sniffer Sensors 1872 section. First, the filters defined in the Include Filt er field are considered. From this subset, you can explicitly exclude traffic, using the same syntax. For detailed information, please see Filt er Rules for xFlow, IPFIX , and Packet Sniffer Sensors 1872 section.
Exclude Filter
Inherited Settings
08.10.2013
611
Maintenance Window
Maintenance End At
Dependency Type
612
08.10.2013
Delay (Seconds)
08.10.2013
613
614
08.10.2013
Toplists

Notifications
Others
133
section.
Related Topics
1872
1876
08.10.2013
615
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 48 jFlow V5 Sensor
6.8.48 jFlow V5 Sensor

The jFlow V5 sensor receives traffic data from a jFlow V5 compatible device and shows the traffic by type. On your hardware device, please make sure it matches jFlow V5 and disable any sampling option! There are several filter options available to divide traffic into different channels. Note: In order for the sensor to work, jFlow export of the respective version must be enabled on the device. The device must send the flow data stream to the IP address of the PRTG probe system on which the sensor is set up (either a local or remote probe). The sensor does not support sampling, so please disable sampling in your jFlow device! This sensor type cannot be used in cluster mode. You can set it up on a local probe or remote probe only, not on a cluster probe. For a general introduction to the technology behind flow monitoring, please see Monit oring Bandwidt h via Flows 1820 section.
Add Sensor
Sensor Settings
Tags
Priority
616
08.10.2013
jFlow V5 Specific Set t ings 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. Note: When configuring export, please make sure you select the appropriate jFlow version for this sensor. Enter the IP address of the sending device you want to receive the jFlow from. Enter an IP address to receive data from a specific device only, or leave the field empty to receive data from any device on the specified port. 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. 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! Define if you want to use the sampling mode. This setting must accord to the setting in the flow exporter. Choose between: Off: The standard flow will be used. On: Switch into sampling mode and specify the sampling rate below. Sampling Rate This field is only visible when sampling mode is enabled above. Enter a number that matches the sampling rate in your exporter device. If the number is different, monitoring results will be incorrect. Please enter an integer value. Define if the probe will write a log file of the stream and packet data to the data folder (see Dat a St orage 1912 ). Choose between: None (recommended): Do not write additional log files. Recommended for normal use cases. Only for t he 'Ot her' channel: Only write log files of data that is not filtered otherwise and therefore accounted to the default Ot her channel. All st ream dat a: Write log files for all data received.
Sender IP
Receive jFlow Packets on IP
Sampling Mode
08.10.2013
617
jFlow V5 Specific Set t ings Note: Use with caution! When enabled, huge data files can be created. Please use for a short time and for debugging purposes only.
618
08.10.2013
Chart Type
08.10.2013
619
Inherited Settings
Maintenance Window
Maintenance End At
620
08.10.2013
Delay (Seconds)
08.10.2013
621
622
08.10.2013
Toplists

Notifications
Others
133
section.
Related Topics
1872
1876
08.10.2013
623
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 49 jFlow V5 (Custom) Sensor
6.8.49 jFlow V5 (Custom) Sensor

The jFlow V5 (Custom) sensor receives traffic data from a jFlow V5 compatible device and shows the traffic by type. On your hardware device, please make sure it matches jFlow V5 and disable any sampling option! In this custom sensor, you can define your own channel definitions to divide traffic into different channels. Note: In order for the sensor to work, jFlow export of the respective version must be enabled on the device. The device must send the flow data stream to the IP address of the PRTG probe system on which the sensor is set up (either a local or remote probe). The sensor does not support sampling, so please disable sampling in your jFlow device! This sensor type cannot be used in cluster mode. You can set it up on a local probe or remote probe only, not on a cluster probe. For a general introduction to the technology behind flow monitoring, please see Monit oring Bandwidt h via Flows 1820 section.

Add Sensor
Sensor Settings
624
08.10.2013
Priority
jFlow Specific Set t ings 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. Note: When configuring export, please make sure you select the appropriate jFlow version for this sensor. Enter the IP address of the sending device you want to receive the jFlow from. Enter an IP address to receive data from a specific device only, or leave the field empty to receive data from any device on the specified port. 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. 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! Define if you want to use the sampling mode. This setting must accord to the setting in the flow exporter. Choose between: Off: The standard flow will be used. On: Switch into sampling mode and specify the sampling rate below.
Sender IP
Receive jFlow Packets on IP
Sampling Mode
08.10.2013
625
jFlow Specific Set t ings Sampling Rate This field is only visible when sampling mode is enabled above. Enter a number that matches the sampling rate in your exporter device. If the number is different, monitoring results will be incorrect. Please enter an integer value. Please enter a channel definition to divide the traffic into different channels. Write each definition in one line. For detailed information, please see Channel Defint ions for xFlow and Packet Sniffer Sensors 1876 section. All traffic for which no channel is defined will be accounted to the default channel named Ot her. Note: Extensive use of many filters can cause load problems on your probe system. We recommend defining specific, well-chosen filters for the data you really want to analyse. Define if the probe will write a log file of the stream and packet data to the data folder (see Dat a St orage 1912 ). Choose between: None (recommended): Do not write additional log files. Recommended for normal use cases. Only for t he 'Ot her' channel: Only write log files of data that is not filtered otherwise and therefore accounted to the default Ot her channel. All st ream dat a: Write log files for all data received. Note: Use with caution! When enabled, huge data files can be created. Please use for a short time and for debugging purposes only.
Channel Definition
Exclude Filter
626
08.10.2013
Chart Type
Inherited Settings
08.10.2013
627
Maintenance Window
Maintenance End At
Dependency Type
628
08.10.2013
Delay (Seconds)
08.10.2013
629
630
08.10.2013
Toplists

Notifications
Others
133
section.
Related Topics
1872
1876
08.10.2013
631
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 50 LDAP Sensor
6.8.50 LDAP Sensor

The LDAP sensor monitors directory services using Lightweight Directory Access Protocol (LDAP), connecting to the server trying a "bind". It shows the response time. If the server does not respond or authentication fails, an error message will be triggered.
Add Sensor
Sensor Settings
Tags
Priority
LDAP Specific Port Enter the LDAP port number, usually port 389 for unencrypted connections. Please enter an integer value. 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.
Distinguished Name
632
13.06.2013
LDAP Specific Passwort Enter the password for the entered Distinguished Name.
Chart Type
Inherited Settings
13.06.2013
633
Maintenance Window
Maintenance End At
Dependency Type
634
13.06.2013
Delay (Seconds)
13.06.2013
635

Notifications
Others
133
section.
636
13.06.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 51 Microsoft SQL Sensor
6.8.51 M icrosoft 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
Sensor Settings
Tags
Priority
SQL-Server Specific Dat a 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.
08.10.2013
637
SQL-Server Specific Dat a 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. Define the port for the SQL connection. Choose between: Aut omat ic : Automatically choose the right port. Manual: Use a specific port. Define below. Standard value is 1433. Port This field is only visible if manual port selection is enabled above. Define the port number for the SQL connection. Please enter an integer value.
Port
Dat abase Database Enter the name of the SQL database the sensor will connect to. For example, such a database's name could be Northwind 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 Aut hent icat ion: Use the Windows credentials defined for the parent device this sensor is created on. Note: For successful authentication, the defined Windows credentials must be known to the SQL server, and SQL server and the computer the PRTG probe is running on must be in the same domain. User This field is only visible if SQL server authentication is enabled above. Enter the user name that will be used for the database connection. This field is only visible if SQL server authentication is enabled above. Enter the password that will be used for the database connection.
Authentication
Password
638
08.10.2013
Dat a SQL Expression Enter a valid SQL statement to execute on the server. In your SELECT statement, please specify the field name explicitly. Do not use SELECT *! For example, a correct expression could be: SELECT ProductName FROM Northwind.dbo.Products. When a cursor is returned (i.e. with a SELECT statement), only the first row of data will be processed. Note: Executing stored procedures is currently not supported.
Record Count
Post-processing
If the SQL expression returns a result set, please define if you want to further process it. Choose between: Ignore result set : Do not do anything with the data returned. Process numerical result : Regard the result set returned as integer or float. You can set the sensor to Warning or Down status for specific thresholds. Define below. Process st ring result : Regard the result set returned as a string. You can set the sensor to error for certain sub-strings contained or missing. Define below. Monit or for changes: Monitor if the result set has changed since last check. The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 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 t han: Result set must be below the value provided below.
08.10.2013
639
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 1566 . 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. 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 t han: Result set must be below the value provided below. does not equal: Result set must be unequal to the value provided below. Note: This threshold check the SQL result set only. You can set additional thresholds in the sensor's channel settings 1566 . 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.
Condition "Down"
640
08.10.2013
Inherited Settings
08.10.2013
641
Maintenance End At
Dependency Type
642
08.10.2013

08.10.2013
643
Notifications
Others
133
section.
644
08.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 52 MySQL Sensor
6.8.52 M y SQL 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
Sensor Settings
Tags
Priority
My SQL Server Specific Dat a Port Define the port for the SQL connection. Choose between: Aut omat ic : Automatically choose the right port. Manual: Use a specific port. Define below. Standard value is 3306.
27.11.2012
645
My SQL Server Specific Dat a 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 Dat a 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. Enter the user name that will be used for the database connection. Enter the password that will be used for the database connection.
User Password
Dat a SQL Expression Enter a valid SQL statement to execute on the server. In your SELECT statement, please specify the field name explicitly. Do not use SELECT *! For example, a correct expression could be: SELECT AVG(UnitPrice) FROM Products. When a cursor is returned (i.e. with a SELECT statement), only the first row of data will be processed.
Record Count
Post-processing
If the SQL expression returns a result set, please define if you want to further process it. Choose between: Ignore result set : Do not do anything with the data returned.
646
27.11.2012
Process numerical result : Regard the result set returned as integer or float. You can set the sensor to Warning or Down status for specific thresholds. Define below. Process st ring result : Regard the result set returned as a string. You can set the sensor to error for certain sub-strings contained or missing. Define below. Monit or for changes: Monitor if the result set has changed since last check. The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 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 t han: Result set must be below the value provided below. does not equal: Result set must be unequal to the value provided below. Note: This threshold check the SQL result set only. You can set additional thresholds in the sensor's channel settings 1566 . 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. 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 t han: Result set must be below the value provided below. does not equal: Result set must be unequal to the value provided below. Note: This threshold check the SQL result set only. You can set additional thresholds in the sensor's channel settings 1566 .
Condition "Down"
27.11.2012
647
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.
Chart Type
Note: For this sensor type, no port number can be set.
Inherited Settings
648
27.11.2012
Maintenance Window
Maintenance End At
Dependency Type
27.11.2012
649
Delay (Seconds)
650
27.11.2012

Notifications
Others
133
section.
27.11.2012
651
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 53 NetFlow V5 Sensor
6.8.53 NetFlow V5 Sensor

The NetFlow V5 sensor receives traffic data from a NetFlow V5 compatible device and shows the traffic by type. Please make sure the sensor matches the NetFlow version your device is exporting! There are several filter options available to divide traffic into different channels. Note: In order for the sensor to work, NetFlow export of the respective version must be enabled on the device. The device must send the flow data stream to the IP address of the PRTG probe system on which the sensor is set up (either a local or remote probe). This sensor type cannot be used in cluster mode. You can set it up on a local probe or remote probe only, not on a cluster probe. For a general introduction to the technology behind flow monitoring, please see Monit oring Bandwidt h via Flows 1820 section.
Add Sensor
Sensor Settings
Tags
Priority
652
27.11.2012
Net Flow Specific Set t ings 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. Note: When configuring export, please make sure you select the appropriate NetFlow version for this sensor. Enter the IP address of the sending device you want to receive the NetFlow from. Enter an IP address to receive data from a specific device only, or leave the field empty to receive data from any device on the specified port. 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. 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! Define if you want to use the sampling mode. This setting must accord to the setting in the flow exporter. Choose between: Off: The standard flow will be used. On: Switch into sampling mode and specify the sampling rate below. Sampling Rate This field is only visible when sampling mode is enabled above. Enter a number that matches the sampling rate in your exporter device. If the number is different, monitoring results will be incorrect. Please enter an integer value. Define if the probe will write a log file of the stream and packet data to the data folder (see Dat a St orage 1912 ). Choose between: None (recommended): Do not write additional log files. Recommended for normal use cases. Only for t he 'Ot her' channel: Only write log files of data that is not filtered otherwise and therefore accounted to the default Ot her channel. All st ream dat a: Write log files for all data received.
Sender IP
Receive NetFlow Packets on IP
Sampling Mode
27.11.2012
653
Net Flow Specific Set t ings Note: Use with caution! When enabled, huge data files can be created. Please use for a short time and for debugging purposes only.
654
27.11.2012
Chart Type
27.11.2012
655
Inherited Settings
Maintenance Window
Maintenance End At
656
27.11.2012
Delay (Seconds)
27.11.2012
657
658
27.11.2012
Toplists
More
Paessler Website: Paessler NetFlow Testers http://www.paessler.com/tools/netflowtester

Notifications
Others
133
section.
Related Topics
1872
1876
27.11.2012
659
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 54 NetFlow V5 (Custom) Sensor
6.8.54 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). This sensor type cannot be used in cluster mode. You can set it up on a local probe or remote probe only, not on a cluster probe. For a general introduction to the technology behind flow monitoring, please see Monit oring Bandwidt h via Flows 1820 section.

Add Sensor
Sensor Settings
Tags
660
07.02.2013
Net Flow Specific Set t ings 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. Note: When configuring export, please make sure you select the appropriate NetFlow version for this sensor. Enter the IP address of the sending device you want to receive the NetFlow from. Enter an IP address to receive data from a specific device only, or leave the field empty to receive data from any device on the specified port. 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. 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! Define if you want to use the sampling mode. This setting must accord to the setting in the flow exporter. Choose between: Off: The standard flow will be used. On: Switch into sampling mode and specify the sampling rate below. Sampling Rate This field is only visible when sampling mode is enabled above. Enter a number that matches the sampling rate in your device. If the number is different, monitoring results will be incorrect. Please enter an integer value.
Sender IP
Sampling Mode
07.02.2013
661
Net Flow Specific Set t ings Channel Definition Please enter a channel definition to divide the traffic into different channels. Write each definition in one line. For detailed information, please see Channel Definit ions for xFlow, IPFIX , and Packet Sniffer Sensors 1876 section. All traffic for which no channel is defined will be accounted to the default channel named Ot her. Note: Extensive use of many filters can cause load problems on your probe system. We recommend defining specific, well-chosen filters for the data you really want to analyze. Define if the probe will write a log file of the stream and packet data to the data folder (see Dat a St orage 1912 ). Choose between: None (recommended): Do not write additional log files. Recommended for normal use cases. Only for t he 'Ot her' channel: Only write log files of data that is not filtered otherwise and therefore accounted to the default Ot her channel. All st ream dat a: Write log files for all data received. Note: Use with caution! When enabled, huge data files can be created. Please use for a short time and for debugging purposes only.
Exclude Filter
Chart Type
662
07.02.2013
Inherited Settings
07.02.2013
663
Maintenance Window
Maintenance End At
Dependency Type
664
07.02.2013
Delay (Seconds)
07.02.2013
665
666
07.02.2013
Toplists

Notifications
Others
133
section.
Related Topics
1872
1876
07.02.2013
667
6.8.55 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). This sensor type cannot be used in cluster mode. You can set it up on a local probe or remote probe only, not on a cluster probe. For a general introduction to the technology behind flow monitoring, please see Monit oring Bandwidt h via Flows 1820 section.
Add Sensor
Sensor Settings
Tags
Priority
668
27.11.2012
Net Flow Specific Set t ings 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. Note: When configuring export, please make sure you select the appropriate NetFlow version for this sensor. Enter the IP address of the sending device you want to receive the NetFlow from. Enter an IP address to receive data from a specific device only, or leave the field empty to receive data from any device on the specified port. 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. 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! Define if you want to use the sampling mode. This setting must accord to the setting in the flow exporter. Choose between: Off: The standard flow will be used. On: Switch into sampling mode and specify the sampling rate below. Sampling Rate This field is only visible when sampling mode is enabled above. Enter a number that matches the sampling rate in your exporter device. If the number is different, monitoring results will be incorrect. Please enter an integer value. Define if the probe will write a log file of the stream and packet data to the data folder (see Dat a St orage 1912 ). Choose between: None (recommended): Do not write additional log files. Recommended for normal use cases. Only for t he 'Ot her' channel: Only write log files of data that is not filtered otherwise and therefore accounted to the default Ot her channel. All st ream dat a: Write log files for all data received.
Sender IP
Sampling Mode
27.11.2012
669
Net Flow Specific Set t ings Note: Use with caution! When enabled, huge data files can be created. Please use for a short time and for debugging purposes only.
670
27.11.2012
Chart Type
27.11.2012
671
Inherited Settings
Maintenance Window
Maintenance End At
672
27.11.2012
Delay (Seconds)
27.11.2012
673
674
27.11.2012
Toplists
More
Paessler Website: Paessler NetFlow Testers http://www.paessler.com/tools/netflowtester

Notifications
Others
133
section.
Related Topics
1872
1876
27.11.2012
675
6.8.56 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). This sensor type cannot be used in cluster mode. You can set it up on a local probe or remote probe only, not on a cluster probe. For a general introduction to the technology behind flow monitoring, please see Monit oring Bandwidt h via Flows 1820 section.

Add Sensor
Sensor Settings
Tags
676
07.02.2013
Net Flow Specific Set t ings 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. Note: When configuring export, please make sure you select the appropriate NetFlow version for this sensor. Enter the IP address of the sending device you want to receive the NetFlow from. Enter an IP address to receive data from a specific device only, or leave the field empty to receive data from any device on the specified port. 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. 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! Define if you want to use the sampling mode. This setting must accord to the setting in the flow exporter. Choose between: Off: The standard flow will be used. On: Switch into sampling mode and specify the sampling rate below. Sampling Rate This field is only visible when sampling mode is enabled above. Enter a number that matches the sampling rate in your device. If the number is different, monitoring results will be incorrect. Please enter an integer value.
Sender IP
Sampling Mode
07.02.2013
677
Net Flow Specific Set t ings Channel Definition Please enter a channel definition to divide the traffic into different channels. Write each definition in one line. For detailed information, please see Channel Definit ions for xFlow, IPFIX , and Packet Sniffer Sensors 1876 section. All traffic for which no channel is defined will be accounted to the default channel named Ot her. Note: Extensive use of many filters can cause load problems on your probe system. We recommend defining specific, well-chosen filters for the data you really want to analyze. Define if the probe will write a log file of the stream and packet data to the data folder (see Dat a St orage 1912 ). Choose between: None (recommended): Do not write additional log files. Recommended for normal use cases. Only for t he 'Ot her' channel: Only write log files of data that is not filtered otherwise and therefore accounted to the default Ot her channel. All st ream dat a: Write log files for all data received. Note: Use with caution! When enabled, huge data files can be created. Please use for a short time and for debugging purposes only.
Exclude Filter
Chart Type
678
07.02.2013
Inherited Settings
07.02.2013
679
Maintenance Window
Maintenance End At
Dependency Type
680
07.02.2013
Delay (Seconds)
07.02.2013
681
682
07.02.2013
Toplists

Notifications
Others
133
section.
Related Topics
1872
1876
07.02.2013
683
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 57 Oracle SQL Sensor
6.8.57 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 queryif configuredhave been received). Additionally, it can read the number of records and a value. The following SQL servers are supported: Supports Oracle servers 11g, 10g, 9i, 8i, 8.0, and 7.3, including Oracle 10g Express, and Oracle 8i Personal and Lite editions (requires default TCP port setting 1521). Note: On the client computer running the PRTG probe where this sensor is created on, Oracle Net is used for direct TCP/IP communication; OCI is not supported any more. You do not need to install an Oracle client or define a TNSNAMES.ORA on the client computer.
Add Sensor
Sensor Settings
Tags
Priority
684
13.06.2013
Oracle Specific Dat a 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. Enter the port number that will be used for the connection. Default value is 1521. Please enter an integer value.
Port
DB/SQL Dat a Database Enter the name of the SQL database the sensor will connect to. For example, such a database's name could be orcl Enter the user name that will be used for the database connection. Enter the password that will be used for the database connection.
User Password
Dat a SQL Expression Enter a valid SQL statement to execute on the server. In your SELECT statement, please specify the field name explicitly. Do not use SELECT *! For example, a correct expression could be: SELECT sum(salary) FROM hr.employees. When a cursor is returned (i.e. with a SELECT statement), only the first row of data will be processed.
Record Count
Post-processing
If the SQL expression returns a result set, please define if you want to further process it. Choose between: Ignore result set : Do not do anything with the data returned. Process numerical result : Regard the result set returned as integer or float. You can set the sensor to Warning or Down status for specific thresholds. Define below.
13.06.2013
685
Process st ring result : Regard the result set returned as a string. You can set the sensor to error for certain sub-strings contained or missing. Define below. Monit or for changes: Monitor if the result set has changed since last check. The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 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 t han: Result set must be below the value provided below. does not equal: Result set must be unequal to the value provided below. Note: This threshold check the SQL result set only. You can set additional thresholds in the sensor's channel settings 1566 . 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. 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 t han: Result set must be below the value provided below. does not equal: Result set must be unequal to the value provided below. Note: This threshold check the SQL result set only. You can set additional thresholds in the sensor's channel settings 1566 . 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.
Condition "Down"
686
13.06.2013
Chart Type
Inherited Settings
13.06.2013
687
Maintenance Window
Maintenance End At
Dependency Type
688
13.06.2013
Delay (Seconds)
13.06.2013
689
More
Knowledge Base: How do PRTG sensors connect to Oracle databases? http://www.paessler.com/knowledgebase/en/topic/52803

Notifications
690
13.06.2013
Others
133
section.
13.06.2013
691
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 58 Packet Sniffer Sensor
6.8.58 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 Monit oring Bandwidt h via Packet Sniffing 1818 section. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.
Add Sensor
Sensor Settings
Tags
692
08.10.2013
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 Filt er Rules for xFlow, IPFIX , and Packet Sniffer Sensors 1872 section. First, the filters defined in the Include Filt er field are considered. From this subset, you can explicitly exclude traffic, using the same syntax. For detailed information, please see Filt er Rules for xFlow, IPFIX , and Packet Sniffer Sensors 1872 section. 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. Define if the probe will write a log file of the stream and packet data to the data folder (see Dat a St orage 1912 ). Choose between: None (recommended): Do not write additional log files. Recommended for normal use cases. Only for t he 'Ot her' channel: Only write log files of data that is not filtered otherwise and therefore accounted to the default Ot her channel. All st ream dat a: Write log files for all data received. Note: Use with caution! When enabled, huge data files can be created. Please use for a short time and for debugging purposes only.
Exclude Filter
Network Adapters
Channel Configurat ion 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.
08.10.2013
693
Channel Configurat ion Mail: Internet mail traffic. Chat : Traffic caused by chat and instant messaging. Remot e Cont rol: Traffic caused by remote control applications, such as RDP, SSH, Telnet, VNC. Infrast ruct ure: Traffic caused by network services, such as DHCP, DNS, Ident, ICMP, SNMP. Net BIOS : Traffic caused by NetBIOS communication. Ot her Prot ocols: Traffic caused by various other protocols via UDP and TCP. For each traffic group, you can select how many channels will be used for each group, i.e. how detailed 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 Ot her. Yes: Count all traffic of this group and summarize it into one channel. Det ail: Count all traffic of this group and further divide it into different channels. The traffic will appear in several channels as shown in the Cont ent column. Note: Extensive use of this option can cause load problems on your probe system. We recommend setting specific, well-chosen filters for the data you really want to analyse.
Chart Type
694
08.10.2013
Inherited Settings
08.10.2013
695
Maintenance Window
Maintenance End At
Dependency Type
696
08.10.2013
Delay (Seconds)
08.10.2013
697
Toplists

Notifications
Others
133
section.
Related Topics
1872
1876
698
08.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 59 Packet Sniffer (Custom) Sensor
6.8.59 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 Monit oring Bandwidt h via Packet Sniffing 1818 section. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Add Sensor
Sensor Settings
08.10.2013
699
Priority
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 Filt er Rules for xFlow and Packet Sniffer Sensors 1872 section. First, the filters defined in the Include Filt er field are considered. From this subset, you can explicitly exclude traffic, using the same syntax. For detailed information, please see Filt er Rules for xFlow and Packet Sniffer Sensors 1872 section. Please enter a channel definition to divide the traffic into different channels. Write each definition in one line. For detailed information, please see Channel Defint ions for xFlow and Packet Sniffer Sensors 1876 section. All traffic for which no channel is defined will be accounted to the default channel named Ot her. Note: Extensive use of many filters can cause load problems on your probe system. We recommend defining specific, well-chosen filters for the data you really want to analyse. We recommend to not use more than 20 channels in graphs and tables, and not more than 100 channels in total. For performance reasons, it is better to add several sensors with less channels each. 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. Define if the probe will write a log file of the stream and packet data to the data folder (see Dat a St orage 1912 ). Choose between: None (recommended): Do not write additional log files. Recommended for normal use cases.
Exclude Filter
Channel Definition
Network Adapters
700
08.10.2013
Sniffer specific Only for t he 'Ot her' channel: Only write log files of data that is not filtered otherwise and therefore accounted to the default Ot her channel. All st ream dat a: Write log files for all data received. Note: Use with caution! When enabled, huge data files can be created. Please use for a short time and for debugging purposes only.
Chart Type
08.10.2013
701
Inherited Settings
Maintenance Window
Maintenance End At
702
08.10.2013
Delay (Seconds)
08.10.2013
703
704
08.10.2013
Toplists

Notifications
Others
133
section.
Related Topics
1872
1876
08.10.2013
705
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 60 Passive Application Performance Sensor
6.8.60 Passive Application Performance Sensor

The Passive Application Performance sensor monitors Transport Control Protocol (TCP) connection timings using packet sniffer. It can measure the performance of many different web applications without actually having direct access to neither the client nor the server. In order to obtain valuable data, these applications must work TCP-based and initiate a new session with each request. The sensor shows the total number of packets per second on the selected network card, the number of dropped packets per second by PRTG because of system overload (more processor power is required if this value is above zero to cope with the traffic), as well as the number of currently active connections on all monitored applications. For defined applications, the sensor can show (together with the corresponding application name): Request time in msec: average time between the initial (SYN) packet from the client and the first request package from the client Response time in msec: average time between the initial (SYN) packet from the client and first packet of the result from the server ACK (acknowledge) time in msec: average time between the initial (SYN) packet of a connection from the client until the server sends an ACK (acknowledge) packet. This means that a TCP connection was successfully established (in LANs this value is zero in most cases and only increases for extreme loads). Count: total number of observed connections to the service in the last monitoring interval. This is the number of measurements the average is based on. The higher the value the more reliable/averaged the data is. If this value is zero, PRTG did not see any packets for this service. Important notice: This sensor is an experimental sensor. Currently, it is in bet a status. The methods of operating can change at any time, as well as the available settings. Do not expect that all functions will work properly, or that this sensor works as expected at all. Be aware that this type of sensor can be removed again from PRTG at any time. For a general introduction to the technology behind packet sniffing, please see Monit oring Bandwidt h via Packet Sniffing 1818 section. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.
Add Sensor
706
08.10.2013
Sensor Settings
Tags
Priority
Applicat ions Network Adapter Applications Select the network adapter you want to monitor. Define the applications you want to monitor. For each application, use one dedicated line. Use the following syntax to define an application to be monitored: ip:port=application. Provide the IP address and port number of the application. Behind the equals sign, enter a name for the application which will be displayed in the channels. Please enter a string. This sensor will create four sensor channels with the application name, e.g., "Application (ACK)".
08.10.2013
707
Inherited Settings
708
08.10.2013
Maintenance End At
Dependency Type
08.10.2013
709

710
08.10.2013
Notifications
Others
133
section.
08.10.2013
711
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 61 PerfCounter Custom Sensor
6.8.61 PerfCounter Custom Sensor

The PerfCounter Custom sensor monitors a configured set of Windows Performance Counters. You can define your own channels. There are no predefined channels available for this sensor type. To find out which performance counters are available on the target system and what their names are, please see section More 717 .

For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. In the parent device's 264 Credent ials for Windows Sy st ems settings, please prefer using Windows domain credentials. Note: If you use local credentials, please make sure the same Windows user accounts (with same username and password) exist on both the system running the PRTG probe and the target computer. If you fail to do so, a connection via Performance Counters will not be possible. Note: The user account has to be a member of the Performance Monitor Users user group on the target system.

In order for this sensor to work with Windows Performance Counters, please make sure the RemoteRegistry "Remote Registry" Windows service is running on the target computer. If you fail to do so, a connection via Performance Counters will not be possible. 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
712
13.06.2013
Performance Count er Set t ings List of Counters Enter a list of performance counters which will be queried. Define one counter per row. PRTG will create one channel for each counter. Use the following syntax: the name of the counter, followed by two colons (::) and the unit. Example: \Processor (_Total)\% Processor Time::% This setting determines if the returning value will be displayed as absolute value or if the difference between the last and the current value will be used. Choose between: Absolut e (recommended): The returning value will be displayed as absolute value. Difference: The difference between last and current value will be displayed. Note: Please make sure that all counters which are monitored are capable of this mode if you select it.
Mode
Sensor Settings
Tags
Priority
13.06.2013
713
Performance Count er Set t ings List of Counters The list of counters 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. The mode in which the returning values are displayed. 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.
Mode
Chart Type
Inherited Settings
714
13.06.2013
Maintenance Window
Maintenance End At
Dependency Type
13.06.2013
715
Delay (Seconds)
716
13.06.2013
More
Knowledge Base: How can I find out the names of available Performance Counters?
13.06.2013
717
http://www.paessler.com/knowledgebase/en/topic/50673 Edit Sensor Channels

Notifications
Others
133
section.
718
13.06.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 62 PerfCounter IIS Application Pool Sensor
6.8.62 PerfCounter IIS Application Pool Sensor

The PerfCounter IIS Application Pool sensor monitors a Microsoft Internet Information Services (IIS) application pool using Windows Performance Counters. This sensor can show the overall state of an application pool, the number of worker processes, the number of failures in worker processes, as well as the number of ping failures, shutdown failures, and startup failures in worker processes.
Requirement: Microsoft IIS Version 7.5

In order to monitor Microsoft Internet Information Services (IIS) application pools, this sensor needs IIS version 7.5 or later to be installed on the target system.

For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. In the parent device's 264 Credent ials for Windows Sy st ems settings, please prefer using Windows domain credentials. Note: If you use local credentials, please make sure the same Windows user accounts (with same username and password) exist on both the system running the PRTG probe and the target computer. If you fail to do so, a connection via Performance Counters will not be possible. Note: The user account has to be a member of the Performance Monitor Users user group on the target system.

In order for this sensor to work with Windows Performance Counters, please make sure the RemoteRegistry "Remote Registry" Windows service is running on the target computer. If you fail to do so, a connection via Performance Counters will not be possible. 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.

03.05.2013
719
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor Microsoft Internet Information Services (IIS) application pools, PRTG will create one sensor for each pool. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
IIS Applicat ion Pool Specific Application Pool A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
Priority
720
03.05.2013
IIS Applicat ion Pool Specific Application Pool The name of the application pool that is 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.
Chart Type
Inherited Settings
03.05.2013
721
Maintenance Window
Maintenance End At
Dependency Type
722
03.05.2013
Delay (Seconds)
03.05.2013
723
724
03.05.2013

Notifications
Others
133
section.
03.05.2013
725
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 63 Ping Sensor
6.8.63 Ping Sensor

The Ping sensor sends an Internet Control Message Protocol (ICMP) echo request ("Ping") from the computer running the probe to the device it is created on, in order 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
Sensor Settings
Tags
Priority
Ping Set t ings Timeout (seconds) Enter a timeout in seconds for the Ping. If the reply takes longer than this value the request is aborted and an error message is triggered. Enter the packet size in bytes for the Ping. You can choose any value between 1 and 10000. We recommend using the default value.
Packet Size (Bytes)
726
27.11.2012
Ping Set t ings Ping Method Define the kind of Ping check that will be performed. Choose between: Send one single Ping : With each scanning interval, send a single Ping only. A sensor in this setting will show the Ping time only. This setting is good for simply availability monitoring. Send mult iple Ping request : With each scanning interval, send multiple Pings in a row. A sensor in this setting will also show minimum and maximum Ping time as well as packet loss (in percent). This setting is good if you want to create reports about average Ping times out of a series of ping requests. 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. 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. You can define that a Down status of this sensor will be acknowledged 136 automatically. Show "Down" st at us on error (default ): Do not automatically acknowledge an alarm if this sensor changes to a Down status. Show "Down (Acknowledged)" st at us on error: Automatically acknowledge an alarm. If this sensor changes to a Down status, it will automatically change to Down (Acknowledged). Note: The sensor will also go through a Down status, so any sensor state triggers 1573 using this will still provoke notifications, as configured.
Ping Delay (in ms)
Auto Acknowledge
27.11.2012
727
Inherited Settings
728
27.11.2012
Maintenance End At
Dependency Type
27.11.2012
729
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?
730
27.11.2012

Notifications
Others
133
section.
27.11.2012
731
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 64 Ping Jitter Sensor
6.8.64 Ping Jitter Sensor

The Ping Jitter sensor sends a series of Internet Control Message Protocol (ICMP) echo requests ("Pings") to the given URI to determine the statistical jitter. The Real Time Jitter value is updated every time a packet is received using the formula described in RFC 1889: Jitter = Jitter + ( abs( ElapsedTime OldElapsedTime ) Jitter ) / 16 The Statistical Jitter value is calculated on the first x packets received using the statistical variance formula: Jitter Statistical = SquareRootOf( SumOf( ( ElapsedTime[i] Average) ^ 2 ) / ( ReceivedPacketCount 1 ) ) Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Add Sensor
Sensor Settings
Basic Sensor Set t ings Sensor Name Enter a meaningful name to identify the sensor. The name will be
732
07.02.2013
Basic Sensor Set t ings 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 84 from objects further up in the device tree. Those are not visible here. Select a priority for the sensor. This setting determines where the sensor will be placed in sensor lists. Top priority will be at the top of a list. You can choose from one star (low priority) to five stars (top priority).
Priority
Sensor Set t ings Ping Count Define the number of pings that will be sent. Please enter an integer value.
Chart Type
07.02.2013
733
Inherited Settings
Maintenance Window
Maintenance End At
734
07.02.2013
Delay (Seconds)
07.02.2013
735

Notifications
Others
133
section.
736
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 65 Pingdom Sensor
6.8.65 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. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Add Sensor
Sensor Settings
Tags
07.02.2013
737
Sensor Set t ings 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. Please enter the username of the Pingdom account you want to query. Please enter a string. Please enter the password of the Pingdom account you want to query. Please enter a string. 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' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Username
Password
If Value Changes
Chart Type
738
07.02.2013
Inherited Settings
By default, all following settings are inherited from objects higher in the hierarchy and should be changed there, if necessary. Often, best practice is to change them centrally in the Root 213 group's settings. To change a setting for this object, 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 Int erval 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 1691 . 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".
07.02.2013
739
Maintenance End At
Dependency Type
740
07.02.2013

07.02.2013
741
Notifications
Others
133
section.
742
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 66 POP3 Sensor
6.8.66 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
Sensor Settings
Tags
Priority
27.11.2012
743
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. 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. Specifiy if an encryption will be used for the connection. Choose between: Encry pt dat a using Transport -Level Securit y (TLS) No encry pt ion (use plain t ext )
Port
Security
SSL-Method
744
27.11.2012
Pop3 Aut horisat ion POP3 Authentication Type Select the kind of authentication for the POP3 connection. Choose between: Wit hout Login: Monitor the connection to the POP3 server only. Username and Password: Log into the POP3 server with user name and password (simple login, non-secure). 128-bit MD5 hash value (APOP): Send the password in an encrypted form using APOP. This option must be supported by the POP3 server you're connecting to. Username This field is only visible if an option with login is selected above. Enter a username for POP3 authentication. Please enter a string. This field is only visible if an option with login is selected above. Enter a password for POP3 authentication. Please enter a string.
Password
Chart Type
27.11.2012
745
Inherited Settings
Maintenance Window
Maintenance End At
746
27.11.2012
Delay (Seconds)
27.11.2012
747

Notifications
Others
133
section.
748
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 67 POP3 Email Count Sensor
6.8.67 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. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Add Sensor
Sensor Settings
Tags
07.02.2013
749
Sensor Set t ings 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. Define the passwort for the POP3 account. Note: As POP3 server, this sensor will use the parent device's IP Address/DNS Name value. Define the port number the POP3 server is running at. Please enter an integer value. Note: As POP3 server, this sensor will use the parent device's IP Address/DNS Name value. 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. Optionally define a From address. Only mails containing this will be counted by the sensor. Please enter a string or leave the field empty. Optionally define an email Subject. Only mails containing this will be counted by the sensor. Please enter a string or leave the field empty.
Password
Mailserver POP3 Port
Use SSL
Filter From Address
Filter Subject Content
750
07.02.2013
Chart Type
Inherited Settings
07.02.2013
751
Maintenance Window
Maintenance End At
Dependency Type
752
07.02.2013
Delay (Seconds)
07.02.2013
753

Notifications
Others
133
section.
754
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 68 Port Sensor
6.8.68 Port Sensor

The Port sensor monitors a network service by connecting to its port. It tries to connect to the specified TCP/IP port number of a device and waits for the request to be accepted. Depending on your settings, it can alert you either when the monitored port is open, or when it is closed.
Add Sensor
Sensor Settings
Tags
Priority
Port Specific Timeout (sec.) Enter a timeout in seconds for the port connect. If the reply takes longer than this value the request is aborted and an error message is triggered. Enter the number of the port the sensor will try to connect to. Please enter an integer value.
Port
11.10.2013
755
Port Specific SSL (Secure Sockets Layer) Specify if an encryption will be used for the connection. Choose between: Don't use SSL (recommended) Use SSL
SSL-Method
Advanced Sensor Set t ings Goal Define how the sensor will report on the port defined above. Choose between: Open: The sensor will return a green OK status if the port is open, and show a red Down status if the port is closed. Closed: The sensor will return a green OK status if the port is closed, and show a red Down status if the port is open. Command Define whether a command will be sent after the port is opened. Choose between: Don't send command: Only check if a connection to the port is possible. Send command: Open a Telnet session to the respective port and send the command. Note: You cannot use this option if the target machine is a webserver. Command 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. Define if the response received will be further processed. Choose between: Ignore response: Do not check the response.
Response
756
11.10.2013
Advanced Sensor Set t ings Check response code (int eger): Check if the response matches a defined response code. Define below. Check response t ext : Check if the response matches a defined response text. Define below. Allowed Code This field is only visible if response code check is enabled above. Enter a code that must be returned. If it does not match the sensor will be set to a Down status. Please enter an integer value.
Check For Existing Keywords (Positive)
This setting is only visible if 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 key word check (posit ive): Check if a certain keyword exists in the received value. Define below.
Text Must Include
This setting is only visible if keyword check is activated above. Enter a search string that must be contained in the returned value. 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 1886 section.
For Keyword Search Use
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 key word check (negat ive): Check if a certain keyword does not exist in the received value. Define below.
Text Must Not Include
This setting is only visible if keyword check is activated above. Enter a search string that must not be contained in the returned value. 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 1886 section.
11.10.2013
757
Chart Type
Inherited Settings
758
11.10.2013
Maintenance Window
Maintenance End At
Dependency Type
11.10.2013
759
Delay (Seconds)
760
11.10.2013

Notifications
Others
133
section.
11.10.2013
761
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 69 Port Range Sensor
6.8.69 Port Range Sensor

The Port Range sensor monitors a network service by connecting to various TCP/IP ports. It tries to connect to the specified TCP/IP port numbers of a device in succession and waits for each request to be accepted. It returns the number of closed ports and open ports in two different channels. Optionally, you can set limits in the sensor's channel settings. This way you can get alerted about open/closed ports.
Add Sensor
Sensor Settings
Tags
Priority
Port Range Specific Timeout (sec.) Enter a timeout in seconds for the port connect. If the reply takes longer than this value the request is aborted and an error message is triggered. Specify in milliseconds how long the sensor will wait to go to the next port while running through all given ports.
Port-by-Port-Delay (ms)
762
29.11.2012
Port Range Specific Port Range Selection Method Define whether you want to monitor all ports within a range or if you want to monitor several individual ports. Choose between: Port Range wit h st art /end: Monitor ports within a range. List of Port s: Provide a list of several individual ports to monitor. Range Start This field is only visible if the port range method is enabled above. Enter the port number where the scan will start. Please enter an integer value. This field is only visible if the port range method is enabled above. Enter the port number where the scan will end. Please enter an integer value. This field is only visible if the list of ports method is enabled above. Enter the numbers of the ports the sensor will try to connect to. Please enter one or more individual integer values. Define what will be done in case the value of a sensor channel changes. Choose between: Ignore changes: No action will be taken on change. Trigger 'change' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Range End
Port List
If Value Changes
Chart Type
29.11.2012
763
Inherited Settings
Maintenance Window
764
29.11.2012
Maintenance End At
Dependency Type
Delay (Seconds)
29.11.2012
765

Notifications
Others
133
section.
766
29.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 70 Probe Health Sensor
6.8.70 Probe Health Sensor

The Probe Health sensor monitors internal PRTG parameters. It shows the state of the PRTG probe (either for the local probe, a remote probe 1888 , or a cluster 76 probe). This sensor type is created automatically by PRTG and cannot be deleted. It checks various parameters of your PRTG system which can affect the quality of the monitoring results: Healt h: This index value sums up the probe state into a value between 100% (healthy) and 0% (failing). Frequent or repeated health values below 100% should be investigated. CPU Load: This channel shows the current percentage CPU load. Extensive CPU load can lead to false, incomplete, and incorrect monitoring results. This value usually should stay below 50%. Handles: This is a counter for the data structures of the operating system. It is responsible for internal resource management. Repeated obviously increasing values should be investigated. Int erval Delay non-WMI&SNMP: This channel shows the percentage interval delay for all sensor types which are not from the type SNMP or WMI. Int erval Delay SNMP: This channel shows the percentage interval delay for SNMP sensors. If this value is above 0% there are probably very slow SNMP V3 sensors. In this case, try to increase the monitoring intervals or distribute the sensors over several probes. Int erval Delay WMI: This channel shows the percentage interval delay for WMI sensors. If this value is above 0% WMI sensors could not be checked according to their interval. 100% means that WMI sensors on the average are checked with twice their interval. For values above 0% try to increase the monitoring intervals or distribute the sensors over several probes to keep the number of WMI sensors per probe below 120 (with 60 seconds interval) or 600 (with 300 seconds interval). Lost Flow Packet s: This channel shows the percentage of lost flow packets. Memory Usage: This channel shows the amount of memory being used by the PRTG probe service as reported by the memory manager. Repeated obviously increasing values should be investigated. If the value is constantly above 2 GB this indicates that PRTG runs at its limits. In this case you should distribute some sensors to Remote Probe 1888 . Message Queue: This channel shows the number of monitoring results from the probe which have not been processed yet by the core. This value usually should stay below 1/10 of the sensor count. Open Request s: This channel shows the number of currently active monitoring requests. This value should stay below the maximum of 500 open requests. Threads: This channel shows the number of program parts which are running simultaneously currently. This value can increase with heavy load. The number should not exceed 100 in normal operation. This sensor can be set up on a Probe Device only!
Sensor Settings
03.05.2013
767
Tags
Priority
Chart Type
768
03.05.2013
Inherited Settings
03.05.2013
769

Notifications
Others
133
section.
770
03.05.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 71 QoS (Quality of Service) One Way Sensor
6.8.71 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 1887 configured in your setup. The sensor can be created on the Probe Device of either a local or remote probe. Note: This sensor type cannot be cloned using the Clone Object
1592
function.
For a general introduction to the technology behind Quality of Service monitoring, please see Monit oring Qualit y of Service 1825 section.
Add Sensor
Sensor Settings
Tags
Priority
27.11.2012
771
Qualit y of Service Measurement 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. 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 1887 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. 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. Define the source and t arget port for the UDP packets. This port will be used on both the source and target probe. Please use a different port for each QoS sensor to make sure packets can be assigned correctly. Enter an integer value between 1024 and 65536. Note: This port must be available on both the source and target system. Define how many packets are sent for each scanning interval. We recommend using 1000. Please enter an integer value. Define the size in bytes of the packets sent. We recommend using 172. Please enter an integer value. Define the size in milliseconds that will be waited between two packets. We recommend using 20. Please enter an integer value. 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. 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.
Target Probe
Target IP
Port
Number of Packets
Size of Packets (Bytes)
Time between packets (ms) DSCP
802.1p
772
27.11.2012
Chart Type
Inherited Settings
27.11.2012
773
Maintenance Window
Maintenance End At
Dependency Type
774
27.11.2012
Delay (Seconds)
27.11.2012
775

Notifications
Others
133
section.
776
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 72 QoS (Quality of Service) Round Trip Sensor
6.8.72 QoS (Quality of Service) Round Trip Sensor

The QoS (Quality of Service) Round Trip sensor monitors parameters regarding the quality of a network connection between two probes. This is important, for example, when using Voice over IP (VoIP) over this connection. The sensor sends a series of UDP packets from the 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), the round trip time (RTT), etc. Note: In order for this sensor to work, there has to be at least one remote probe 1887 configured in your setup. The sensor can be created on the Probe Device of either a local or remote probe. Note: This sensor type cannot be cloned using the Clone Object
1592
function.
For a general introduction to the technology behind Quality of Service monitoring, please see Monit oring Qualit y of Service 1825 section.
Add Sensor
Sensor Settings
Tags
Priority
03.05.2013
777
Qualit y of Service Measurement 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. 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 1887 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. 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. Define the source and t arget port for the UDP packets. This port will be used on both the source and target probe. Please use a different port for each QoS sensor to make sure packets can be assigned correctly. Enter an integer value between 1024 and 65536. Note: This port must be available on both the source and target system. Define how many packets are sent for each scanning interval. We recommend using 1000. Please enter an integer value. Define the size in bytes of the packets sent. We recommend using 172. Please enter an integer value. Define the size in milliseconds that will be waited between two packets. We recommend using 20. Please enter an integer value. 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. 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.
Target Probe
Target IP
Port
Number of Packets
Size of Packets (Bytes)
Time between packets (ms) DSCP
802.1p
778
03.05.2013
Chart Type
Inherited Settings
03.05.2013
779
Maintenance Window
Maintenance End At
Dependency Type
780
03.05.2013
Delay (Seconds)
03.05.2013
781

Notifications
Others
133
section.
782
03.05.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 73 RADIUS Sensor
6.8.73 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
Sensor Settings
Tags
Priority
19.07.2013
783
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. Define the user name used for authentication at the server. Please enter a string. Define the password used for authentication at the server. Please enter a string. Note: The password must not be longer than 6 characters. Define the shared secret used for authentication at the server. Please enter a string. Enter the port number used for connection to the server. Default value is 1812. Please enter an integer value. Define a valid NAS IP address or leave the field empty. Enter a NAS identifier. Please enter a string or leave the field empty. Add a check mark if you want to use the Challenge Handshake Authentication Protocol.
User
Password
Secret
Port
NAS IP Address NAS-Identifier Use Chap
Chart Type
784
19.07.2013
Inherited Settings
Maintenance Window
19.07.2013
785
Maintenance End At
Dependency Type
Delay (Seconds)
786
19.07.2013

Notifications
Others
133
section.
19.07.2013
787
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 74 RDP (Remote Desktop) Sensor
6.8.74 RDP (Remote Desktop) Sensor

The RDP (Remote Desktop) Sensor monitors remote desktop services (RDP, Terminal Services Client).
Add Sensor
Sensor Settings
Tags
Priority
Sensor 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. 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.
Port
788
27.11.2012
Chart Type
Inherited Settings
27.11.2012
789
Maintenance Window
Maintenance End At
Dependency Type
790
27.11.2012
Delay (Seconds)
27.11.2012
791

Notifications
Others
133
section.
792
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 75 SCVMM Host Sensor
6.8.75 SCVM M Host Sensor

The SCVMM Host sensor monitors a host that is managed by a Microsoft System Center Virtual Machine Manager (SCVMM). This can be, for example, a Hyper-V host, a VMware host, or a XenServer host. It can show the CPU usage, free memory (in bytes and percentage), the overall state, the communication state, the status of the cluster node, the state of the virtual server, the computer state, and the VM count. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.


Requirement: Remote PowerShell 2.0

This sensor type uses PowerShell commands. In order to monitor devices with this sensor, Remot e PowerShell 2.0 has to be enabled. For detailed information, please see More 798 section below. Note: PowerShell 1.0 is not supported.
Requirement: VMM PowerShell Plugin

This sensor type needs the VMM PowerShell Plugin to be installed on the target machine. Under Windows 2008 and 2012 it is part of the VMM 2008 Administrator Console, or the VMM 2012 Management Console, respectively.
23.10.2013
793
Note: To provide good performance, the System Center Virtual Manager (SCVMM) only reads the performance data from time to time and caches them. Because of this, updates can take up to several minutes. If your monitoring returns the same values again and again, please increase the scanning interval.
Requirement for Windows Server 2012 Compatibility

In order to make this sensor type compatible for Windows Server 2012 systems, the following requirements have to be met: The SCVMM PowerShell module has to be in the directory C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\psModules\virtualmachinemanager \virtualmachinemanager. You have to set the execution policy in PowerShell to allow the execution of Import-Module C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\psModules \virtualmachinemanager\virtualmachinemanager. Use the command Set -Execut ionPolicy . We recommend the execution policy Remot eSigned; AllSigned and Unrest rict ed are also possible.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor hosts, PRTG will create one sensor for each host. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Host Set t ings Host Select the host you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. Note: Please make sure the name of your hosts do not contain unsupported characters, especially avoid the hash ('#') sign. We recommend to not rename hosts once you've set up monitoring. For detailed information, please see More 563 section below.
Sensor Settings
794
23.10.2013
Tags
Priority
Host Set t ings Sensor Result Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results. Writ e sensor result t o disk (Filename: "Result of Sensor [ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Chart Type
23.10.2013
795
Inherited Settings
796
23.10.2013
Maintenance End At
Dependency Type
23.10.2013
797
More
Knowledge Base: How do I enable and use remote commands in Windows PowerShell? http://www.paessler.com/knowledgebase/en/topic/44453 Knowledge Base: Why don't my Hyper-V sensors work after changing names? http://www.paessler.com/knowledgebase/en/topic/15533
798
23.10.2013

Notifications
Others
133
section.
23.10.2013
799
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 76 SCVMM Virtual Machine Sensor
6.8.76 SCVM M Virtual M achine Sensor

The SCVMM Virtual Machine sensor monitors a virtual machine (VM) that is managed by a Microsoft System Center Virtual Machine Manager (SCVMM). This can be, for example, a HyperV virtual machine, a VMware virtual machine, or a XenServer virtual machine. It can show the CPU usage, the status of a VM, and disk read and write speed. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.


Requirement: Remote PowerShell 2.0

This sensor type uses PowerShell commands. In order to monitor devices with this sensor, Remot e PowerShell 2.0 has to be enabled. For detailed information, please see More 805 section below. Note: PowerShell 1.0 is not supported.
Requirement: VMM PowerShell Plugin

This sensor type needs the VMM PowerShell Plugin to be installed on the target machine. Under Windows 2008 and 2012 it is part of the VMM 2008 Administrator Console, or the VMM 2012 Management Console, respectively.
800
23.10.2013
Note: To provide good performance, the System Center Virtual Manager (SCVMM) only reads the performance data from time to time and caches them. Because of this, updates can take up to several minutes. If your monitoring returns the same values again and again, please increase the scanning interval.
Requirement for Windows Server 2012 Compatibility

In order to make this sensor type compatible for Windows Server 2012 systems, the following requirements have to be met: The SCVMM PowerShell module has to be in the directory C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\psModules\virtualmachinemanager \virtualmachinemanager. You have to set the execution policy in PowerShell to allow the execution of Import-Module C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\psModules \virtualmachinemanager\virtualmachinemanager. Use the command Set -Execut ionPolicy . We recommend the execution policy Remot eSigned; AllSigned and Unrest rict ed are also possible.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor VMs, PRTG will create one sensor for each VM. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Virt ual Machine Set t ings Virtual Machine Select the Virtual Machine (VM) you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. Note: Please make sure the name of your VMs do not contain unsupported characters, especially avoid the hash ('#') sign. We recommend to not rename VMs once you've set up monitoring. For detailed information, please see More 563 section below.
Sensor Settings
23.10.2013
801
Tags
Priority
Virt ual Machine Set t ings Sensor Result Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results. Writ e sensor result t o disk (Filename: "Result of Sensor [ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Chart Type
802
23.10.2013
Inherited Settings
23.10.2013
803
Maintenance End At
Dependency Type
804
23.10.2013
More
Knowledge Base: How do I enable and use remote commands in Windows PowerShell? http://www.paessler.com/knowledgebase/en/topic/44453 Knowledge Base: Why don't my Hyper-V sensors work after changing names? http://www.paessler.com/knowledgebase/en/topic/15533
23.10.2013
805

Notifications
Others
133
section.
806
23.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 77 Sensor Factory Sensor
6.8.77 Sensor Factory Sensor

The Sensor Factory sensor is a powerful tool that allows you to create your own sensor with channels based on data from other sensors. You can define one or more channels using formulas that combine monitoring results from other sensors. Samples for usage are: Show single channels of one or more sensors in one graph. Use the data from single channels of one or more sensors to calculate new values (for example, you can subtract, multiply, and divide). Create graphs with data from other sensor channels and add horizontal lines at specific vertical positions. Note: A sensor factory sensor does not show a "Downtime" channel. Downtime cannot be calculated for this sensor type. Note: The Sensor Factory sensor might not work with flow sensors 1820 . Sensor types using active flow timeout, this is, NetFlow and jFlow sensors 279 , are not supported by the Sensor Factory sensor. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Add Sensor
Sensor Settings
03.05.2013
807
Tags
Priority
808
03.05.2013
Sensor Fact ory Specific Set t ings 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 812 below. 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: Fact ory sensor shows error st at e when one or more source sensors are in error st at e: 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. Fact ory sensor shows warning st at e when one or more source sensors are in error st at e: 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 cust om formula: Define the status of the factory sensor by adding a status definition in the field below. Status Definition This field is only visible if 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 St at us 819 below. 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 calculat e fact ory channels t hat use t he 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. Calculat e t he fact ory 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.
Error Handling
If a Sensor Has No Data
03.05.2013
809
Inherited Settings
Maintenance Window
Maintenance End At
810
03.05.2013
Delay (Seconds)
03.05.2013
811
Define Sensor Channels

The channels of a Sensor Factory sensor are controlled by the Channel Definit ion text field. Using a special syntax you can refer to other sensor channels, calculate values, and add horizontal lines. You can define factory sensor channels using data from any other sensor's channels on your PRTG core server.
812
03.05.2013
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 Healt h channel (ID 0) of the Core/Probe Healt h sensor (ID 1001) running on the Local Probe device. The second channel (#2) collects data from the Traffic out channel (ID 1) of a traffic sensor (ID 1004) measuring the system's local network card. Both channels will be shown together in the factory sensor's data tables and graphs.
The basic syntax for a sensor factory channel definition looks like this:
#<id>:<name>[<unit>] <formula>
For each channel one section is used. A section begins with the # sign. Function names in formulas are not case sensitive. The parameters are: <id> is the ID of the factory sensor's channel and must be a unique number > 0. <name> is the name of the factory sensor's channel (displayed in graphs and tables). [<unit >] is an optional unit description for the factory sensor's channel (e.g. bytes). If 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() 814 , min() 815 , max() 815 , avg() 815 , or percent () 816 .
Define Sensor ChannelsFormula Calculations

Within a formula the following elements are allowed to perform calculations with the values that are returned by one or more functions: Basic operations: + (add), - (substract), * (multiply), / (divide) Example: 3 + 5 * 2 Brackets: ( ) Example: 3 * (2 + 6)
03.05.2013
813
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.
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 () Funct ion 816 to make sure you obtain the expected values! There are calculations you cannot do: You cannot add/subtract a delta from a gauge channel (and vice versa). You cannot multiply two delta channels. You cannot compare a delta with a gauge channel. You cannot use a channel of (another) Sensor Factory sensor channel in the formula.
Define Sensor Channelschannel() Function

The channel() function allows to read the data from a channel of a different sensor. The syntax is:
channel(<sensorId>,<channelId>)
The parameters are: <sensorId> is the ID of the sensor. It is displayed on the sensor details page, in the 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.
814
03.05.2013
Example
channel(2001,2)
This function reads the data from channel ID 2 of the sensor with the ID 2001.
#1:Sample channel(2001,2)
This full channel definition reads the data from channel ID 2 of the sensor with the ID 2001 and displays it in the first factory sensor channel (#1), without any additional calculations.
Define Sensor Channelsmin() and max() Functions

The min() and max() functions return the minimum or maximum of the two values. The syntax is:
min(<a>,) max(<a>,)
Values for <a> and are either numbers or channel()
814
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 Channelsavg() Function

The avg() function returns the average of the two values. This equals: (a+b) / 2. The syntax is:
avg(<a>,)
Values for <a> and are either numbers or channel()
814
functions.
03.05.2013
815
Examples
avg(20,10)
This function returns 15: (20+10) / 2 = 15.

avg( channel(2001,1),channel(2002,1) )
This function returns the average of channel 1 of the sensor with ID 2001 and channel 1 of the sensor with ID 2002.
Define Sensor Channelspercent() Function

The percent () function calculates the percent value of two given values, for example, a channel and a fixed value. The syntax is:
percent(<source>,<maximum>[,<unit>])
The parameters are: <source> is the value the percent is calculated for. This is usually a channel() <maximum> is the limit value used for the percent calculation. [<unit >] is an optional unit the maximum is provided in. You can use constants with this function (see Const ant s 818 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
814
function.
816
03.05.2013
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.
Define Sensor ChannelsHorizontal Lines

You can add lines to the graph using a formula without channel() function. Use a fixed value instead. The syntax is:
#<id>:<name>[<unit>] <value>
The parameters are: <id> is the ID of the factory sensor's channel and must be a unique number > 1. Although 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.
03.05.2013
817
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.
Define Sensor ChannelsConstants

The following constants are defined and can be used in calculations: one = 1 kilo = 1000 mega = 1000 * kilo giga = 1000 * mega t era = 1000 * giga by t e = 1 kiloby t e = 1024 megaby t e = 1024 * kilobyte gigaby t e = 1024 * megabyte t eraby t e = 1024 * gigabyte bit = 1/8 kilobit = kilo / 8
818
03.05.2013
megabit = mega / 8 gigabit = giga / 8 t erabit = tera / 8
Define Sensor Statusstatus() Function

The status of a Sensor Factory sensor can be controlled by the St at us Definit ion text field, if the custom formula option is enabled in the Sensor Set t ings 807 . 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.
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.
03.05.2013
819
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.
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 812 . Using this functionality, it is for example possible to display the numeric status value of sensors in a factory sensor channel.
Using Factory Sensors in a Cluster Setup

If you're running PRTG in Clustering
76
mode, please note these additional facts:
If you add a Sensor Factory sensor underneath the Clust er Probe, and in the Sensor Factory formula, you refer to a channel of a sensor running on the Clust er Probe as well, the Sensor Factory sensor will show the data of all cluster nodes for this sensor channel. If you add a Sensor Factory sensor underneath the Local Probe, and in the Sensor Factory formula, you refer to a channel of a sensor running on the Clust er Probe, the Sensor Factory sensor will only show data of the primary master node for this sensor channel.
820
03.05.2013

Notifications
Others
133
section.
03.05.2013
821
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 78 sFlow Sensor
6.8.78 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). The sensor accepts RAW data only. The stream must be sent via IPv4. This sensor type cannot be used in cluster mode. You can set it up on a local probe or remote probe only, not on a cluster probe. For a general introduction to the technology behind flow monitoring, please see Monit oring Bandwidt h via Flows 1820 section.
Limitations of This Sensor Type

There are some limitations that you want to consider before using this sensor type: Only sFlow version 5 datagrams are supported Only IPv4 flows are supported Only the "raw packet header" format is supported Only the "Flow sample" format is supported. "Extended flow" and "Counter" formats cannot be processed PRTG processes only samples where the source ID matches the ifIndex of the input interface (avoiding double counted traffic) and ascending sequence numbers. Due to internal limitations, only interface numbers up to 65535 are supported. Sample packets have to be of ethernet type "IP" (with optional VLAN tag) Sampled packets of type TCP and UDP are supported We recommend using sFlow tester for debugging (see More section below).
Add Sensor
Sensor Settings
822
08.10.2013
Tags
Priority
sFlow Specific Set t ings 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. Note: When configuring export, please make sure you select the appropriate sFlow version 5. Enter the IP address of the sending device you want to receive the sFlow from. Enter an IP address to receive data from a specific device only, or leave the field empty to receive data from any device on the specified port. 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.
Sender IP
Receive sFlow Packets on IP
Channel Configurat ion Channel Selection Define the categories the traffic will be accounted to. There are different groups of traffic available. Choose between: Web: Internet web traffic.
08.10.2013
823
Channel Configurat ion File Transfer: Traffic caused by FTP. Mail: Internet mail traffic. Chat : Traffic caused by chat and instant messaging. Remot e Cont rol: Traffic caused by remote control applications, such as RDP, SSH, Telnet, VNC. Infrast ruct ure: Traffic caused by network services, such as DHCP, DNS, Ident, ICMP, SNMP. Net BIOS : Traffic caused by NetBIOS communication. Ot her Prot ocols: Traffic caused by various other protocols via UDP and TCP. For each traffic group, you can select how many channels will be used for each group, i.e. how detailed 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 Ot her. Yes: Count all traffic of this group and summarize it into one channel. Det ail: Count all traffic of this group and further divide it into different channels. The traffic will appear in several channels as shown in the Cont ent column. Note: Extensive use of this option can cause load problems on your probe system. We recommend setting specific, well-chosen filters for the data you really want to analyse.
Exclude Filter
824
08.10.2013
Chart Type
Inherited Settings
08.10.2013
825
Maintenance Window
Maintenance End At
Dependency Type
826
08.10.2013
Delay (Seconds)
08.10.2013
827
828
08.10.2013
Toplists
More
Paessler Website: Paessler sFlow Tester http://www.paessler.com/tools/sflowtester

Notifications
Others
133
section.
Related Topics
1872
1876
08.10.2013
829
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 79 sFlow (Custom) Sensor
6.8.79 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). The sensor accepts RAW data. This sensor type cannot be used in cluster mode. You can set it up on a local probe or remote probe only, not on a cluster probe. For a general introduction to the technology behind flow monitoring, please see Monit oring Bandwidt h via Flows 1820 section.
Limitations of This Sensor Type

There are some limitations that you want to consider before using this sensor type: Only sFlow version 5 datagrams are supported Only IPv4 flows are supported Only the "raw packet header" format is supported Only the "Flow sample" format is supported. "Extended flow" and "Counter" formats cannot be processed PRTG processes only samples where the source ID matches the ifIndex of the input interface (avoiding double counted traffic) and ascending sequence numbers. Due to internal limitations, only interface numbers up to 65535 are supported. Sample packets have to be of ethernet type "IP" (with optional VLAN tag) Sampled packets of type TCP and UDP are supported We recommend using sFlow tester for debugging (see More section below).

Add Sensor
830
08.10.2013
Sensor Settings
Tags
Priority
sFlow Specific Set t ings 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. Note: When configuring export, please make sure you select the appropriate sFlow version 5. Enter the IP address of the sending device you want to receive the sFlow from. Enter an IP address to receive data from a specific device only, or leave the field empty to receive data from any device on the specified port. 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.
Sender IP
Receive sFlow Packets on IP
08.10.2013
831
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 Defint ions for xFlow and Packet Sniffer Sensors 1876 section. All traffic for which no channel is defined will be accounted to the default channel named Ot her. Note: Extensive use of many filters can cause load problems on your probe system. We recommend defining specific, well-chosen filters for the data you really want to analyse.
Exclude Filter
Chart Type
832
08.10.2013
Inherited Settings
Schedules, Dependencies, and Maint enance Window Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings. Schedule Select a schedule from the list. Schedules can be used to monitor for a certain time span (days, hours) throughout the week. With the period list option it is also possible to pause monitoring for a specific time span. You can create new schedules and edit existing ones in the account settings 1678 . Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active. Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between:
Maintenance Window
08.10.2013
833
Schedules, Dependencies, and Maint enance Window Not set (monit or cont inuously ): No maintenance window will be set. Set up a one-t ime maint enance window: Pause monitoring within a maintenance window. Maintenance Begins At This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window. This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window. 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. Mast er object for parent : Make this sensor the master object for its parent device. The sensor will influence the behavior of the device it is created on: If the sensor is in a Down status, the device will be paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor will be paused if the parent group of its parent device is in a Down status, or if it is paused by another dependency. Note: Testing your dependencies is easy! Simply choose Simulat e Error St at us from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused. Dependency This field is only visible if the select object option is enabled above. Click on the reading-glass symbol and use the object selector 143 to choose an object on which the current sensor will be dependent on.
Maintenance End At
Dependency Type
834
08.10.2013
08.10.2013
835
Toplists
More
Paessler Website: Paessler sFlow Tester http://www.paessler.com/tools/sflowtester

Notifications
Others
133
section.
836
08.10.2013
Related Topics
1872
1876
08.10.2013
837
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 80 SFTP Secure File Transfer Protocol Sensor
6.8.80 SFTP Secure File Transfer Protocol Sensor

The sFTP Secure File Transfer Protocol sensor monitors FTP servers of a Linux/Unix system using SSH File Transfer Protocol (FTP over SSH). It tries to connect to a server and shows the response time. For this sensor type credentials for Linux (SSH/WBEM) systems must be defined for the device you want to use the sensor on. Note: Not all Linux/Unix and Mac OS distributions can be supported by this sensor type. For a general introduction to SSH monitoring, please see Monit oring via SSH
1816
section.
Add Sensor
Sensor Settings
Tags
Priority
838
08.10.2013
SSH Specific Connection Timeout (sec.) Define a timeout for the connection. This is the the time the sensor waits to establish a connection to the host. You should keep this value as low as possible. Define a timeout for the shell response. This is the time in seconds the sensor waits for the shell to return a response after it has sent its specific command (e.g. cat /proc/loadavg). Define which port this sensor will use for the SSH connection. Choose between: Inherit port number from parent device (default ): Use the port number as defined in the Credentials for Linux/Solaris/Mac OS (SSH/WBEM) Systems section of the device this sensor is created on. Ent er cust om port number: Do not use the port number from the parent device's settings, but define a different port number below. Use Port Number This field is only visible if the custom port number setting is enabled above. Enter the port number this sensor will use for the SSH connection. Please enter an integer value. Define what will be done with the result data received by the sensor. Choose between: Discard result : Do not store the result data. Writ e result t o disk (Filename: "Result of Sensor [ID].t xt ): Store the last result received from the query to the "Logs (Sensors)" directory (on the Master node, if in a cluster). File name: Result of Sensor [ID].txt. This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Shell Timeout (sec.)
SSH Port
Result Handling
Chart Type
08.10.2013
839
Sensor Display St ack channels on t op of each ot her: Stack channels on top of each other to create a multi-channel graph. This will generate an easy-to-read graph which visualizes the different components of your total traffic. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 settings). Show in and out t raffic as posit ive and negat ive area chart : Show channels for incoming and outgoing traffic as positive and negative area chart. This will visualize your traffic in a clear way. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 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
840
08.10.2013
Maintenance Window
Maintenance End At
Dependency Type
08.10.2013
841
Delay (Seconds)
842
08.10.2013

Notifications
Others
133
section.
08.10.2013
843
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 81 Share Disk Free Sensor
6.8.81 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
Sensor Settings
Tags
844
27.11.2012
Share Configurat ion 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.
Chart Type
27.11.2012
845
Inherited Settings
Maintenance Window
Maintenance End At
846
27.11.2012
Delay (Seconds)
27.11.2012
847
More

Notifications
848
27.11.2012
Others
133
section.
27.11.2012
849
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 82 SIP Options Ping Sensor
6.8.82 SIP Options Ping Sensor

The SIP Options Ping sensor monitors the connectivity for a Session Initiation Protocol (SIP) server using SIP options "Ping". It can be used to monitor voice-over-IP (VoIP) services. The sensor sends "auth" and "options" requests to the SIP server and shows the response time. It can alert in case of an error. Note: A SIP server might return a 480 Service temporarily unavailable error until at least one reachable SIP client is connected to the server. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Add Sensor
Sensor Settings
850
07.02.2013
Priority
SIP Specific Port Define the UDP port this sensor will connect to. Please enter an integer value. Enter the username of the SIP account this sensor will log into after a connection to the SIP server has been established. Please enter a string. Enter the password of the SIP account this sensor will log into after a connection to the SIP server has been established. Please enter a string. Enter the timeout for the connection to the SIP server. Please enter an integer value. In case the connection to the SIP server fails, the sensor can re-try to connect. Enter the maximum number of retries. After reaching the maximum count the sensor will show a red Down status. Please enter an integer value.
Username
Password
Timeout (Seconds)
Retry Count
Chart Type
07.02.2013
851
Inherited Settings
852
07.02.2013
Maintenance End At
Dependency Type
07.02.2013
853
854
07.02.2013

Notifications
Others
133
section.
07.02.2013
855
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 83 SMTP Sensor
6.8.83 SM TP 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
Sensor Settings
Tags
Priority
SMTP specific Timeout (sec) Enter a timeout in seconds for the SMTP connect. If the reply takes longer than this value the request is aborted and an error message is triggered.
856
27.11.2012
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. 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
Aut hent icat ion 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. This field is only visible if SMTP authentication is enabled above. Enter a password for SMTP authentication. Please enter a string.
Password
27.11.2012
857
Monit oring 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 change to a Down status. 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. Specify which address the sent emails will contain in the from field. Please enter a valid email address. Specify to which address the emails will be sent to. Please enter a valid email address. Specify which subject will be used in the sent emails. Please enter a string or leave the field empty. Specify which body will be used in the sent emails. Please enter a string or leave the field empty.
From
To
Topic
Content
Chart Type
858
27.11.2012
Inherited Settings
Maintenance Window
27.11.2012
859
Maintenance End At
Dependency Type
Delay (Seconds)
860
27.11.2012

Notifications
Others
133
section.
27.11.2012
861
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 84 SMTP&IMAP Round Trip Sensor
6.8.84 SM TP&IM AP 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 Monit oring Email Round Trip 1829 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. We recommend adding this sensor on an SMTP server device only, as the sensor's settings are optimized for this scenario.
Sensor Settings
Tags
Priority
862
07.02.2013
Email Set t ings From Specify which address the sent emails will contain in the from field. Please enter a valid email address. Specify to which address the emails will be sent to. Please enter a valid email address. 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.
To
Helo Ident
07.02.2013
863
St ep 1: Send email t o parent device using SMTP In this step, you configure how emails will be sent. As SMTP server, the sensor uses the IPAddress/DNS Name property's value of the device it is added on. Port Enter the number of the port that will be used to send an email via SMTP. Please enter an integer value. For non-secure connections usually port 25 is used; usually port 465 or 587 for SSL connections. The actual setting depends on the server you are connecting to. Please enter an integer value. We recommend using the default value. If you do not get a connection, please try another port number. 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. 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 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. This field is only visible if SMTP authentication is enabled above. Enter a password for SMTP authentication. Please enter a string. The subject part of the round trip email is created automatically by PRTG. It consists of the string "PRTG Roundtrip Mail:" followed by a unique GUID to correctly identify the email in the IMAP mailbox (e.g. PRTG Roundtrip Mail: {5E858D9C-AC70-466A-9B2A07.02.2013 55630165D276}). Use this field to place your custom text before the automatically created text.
Timeout for SMTP Connection (sec)
Password
Additional Text for Email Subject 864
St ep 2: Check an IMAP mailbox unt il email arrives In this step, you configure how the sent emails will be received. IP-Address/DNS Name Mailbox Specify the IMAP server. Enter a valid IP address or DNS name. Specify the IMAP Mailbox (resp. "IMAP folder") you want to check. Please enter the IMAP mailbox/folder name. Specify the port that will be used for the IMAP connection. For nonsecure 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. 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. 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. 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. Select the kind of authentication for the IMAP connection. Choose between: Username and Password (simple) Simple Aut hent icat ion and Securit y Lay er (SASL) Username Password Enter a username for IMAP authentication. Please enter a string. Enter a username for IMAP authentication. Please enter a string.
Port
Connection Interval (sec)
Maximum Trip Time (sec)
IMAP Authentication Type
07.02.2013
865
Chart Type
Inherited Settings
866
07.02.2013
Maintenance Window
Maintenance End At
Dependency Type
07.02.2013
867
Delay (Seconds)
868
07.02.2013

Notifications
Others
133
section.
07.02.2013
869
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 85 SMTP&POP3 Round Trip Sensor
6.8.85 SM TP&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 Monit oring Email Round Trip 1829 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. We recommend adding this sensor on an SMTP server device only, as the sensor's settings are optimized for this scenario.
Sensor Settings
Tags
Priority
870
07.02.2013
Email Set t ings From Specify which address the sent emails will contain in the from field. Please enter a valid email address. Specify to which address the emails will be sent to. Please enter a valid email address. 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.
To
Helo Ident
St ep 1: Send email t o parent device using SMTP In this step, you configure how emails will be sent. As SMTP server, the sensor uses the IPAddress/DNS Name property's value of the device it is added on. Port Enter the number of the port that will be used to send an email via SMTP. Please enter an integer value. For non-secure connections usually port 25 is used; usually port 465 or 587 for SSL connections. The actual setting depends on the server you are connecting to. Please enter an integer value. We recommend using the default value. If you do not get a connection, please try another port number. 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. 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.
Timeout for SMTP Connection (sec)
SSL-Method
07.02.2013
871
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. This field is only visible if SMTP authentication is enabled above. Enter a password for SMTP authentication. Please enter a string. The subject part of the round trip email is created automatically by PRTG. It consists of the string "PRTG Roundtrip Mail:" followed by a unique GUID to correctly identify the email in the POP3 mailbox (e.g. PRTG Roundtrip Mail: {5E858D9C-AC70-466A-9B2A55630165D276}). Use this field to place your custom text before the automatically created text.
Password
Additional Text for Email Subject
872
07.02.2013
St ep 2: Check a POP3 mailbox unt il email arrives In this step, you configure how the sent emails will be received. IP-Address/DNS Name Port Specify the POP3 server. Enter a valid IP address or DNS name. 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. 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. 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. 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. Select the kind of authentication for the POP3 connection. Choose between: Wit hout Login: Monitor the connection to the POP3 server only. Username and Password: Log into the POP3 server with user name and password (simple login, non-secure). 128-bit MD5 hash value (APOP): Send the password in an encrypted form using APOP. This option must be supported by the POP3 server you're connecting to. Username This field is only visible if an option with login is selected above. Enter a username for POP3 authentication. Please enter a string. This field is only visible if an option with login is selected above. Enter a username for POP3 authentication. Please enter a string.
Connection Interval (sec)
Maximum Trip Time (sec)
POP3 Authentication Type
Password
07.02.2013
873
Inherited Settings
Maintenance Window
Maintenance End At
874
07.02.2013
Delay (Seconds)
07.02.2013
875

Notifications
Others
133
section.
876
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 86 SNMP APC Hardware Sensor
6.8.86 SNM P 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 Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. For devices with multiple performance counters multiple sensors are created at once in the Add Sensor dialog. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
APC UPS Specific Library OIDs Select the performance counters you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
07.02.2013
877
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. Define the unit of the numerical data that will be received at the given OID. Please enter a string. If you want to multiply the received data with a certain value, enter the quotient here. Please enter an integer or float value. If you want to divide the received data by a certain value, enter the divisor here. Please enter an integer or float value. 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' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Unit String
Multiplication
Division
If Value Changes
878
07.02.2013
Chart Type
Inherited Settings
07.02.2013
879
Maintenance Window
Maintenance End At
Dependency Type
880
07.02.2013
Delay (Seconds)
07.02.2013
881

Notifications
Others
133
section.
882
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 87 SNMP Cisco ADSL Sensor
6.8.87 SNM P Cisco ADSL Sensor

The SNMP Cisco ADSL sensor monitors Asymmetric Digital Subscriber Line (ADSL) statistics of a Cisco router using Simple Network Management Protocol (SNMP). It shows the speed of downlink and uplink, remote and local attenuation, remote and local SNR (signal-to-noise ratio), and remote and local power output. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
Sensor Settings
Tags
Priority
19.12.2012
883
Chart Type
Inherited Settings
884
19.12.2012
Maintenance Window
Maintenance End At
Dependency Type
19.12.2012
885
Delay (Seconds)
886
19.12.2012

Notifications
Others
133
section.
19.12.2012
887
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 88 SNMP Cisco ASA VPN Connections Sensor
6.8.88 SNM P Cisco ASA VPN Connections Sensor

The SNMP Cisco ASA VPN Connections sensor monitors the VPN connections on a Cisco Adaptive Security Appliance using Simple Network Management Protocol (SNMP). It shows the active sessions of the connection types email, IPsec, L2L, LB, SVC, WebVPN, as well as the total number of sessions, active users, and groups with active users. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
Sensor Settings
Tags
Priority
888
27.11.2012
Chart Type
Inherited Settings
27.11.2012
889
Maintenance Window
Maintenance End At
Dependency Type
890
27.11.2012
Delay (Seconds)
27.11.2012
891

Notifications
Others
133
section.
892
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 89 SNMP Cisco ASA VPN Traffic Sensor
6.8.89 SNM P Cisco ASA VPN Traffic Sensor

The SNMP Cisco ASA VPN Traffic sensor monitors the traffic of an Internet Protocol Security (IPsec) Virtual Private Network (VPN) connection on a Cisco Adaptive Security Appliance using Simple Network Management Protocol (SNMP). It shows incoming and outgoing traffic. This sensor type is indented to monitor permanent connections. It will show an error if a connection is interrupted. It can monitor IPsec connections only! For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. If you select more than one connections, multiple sensors are created at once in the Add Sensor dialog. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
ASA VPN Specific Connections Select the IPsec VPN connection you want to add a sensor for. You see a list of all active IPsec VPN connections available on the target ASA, listed with remote IP, user name, and the kind of connection. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. Note: This sensor type can only monitor VPN connections based on IPsec. This means, for example, that connections using "Cisco AnyConnect" will not be listed here.
Sensor Settings
07.02.2013
893
Tags
Priority
ASA VPN Specific Remote IP The IP address of the connection this sensor monitors. 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. Note: This sensor type can only monitor VPN connections based on IPsec.
Chart Type
894
07.02.2013
Inherited Settings
Maintenance Window
07.02.2013
895
Maintenance End At
Dependency Type
Delay (Seconds)
896
07.02.2013

Notifications
Others
133
section.
07.02.2013
897
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 90 SNMP Cisco CBQoS Sensor
6.8.90 SNM P Cisco CBQoS Sensor

The SNMP Cisco CBQoS sensor monitors network parameters using Cisco's Class Based Quality of Service (CBQoS) via Simple Network Management Protocol (SNMP). It supports the classes Class Map, Match Statement, and Queueing. The sensor shows current and maximum queue depth, pre policy packets, pre and post policy size, drop packets and size, drop packets without buffer, as well as fragment packets and size. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor quality-of-service vie compatible devices, PRTG will create one sensor for each CBQoS entry you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Class Based QoS Specific CBQoS Entries Select the measurements you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
898
19.07.2013
Priority
Class Based QoS Specific Interface Description Bitmask ObjectID ConfigID Shows further information about the parameter this sensor is monitoring. 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.
Inherited Settings
19.07.2013
899
Maintenance Window
Maintenance End At
Dependency Type
900
19.07.2013
Delay (Seconds)
19.07.2013
901

Notifications
Others
133
section.
902
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 91 SNMP Cisco System Health Sensor
6.8.91 SNM P Cisco Sy stem Health Sensor

The SNMP Cisco System Health sensor monitors the system health of a Cisco device via Simple Network Management Protocol (SNMP). It can show the percentage CPU load, available memory in absolute and percentage values, the status of power supplies, temperatures (in Celsius), the current temperature states, and many more, depending on the available components of your device. This sensor type has predefined limits for several metrics. These limits can be changed individually in the channel settings. For detailed information about channel limits please refer to the section Sensor Channels Set t ings 1566 . This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor the system health of a Cisco device, PRTG will create one sensor for each measurement you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Cisco Sy st em Healt h Specific Measurement Select the measurements you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
19.07.2013
903
Tags
Priority
Cisco Sy st em Healt h Specific Measurement Shows the ID of the measurement that this sensor is monitoring. 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.
Chart Type
904
19.07.2013
Inherited Settings
By default, all following settings are inherited from objects higher in the hierarchy and should be changed there, if necessary. Often, best practice is to change them centrally in the Root 213 group's settings. To change a setting for this object, disable inheritance by clicking on the check mark symbol in front of the respective setting name. You will then see the options described below. Schedules, Dependencies, and Maint enance Window Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings. Schedule Select a schedule from the list. Schedules can be used to monitor for a certain time span (days, hours) throughout the week. With the period list option it is also possible to pause monitoring for a specific time span. You can create new schedules and edit existing ones in the account settings 1678 . Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active. Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between: Not set (monit or cont inuously ): No maintenance window will be set. Set up a one-t ime maint enance window: Pause monitoring within a maintenance window.
Maintenance Window
19.07.2013
905
Maintenance End At
Dependency Type
Delay (Seconds)
906
19.07.2013
19.07.2013
907

Notifications
Others
133
section.
908
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 92 SNMP CPU Load Sensor
6.8.92 SNM P CPU Load Sensor

The SNMP CPU Load sensor monitors the system load using Simple Network Management Protocol (SNMP). It can show the load of several CPUs in percent. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
Sensor Settings
Tags
Priority
07.02.2013
909
Inherited Settings
910
07.02.2013
Maintenance End At
Dependency Type
07.02.2013
911
912
07.02.2013

Notifications
Others
133
section.
07.02.2013
913
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 93 SNMP Custom Sensor
6.8.93 SNM P Custom Sensor

The 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 Monit oring via SNMP 1809 section.
Add Sensor
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 1566 . Select how the results at the given OID will be handled. Choose between: Gauge (unsigned Int eger): For integer values, such as 10 or 120. Gauge (signed int eger): For integer values, such as -12 or 120. Gauge (float ): For float values, such as -5.80 or 8.23. Delt a (Count er): For counter values. PRTG will calculate the difference between the last and the current value. Once a sensor is created this value cannot be changed. It is shown for reference purposes only. If you need to change this, please add the sensor anew.
Value Type
Sensor Settings
914
18.02.2013
Tags
Priority
18.02.2013
915
OID values OID value Enter the OID of the SNMP object you want to receive numerical data from. Note: Most OIDs begin with 1.3.6.1. However, entering OIDs starting with 1.0, or 1.1, or 1.2 is also allowed. If you want to disable the validation of your entry entirely, add the string norfccheck: at the beginning of your OID, for example, norfccheck:2.0.0.0.1. Define the unit of the numerical data that will be received at the given OID. Please enter a string. 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. If you want to multiply the received data with a certain value, enter the quotient here. Please enter an integer or float value. If you want to divide the received data by a certain value, enter the divisor here. Please enter an integer or float value. Define what shall be done in case the value of this sensor changes. You can choose between: Ignore changes (default ): No action will be taken on change. Trigger 'On Change' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Unit String
Value Type
Multiplication
Division
If value changes
Chart Type
916
18.02.2013
Inherited Settings
18.02.2013
917
Maintenance End At
Dependency Type
918
18.02.2013
18.02.2013
919
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

Notifications
Others
133
section.
920
18.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 94 SNMP Custom String Sensor
6.8.94 SNM P Custom String Sensor

The SNMP Custom String sensor monitors a string returned by a specific OID using Simple Network Management Protocol (SNMP). It can check for keywords. If you want to use limits for the sensor channel value, you can also extract a numeric value contained in the string. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
Sensor Settings
Tags
Priority
08.10.2013
921
OID Values OID Value Enter the OID of the SNMP object you want to receive a string from. Note: Most OIDs begin with 1.3.6.1. However, entering OIDs starting with 1.0, or 1.1, or 1.2 is also allowed. If you want to disable the validation of your entry entirely, add the string norfccheck: at the beginning of your OID, for example, norfccheck:2.0.0.0.1. 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. Define what shall be done in case the value of this sensor changes. You can choose between: Ignore changes (default ): No action will be taken on change. Trigger 'On Change' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Maximum Length of String
If Value Changes
922
08.10.2013
Key word Search Response Must Include Define which string must be part of the data that is received from (Error State) the SNMP object at the given OID. You can either enter plain text or a Regular Expression 1886 . If the data does not include the search pattern, the sensor will be set to an error state. Please enter a string or leave the field empty. For Keyword Search Use Define 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 1886 . Response Must Not Include (Error State) Define which string must not be part of the data that is received form the SNMP object at the given OID. You can either enter plain text or a Regular Expression 1886 . If the data does include the search pattern, the sensor will be set to an error state. Please enter a string or leave the field empty. 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 1886 . Response Must Include Define which string must be part of the data that is received from (Warning State) the SNMP object at the given OID. You can either enter plain text or a Regular Expression 1886 . If the data does not include the search pattern, the sensor will be set to a warning state. Please enter a string or leave the field empty. For Keyword Search Use 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.
08.10.2013
Regular Expression: Treat the search pattern as a Regular Expression 1886 . Response Must Not Define which string must not be part of the data that is received
923
Ext ended Processing Extract Number Using Regular Expression Define if you want to filter out a numeric value from the string received from the SNMP object at the given OID. You can convert this into a float value in order to use it with channel limits (see Sensor Channels Set t ings 1566 ). No ext ract ion: Do not extract a float value. Use the result as a string value. Ext ract a numeric value using a regular expression: Use a regular expression to identify a numeric value in the string and convert it to a float value. Define below. See also the example below. Regular Expression
927
This setting is only visible if number extraction is enabled above. Enter a Regular Expression 1886 to identify the numeric value you want to extract from the string returned by the SNMP object at the given OID. You can use capturing groups here. Make sure the expression returns numbers only (including decimal and thousands separators). The result will be further refined by the settings below. This setting is only visible if number extraction is enabled above. If your regular expression uses capturing groups, please specify which one will be used to capture the number. Please enter an integer value or leave the field empty. This setting is only visible if number extraction is enabled above. Define which character is used as decimal separator for the number extracted above. Please enter a string or leave the field empty. This setting is only visible if number extraction is enabled above. Define which character is used as thousands separator for the number extracted above. Please enter a string or leave the field empty.
Index of Capturing Group
Decimal Separator
Thousands Separator
Chart Type
924
08.10.2013
Inherited Settings
08.10.2013
925
Maintenance End At
Dependency Type
926
08.10.2013
Example: Number Extraction with Regular Expression

If you want to extract a number in the response string using a regular expression, please note that the index for captures in this sensor is based on 1 (not on 0). Furthermore, capturing groups are not created automatically. The example below will illustrate this issue. Consider the following string as returned by a request for CPU usage:
08.10.2013
927
5 Sec (3.49%), 1 Min (3.555%), 5 Min (3.90%)
Assuming you would like to filter for the number 3.555, i.e., the percentage in the second parentheses. Then enter the following regex in the Regular Expression field:
(\d+\.\d+).*(\d+\.\d+).*(\d+\.\d+)
As Index of Capt uring Group enter 3. This will extract the desired number 3.555. The index has to be 3 in this case because the capturing groups here are the following: Group 1 contains "3.49%), 1 Min (3.555), 5 Min (3.90" Group 2 contains "3.49" Group 3 contains "3.555" Group 4 contains "3.90" Please keep in mind this note about index and capturing groups when using number extraction.
More
Knowledge Base: How do I find out what OID I need to use for a custom sensor? http://www.paessler.com/knowledgebase/en/topic/903

Notifications
Others
133
section.
928
08.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 95 SNMP Dell Hardware Sensor
6.8.95 SNM P 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 Monit oring via SNMP 1809 section.
Add Sensor
Dell Hardware Specific Library OIDs Select the performance counters you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
07.02.2013
929
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. Define the unit of the numerical data that will be received at the given OID. Please enter a string. If you want to multiply the received data with a certain value, enter the quotient here. Please enter an integer or float value. If you want to divide the received data by a certain value, enter the divisor here. Please enter an integer or float value. 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' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Unit String
Multiplication
Division
If Value Changes
930
07.02.2013
Chart Type
Inherited Settings
07.02.2013
931
Maintenance Window
Maintenance End At
Dependency Type
932
07.02.2013
Delay (Seconds)
07.02.2013
933

Notifications
Others
133
section.
934
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 96 SNMP Dell PowerEdge Physical Disk Sensor
6.8.96 SNM P Dell PowerEdge Phy sical Disk Sensor

The SNMP Dell PowerEdge Physical Disk sensor monitors a physical disk in a Dell PowerEdge server using Simple Network Management Protocol (SNMP). It can show the disk status, the roll up status, the component status, as well as if there is currently a warning regarding the SelfMonitoring, Analysis and Reporting Technology (S.M.A.R.T.) status. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Requirement: Dell OpenManage

This sensor needs the Dell OpenManage tool to be installed on the device in order to monitor PowerEdge servers which are older than 12th generation. Please make sure that you enable SNMP in the OpenManage Server Administrator. For details, please see More below.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor physical disks in a Dell PowerEdge server, PRTG will create one sensor for each disk. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Dell PowerEdge Phy sical Disk Set t ings Disk Select the disks you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
07.02.2013
935
Tags
Priority
Dell PowerEdge Phy sical Disk Set t ings Disk Shows the name of the disk that this sensor is monitoring. 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.
Chart Type
936
07.02.2013
Maintenance Window
Maintenance End At
07.02.2013
937
Delay (Seconds)
938
07.02.2013
More
Knowledge Base: What do I need to monitor Dell servers?
07.02.2013
939

Notifications
Others
133
section.
940
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 97 SNMP Dell PowerEdge System Health Sensor
6.8.97 SNM P Dell PowerEdge Sy stem Health Sensor

The SNMP Dell PowerEdge System Health sensor monitors the system health of a Dell PowerEdge server using Simple Network Management Protocol (SNMP). It can show the global system status, the power supply status, the temperature status, the cooling device status, the memory device status, the voltage status, and many more, depending on the available components of your device. This sensor type has predefined limits for several metrics. These limits can be changed individually in the channel settings. For detailed information about channel limits please refer to the section Sensor Channels Set t ings 1566 . This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Requirement: Dell OpenManage

This sensor needs the Dell OpenManage tool to be installed on the device in order to monitor PowerEdge servers which are older than 12th generation. Please make sure that you enable SNMP in the OpenManage Server Administrator. For details, please see More below.
Add Sensor
Sensor Settings
07.02.2013
941
Priority
Chart Type
942
07.02.2013
Maintenance Window
Maintenance End At
Dependency Type
07.02.2013
943
Delay (Seconds)
944
07.02.2013
More
Knowledge Base: What do I need to monitor Dell servers?
07.02.2013
945

Notifications
Others
133
section.
946
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 98 SNMP Disk Free Sensor
6.8.98 SNM P Disk Free Sensor

The SNMP Disk Free sensor monitors the free disk space on a logical disk via Simple Network Management Protocol (SNMP). It can show free space in percent and in total, as well as the total space. Note: This sensor uses more generic Object Identifier (OID) values compared to the SNMP Linux Disk Free Sensor 1031 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor memory usage, PRTG will create one sensor for each memory type you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Disk Free Set t ings Disk Select one or more disks you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
07.02.2013
947
Priority
Disk Free Set t ings Disk Shows the name of the disk that this sensor is monitoring. 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.
Chart Type
948
07.02.2013
Inherited Settings
Maintenance Window
Maintenance End At
07.02.2013
949
Delay (Seconds)
950
07.02.2013
07.02.2013
951

Notifications
Others
133
section.
952
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 99 SNMP GSA System Health Sensor
6.8.99 SNM P GSA Sy stem Health Sensor

The SNMP GSA System Health sensor monitors the system health of a Google Search Appliance (GSA) via Simple Network Management Protocol (SNMP). It can show the number of queries per minute, the number of processed documents, the number of indexed documents, the number of processed bytes, the activity status of crawling, the crawling rate per second, as well as the health status of disk, temperature, and machine. Note: The location you provide in the GSA's SNMP configuration section will be shown in PRTG's GeoMaps 1603 . In order to use SNMP v3 for monitoring, you need to add an SNMP v3 user in the GSA's SNMP configuration. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
Sensor Settings
Tags
Priority
13.06.2013
953
Chart Type
Inherited Settings
954
13.06.2013
Maintenance Window
Maintenance End At
Dependency Type
13.06.2013
955
Delay (Seconds)
956
13.06.2013

Notifications
Others
133
section.
13.06.2013
957
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 100 SNMP Hardware Status Sensor
6.8.100 SNM P Hardware Status Sensor

The SNMP Hardware Status sensor monitors the status of a hardware component of a server via Simple Network Management Protocol (SNMP). It shows the current status of the component, as well as the number of errors per time period. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor hardware components of a server, PRTG will create one sensor for each component you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Hardware Specific Hardware Component Select the hardware components you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
958
13.06.2013
Priority
Hardware Specific Hardware Component Product ID Description Type Shows further information about the hardware component. 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.
Chart Type
13.06.2013
959
Inherited Settings
Maintenance Window
960
13.06.2013
Maintenance End At
Dependency Type
Delay (Seconds)
13.06.2013
961

Notifications
Others
133
section.
962
13.06.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 101 SNMP HP LaserJet Hardware Sensor
6.8.101 SNM P HP LaserJet Hardware Sensor

The SNMP HP LaserJet Hardware sensor monitors performance counters on a HP LaserJet hardware device using Simple Network Management Protocol (SNMP). For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
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/St at us Paper/St at us Jam/St at us 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
27.11.2012
963
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. 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' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
If Value Changes
Chart Type
964
27.11.2012
Inherited Settings
27.11.2012
965
Maintenance End At
Dependency Type
966
27.11.2012

27.11.2012
967
Notifications
Others
133
section.
968
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 102 SNMP HP ProLiant Logical Disk Sensor
6.8.102 SNM P HP ProLiant Logical Disk Sensor

The SNMP HP ProLiant Logical Disk sensor monitors a logical disk in an HP server via Simple Network Management Protocol (SNMP). It can show disk status and completion. Completion is only important when the disk status is "Reconstructing" or "Expanding" and illustrates the progress of this task. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Requirement: HP System Management Tools

This sensor needs a specific HP system management tool to be installed on the target device, so it reports data via SNMP: HP Insight Management Agents for Windows Server 2003/2008. In order to receive SNMP data from RAID controllers you will additionally need HP Insight Management WBEM Providers. For more details and download links please refer to the subsection More below.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor logical disks in a HP server, PRTG will create one sensor for each disk you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
HP ProLiant Logical Disk Set t ings Disk Select the disks you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
07.02.2013
969
Tags
Priority
HP ProLiant Logical Disk Set t ings Disk Shows the name of the disk that this sensor is monitoring. 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.
Chart Type
970
07.02.2013
Inherited Settings
Maintenance Window
07.02.2013
971
Maintenance End At
Dependency Type
Delay (Seconds)
972
07.02.2013
More
Knowledge Base: Monitor HP ProLiant via SNMP
07.02.2013
973

Notifications
Others
133
section.
974
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 103 SNMP HP ProLiant Memory Controller Sensor
6.8.103 SNM P HP ProLiant M emory Controller Sensor

The SNMP HP ProLiant Memory Controller sensor monitors a memory controller in an HP server via Simple Network Management Protocol (SNMP). It checks which memory modules are available during the meta scan and monitors these. Note: If modules are inserted at a later point, the sensor has to be added again. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For supported lookup values of this specific sensor, please see subsection More
979
below.
For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.

Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor memory controllers in a HP server, PRTG will create one sensor for each controller you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
HP ProLiant Memory Cont roller Set t ings Controller Select the controllers you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
07.02.2013
975
Tags
Priority
HP ProLiant Memory Cont roller Set t ings Controller Shows the name of the controller that this sensor is monitoring. 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.
Chart Type
976
07.02.2013
Inherited Settings
Maintenance Window
07.02.2013
977
Maintenance End At
Dependency Type
Delay (Seconds)
978
07.02.2013
More
07.02.2013
979
http://www.paessler.com/knowledgebase/en/topic/33133 Knowledge Base: Which lookup values are supported by the SNMP HP ProLiant Memory Controller Sensor? http://www.paessler.com/knowledgebase/en/topic/44803

Notifications
Others
133
section.
980
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 104 SNMP HP ProLiant Network Interface Sensor
6.8.104 SNM P HP ProLiant Network Interface Sensor

The SNMP HP ProLiant Network Interface sensor monitors a network interface in an HP server via Simple Network Management Protocol (SNMP). It can show traffic in and out, the number of transmitted and received good frames, the number of transmitted and received bad frames, alignment and FCS (Frame Check Sequence) errors, late and excessive collisions, carrier sense errors, and when the frames are too long. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.

Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor network interfaces in a HP server, PRTG will create one sensor for each interface. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
HP ProLiant Net work Int erface Set t ings Network Interface Select the interfaces you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Note: In the HP ProLiant Net work Int erface Set t ings section, the St at us of each available network interface is shown. If this status is Link Failure, it is still possible to add a sensor for the respective interface. Though, most likely the sensor for this interface will not work correctly. The error message in this case will be No Such Name (SNMP error # 2).
Sensor Settings
12.02.2013
981
Tags
Priority
HP ProLiant Net work Int erface Set t ings Network Interface Shows the name of the interface that this sensor is monitoring. 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.
Chart Type
982
12.02.2013
Sensor Display Show in and out t raffic as posit ive and negat ive area chart : Show channels for incoming and outgoing traffic as positive and negative area chart. This will visualize your traffic in a clear way. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 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
12.02.2013
983
Maintenance End At
Dependency Type
984
12.02.2013
12.02.2013
985
More
Knowledge Base: Monitor HP ProLiant via SNMP http://www.paessler.com/knowledgebase/en/topic/33133

Notifications
Others
133
section.
986
12.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 105 SNMP HP ProLiant Physical Disk Sensor
6.8.105 SNM P HP ProLiant Phy sical Disk Sensor

The SNMP HP ProLiant Physical Disk sensor monitors a physical disk in an HP server via Simple Network Management Protocol (SNMP). It can show read and written sectors, hard and corrected read errors, hard and corrected write errors, the disk status, the drive condition, the Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) status, and if the threshold is passed. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.

Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor physical disks in a HP server, PRTG will create one sensor for each disk. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
HP ProLiant Phy sical Disk Set t ings Disk Select the disks you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
07.02.2013
987
Tags
Priority
HP ProLiant Phy sical Disk Set t ings Disk Shows the name of the disk that this sensor is monitoring. 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.
Chart Type
988
07.02.2013
Inherited Settings
07.02.2013
989
Maintenance End At
Dependency Type
990
07.02.2013
07.02.2013
991
More
Knowledge Base: Monitor HP ProLiant via SNMP http://www.paessler.com/knowledgebase/en/topic/33133

Notifications
Others
133
section.
992
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 106 SNMP HP ProLiant System Health Sensor
6.8.106 SNM P HP ProLiant Sy stem Health Sensor

The SNMP HP ProLiant System Health sensor monitors the system health of an HP ProLiant server via Simple Network Management Protocol (SNMP). It can show the overall status, the thermal status, the system fan status, the CPU fan status, the number of broken and running fans, as well as the number of broken and running fans that are fault tolerant, and status and condition of the power supply. Furthermore it can show several temperatures for various components of an HP ProLiant serverfor example: memory, power supply, CPU, system, and storage. It is also possible to display the power consumption and disk controller status. These channels are created at runtime, depending on the available measurement components. The SNMP HP ProLiant System Health sensor has predefined limits for temperatures and broken frames. These limits can be changed individually in the channel settings. For detailed information about channel limits please refer to the subsection Channels 998 below. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.

Add Sensor
Sensor Settings
19.07.2013
993
Tags
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. Note: You can set another primary channel later by clicking on the pin symbol of a channel in the sensor's overview tab. Define how different channels will be shown for this sensor. Show channels independent ly (default ): Show an own graph for each channel. St ack channels on t op of each ot her: Stack channels on top of each other to create a multi-channel graph. This will generate an easy-to-read graph which visualizes the different components of your total traffic. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 settings). Show in and out t raffic as posit ive and negat ive area chart : Show channels for incoming and outgoing traffic as positive and negative area chart. This will visualize your traffic in a clear way. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 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.
Chart Type
994
19.07.2013
Inherited Settings
Maintenance Window
Maintenance End At
19.07.2013
995
Delay (Seconds)
996
19.07.2013
More
19.07.2013
997

Notifications
Others
133
section.
998
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 107 SNMP IBM System X Logical Disk Sensor
6.8.107 SNM P IBM Sy stem X Logical Disk Sensor

The SNMP IBM System X Logical Disk sensor monitors a logical disk in an IBM server via Simple Network Management Protocol (SNMP). It shows the status of a logical disk. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Requirement: IBM Systems Director Platform Agent

This sensor type needs the IBM Systems Director Platform Agent to be installed on the target IBM device in order to monitor it through SNMP. For more information, please see section More below.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor the logical disks of an IBM device, PRTG will create one sensor for each disk you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
IBM Sy st em X Logical Disk Set t ings Disk Select the logical disks you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
23.10.2013
999
Tags
Priority
IBM Sy st em X Logical Disk Set t ings Disk Shows the ID of the logical 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.
Chart Type
1000
23.10.2013
Inherited Settings
Maintenance Window
23.10.2013
1001
Maintenance End At
Dependency Type
Delay (Seconds)
1002
23.10.2013
More
Knowledge Base: What are the requirements to monitor IBM System x?
23.10.2013
1003

Notifications
Others
133
section.
1004
23.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 108 SNMP IBM System X Physical Disk Sensor
6.8.108 SNM P IBM Sy stem X Phy sical Disk Sensor

The SNMP IBM System X Physical Disk sensor monitors a physical disk in an IBM server via Simple Network Management Protocol (SNMP). It shows the status of a physical disk. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.

Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor the physical disks of an IBM device, PRTG will create one sensor for each disk you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
IBM Sy st em X Phy sical Disk Set t ings Disk Select the physical disks you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
23.10.2013
1005
Tags
Priority
IBM Sy st em X Phy sical Disk Set t ings Disk Shows the ID of the physical 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.
Chart Type
1006
23.10.2013
Inherited Settings
Maintenance Window
23.10.2013
1007
Maintenance End At
Dependency Type
Delay (Seconds)
1008
23.10.2013
More
23.10.2013
1009

Notifications
Others
133
section.
1010
23.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 109 SNMP IBM System X Physical Memory Sensor
6.8.109 SNM P IBM Sy stem X Phy sical M emory Sensor

The SNMP IBM System X Physical Memory sensor monitors the memory modules in an IBM server via Simple Network Management Protocol (SNMP). It shows the condition of a memory module, as well as its power status. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.

Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor the memory modules of an IBM device, PRTG will create one sensor for each module you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
IBM Sy st em X Phy sical Memory Set t ings Module Select the memory modules you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
23.10.2013
1011
Tags
Priority
IBM Sy st em X Phy sical Memory Set t ings Name Caption Serial Number Size Shows further information about the module. 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.
Chart Type
1012
23.10.2013
Inherited Settings
Maintenance Window
23.10.2013
1013
Maintenance End At
Dependency Type
Delay (Seconds)
1014
23.10.2013
More
23.10.2013
1015

Notifications
Others
133
section.
1016
23.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 110 SNMP IBM System X System Health Sensor
6.8.110 SNM P IBM Sy stem X Sy stem Health Sensor

The SNMP IBM System X System Health sensor monitors the system health of an IBM device via Simple Network Management Protocol (SNMP). It can show revolutions per minute of fans, temperatures of ambient and CPUs, voltage, status of power supplies, and many more, depending on the available measurement components. This sensor type has predefined limits for several metrics. These limits can be changed individually in the channel settings. For detailed information about channel limits please refer to the section Sensor Channels Set t ings 1566 . This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.

This sensor type needs the IBM Systems Director Platform Agent to be installed on the target IBM device in order to monitor it through SNMP. For more information, please see section More below. Note: The SNMP IBM System X System Health sensor can also run directly on an Integrated Management Module (IMM) network port.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor the system health of an IBM device, PRTG will create one sensor for each measurement you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
IBM Sy st em X Sy st em Healt h Specific Measurement Select the measurements you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
23.10.2013
1017
Sensor Settings
Tags
Priority
IBM Sy st em X Sy st em Healt h Specific Source Shows the source of the measurement. 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. Shows the ID of the measurement that this sensor is monitoring. 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.
Measurement
Chart Type
1018
23.10.2013
Inherited Settings
23.10.2013
1019
Maintenance End At
Dependency Type
1020
23.10.2013
23.10.2013
1021
More
Knowledge Base: What are the requirements to monitor IBM System x? http://www.paessler.com/knowledgebase/en/topic/59393

Notifications
Others
133
section.
1022
23.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 111 SNMP Library Sensor
6.8.111 SNM P Library Sensor

The SNMP Library sensor monitors a device using Simple Network Management Protocol (SNMP) in combination with a compiled Management Information Base (MIB) library file. This provides extended monitoring beyond the standard SNMP sensors of PRTG. 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 convenient as possible, PRTG is delivered with pre-compiled oidlib library files that already contain the Object Identifier (OID) of SNMP counters for the most common devices in a network. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
Manually add 209 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 directoryboth the ones delivered with PRTG and your own files. For details about directory paths, please see section Dat a St orage 1912 .
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 ret ry button and try with another file. If counters were found for your device, you will see the sensor's settings.
03.05.2013
1023
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-int erfaces.oidlib Can be used to monitor Cisco specific parameters. cisco-queue.oidlib Can be used to monitor Cisco specific parameters. Dell St orage Management .oidlib Can be used to monitor Dell storage devices. Possible parameters include disk arrays, battery and power supply, fan and temperature, virtual disk, etc. Dell Sy st ems Management Inst rument at ion.oidlib Can be used to monitor the hardware of Dell systems. Possible parameters include ACPower and battery, alerts, base board, Bios, BMC, chassis, COO, cooling, event log, firmware, IDE, keyboard, memory, port, network, processor, SCSI, system, temperature, USB, UUID, etc. Linux SNMP (AX BGP DisMan Et herLike Host ).oidlib Can be used to monitor different aspects of Linux systems. Note: This file can find a very large number of possible interfaces. It may take a few seconds until the selection table is shown. Linux SNMP (Framework Proxy Not i v2).oidlib 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 Not i 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.
1024
03.05.2013
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 Import er. 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 Dat a St orage 1912 . For more information and download of MIB Import er, please see the link in the More 1029 section below.
SNMP Library SensorAdd 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. 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 Cont inue button.
Library-OIDs
Sensor Settings
03.05.2013
1025
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. Enter a string describing the unit of the returned values. This is for display purposes only. Please enter a string. 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. 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.
Unit String
Multiplication
Division
Chart Type
1026
03.05.2013
Inherited Settings
03.05.2013
1027
Maintenance End At
Dependency Type
1028
03.05.2013
More
Knowledge Base: How can I import my MIB files into PRTG? http://www.paessler.com/knowledgebase/en/topic/733
03.05.2013
1029

Notifications
Others
133
section.
1030
03.05.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 112 SNMP Linux Disk Free Sensor
6.8.112 SNM P Linux Disk Free Sensor

The SNMP Linux Disk Free sensor monitors free space on disks of a Linux/Unix system using Simple Network Management Protocol (SNMP). It shows the total free disk space (sum), and the free disk space in percent for every mounted partition (volume). Note: The free space returned by this sensor type shows the disk space that is not yet used. Not all of this space may be available for use, as a part of this space can be reserved by the system, e.g. for redundancy purposes. For details, please see the article linked in the More 1038 section below. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
Sensor Settings
Tags
Priority
08.10.2013
1031
Set limit s checked against ALL disks In this section you can set limits that are valid for all channels and all drives. By entering limits, you can define when the sensor will enter a Warning or Down status; depending on the data provided by all drives that this sensor monitors. If you want to define limits for separate channels individually please use the limit settings in the sensor's Channels settings. Note: All limits defined here are valid additionally to the limits defined in the particular Channels settings! Percentage Limit Check Enable or disable a limit check for the free space in percentage channels of all drives. By default percentage limits are enabled with lower warning and lower error limit. Choose between: Disable Percent age Limit s: Do not use the drives' data to control the sensor's status. Enable Percent age Limit s: Define limits. Additional fields appear below. The sensor will enter a warning or down state when free space limits are undercut or overrun. Upper Error Limit This field is only visible if percentage limit check is enabled above. Specify an upper limit in percent for a Down status. If the free disk space of one of your drives overruns this percent value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if percentage limit check is enabled above. Specify an upper limit in percent for a Warning status. If the free disk space of one of your drives overruns this percent value, the sensor will be set to Warning . Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if percentage limit check is enabled above. Specify a lower limit in percent for a warning state. If the free disk space of one of your drives undercuts this percent value, the sensor will be set to warning. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously!
Upper Warning Limit
Lower Warning Limit
1032
08.10.2013
Set limit s checked against ALL disks Lower Error Limit This field is only visible if percentage limit check is enabled above. Specify a lower limit in percent for entering a Down status. If the free disk space of one of your drives undercuts this percent value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! Enable or disable a limit check for the free bytes channels of all drives. Choose between: Disable By t e Limit s: Do not use the drives' data to control the sensor's status. Enable By t e Limit s: Define limits. Additional fields appear below. The sensor will enter a warning or down state when free space limits are undercut or overrun. Upper Error Limit This field is only visible if byte limit check is enabled above. Specify an upper limit. Use the same unit as shown by the free bytes channels of this sensor (by default this is MByte). If the free disk space of one of your drives overruns this bytes value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if byte limit check is enabled above. Specify an upper limit. Use the same unit as shown by the free bytes channels of this sensor (by default this is MByte). If the free disk space of one of your drives overruns this bytes value, the sensor will be set to Warning . Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if byte limit check is enabled above. Specify a lower limit. Use the same unit as shown by the free bytes channels of this sensor (by default this is MByte). If the free disk space of one of your drives undercuts this bytes value, the sensor will be set to Warning . Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously!
Byte Limit Check
Upper Warning Limit
Lower Warning Limit
08.10.2013
1033
Set limit s checked against ALL disks Lower Error Limit This field is only visible if byte limit check is enabled above. Specify a lower limit. Use the same unit as shown by the free bytes channels of this sensor (by default this is MByte). If the free disk space of one of your drives undercuts this bytes value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! If a monitored disk is removed or not found, values are set to zero. Select the alarming approach in this case. Choose between: Deact ivat e alarm (default ): Select this option if you do not want an alarm for a removed disk. Act ivat e Alarm: Select this option if you want to be alerted if a monitored disk is removed.
Alarm on Missing/ Removed Disk
Chart Type
1034
08.10.2013
Inherited Settings
Maintenance Window
Maintenance End At
08.10.2013
1035
Delay (Seconds)
1036
08.10.2013
08.10.2013
1037
More
Knowledge Base: Why do SSH Disk Free and SNMP Linux Disk Free show different values for my target Linux system? http://www.paessler.com/knowledgebase/en/topic/43183

Notifications
Others
133
section.
1038
08.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 113 SNMP Linux Load Average Sensor
6.8.113 SNM P Linux Load Average Sensor

The SNMP Load Average sensor monitors the system load average of a Linux/Unix system using Simple Network Management Protocol (SNMP). It shows the average system load within a one, five, and 15 minutes interval (each in one channel). For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
Sensor Settings
Tags
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. Note: You can set another primary channel later by clicking on the pin symbol
27.11.2012
1039
Sensor Display of a channel in the sensor's overview tab. Chart Type Define how different channels will be shown for this sensor. Show channels independent ly (default ): Show an own graph for each channel. St ack channels on t op of each ot her: Stack channels on top of each other to create a multi-channel graph. This will generate an easy-to-read graph which visualizes the different components of your total traffic. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 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
1040
27.11.2012
Maintenance Window
Maintenance End At
Dependency Type
27.11.2012
1041
Delay (Seconds)
1042
27.11.2012

Notifications
Others
133
section.
27.11.2012
1043
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 114 SNMP Linux Meminfo Sensor
6.8.114 SNM P Linux M eminfo Sensor

The SNMP Linux Meminfo sensor monitors the memory usage of a Linux/Unix system using Simple Network Management Protocol (SNMP). It shows the available memory in total and in percent. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
Sensor Settings
Tags
Priority
1044
08.10.2013
Inherited Settings
08.10.2013
1045
Maintenance Window
Maintenance End At
Dependency Type
1046
08.10.2013
Delay (Seconds)
08.10.2013
1047

Notifications
Others
133
section.
1048
08.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 115 SNMP Linux Physical Disk Sensor
6.8.115 SNM P Linux Phy sical Disk Sensor

The SNMP Linux Physical Disk sensor monitors input/output (I/O) on disks of a Linux/Unix system using Simple Network Management Protocol (SNMP). It shows read and written bytes per second, read and write accesses per second, as well as load average within a specific time span (1, 5, and 15 minutes), depending on the counters available on the disk. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor I/O on disks of a Linux/Unix system, PRTG will create one sensor for each disk you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Phy sical Disk Set t ings Disk Select one or more disks you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
19.07.2013
1049
Priority
Phy sical Disk Set t ings Disk Bitmask Shows further information about the disk that this sensor is monitoring. 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.
Set limit s checked against ALL disks In this section you can set limits that are valid for all channels and all drives. By entering limits, you can define when the sensor will enter a Warning or Down status; depending on the data provided by all drives that this sensor monitors. If you want to define limits for separate channels individually please use the limit settings in the sensor's Channels settings. Note: All limits defined here are valid additionally to the limits defined in the particular Channels settings! Percentage Limit Check Enable or disable a limit check for load average in percentage channels of all drives. By default percentage limits are enabled with lower warning and lower error limit. Choose between: Disable Percent age Limit s: Do not use the drives' data to control the sensor's status. Enable Percent age Limit s: Define limits. Additional fields appear below. The sensor will enter a warning or down state when load average limits are undercut or overrun.
1050
19.07.2013
Set limit s checked against ALL disks Upper Error Limit This field is only visible if percentage limit check is enabled above. Specify an upper limit in percent for a Down status. If load average of one of your drives overruns this percent value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if percentage limit check is enabled above. Specify an upper limit in percent for a Warning status. If load average of one of your drives overruns this percent value, the sensor will be set to Warning . Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if percentage limit check is enabled above. Specify a lower limit in percent for a warning state. If load average of one of your drives undercuts this percent value, the sensor will be set to warning. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if percentage limit check is enabled above. Specify a lower limit in percent for entering a Down status. If load average of one of your drives undercuts this percent value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! Enable or disable a limit check for read and written bytes channels of all drives. Choose between: Disable By t e Limit s: Do not use the drives' data to control the sensor's status. Enable By t e Limit s: Define limits. Additional fields appear below. The sensor will enter a warning or down state when read and written bytes limits are undercut or overrun.
Upper Warning Limit
Lower Warning Limit
Lower Error Limit
Byte Limit Check
19.07.2013
1051
Set limit s checked against ALL disks Upper Error Limit This field is only visible if byte limit check is enabled above. Specify an upper limit. Use the same unit as shown by the bytes channels of this sensor (by default this is MByte). If the read and/or written bytes of one of your drives overruns this bytes value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if byte limit check is enabled above. Specify an upper limit. Use the same unit as shown by the bytes channels of this sensor (by default this is MByte). If the read and/or written bytes of one of your drives overruns this bytes value, the sensor will be set to Warning . Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if byte limit check is enabled above. Specify a lower limit. Use the same unit as shown by the bytes channels of this sensor (by default this is MByte). If the read and/or written bytes of one of your drives undercuts this bytes value, the sensor will be set to Warning . Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if byte limit check is enabled above. Specify a lower limit. Use the same unit as shown by the bytes channels of this sensor (by default this is MByte). If the read and/or written bytes of one of your drives undercuts this bytes value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! If a monitored disk is removed or not found, values are set to zero. Select the alarming approach in this case. Choose between: Deact ivat e alarm (default ): Select this option if you do not want an alarm for a removed disk. Act ivat e Alarm: Select this option if you want to be alerted if a monitored disk is removed.
Upper Warning Limit
Lower Warning Limit
Lower Error Limit
1052
19.07.2013
Chart Type
Inherited Settings
19.07.2013
1053
Maintenance Window
Maintenance End At
Dependency Type
1054
19.07.2013
Delay (Seconds)
19.07.2013
1055

Notifications
Others
133
section.
1056
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 116 SNMP Memory Sensor
6.8.116 SNM P M emory Sensor

The SNMP Memory sensor monitors the memory usage of a system via Simple Network Management Protocol (SNMP). It can show the available memory in total and in percent, as well as the total memory. Note: This sensor uses more generic Object Identifier (OID) values compared to the SNMP Linux Meminfo Sensor 1044 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor memory usage, PRTG will create one sensor for each memory type you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Memory Set t ings Memory Select one or more memory types you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
07.02.2013
1057
Priority
Memory Set t ings Memory Shows the type of the memory that this sensor is monitoring. 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.
Chart Type
1058
07.02.2013
Inherited Settings
Maintenance Window
Maintenance End At
07.02.2013
1059
Delay (Seconds)
1060
07.02.2013
07.02.2013
1061

Notifications
Others
133
section.
1062
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 117 SNMP NetApp Disk Free Sensor
6.8.117 SNM P NetApp Disk Free Sensor

The SNMP NetApp Disk Free sensor monitors free space on disks of a NetApp storage system via Simple Network Management Protocol (SNMP). It can show deduplication saved space and shared space, in total and in percent; disk free (total and percent), as well as percentage values for files free and inodes free. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor disk space on a NetApp, PRTG will create one sensor for each disk. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Net App Disk Free Set t ings File System Select the disks you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
07.02.2013
1063
Priority
Net App Disk Free Set t ings File System Shows the name of the disk that this sensor is monitoring. 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. Shows the name of the virtual disk that this sensor is monitoring (if applicable). 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.
Virtual Disk
Chart Type
1064
07.02.2013
Inherited Settings
07.02.2013
1065
Maintenance End At
Dependency Type
1066
07.02.2013
07.02.2013
1067

Notifications
Others
133
section.
1068
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 118 SNMP NetApp Enclosure Sensor
6.8.118 SNM P NetApp Enclosure Sensor

The SNMP NetApp Enclosure sensor monitors the power supply and cooling of an enclosure that is part of a NetApp storage system via SNMP. It can measure temperatures, fans, voltages, and currents. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor power supply and cooling of an enclosure on a NetApp, PRTG will create one sensor for each enclosure/measurement combination. 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:
Net App Enclosure Set t ings Enclosure Select the enclosures with the desired measurement you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
07.02.2013
1069
Priority
Net App Enclosure Set t ings Enclosure Shows the identifier of the enclosure that this sensor is monitoring. 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. Shows the monitored measurement. 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.
Measurement
Chart Type
1070
07.02.2013
Inherited Settings
07.02.2013
1071
Maintenance End At
Dependency Type
1072
07.02.2013
07.02.2013
1073

Notifications
Others
133
section.
1074
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 119 SNMP NetApp I/O Sensor
6.8.119 SNM P NetApp I/O Sensor

The SNMP NetApp I/O sensor monitors input/output operations (IOPS) on a NetApp storage system via Simple Network Management Protocol (SNMP). It can show FCP Read, CIFS Ops, Disk Read, Disk Write, FCP Ops, FCP Write, HTTP Ops, ISCSI Ops, ISCSI Read, ISCSI Write, Network Received, Network Sent, NFS Ops, Tape Read, and Tape Write. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
Sensor Settings
Tags
Priority
27.11.2012
1075
Chart Type
Inherited Settings
1076
27.11.2012
Maintenance Window
Maintenance End At
Dependency Type
27.11.2012
1077
Delay (Seconds)
1078
27.11.2012
27.11.2012
1079

Notifications
Others
133
section.
1080
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 120 SNMP NetApp License Sensor
6.8.120 SNM P NetApp License Sensor

The SNMP NetApp License sensor monitors the licenses for the services of a NetApp storage system via Simple Network Management Protocol (SNMP). It indicates how much time is left until the license for a service expires. This can help you to detect when a timely limited NetApp license is going to expire. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor licenses on a NetApp, PRTG will create one sensor for each license. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Net App License Set t ings License for Service Select the licenses you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
07.02.2013
1081
Priority
Net App License Set t ings License for Service Shows the name of the license that this sensor is monitoring. 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.
Chart Type
1082
07.02.2013
Inherited Settings
Maintenance Window
Maintenance End At
07.02.2013
1083
Delay (Seconds)
1084
07.02.2013
07.02.2013
1085

Notifications
Others
133
section.
1086
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 121 SNMP NetApp Network Interface Sensor
6.8.121 SNM P NetApp Network Interface Sensor

The SNMP NetApp Network Interface sensor monitors a network card of a NetApp storage system via Simple Network Management Protocol (SNMP). It can show traffic in and out, as well as the number of errors per second (in and out). For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor network interfaces on a NetApp, PRTG will create one sensor for each interface. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Net App Net work Int erface Set t ings Network Interface Select the interfaces you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
07.02.2013
1087
Priority
Net App Net work Int erface Set t ings Network Interface Shows the name of the interface that this sensor is monitoring. 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. Note: You can set another primary channel later by clicking on the pin symbol of a channel in the sensor's overview tab. Define how different channels will be shown for this sensor. Show channels independent ly (default ): Show an own graph for each channel. St ack channels on t op of each ot her: Stack channels on top of each other to create a multi-channel graph. This will generate an easy-to-read graph which visualizes the different components of your total traffic. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 settings). Show in and out t raffic as posit ive and negat ive area chart : Show channels for incoming and outgoing traffic as positive and negative area chart. This will visualize your traffic in a clear way. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 settings).
Chart Type
1088
07.02.2013
Inherited Settings
Maintenance Window
07.02.2013
1089
Maintenance End At
Dependency Type
Delay (Seconds)
1090
07.02.2013
07.02.2013
1091

Notifications
Others
133
section.
1092
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 122 SNMP NetApp System Health Sensor
6.8.122 SNM P NetApp Sy stem Health Sensor

The SNMP NetApp Disk Free sensor monitors free space on disks of a NetApp storage system via Simple Network Management Protocol (SNMP). It can show the CPU load in percent, active restore, current CIFS users; the number of disks active, being added, being scrubbed, failed, failing soon, being out of date, reconstructing (parity), spare, verifying parity, and total; the number of fans and power supplies failed; as well as the max used disk space and max used inodes, in percent. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
Sensor Settings
Tags
Priority
27.11.2012
1093
Chart Type
Inherited Settings
1094
27.11.2012
Maintenance Window
Maintenance End At
Dependency Type
27.11.2012
1095
Delay (Seconds)
1096
27.11.2012
27.11.2012
1097

Notifications
Others
133
section.
1098
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 123 SNMP Poseidon Environment Sensor
6.8.123 SNM P Poseidon Environment Sensor

The SNMP Poseidon Environment sensor monitors performance counters for environmental measurements on Poseidon hardware via Simple Network Management Protocol (SNMP). It can show, for example, humidity and temperature in the environment, depending on available measurement components on the hardware device. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor performance counters for environmental measurements on Poseidon hardware, PRTG will create one sensor for each measuring point you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Poseidon Environment Specific Measuring Point Select the measurements you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
13.06.2013
1099
Priority
Poseidon Environment Specific Name Unit Measuring Point Shows further information about the measurement. 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.
Chart Type
1100
13.06.2013
Inherited Settings
Maintenance Window
13.06.2013
1101
Maintenance End At
Dependency Type
Delay (Seconds)
1102
13.06.2013

Notifications
Others
133
section.
13.06.2013
1103
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 124 SNMP QNAP Logical Disk Sensor
6.8.124 SNM P QNAP Logical Disk Sensor

The SNMP QNAP Logical Disk sensor monitors a logical disk in a QNAP Network Attached Storage (NAS) via Simple Network Management Protocol (SNMP). It can show free space and free bytes, as well as the status of a volume. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor the logical disks in a QNAP NAS, PRTG will create one sensor for each disk you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
QNAP NAS Set t ings Disk Select the logical disks you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
1104
13.06.2013
Priority
QNAP NAS Set t ings Disk Description File System Shows further information about the 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.
Chart Type
13.06.2013
1105
Inherited Settings
Maintenance Window
1106
13.06.2013
Maintenance End At
Dependency Type
Delay (Seconds)
13.06.2013
1107

Notifications
Others
133
section.
1108
13.06.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 125 SNMP QNAP Physical Disk Sensor
6.8.125 SNM P QNAP Phy sical Disk Sensor

The SNMP QNAP Physical Disk sensor monitors a physical disk in a QNAP Network Attached Storage (NAS) via Simple Network Management Protocol (SNMP). It can show the temperature, the HD status, and the Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) status of the disk. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor the physical disks in a QNAP NAS, PRTG will create one sensor for each disk you choose. You can also define the unit of the temperature measurement. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
QNAP NAS Set t ings Disk Select the physical disks you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. Select the unit of the temperature measurement. Choose between Celsius and Fahrenheit .
Unit
Sensor Settings
13.06.2013
1109
Tags
Priority
QNAP NAS Set t ings Disk Description Model Capacity Unit Shows further information about the 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.
Chart Type
1110
13.06.2013
Inherited Settings
13.06.2013
1111
Maintenance End At
Dependency Type
1112
13.06.2013

13.06.2013
1113
Notifications
Others
133
section.
1114
13.06.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 126 SNMP QNAP System Health Sensor
6.8.126 SNM P QNAP Sy stem Health Sensor

The SNMP QNAP System Health sensor monitors the system health of a QNAP Network Attached Storage (NAS) via Simple Network Management Protocol (SNMP). It can show the usage of the CPU, available memory in absolute numbers and percent, the temperature of CPU and system, as well as various other values, for example, revolutions of fans per minute, depending on the available measurement components. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor the system health of a QNAP NAS, please specify the unit of the temperature measurement. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
QNAP NAS Set t ings Unit Select the unit of the temperature measurement. Choose between Celsius and Fahrenheit .
Sensor Settings
Tags
13.06.2013
1115
QNAP NAS Set t ings Unit Shows the unit of temperatures as monitored with 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.
Chart Type
1116
13.06.2013
Inherited Settings
Maintenance Window
Maintenance End At
13.06.2013
1117
Delay (Seconds)
1118
13.06.2013

Notifications
Others
133
section.
13.06.2013
1119
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 127 SNMP RMON Sensor
6.8.127 SNM P RM ON Sensor

The SNMP RMON sensor monitors traffic on a device using the Remote Monitoring (RMON) standard via Simple Network Management Protocol (SNMP). It can be created on an SNMP compatible device which provides traffic data via RMON. Depending on the data returned by your device, traffic data for each port can be displayed in different channels, allowing detailed analysis. For example, available channels for each traffic port may include Transmitted kbit/s, Packets (#/ s), Broadcast Packets (#/s), Multicast Packets (#/s), CRC Errors (#/s), Undersize Packets (#/s), Oversize Packets (#/s), Fragments (#/s), Jabbers (#/s), Collisions (#/s), Packets <= 64 Byte (#/ s), Packets 65 - 127 Bytes (#/s), Packets 128 - 255 Bytes (#/s), Packets 256 - 511 Bytes (#/s), Packets 512 - 1023 Bytes (#/s), Packets 1024 - 1518 Bytes (#/s), and Drop Events (#/s). For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. For SNMP devices with multiple interfaces 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:
RMON Specific Interface number Select the interfaces you want to add a sensor for. A list of SNMP device interfaces is shown containing all traffic interfaces which the device provides via Remote Monitoring (RMON). In the In Use column you will see a Yes if there was already traffic detected on this interface in the past, and a No if there wasn't any traffic yet on this interface (since last device restart, usually). The In Use column does not show whether or not an interface is currently connected! Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
1120
13.06.2013
Tags
Priority
RMON Specific Port Shows the number of the interface port in your physical device that this sensor is monitoring. 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.
Chart Type
13.06.2013
1121
Inherited Settings
1122
13.06.2013
Maintenance End At
Dependency Type
13.06.2013
1123
1124
13.06.2013

Notifications
Others
133
section.
13.06.2013
1125
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 128 SNMP SonicWALL System Health Sensor
6.8.128 SNM P SonicWALL Sy stem Health Sensor

The SNMP SonicWALL System Health sensor monitors health values of a Dell SonicWALL Network Security Appliance (NSA) via Simple Network Management Protocol (SNMP). It shows usage of CPU and memory, as well as usage of the connection cache. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
Sensor Settings
Tags
Priority
1126
15.08.2013
Inherited Settings
15.08.2013
1127
Maintenance Window
Maintenance End At
Dependency Type
1128
15.08.2013
Delay (Seconds)
15.08.2013
1129

Notifications
Others
133
section.
1130
15.08.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 129 SNMP SonicWALL VPN Traffic Sensor
6.8.129 SNM P SonicWALL VPN Traffic Sensor

The SNMP SonicWALL VPN Traffic sensor monitors the traffic of an Internet Protocol Security (IPsec) Virtual Private Network (VPN) on a Dell SonicWALL Network Security Appliance (NSA) via Simple Network Management Protocol (SNMP). It can show the number of encrypted and decrypted packets, the number of bytes of encrypted and decrypted transmissions, as well as the number of in- and outgoing fragmented packets. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor the traffic of a SonicWALL VPN, PRTG will create one sensor for each connection you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
SonicWALL VPN Specific Connections Select the connections you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. Select the criteria PRTG will use to identify the connection. PRTG will always use the first connection found that matches all criteria. Choose between: By Index: Every connection has a unique index. This is the safest method to identify your connection. Though, if the connection is lost and reconnected, a new index will be assigned. By Remot e IP: If the target of the VPN has always the same IP, you can use this IP to identify the connection. By Securit y Policy Name: If you use a different Security Policy for every VPN, you can use its name to identify the connection. By Remot e IP and Securit y Policy Name: You can also combine both identification methods.
Identification Method
Sensor Settings
08.10.2013
1131
Tags
Priority
SonicWALL VPN Specific Security Policy Remote IP Index Identification Method Shows further information about the monitored connection. 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.
Chart Type
1132
08.10.2013
Maintenance Window
08.10.2013
1133
Maintenance End At
Dependency Type
Delay (Seconds)
1134
08.10.2013
08.10.2013
1135

Notifications
Others
133
section.
1136
08.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 130 SNMP Synology Logical Disk Sensor
6.8.130 SNM P Sy nology Logical Disk Sensor

The SNMP Synology Logical Disk sensor monitors a logical disk in a Synology Network Attached Storage (NAS) via Simple Network Management Protocol (SNMP). It can show the status of a volume. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor the logical disks in a Synology NAS, PRTG will create one sensor for each disk you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Sy nology NAS Set t ings Disk Select the logical disks you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
13.06.2013
1137
Priority
Sy nology NAS Set t ings Disk Shows further information about the 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
Chart Type
1138
13.06.2013
Inherited Settings
Maintenance Window
Maintenance End At
13.06.2013
1139
Delay (Seconds)
1140
13.06.2013

Notifications
Others
133
section.
13.06.2013
1141
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 131 SNMP Synology Physical Disk Sensor
6.8.131 SNM P Sy nology Phy sical Disk Sensor

The SNMP Physical Disk sensor monitors a physical disk in a Synology Network Attached Storage (NAS) via Simple Network Management Protocol (SNMP). It can show temperature and disk status. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor the physical disks in a Synology NAS, PRTG will create one sensor for each disk you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Sy nology NAS Set t ings Disk Select the physical disks you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
1142
13.06.2013
Priority
Sy nology NAS Set t ings Disk Name Model Type Shows further information about the 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.
Chart Type
13.06.2013
1143
Inherited Settings
Maintenance Window
1144
13.06.2013
Maintenance End At
Dependency Type
Delay (Seconds)
13.06.2013
1145

Notifications
Others
133
section.
1146
13.06.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 132 SNMP Synology System Health Sensor
6.8.132 SNM P Sy nology Sy stem Health Sensor

The SNMP Synology System Health sensor monitors the system health of a Synology Network Attached Storage (NAS) via Simple Network Management Protocol (SNMP). It can show temperature, system status, power status, fan status, as well as several other values, depending on the available measurement components. This sensor type uses lookups to determine the status values of some sensor channels. For details, please see section Define Lookups 1879 . For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor the system health of a Synology NAS, please specify the unit of the temperature measurement. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Sy nology NAS Set t ings Unit Select the unit of the temperature measurement. Choose between Celsius and Fahrenheit .
Sensor Settings
13.06.2013
1147
Priority
Sy nology NAS Set t ings Unit Shows the unit of temperatures as monitored with 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.
Chart Type
1148
13.06.2013
Inherited Settings
Maintenance Window
Maintenance End At
13.06.2013
1149
Delay (Seconds)
1150
13.06.2013

Notifications
Others
133
section.
13.06.2013
1151
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 133 SNMP System Uptime Sensor
6.8.133 SNM P Sy stem Uptime Sensor

The SNMP System Uptime sensor monitors the uptime of a device using Simple Network Management Protocol (SNMP). It read a device's value for system uptime and shows it. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
Sensor Settings
Tags
Priority
1152
27.11.2012
Inherited Settings
27.11.2012
1153
Maintenance End At
Dependency Type
1154
27.11.2012

27.11.2012
1155
Notifications
Others
133
section.
1156
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 134 SNMP Traffic Sensor
6.8.134 SNM P Traffic Sensor

The SNMP Traffic sensor monitors traffic on a device using Simple Network Management Protocol (SNMP). It can be created on a device which provides traffic data. For each individual port one traffic sensor is created. It can show traffic in, traffic out, and traffic total. Additional channels can be added. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. For SNMP devices with multiple interfaces 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:
Traffic Specific Interface number Select the interfaces you want to add a sensor for. A list of SNMP device interfaces is shown; containing all interfaces which your device provides. Connected interfaces are printed in bold face; not connected in non-bold face. One sensor will be created for each interface. You can group-select and -unselect interfaces by using the buttons Select all connect ed int erfaces, Select all disconnect ed int erfaces, and Deselect all int erfaces. You can also select and deselect all items by using the check box in the table head. For the standard channel "Traffic In" enter the description here. It will be shown in graphs and tables. You can change this description and the description of all other channels in the sensor's channel settings 1566 later. For the standard channel "Traffic Out" enter the description here. It will be shown in graphs and tables. You can change this description and the description of all other channels in the sensor's channel settings 1566 later. For the standard channel traffic "Sum" enter the description here. It will be shown in graphs and tables. You can change this description and the description of all other channels in the sensor's channel settings 1566 later.
Description IN
Description OUT
Description SUM
07.02.2013
1157
Sensor Settings
Tags
Priority
1158
07.02.2013
Traffic Specific Interface number Shows the number and name of the interface in your physical device that this sensor is monitoring. 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. By default, the channels "Traffic In" and "Traffic out" are created for each sensor. Choose additional channels for all selected interfaces. Please click on the respective channel name(s); a check mark symbol will appear in front of them. You can choose from the following additional channels: Errors In & Out Discards In & Out Unicast Packet s In & Out Non Unicast Packet s In & Out (32-bit only ) Mult icast Packet s In & Out (64-bit only ) Broadcast Packet s In & Out (64-bit only ) Unknown Prot ocols Channels that are once created cannot be deleted later. They can be disabled only. Connection State Handling Choose how PRTG will react when an interface is disconnected. A disconnected interface is, for example, an ethernet port on a switch with no cable plugged in. This setting is valid for all interfaces selected above. You can choose between: Show alarm when disconnect ed (recommended): The sensor for the interface will turn into a red error state. Ignore int erface when disconnect ed: No alarm will be shown in PRTG; monitoring will be discontinued without notice.
Additional Channels
Chart Type
07.02.2013
1159
Sensor Display Show channels independent ly (default ): Show an own graph for each channel. St ack channels on t op of each ot her: Stack channels on top of each other to create a multi-channel graph. This will generate an easy-to-read graph which visualizes the different components of your total traffic. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 settings). Show in and out t raffic as posit ive and negat ive area chart : Show channels for incoming and outgoing traffic as positive and negative area chart. This will visualize your traffic in a clear way. Note: This option cannot be used in combination with manual Vertical Axis Scaling (available in the Sensor Channels Set t ings 1566 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
1160
07.02.2013
Maintenance Window
Maintenance End At
Dependency Type
07.02.2013
1161
Delay (Seconds)
1162
07.02.2013
More
Knowledge Base: How do PRTG's automatic port name and number updates work for SNMP traffic sensors? http://www.paessler.com/knowledgebase/en/topic/25893

Notifications
Others
133
section.
07.02.2013
1163
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 135 SNMP Trap Receiver Sensor
6.8.135 SNM P Trap Receiver Sensor

The SNMP Trap Receiver sensor receives and analyzes Simple Network Management Protocol (SNMP) traps. It returns the number of new traps per second received within the last scanning interval as well as the number of warnings per second. For a general introduction to the technology behind SNMP, please see Monit oring via SNMP 1809 section.
Add Sensor
Sensor Settings
Tags
Priority
1164
18.02.2013
OID Values OID Value Enter the OID of the SNMP object you want to receive numerical data from. Note: Most OIDs begin with 1.3.6.1. However, entering OIDs starting with 1.0, or 1.1, or 1.2 is also allowed. If you want to disable the validation of your entry entirely, add the string norfccheck: at the beginning of your OID, for example, norfccheck:2.0.0.0.1. Define the port on which SNMP traps are received. We recommend using the default value. Define what will be done when a message comes in. Choose between: Do not hing : Do not perform any action. Writ e message t o log and fire 'change' t rigger: Write an entry to the PRTG log file every time a message is received and fire one change trigger after each scanning interval, if messages were received during this interval. Note: Use with caution; this option may create a lot of log entries! Sender Define if you want to filter for a specific sender only. If you enter something here, only traps with this sender will be regarded. Make sure the string matches exactly the value of the sender value in the trap. Please enter a string or leave the field empty. Define if you want to filter for a specific trap code value only. If you enter something here, only traps with this code will be regarded. Make sure the value matches exactly the code in the trap. Please enter an integer value or leave the field empty. Define when the sensor will be put to a Warning status. Choose between: Never: Never put the sensor to a warning status. Depending on Cont ent : Put the sensor to a warning status, depending on the content of the messages received. Please define below. Message Must Include This setting is only visible if a sensor status change is enabled above. Define which string must be part of the trap's message. If the message does not include this string, the sensor will be set to a Warning status. Please enter a string or leave the field empty. This setting is only visible if a sensor status change is enabled above. Define which string must not be part of the trap's message. If the message does include this string, the sensor will be set to a Warning status. Please enter a string or leave the field empty.
Listen on Port
When Message Comes In
Specific Trap Code
Set Sensor to 'Warning'
Message Must Not Include
18.02.2013
1165
Chart Type
Inherited Settings
1166
18.02.2013
Maintenance Window
Maintenance End At
Dependency Type
18.02.2013
1167
Delay (Seconds)
1168
18.02.2013
More
Knowledge Base: How can I use PRTGs trap receiver and what are its limitations? http://www.paessler.com/knowledgebase/en/topic/143 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 Knowledge Base: How do I test an SNMP Trap Receiver Sensor? http://www.paessler.com/knowledgebase/en/topic/10193

Notifications
Others
133
section.
18.02.2013
1169
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 136 SNTP Sensor
6.8.136 SNTP Sensor

The SNTP Sensor monitors a Simple Network Time Protocol (SNTP) server. It returns the response time and the time difference in comparison to the local system time.
Add Sensor
Sensor Settings
Tags
Priority
Sensor Set t ings Timeout (sec.) Enter a timeout in seconds. If the reply takes longer than this value the request is aborted and an error message is triggered.
1170
27.11.2012
Chart Type
Inherited Settings
27.11.2012
1171
Maintenance Window
Maintenance End At
Dependency Type
1172
27.11.2012
Delay (Seconds)
27.11.2012
1173

Notifications
Others
133
section.
1174
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 137 SSH Disk Free Sensor
6.8.137 SSH Disk Free Sensor

The SSH Disk Free sensor monitors free space on disks of a Linux/Unix system using Secure Shell (SSH). It shows the total free disk space (sum), and the free disk space in percent for every mounted partition (volume). Note: The free space returned by this sensor type shows the available disk space of the volume, minus a reserve defined for this volume (e.g. for redundancy purposes). So, this sensor shows the disk space that is actually available for use. The size of the reserved disk space can be defined with tune2fs. For details, please see the article linked in the More 1182 section below. For this sensor type credentials for Linux (SSH/WBEM) systems must be defined for the device you want to use the sensor on. Note: Not all Linux/Unix and Mac OS distributions can be supported by this sensor type. For a general introduction to SSH monitoring, please see Monit oring via SSH
1816
section.
Add Sensor
Sensor Settings
Tags
27.11.2012
1175
SSH Specific Connection Timeout (sec.) Define a timeout for the connection. This is the the time the sensor waits to establish a connection to the host. You should keep this value as low as possible. Define a timeout for the shell response. This is the time in seconds the sensor waits for the shell to return a response after it has sent its specific command (e.g. cat /proc/loadavg). Define which port this sensor will use for the SSH connection. Choose between: Inherit port number from parent device (default ): Use the port number as defined in the Credentials for Linux/Solaris/Mac OS (SSH/WBEM) Systems section of the device this sensor is created on. Ent er cust om port number: Do not use the port number from the parent device's settings, but define a different port number below. Use Port Number This field is only visible if the custom port number setting is enabled above. Enter the port number this sensor will use for the SSH connection. Please enter an integer value. Define what will be done with the result of the query. Choose between: Discard t ext result : Do not store the requested web page. St ore lat est t ext result : Store the last result received from the query to the "Logs (Sensors)" directory (on the Master node, if in a cluster). File name: Result of Sensor [ID].txt. This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
SSH Port
Result Handling
1176
27.11.2012
Set limit s checked against ALL disks In this section you can set limits that are valid for all channels and all drives. By entering limits, you can define when the sensor will enter a Warning or Down status; depending on the data provided by all drives that this sensor monitors. If you want to define limits for separate channels individually please use the limit settings in the sensor's Channels settings. Note: All limits defined here are valid additionally to the limits defined in the particular Channels settings! Percentage Limit Check Enable or disable a limit check for the free space in percentage channels of all drives. By default percentage limits are enabled with lower warning and lower error limit. Choose between: Disable Percent age Limit s: Do not use the drives' data to control the sensor's status. Enable Percent age Limit s: Define limits. Additional fields appear below. The sensor will enter a warning or down state when free space limits are undercut or overrun. Upper Error Limit This field is only visible if percentage limit check is enabled above. Specify an upper limit in percent for a Down status. If the free disk space of one of your drives overruns this percent value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if percentage limit check is enabled above. Specify an upper limit in percent for a Warning status. If the free disk space of one of your drives overruns this percent value, the sensor will be set to Warning . Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if percentage limit check is enabled above. Specify a lower limit in percent for a warning state. If the free disk space of one of your drives undercuts this percent value, the sensor will be set to warning. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously!
Upper Warning Limit
Lower Warning Limit
27.11.2012
1177
Set limit s checked against ALL disks Lower Error Limit This field is only visible if percentage limit check is enabled above. Specify a lower limit in percent for entering a Down status. If the free disk space of one of your drives undercuts this percent value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! Enable or disable a limit check for the free bytes channels of all drives. Choose between: Disable By t e Limit s: Do not use the drives' data to control the sensor's status. Enable By t e Limit s: Define limits. Additional fields appear below. The sensor will enter a warning or down state when free space limits are undercut or overrun. Upper Error Limit This field is only visible if byte limit check is enabled above. Specify an upper limit. Use the same unit as shown by the free bytes channels of this sensor (by default this is MByte). If the free disk space of one of your drives overruns this bytes value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if byte limit check is enabled above. Specify an upper limit. Use the same unit as shown by the free bytes channels of this sensor (by default this is MByte). If the free disk space of one of your drives overruns this bytes value, the sensor will be set to Warning . Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if byte limit check is enabled above. Specify a lower limit. Use the same unit as shown by the free bytes channels of this sensor (by default this is MByte). If the free disk space of one of your drives undercuts this bytes value, the sensor will be set to Warning . Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously!
Byte Limit Check
Upper Warning Limit
Lower Warning Limit
1178
27.11.2012
Set limit s checked against ALL disks Lower Error Limit This field is only visible if byte limit check is enabled above. Specify a lower limit. Use the same unit as shown by the free bytes channels of this sensor (by default this is MByte). If the free disk space of one of your drives undercuts this bytes value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! If a monitored disk is removed or not found, values are set to zero. Select the alarming approach in this case. Choose between: Deact ivat e alarm (default ): Select this option if you do not want an alarm for a removed disk. Act ivat e Alarm: Select this option if you want to be alerted if a monitored disk is removed.
Chart Type
27.11.2012
1179
Inherited Settings
Maintenance Window
Maintenance End At
1180
27.11.2012
Delay (Seconds)
27.11.2012
1181
More
Knowledge Base: How and Where Does PRTG Store its Data?
1182
27.11.2012
http://www.paessler.com/knowledgebase/en/topic/463 Knowledge Base: Why do SSH Disk Free and SNMP Linux Disk Free show different values for my target Linux system? http://www.paessler.com/knowledgebase/en/topic/43183

Notifications
Others
133
section.
27.11.2012
1183
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 138 SSH INodes Free Sensor
6.8.138 SSH INodes Free Sensor

The SSH INodes Free sensor monitors the free index nodes on disks of Linux/Unix and Mac OS systems via Secure Shell (SSH). It shows the free index nodes in percent, for each mount in an own sensor channel. UNIX file systems only allow a limited number of index nodes. If the limit is exceeded, no more data can be stored, although there might be still free space available. This sensor can help you to notice early on if one of your drives is running out of INodes. For this sensor type credentials for Linux (SSH/WBEM) systems must be defined for the device you want to use the sensor on. Note: Not all Linux/Unix and Mac OS distributions can be supported by this sensor type. For a general introduction to SSH monitoring, please see Monit oring via SSH
1816
section.
Add Sensor
Sensor Settings
Tags
Priority
1184
27.11.2012
SSH Port
Result Handling
Chart Type
27.11.2012
1185
Inherited Settings
1186
27.11.2012
Maintenance End At
Dependency Type
27.11.2012
1187
1188
27.11.2012
More
Knowledge Base: How and Where Does PRTG Store its Data? http://www.paessler.com/knowledgebase/en/topic/463

Notifications
Others
133
section.
27.11.2012
1189
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 139 SSH Load Average Sensor
6.8.139 SSH Load Average Sensor

The SSH Load Average sensor monitors the load average of a Linux/Unix system using Secure Shell (SSH). It shows the average system load within a one, five, and 15 minutes interval (each in one channel). For this sensor type credentials for Linux (SSH/WBEM) systems must be defined for the device you want to use the sensor on. Note: Not all Linux/Unix and Mac OS distributions can be supported by this sensor type. For a general introduction to SSH monitoring, please see Monit oring via SSH
1816
section.
Add Sensor
Sensor Settings
Tags
Priority
1190
27.11.2012
SSH Port
Result Handling
Chart Type
27.11.2012
1191
Inherited Settings
1192
27.11.2012
Maintenance End At
Dependency Type
27.11.2012
1193
1194
27.11.2012
More

Notifications
Others
133
section.
27.11.2012
1195
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 140 SSH Meminfo Sensor
6.8.140 SSH M eminfo Sensor

The SSH Meminfo sensor monitors the memory usage of a Linux/Unix system using Secure Shell (SSH). It shows the available memory in total and in percent. Note: This sensor type is not compatible with Mac OS systems. For this sensor type credentials for Linux (SSH/WBEM) systems must be defined for the device you want to use the sensor on. Note: Not all Linux/Unix and Mac OS distributions can be supported by this sensor type. For a general introduction to SSH monitoring, please see Monit oring via SSH
1816
section.
Add Sensor
Sensor Settings
Tags
Priority
1196
27.11.2012
SSH Port
Result Handling
Chart Type
27.11.2012
1197
Inherited Settings
1198
27.11.2012
Maintenance End At
Dependency Type
27.11.2012
1199
1200
27.11.2012
More

Notifications
Others
133
section.
27.11.2012
1201
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 141 SSH Remote Ping Sensor
6.8.141 SSH Remote Ping Sensor

The SSH Remote Ping sensor remotely monitors the connectivity between a system running Linux/OS X and an other device, using Internet Control Message Protocol (ICMP) echo requests ("Ping") and Secure Shell (SSH). It can show packet loss, as well as minimum, maximum, and average response times; all measured from the remote device you connect to. For this sensor type credentials for Linux (SSH/WBEM) systems must be defined for the device you want to use the sensor on. Note: Not all Linux/Unix and Mac OS distributions can be supported by this sensor type. For a general introduction to SSH monitoring, please see Monit oring via SSH
1816
section.
Add Sensor
Sensor Settings
Tags
Priority
1202
27.11.2012
SSH Remot e Ping Configurat ion Target Enter the DNS name or IP address of the target device the Ping is sent to. The sensor will remotely connect to the parent device it is created on via SSH, then perform a Ping request from this remote device to the target device/server. Please enter a string. Enter the packet size in bytes for the Ping. You can choose any value between 1 and 10000. Please enter an integer value. We recommend using the default value. Enter the number of packets that is sent with each scanning interval. Optionally enter additional parameters that will be added at the end of the ping command. Please do not use parameters that change the output format of the result to make sure it can still be parsed. You cannot enter another command here. Please enter a string or leave the field empty.
Packet Size (Bytes)
Packet Count
Custom Parameter
SSH Specific Connection Timeout (sec.) Define a timeout for the connection. This is the the time the sensor waits to establish a connection to the host. You should keep this value as low as possible. Define a timeout for the shell response. This is the time in seconds the sensor waits for the shell to return a response after it has sent its specific command (e.g. cat /proc/loadavg). Define which port this sensor will use for the SSH connection. Choose between: Inherit port number from parent device (default ): Use the port number as defined in the Credentials for Linux/Solaris/Mac OS (SSH/WBEM) Systems section of the device this sensor is created on. Ent er cust om port number: Do not use the port number from the parent device's settings, but define a different port number below. Use Port Number This field is only visible if the custom port number setting is enabled above. Enter the port number this sensor will use for the SSH connection. Please enter an integer value. Define what will be done with the result of the query. Choose between:
SSH Port
Result Handling
27.11.2012
1203
SSH Specific Discard t ext result : Do not store the requested web page. St ore lat est t ext result : Store the last result received from the query to the "Logs (Sensors)" directory (on the Master node, if in a cluster). File name: Result of Sensor [ID].txt. This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Chart Type
Inherited Settings
1204
27.11.2012
Maintenance Window
Maintenance End At
Dependency Type
27.11.2012
1205
Delay (Seconds)
1206
27.11.2012
More

Notifications
27.11.2012
1207
Others
133
section.
1208
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 142 SSH Script Sensor
6.8.142 SSH Script Sensor

The SSH Script sensor connects to a Linux/Unix system via Secure Shell (SSH) and executes a script file located on the target system. The sensor shows the execution time, and can show one value returned by the executable file or script (in one channel only). For details about the return value format please see the Applicat ion Programming Int erface (API) Definit ion 1871 . Note: For security reasons, the script file must be stored on the target system. Please make sure the script has executable rights. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor. For this sensor type credentials for Linux (SSH/WBEM) systems must be defined for the device you want to use the sensor on. Note: Not all Linux/Unix and Mac OS distributions can be supported by this sensor type. For a general introduction to SSH monitoring, please see Monit oring via SSH
1816
section.
Add Sensor
07.02.2013
1209
Sensor Set t ings Script Select a script file from the list. The drop down menu will list all script files available in the /var/prtg/scripts directory on the target Linux/Unix system. In order for the files to appear in this list, please store them into this directory. Please make sure the script has executable rights. In order for the sensor to show the expected values and sensor status, your files must use the right format for the returned values (in this case, exitcode:value:message to stdout). The exitcode will determine the sensor status. For detailed information on the expected return format and on how to build custom sensors, please see the API documentation (Applicat ion Programming Int erface (API) Definit ion 1871 ). There, find detailed information the the "Custom Sensors" tab. For an example script, please see More 1216 section below. Define what kind of values your script file gives back. Choose between: Int eger: An integer is expected as return value. If the script gives back a float, PRTG will display the value 0. Float : A float is expected as return value, with a dot (.) between pre-decimal position and decimal places. In this setting, the sensor will also display integer values unless they don't produce a buffer overflow. Count er: Your script returns an integer which increases. PRTG will show the difference between the values of two sensor scans. Note: A counter must return an integer; float is not supported here!
Value Type
Sensor Settings
1210
07.02.2013
Priority
Sensor Set t ings Script Shows the script that is executed with each sensor scan, as defined on sensor creation. 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 your script file catches command line parameters, you can define them here. Placeholders can be used as well. For a full list of all placeholders please see the API documentation (Applicat ion Programming Int erface (API) Definit ion 1871 ). Note: Please make sure you write the placeholders in quotes to ensure that they are working properly if their values contain blanks. Use single quotation marks ' ' with PowerShell scripts, and double quotes " " with all others. Please enter a string or leave the field empty. 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 422 section below. Please enter a string or leave the field empty. Shows the expected value type, chosen on sensor creation. 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. Note: The sensor cannot handle string values. 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.
Parameters
Mutex Name
Value Type
If Value Changes
07.02.2013
1211
Sensor Set t ings Trigger 'On Change' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
SSH Port
Result Handling
1212
07.02.2013
Chart Type
Inherited Settings
07.02.2013
1213
Maintenance Window
Maintenance End At
Dependency Type
1214
07.02.2013
Delay (Seconds)
07.02.2013
1215
More
Knowledge Base: Is there a shell script example for PRTG's SSH Script Sensor? http://www.paessler.com/knowledgebase/en/topic/39513 Information about custom scripts and executables Applicat ion Programming Int erface (API) Definit ion Addit ional Sensor Ty pes (Cust om Sensors)
1563 1871

1216
07.02.2013
Notifications
Others
133
section.
07.02.2013
1217
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 143 SSH Script Advanced Sensor
6.8.143 SSH Script Advanced Sensor

The SSH Script Advanced sensor connects to a Linux/Unix system via Secure Shell (SSH) and executes a script file located on the target system. The sensor shows the execution time, and can show values returned by the script in multiple channels. The return value of this sensor must be valid XML. For details about the return value format please see the Applicat ion Programming Int erface (API) Definit ion 1871 . Note: For security reasons, the script file must be stored on the target system. Please make sure the script has executable rights. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor. For this sensor type credentials for Linux (SSH/WBEM) systems must be defined for the device you want to use the sensor on. Note: Not all Linux/Unix and Mac OS distributions can be supported by this sensor type. For a general introduction to SSH monitoring, please see Monit oring via SSH
1816
section.

Add Sensor
1218
10.01.2013
Sensor Set t ings Script Select a script file from the list. The drop down menu will list all script files available in the /var/prtg/scriptsxml directory on the target Linux/Unix system. In order for the files to appear in this list, please store them into this directory. Please make sure the script has executable rights. In order for the sensor to show the expected values and sensor status, your files must return the expected XML format to standard output. Values and message must be embedded in the XML. For detailed information on the expected return format and on how to build custom sensors, please see the API documentation (Applicat ion Programming Int erface (API) Definit ion 1871 ). There, find detailed information the the "Custom Sensors" tab.
Sensor Settings
Tags
Priority
Sensor Set t ings Script Shows the script that is executed with each sensor scan, as defined on sensor creation. 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.
10.01.2013
1219
Sensor Set t ings Parameters If your script file catches command line parameters, you can define them here. Placeholders can be used as well. For a full list of all placeholders please see the API documentation (Applicat ion Programming Int erface (API) Definit ion 1871 ). Note: Please make sure you write the placeholders in quotes to ensure that they are working properly if their values contain blanks. Use single quotation marks ' ' with PowerShell scripts, and double quotes " " with all others. Please enter a string or leave the field empty. 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 422 section below. Please enter a string or leave the field empty. Define what will be done with the results the executable file gives back. Choose between: Discard EX E result : Do not store the requested web page. Writ e EX E result t o disk (Filename: "Result of Sensor [ID].t xt "): Store the last result received from the script to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Mutex Name
EXE Result
SSH Specific Connection Timeout (sec.) Define a timeout for the connection. This is the the time the sensor waits to establish a connection to the host. You should keep this value as low as possible. Define a timeout for the shell response. This is the time in seconds the sensor waits for the shell to return a response after it has sent its specific command (e.g. cat /proc/loadavg). Define which port this sensor will use for the SSH connection. Choose between: Inherit port number from parent device (default ): Use the port number as defined in the Credentials for Linux/Solaris/Mac OS (SSH/WBEM) Systems section of the device this sensor is created on. Ent er cust om port number: Do not use the port number from the parent device's settings, but define a different port number below.
SSH Port
1220
10.01.2013
SSH Specific Use Port Number This field is only visible if the custom port number setting is enabled above. Enter the port number this sensor will use for the SSH connection. Please enter an integer value. Define what will be done with the result of the query. Choose between: Discard t ext result : Do not store the requested web page. St ore lat est t ext result : Store the last result received from the query to the "Logs (Sensors)" directory (on the Master node, if in a cluster). File name: Result of Sensor [ID].txt. This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Result Handling
Chart Type
10.01.2013
1221
Inherited Settings
Maintenance Window
Maintenance End At
1222
10.01.2013
Delay (Seconds)
10.01.2013
1223
More
1224
10.01.2013
1563
1871

Notifications
Others
133
section.
10.01.2013
1225
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 144 SSH VMWare ESX(i) Disk Sensor
6.8.144 SSH VM Ware ESX(i) Disk Sensor

The SSH VMWare ESX(i) Disk sensor monitors free space on disks of a VMware ESX(i) system using Secure Shell (SSH). It shows the free disk space for different mounts and total, in total and percent values. For this sensor type credentials for Linux (SSH/WBEM) systems must be defined for the device you want to use the sensor on. Note: Not all Linux/Unix and Mac OS distributions can be supported by this sensor type. For a general introduction to SSH monitoring, please see Monit oring via SSH
1816
section.
Requirement: Root Credentials

For this sensor type credentials for Linux (SSH/WBEM) systems must be defined for the device you want to use the sensor on. In the parent device's Credent ials for Linux (SSH/WBEM) Sy st ems settings, please use the root user of your VMware host for authentication! See More 1231 section below. Please make sure you enable SSH on your VMware system!
Add Sensor
Sensor Settings
Tags
1226
27.11.2012
SSH Port
Result Handling
27.11.2012
1227
Chart Type
Inherited Settings
1228
27.11.2012
Maintenance Window
Maintenance End At
Dependency Type
27.11.2012
1229
Delay (Seconds)
1230
27.11.2012
More
Knowledge Base: How and Where Does PRTG Store its Data? http://www.paessler.com/knowledgebase/en/topic/463 Knowledge Base: Settings on ESXi 5 host when monitoring via SSH VMware ESX(i) Disk Sensor http://www.paessler.com/knowledgebase/en/topic/32603 Knowledge Base: Why do I need root credentials when monitoring VMware hosts via SSH? http://www.paessler.com/knowledgebase/en/topic/33763

Notifications
Others
133
section.
27.11.2012
1231
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 145 Syslog Receiver Sensor
6.8.145 Sy slog Receiver Sensor

The Syslog Receiver sensor receives and analyzes Syslog messages. It shows the number of new messages and warnings, per second. Note: This sensor type cannot be used in cluster mode. You can set it up on a local probe or remote probe only, not on a cluster probe.
Add Sensor
Sensor Settings
Tags
Priority
Sy slog Specific Listen on port Enter the port the sensor will listen on for Syslog messages. Usually port 514 is used. Please enter an integer value. We recommend using the default value.
1232
27.11.2012
Sy slog Specific Specify Sender Enter the sender which the Syslog messages are to come from. Only messages from a sender matching this string will be regarded. If you enter a value here, make sure your entry matches exactly the value for the sender in the Syslog message. Please enter a string or leave the field empty. Define what will be done when a message comes in. Choose between: Do not hing : Do not perform any action. Writ e message t o log and fire 'change' t rigger: Write an entry to the PRTG log file every time a message is received and fire one change trigger after each scanning interval, if messages were received during this interval. Note: Use with caution; this option may create a lot of log entries! Set Sensor to "Warning" Define which conditions will set the sensor's status to warning. Choose between: Never: The sensor's status will always show ok, no matter if messages are received or not. Depending on Severit y : The sensor's status will be set to warning for certain conditions in the Syslog messages. Depending on Cont ent : The sensor's status will be set to warning if the Syslog message does or does not a defined string. Emergency This option is only visible if warning depending on severity is enabled above. Set sensor to warning if a Syslog message contains an emergency message.Add a check mark symbol in front of the Warn on t his condit ion text to enable this option. This option is only visible if warning depending on severity is enabled above. Set sensor to warning if a Syslog message contains an alert message. Add a check mark symbol in front of the Warn on t his condit ion text to enable this option. This option is only visible if warning depending on severity is enabled above. Set sensor to warning if a Syslog message contains a critical message. Add a check mark symbol in front of the Warn on t his condit ion text to enable this option. This option is only visible if warning depending on severity is enabled above. Set sensor to warning if a Syslog message contains an error message. Add a check mark symbol in front of the Warn on t his condit ion text to enable this option.
When Message Comes In
Alert
Critical
Error
27.11.2012
1233
Sy slog Specific Warning This option is only visible if warning depending on severity is enabled above. Set sensor to warning if a Syslog message contains a warning message. Add a check mark symbol in front of the Warn on t his condit ion text to enable this option. This option is only visible if warning depending on severity is enabled above. Set sensor to warning if a Syslog message contains a notice message. Add a check mark symbol in front of the Warn on t his condit ion text to enable this option. This option is only visible if warning depending on severity is enabled above. Set sensor to warning if a Syslog message contains an informational message. Add a check mark symbol in front of the Warn on t his condit ion text to enable this option. This option is only visible if warning depending on content is enabled above. Define which string must be part of one or more Syslog message(s) received, in order for the sensor to show an Up status. If a message does not include this string, the sensor's status will be set to warning. Please enter a string or leave the field empty. This option is only visible if warning depending on content is enabled above. Define which string must not be part of one or more Syslog message(s) received, in order for the sensor to show an Up status. If a message does include this string, the sensor's status will be set to warning. Please enter a string or leave the field empty.
Notice
Informational
Message Must Include
Message Must Not Include
Chart Type
1234
27.11.2012
Inherited Settings
27.11.2012
1235
Maintenance End At
Dependency Type
1236
27.11.2012

27.11.2012
1237
Notifications
Others
133
section.
1238
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 146 System Health Sensor
6.8.146 Sy stem Health Sensor

The System Health sensor monitors internal PRTG parameters. It shows the status of the system. This sensor type is created automatically by PRTG and cannot be deleted. It checks various parameters of your PRTG system which can affect the quality of the monitoring results: Healt h: This index value sums up the probe state into a value between 100% (healthy) and 0% (failing). Frequent or repeated health values below 100% should be investigated. Available Memory : This channel shows the amount of free memory available on the system. This value should not fall below 500 MB. This way PRTG still can request resources during report generation, auto-discoveries, and other issues. Available Memory Percent : This channel shows the free memory available on the system in percent. CPU Load: This channel shows the current percentage CPU load. Extensive CPU load can lead to false, incomplete, and incorrect monitoring results. This value usually should stay below 50%. This sensor can be set up on a Probe Device only!
Sensor Settings
Tags
Priority
03.05.2013
1239
Chart Type
Inherited Settings
1240
03.05.2013
03.05.2013
1241

Notifications
Others
133
section.
1242
03.05.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 147 TFTP Sensor
6.8.147 TFTP Sensor

The TFTP sensor monitors a Trivial File Transfer Protocol (TFTP) server and checks if a certain file is available for download. It shows the availability.
Add Sensor
Sensor Settings
Tags
Priority
Sensor Specific Timeout (sec) Enter a timeout in seconds for the TFTP connect. If the reply takes longer than this value the request is aborted and an error message is triggered. Please enter an integer value. Enter the number of the port the TFTP service is running on. The sensor will try to connect to it. Please enter an integer value.
Port
27.11.2012
1243
Sensor Specific Filename Enter the name of the file the sensor will check. If this filename is not available on the server, the sensor's state will be set to down. Please enter a string.
Chart Type
Inherited Settings
1244
27.11.2012
Maintenance Window
Maintenance End At
Dependency Type
27.11.2012
1245
Delay (Seconds)
1246
27.11.2012
27.11.2012
1247

Notifications
Others
133
section.
1248
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 148 Traceroute Hop Count Sensor
6.8.148 Traceroute Hop Count Sensor

The Traceroute Hop Count sensor traces the number of hops needed from the probe system the sensor is running on to the IP Address/DNS Name defined in the sensor's parent device. It returns the number of hops. In case this number changes, you can additionally change the sensor's status. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Add Sensor
Sensor Settings
Tags
07.02.2013
1249
Sensor Set t ings If Route Changes Define what will be done in case the number of hops has changed since last check. Choose between: Ignore: Do not perform any action. Set sensor t o "Warning": Set the sensor to warning status. Set sensor t o "Error": Set the sensor to error status. Timeout (sec.) Define the timeout for the internal process. It will be killed if it has not returned a result after this time. Please enter an integer value.
Chart Type
1250
07.02.2013
Inherited Settings
Maintenance Window
Maintenance End At
07.02.2013
1251
Delay (Seconds)
1252
07.02.2013

Notifications
Others
133
section.
07.02.2013
1253
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 149 Virtuozzo Container Disk Sensor
6.8.149 Virtuozzo Container Disk Sensor

must be created on a Windows server parent device running Virtuozzo. For each container, it can show disk space used (kb-blocks), disk space soft and hard limit (kb-blocks), the number of inodes, and inodes soft and hard limit.
Add Sensor
Cont ainer Set t ings Container Select all Containers for which you want to create a sensor for disk monitoring. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
1254
07.02.2013
Cont ainer Set t ings Env ID Shows the unique ID of the container. 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. Shows the name of the monitored container. 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. Shows the operating system running on the container. 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. Shows a description for the container. 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. Define if the sensor will go into an error state if the container is powered off. Alarm when powered off: Set the sensor for a container to error if the container is powered off. Ignore powered off st at e: Only show zero values for a sensor when the monitored container is powered off. Do not set the sensor to error.
Name
OS
Description
Powered Off Containers
Chart Type
07.02.2013
1255
Inherited Settings
1256
07.02.2013
Maintenance End At
Dependency Type
07.02.2013
1257

1258
07.02.2013
Notifications
Others
133
section.
07.02.2013
1259
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 150 Virtuozzo Container Network Sensor
6.8.150 Virtuozzo Container Network Sensor

must be created on a Windows server parent device running Virtuozzo. For each container, it can show network usage as incoming and outgoing bytes, and the number of incoming and outgoing packets.
Add Sensor
Cont ainer Set t ings Container Select all Containers for which you want to create a sensor for disk monitoring. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
1260
07.02.2013
Cont ainer Set t ings Env ID Shows the unique ID of the container. 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. Shows the name of the monitored container. 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. Shows the operating system running on the container. 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. Shows a description for the container. 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. Define if the sensor will go into an error state if the container is powered off. Alarm when powered off: Set the sensor for a container to error if the container is powered off. Ignore powered off st at e: Only show zero values for a sensor when the monitored container is powered off. Do not set the sensor to error.
Name
OS
Description
Powered Off Containers
Chart Type
07.02.2013
1261
Scanning Int erval Interval The scanning interval of this sensor type cannot be inherited or changed. Due to internal restrictions of the Virtuozzo system, a fix value must be used.
Inherited Settings
1262
07.02.2013
Maintenance End At
Dependency Type
07.02.2013
1263

1264
07.02.2013
Notifications
Others
133
section.
07.02.2013
1265
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 151 VMware Host Hardware (WBEM) Sensor
6.8.151 VM ware Host Hardware (WBEM ) Sensor

The VMware Host Hardware sensor monitors hardware information of a ESX/ESXi server using Web-Based Enterprise Management (WBEM). It shows the current reading and health state. Note: The parent device must be a VMware ESX/ESXi server version 3.5, 4.0, 5.0, 5.1, or 5.5. For this sensor type credentials for Linux (SSH/WBEM) systems must be defined for the device you want to use the sensor on. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. If you select more than one elements 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:
ESX Server Element s ESX Element Select the hardware elements you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
1266
26.09.2013
Priority
ESX Server Element s Element Shows the ESX element 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. Define if the sensor will change it's status dependent on the health state reading. Choose between: Set sensor st at e aut omat ically t o 'Warning' or 'Down': Set the sensor to a Warning or Down status when the server returns respective values. The sensor will additionally change to a Down status if the connection to the server fails. Just report t he current reading, ignore Server Healt h Value: Never change the sensor's status dependent on the values returned by the server. The sensor will only change to a Down status if the connection to the server fails.
Automatic Sensor State
Chart Type
26.09.2013
1267
Inherited Settings
1268
26.09.2013
Maintenance End At
Dependency Type
26.09.2013
1269

1270
26.09.2013
Notifications
Others
133
section.
26.09.2013
1271
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 152 VMware Host Hardware Status (SOAP) Sensor
6.8.152 VM ware Host Hardware Status (SOAP) Sensor

The VMware Host Hardware Status (SOAP) sensor monitors the hardware status of a VMware host server using Simple Object Access Protocol (SOAP). It shows the total number of items in "Normal", "Warning," and "Alert" states, just as shown in the vSphere client. This sensor is intended to give you a general status overview for your host. Any states other than "Normal" will be reported in the sensor message. Note: This sensor only shows items that report an actual state; therefore you might see more "sensors" in your vSphere client than the number of states available in the channels of this PRTG sensor. Note: The parent device must be a VMware ESX/ESXi server version 3.5, 4.0, 5.0, 5.1, or 5.5. We recommend to not use this sensor type on your vCenter. Reliable hardware information can only be provided when this sensor is created on your physical host server as parent device. For this sensor type credentials for VMware servers must be defined for the device you want to use the sensor on. Please make sure you enter a user with sufficient access rights to obtain statistics (read-only should work). Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.

Settings on VMware Host System

If you set up this sensor on different probes (for example, when using remote probes 1888 or when running a cluster 76 setup), you might need to change the settings of your VMware host, so it accepts more incoming connections. Otherwise you might get connection timeouts when running plenty of VMware sensors with a short scanning interval. For details about this setting, please see More section below.
Add Sensor
1272
03.05.2013
VMware Host Set t ings Host Server Select the host server you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
Priority
VMware Host Set t ings MoID The Managed Object ID (MoID) of the host. 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.
03.05.2013
1273
Chart Type
Inherited Settings
1274
03.05.2013
Maintenance Window
Maintenance End At
Dependency Type
03.05.2013
1275
Delay (Seconds)
1276
03.05.2013
More
Knowledge Base: How can I increase the connection limit on VMware systems? http://www.paessler.com/knowledgebase/en/topic/30643

Notifications
Others
133
section.
03.05.2013
1277
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 153 VMware Host Performance (SOAP) Sensor
6.8.153 VM ware Host Performance (SOAP) Sensor

The VMware Host Performance (SOAP) sensor monitors a VMware host server using Simple Object Access Protocol (SOAP). It shows CPU (percent) and memory (absolute) usage, disk read and write speed, and network received and transmitted speed of a VMware host server. Note: The parent device must be a VMware ESX/ESXi server version 3.5, 4.0, 5.0, 5.1, or 5.5. For this sensor type credentials for VMware servers must be defined for the device you want to use the sensor on. Please make sure you enter a user with sufficient access rights to obtain statics (read-only should work). Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.


Add Sensor
Sensor Settings
1278
07.02.2013
Tags
Priority
Chart Type
07.02.2013
1279
Inherited Settings
Maintenance Window
Maintenance End At
1280
07.02.2013
Delay (Seconds)
07.02.2013
1281
More

Notifications
1282
07.02.2013
Others
133
section.
07.02.2013
1283
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 154 VMware Virtual Machine (SOAP) Sensor
6.8.154 VM ware Virtual M achine (SOAP) Sensor

The VMware Virtual Machine (SOAP) sensor monitors a virtual machine on a VMware host server using Simple Object Access Protocol (SOAP). It shows CPU (percent) and memory (absolute) usage, disk read and write speed, and network received and transmitted speed of a single virtual machine. Note: The parent device must be a VMware ESX/ESXi server version 3.5, 4.0, 5.0, 5.1, or 5.5; or a respective Virtual Center server. We recommend using Virtual Center as parent device, because this way PRTG will continue to monitor your virtual machines also when they change the physical host using vMotion. For this sensor type credentials for VMware servers must be defined for the device you want to use the sensor on. Please make sure you enter a user with sufficient access rights to obtain statics (read-only should work). Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.


Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. Note: PRTG requests a full list of all virtual machines configured on the device. Therefore, it may take a few seconds before the dialog is loaded.
1284
07.02.2013
If you select more than one virtual machine, 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:
Virt ual Machine Set t ings Virtual Machine You see a list of all virtual machines (VMs) available on the host server on this device, including the ones that are not running. All VMs are listed with name and the OS it is running on. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
Priority
07.02.2013
1285
Virt ual Machine Set t ings MoID Shows the Managed Object ID (MoID) of the virtual machine. 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. Choose how the sensor will react to a virtual machine that is powered off. Please choose between: Ignore "powered off" st at e (default ): The sensor will not change to a Down status if the virtual machine is powered off; it will report zero values instead. Alarm when VM is "powered off": The sensor will change to a Down 115 status if the virtual machine is powered off. Note: While in Down status, a sensor does not record any data in all of its channels.
Handling of "Powered off" VM
Chart Type
1286
07.02.2013
Inherited Settings
Maintenance Window
Maintenance End At
07.02.2013
1287
Delay (Seconds)
1288
07.02.2013
More

Notifications
07.02.2013
1289
Others
133
section.
1290
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 155 WBEM Custom Sensor
6.8.155 WBEM Custom Sensor

The WBEM Custom Sensor performs a custom query via Web-Based Enterprise Management (WBEM). It can show the total and channels received. For this sensor type credentials for Linux (SSH/WBEM) systems must be defined for the device you want to use the sensor on.
Add Sensor
Sensor Settings
Tags
Priority
Cust om Query Specific Namespace WBEM Query (WQL) Enter the namespace for the query. Default value is root /cimv2. Enter the WBEM Query that will be performed with every scanning interval. It has to be written in CQL/WQL.
27.11.2012
1291
Cust om Query Specific Numeric Format Define how the returned values will be handled as. Choose between: Int eger: The query returns integer values. Float : The query returns float values.
Chart Type
Inherited Settings
1292
27.11.2012
Maintenance Window
Maintenance End At
Dependency Type
27.11.2012
1293
Delay (Seconds)
1294
27.11.2012
27.11.2012
1295
More
For more tips and tricks regarding WQL scripts, please see the Paessler Knowledge Base and search for WQL. http://www.paessler.com/knowledgebase

Notifications
Others
133
section.
1296
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 156 Windows CPU Load Sensor
6.8.156 Windows CPU Load Sensor

The Windows CPU Load sensor monitors the CPU load on a computer via Windows Performance Counters or Windows Management Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent device. It shows the CPU usage in percent. Note: By default, this sensor type uses a hybrid approach, first trying to query data via Windows Performance Counters (which needs less system resources), and using Windows Management Instrumentation (WMI) as a fallback in case Performance Counters are not available. When running in fallback mode, the sensor will re-try to connect via Performance Counters after 24 hours. The default behavior can be changed in the Windows Compat ibilit y Opt ions of the parent device's settings 268 this sensor is created on. Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813



19.07.2013
1297
Add Sensor
Sensor Settings
Tags
Priority
WMI Alt ernat ive Query Errors and invalid data This is an extended help field only. PRTG's WMI sensors are equipped with the most efficient and accurate WMI queries. However, Microsoft has changed (and will continue to do that in the future) some WMI classes over the various Windows/ ServicePack/patchlevel versions, resulting in errors like "class not valid" or "invalid data". Wherever possible PRTG features an alternative query that might work in your specific circumstances. When you keep getting errors for this sensor please try enabling the alternative query method below. Choose the method PRTG uses to query via WMI. For compatibility reasons, an alternative query method can be enabled. We recommend using the default value. You can choose between:
Alternative query
1298
19.07.2013
WMI Alt ernat ive Query use default : Use PRTG's standard method to query WMI. This is the best setting in most cases. use alt ernat ive: Use an alternative method to query WMI. If you keep getting errors, please try this setting.
Chart Type
Inherited Settings
19.07.2013
1299
Maintenance Window
Maintenance End At
Dependency Type
1300
19.07.2013
Delay (Seconds)
19.07.2013
1301

Notifications
Others
133
section.
1302
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 157 Windows IIS 6.0 SMTP Received Sensor
6.8.157 Windows IIS 6.0 SM TP Received Sensor

The Windows IIS 6.0 SMTP Receiver Sensor monitors Microsoft's Internet Information Services regarding the number of received emails for an IIS 6.0 SMTP service (Exchange 2003) using Windows Performance Counters or Windows Management Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent device. It shows the number of messages, the bytes, and the number of retries, per second for received messages. Note: This service is not used by Exchange Server 2007 and higher. Exchange Server 2007 uses its own SMTP stack implemented in the Microsoft Exchange Transport service. Note: By default, this sensor type uses a hybrid approach, first trying to query data via Windows Performance Counters (which needs less system resources), and using Windows Management Instrumentation (WMI) as a fallback in case Performance Counters are not available. When running in fallback mode, the sensor will re-try to connect via Performance Counters after 24 hours. The default behavior can be changed in the Windows Compat ibilit y Opt ions of the parent device's settings 268 this sensor is created on. Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813



In order for this sensor to work with Windows Performance Counters, please make sure the Remote Registry Windows service is running on the target computer. If you fail to do so, a connection via Performance Counters will not be possible. However, WMI connections may still work.
19.07.2013
1303
To enable the service, please log in to the respective computer and open the services manager (e.g. via services.msc). In the list, find the respective service and set its Start Type to Automatic.
Add Sensor
Sensor Settings
Tags
Priority
Chart Type
1304
19.07.2013
Inherited Settings
19.07.2013
1305
Maintenance End At
Dependency Type
1306
19.07.2013
19.07.2013
1307

Notifications
Others
133
section.
1308
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 158 Windows IIS 6.0 SMTP Sent Sensor
6.8.158 Windows IIS 6.0 SM TP Sent Sensor

The Windows IIS 6.0 SMTP Sent Sensor monitors Microsoft's Internet Information Services regarding the number of sent emails for an IIS 6.0 SMTP service (Exchange 2003) using Windows Performance Counters or Windows Management Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent device. It shows the number of messages, the bytes, and the number of retries, per second for sent messages. Note: This service is not used by Exchange Server 2007 and higher. Exchange Server 2007 uses its own SMTP stack implemented in the Microsoft Exchange Transport service. Note: By default, this sensor type uses a hybrid approach, first trying to query data via Windows Performance Counters (which needs less system resources), and using Windows Management Instrumentation (WMI) as a fallback in case Performance Counters are not available. When running in fallback mode, the sensor will re-try to connect via Performance Counters after 24 hours. The default behavior can be changed in the Windows Compat ibilit y Opt ions of the parent device's settings 268 this sensor is created on. Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813



19.07.2013
1309
Add Sensor
Sensor Settings
Tags
Priority
Chart Type
1310
19.07.2013
Inherited Settings
19.07.2013
1311
Maintenance End At
Dependency Type
1312
19.07.2013
19.07.2013
1313

Notifications
Others
133
section.
1314
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 159 Windows IIS Application Sensor
6.8.159 Windows IIS Application Sensor

The Windows IIS Application sensor monitors a Microsoft Internet Information Services server using Windows Performance Counters or Windows Management Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent device. It can also monitor applications that use IIS, such as Microsoft SharePoint or Microsoft Reporting Services (SSRS). The sensor shows bytes sent and received as well as post, get, and CGI requests, not found errors, anonymous and known users, and received and sent files, in number/second. Note: By default, this sensor type uses a hybrid approach, first trying to query data via Windows Performance Counters (which needs less system resources), and using Windows Management Instrumentation (WMI) as a fallback in case Performance Counters are not available. When running in fallback mode, the sensor will re-try to connect via Performance Counters after 24 hours. The default behavior can be changed in the Windows Compat ibilit y Opt ions of the parent device's settings 268 this sensor is created on. Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813



19.07.2013
1315
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. If you select more than one web service instance, 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:
WMI Int ernet Informat ion Services Specify Instance You see a list of all web service instances running on this device. There is also a "_Total" instance available. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
1316
19.07.2013
WMI Int ernet Informat ion Services Instance The name of the web services instance that is 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.
Chart Type
19.07.2013
1317
Inherited Settings
Maintenance Window
Maintenance End At
1318
19.07.2013
Delay (Seconds)
19.07.2013
1319
1320
19.07.2013

Notifications
Others
133
section.
19.07.2013
1321
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 160 Windows Last Update Sensor
6.8.160 Windows Last Update Sensor

The Windows Last Update sensor reads the number of days since last Windows update from its parent device and returns the number of days. Use threshold triggers 1573 to get notified in case this number breaches a certain value. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.


Requirement: Enable Remote Registry Service

In order for this sensor to work, you need to enable the RemoteRegistry "Remote Registry" Windows service on the target machine. To do so, please log in to this machine and open the services manager (e.g. start services.msc). In the list of services, find the Remot e Regist ry service and set its Start Type to Automatic.
Add Sensor
1322
07.02.2013
Sensor Settings
Tags
Priority
Sensor Set t ings Timeout (sec.) Define the timeout for the internal process. It will be killed if it has not returned a result after this time. Please enter an integer value. Define what will 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' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
If Value Changes
07.02.2013
1323
Chart Type
Inherited Settings
1324
07.02.2013
Maintenance Window
Maintenance End At
Dependency Type
07.02.2013
1325
Delay (Seconds)
1326
07.02.2013
More
Knowledge Base: Fixing a Protocol Error Appearing With Windows Last Update Sensor http://www.paessler.com/knowledgebase/en/topic/41113

Notifications
Others
133
section.
07.02.2013
1327
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 161 Windows Logged In Users Sensor
6.8.161 Windows Logged In Users Sensor

The Windows Logged In Users sensor queries the number of users logged in to a Windows installation on the parent device. It returns the total number. You can optionally filter for certain user names. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.


Add Sensor
Sensor Settings
1328
07.02.2013
Tags
Priority
Sensor Set t ings User Filter (optional) To filter the value returned by certain user names, define them here. Enter a comma separated list of user names, or leave the field empty. Define how the user names entered above will be used. Choose between: Do not count users list ed in "User Filt er": Exclude the users entered above from counting and only count other uses. Only count users list ed in "User Filt er": Ignore all other users and only count user names from the list entered above. If Value Changes Define what will 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' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Processing of Users in "User Filter"
07.02.2013
1329
Chart Type
Inherited Settings
1330
07.02.2013
Maintenance Window
Maintenance End At
Dependency Type
07.02.2013
1331
Delay (Seconds)
1332
07.02.2013

Notifications
Others
133
section.
07.02.2013
1333
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 162 Windows MSMQ Queue Length Sensor
6.8.162 Windows M SM Q Queue Length Sensor

The Windows MSMQ Queue Length sensor reads the number of messages in a Microsoft Message Queue of the parent device. It gives back the total number. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.


Requirement: Message Queuing Service

In order for this sensor to work, the MSMQ "Message Queuing" service must be started both on the target system and on the computer running the PRTG probe: Either on the local system (on every node, if on a cluster probe), or on the system running the remote probe 1888 . Additionally, the MSMQ "Message Queuing" service must also be started 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. Depending on your Windows version you may first need to install the Microsoft Message Queue (MSMQ) Server.
1334
07.02.2013
Note: When installing Microsoft Message Queue (MSMQ) Server, make sure you install it including the Directory Service. Depending on your Windows installation this might have different names, such as MSMQ Active Directory Domain Service Integration Directory Service Integration Active Directory Integration For details, please see More section below.
1339
Add Sensor
Sensor Set t ings Message Queue You see a list showing the names of all message queues found on the target device. If there are no message queues available, you will see a corresponding message. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. Note: Sub-queues are not supported by this sensor.
Sensor Settings
07.02.2013
1335
Priority
Sensor Set t ings Message Queue Shows the name of the task monitored by this sensor. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page: Optionally define an age in minutes the message has to be old. If set, messages younger than this will not be regarded. If you leave this field blank, the sensor will not check for the message age. Please enter an integer value or leave the field empty. Define what will be done in case the value of this sensor changes. You can choose between: Ignore changes: No action will be taken on change. Trigger 'change' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Min. Message Age
If Value Changes
Chart Type
1336
07.02.2013
Inherited Settings
07.02.2013
1337
Maintenance End At
Dependency Type
1338
07.02.2013
More
Knowledge Base: How do I activate Message Queuing in my Windows installation? http://www.paessler.com/knowledgebase/en/topic/25963
07.02.2013
1339

Notifications
Others
133
section.
1340
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 163 Windows Network Card Sensor
6.8.163 Windows Network Card Sensor

The Windows Network Card sensor monitors bandwidth usage and traffic of a network interface using Windows Performance Counters or Windows Management Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent device. Note: By default, this sensor type uses a hybrid approach, first trying to query data via Windows Performance Counters (which needs less system resources), and using Windows Management Instrumentation (WMI) as a fallback in case Performance Counters are not available. When running in fallback mode, the sensor will re-try to connect via Performance Counters after 24 hours. The default behavior can be changed in the Windows Compat ibilit y Opt ions of the parent device's settings 268 this sensor is created on. Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813



19.07.2013
1341
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. For devices with multiple network cards 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: Specify network interface Select the network card(s) you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
Priority
1342
19.07.2013
Selected Interface
Shows the name of the network card that this sensor is monitoring. 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.
Chart Type
Inherited Settings
19.07.2013
1343
Maintenance Window
Maintenance End At
Dependency Type
1344
19.07.2013
Delay (Seconds)
19.07.2013
1345
1346
19.07.2013

Notifications
Others
133
section.
19.07.2013
1347
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 164 Windows Pagefile Sensor
6.8.164 Windows Pagefile Sensor

The Windows Pagefile sensor monitors the Windows pagefile usage via Windows Performance Counters or Windows Management Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent device. It shows the usage in percent. Note: This sensor does not work with Windows 2000, because the respective WMI class does not exist on this operating system! Note: By default, this sensor type uses a hybrid approach, first trying to query data via Windows Performance Counters (which needs less system resources), and using Windows Management Instrumentation (WMI) as a fallback in case Performance Counters are not available. When running in fallback mode, the sensor will re-try to connect via Performance Counters after 24 hours. The default behavior can be changed in the Windows Compat ibilit y Opt ions of the parent device's settings 268 this sensor is created on. Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813



1348
19.07.2013
Add Sensor
Sensor Settings
Tags
Priority
Chart Type
19.07.2013
1349
Inherited Settings
1350
19.07.2013
Maintenance End At
Dependency Type
19.07.2013
1351

1352
19.07.2013
Notifications
Others
133
section.
19.07.2013
1353
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 165 Windows Physical Disk Sensor
6.8.165 Windows Phy sical Disk Sensor

The Windows Physical Disk sensor monitors parameters of a physical disk of a Windows device using Windows Performance Counters or Windows Management Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent device. It shows accumulated disk read/write time and bytes, queue, split IO, etc. on physical disks. Note: By default, this sensor type uses a hybrid approach, first trying to query data via Windows Performance Counters (which needs less system resources), and using Windows Management Instrumentation (WMI) as a fallback in case Performance Counters are not available. When running in fallback mode, the sensor will re-try to connect via Performance Counters after 24 hours. The default behavior can be changed in the Windows Compat ibilit y Opt ions of the parent device's settings 268 this sensor is created on. Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813



1354
19.07.2013
Add Sensor
WMI Phy sical Disk Specific Physical Disks You see a list showing the Name of the counters you can monitor as well as the Inst ance, i.e. the respective logical disk (or '_Total'). If there are no logical disks available, you will see a corresponding message. From the list, choose all Name/Inst ance combinations you want to monitor by adding a check mark in front of the respective line (for example, choose '% Disk Read Time for C:'). For each selection one sensor will be created using the defined settings.
Sensor Settings
Tags
Priority
19.07.2013
1355
Sensor Set t ings Counter Instance WMI Class Datafield Basefield Frequencyfield Countertype Sensor Result Define what will be done with the result of the sensor. Choose between: Discard sensor result : Do not store the results. Writ e sensor result t o disk (Filename: "Result of Sensor [ID].t xt "): Store the last result received to the "Logs (System)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section. These fields show the parameters that are used to query data for this sensor from the target 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.
Chart Type
1356
19.07.2013
Inherited Settings
Maintenance Window
19.07.2013
1357
Maintenance End At
Dependency Type
Delay (Seconds)
1358
19.07.2013
19.07.2013
1359

Notifications
Others
133
section.
1360
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 166 Windows Print Queue Sensor
6.8.166 Windows Print Queue Sensor

The Windows Print Queue sensor reads the print queue on its parent device and gives back the number of jobs in the print queue. It can monitor queues for all printers that are installed locally. For example, you can use this sensor to monitor all print queues on your Windows print server. Additionally, this sensor can change to a Warning status if there is a printer problem, such as out of paper, etc. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.


Requirement: Print Spooler Service

In order for this sensor to work, the Spooler "Print Spooler" service must be started 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.
13.06.2013
1361
Add Sensor
Sensor Set t ings Print Queue You see a list showing the names of all print queues found on the target device. If there are no print queues available, you will see a corresponding message. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. Note: If a printer name changes after you created a sensor for its queue, please add the sensor anew.
Sensor Settings
Tags
Priority
1362
13.06.2013
Sensor Set t ings Print Queue Name Shows the name of the task monitored by this sensor. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page: Optionally define the age in sedonds. If set, jobs younger than this will not be regarded. If you leave this field blank, the sensor will not check for the print job age. Please enter an integer value or leave the field empty. Define if the sensor will change to a Warning status in case a printer reports a problem. Choose between: No Yes
Min. Print Job Age (sec.)
Set to Warning on Problem Reported
Chart Type
13.06.2013
1363
Inherited Settings
Maintenance Window
Maintenance End At
1364
13.06.2013
Delay (Seconds)
13.06.2013
1365

Notifications
Others
133
section.
1366
13.06.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 167 Windows Registry Sensor
6.8.167 Windows Registry Sensor

The Windows Registry sensor reads a string value from the Windows registry and can process the result using a keyword search. The value is shown in the sensor's last message field. Note: Only REG_SZ values can be processed with this sensor.

In order for this sensor to work, please make sure the RemoteRegistry "Remote Registry" Windows service is running on both the computer running the PRTG probe and the target machine. 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.

For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Please make sure that the Windows user account running the PRTGProbeService "PRTG Probe Service" on the computer running the PRTG probe has access to the registry of the remote computer (by default, this is the probe computer's local Windows "system" account). Additionally, the computer running the PRTG probe and the target computer must be member of the same Windows local domain. Note: You cannot perform a remote registry call with a Windows user account for which no password is defined.
Add Sensor
Sensor Settings
19.07.2013
1367
Tags
Priority
Regist ry Set t ings Root Select the root key of the registry entry you want to monitor. Choose between: HKEY_CLASSES_ROOT HKEY_CURRENT_USER HKEY_LOCAL_MACHINE HKEY_USERS HKEY_PERFORMANCE_DATA HKEY_CURRENT_CONFIG HKEY_DYN_DATA Key Name Enter the path of the key you want to monitor. Enter the full path after the root, each subkey divided by a backslash. For example, enter Software\Microsoft\Windows\CurrentVersion Enter the name of the value you want to monitor. For example, enter ProductId to read the product ID of the target computer's Windows installation. Define how the provided key name will be looked up. This is relevant for some registry keys only, for example those containing the Wow6432Node subkey. Choose between: Use 32-bit regist ry view: The key provided above is copied from the 32-bit registry editor.
Value Name
64-Bit Selection
1368
19.07.2013
Regist ry Set t ings Use 64-bit regist ry view: The key provided above is copied from the 64-bit registry editor. For more information, see the More Value
1373
section below.
Select if the returned result will be further processed. Choose between: Ignore Value: Do not perform any more keyword checks. The registry value is shown in the sensor last message field only. Process Text : Use the returned value to perform keyword checks. Select below.
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 key word check (posit ive): Check if a certain keyword exists in the received value. Define below.
Text Must Include
This setting is only visible if keyword check is activated above. Enter a search string that must be contained in the returned value. 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 1886 section.
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 key word check (negat ive): Check if a certain keyword does not exist in the received value. Define below.
Text Must Not Include
This setting is only visible if keyword check is activated above. Enter a search string that must not be contained in the returned value. Define the method you want to provide the search string with. Choose between:
19.07.2013
1369
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 key word check (posit ive): Check if a certain keyword exists in the received value. Define below. Plain Text : Search for a simple string. Regular Expression: Search using a regular expression. For more details, see Regular Expressions 1886 section.
Chart Type
Inherited Settings
1370
19.07.2013
Maintenance Window
Maintenance End At
Dependency Type
19.07.2013
1371
Delay (Seconds)
1372
19.07.2013
More
How do I discern 32-bit registry values vs. 64-bit registry values? http://www.paessler.com/knowledgebase/en/topic/25513

Notifications
19.07.2013
1373
Others
133
section.
1374
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 168 Windows Scheduled Task Sensor
6.8.168 Windows Scheduled Task Sensor

The Windows Scheduled Task sensor returns the number of minutes since the last run of the specified task as well as the exit code. If a task was never run or if a defined Exit code does not match, the sensor shows an error. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.


In order for this sensor to work, please make sure the RemoteRegistry "Remote Registry" Windows service is running on both the computer running the PRTG probe and the target machine. 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.

Requirement: Monitored Systems

Note: We recommend running the PRTG probe on Windows 2008 R2 or later.
07.02.2013
1375
Microsoft implemented two versions of scheduled task, V1 and V2. Windows 2000, Windows XP, and Windows Server 2003 create scheduled tasks V1 by default. Later Windows versions can create and read both versions. If the system running the PRTG probe (either on the core server or a remote probe) runs on one of these early Windows versions, you will not be able to monitor scheduled tasks of V2. In this case, please create the tasks on the monitored machines compatible with "Windows Server 2003, Windows XP, or Windows 2000" if there is a newer Windows version installed. If the system running the PRTG probe (either on the core server or a remote probe) runs on Windows Vista or later, you will be able to monitor scheduled tasks of both V1 and V2 (i.e. from all Windows versions).
Add Sensor
Sensor Set t ings Task Name You see a list showing the names of all tasks found in the Windows Task Scheduler on the target device. If there are no scheduled tasks, you will see a corresponding message. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.. Note: If a task name changes after you created a sensor for it, please add the sensor anew.
Sensor Settings
1376
07.02.2013
Priority
Sensor Set t ings Name Shows the name of the task 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. 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' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
If Value Changes
Chart Type
07.02.2013
1377
Inherited Settings
1378
07.02.2013
Maintenance End At
Dependency Type
07.02.2013
1379
1380
07.02.2013

Notifications
Others
133
section.
07.02.2013
1381
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 169 Windows System Uptime Sensor
6.8.169 Windows Sy stem Uptime Sensor

The Windows System Uptime sensor monitors uptime of a Windows system using Windows Performance Counters or Windows Management Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent device. It returns the total uptime. Note: By default, this sensor type uses a hybrid approach, first trying to query data via Windows Performance Counters (which needs less system resources), and using Windows Management Instrumentation (WMI) as a fallback in case Performance Counters are not available. When running in fallback mode, the sensor will re-try to connect via Performance Counters after 24 hours. The default behavior can be changed in the Windows Compat ibilit y Opt ions of the parent device's settings 268 this sensor is created on. Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813



1382
27.11.2012
Add Sensor
Sensor Settings
Tags
Priority
Chart Type
27.11.2012
1383
Inherited Settings
1384
27.11.2012
Maintenance End At
Dependency Type
27.11.2012
1385

1386
27.11.2012
Notifications
Others
133
section.
27.11.2012
1387
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 170 Windows Updates Status (Powershell) Sensor
6.8.170 Windows Updates Status (Powershell) Sensor

The Windows Updates Status (Powershell) sensor monitors the status of Windows updates on a computer and counts the available and installed Windows updateseither from Microsoft or from the local WSUS server. This sensor can show the time elapsed since the last update, as well as the following numbers: Installed Windows updates Missing Windows updates Installed security updates with low, moderate, important, and critical priority Missing security updates with low, moderate, important, and critical priority Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on.

Requirement: Remote PowerShell

The Windows Updates Status (Powershell) sensor uses PowerShell commands. In order to monitor devices with this sensor, Remot e PowerShell access has to be enabled on the target computer. For detailed information, please see More 549 section below.
Add Sensor
Sensor Settings
1388
08.10.2013
Tags
Priority
Chart Type
08.10.2013
1389
Inherited Settings
Maintenance Window
Maintenance End At
1390
08.10.2013
Delay (Seconds)
08.10.2013
1391
More
Knowledge Base: How do I enable and use remote commands in Windows PowerShell? http://www.paessler.com/knowledgebase/en/topic/44453

Notifications
1392
08.10.2013
Others
133
section.
08.10.2013
1393
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 171 WMI Custom Sensor
6.8.171 WM I Custom Sensor

The WMI Custom Sensor performs a custom query via Windows Management Instrumentation (WMI). Note: Your Windows Management Instrumentation Query Language (WQL) query code must be stored in a file on the system of the probe the sensor is created on: If used on a remote probe, the file must be stored on the system running the remote probe. In a cluster setup, please copy the file to every cluster node. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
Cust om Query Specific Channel Name Enter a name for the channel in which the received data will be presented. The name will be displayed in graphs and tables. Please enter a string. You can change the name later in the sensor's channel settings 1566 . Select a file that will be used for this sensor from the drop down menu. It will be executed with every scanning interval. The menu contains WQL scripts from the \Cust om Sensors\WMI WQL script s sub folder of your PRTG installation. Please store your script there. If used on a remote probe, the file must be stored on the system running the remote probe. If used on a cluster probe, you must store the file on all servers running a cluster node! For more information on how to find this path, please see Dat a St orage 1912 section. Note: Your query must return an integer or float value. Strings are not supported!
WQL File
1394
07.02.2013
Sensor Settings
Tags
Priority
Cust om Query Specific Namespace WQL File Enter the namespace for the query. Select a file that will be used for this sensor from the drop down menu. It will be executed with every scanning interval. The menu contains WQL scripts from the \Cust om Sensors\WMI WQL script s sub folder of your PRTG installation. Please store your script there. If used on a remote probe, the file must be stored on the system running the remote probe. If used on a cluster probe, you must store the file on all servers running a cluster node! For more information on how to find this path, please see Dat a St orage 1912 section. Note: Your query must return an integer or float value. Strings are not supported! In your WQL script, you can use up to three placeholders that you can assign a value to using this field. Please enter a string for variable <#PH1> or leave the field empty. In your WQL script, you can use up to three placeholders that you can assign a value to using this field. Please enter a string for variable <#PH2> or leave the field empty.
Placeholder <#PH1>
Placeholder <#PH2>
07.02.2013
1395
Cust om Query Specific Placeholder <#PH3> In your WQL script, you can use up to three placeholders that you can assign a value to using this field. Please enter a string for variable <#PH3> or leave the field empty. Define what shall be done in case the value of this sensor changes. You can choose between: Ignore changes (default ): No action will be taken on change. Trigger 'On Change' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes. Channel Name Enter a name for the channel in which the received data will be presented. The name will be displayed in graphs and tables. Please enter a string. Enter a unit for the data that will be received by your script. This is for displaying purposes only. The unit will be displayed in graphs and tables. Please enter a string. Define with which value the received values will be multiplied by. By default, this is set to 1 in order to not change the received values. Please enter an integer, a decimal value, or leave the field empty. Define with which value the received values will be divided by. By default, this is set to 1 in order to not change the received values. Please enter an integer, a decimal value, or leave the field empty.
If Value Changes
Unit String
Multiplication
Division
Chart Type
1396
07.02.2013
Inherited Settings
07.02.2013
1397
Maintenance End At
Dependency Type
1398
07.02.2013
07.02.2013
1399
More
Addit ional Sensor Ty pes (Cust om Sensors)
1563
Knowledge Base: How do I properly configure a WMI custom sensor? http://www.paessler.com/knowledgebase/en/topic/163

Notifications
Others
133
section.
1400
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 172 WMI Custom String Sensor
6.8.172 WM I Custom String Sensor

The WMI Custom String sensor performs a custom string query via Windows Management Instrumentation (WMI). Note: Your Windows Management Instrumentation Query Language (WQL) query code must be stored in a file on the system of the probe the sensor is created on: If used on a remote probe, the file must be stored on the system running the remote probe. In a cluster setup, please copy the file to every cluster node. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
Cust om Query Specific Channel Name Enter a name for the channel in which the received data will be presented. The name will be displayed in graphs and tables. Please enter a string. You can change the name later in the sensor's channel settings 1566 . Select a file that will be used for this sensor from the drop down menu. It will be executed with every scanning interval. The menu contains WQL scripts from the \Cust om Sensors\WMI WQL script s sub folder of your PRTG installation. Please store your script there. If used on a remote probe, the file must be stored on the system running the remote probe. If used on a cluster probe, you must store the file on all servers running a cluster node! For more information on how to find this path, please see Dat a St orage 1912 section.
WQL File
08.10.2013
1401
Sensor Settings
Tags
Priority
Cust om Query Specific Namespace WQL File Enter the namespace for the query. Shows the name of the file that this sensor is using. 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. In your WQL script, you can use up to three placeholders that you can assign a value to using this field. Please enter a string for variable <#PH1> or leave the field empty. In your WQL script, you can use up to three placeholders that you can assign a value to using this field. Please enter a string for variable <#PH2> or leave the field empty. In your WQL script, you can use up to three placeholders that you can assign a value to using this field. Please enter a string for variable <#PH3> or leave the field empty.
Placeholder <#PH1>
Placeholder <#PH2>
Placeholder <#PH3>
1402
08.10.2013
Cust om Query Specific If Value Changes Define what shall be done in case the value of this sensor changes. You can choose between: Ignore changes (default ): No action will be taken on change. Trigger 'On Change' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes. Channel Name Enter a name for the channel in which the received data will be presented. The name will be displayed in graphs and tables. Please enter a string. Enter a unit for the data that will be received by your script. This is for displaying purposes only. The unit will be displayed in graphs and tables. Please enter a string. Define with which value the received values will be multiplied by. By default, this is set to 1 in order to not change the received values. Please enter an integer, a decimal value, or leave the field empty. Define with which value the received values will be divided by. By default, this is set to 1 in order to not change the received values. Please enter an integer, a decimal value, or leave the field empty.
Unit String
Multiplication
Division
Response Must Include Define which string must be part of the data that is received form the WMI object. You can either enter plain text or a Regular Expression 1886 . If the data does not include the search pattern, the sensor will be set to an error state. Please enter a string or leave the field empty. Response Must Not Include Define which string must not be part of the data that is received form the WMI object. You can either enter plain text or a Regular Expression 1886 . If the data does include the search pattern, the sensor will be set to an error state. Please enter a string or leave the field empty. 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.
08.10.2013
1403
Cust om Query Specific Regular Expression: Treat the search pattern as a Regular Expression 1886 . Maximum Length of String Define the maximum length of the string that will be received from the WMI object. 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. Define if you want to filter out a numeric value from the string received from the WMI object. You can convert this into a float value, in order to use it with channel limits (see Sensor Channels Set t ings 1566 ). No ext ract ion: Do not extract a float value. Use the result as a string value. Ext ract a numeric value using a regular expression: Use a regular expression to identify a numeric value in the string and convert it to a float value. Define below. See also the example below. Regular Expression
Extract Number Using Regular Expression
1408
This setting is only visible if number extraction is enabled above. Enter a Regular Expression 1886 to identify the numeric value you want to extract from the string returned by the WMI object. You can use capturing groups here. Make sure the expression returns numbers only (including decimal and thousands separators). The result will be further refined by the settings below. This setting is only visible if number extraction is enabled above. If your regular expression uses capturing groups, please specify which one will be used to capture the number. Please enter an integer value or leave the field empty. This setting is only visible if number extraction is enabled above. Define which character is used as decimal separator for the number extracted above. Please enter a string or leave the field empty. This setting is only visible if number extraction is enabled above. Define which character is used as thousands separator for the number extracted above. Please enter a string or leave the field empty. Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results.
Index of Capturing Group
Decimal Separator
Thousands Separator
Sensor Result
1404
08.10.2013
Cust om Query Specific Writ e sensor result t o disk (Filename: "Result of Sensor (ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Chart Type
Inherited Settings
08.10.2013
1405
Maintenance Window
Maintenance End At
Dependency Type
1406
08.10.2013
Delay (Seconds)
08.10.2013
1407
Example: Number Extraction with Regular Expression

If you want to extract a number in the response string using a regular expression, please note that the index for captures in this sensor is based on 1 (not on 0). Furthermore, capturing groups are not created automatically. The example below will illustrate this issue. Consider the following string as returned by a request for CPU usage:
5 Sec (3.49%), 1 Min (3.555%), 5 Min (3.90%)
Assuming you would like to filter for the number 3.555, i.e., the percentage in the second parentheses. Then enter the following regex in the Regular Expression field:
(\d+\.\d+).*(\d+\.\d+).*(\d+\.\d+)
As Index of Capt uring Group enter 3. This will extract the desired number 3.555.
1408
08.10.2013
The index has to be 3 in this case because the capturing groups here are the following: Group 1 contains "3.49%), 1 Min (3.555), 5 Min (3.90" Group 2 contains "3.49" Group 3 contains "3.555" Group 4 contains "3.90" Please keep in mind this note about index and capturing groups when using number extraction.

Notifications
Others
133
section.
08.10.2013
1409
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 173 WMI Event Log Sensor
6.8.173 WM I Event Log Sensor

The WMI Event Log sensor monitors a specific Windows log file using Windows Management Instrumentation (WMI). It shows the number of new records (volume), the number of new records per second (speed), and it returns the last message in the sensor status. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. If you select more than one log file, 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:
WMI Event log Monit or Log file The Windows event log provides several different log files. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
1410
07.02.2013
Tags
Priority
WMI Event Log Monit or Log file Shows the Windows log file that this sensor will monitor. 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.
Filt er Event Log Ent ries 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 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.
Filter by ID
07.02.2013
1411
Filt er Event Log Ent ries On: Enable filtering by event ID. 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 all received events for a certain event category. If enabled, only messages matching the defined value will be considered by the sensor. Choose between: 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 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 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.
Filter by Category
Filter by Event User
Filter by Event Computer
1412
07.02.2013
Filt er Event Log Ent ries 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 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. 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.
Filter by Event Message
Chart Type
07.02.2013
1413
Inherited Settings
Maintenance Window
Maintenance End At
1414
07.02.2013
Delay (Seconds)
07.02.2013
1415

Notifications
Others
133
section.
1416
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 174 WMI Exchange Server Sensor
6.8.174 WM I Exchange Server Sensor

The WMI Exchange Server sensor monitors a Microsoft Exchange Server 2003, 2007, or 2010 using Windows Management Instrumentation (WMI). It can show information about the queue, delivery time, latency, users, etc. Note: Existing former "WMI Exchange Server 2003/2007 Sensors" from previous PRTG versions will continue to monitor your Exchange server in PRTG 9, but newly added Exchange server sensors will be of the "WMI Exchange Server Sensor" type which is able to monitor Exchange servers regardless of their version. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor an Exchange Server, PRTG will create one sensor for each performance counter you choose. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
Exchange Server Dat a Readings Accessible Using WMI Performance Counter You see a list of data values the sensor can monitor on your Exchange server. The available options depend on your Exchange server configuration. PRTG shows all possible performance counters with name and instance description (if available). Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. You might be able to select aspects regarding: SMTP Server: Queue Lengths
13.06.2013
1417
Exchange Server Dat a Readings Accessible Using WMI MSExchangeIS Mailbox: Queue Sizes, Delivery Times, Operations, Messages MSExchangeIS Public : Queue Sizes, Delivery Times, Operations, Messages MSExchangeIS : Packets, Operations, Clients, Latency, Requests, Users MS Exchange RPC Client Access: Active User Count, User Count, Connection Count MS Exchange OWA: Current Unique Users, Average Response Time
Sensor Settings
Tags
Priority
Sensor Set t ings Counter Instance These fields show the parameters that are used to query data for this sensor from the target 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.
1418
13.06.2013
Sensor Set t ings WMI Class Datafield Basefield Frequencyfield Countertype Sensor Result Define what will be done with the result of the sensor. Choose between: Discard sensor result : Do not store the results. Writ e sensor result t o disk (Filename: "Result of Sensor [ID].t xt "): Store the last result received to the "Logs (System)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Chart Type
13.06.2013
1419
Inherited Settings
Maintenance Window
Maintenance End At
1420
13.06.2013
Delay (Seconds)
13.06.2013
1421
1422
13.06.2013

Notifications
Others
133
section.
13.06.2013
1423
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 175 WMI Exchange Transport Queue Sensor
6.8.175 WM I Exchange Transport Queue Sensor

The WMI Exchange Server sensor monitors the length of transport queues of a Microsoft Exchange Server 2003, 2007, or 2010 using Windows Management Instrumentation (WMI). It shows the same information as shown in Windows System Monitor ('perfmon'). See section More 1429 below for an explanation of the transport queue types. Possible values that can be monitored: Active Mailbox Delivery Queue Length, Active Non-Smtp Delivery Queue Length, Active Remote Delivery Queue Length, Aggregate Delivery Queue Length (All Queues), Aggregate Shadow Queue Length, Categorizer Job Availability, Items Completed Delivery Per Second, Items Completed Delivery Total, Items Deleted By Admin Total, Items Queued For Delivery Expired Total, Items Queued for Delivery Per Second, Items Queued For Delivery Total, Items Resubmitted Total, Largest Delivery Queue Length, Messages Completed Delivery Per Second, Messages Completed Delivery Total, Messages Completing Categorization, Messages Deferred Due To Local Loop, Messages Deferred during Categorization, Messages Queued For Delivery, Messages Queued for Delivery Per Second, Messages Queued For Delivery Total, Messages Submitted Per Second, Messages Submitted Total, Poison Queue Length, Retry Mailbox Delivery Queue Length, Retry Non-Smtp Delivery Queue Length, Retry Remote Delivery Queue Length, Shadow Queue Auto Discards Total, Submission Queue Items Expired Total, Submission Queue Length, Unreachable Queue Length. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. If you select more than one queue, multiple sensors are created at once in the Add Sensor dialog. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
1424
19.07.2013
WMI Exchange Transport Queue Specific MSExchangeTransport Queues You see a list of transport queues that can be monitored on your Exchange server. The available options depend on your Exchange server configuration. PRTG shows all possible queues with name and instance description (if available). Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. Note: For performance reasons, we recommend to only select necessary items!
Sensor Settings
Tags
Priority
WMI Exchange Transport Queue Specific Displayname Instance WMI Class These fields show different information about the transport queue 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.
19.07.2013
1425
WMI Exchange Transport Queue Specific Counter TimeStamp TimeFreq Countertype Sensor Result Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results. Writ e sensor result t o disk (Filename: "Result of Sensor (ID].t xt "): Store the last result received to the "Logs (System)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Chart Type
1426
19.07.2013
Inherited Settings
Maintenance Window
Maintenance End At
19.07.2013
1427
Delay (Seconds)
1428
19.07.2013
More
Knowledge Base: Types of Transport Queues in Microsoft Exchange
19.07.2013
1429

Notifications
Others
133
section.
1430
19.07.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 176 WMI File Sensor
6.8.176 WM I File Sensor

The WMI File monitors a file using Windows Management Instrumentation (WMI). It shows the file size and the last modified date. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
Sensor Settings
Tags
Priority
27.11.2012
1431
WMI File Monit or File name Enter the name of the file that this sensor will check. Please enter a full local path. The file must exist on the computer your local or remote probe is running on; UNC paths are not allowed here. For example, when creating this sensor on a device under the local probe, the file be accessible on the local system. Define what shall be done in case the timestamp of the file changes. You can choose between: Ignore changes (default ): No action will be taken on change. Trigger 'On Change' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
If timestamp changes
Chart Type
1432
27.11.2012
Inherited Settings
Maintenance Window
Maintenance End At
27.11.2012
1433
Delay (Seconds)
1434
27.11.2012
27.11.2012
1435

Notifications
Others
133
section.
1436
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 177 WMI Free Disk Space (Multi Drive) Sensor
6.8.177 WM I Free Disk Space (M ulti Drive) Sensor

The WMI Free Disk Space (Multi Drive) sensor monitors the free disk space of one or multiple drive(s) using Windows Management Instrumentation (WMI). It shows the space in percent and total. One single sensor is used for all drives; the data is presented in different channels. This sensor monitors logical partitions of a hard or fixed disk drive. PRTG identifies logical disks by their drive letter, such as C. Note: This sensor is also supported on Windows XP and earlier. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
WMI Volume Specific Drive From the drop down menu select the drive(s) you want to monitor. We recommend using the default value. You can choose All to monitor all available drives or you can choose one specific drive letter to monitor this single drive only. The data in the drop down menu may also contain drive letters that do not exist on your device. The drive setting cannot be changed once the sensor is created.
Sensor Settings
07.02.2013
1437
Tags
Priority
WMI Disk Free Configurat ion Drive Shows the drive(s) that this sensor is monitoring; either All or a specific drive letter. 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.
Set limit s checked against ALL disks In this section you can set limits that are valid for all channels and all drives. By entering limits, you can define when the sensor will enter a Warning or Down status; depending on the data provided by all drives that this sensor monitors. If you want to define limits for separate channels individually please use the limit settings in the sensor's Channels settings. Note: All limits defined here are valid additionally to the limits defined in the particular Channels settings! Percentage Limit Check Enable or disable a limit check for the free space in percentage channels of all drives. By default percentage limits are enabled with lower warning and lower error limit. Choose between: Disable Percent age Limit s: Do not use the drives' data to control the sensor's status. Enable Percent age Limit s: Define limits. Additional fields appear below. The sensor will enter a warning or down state when free space limits are undercut or overrun.
1438
07.02.2013
Set limit s checked against ALL disks Upper Error Limit This field is only visible if percentage limit check is enabled above. Specify an upper limit in percent for a Down status. If the free disk space of one of your drives overruns this percent value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if percentage limit check is enabled above. Specify an upper limit in percent for a Warning status. If the free disk space of one of your drives overruns this percent value, the sensor will be set to Warning . Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if percentage limit check is enabled above. Specify a lower limit in percent for a warning state. If the free disk space of one of your drives undercuts this percent value, the sensor will be set to warning. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if percentage limit check is enabled above. Specify a lower limit in percent for entering a Down status. If the free disk space of one of your drives undercuts this percent value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! Enable or disable a limit check for the free bytes channels of all drives. Choose between: Disable By t e Limit s: Do not use the drives' data to control the sensor's status. Enable By t e Limit s: Define limits. Additional fields appear below. The sensor will enter a warning or down state when free space limits are undercut or overrun.
Upper Warning Limit
Lower Warning Limit
Lower Error Limit
Byte Limit Check
07.02.2013
1439
Set limit s checked against ALL disks Upper Error Limit This field is only visible if byte limit check is enabled above. Specify an upper limit. Use the same unit as shown by the free bytes channels of this sensor (by default this is MByte). If the free disk space of one of your drives overruns this bytes value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if byte limit check is enabled above. Specify an upper limit. Use the same unit as shown by the free bytes channels of this sensor (by default this is MByte). If the free disk space of one of your drives overruns this bytes value, the sensor will be set to Warning . Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if byte limit check is enabled above. Specify a lower limit. Use the same unit as shown by the free bytes channels of this sensor (by default this is MByte). If the free disk space of one of your drives undercuts this bytes value, the sensor will be set to Warning . Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! This field is only visible if byte limit check is enabled above. Specify a lower limit. Use the same unit as shown by the free bytes channels of this sensor (by default this is MByte). If the free disk space of one of your drives undercuts this bytes value, the sensor will be set to Down. Please enter an integer value or leave the field empty. Note: The limits set here are valid for all channels of this sensor. You can additionally set individual limits for each sensor channel in the Sensor Channels Set t ings 1566 . The limits set here and in the channel settings are valid simultaneously! If a monitored disk is removed or not found, values are set to zero. Select the alarming approach in this case. Choose between: Deact ivat e alarm (default ): Select this option if you do not want an alarm for a removed disk. Act ivat e Alarm: Select this option if you want to be alerted if a monitored disk is removed.
Upper Warning Limit
Lower Warning Limit
Lower Error Limit
1440
07.02.2013
Chart Type
Inherited Settings
07.02.2013
1441
Maintenance Window
Maintenance End At
Dependency Type
1442
07.02.2013
Delay (Seconds)
07.02.2013
1443

Notifications
Others
133
section.
1444
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 178 WMI HDD Health Sensor
6.8.178 WM I HDD Health Sensor

This sensor type connects to the parent device via Windows Management Instrumentation (WMI) and monitors the health of IDE disk drives on the target system, using Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.). This is built into most modern IDE hard disk drives. Note: This sensor officially requires Windows Vista or later running on the target machine which holds the hard disk drives you want to monitor. The sensor may not work reliably when the target machine runs on Windows 2003 or Windows XP; due to a known bug in those systems, the sensor may not be able to detect available hard disk drives. Available sensor channels may vary, depending on the hardware used on the target system. Available measurements may include: Read Error Rate, Spin-Up Time, Start/Stop Count, Reallocated Sectors Count, Seek Error Rate, Power-On Hours, Spin Retry Count, Calibration Retry Count, Power Cycle Count, Power-off Retract Count, Load Cycle Count, Temperature Celsius, Reallocation Event Count, Current Pending Sector Count, Uncorrectable Sector Count, UltraDMA CRC Error Count, Write Error Rate, Transfer Error Rate, Total LBAs Written, and Total LBAs Read. The channel names indicate the ID of the channel, followed by a colon, and the typical meaning of the channel. Note: Some vendors define meanings other than the common one. Every attribute of a disk assumes a value. PRTG shows these attributes as channels with their last, minimum, and maximum value. These channel values change over time and indicate the disk healthhigher values correspond to a better health. The disk's attributes come with a threshold, defined by the manufacturer of the drive. If a channel value is lower than this threshold, the sensor is automatically set to a Warning status. This indicates that the SelfMonitoring, Analysis and Reporting Technology (S.M.A.R.T.) status of the HDD might break soon. Note: For some attributes are no thresholds defined and thus cannot be judged for a status other than Up. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. In order to monitor the health of a disk, PRTG will create one sensor for each IDE device you choose. The settings you make in this dialog are valid for all of the sensors that are created.
13.06.2013
1445
SMART Specific IDE Devices Please select one or more hard disks you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. Names are chosen automatically and can be changed later in the sensor's settings. The items shown in the list are specific to the parent device you're creating the sensor on.
Sensor Settings
Tags
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.
1446
13.06.2013
SMART Specific 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. 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. 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.
Name
Timeout (sec)
Chart Type
Inherited Settings
13.06.2013
1447
Maintenance Window
Maintenance End At
Dependency Type
1448
13.06.2013
Delay (Seconds)
13.06.2013
1449

Notifications
Others
133
section.
1450
13.06.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 179 WMI Logical Disk Sensor
6.8.179 WM I Logical Disk Sensor

The WMI Logical Disk sensor monitors parameters of a logical disk of a Windows device using Windows Management Instrumentation (WMI). It shows disk read/write time, queue, free space, etc. on logical partitions of a disk drive. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
WMI Logical Disk Specific Logical Disks You see a list showing the Name of the counters you can monitor as well as the Inst ance, i.e. the respective logical disk (or '_Total'). If there are no logical disks available, you will see a corresponding message. From the list, choose all Name/Inst ance combinations you want to monitor by adding a check mark in front of the respective line (for example, choose '% Disk Read Time for C:'). For each selection one sensor will be created using the defined settings.
Sensor Settings
27.11.2012
1451
Tags
Priority
1452
27.11.2012
Chart Type
Inherited Settings
27.11.2012
1453
Maintenance Window
Maintenance End At
Dependency Type
1454
27.11.2012
Delay (Seconds)
27.11.2012
1455

Notifications
Others
133
section.
1456
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 180 WMI Memory Sensor
6.8.180 WM I M emory Sensor

The WMI Memory sensor monitors available (free) system memory on Windows systems using Windows Management Instrumentation (WMI). For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
Sensor Settings
Tags
Priority
27.11.2012
1457
WMI Alt ernat ive Query Errors and invalid data This is an extended help field only. PRTG's WMI sensors are equipped with the most efficient and accurate WMI queries. However, Microsoft has changed (and will continue to do that in the future) some WMI classes over the various Windows/ ServicePack/patchlevel versions, resulting in errors like "class not valid" or "invalid data". Wherever possible PRTG features an alternative query that might work in your specific circumstances. When you keep getting errors for this sensor please try enabling the alternative query method below. Choose the method PRTG uses to query via WMI. For compatibility reasons, an alternative query method can be enabled. We recommend using the default value. You can choose between: use default : Use PRTG's standard method to query WMI. This is the best setting in most cases. use alt ernat ive: Use an alternative method to query WMI. If you keep getting errors, please try this setting.
Alternative query
Chart Type
1458
27.11.2012
Inherited Settings
Maintenance Window
Maintenance End At
27.11.2012
1459
Delay (Seconds)
1460
27.11.2012

Notifications
Others
133
section.
27.11.2012
1461
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 181 WMI Microsoft SQL Server 2005 Sensor (Deprecated)
6.8.181 WM I M icrosoft SQL Server 2005 Sensor (Deprecated)
Import ant Not ice This sensor type is deprecated. Monitoring of Microsoft SQL Server 2005 using PRTG is discontinued. It cannot be monitored with PRTG any more with the latest updates of SQL Server 2005. The reason for this is a software update delivered by Microsoft in August 2012. The following updates cause this issue: Securit y Updat e for SQL Server 2005 Service Pack 4 (KB2716429) Securit y Updat e for SQL Server 2005 Service Pack 4 (KB2716427) We have made reasonable effort to fix this from our side but we were unable to. We do not have instructions to circumvent this issue at this time. Please ask the vendor to fix this.
More
Knowledge Base: Why does my WMI Microsoft SQL Server 2005 Sensor not work anymore? http://www.paessler.com/knowledgebase/en/topic/44713
The WMI Microsoft SQL Server sensor monitors the performance of a Microsoft SQL server via Windows Management Instrumentation (WMI). This sensor can monitor SQL General St at ist ics, Access Met hods, the Buffer Manager, the Memory Manager, the Locks Manager, and SQL St at ist ics. The channels actually available for a sensor depend on which performance counters you choose during setup.
Channel Overview User Connections Number of user connections. Because each user connection consumes some memory, configuring overly high numbers of user connections could affect throughput. Set user connections to the maximum expected number of concurrent users. Total number of logins started per second. Total number of logout operations started per second. Number of unrestricted full scans per second. These can be either base-table or full-index scans.
Logins Logouts Full Scans
1462
07.02.2013
Channel Overview Page Splits Number of page splits per second that occur as the result of overflowing index pages. Number of times locks on a table were escalated. Percentage of pages found in the buffer cache without having to read from disk. The ratio is the total number of cache hits divided by the total number of cache lookups since an instance of SQL Server was started. After a long period of time, the ratio moves very little. Because reading from the cache is much less expensive than reading from disk, you want this ratio to be high. Generally, you can increase the buffer cache hit ratio by increasing the amount of memory available to SQL Server. Number of pages in the buffer pool with database content. Number of pages used for miscellaneous server purposes (including procedure cache). Number of seconds a page will stay in the buffer pool without references. Total amount of dynamic memory the server is using for maintaining connections. Total amount of dynamic memory the server is using for query optimization. Total amount of dynamic memory (in kilobytes) that the server is using currently. Total amount of dynamic memory the server can consume.
Table Lock Escalations Buffer Cache Hit Ratio
Database Pages Stolen Pages
Page Life Expectancy
Connection Memory (KB) Optimizer Memory (KB)
Total Server Memory (KB) Target Server Memory (KB) SQL Cache Memory (KB) Lock Requests
Total amount of dynamic memory the server is using for the dynamic SQL cache. Number of new locks and lock conversions per second requested from the lock manager. Number of lock requests per second that resulted in a deadlock. Average amount of wait time (in milliseconds) for each lock request that resulted in a wait.
Deadlocks Average Wait Time
07.02.2013
1463
Channel Overview Batch Requests Number of Transact-SQL command batches received per second. This statistic is affected by all constraints (such as I/O, number of users, cache size, complexity of requests, and so on). High batch requests mean good throughput. Number of SQL compilations per second. Indicates the number of times the compile code path is entered. Includes compiles due to recompiles. After SQL Server user activity is stable, this value reaches a steady state. Number of SQL recompiles per second. Counts the number of times recompiles are triggered. In general, you want the recompiles to be low.
SQL Compilations
SQL Re-Compilations
Note: This sensor can only be added to a device (computer) running a Microsoft SQL database. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
SQL Server Set t ings MS SQL Server Instance You see a list of all server instances available on the device. Display name and service name are provided as returned by the SQL server. Please choose one or more instances by adding a check mark in front of the respective line. For each instance one sensor will be created.
1464
07.02.2013
SQL Server Set t ings SQL Server Version Enter the version of the SQL server. Usually, you can keep the default value.
SQL Count er Specific SQL Performance Counters You see a list of different performance counters which can be monitored for the instance(s) selected above. The sensors created for the server instances will all monitor the performance counter you select here. Choose from: General St at ist ics: Read general performance counters. This will show the number of user connections, and the number of logins and logouts per second. Access Met hods: Read access method counters. This will show the number of full scans, page splits, and table lock escalations, per second. Buffer Manager: Read buffer manager counters. This will show the buffer cache hit ratio in percent, and the number of database pages and stolen pages. Memory Manager: Read memory manager counters. This will show the connection memory, optimizer memory, total server memory, target server memory, and SQL cache memory, in KB. Locks: Read locks counters. This will show the number of lock requests and deadlocks, per second, and the average wait time. SQL St at ist ics: Read SQL statistics. This will show the number of batch requests, SQL compilations, and SQL re-compilations, per second. Depending on your selection, a sensor with the specified channels will be created. Note: In order to monitor several performance counters for an instance, please add the sensor several times.
Sensor Settings
07.02.2013
1465
Tags
Priority
SQL Server Set t ings Service Shows the service 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. Shows the name of the server instance 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. Select whether PRTG will select the name of the WMI class used for monitoring automatically. Choose between: Aut omat ic : Choose WMI class automatically. This is the recommended setting. Manual: Manually enter a WMI class name. Use this if your server instance returns an error code in automatic mode. WMI Class This field is only shown if manual WMI class selection is enabled above. This setting is intended for experienced users only. Enter the WMI class name that will be used for monitoring your server instance. Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results.
Name
WMI Class Name
Sensor Result
1466
07.02.2013
SQL Server Set t ings Writ e sensor result t o disk (Filename: "Result of Sensor (ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Chart Type
Inherited Settings
07.02.2013
1467
Maintenance Window
Maintenance End At
Dependency Type
1468
07.02.2013
Delay (Seconds)
07.02.2013
1469

Notifications
Others
133
section.
1470
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 182 WMI Microsoft SQL Server 2008 Sensor
6.8.182 WM I M icrosoft SQL Server 2008 Sensor

Channel Overview User Connections Number of user connections. Because each user connection consumes some memory, configuring overly high numbers of user connections could affect throughput. Set user connections to the maximum expected number of concurrent users. Total number of logins started per second. Total number of logout operations started per second. Number of unrestricted full scans per second. These can be either base-table or full-index scans. Number of page splits per second that occur as the result of overflowing index pages. Number of times locks on a table were escalated. Percentage of pages found in the buffer cache without having to read from disk. The ratio is the total number of cache hits divided by the total number of cache lookups since an instance of SQL Server was started. After a long period of time, the ratio moves very little. Because reading from the cache is much less expensive than reading from disk, you want this ratio to be high. Generally, you can increase the buffer cache hit ratio by increasing the amount of memory available to SQL Server. Number of pages in the buffer pool with database content. Number of pages used for miscellaneous server purposes (including procedure cache). Number of seconds a page will stay in the buffer pool without references. Total amount of dynamic memory the server is using for maintaining connections.
Page Splits
Connection Memory (KB)
27.11.2012
1471
Channel Overview Optimizer Memory (KB) Total amount of dynamic memory the server is using for query optimization. Total amount of dynamic memory (in kilobytes) that the server is using currently. Total amount of dynamic memory the server can consume.
Total amount of dynamic memory the server is using for the dynamic SQL cache. Number of new locks and lock conversions per second requested from the lock manager. Number of lock requests per second that resulted in a deadlock. Average amount of wait time (in milliseconds) for each lock request that resulted in a wait. Number of Transact-SQL command batches received per second. This statistic is affected by all constraints (such as I/O, number of users, cache size, complexity of requests, and so on). High batch requests mean good throughput. Number of SQL compilations per second. Indicates the number of times the compile code path is entered. Includes compiles due to recompiles. After SQL Server user activity is stable, this value reaches a steady state. Number of SQL recompiles per second. Counts the number of times recompiles are triggered. In general, you want the recompiles to be low.
Batch Requests
SQL Compilations
SQL Re-Compilations
1813
1472
27.11.2012
Add Sensor
SQL Server Set t ings MS SQL Server Instance You see a list of all server instances available on the device. Display name and service name are provided as returned by the SQL server. Please choose one or more instances by adding a check mark in front of the respective line. For each instance one sensor will be created. Enter the version of the SQL server. Usually, you can keep the default value.
SQL Server Version
SQL Count er Specific SQL Performance Counters You see a list of different performance counters which can be monitored for the instance(s) selected above. The sensors created for the server instances will all monitor the performance counter you select here. Choose from: General St at ist ics: Read general performance counters. This will show the number of user connections, and the number of logins and logouts per second. Access Met hods: Read access method counters. This will show the number of full scans, page splits, and table lock escalations, per second. Buffer Manager: Read buffer manager counters. This will show the buffer cache hit ratio in percent, and the number of database pages and stolen pages. Memory Manager: Read memory manager counters. This will show the connection memory, optimizer memory, total server memory, target server memory, and SQL cache memory, in KB. Locks: Read locks counters. This will show the number of lock requests and deadlocks, per second, and the average wait time. SQL St at ist ics: Read SQL statistics. This will show the number of batch requests, SQL compilations, and SQL re-compilations, per second.
27.11.2012
1473
SQL Count er Specific Depending on your selection, a sensor with the specified channels will be created. Note: In order to monitor several performance counters for an instance, please add the sensor several times.
Sensor Settings
Tags
Priority
SQL Server Set t ings Service Shows the service 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. Shows the name of the server instance 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. Select whether PRTG will select the name of the WMI class used for monitoring automatically. Choose between:
Name
WMI Class Name
1474
27.11.2012
SQL Server Set t ings Aut omat ic : Choose WMI class automatically. This is the recommended setting. Manual: Manually enter a WMI class name. Use this if your server instance returns an error code in automatic mode. WMI Class This field is only shown if manual WMI class selection is enabled above. This setting is intended for experienced users only. Enter the WMI class name that will be used for monitoring your server instance. Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results. Writ e sensor result t o disk (Filename: "Result of Sensor (ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Sensor Result
Chart Type
27.11.2012
1475
Inherited Settings
Maintenance Window
Maintenance End At
1476
27.11.2012
Delay (Seconds)
27.11.2012
1477

Notifications
Others
133
section.
1478
27.11.2012
6.8.183 WM I M icrosoft SQL Server 2012 Sensor

Channel Overview User Connections Number of user connections. Because each user connection consumes some memory, configuring overly high numbers of user connections could affect throughput. Set user connections to the maximum expected number of concurrent users. Total number of logins started per second. Total number of logout operations started per second. Number of unrestricted full scans per second. These can be either base-table or full-index scans. Number of page splits per second that occur as the result of overflowing index pages. Number of times locks on a table were escalated. Percentage of pages found in the buffer cache without having to read from disk. The ratio is the total number of cache hits divided by the total number of cache lookups since an instance of SQL Server was started. After a long period of time, the ratio moves very little. Because reading from the cache is much less expensive than reading from disk, you want this ratio to be high. Generally, you can increase the buffer cache hit ratio by increasing the amount of memory available to SQL Server. Number of pages in the buffer pool with database content. Number of pages used for miscellaneous server purposes (including procedure cache). Number of seconds a page will stay in the buffer pool without references. Total amount of dynamic memory the server is using for maintaining connections.
Page Splits
Connection Memory (KB)
21.12.2012
1479
Channel Overview Optimizer Memory (KB) Total amount of dynamic memory the server is using for query optimization. Total amount of dynamic memory (in kilobytes) that the server is using currently. Total amount of dynamic memory the server can consume.
Total amount of dynamic memory the server is using for the dynamic SQL cache. Number of new locks and lock conversions per second requested from the lock manager. Number of lock requests per second that resulted in a deadlock. Average amount of wait time (in milliseconds) for each lock request that resulted in a wait. Number of Transact-SQL command batches received per second. This statistic is affected by all constraints (such as I/O, number of users, cache size, complexity of requests, and so on). High batch requests mean good throughput. Number of SQL compilations per second. Indicates the number of times the compile code path is entered. Includes compiles due to recompiles. After SQL Server user activity is stable, this value reaches a steady state. Number of SQL recompiles per second. Counts the number of times recompiles are triggered. In general, you want the recompiles to be low.
Batch Requests
SQL Compilations
SQL Re-Compilations
1813
1480
21.12.2012
Add Sensor
SQL Server Set t ings MS SQL Server Instance You see a list of all server instances available on the device. Display name and service name are provided as returned by the SQL server. Please choose one or more instances by adding a check mark in front of the respective line. For each instance one sensor will be created. Enter the version of the SQL server. Usually, you can keep the default value.
SQL Server Version
SQL Count er Specific SQL Performance Counters You see a list of different performance counters which can be monitored for the instance(s) selected above. The sensors created for the server instances will all monitor the performance counter you select here. Choose from: General St at ist ics: Read general performance counters. This will show the number of user connections, and the number of logins and logouts per second. Access Met hods: Read access method counters. This will show the number of full scans, page splits, and table lock escalations, per second. Buffer Manager: Read buffer manager counters. This will show the buffer cache hit ratio in percent, and the number of database pages and stolen pages. Memory Manager: Read memory manager counters. This will show the connection memory, optimizer memory, total server memory, target server memory, and SQL cache memory, in KB. Locks: Read locks counters. This will show the number of lock requests and deadlocks, per second, and the average wait time. SQL St at ist ics: Read SQL statistics. This will show the number of batch requests, SQL compilations, and SQL re-compilations, per second.
21.12.2012
1481
SQL Count er Specific Depending on your selection, a sensor with the specified channels will be created. Note: In order to monitor several performance counters for an instance, please add the sensor several times.
Sensor Settings
Tags
Priority
SQL Server Set t ings Service Shows the service 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. Shows the name of the server instance 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. Select whether PRTG will select the name of the WMI class used for monitoring automatically. Choose between:
Name
WMI Class Name
1482
21.12.2012
SQL Server Set t ings Aut omat ic : Choose WMI class automatically. This is the recommended setting. Manual: Manually enter a WMI class name. Use this if your server instance returns an error code in automatic mode. WMI Class This field is only shown if manual WMI class selection is enabled above. This setting is intended for experienced users only. Enter the WMI class name that will be used for monitoring your server instance. Define what will be done with the results the sensor receives. Choose between: Discard sensor result : Do not store the results. Writ e sensor result t o disk (Filename: "Result of Sensor (ID].t xt "): Store the last result received to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Sensor Result
Chart Type
21.12.2012
1483
Inherited Settings
Maintenance Window
Maintenance End At
1484
21.12.2012
Delay (Seconds)
21.12.2012
1485

Notifications
Others
133
section.
1486
21.12.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 184 WMI Process Sensor
6.8.184 WM I Process Sensor

The WMI Process sensor monitors a Windows process using Windows Management Instrumentation (WMI). It shows the absolute working set and commit size, the number of threads and handles, as well as the average CPU usage (if there are multiple instances running) and the total CPU usage of the process. For the "total CPU usage" value of a process, all CPU usage values are summed up. The total is divided by the number of all CPUs; the maximum value is 100%. This corresponds to the CPU usage of all instances of this specific process. Regarding the "per instance" value, the summed up CPU usage value is divided by the number of all instances. It shows the average CPU usage of a single instance of the process on one CPU. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
Sensor Settings
Tags
04.12.2012
1487
WMI Process Monit or Executable Enter the name of the process that will be monitored. Please enter the name of an executable file without the .exe extension. The sensor will be set to an error state if the process is not active on the device.
Chart Type
1488
04.12.2012
Inherited Settings
Maintenance Window
Maintenance End At
04.12.2012
1489
Delay (Seconds)
1490
04.12.2012
04.12.2012
1491

Notifications
Others
133
section.
1492
04.12.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 185 WMI Remote Ping Sensor
6.8.185 WM I Remote Ping Sensor

The WMI Remote Ping sensor connects remotely to a Windows system using Windows Management Instrumentation (WMI), then performs an Internet Control Message Protocol (ICMP) echo request ("Ping") from this device to a specified target. The sensor shows the Ping time from the remote device to the target device that is being pinged. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
Sensor Settings
Tags
Priority
27.11.2012
1493
WMI Remot e Ping Configurat ion Target Enter the DNS name or IP address of the target device the Ping is sent to. The sensor will remotely connect to the parent device it is created on via WMI, then perform a Ping request from this remote device to the target device/server. Please enter a string. Enter a timeout in seconds for the Ping. If the reply takes longer than this value the request is aborted and an error message is triggered. Please enter an integer value. The maximum is 300. Enter the packet size in bytes for the Ping. You can choose any value between 1 and 10000. Please enter an integer value. We recommend using the default value.
Timeout (Seconds)
Packet Size (Bytes)
Chart Type
Inherited Settings
1494
27.11.2012
Maintenance Window
Maintenance End At
Dependency Type
27.11.2012
1495
Delay (Seconds)
1496
27.11.2012

Notifications
Others
133
section.
27.11.2012
1497
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 186 WMI Security Center Sensor
6.8.186 WM I Security Center Sensor

The WMI Security Center sensor monitors the security status of a Windows computer using Windows Management Instrumentation (WMI). It can monitor all security products that are controlled by Windows Security Center / Windows Action Center. It returns a status code of the monitored product and sets the sensor status to Warning if a product status is unknown, if it is reported as out of date, or if the access scan is disabled. A sensor status showing Up indicates that the product is up to date and the access scan is running. Possible return values for status codes are:
St at us Code
Meaning: St at us of Monit ored Securit y Product Is ... Unknown Not running, Out of date Running, Out of date Not running, Up to date Running, Up to date
Will Result in Sensor St at us
0 1 2 3 4
Warning Warning Warning Warning OK
Note: This sensor requires Windows XP SP2 or later on the target computer. The Windows Security Center / Windows Action Center is only available on client Windows versions. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
1498
07.02.2013
WMI Securit y Cent er Specific Security Center Products You see a list showing the Name and Ty pe of all security products found in the Windows Security Center on the target device. If there are no products, you will see a corresponding message. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
Tags
Priority
WMI Securit y Cent er Specific Displayname Shows the name of the product 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. Shows the type of the product 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.
Type
07.02.2013
1499
WMI Securit y Cent er Specific If Value Changes Define what will be done in case the value of this sensor changes. You can choose between: Ignore changes: No action will be taken on change. Trigger 'change' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Chart Type
Inherited Settings
1500
07.02.2013
Maintenance Window
Maintenance End At
Dependency Type
07.02.2013
1501
Delay (Seconds)
1502
07.02.2013

Notifications
Others
133
section.
07.02.2013
1503
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 187 WMI Service Sensor
6.8.187 WM I Service Sensor

The WMI Service sensor monitors a Windows service using Windows Management Instrumentation (WMI). It shows the execution time of the monitoring request. Additionally, it can show CPU and pagefile usage, the number of handles and threads, and the working set of the monitored service. You can monitor these channels if you enable Monit or ext ended values in the sensor settings. Note: The "Running (msec)" channel of this sensor shows the execution time of the monitoring request. It does not refer to the time the Windows service has been running! As of PRTG version 13, the name of this sensor channel is Sensor Execut ion Time. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. If you select more than one service multiple sensors are created at once in the Add Sensor dialog. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
WMI Service Monit or Service A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. Name and description are provided in the language of the device's Windows installation. Later on, a sensor's status will be set to Down if the service is not running.
Sensor Settings
1504
08.10.2013
Tags
Priority
WMI Service Monit or If Service is Not Running Select whether the service will be (re-)started if it is stopped or paused. Choose between: St art /Rest art service (default ): PRTG will try to start the service if it is not running when scanning the device. Do not hing : PRTG will not start any service on the device automatically. Monitoring Select whether you want to monitor CPU usage and other useful performance counters. This may cause a "Class not found" error on some Windows systems. If you do not monitor these counters, the value '0' is returned for these channels. Choose between: Just check if services is running : PRTG will only monitor the channel "Sensor Execution Time". Monit or ext ended values: PRTG will monitor also other useful performance counters. Service Shows the Windows service this sensor will monitor. 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.
08.10.2013
1505
WMI Service Monit or Description Shows the description for the service. 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. Define what will be done with the result of the sensor. Choose between: Discard sensor result : Do not store the sensor result. Writ e sensor result t o disk (Filename: "Result of Sensor [ID].t xt "): Store the last result received from the sensor to the "Logs (Sensor)" directory (on the Master node, if in a cluster). File name: Result of Sensor [ID].txt. This is for debugging purposes. The file will be overridden with each scanning interval. For information on how to find the folder used for storage, please see Dat a St orage 1912 section.
Sensor Result
Chart Type
1506
08.10.2013
Inherited Settings
Maintenance Window
Maintenance End At
08.10.2013
1507
Delay (Seconds)
1508
08.10.2013

Notifications
Others
133
section.
08.10.2013
1509
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 188 WMI Share Sensor
6.8.188 WM I Share Sensor

The WMI Share sensor monitors a shared resource on a Windows system using Windows Management Instrumentation (WMI). It shows the availability; you can set a sensor to Down status for different share status messages. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. If you select more than one share 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:
WMI Shared Recource Share Select the shares you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. Note: In order to provide any shares, the LanmanServer "Server" Windows service must be running on the target computer. If it is not, there are no shares and you will see a No Share available message here.
Sensor Settings
1510
07.02.2013
Tags
Priority
WMI Shared Recource Shared Recource 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. 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. 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. 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.
Description
Type
TypeID
Trigger Errorst at e on following condit ions Select under which conditions the sensor will change to a Down status from the list below. As long as the share returns OK, the sensor status will be Up. Choose a Down condition by adding a check mark symbol in front of the according line. Please choose none, one, or several from the following conditions. Note: While in Down status, a sensor does not record any data in all of its channels. Error Set sensor to Down status if the share returns an error status. A share in this status is not operational.
07.02.2013
1511
Trigger Errorst at e on following condit ions Degraded Set sensor to Down status if the share returns a degraded status. A share in this status is still operational. Set sensor to Down status if the share returns an unknown status. Set sensor to Down status if the share returns a "predicted fail" status. This indicates that an element is functioning properly but is predicting a failure (for example, a SMART-enabled hard drive). A share in this status is still operational. Set sensor to Down status if the share returns a starting status. A share in this status is not operational. Set sensor to Down status if the share returns a stopping status. A share in this status is not operational. Set sensor to Down status if the share returns a service status. This can apply during disk mirror-resilvering, reloading a user permissions list, or other administrative work on the monitored device. Not all such work is online, but the managed element is neither OK nor in one of the other states. A share in this status is not operational. Set sensor to Down status if the share returns a stressed status. Set sensor to Down status if the share returns a "non recover" status. Set sensor to Down status if the share returns a "no contact" status. Set sensor to Down status if the share returns "lost communication" status.
Unknown Pred Fail
Starting
Stopping
Service
Stressed Nonrecover
NoContact
LostComm
Chart Type
1512
07.02.2013
Inherited Settings
07.02.2013
1513
Maintenance End At
Dependency Type
1514
07.02.2013

07.02.2013
1515
Notifications
Others
133
section.
1516
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 189 WMI SharePoint Process Sensor
6.8.189 WM I SharePoint Process Sensor

The WMI SharePoint Process sensor monitors a Microsoft SharePoint server using Windows Management Instrumentation (WMI). It shows the number of current page requests, active threads, and SQL queries currently executed, as well as global heap size, object cache always live size, template cache size, and CPU utilization. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. If you select more than one SharePoint process, multiple sensors are created at once in the Add Sensor dialog. The settings you make in this dialog are valid for all of the sensors that are created. The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the sensor's settings page:
WMI Process Monit or SharePoint Processes You see a list of all SharePoint processes running on this device. There is also a "_Total" process available. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
07.02.2013
1517
Tags
Priority
WMI Process Monit or SharePoint Process The name of the SharePoint process that is 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.
Chart Type
1518
07.02.2013
Inherited Settings
Maintenance Window
07.02.2013
1519
Maintenance End At
Dependency Type
Delay (Seconds)
1520
07.02.2013
07.02.2013
1521

Notifications
Others
133
section.
1522
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 190 WMI Terminal Services (Windows 2008) Sensor
6.8.190 WM I Terminal Services (Windows 2008) Sensor

The WMI Terminal Services sensor monitors the number of sessions on a Windows Terminal Services (Remote Desktop Services) server using Windows Management Instrumentation (WMI). It shows the number of active and total sessions. Active sessions are sessions with a currently logged in user; inactive sessions (included in total) can be sessions with a disconnected user that has not logged out, or system services using a session. Note: As "Total Sessions", this sensor type will return the number of the active sessions, plus two additional sessions: one for the console, and another for the services. So, the number of total sessions may actually be higher than expected. Note: Depending on the OS that will be monitored, please select either the sensor for Windows XP/Vista/2003 or the one for Windows 2008. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
Sensor Settings
Tags
27.11.2012
1523
Chart Type
Inherited Settings
1524
27.11.2012
Maintenance Window
Maintenance End At
Dependency Type
27.11.2012
1525
Delay (Seconds)
1526
27.11.2012

Notifications
Others
133
section.
27.11.2012
1527
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 191 WMI Terminal Services (Windows XP/Vista/2003) Sensor
6.8.191 WM I Terminal Services (Windows XP/Vista/2003) Sensor

The WMI Terminal Services sensor monitors the number of sessions on a Windows Terminal Services (Remote Desktop Services) server using Windows Management Instrumentation (WMI). It shows the number of active and total sessions. Active sessions are sessions with a currently logged in user; inactive sessions (included in total) can be sessions with a disconnected user that has not logged out, or system services using a session. Note: As "Total Sessions", this sensor type will return the number of the active sessions, plus two additional sessions: one for the console, and another for the services. So, the number of total sessions may actually be higher than expected. Note: Depending on the OS that will be monitored, please select either the sensor for Windows XP/Vista/2003 or the one for Windows 2008. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
Sensor Settings
Tags
1528
27.11.2012
Chart Type
Inherited Settings
27.11.2012
1529
Maintenance Window
Maintenance End At
Dependency Type
1530
27.11.2012
Delay (Seconds)
27.11.2012
1531

Notifications
Others
133
section.
1532
27.11.2012
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 192 WMI UTC Time Sensor
6.8.192 WM I UTC Time Sensor

The WMI UTC Time sensor monitors the UTC time of a target device using Windows Management Instrumentation (WMI). It shows the UTC time of the target device, and the time difference between the PRTG system time and the target device, in seconds. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
Sensor Settings
Tags
Priority
27.11.2012
1533
Chart Type
Inherited Settings
1534
27.11.2012
Maintenance Window
Maintenance End At
Dependency Type
27.11.2012
1535
Delay (Seconds)
1536
27.11.2012

Notifications
Others
133
section.
27.11.2012
1537
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 193 WMI Vital System Data (V2) Sensor
6.8.193 WM I Vital Sy stem Data (V2) Sensor

The WMI Vital System Data sensor monitors vital system parameters (CPU, system, memory, disk, network, pagefile, etc.) using Windows Management Instrumentation (WMI). For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
Vit al Sy st em Dat a Readings Accessible Using WMI Performance Counter You see a list of available vital system data values the sensor can monitor on the target device. The available options depend on your configuration. PRTG shows all possible performance counters with name and instance description (if available). Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head. You can choose between the following counters: CPU Thread Memory Net work Pagefile
Sensor Settings
1538
13.06.2013
Tags
Priority
13.06.2013
1539
Chart Type
Inherited Settings
1540
13.06.2013
Maintenance Window
Maintenance End At
Dependency Type
13.06.2013
1541
Delay (Seconds)
1542
13.06.2013

Notifications
Others
133
section.
13.06.2013
1543
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 194 WMI Volume Sensor
6.8.194 WM I Volume Sensor

The WMI Volume sensor monitors the free disk space on one drive or one logical volume using Windows Management Instrumentation (WMI). It shows the space in percent and total. For each drive or logical volume, one sensor is used. This sensor monitors an area of storage on a hard disk. It can monitor local volumes that are formatted, unformatted, mounted, or offline. A volume is formatted by using a file system, such as File Allocation Table (FAT) or New Technology File System (NFTS), and might have a drive letter assigned to it. One hard disk can have multiple volumes, and volumes can span multiple physical disks. The sensor does not support disk drive management. Note: This sensor is not supported on Windows XP and earlier. For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on. Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For a general introduction to the technology behind WMI, please see Monit oring via WMI section.
1813
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 209 . It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later. For devices with multiple volumes 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:
WMI Volume Specific Volumes Select the volume(s) you want to add a sensor for. A list of all available items is shown with their name. Select the desired items by adding check marks in front of the respective lines. One sensor will be created for each selection. You can also select and deselect all items by using the check box in the table head.
Sensor Settings
1544
07.02.2013
Tags
Priority
WMI Volume Specific DeviceID Shows the id of the volume that this sensor is monitoring. 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. Shows the type of the drive the sensor is monitoring. 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. Enter a timeout in seconds for the WMI request. If the reply takes longer than this value the request is aborted and an error message is triggered.
Drive Type
Timeout (sec)
Chart Type
07.02.2013
1545
Inherited Settings
1546
07.02.2013
Maintenance End At
Dependency Type
07.02.2013
1547
1548
07.02.2013

Notifications
Others
133
section.
07.02.2013
1549
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 195 WMI Windows Version Sensor
6.8.195 WM I Windows Version Sensor

The WMI Windows Version sensor reads the Windows version of the parent device via Windows Management Instrumentation (WMI). It returns the version number (in a channel) as well as the according version name (in the sensor message). Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.


Add Sensor
Sensor Settings
1550
07.02.2013
Tags
Priority
Sensor Set t ings If Value Changes Define what will 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' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Chart Type
07.02.2013
1551
Inherited Settings
Maintenance Window
1552
07.02.2013
Maintenance End At
Dependency Type
Delay (Seconds)
07.02.2013
1553
1554
07.02.2013

Notifications
Others
133
section.
07.02.2013
1555
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings 196 WSUS Statistics Sensor
6.8.196 WSUS Statistics Sensor

The WSUS Statistics sensor monitors various statistics on a Windows Server Update Services (WSUS) server using Windows Management Instrumentation (WMI). It can show the number of: Approved updates, computers having update errors, computers needing updates, computers not synchronized for 7 days, computers registered, computers up to date, declined updates, expired updates, not approved critical or security updates, not approved updates, total updates, unapproved needed updates, updates needed by computers, updates needing files, updates up to date, updates with client errors, updates with server errors, updates with stale update approvals, and the number of WSUS infrastructure updates not approved for installation. Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.


Requirement: WSUS 3.0 Administration Console

In order for this sensor to work, Microsoft's WSUS 3.0 Administration Console must be installed on the computer running the PRTG probe: Either on the local system (on every node, if on a cluster probe), or on the system running the remote probe.
1556
07.02.2013
Add Sensor
Sensor Settings
Tags
Priority
Sensor Set t ings WSUS Server Port Define the port where the WSUS server service is running on. Default value is 80. Please enter an integer value. Define if SSL-encryption will be used for the connection to the WSUS server. Choose between: Yes No If Value Changes Define what will be done in case the value of this sensor changes. You can choose between: Ignore changes: No action will be taken on change.
Use SSL
07.02.2013
1557
Sensor Set t ings Trigger 'change' not ificat ion: The sensor will send an internal message indicating that its value has changed. In combination with a Change Trigger, you can use this mechanism to trigger a notification 1573 whenever the sensor value changes.
Chart Type
Inherited Settings
1558
07.02.2013
Maintenance Window
Maintenance End At
Dependency Type
07.02.2013
1559
Delay (Seconds)
1560
07.02.2013
07.02.2013
1561

Notifications
Others
133
section.
1562
07.02.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 9 Additional Sensor Types (Custom Sensors)
6.9
Additional Sensor Types (Custom Sensors)

Users can create and use their own, self-written custom sensors in PRTG Network Monitor to go far beyond PRTG's standard sensor set. You can create your own sensors using Windows Management Instrumentation Query Language (WQL), visual basic scripting, PowerShell, batch scripting, and by compiling an EXE or DLL file (using any Windows software development tool).
Basics
For a general introduction, please see the sections about EXE/Script sensors and the API documentation which contains details about the necessary return format for those sensors. WMI Custom sensors allow executing WQL requests. EX E/Script Sensor
415
EX E/Script Advanced Sensor SSH Script Sensor

1209
424
Applicat ion Programming Int erface (API) Definit ion WMI Cust om Sensor
1394
1871
Custom Sensors Included in PRTG

After installing PRTG Network Monitor you will already find a selection of custom EXE/Script and WMI WQL sensors in the PRTG program directory 1912 . Many of these are sample projects that you can edit and improve for your needs.
Custom Sensors Included in PRTGFolder: \Custom Sensors\EXE

Demo Batchfile - Returns 200.bat Demo Batchfile - Set sensorstate to warning.bat Demo Cmd - Returns 200.cmd Demo Dll - Returns a random integer.dll Demo EXE - Returns a random integer.exe Demo EXE - Returns number of files in folder (parameter).exe Demo EXE - Returns user of process.exe Demo Powershell Script - Available MB via WMI.ps1 Demo Powershell Script - InterruptsPerSec via WMI.ps1 Demo Powershell Script - Returns a fixed integer value.ps1 Demo Powershell Script - Returns a random integer value.ps1 Demo Powershell Script - Returns Random Integer and Warnings.ps1 Demo VBScript - InterruptsPerSec via WMI.vbs
27.11.2012
1563
Demo VBScript - Multiplies two integers(2 parameters).vbs Demo VBScript - Returns a fixed float value.vbs Demo VBScript - Returns a fixed integer value.vbs Demo VBScript - Returns a random value.vbs Demo VBScript - Returns number of svchost processes.vbs Demo VBScript - Returns user of process.vbs Demo VBScript - Returns warning depending on number of svchost processes.vbs Demo VBScript - UTCTime via WMI.vbs Load_Test_CPU_10_Mio_Primes.exe Load_Test_CPU_1_Mio_Primes.exe Load_Test_Disk_Write_Read_10000_files.exe Load_Test_Disk_Write_Read_1000_files.exe Load_Test_Memory_Allocate_And_Free_400MB.exe To create a new sensor based on one of these files, create a new EX E/Script Sensor choose the respective file from the drop down list.
415
and
Custom Sensors Included in PRTGFolder: \Custom Sensors\EXEXML

Demo Batchfile - Returns static values in four channels.bat To create a new sensor based on one of these files, create a new EX E/Script Advanced Sensor 424 and choose the respective file from the drop down list.
Custom Sensors Included in PRTGFolder: \Custom Sensors\WMI WQL scripts

Demo WQL Script - Get Win32LogicalDiscFreeMB.wql Demo WQL Script - Get Win32OsBuildnumber.wql Demo WQL Script - Get Win32PercentProcessorIdleTime.wql Demo WQL Script - Get Win32PercentProcessorTime.wql To create a new sensor based on one of these files, create a new WMI Cust om Sensor choose the respective file from the drop down list.
1394
and
Downloading Pre-Build Custom Sensors

A good resource is the PRTG Add-Ons website on the open source platform Google Code. There are also additional tools available. Open Source Add-Ons for PRTG Network Monitor
1564
27.11.2012
http://code.google.com/p/prtg-addons/
More
For the other sensor types that work out-of-the-box, please see List of Available Sensor Ty pes
279
Knowledge Base: How can I test if parameters are correctly transmitted to my script when using an EXE/Script sensor? http://www.paessler.com/knowledgebase/en/topic/11283
27.11.2012
1565
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 10 Sensor Channels Settings
6.10
Sensor Channels Settings

A sensor has one or more channels in which it handles the actual monitoring data. In the channel settings you can define how the data from the sensor's different channels will be displayed in graphs, gauges, and tables. Additionally, the channel data can determine the sensor's status. Use the limit settings to achieve this. On the sensor's Overview page, click on the gear icon of a specific channel gauge to change its settings. A click on the pin symbol on the left of the gear icon in a gauge will make this channel the primary channel of the selected sensor. You can alternatively call the settings of a channel by clicking on the respective gear icon in the channels data table underneath the gauges. Note: For lookup 1879 channels, we recommend staying below 120 lookup values to get expressive gauges. For non-primary lookup channels the upper limit is around 40 lookup values.
The Gear Ic on of a SNMP Traffic Total Channel
The available options are nearly the same for all sensor types. An exception applies to the "Downtime" channel which is automatically calculated and does not offer all settings. Channels with "absolute" values additionally have an option for defining the Value Mode.
1566
08.10.2013
Channel Settings for an SNMP Traffic Sensor
08.10.2013
1567
Available Channel Settings

Edit Channel "[Name]" Name Enter a meaningful name to identify the channel (not editable for script sensors after sensor creation). The name will be shown in graphs and tables. You can automatically add the sensor's ID to the name by using the placeholder [#id]. This field is only visible for script sensors, the SNMP Custom sensor, and the SNMP Library sensor. Enter a string describing the unit of the returned values. This is for display purposes only. Please enter a string. This field is only visible for script sensors, the SNMP Custom sensor, and the SNMP Library sensor. Select the lookup list to be applied to this channel's settings. The ID of the channel cannot be changed; it is used for unique definition. For example, you need the ID when using Sensor Fact ory 807 sensors. Define where the channel will be displayed. Choose from: Show in Chart s: The data of this channel will be shown in sensor graphs. Note: If you hide a channel here, it will also be hidden if this graph is used in a Report 1636 . Show in Tables: The data of this channel will be shown in sensor data tables. Note: If you hide a channel here, it will not be considered for the calculation of the "sum" (total) channel of this sensor! To change this setting, remove or add the check mark symbol in front of it. Line Color Define in what color the channel will be displayed in graphs. You can choose between Aut omat ic Manual When you set this option to manual color definition please enter a color below. Color (#rrggbb) This option is only available if Manual is selected in the Line Color setting above. Please either enter a color in hexadecimal RGB notation (as in HTML/CSS), or choose a color from the visual color selector. The field containing the hexadecimal color value will change to the resulting color immediately in both cases.
Unit
Value Lookup
ID
Display
1568
08.10.2013
Edit Channel "[Name]" Data This setting is available for most channels. Define how data will be displayed. Choose between: Display act ual values in [unit]: Display the values in the unit shown. Display in percent of maximum: Calculate and show percent values based on a maximum value. Provide a maximum below. Maximum ([unit]) This field is only visible if the percent of maximum setting is selected above. Enter a value that will be regarded as maximum. Please pay attention to the given unit. All percent values will be calculated based on this value. Please enter an integer value. Define in what color the channel will be displayed in graphs. Enter an integer value in pixels. Although the line width is not limited, we recommend using values between 1 and 7 only in order to achieve optimal results. This setting is only available for sensor channels which return absolute values. It is not available for sensors showing difference values, such as traffic sensors. Depending on this setting, the channel can not only show averages, but also minimum or maximum values in the graphs for the respective time spans. For example, in a 5 minutes graph, you can display maximum/minimum values within this time interval instead of the average. Choose between: Average: The channel shows average values. Minimum: The channel shows minimum values. Maximum: The channel shows maximum values. Decimal Places Define how many decimal places of the channel's data will be displayed in graphs and tables. Choose between: Aut omat ic : Let PRTG choose how many decimal places will be used for optimal viewing results. All: Force display of all available decimal places. Cust om: Manually define the number of decimal places. If you choose this option, an additional field will appear. Please enter an integer value there.
Line Width
Value Mode
08.10.2013
1569
Edit Channel "[Name]" Spike Filter A spike filter can be used to correct obviously faulty monitoring data. Sometimes, sensors report enormously high or far too low values; due to an error in data transmission, or due to incompatibilities of the physical device you are monitoring. This can make graphs unreadable. A spike filter can compensate for these flaws. When enabled values above and below a certain limit are disregarded in the monitoring data for graphs and tables. Note: The monitoring data itself will not be changed (but only the presentation of the data) and this setting is valid for all data of this channel (also the historic data). Choose between: Disable Filt ering : Display all data as it is; do not filter out spikes. Enable Filt ering : Enable a filter to remove spike values. Additional fields appear below. Note: The spike filter option is not available for the channel Downt ime. Spike Filter Max. Value [unit] This field is only visible if spike filter is enabled above. Specify the maximum value allowed in the channel's data. All values above this value will be disregarded in graphs and tables. Please enter an integer value or leave the field empty. This field is only visible if spike filter is enabled above. Specify the minimum value allowed in the channel's data. All values below this value will be disregarded in graphs and tables. Please enter an integer value or leave the field empty. Define how the vertical axis for the channel is displayed in graphs. Choose between: Aut omat ic Scaling : Let PRTG decide on the optimum scaling; usually ranging from the minimum to the maximum value. PRTG will use one single scale for each unit label only. Manual Scaling : Define the scaling manually. Additional fields appear below. Defining manual axis scaling can make low values better visible in your graph; but it may result in a chart with multiple vertical axis for the same unit label. Note: Settings for this option are ignored if Chart Type St ack channels on t op of each ot her or Show in and out t raffic as posit ive and negat ive area chart (available for traffic sensors) is enabled in the sensor's Set t ings tab. Vertical Axis Maximum [unit] This field is only visible if vertical axis scaling is enabled above. Specify the maximum value that will be used on the vertical axis for the channel. Enter an integer value.
Spike Filter Min. Value [unit]
Vertical Axis Scaling
1570
08.10.2013
Edit Channel "[Name]" Vertical Axis Minimum [unit] This field is only visible if vertical axis scaling is enabled above. Specify the minimum value that will be used on the vertical axis for the channel. Enter an integer value. The channel can affect the status of the sensor it is part of. By entering limits, you can define when the sensor will enter a Warning or Down status; depending on the channel's data. Using this function, you can e.g. set a traffic sensor (which is usually never in a down state) to error when certain limits that you consider critical are reached. Choose between: Disable Limit s: Do not use the channel's data to control the sensor's status. Enable Limit s: Define limits. Additional fields appear below. The sensor belonging to the channel will enter a Warning or Down status when limits are undercut or overrun. Note: The limits option is not available for the channel "Downtime". Upper Error Limit [unit] This field is only visible if limits are enabled above. Specify an upper limit for an error state. If the channel's values overrun this value, the sensor will be set to Down. Note: While a sensor shows a Down 115 status triggered by a limit, it will still receive data in its channels. Please enter a decimal value or leave the field empty. This field is only visible if limits are enabled above. Specify an upper limit for a warning state. If the channel's values overrun this value, the sensor will be set to Warning . Please enter a decimal value or leave the field empty. This field is only visible if limits are enabled above. Specify a lower limit for a warning state. If the channel's values undercut this value, the sensor will be set to Warning . Please enter a decimal value or leave the field empty. This field is only visible if limits are enabled above. Specify a lower limit for an error state. If the channel's values undercut this value, the sensor will be set to Down. Note: While a sensor shows a Down 115 status triggered by a limit, it will still receive data in its channels. Please enter a decimal value or leave the field empty. This field is only visible if limits are enabled above. Enter an additional message. It will be added to the sensor's message when entering a Down status. Please enter a string or leave the field empty.
Limits
Upper Warning Limit [unit]
Lower Warning Limit [unit]
Lower Error Limit [unit]
Error Limit Message
08.10.2013
1571
Edit Channel "[Name]" Warning Limit Message This field is only visible if limits are enabled above. Enter an additional message. It will be added to the sensor's message when entering a Warning status. Please enter a string or leave the field empty.
Click on Save to store your settings or Cancel your changes.

278
279
1566
1563
1573
1572
08.10.2013
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 11 Sensor Notifications Settings
6.11
Sensor Notifications Settings

The status or the data of a sensor can trigger notifications. Using this mechanism, you can configure external alerting tailored to you needs.
Example of Notific ation Trigger Settings
Note: Although it's the sensors that activate a trigger, you can set notification triggers higher in the hierarchy (for example for groups or devices), thus defining triggers for multiple sensors using the inheritance mechanism 82 .
Note
This section describes one of three steps to set up the notification system in PRTG. A complete notification setup involves: 1. Check and set up the Not ificat ion Delivery settings. This will tell PRTG how to send messages. For detailed information, see Sy st em Administ rat ionNot ificat ion Delivery 1702 . 2. Check and set up several Not ificat ions. This will define the kind of message and its content. For detailed information, see Account Set t ingsNot ificat ions 1678 . 3. Check and set up Not ificat ion Triggers for objects. These will provoke the defined notifications. For detailed information, see Sensor Not ificat ions Set t ings 1573 . For background information, please see Not ificat ions
1609
section.
Available Notification Triggers Settings

On an object's detail page, click on the Not ificat ions tab to change sensor notification triggers. The available options are the same for all objects. When defining triggers for probes, groups, or devices, they can be inherited down to sensor level.
27.11.2012
1573
Triggers t hat can be inherit ed from parent object (s) You see a list of all notification triggers that are defined higher in the hierarchy. The list is empty when there are no triggers defined in groups or devices above the current object. You can see the type and the notifications that are executed once this trigger is activated. Trigger Inheritance Define whether the triggers shown above will be handed on to the current object. Choose between: Inherit t rigger(s) from parent object (s): Use the triggers shown above. Only use t riggers defined for t his object : Do not use the triggers shown above; for this object only use the triggers defined below. This setting is valid for all triggers shown above. It is not possible to only select some of them.
You can set up one or more of the following triggers, each with different setting options. Which trigger types will be visible depends on the kind of object you're editing: Add State Trigger Add Speed Trigger
1574
1576
Add Volume Trigger
1578
Add Threshold Trigger Add Change Trigger

1581
1579
All notification triggers can be created in a very easy way, forming natural sentences. There are different options for every type.
Add State Trigger

Define a trigger that is activated when a sensor changes its current status. This is the most common reason to send out notifications. Click on the Add St at e Trigger button to add a new trigger, or click on the Edit button next to an existing notification to change it. Then define settings as described below. Every trigger will provoke one or more notification(s) 1678 to be executed.
St at e Trigger When sensor is... Select the condition that will trigger the notification. The trigger will be activated when a sensor enters the selected status. Choose from the drop down menu:
1574
27.11.2012
St at e Trigger Down: The trigger will be prompted if a sensor changes to a Down status. Warning : The trigger will be prompted if a sensor changes to a Warning status. Unusual: The trigger will be prompted if a sensor changes to an Unusual status. Part ial Down: The trigger will be prompted if a sensor changes to a Down (Part ial) status (available in a cluster 76 configuration). ...for at least ... seconds Define how many seconds will be waited before a notification is provoked. This can avoid false alarms in case a sensor 'flickers' and, for example, changes to a down status for just a few seconds. If the selected condition (i.e. the sensor status) persists after the defined time in seconds, the notification will be triggered. Please enter an integer value. Select a notification that will be triggered if the condition (i.e. the sensor status) selected is true and the latency time defined has elapsed. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Set t ings Not ificat ions 1678 setttings. You can also choose no not ificat ion in order to only use other conditions for this trigger. Define an escalation latency in seconds. A second notification can be triggered if this number of seconds has passed since the sensor status has entered the defined condition. Use this to automatically escalate a notification in case a problem persists for a longer time. Please enter an integer value. Select a (second) notification that will be triggered if the condition (i.e. the sensor status) selected is true and the escalation latency time defined has elapsed. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Set t ingsNot ificat ions 1678 settings. You can also choose no not ificat ion in order to only use other conditions for this trigger. Define an interval in minutes in which the second (escalation) notification will be sent repeatedly. The second (escalation) notification defined will be resent every x minutes. Please enter an integer value.
...perform...
When condition continues for at least ... seconds
...perform...
...and repeat every ... minutes
27.11.2012
1575
St at e Trigger When condition clears perform... Select a notification that will be triggered if the condition (i.e. the sensor status) selected is not true any more because the sensor's status has changed again. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Set t ingsNot ificat ions 1678 setttings. You can also choose no not ificat ion in order to only use other conditions for this trigger. Click on the Save button to save your settings. Click on the Delet e button next to an existing notification trigger to delete it.
Save Delete
Add Speed Trigger

Define a trigger that is activated when a sensor (e.g. a traffic sensor) changes its current speed. Click on the Add Speed Trigger button to add a new trigger, or click on the Edit button next to an existing notification to change it. Then define settings as described below. Every trigger will provoke one or more notification(s) 1678 to be executed.
Speed Trigger When ... channel From the drop down menu, select the channel which's data will be regarded for this comparison. Select Primary to generally use a sensor's primary channel (this can be defined in the sensor's settings 278 ) or choose a specific channel name from the list (there are different channels for every sensor type). All following settings for this trigger will be based on the chosen channel. Select the condition that will trigger the notification. Choose from the drop down menu: Above: The trigger will be prompted if the value of the selected channel overruns a defined value. Below: The trigger will be prompted if the value of the selected channel undercuts a defined value. Equal To : The trigger will be prompted if the value of the selected channel is the same as a defined value. Not Equal To : The trigger will be prompted if the value of the selected channel is different than a defined value. [value] Define the value the channel's data will be compared with. Please enter an integer value.
...is...
1576
27.11.2012
Speed Trigger [scale] From the drop down menu, select the unit in which you entered the [value] above. [scale] and [t ime] together define the unit for the given value. If the channel's data is shown in a different unit PRTG will automatically convert values internally. Choose between: bit kbit mbit gbit t bit By t e KBy t e MBy t e GBy t e TBy t e [time] Select the time for the scale (so you create a scale per time designation). Choose from the drop down menu: second minut e hour day [scale] and [t ime] together define the unit for the given value. If the channel's data is shown in a different unit PRTG will automatically convert values internally. ..for at least ... seconds Define how many seconds will be waited before a notification is provoked. This can avoid false alarms in case a channel reaches a limit for just a few moments. If the combined channel condition of [value], [scale], and [t ime] persists after the defined time span, the notification will be triggered. Please enter an integer value. Select a notification that will be triggered if the combined channel condition of [value], [scale], and [t ime] is true and the latency time defined has elapsed. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Set t ingsNot ificat ions 1678 settings. You can also choose no not ificat ion in order to only use other conditions for this trigger.
...perform...
27.11.2012
1577
Speed Trigger When condition clears perform... Select a notification that will be triggered if the combined channel condition of [value], [scale], and [t ime] is not true any more because the channel's value has changed again. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Set t ingsNot ificat ions 1678 settings. You can also choose no not ificat ion in order to only use other conditions for this trigger. Click on the Save button to save your settings. Click on the Delet e button next to an existing notification trigger to delete it.
Save Delete
Note: No escalation notification and no repeat are available for this trigger type.
Add Volume Trigger

Define a trigger that is activated when a sensor (e.g. a traffic sensor) reaches a certain volume limit in a specified time. Click on the Add Volume Trigger button to add a new trigger, or click on the Edit button next to an existing notification to change it. Then define settings as described below. Every trigger will provoke one or more notification(s) 1678 to be executed.
Volume Trigger When ... channel From the drop down menu, select the channel which's data will be regarded for this comparison. Select Primary to generally use a sensor's primary channel (this can be defined in the sensor's settings 278 ) or choose a specific channel name from the list (there are different channels for every sensor type). All following settings for this trigger will be based on the chosen channel. Define the value the channel's data will be compared with. If the channel's data overruns this value, a notification will be triggered. Please enter an integer value. From the drop down menu, select the unit in which you entered the [value] above. [scale] and [t ime] together define the unit for the given value. If the channel's data is shown in a different unit PRTG will automatically convert values internally. Choose between: By t e KBy t e MBy t e GBy t e
...has reached... [value]
[scale]
1578
27.11.2012
Volume Trigger TBy t e per [time] Select the time for the scale (so you create a scale per time designation). Choose from the drop down menu: Hour Day Week Mont h [scale] and [t ime] together define the unit for the given value. If the channel's data is shown in a different unit PRTG will automatically convert values internally. ...perform... Select a notification that will be triggered if the [value] in the combined unit of [scale] and [t ime] is overrun. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Set t ingsNot ificat ions 1678 settings. You can also choose no not ificat ion in order to only use other conditions for this trigger. Click on the Save button to save your settings. Click on the Delet e button next to an existing notification trigger to delete it.
Save Delete
Note: No escalation notification, no repeat, and no notification when condition clears are available for this trigger type.
Add Threshold Trigger

Define a trigger that is activated when a sensor reaches specific values. Click on the Add Threshold Trigger button to add a new trigger, or click on the Edit button next to an existing notification to change it. Then define settings as described below. Every trigger will provoke one or more notification(s) 1678 to be executed.
Threshold Trigger When ... channel From the drop down menu, select the channel which's data will be regarded for this comparison. Select Primary to generally use a sensor's primary channel (this can be defined in the sensor's settings 278 ) or choose a specific channel name from the list (there are different channels for every sensor type). All following settings for this trigger will be based on the chosen channel.
27.11.2012
1579
Threshold Trigger ...is... Select the condition that will trigger the notification. Choose from the drop down menu: Above: The trigger will be prompted if the value of the selected channel overruns a defined value. Below: The trigger will be prompted if the value of the selected channel undercuts a defined value. Equal To : The trigger will be prompted if the value of the selected channel is the same as a defined value. Not Equal To : The trigger will be prompted if the value of the selected channel is different than a defined value. [value] Define the value the channel's data will be compared with. It will be directly compared to the channel's data. Please enter values in the smallest possible (base) unit, for example, in bytes or seconds. Please enter an integer value. Define how many seconds will be waited before a notification is provoked. This can avoid false alarms in case a channel reaches a limit for just a few moments. If the defined channel condition persists after the defined time span, the notification will be triggered. Please enter an integer value. Select a notification that will be triggered if the defined channel condition is true and the latency time defined has elapsed. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Set t ingsNot ificat ions 1678 settings. You can also choose no not ificat ion in order to only use other conditions for this trigger. Select a notification that will be triggered if the defined channel condition is not true any more because the channel's value has changed again. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Set t ings Not ificat ions 1678 settings. You can also choose no not ificat ion in order to only use other conditions for this trigger. Click on the Save button to save your settings. Click on the Delet e button next to an existing notification trigger to delete it.
..for at least ... seconds
...perform...
When condition clears perform...
Save Delete
Note: No escalation notification and no repeat are available for this trigger type.
1580
27.11.2012
Add Change Trigger

Define a trigger that is activated by a 'on change' trigger. Some sensors offer the option to send such a trigger whenever sensor values have changed. Click on the Add Change Trigger button to add a new trigger, or click on the Edit button next to an existing notification to change it. Then define settings as described below. Every trigger will provoke one or more notification(s) 1678 to be executed.
Change Trigger When sensor changes perform... Select a notification that will be triggered whenever a compatible sensor sends a 'change notification'. You can enable this option in the settings 278 of some sensors. The notification trigger will be activated immediately whenever a sensor sends an 'on change' trigger. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Set t ings Not ificat ions 1678 settings.
Note: There are no other options available for this trigger type.

278
279
1566
1563
1573
Object Settings Overview

For more general information about object settings, please see section Object Set t ings
133
27.11.2012
1581
Part 7
Ajax Web InterfaceAdvanced Procedures
27.11.2012
1583
Part 7: Ajax Web InterfaceAdvanced Procedures |
Ajax Web InterfaceAdvanced 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 96 , 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 1710 by the user). The following sections introduce more advanced procedures in the Ajax Graphical User Interface (GUI).
1584
27.11.2012
Part 7: Ajax Web InterfaceAdvanced Procedures |
Ajax Web InterfaceAdvanced ProceduresTopics

Toplist s
1586
Arrange Object s Clone Object Mult i-Edit

1595 1592
1591
Creat e Device Templat e Geo Maps

1603
1600
Not ificat ions Libraries Report s Maps Set up

1655 1619
1609
1636
1671

94
180
Ajax Web Int erfaceDevice and Sensor Set up
Related Topics
Ent erprise Console
1744
1796
27.11.2012
1585
Part 7: Ajax Web InterfaceAdvanced Procedures | 1 Toplists
7.1
Toplists
Packet Sniffer and xFlow (including IPFIX) sensor types can not only measure the total bandwidth usage, they can also break down the traffic by IP address, port, protocol, and other parameters. The results are shown in so-called Toplist s. This way PRTG is able to tell which IP address, connection, or protocol uses the most bandwidth. PRTG looks at all network packets (or streams) and collects the bandwidth information for all IPs, ports, and protocols. At the end of the toplist period, PRTG stores only the top entries of each list in its database.
Only Top Entries are Stored

Storing all available analysis data in a database during the analysis process would create a huge amount of data which would be very slow to transfer between probe and core and also retrieving data would be too slow. By storing only the top 100 entries for short periods of time it is possible to reduce the amount of data to a minimum while still being able to identify devices with huge bandwidth usage.
Toplists Overview
Toplist s are available for xFlow, IPFIX, and Packet Sniffer sensors 279 only. Toplist graphs are displayed right on the sensor overview page. By default, there are three different toplists predefined for each sensor: Top Connect ions: Shows bandwidth usage by connection. Top Prot ocols: Shows bandwidth usage by protocol. Top Talkers: Shows bandwidth usage by IP address.
1586
08.10.2013
Toplist Top Protoc ols for a Pac ket Sniffer Sensor
Click on one of these items to view a distribution chart, and a list of source and destination IP and port, protocols, kind of traffic in different channels, etc. It depends on the selected list, which information is available. Click on an entry in the Available Periods lists on the left side to view data for a certain time span. By default, a time span of 15 minutes, and a top count of 100 is set. This means, for every list, you can view the top 100 measured in 15 minutes intervals. In order to print a toplist, click on the Print t his t oplist button to view a printer-friendly version and then use the print option of your browser to send it to your printer. With Back t o Sensor Overview you will return to the current sensor's overview tab. In the sensor overview, you can add or delete new toplists, or edit existing ones.
08.10.2013
1587
Add
Click on the Add Toplist item in the sensor overview to create a new toplist. The available options are the same as for editing 1588 a list.
Edit
Click on the small gear icon of a toplist item in the sensor overview to modify it.
Toplist Set t ings Name Type Enter a meaningful name to identify the toplist. Top Talkers (Which IPs uses t he most bandwidt h?): Shows bandwidth usage by IP address. Top Connect ions (Which connect ions use most bandwidt h?): Shows bandwidth usage by connection. Top Prot ocols (Which prot ocols use t he most bandwidt h?): Shows bandwidth usage by protocol. Cust om (Creat e y our own t oplist ): Create your own list by selecting criteria below. Toplist is based on This setting is only available if a custom type is selected above. Select the fields you want to add to the toplist by adding a check mark in front of the respective field name. The available options depend on the type of sensor used. They're different for Packet Sniffer, NetFlow v5, v9 (and IPFIX), and sFlow. Note: For performance reasons, only select the field you really want to monitor. Please see Performance Considerat ions 1589 section below. Define the interval for the toplist in minutes. Please enter an integer value. Toplists always cover a certain time span. Once a time span has passed, the top results are stored and a new toplist is started. Note: In order to avoid load problems on your probe system, please do not set this interval too long. Default setting is 15 minutes. Please see Performance Considerat ions 1589 section below. Define the length of your toplist. Only this number of entries will be stored for each period. Please enter an integer value. Note: In order to avoid load problems on your probe system, please do not set this value as low as possible. Default setting is 100, in order to store the top 100 entries for each period. Please see Performance Considerat ions 1589 section below.
Period (Minutes)
Top Count
1588
08.10.2013
Toplist Set t ings Probe/Core Data Transfer Define how the probe sends the toplist dataset to the core server. Choose between: According t o sensor int erval (default ): Send data in the interval defined in the settings of the sensor this toplist is created for. This can create a lot of bandwidth and CPU load with many sniffer sensors, complex traffic, or long toplists. Wait unt il t oplist period ends (less cpu&bandwidt h usage): Send data once a toplist period has finished. This will create less bandwidth usage and CPU load, but you cannot see the current toplist in the web interface, but only toplists with finished periods. For more information, please see Performance Considerat ions section below. Memory Limit (MB)
1589
Define the maximal amount of memory in MB the probe will use for collecting the different connection information. Every toplist adds its amount to the probe's memory consumption. Increase this value if the number of captured connections is not sufficient. Please enter an integer value.
Delete
Click on the small trashcan icon of a toplist item in the sensor overview to delete it. Confirm with Delet e to delete the list.
Performance Considerations
If you create toplists for data lines with considerable usage (e.g. steady bandwidth over 10 Mbit/s) or if the traffic is very diverse (i.e. many IPs/ports with only little traffic each) please consider the following aspects: The probe gathers all information needed for the toplist in RAM memory during each period. Only the top 100 entries are transferred to the core. Depending on the toplist type and traffic patterns the required memory can grow into many megabytes. Choose periods as short as desirable (especially important when traffic has a high level of diversity) to minimize memory usage. Memory requirements can grow almost exponentially with each field used in the toplists definition (depending on traffic pattern). Avoid complex toplists for high and diverse traffic. For example, Top Connect ions (5 fields) needs a lot more memory than Top Talkers (1 field).
08.10.2013
1589
If you experience high bandwidth usage between core and probe try to choose the Wait unt il t oplist period ends option. If you experience Data incomplete, memory limit was exceeded messages try to increase the memory limit in the toplist's settings but keep an eye on the probe process' memory usage.
Notes
When working with toplists be aware that privacy issues can come up for certain configurations of this feature. Using toplists you can track all single connections of an individual PC to the outside world and you, as the administrator, must make sure that it is legal for you to configure PRTG like this. Keep in mind that toplists can be viewed through the web interface. You may not want to show lists of domains used in your network to others. So you should restrict access to sensor types having toplists. Note that diagrams for, e.g., top connections are not meant to be used for detailed analysis. Rather they should indicate if there is an uncommon bigger change in this toplist.
More
Monit oring Bandwidt h via Flows
1820
Monit oring Bandwidt h via Packet Sniffing
1818
1590
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 2 Arrange Objects
7.2
Arrange Objects
There are several possibilities to move objects within the device tree, or to move objects from one probe or group to another.
Manage Tab in Device Tree

While viewing the device tree (or parts of it), click on the Manage tab to switch to a tree view in which you can move monitoring objects using drag&drop in your browser window. For more information, see section Manage Device Tree 211 .
Device Details View: Arrange Sensors

When viewing the Overview tab of a device, you will see a list of all sensors on this device.
Arrange Sensors on a Dev ic e
Click on the column headers Pos, Sensors, St at us, or Priorit y to re-sort the sensor list. To change a sensor's position, simply click on the small grip at the beginning of the row, drag it to the position you like, and drop it. Changes take effect immediately.
Context Menu: Move

You can also right-click on any object to show the Context Menu 148 . Select the Move entry to move sensors, devices, or groups up and down, or to move groups or devices into other groups or on other probes.
08.10.2013
1591
Part 7: Ajax Web InterfaceAdvanced Procedures | 3 Clone Object
7.3
Clone Object
If you want to duplicate an object with the same settings, you can clone it. Cloning is available for groups, devices, and sensors. Unlike the results when using the Creat e Device Templat e 1600 option, a cloned device will contain all objects of the original device, regardless of whether they bring about working sensors or not (which often depends on the settings of the cloned device). Note: You cannot clone 'fixed' objects, such as the root group or a probe device. You cannot clone the sensor types QoS (Qualit y of Service) One Way Sensor 771 and QoS (Qualit y of Service) Round Trip Sensor 777 . Note: If you want to clone a sensor, a faster way will be to use the Manage Device Tree function. To start, right click on an object in your device tree, and from the context menu Clone... . An assistant will appear.
148 211
, select
1592
08.10.2013
Cloning a Sensor
08.10.2013
1593
Clone Object Settings

Object To Be Cloned Object Several fields show information about the object that is to be cloned. The available information varies depending on whether you are about to clone a group, device, or sensor.
New Object's Name New Object Name Enter a name for the cloned object. By default, the old name is filled in, proceeded by Clone of. This field is only available when cloning a device. Enter the IP address or DNS name for the new device.
New IP Address/DNS Name
Please choose a group/device t o add t he new object t o From the device tree shown, choose an object you want to add the cloned object to. When cloning a group or device, select a group. When cloning a sensor, select the device you want to add it to.
Click on the Cont inue button to store your settings. If you change tabs or use the main menu, all changes to the settings will be lost! You will be redirected to the newly cloned object's overview 118 page. By default, all sensors are initially paused to give you the chance to change settings before monitoring starts. Please check the settings 133 and resume 147 monitoring.
Related Topics
Creat e Device Templat e Manage Device Tree
211
1600
1594
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 4 Multi-Edit
7.4
Multi-Edit
Device and sensor table lists, as well as some other lists, offer multi-edit functionality. With this, you can bulk edit the properties of many objects at a time. Multi-edit is also available in the Management tab if you select multiple objects by holding down the Ctrl key (see Manage Device Tree 212 ). Note: Using multi-edit, not all settings can be changed. PRTG will offer only settings which all selected objects have in common. Note: The multi-edit option is not available for the standard user groups Administrators and PRTG Users Group.
1715
PRTG
Example of a Table List
Start Multi-Edit in Lists

Start with viewing a table list. For example, choose Sensors | By Ty pe | ... or Devices | Device List | ... from the main menu. Table lists are also available in the Overview tab of Libraries 1619 , Maps 1655 , Report s 1636 , Not ificat ions 1609 , and Schedules 1687 . In a table list, start multi-edit by selecting objects using the check boxes on the right. You can also select all objects of the current page at once by clicking the check box in the table header. Use the It em Count option to view more items per page. As soon as you select one or more objects, the multi-edit menu will appear at the top of the table and chosen objects are shaded in green.
Multi Edit Menu
19.07.2013
1595
Depending on the object type different functions are available. For example, for sensor lists, some frequently used functions are available as quick buttons, such as Delet e, Pause, Resume, Check Now, and Edit . If you click on one of those buttons, the respective function will be applied to all selected objects. Other options are available in the drop down menu. Hover the arrow symbol to show it.
Example of Multi Edit Drop Down Menu
The options in this menu vary depending on the kind of objects selected. If you choose an entry, the respective function will be applied to all selected objects. Once you have selected the objects you want to change settings for, click on the screwdriver symbol to enter the edit settings mode. For available settings, please see below.
Start Multi-Edit in Management Tab

In the device tree, start by clicking the Management tab. You can use Multi-Edit for object settings: Hold down the Ctrl key and select multiple groups, devices, or sensors (one of a kind). In the appearing dialog, select the settings you would like to edit, change the according values and click on Save. The changes will be applied to all selected objects. For available settings, please see below.
Edit SettingsSettings
In the multi-selected sensors' Set t ings tab within the Edit Mult iple Object s popup, you can edit most of the sensors' properties which they have in common, respectively in the Edit Mult iple Object s popup for devices. For example, for devices or sensors, edit the name, tags, priority, scanning interval, access rights, etc.
1596
19.07.2013
Example of Dev ic e Settings in Multi-Edit Mode
The available options depend on the selected objects and will vary according to your selection. When editing multiple sensors, it may be useful to only choose one certain sensor type from the list, so that there are as much settings as possible available for multi-edit. In order to change a property, add a check mark in front of the respective line and then change the settings. The new setting(s) will be applied to all objects you selected for multiedit. All properties that are not activated with a check mark will remain unchanged. Click on the OK button to store your settings. If you close the popup via the X or Cancel button, all changes to the settings will be lost!
19.07.2013
1597
Edit SettingsChannel Settings

The Channel Set t ings tab in the Edit Mult iple Object s popup is only available when editing sensors. You can edit settings of all channels which the selected sensors have in common. Select a channel name from the Channel list. You can then edit, for example, channel name, ID, display settings, colors, scaling, limits, etc.
Example of Sensor Channel Settings in Multi-Edit Mode
1598
19.07.2013
The available options depend on the selected sensors and will vary according to your selection. It may be useful to only choose one certain sensor type from the list, so that there are as much channel settings as possible available for multi-edit. In order to change a property, add a check mark in front of the respective line and then change the channel settings. The new setting(s) will be applied to all sensors you selected for multi-edit. All properties that are not activated with a check mark will remain unchanged. Click on the OK button to store your settings. If you close the popup via the X or Cancel button, all changes to the settings will be lost!
Related Topics
Working wit h Table List s Manage Device Tree
211 141
19.07.2013
1599
Part 7: Ajax Web InterfaceAdvanced Procedures | 5 Create Device Template
7.5
Create Device Template

If you want to add a certain device several times, you can create a device template from an existing device in your device tree. When creating a device template, information for nearly all sensors on this device will be saved to a template file which you can later use in combination with Aut o-Discovery 181 (restrictions apply for a few sensor types). From the sensors, all relevant settings will be saved, except those that refer to other objects, such as schedules, triggers, access rights, etc. They will automatically be reverted to Inherit . To start, right click on a device in your device tree, and from the context menu Creat e Device Templat e... . An assistant will appear.
148
, select
Create Dev ic e Template Assistant
Device Template Settings

File name for t he t emplat e File Name Enter a name under which the file will be stored. It will be stored with the extension .odt in the \PRTG Network Monitor \devicetemplates sub-directory of your PRTG core installation (of the Master node, if in a cluster). The file may not exist in this directory, otherwise you will see an error message. Enter a meaningful display name for the template, as it will appear in the web interface.
Template Name
1600
08.10.2013
You should see a success message indicating that your template file was saved. Finished! The device template is now stored in the program path of your PRTG core installation. Your device template file contains all sensors, including their settings, of the original device. During your next auto-discovery, choose the Aut omat ic sensor creat ion using specific device t emplat e(s) option and select the name of your newly created device template from the list. PRTG will then try to discover the stored sensor types on the new (or existing) device. If the physical device answers to a sensor request, the sensor is added to the PRTG device. Note: Numbers will be added to the original sensor names. For detailed information, please see Aut o-Discovery 181 section.
Settings That are Not Saved

There are a few settings which cannot be saved into a device template, and will therefore be set to default, such as the Dependency Type setting Mast er object for parent (in Schedules and Dependencies section), and Result Handling settings Writ e result do disk (as this is intended for debugging purposes only). Also, settings in the Access Right s section are not saved to avoid security flaws. Furthermore, due to internal restrictions, the following sensor types will not be saved into a device template: Core/Probe/Clust er Healt h DHCP HDD Healt h IPFIX IPFIX (Cust om) jFlow V5 jFlow V5 (Cust om) Net Flow V5 Net Flow V5 (Cust om) Net Flow V9 Net Flow V9 (Cust om) Packet Sniffer Packet Sniffer (Cust om) QoS (Qualit y of Service) Sensor Fact ory sFlow sFlow (Cust om) SNMP Trap Receiver Sy slog Receiver
08.10.2013
1601
WMI Volume (use WMI Free Disk Space (Mult i Drive) Sensor
1437
instead)
No Update of Device Templates

Once a device template is created, it is not possible to add additional sensors to it. If you want to create a template with an extended set of sensors, please create a new one. Note: When saving a new device template, all internal IDs of the sensors contained in this template are updated. Therefore, when applying a new template to an existing device, all sensors contained in this template will be newly created on this device, even if those sensors were previously created using (another) device template!
Related Topics
Clone Object
1592
Manage Device Tree
211
1602
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 6 Geo Maps
7.6
Geo Maps
With the PRTG Geo Maps feature you can visualize geographical information about your monitored objects. You can display the location of probes, groups, and devices in a graphical map on an object's details page, or on PRTG Maps 1655 . This feature is especially useful when you monitor networks which are spread over different locations, for example, in various cities of a country or all over the globe. For each probe, group, or device, you can enter Locat ion information. PRTG will use the first line of this information to query a geographical map which shows your objects. Your location specification will be resolved to global geographical coordinates by the PRTG core server with the help of an external map service provider. PRTG will connect to the specified maps provider to get map tiles. These are used to set up the graphical map. Then the defined locations will be marked with the corresponding object icons and their status 1606 on the map. You can select your favorite map tiles provider in Sy st em Administ rat ionSy st em and Websit e 1692 (setting Geo Maps). Geographical maps can be displayed on the device tree. PRTG will adjust the zoom of a map automatically such that all locations of a selected object can be displayed. You can also add geographical maps to PRTG Maps 1655 . For this concern, go to the PRTG Maps Designer 1660 (either in an existing map or creating a new one) and choose the entry Geo Maps from the properties menu on the right.
Example of Geo Maps in PRTG Ajax Web Interfac e
08.10.2013
1603
Using Geo Maps

In order to use geographical maps within the PRTG web interface , please make sure the following:
94
or Ent erprise Console
1744
1. In the system administration (within the web interface), select the maps provider and type you want to view. There, you will also find an option to disable geo maps integration if you do not want to use it. See section Sy st em Administ rat ionSy st em and Websit e 1692 (setting Geo Maps) for detailed information. 2. In your objects' settings 133 , add a city name, or address, or coordinates in the first line of the Locat ion field. As soon as you view the details of such an object, a geographical map will be shown. The Locat ion information will also be used when viewing objects in the Ent erprise Console 1744 or when adding Geo Maps objects to PRTG Maps 1655 . 3. Make sure your PRTG core server has access to the internet in order to obtain map tiles. If a proxy is mandatory in your network, please configure proxy settings accordingly. For details, please see Sy st em Administ rat ionSy st em and Websit e 1698 . For details about tile server domains, please see More 1607 section below.
Labeling Locations
You can define your own labels for locations of objects. For this concern, enter the desired label in the first line of the Locat ion settings and provide the geo coordinates of the location in the second line. In PRTG's geo map, this object will be displayed with the defined label.
1604
08.10.2013
Defining Loc ation New York City with Geo Coordinates and Label Big Apple
The location New York City will appear with the label Big Apple then:
08.10.2013
1605
Loc ation New York City with Label Big Apple
It is also possible to define the same label for different locations. For example, imagine your company's headquarter is spread over several different locations. For each object representing a dedicated headquarter in the PRTG device tree, enter its coordinates in the second line of the respective Locat ion settings and the label "Headquarter" in the first line. All corresponding objects will be displayed as "Headquarter". This way, you can easily find your desired objects on the map.
Map Icon Colors

On the geographical maps the different location icons will show the overall status at this location by using a color code. Following, all possible location states are listed ordered by their hierarchy:
1606
08.10.2013
Flag
Flag Color Red
Locat ion St at us Meaning Down At least one sensor at this location shows a red Down status. Hover the circle with the letter symbol in the legend to view the total number of alarms at this location. At least one sensor at this location is Down and the status was acknowledged by a PRTG user, applying the Acknowledge Alarm function. The Down states of all sensors at this location have to be acknowledgedif at least one sensor is unacknowledged down, this location will be displayed as Down. At least one sensor at this location shows a yellow Warning status. There is no sensor in a Down or Down (Acknowledged) status at this location. At least one sensor at this location shows an orange Unusual status. There is no sensor in a Down, Down (Acknowledged), or Warning status at this location. All sensors at this location are in a green Up status. There is no sensor in a Down, Down (Acknowledged), Warning , Paused, or Unusual status at this location. All sensors at this location show a blue Paused status. There is no sensor in a Down, Down (Acknowledged), Warning , Unusual, or Up status at this location. All sensors at this location have an Unknown status. There is no sensor in a Down, Down (Acknowledged), Warning , Unusual, Paused, or Up status at this location.
Bright-Red
Down (Acknowledged)
Yellow
Warning
Orange
Unusual
Green
Up
Blue
Paused
Black (Grey)
Unknown
Note: For detailed information about sensor states, please see Sensor St at es
115
section.
More
Knowledge Base: Which provider should I use for PRTG's "Geo Maps" feature? http://www.paessler.com/knowledgebase/en/topic/34603
08.10.2013
1607
Knowledge Base: Which domains and ports does the GeoMaps feature use? http://www.paessler.com/knowledgebase/en/topic/35823 Knowledge Base: Why does my street not appear on the Geo Map shown in PRTG? http://www.paessler.com/knowledgebase/en/topic/35653 Knowledge Base: How do I get a Google Maps API key for use in PRTG? http://www.paessler.com/knowledgebase/en/topic/32363 Knowledge Base: Which limitations apply when using the Google Maps API in PRTG? http://www.paessler.com/knowledgebase/en/topic/7913 Knowledge Base: How can I change the way markers look like in PRTG's geo maps? http://www.paessler.com/knowledgebase/en/topic/43153
1608
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 7 Notifications
7.7
Notifications
Notifications are used to send alerts to the user whenever PRTG discovers a defined status, such as slow or failing sensors, or when threshold values are breached. You can define an unlimited number of notifications allowing to use one, or more, of several communication channels like email, text messaging, and many more. For video instructions, please see the More 1610 section below.
Overview
Notifications can be triggered by: Sensor st at us changes For example, when a sensor changes status to Up or Down, if responses are slow or sensors show an Unusual status. Sensor value t hreshold breaches For example, when a sensor shows a request time higher than 1,000 ms for more than 30 minutes. Speed t hreshold breaches For example, when a traffic sensor shows more than 1 Mbit/s for more than 5 minutes. Volume t hreshold breaches For example, when a traffic sensor shows more than 1 Gbyte transferred in 24 hours. Sensor value changes For some sensors you can trigger a notification whenever the value changes, for example, when monitoring files on a hard disk drive. A notification can be one of these actions: Send Email Add Entry to Event Log Send Syslog Message Send SNMP Trap Send SMS/Pager Message Execute HTTP Action Execute Program Send Amazon Simple Notification Service (SNS) Message For details, see section Account Set t ingsNot ificat ions
1681
Note: Usually there are three successive attempts to deliver a notification. If all of these attempts fail, the notification is lost. Notifications can contain valuable sensor information, such as: Last error message
08.10.2013
1609
Part 7: Ajax Web InterfaceAdvanced Procedures | 7 Notifications
Last good/failed request Total downtime Total uptime Recent sensor history A direct link to the web interface
Notifications Setup
There are three steps to take in order to use notifications with PRTG. Please go through all of them: 1. Check and set up the Not ificat ion Delivery settings. This will tell PRTG how to send messages. For detailed information, see Sy st em Administ rat ionNot ificat ion Delivery 1702 . 2. Check and set up several Not ificat ions. This will define the kind of message and its content. For detailed information, see Account Set t ingsNot ificat ions 1678 . 3. Check and set up Not ificat ion Triggers for objects. These will provoke the defined notifications. For detailed information, see Sensor Not ificat ions Set t ings 1573 . See section Set t ing Up Not ificat ions Based on Sensor Limit s: Example step guide describing a potential notifications setup.
1611
for a step-by-
More
Video Tutorial: There is a video available on the Paessler video tutorials page. http://www.paessler.com/support/video_tutorials Knowledge Base: Notifications based on priorities http://www.paessler.com/knowledgebase/en/topic/31243
1610
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 7 Notifications 1 Setting Up Notifications Based on Sensor Limits: Example
7.7.1
Setting Up Notifications Based on Sensor Limits: Example

Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default. This section will show you exemplarily how to set up a notification for exceeded disk free limits. The approach for this specific use case is examined step by step. You can easily adapt it to declare limits for other sensor types. There are several steps to take in order to set up notifications based on limits: Step 1: Step 2:
1611
Provide necessary information about the delivery of notifications (SMTP and SMS). Create notifications, specifying the type of notification and its content.
1611
Step 3: 1613 Define thresholds that will change a sensor's status (this is not necessary for every kind of notification). Step 4: 1615 Add suitable triggers to objects which will evoke notifications if something is going wrong in your network. Step 5:
1616
Test if the created notification will be triggered and delivered correctly.
Note: When you set up your own notifications, you will not necessarily need to go through all the steps described here. In this section, our main goal is to give you a general idea of the notifications concept.
Step 1: Setting up the Notification Delivery

Before creating notifications, you first have to define how those notifications actually will be delivered to your email account, mobile phone, or pager. To do so, choose Set up | Sy st em Administ rat ion | Not ificat ion Delivery from PRTG's main menu bar. Specify the mechanism of SMTP delivery, sender email and name, as well as the HELO ident. For SMS delivery, select your service provider and provide the corresponding credentials. You can find details about notification delivery in section Sy st em Administ rat ionNot ificat ion Delivery 1702 .
Step 2: Setting up the Notification's Content

In order to get an informative message when a disk is running out of capacity, create a corresponding notification. Choose Set up | Account Set t ings | Not ificat ions from PRTG's main menu bar and click on the button Add New Not ificat ion. Give the notification an explanatory name; in our case you could use Disk Free Limit Notification. However, if you want to trigger this notification on a global level (for example, for a probe or group) such that it would not only apply to breached disk free limits, a general name would be more suitable (like the predefined notification "Email to Admin"). If you leave the default text of the newly created notification, it will already contain all necessary information, like: which sensor is affected, since when the sensor is affected, last value of this sensor,
08.10.2013
1611
etc. See section More

1616
for the other options you have here.
After providing this basic information, select the delivery method. In our case, we choose Send Email for this notification by marking the corresponding checkbox. Specify who will receive the notification, its subject, the format, the content of the email, and its priority. By default, the email notification will contain several information parameters about the evoking sensor: its name, status, time, message, location in the device tree, etc. Feel free to adjust email messages to your needs (see section More 1616 ). You can choose any other notification method, of course (see Account Set t ingsNot ificat ions 1681 ).
Creating an Email Notific ation
Once the notification is set up completely, click on Save. You will be redirected to the notifications overview page. You can now use this notification for every trigger on every object in your device tree.
1612
08.10.2013
Step 3: Define Limits

Before creating triggers that evoke notifications, first specify the limits which you want to apply to your disks. For example, if you want to be notified when a disk has exceeded 80% of its capacity, force the sensor into a Warning status at this utilization. You have several options to set limits for disk free sensors: Set limits checked against all disks in the settings of multi-drive sensors: WMI Free Disk Space 1437 , SNMP Linux Disk Free 1031 , SSH Disk Free 1175 Enable limits in Channel settings of single sensors You can be achieve both with Mult i-Edit
1595
Step 3.1: Define Limits in Sensor Settings (Multi-Disk Free Sensors Only)
You can set limits for sensors monitoring multiple disks directly via the Set t ings tab on a sensor's details page. Mult i-Edit 1596 for existing sensors is also possible. Open the settings of the selected sensor(s) and go to section Set limit s checked against ALL disks. There, for example, enable Percent age Limit Check. In the field Lower Warning Limit , enter the percentage suitable to your needs. In our example, this would be 20. Alternatively, you can use bytes to define a limit. However, we recommend using percentage values for more flexibility. This limit will apply to all channels of this sensor representing disks.
Setting Limits for all Disks
Note: This sensor setting is only available for multi-drive sensors. You can omit Step 3.1 for all sensors that are not from the type "disk free".
08.10.2013
1613
Step 3.2: Define Limits for Sensor Channels

In order to set specific limits for single disks, use the sensor's Channel settings. You can open channel settings via the gear icon in the respective channel gauge or in the channels table. Enable Limit s at the bottom of the channel settings dialog and specify your desired limits in the Lower Warning Limit field. This limit will only apply to the respective channel. Note: If you define channel limits when using the sensor's limit setting in the sensor's Set t ings tab at the same time, the first limit that applies will be considered. This way, you can individually define harder limits for single disks in a multi-disk sensor. All defined limits are valid side-byside. You have to take the approach via channel settings for sensor types that monitor only one (logical) disk, for example, the SNMP Disk Free Sensor 947 . For these sensor types, you can use Mult i-Edit 1598 if you want to apply the same limits for each of these sensors automatically. To see all sensors of this type at a glance, just filter for it: From PRTG's main menu bar, choose Sensors | By Ty pe | SNMP Disk Free. Mark the checkboxes of the sensors you want to add a limit for. Click the screwdriver symbol in the multi-edit bar. Open the Channel Set t ings tab. Select the channel you want to add a limit for; in this case it would be most likely the channel Free Space. Then Enable Limit s at the bottom of the dialog and enter the number in the correct field as described above. Once done, save these settingsthe new limit will apply to all channels with this name of the multi-edited sensors.
1614
08.10.2013
Setting Limits for Channels with Multi-Edit
Step 4: Setting up the Notification Trigger

You have specified limits to define when a sensor will go into a Warning (or Error) status. Now you can create the according triggers. The trigger we use in this example is the St at e Trigger. For details about other possible notification triggers, see section More 1616 . You can set up a St at e Trigger on any level in your device tree. For example, open a group containing the device(s) representing your disks. Go on the Not ificat ions tab. Click Add St at e Trigger. Set the trigger to "When sensor is Warning" and choose the notification you have created before ("Disk Free Limit Notification" or a more general one) from the drop down list. Adjust the other notification settings to your needs and save this new object trigger. Now you will be notified immediately when the capacity of one of your disks falls below the defined limit, in this case 20% free disk space.
08.10.2013
1615
Setting a Trigger for Disk Free Limit Notific ation
Step 5: Testing the Notification

Finally, test the notification which you have created. You can trigger this notification for test purposes immediately: From the main menu bar
165
, choose Set up | Account Set t ings | Not ificat ions.
For the respective notification, click on the corresponding Test button. Then, check if the notification was triggered and delivered correctly, depending on what delivery method you defined before. If you do not get a notification (or a defined action is not executed) at all, check the notification logs: From the main menu bar, choose Logs | Sy st em Event s | Not ificat ions. Look for the triggered notification in the table list (verifying that the notification delivery is set up correctly in general) and consider the corresponding message. See section Logs 137 for more information.
More
This section provides information about additional options you have when working with notifications. Not ificat ion Set t ings: You can create schedules to activate notifications only at specific times, for example, only on weekdays. In section Not ificat ion Summarizat ion you can choose between various options to avoid message floodings. Furthermore, define which user groups will have access to edit this notification. For details about notification settings, refer to section Account Set t ingsNot ificat ions 1678 . Cont ent of Emails: You can individually adjust the subject, content, header, and footer of emails to your needs. PRTG allows you to use placeholders here. See section Account Set t ingsNot ificat ions 1681 for details about editing subject and message, and section Sy st em Administ rat ion Sy st em and Websit e 1693 for details about editing header and footer of emails.
1616
08.10.2013
Ot her Triggers: An alternative to the state trigger would be to add a Threshold Trigger; then you would not need to set up limits explicitly, though, this trigger type would only be suitable for disk free sensors when using the trigger for single sensors, one by one. Free disk sensors have free space in percent as primary by default, other sensors have primary channels with the units bytes or seconds. However, threshold triggers only apply to the primary or total channel. General notification triggering by threshold might not work as expected for sensors of the "percentage" type. You can find all available triggers in section Not ificat ions 1609 . Add a Threshold Trigger to a sensor directly: Go on a sensor's detail page and select the Not ificat ions tab. Click on Add Threshold Trigger, select the desired channel, and provide the condition when this notification will be sent. In this example for free disk space, the setting would be "When Free Bytes C: (%) channel is Below 20 for at least 60 seconds perform Disk Free Limit Notification". Not ificat ions wit h Libraries: If your disk devices are spread over many groups, we recommend you to use a PRTG library 1619 for your disks. Choose Libraries | All diskspace sensors from the main menu bar, go on the Not ificat ions tab, and add a state trigger as described above. Note: Not all disk free sensor types might appear. You can add them to this library in the settings of the library node. There you can filter by type or tag 1629 and add missing sensors this way. You can also filter by priority and other sensor properties.
08.10.2013
1617
Creating a Library with all Diskspac e Sensors
1618
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 8 Libraries
7.8
Libraries
With PRTG's Libraries feature you can create special views of your device tree with up-to-theminute monitoring status information, arranged the way you want it.
Example of a Library
In this section: Int roduct ion

1619
St art Libraries Libraries List
1620
1620
Working wit h Libraries
1621
Introduction
Libraries is a powerful feature which enables you to create additional views of your device tree, which are updated with the same scanning interval as your device tree, showing the same monitoring data, but arranged in a way you want it. This is interesting if you want to show data in different ways, e.g. depending on target groups or use case. For example, you can create a library which contains an overview of all your bandwidth monitoring sensors, regardless of which device they're running on. Library features include: Create libraries containing nodes with monitoring objects from all over your configuration Show data from different PRTG probes in one library Show different branches of your device tree right next to each other Arrange sensors in a tree-like view regardless of which device they are running on
07.02.2013
1619
Filter your entire tree (or parts of it) for sensor type, state, or tag, showing only matching sensors You can create libraries easily, using drag&drop right within your browser. PRTG comes with several pre-configured standard libraries, which you can use right away. You can also change or delete them, if you like. The following libraries are automatically created when you install PRTG for the first time (visible for the PRTG Administrator user). Some of them will be initially empty, but as you add more sensors, they will be filled automatically according to the filter settings defined for the nodes of the libraries: All bandwidth sensors All CPU load sensors All diskspace sensors All memory sensors All VMware sensors Sensors grouped by priority Sensors grouped by state Note: Sensors which are added to libraries are not counted against the maximum number of sensors of your license.
Start Libraries
Click the Libraries entry from the main menu 168 to view or add custom views of your network's status and monitoring data. Hover to show other menu items. Choose between: 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
1622
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.
Libraries List
In the All view, you see a list of all existing libraries. Using the links next to a library name, you can perform the following actions. Click on the name of a library to view it.
1620
07.02.2013
Delet e: Delete this library. Clone: Create a clone of this library. Used by : Show which other monitoring objects use this library. Click on the Add Library button to add a new library. Please see also Working wit h Table List s 141 . Additionally, there is multi-edit available. This enables you to change properties of several objects at a time. For more details, please see Mult i-Edit List s 1595 section.
Working with Libraries

For detailed information on how to create and edit libraries please see the following sections. Libraries St ep By St ep Management
1626 1622
Libraries and Node Set t ings Cont ext Menus

1635
1629
07.02.2013
1621
Part 7: Ajax Web InterfaceAdvanced Procedures | 8 Libraries 1 Libraries Step By Step
7.8.1
Libraries Step By Step

In order to create a new library, follow the steps in this section. In the web interface, click on the Libraries entry in the main menu to show the libraries main screen. Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default. In this section: St ep 1: Add Library
1622
St ep 2: Add Library Nodes
1622
St ep 3: Set Library Node Display Set t ings St ep 4: View

1624
1623
Step 1: Add Library

Click on the Add Library button. An assistant is shown. Enter a Library Name, and define Tags and Access Right s, if you like. Click on Cont inue. For detailed information, see Libraries Set t ings
1629
section.
Add Library Assistant Step 1
Step 2: Add Library Nodes

Click to the Management tab. You will see a split screen: On the left side, your library is show (empty in the beginning), and on the right side, you see a less colorful view of your device tree, as known from the device tree's Management 211 tab.
1622
07.02.2013
Empty Library in Management Mode
From the device tree on the right side, drag objects and drop them on the library on the left side. Each dropped object will be added immediately as a new Library Node. Repeat this procedure as often as you wish until you have added all desired items to the library. Note: When adding single sensors to the library, there can only be one sensor in one library node. You can also create nested library nodes by adding a new node underneath an existing one. Drag and drop nodes within the library to change their position. If you want to change the monitoring object that is associated with a library node, you can change the Linked Object in the node's settings.
Step 3: Set Library Node Display Settings

You are still in the library Management tab. Right-click on the name of a Library Node and from the context menu, select Edit | Set t ings... to change the Node Display Set t ings. In this dialog, you can change the name of the library and its tags, as well as the linked object, node type, and filters.
07.02.2013
1623
These settings are available for each library node. You can choose to either show the Linked Object as a sub-tree of your device tree, or to view a collection of all sensors underneath the Linked Object . When selecting the sub-tree view, the library node will just look like a branch in your device tree, as shown in the screen shot below for the library node names "My Sub Tree".
Library with one Node Showing a Branc h of the Dev ic e Tree
When selecting a sensor collection view, only the sensors underneath the Linked Object are shown, omitting probes, groups, and devices. You can additionally filter by certain sensor Ty pe, St at us, and Tags. Only matching sensors will be shown. The screen shot below shows the same Linked Object as above, but in sensor collection view, additionally filtered for sensors with a bandwidt hsensor tag.
Library with one Node Showing a Collec tion of Bandwidth Sensors Only
For detailed information, see Libraries and Node Set t ings Display Settings) section.
1629
(OverviewLibrary Node
Step 4: View
Click on the Overview tab to see the final appearance of your library. You have the following options: Hover an object to view a popup window with recent monitoring and status data. Use the sensor state selection bar to select which sensors you want to see for the library: Simply remove check marks for sensor states you want to hide. Note: This function is the same you know from the device tree's Sensor Status Bar 107 . The setting is reset the next time you open the library. Use the Device Tree View selection in the page header bar 107 to change the size of the library display. Note: This function is the same you know from the device tree 109 .
1624
07.02.2013
Use the Search box in the page header bar 107 to search the library for a string in object names. Matching objects will be shown full-colored, all others will be grayed out while the filter is active. Click on the small x symbol in the search field to reset the filter. Note: This function is the same you know from the device tree 107 . It depends on the library's access rights and the currently logged in user account if it will be visible to other PRTG users. Also, clicking on objects (for example, on sensors) will lead to more detailed information about the object or to an error message indicating insufficient access rightsdepending on user account and access rights. In libraries, you can right-click objects to access their Cont ext Menus
1635
07.02.2013
1625
Part 7: Ajax Web InterfaceAdvanced Procedures | 8 Libraries 2 Management
7.8.2
M anagement
Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default. Click to the Management tab. You will see a split screen: On the left side, your library is show (empty in the beginning), and on the right side, you see a less colorful view of your device tree, as known from the device tree's Management 211 tab.
Empty Library in Management Mode
Add and Change Library Nodes

From the device tree on the right side, drag objects and drop them on the library on the left side. Each dropped object will be added immediately as a new Library Node. Repeat this procedure as often as you wish until you have added all desired items to the library. Note: When adding single sensors to the library, there can only be one sensor in one library node.
1626
07.02.2013
You can also create nested library nodes by adding a new node underneath an existing one. Drag and drop nodes within the library to change their position. If you want to change the monitoring object that is associated with a library node, you can change the Linked Object in the node's settings.
Set Library Node Display Settings

Right-click on the name of a Library Node and from the context menu, select Edit | Set t ings... to change the Node Display Set t ings. In this dialog, you can change the name of the library and its tags, as well as the linked object, node type, and filters. These settings are available for each library node. You can choose to either show the Linked Object as a sub-tree of your device tree, or to view a collection of all sensors underneath the Linked Object . When selecting the sub-tree view, the library node will just look like a branch in your device tree, as shown in the screen shot below for the library node names "My Sub Tree".
Library with one Node Showing a Branc h of the Dev ic e Tree
When selecting a sensor collection view, only the sensors underneath the Linked Object are shown, omitting probes, groups, and devices. You can additionally filter by certain sensor Ty pe, St at us, and Tags. Only matching sensors will be shown. The screen shot below shows the same Linked Object as above, but in sensor collection view, additionally filtered for sensors with a bandwidt hsensor tag.
Library with one Node Showing a Collec tion of Bandwidth Sensors Only
For detailed information, see Libraries and Node Set t ings Display Settings) section.
1629
(OverviewLibrary Node
Context Menus
On right-click, there are different context menus availablein the Management as well as in the Overview tab.
07.02.2013
1627
For detailed information, please see Cont ext Menus
1635
section.
1628
07.02.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 8 Libraries 3 Libraries and Node Settings
7.8.3
Libraries and Node Settings

Using the libraries tabs you can access all functionalities and settings for a library.
Libraries Tabs
Overview
Click on the Overview tab any time to show the current state of your library.
Library Node Display Settings

While in the Overview tab, click on a library node's name to change its settings. Or, while in the Management tab, right-click a library node's name and select Edit | Set t ings.. . from the context menu. In both cases, the following settings are shown. Note: You can only change the settings of a node if it contains monitoring objects already, e.g. groups, devices, or sensors. Basic Library Node Set t ings Library Node Name Tags Enter a meaningful name for the library node. Enter one or more tags, separated by space or comma. For example, you can use tags later to search for the library. Tags are not case sensitive.
Node Display Set t ings Linked Object Click on the reading-class symbol to change the object which is linked with this library node. A popup window will appear, showing the Object Select or 143 . Select what you want to view for this library node. Choose between: Show a subt ree of t he device t ree in t he library : View all objects underneath the linked object as a device tree. Show a collect ion of (filt ered) sensors in t he library : View all sensors underneath the linked object (only sensors are shown). You can combine several filters with each other (see below). Filter By Type This option is visible only if collection of sensors is enabled above. Select if you want to filter the sensor list by a certain type. Choose between: Show all sensor t y pes: Do not filter for a sensor type.
Node Type
08.10.2013
1629
Node Display Set t ings Show specific sensor t y pes only : Filter the sensor list of the linked object for certain sensor type(s). Note: This filter is applied in real-time. If the configuration underneath the linked object changes, the library node will show matching sensors accordingly. Select Sensor Types This option is visible only if filtering by type is enabled above. A list of all sensor types is shown, currently available sensor types are shown in bold letters for your convenience. Set a check mark in front of each sensor type you want to include in the library node view. You can also select and deselect all items by using the check box in the table head. Note: This filter is applied in real-time. If the configuration underneath the linked object changes, the library node will show matching sensors accordingly. Filter By Status This option is visible only if collection of sensors is enabled above. Choose between: Show all sensor st at es: Do not filter for a sensor status. Show sensors wit h a specific st at us only : Filter the sensor list of the linked object for sensors in certain states. Select Sensor States This option is visible only if filtering by sensor state is enabled above. A list of sensor states is shown. Set a check mark in front of each status you want to include in the library node view. Choose from: Unknown Up Warning Down Paused Unusual Down (Acknowledged) Down (Part ial) You can also select and deselect all items by using the check box in the table head. Note: This filter is applied in real-time. If the configuration underneath the linked object changes, the library node will show matching sensors accordingly.
1630
08.10.2013
Node Display Set t ings Filter By Tags This option is visible only if collection of sensors is enabled above. Choose between: Show all sensor t ags: Do not filter for a tag. Show object s wit h a specific t ag only : Filter the sensor list of the linked object for sensors with a certain tag. Note: The tag of a sensor can also be inherited 82 by a parent object. Select Tags This option is visible only if collection of sensors is enabled above. A list of all available tags is shown. Set a check mark in front of each tag you want to include in the library node view. You can also select and deselect all items by using the check box in the table head. Note: This filter is applied in real-time. If the configuration underneath the linked object changes, the library node will show matching sensors accordingly. Filter By Priority This option is visible only if collection of sensors is enabled above. Choose between: Show all priorit ies: Do not filter for the priority setting sensor.
145
of a
Show object s wit h specific priorit y only : Filter the sensor list of the linked object for sensors with specific priority. Note: The priority setting of a group, device, or sensor is ignored here; only the priority setting of the sensor itself is regarded. Select Priority This option is visible only if collection of sensors is enabled above. Define which priority setting sensors must have to appear in this collection. Set a check mark in front of each priority you want to include in the library node view. Choose from: ***** (highest ) **** *** ** * (lowest ) Note: This filter is applied in real-time. If the configuration underneath the linked object changes, the library node will show matching sensors accordingly. 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!
08.10.2013
1631
Note: After applying filters it might take several seconds for the changes to become visible. This is due to internal filter processes running in the background.
Management
Click on the Management tab to edit the contents of your library, for example, to add items to the library using drag&drop. For detailed descriptions, please see Management 1626 section.
Settings
Click on the Set t ings tab to open a library's general settings. Basic Library Set t ings Library Name Tags Enter a meaningful name for the library. Enter one or more tags, separated by space or comma. For example, you can use tags later to search for the library. Tags entered here are inherited 82 to all library nodes underneath. Tags are not case sensitive.
1632
08.10.2013
Access Right s User Group Access Define which user group(s) will have access to the object you're editing. A table with user groups and right is shown; it contains all user groups from your setup. For each user group you can choose from the following access rights: Inherit ed: Use the settings of the parent object. None: Users in this group cannot see or edit the object. The object does not show up in lists and in the device tree. Exception: If a child object is visible to the user, the object is visible in the device tree, though not accessible. Read: Users in this group can see the object and review its monitoring results. Writ e: Users in this group can see the object, review its monitoring results, and edit the object's settings. They cannot edit access rights settings. Full: Users in this group can see the object, review its monitoring results, edit the object's settings, and edit access rights settings. You can create new user groups in the Sy st em Administ rat ion User Groups 1715 settings. To automatically set all objects further down in the hierarchy to inherit this object's access rights, set a check mark for the Revert children's access right s t o inherit ed option. For more details about access rights, please see section User Access Right s 89 . Note: When giving access rights to a user group, all members of this user group will be able to see the objects in the library just as seen by the user who originally created the library. Click on the Save button to store your settings. If you change tabs or use the main menu, all changes to the settings will be lost!
Notifications
You can define notification triggers for any kind of object libraries. This is even possible for dynamic libraries which can change with every scanning interval, for example, when you filter a library for the sensor status or priority. For details about how to use notifications, please see section Not ificat ions 1609 .
Comments
08.10.2013
1633
History
Delete
You can delete the entire library any time by clicking on the trash symbol on the right.
1634
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 8 Libraries 4 Context Menus
7.8.4
Context M enus
On right-click, there are different context menus available.
Library Node Menu

While in the Overview or the Management tab, right-click on any library node to show its context menu.
Library Node Menu
Library Node Menu: Edit
Library Node Menu: Mov e
Select either Det ails... or Edit | Set t ings... to get to the Libraries and Node Set t ings Note: While in the Overview tab, these settings are also accessible via left-click on the node's name. Edit | Rename... will give you an option to rename the library node quickly.
1629
Remove from Library ... will remove this library node from the current library. Note: This will not delete any objects in your device tree. The Move | ... options will move the library node up and down within the library. Click on the Send Link by email entry to open a new email using your system's standard email client. It will contain a direct link to the page you're currently viewing.
Monitoring Objects Menus

In libraries there are the same Cont ext Menus 148 available you already know from the device tree. With one exception: While accessing these menus within libraries, the Move and Delet e options are disabled to avoid accidental changes to your device tree.
07.02.2013
1635
Part 7: Ajax Web InterfaceAdvanced Procedures | 9 Reports
7.9
Reports
Reports are used to analyze historic monitoring results over a specified time such as one or more days, one month, or an entire year. You can create reports for all, or only for certain sensors.
Introduction
PRTG includes a powerful reporting engine for ad-hoc, as well as scheduled report generation in HTML and PDF format. Thus, reports can be run on demand or on a regular basis (e.g. once a day). You can create reports for one single sensor, or you choose a range of sensors you want to create a report for. The content and layout of the report is controlled by the report template of your choice and is the same for all sensors in a report.
Report Sample
The sample above shows a report for a router device. You can see graphs for the last day, plus data tables with numeric results.
Start Reports
Click the Report s entry from the main menu 172 to view or add reports of your monitoring data. Hover to show other menu items. Choose between: All Calls the Reports feature where you can view or add reports of your monitoring data.
1636
27.11.2012
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.
Reports Overview
List of Reports
In the All view, you see a list of all existing reports. Every line shows information about one report: Period: The time span covered by the report. Schedule: Shows if a schedule is set to regularly execute the report automatically. Email: If a schedule and an email address is set in the report settings, this shows the email address the report is automatically sent to. Last Run: If a schedule is set in the report settings, this shows when the report was last run. Next Run: If a schedule is set in the report settings, this shows when the report will be run next. Using the Delet e link at the end of a line you can delete the report. Please see also Working wit h Table List s 141 . Additionally, there is multi-edit available. This enables you to change properties of several objects at a time. For more details, please see Mult i-Edit List s 1595 section. Click on the Add Report button to add a new report, or click on the name of an existing report to view and edit its settings. You can also run a pre-configured report easily by clicking on its name and then using the options in the Run Now tab. For both options, please see Report s St ep By St ep 1639 section.
27.11.2012
1637
Working With Reports

For detailed information on how to create, edit, and schedule reports, please see the following sections: Report s St ep By St ep View and Run Report s Report s Set t ings
1645 1639
1642
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 Up to 40 days 40 to 500 days
Minimum Level of Det ail (Average Int erval) Any 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 Monit oring Dat a Hist oric Dat a Report s
126 118
1638
27.11.2012
Part 7: Ajax Web InterfaceAdvanced Procedures | 9 Reports 1 Reports Step By Step
7.9.1
Reports Step By Step

In order to create a new report, or run an existing one, follow the steps in this section. In the web interface, click on the Report s entry in the main menu to show the reports main screen. Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default.
Quick Start: Run an Existing Report

PRTG is delivered with several pre-configured reports. In order to use one of them, click on a report's name in the reports main screen, select the Set t ings tab. The other steps are the same as for new reports. Although some settings are already given, we recommend checking the settings. For example, check the sensors that will be included in the report. For some reports that come with PRTG there are no sensors added yet. Continue with St ep 3 1640 in this section.
Step 1: Add Report

Click on the Add Report button to add a new report. An assistant is shown. You can define many settings. For a beginning, enter a Report Name.
Add Report Assistant
27.11.2012
1639
Step 2: Select a Template

In the Templat e section, select one of the report templates from the list. This will define the overall look of your report and affect in which detail (interval) monitoring data is included. For a detailed description on the available options, please see Report s Set t ings 1645 (Settings Template) section. If you're not sure, try with a template that appears suitable to you. You can change all settings later.
Step 3: Define Additional Settings

Select a Securit y Cont ext (best choose PRTG Sy st em Administ rat or, if available), your Timezone, and Paper Size and Orient at ion for PDF generation. For detailed information, please see Report s Set t ings 1645 (Settings) section.
Step 4: Select Nodes and Sensors

Choose the sensors you want to include in the report. First, define the Clust er Node the monitoring data will be taken from. Select a specific node from the list. If you select All nodes, a report with data from all of your cluster nodes will be created, but only the primary channel of every sensor will appear in the report. Every report will show monitoring results from sensor data. There are two ways to include sensors in a report: You can either add sensors manually, or by tag. In the Add Sensors by Tag field, enter a tag that matches the sensor range you want a report for. For example, enter the tag bandwidthsensor to include all sensors that measure bandwidth. PRTG suggests this tag as default when adding bandwidth sensors; so this tag typically gathers all bandwidth sensors, unless you haven't configured your system differently. You can enter several tags separated by space or comma. Use the Exclude Sensors by Tag field to explicitly remove sensors with certain tags from the bulk of tags defined above. Tagging is a great tool to group sensors or other objects. For more information, see Tags section. You can also leave the tag fields empty and only choose specific sensors manually later.
84
Step 5: Decide On a Schedule and Additional Settings

In the Report Schedule section, choose if you want to run the report on a regular basis or on demand only. Also choose which time Period will be covered by the report, and if you want to show percentiles, add report comments, or special access rights. For detailed information, please see Report s Set t ings 1645 (Settings) section. Click on the Cont inue button to store your settings. If you change tabs or use the main menu, all changes to the settings will be lost!
1640
27.11.2012
Step 6: Check and Adjust the Sensors Included

When settings are saved, switch to the Sensors Select ed by Tag tab to see a list of all sensors that were added by the tag(s) you defined in step 4. To change tags, go back to the Set t ings tab. You can additionally add sensors manually. To do so, switch to the Select Sensors Manually tab. See Report s Set t ings 1652 (Select Sensors Manually) section for detailed information. The final report will show sensors from both manual and by tag selection.
Step 7: Run Report

Switch to the Run Now tab, select the current or previous period, and in the Processing Opt ions select View Report as HTML. Click the Run Report button. The report will be generated in a new browser window or tab immediately. Depending on the number of selected sensors and the used template it may take a few minutes until you see the report. If you do not want to wait, close the newly opened browser window or tab and select a PDF option in the Processing Opt ions. Click on the Run Report button again. The report will then be generated in the background and you will get a ToDo 139 or email once it's finished. Note: For large PDF reports, PRTG will automatically split the output into separate files to avoid huge PDF files. You can change the number of sensors included into each PDF file by editing the report templates manually. See More 1654 section of Reports Settings 1645 .
27.11.2012
1641
Part 7: Ajax Web InterfaceAdvanced Procedures | 9 Reports 2 View and Run Reports
7.9.2
View and Run Reports

In the web interface, click on the Report s entry in the main menu to show the reports main screen. Click on a report's name to select it. Using the reports tabs you can access all functionalities and settings for this report. Click on the Go t o all report s button at the bottom of the page to return to the list of Reports.
Report Tabs
Run Now
In the Run Now tab you can execute a report immediately with the settings configured.
Run Report "[Name]" Report for Define the time span covered by the report. Choose between: Current Period: Use monitoring data of the current period. The actual time span depends on the report period type defined in the report's settings 1645 . It can be today, this week, this month, or this year. Previous Period: Use monitoring data of the last period. The actual time span depends on the report period type defined in the report's settings 1645 . It can be yesterday, last week, last month, or last year. Select A Period: Use monitoring data of a period other than current or previous. Select below. Select Dat e Range Manually : Define a custom time span for the monitoring data that will be used. Set start and end date below. Date Range This selection is only visible if the period option is enabled above. From the list, select a data range for which the report will be generated. The actual time spans shown depend on the available monitoring data and on the report period type defined in the report's settings 1645 . It can be days, weeks, months, or years. This selection is only visible if the date range option is enabled above. Define the begin of the time span for which the report will be generated. Click in the field and select a data from the calendar. Make sure you define a valid period.
Start Date
1642
03.05.2013
Run Report "[Name]" End Date This selection is only visible if the date range option is enabled above. Define the end of the time span for which the report will be generated. Click in the field and select a data from the calendar. Make sure you define a valid period. This selection is only visible if the date range option is enabled above. Choose between different pre-defined ranges by simply clicking on it. With each click the St art and End Dat e fields above will be changed accordingly.
Quick Range
Processing Opt ions File Format and Delivery Define how you want to view the report. Choose between: View Report as HTML: Directly view the report in your web browser. It will be loaded in a new browser window or tab. Creat e and st ore PDF file: Create a PDF file of the report and store it. Once finished, you will find it in the St ored Report s tab and a ToDo 139 will be created which usually sends out a notification mail to the administrator. Creat e PDF file, st ore it and send by email: Create a PDF file of the report, store it, and send it via email once it is finished. Note: For large PDF reports, PRTG will automatically split the output into separate files to avoid huge PDF files. You can change the number of sensors included into each PDF file by editing the report templates manually. See More 1644 section below. Target Email Address This option is only visible if sending by email is selected above. Please enter a valid email address the report will be sent to. Note: Configuration for outgoing email can be changed in the Sy st em Administ rat ionNot ificat ion Delivery 1702 settings. This option is only visible if sending by email is selected above. Specify if the attached report files will be compressed before sending. Choose between: Uncompressed: The report files will not be compressed before they are sent by email. Compressed: The report files will be compressed to a ZIP file before they are sent by email.
Compression
Click on the Run Report button to start report generation. Depending on the number of selected sensors, this may take a while. If you experience a long waiting time when generating HTML reports for immediate view, please consider using one of the PDF options. You can then view the report as soon as it's finished.
03.05.2013
1643
Note: Any sensor graphs in your report will only show the channels that are enabled via the Show in Chart s option in the Sensor Channels Set t ings 1566 of the respective sensor.
Stored Reports
In the St ored Report s tab you can view PDF reports created in the past. Simply click on a name to open the report. Reports are stored until they are deleted according to the data purging settings of your PRTG configuration. You can set data purging limits for reports in the Sy st em Administ rat ionSy st em and Websit e 1691 settings.
Other Tabs
For all other tabs, please see Report s Set t ings
1645
section.
More
Knowledge Base: Can I change the number of PDFs created by a report? http://www.paessler.com/knowledgebase/en/topic/11863
1644
03.05.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 9 Reports 3 Reports Settings
7.9.3
Reports Settings
In the web interface, click on the Report s entry in the main menu to show the reports main screen. Click on a report's name to select it. Using the reports tabs you can access all functionalities and settings for this report. Click on the Go t o all report s button at the bottom of the page to return to the list of Reports.
Report Tabs
Run Now
In the Run Now tab you can execute a report immediately with the settings configured. Please see View and Run Report s 1642 section.
Stored Reports
In the St ored Report s tab you can view reports created in the past. Please see View and Run Report s 1644 section.
Settings
Click on the Set t ings tab to open a report's settings.
Basic Report Set t ings Report Name Template Enter a meaningful name to identify this report. Select a template for the report. This will define the overall look of your report. There are several report templates delivered with PRTG. They also define in which detail (interval) monitoring data is included. You can choose from templates in the following categories: Graph wit h Dat a Table: Create a report with graphs and data table. Choose from several intervals. Dat a Table Only : Create a report with data tables only. Choose from several intervals. Graph Only : Create a report with graphs only. Choose from several intervals.
08.10.2013
1645
Basic Report Set t ings List of Sensors: Create a report in a compact sensor list style. This is available with and without graphs. Top 100 Highest and Lowest : Create a report with up to 100 objects with the highest and lowest average values. Choose from different intervals. Top 10 Upt ime/Downt ime: Create a report with up to 10 objects with the highest uptime and downtime each. You can choose between data in percent and hours. Top 100 Upt ime/Downt ime: Create a report with up to 100 objects with the highest uptime and downtime each. You can choose between data in percent and hours. Monitoring data within an interval is averaged. See also the comment on data averaging in the Report s 1638 (Automatic Averaging) section. For information on how to modify templates, please see More 1654 section below. Security Context Define the user account that will be used for access to monitoring data. The report will only contain objects which the selected user 89 is allowed to view. Please choose a user from the list. The available users depend on your configuration. By default, this is the user that created the report. PRTG Administrator users can change this setting. Define the time zone that will be used for all date-specific settings in this report (see below). Select a time zone from the list. Define the paper size in which PDF reports will be created. Choose between: A4: Use German DIN A4 format. Legal: Use US legal paper format. Let t er: Use US letter paper format.
Timezone
Paper Size
Sensors Cluster Node This field is only visible when running PRTG in Clust ering 76 mode. Define the cluster node the report will take monitoring data from. Choose a cluster node from the list. The available options are specific to your configuration. Select All nodes to create a report with data from all of your cluster nodes. Note: A report for all nodes will include data of the primary sensor channels only, not for other sensor channels.
1646
08.10.2013
Sensors Add Sensors Manually If you want to manually choose the sensors included in this report, please save settings and switch to the Select Sensors Manually 1652 tab. Define the sensors included in this report by tag. Enter one or more tags separated by space or comma. The report will cover all sensors that have at least one of the tags. Please enter a string or leave the field empty. Note: Tags are inherited 84 invisibly and automatically. So, for example, if you enter the tag of a group here, the report will include all sensors within this group. For detailed information, see Inherit ance of Set t ings 82 section. For sensors that are added by tag, all sensor channels are included in the report automatically, except All nodes is selected in the Clust er Node selection above. Further filter sensors. This is used in combination with sensors that are added manually, or added implicitly with their manually added parent objects. From those sensors, only the ones with the tags entered here will be included. Enter one or more tags separated by space or comma to include sensors in the report. Please enter a string or leave the field empty.
Add Sensors by Tag
Filter Sensors by Tag
Schedule Report Schedule Define when the report will be run. Choose between: No schedule (run int eract ive/on-demand only ): Only use the options in the Run Now tab to start generation of this report manually. Every full hour: Run this report every 60 minutes. Every day at a specific hour: Run this report every 24 hours. Every specific day of a week: Run this report every 7 days. Specify the day below. Every specific day of a mont h: Run this report on a specific day every month. Specify below. The day aft er a quart er is finished (i.e. at 1. April for t he 1. January - 31. March Quart er): Run this report for every quarter of the year. Every specific dat e: Run this report on a specific date every year. Specify below.
08.10.2013
1647
Schedule Specify Hour This setting is only visible if specific hour is selected above. From the list, please select the hour you want to run the report at. PRTG will automatically choose a suitable time within this hour, usually at the beginning of it. This setting is only visible if the day of week or day of month option is selected above. From the list, please select a day of week or a date of the month you want to run the report. When selecting Last , the report will always run on the last day of the month, regardless of how many days the month has. When selecting a date that does not exist in every month, e.g. the 30th in May, PRTG will automatically run the report on the last day of this month. This setting is only visible if the specific date option is selected above. Please enter a valid date in the form DD.MM, e.g. 31.12. The report will be run annually on this date. This setting is only visible if one of the schedule options is selected above. Define what will be done when generating a report. Choose between: Save report t o disk and send it by email: Create a PDF file of the report, store it, and send it via email. You will find the report in your emails and in the St ored Report s tab. Define an email address below. Save report t o disk only : Create a PDF file of the report and store it. Once finished, you will find it in the St ored Report s tab and a ToDo 139 will be created which usually sends out a notification mail to the administrator. Send report by email only : Create a PDF file of the report and send it via email once it is finished. The report is not permanently stored, but only emailed. Define an email address below. Note: For large PDF reports, PRTG will automatically split the output into separate files to avoid huge PDF files. You can change the number of sensors included into each PDF file by editing the report templates manually. See More 1654 section below. Email Address This setting is only visible if a send by email option is selected above. Please enter a valid email address the report will be sent to. To enter more addresses, separate them by comma. PRTG will send a message with all recipients in the "To" field of the email. Note: Configuration for outgoing email can be changed in the Sy st em Administ rat ionNot ificat ion Delivery 1702 settings.
Specify Day
Specify Date
Scheduled Processing
1648
08.10.2013
Schedule Send to User Group This setting is only visible if a send by email option is selected above. From the drop down list, please choose a user group to send an email with the report to all members of this group (you can edit user groups under Sy st em Administ rat ionUser Groups 1715 ). Note: If you define individual email addresses (see field above) and a user group, the report will be sent to the individual email addresses as well as to the members of the selected user group. In both cases, PRTG will send one message with all recipients in the "To" field of the email. This setting is only visible if a send by email option is selected above. Specify if the attached report files will be compressed before sending. Choose between: Uncompressed: The report files will not be compressed before they are sent by email. Compressed: The report files will be compressed to a ZIP file before they are sent by email.
Compression
Period Reported Period Define the time span covered by the report. Choose between: Current : Use monitoring data of the current period. Define the period type below. Previous: Use monitoring data of the last period. Define the period type below. Report Period Type Define the type of period you want to create a report for. Choose between: Day Week Mont h Quart er (January -March, April-June, et c.) Year Depending on your selection, different period selections are shown below. Day Period This setting is only visible if day period type is selected above. Define the hours when a day starts and ends. Choose from the list of hours. Default setting is 0:00-23:59.
08.10.2013
1649
Period Week Period This setting is only visible if week period type is selected above. Define when a week starts and ends. Choose between: Monday -Sunday : A reported week will start on Monday. Sat urday -Friday : A reported week will start on Saturday. Sunday -Sat urday : A reported week will start on Sunday. Month Period This setting is only visible if month period type is selected above. Define when a month starts and ends. Choose between: 1.-last day : A reported month will start on the first and end on last of the month. 15.-14. : A reported month will start von 15th and end on 14th of the month. Year Period This setting is only visible if year period type is selected above. Define when a year starts and ends. Choose between: 1/1-12/31: A reported year will start on January 1st. 7/1-6/30: A reported year will start on July 1st. Report only for specific Include certain time spans within the defined period only. When a hours-of-day schedule is selected, only monitoring data for specified hours or (Schedule) weekdays within the defined period are included in the report. Select None to include all available monitoring data in the report, or choose a schedule. For example, select the schedule Weekday s to exclude all weekends from the report. The available schedules depend on your configuration. For more information, please see Account Set t ingsSchedules 1687 section.
Percent ile Set t ings Show Percentile Define if percentiles between:

1916
will be included in the report. Choose
Off: Do not show percentiles On: Add a column to data tables, showing percentiles for every sensor channel. Note: Percentiles are not available for all report templates. If a template does not support percentiles, they will simply not show up in the report, even when you enable this setting.
1650
08.10.2013
Percent ile Set t ings Show Percentile This setting is only visible when showing percentiles. Enter the percentile number you want to calculate. If you choose, for example, to calculate the 95th percentile, enter "95" here and 5 % of peak values will be discarded. This setting is only visible when showing percentiles. This is the averaging interval in seconds, which is used for percentile calculation. Default value is 300 which is equivalent to 5 minutes. This setting is only visible when showing percentiles. Choose the mode for percentile calculation: Discret e: Discrete percentile chooses the next smaller discrete value. Cont inuous: Continuous percentile interpolates between discrete values. For details, see section Calculat ing Percent iles
1916
Percentile Average (seconds)
Percentile Mode
Report Comment s Introduction Define a custom text that will show up on the first page of the report. Please enter a string or leave the field empty. Define a custom text that will show up on the last page of the report. Please enter a string or leave the field empty.
Footer Comments
08.10.2013
1651
Inherit Access Right s User Group Access Define which user group(s) will have access to the object you're editing. A table with user groups and right is shown; it contains all user groups from your setup. For each user group you can choose from the following access rights: Inherit ed: Use the settings of the parent object. None: Users in this group cannot see or edit the object. The object does not show up in lists. Read: Users in this group can see the object and review its settings. Writ e: Users in this group can see the object, as well as review and edit its settings. However, they cannot edit access rights settings. Full: Users in this group can see the object, as well as review and edit its settings and edit access rights settings. You can create new user groups in the Sy st em Administ rat ion User Groups 1715 settings. Click on the Save button to store your settings. If you change tabs or use the main menu, all changes to the settings will be lost!
Select Sensors Manually

Click on the Select Sensors Manually tab to manually choose sensors that will be included in the report. You will see a split screen: On the left side, your list of objects is show (empty in the beginning), and on the right side, you see a less colorful view of your device tree, as known from the device tree's Management 211 tab. Adding objects to the report is very easy.
1652
08.10.2013
Manual Sensor Selec tion for Reports
Add It ems From the device tree on the right side, drag objects and drop them on the list on the left side. This can be entire probes, groups, devices, or single sensors. Each dropped object will be added immediately as a new list item. Repeat this procedure as often as you wish until you have added all desired items to the library. Note: Objects that already exist in the list on the left side will be grayed out in the device tree on the right side. Select Sensor Channels If in the report settings one specific cluster node is selected and if you are adding a sensor to the selection, you can specify the sensor channels that will be included in the report. By default, all channels are selected. To exclude a channel from the report, simply remove the check mark in front of a channel's name. Note: If All nodes is selected in the report's Clust er Node selection, the channel selection is not available, but only the primary channel of every sensor is included automatically. Remove To remove any objects from the report, click on the trash can symbol next the respective list item, or select several list items while holding down the Ctrl key and click on the green trash symbol appearing at the top of the list. Your selection is saved automatically, and there is no undo function. Note: The final report will include both sensors selected manually and those selected by tag.
08.10.2013
1653
Sensors Selected by Tag

Click on the Sensors Select ed by Tag tab to view all sensors that are added to the report depending on the report's Add Sensors by Tag setting. In the table list 141 , you will see all sensors that are added by tag. This is for your information only, you cannot change sensors here. However, you can switch to the report's Set t ings tab and change the tabs that are used to add sensors. Additionally, you can also exclude sensors with certain tabs there. The final report will include both sensors selected manually and those selected by tag. For sensors that are added by tag, all sensor channels are included in the report automatically, except All nodes is selected in the report's Clust er Node selection. In this case, only the primary channel of every sensor is included. Note: The final report will include both sensors selected manually and those selected by tag.
Comments
More
Knowledge Base: Can I change the number of PDFs created by a report? http://www.paessler.com/knowledgebase/en/topic/11863 Knowledge Base: How do I modify PRTG's report templates? http://www.paessler.com/knowledgebase/en/topic/263 Knowledge Base: How can I show full channel names below report graphs? http://www.paessler.com/knowledgebase/en/topic/58913 Calculat ing Percent iles
1916
1654
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 10 Maps
7.10
Maps
With PRTG's Maps feature (some people might call this 'dashboards') you can create web pages with up-to-the-minute monitoring status information in a customizable layout. Using this unique concept, you can also make your overview pages of live data publicly available, if you like.
Example of a PRTG Map
In this section: Int roduct ion St art Maps

1655
1656
Maps Overview Maps Rot at ion
1656
1657
Working wit h Maps
1657
Introduction
There are countless possibilities for the implementation of maps. For example, this feature can be used to: Create network maps with status icons for each device on the map.
08.10.2013
1655
Create quick views of your network that can be shown on network operations center screens. Create a quick network overview for publishing on the Intranet, allowing at-a-glance information for management of other employees. Create a custom view of the most important sensors in your monitoring setup. Create Top 10 lists of the sensors of a specific group or device. Technically, a map is a usual HTML web page. You can build a schema of your network by choosing from hundreds of device icons and connect them with lines. A map can consist of the following elements: A set of map items, which can include device icons, sensor status icons, graphs, data tables, lists of sensors, connection lines, geographical maps, or custom HTML code. An optional background image (a JPG, PNG, or GIF file, e.g. your company logo or a graphical view of your network). You can also specify the size of the map. Using the AJAX-based map editor, you can place the items anywhere on the map and you can also change their size. Each map has a unique URL which can be used to link to the map. Users who want to access the map either need an account in your PRTG installation, or can access a public URL of the map if you allow the Public Access feature. Public maps contain a unique Map ID access key in the URL to block unwanted visitors.
Start Maps
Click the Maps entry from the main menu 172 to view or add custom views of your network's status and monitoring data. Hover to show other menu items. Choose between: 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
1658
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.
Maps Overview
In the All view, you see a list of all existing maps. Using the links next to a map name, you can perform the following actions. Click on the name of a map to view it. Delet e: Delete this map.
1656
08.10.2013
Clone: Create an exact copy of this map. As soon as you click, the map is cloned and the cloned map's settings are shown. Click on the Add Map button to add a new map. Please see also Working wit h Table List s 141 . Additionally, there is multi-edit available. This enables you to change properties of several objects at a time. For more details, please see Mult i-Edit List s 1595 section.
Map Rotation
To show several maps in a rotation, mark the desired maps using multi-edit 1595 and then select Map Rot at ion from the multi-edit menu. You will be redirected to a page where the rotation is shown. This requires login credentials for PRTG. It is also possible to set up a public map rot at ion without login: Allow public access in the settings 1667 of the desired maps. Use the corresponding map IDs with its secret keys to build a URL that calls a public map rotation. The URL must have this format: the address of your PRTG server, followed by /public/mapshow.htm?ids=. Then list the IDs of the desired maps, each separated by a comma. Each map ID has to be connected with its secret key using a colon: ht t p://yourprtgserver/public/mapshow.ht m? ids=mapid1:secretkey1,mapid2:secretkey2,mapid3:secretkey3 While a map rotation is shown, you can change the refresh interval any time when hovering the arrows symbol in the lower right corner. Choose between 10, 30, or 60 seconds, 10 minutes or Refresh now.
Working with Maps

For detailed information on how to create and edit maps, and to learn how to make them accessible to others, please see the following sections. Maps St ep By St ep Maps Designer
1660 1658
Maps Ot her Set t ings
1667
08.10.2013
1657
Part 7: Ajax Web InterfaceAdvanced Procedures | 10 Maps 1 Maps Step By Step
7.10.1 M aps Step By Step

In order to create a new map, follow the steps in this section. In the web interface, click on Maps entry in the main menu to show the maps main screen. Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default. In this section: St ep 1: Add Map
1658
St ep 2: Add Map It ems St ep 3: View and Share
1659
1659
Step 1: Add Map

Click on the Add Map button. An assistant is shown. Enter a Map Name and define Map Lay out settings. in the Public Access section, define whether your map will be visible without login. For detailed information, see Maps Ot her Set t ings
1667
section (Settings).
Add Maps Assistant Step 1
1658
03.05.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 10 Maps 1 Maps Step By Step
Step 2: Add Map Items

Click on the Add Map It em button to open the Add Map Object assistant. Select an object, define further settings and confirm. The item will be added immediately. Repeat this procedure as often as you wish until you have added all desired items to the map. Drag items to change their position. Additionally, you can also draw connection lines between items or edit existing items. For detailed information, see Maps Designer
1660
section.
Step 3: View and Share

Click on the View Map tab to see the appearance of your map. Later, It will be shown the way you see it there. If available for an object, most object names as well as all sensors can be clicked on. It depends on the object's access rights and the currently logged in user account if clicking the links will lead to more detailed information about the object or to an error message indicating insufficient access rights. Click on the Get HTML tab to get the direct URL of your map that you can share with others. For detailed information, see Maps Ot her Set t ings 1669 section (Get HTML). While showing a map, the single map items will be refreshed in the refresh interval defined for this map.
03.05.2013
1659
Part 7: Ajax Web InterfaceAdvanced Procedures | 10 Maps 2 Maps Designer
7.10.2 M aps Designer

Note: This section refers to PRTG Network Monitor version 8.4. The Map Designer was significantly enhanced with this version. If you're using an earlier version, please update the latest version to profit from the innovations.
41
to
Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default. In this section: Use a Proper Browser Basic Design Concept Device Tree Select ion Propert ies Select ion
1660
1660
1661
1662
Edit Exist ing Map It emsPropert ies Box Edit Exist ing Map It emsHover Icons
1663
1663
Edit Exist ing Map It emsUsing Cursor Key s Draw Connect ion Lines Bet ween It ems Snap To Grid More
1665 1665 1664
1664
Click on the Go t o all maps button at the bottom of the page to return to the list of Maps.
Use a Proper Browser

Due to the map designer's extensive scripting capability, it is important that you use a compatible browser when editing maps. We recommend using Google Chrome 27 or later (recommended) or Mozilla Firefox 21 or later. You can use Microsoft Internet Explorer 9 or 10 as well. The maps designer is not fully compatible with earlier versions of Internet Explorer or Opera browsers.
Basic Design Concept

Click on the Map Designer tab to open the editor. It might take a few moments to load (for unresponsive script warnings, please see More 1665 section below). Here, you can create your map by adding or changing items. The designer screen consists of three main parts: The Device Tree on the left side, the current Map in the middle, and the Propert ies on the right side.
1660
08.10.2013
Map Designer
Each map item takes attributes from both selections. Device Tree (left): Select the monitoring object which's data will be shown on the map Propert ies (right): Define how the map item will be shown Simply drag and drop any object from either side onto the map, or double-click on an object. You will always see all changes immediately.
Device Tree Selection

Use the Device Tree to select the monitoring object which's data will be shown on the map (this can be a probe, a group, a device, or a single sensor). In order to find the right object, you have the following options: Use the arrow symbols at the beginning of each line to open nodes in the device tree to show objects underneath probes, groups, and devices. Enter a view characters into the Search box in the upper left corner to search for names (or part of names) of objects in your configuration. The search results will be shown immediately. Click on the red x icon to clear your search. No matter which method you choose to find the desired object, you can always drag any object from the Device Tree on a free area of the map to create a new map item. If you drag it onto an existing map item, it will be replaced, while Propert ies and size will remain. You can also select a map item and double click on a Device Tree object to replace the map item. If no item is selected, a double-click on an object will add a new map item. To gain more space for map editing, click on the pin symbol in the upper right corner of the Device Tree box to swing it in. Click it a second time to fix the box again. You can also resize the box by dragging its right border to left or to the right
08.10.2013
1661
Properties Selection
Use the Propert ies selection to define how the map item will be shown (for example, as an icon, a map, a table, or a graph). Select the appearance in different categories. Hover a property object to get a live preview of it (in most cases). Note: If a certain Propert ies object is not available for the selected Device Tree object, you will see a corresponding text hint. There are many different property object types available. Simply click a category's name to show all available types. Icons A, Icons B, Icons C These three categories offer a variety of iconic symbols of typical network devices. Below each icon the object name and a sensor overview for the object is shown. This shows how many sensors are in which state. For some sensors, a mini graph is shown as well. Icons A (St at ic), Icons B (St at ic), Icons C (St at ic) These three categories offer the same variety of iconic symbols of typical network devices as the category described above. Here, no object data displayed with them, but only the icon is shown. St at ic Maps This category offers free or public domain geographical maps from different sources. For additional geographical maps, please see More 1665 section below. Note: The items in this section are independent from the selected Device Tree objects. St at us Icons This category shows options to insert status icons in different styles. These show the object name and an overview of how many sensors are in which state. There is also an object available for audible alert which will play a sound when the number of alarms of the monitored object are > 0. Please note that your browser must support playing embedded sounds (see More 1665 section below for further information). Geo Maps In this category you can choose from different geographical map styles from Google: road map, satellite, hybrid, and terrain maps. The location of the currently selected object in the Device Tree will be shown on the map as a pin mark. To use this feature, Geo Maps integration must be enabled and you have to enter a Locat ion in the settings of the monitoring object you want to use this with. For more information, please see Geo Maps 1603 section. Note: If Geo Maps integration is disabled, you will only see white boxes instead of map previews. Graphs This category offers different graph styles in several dimensions and detail. You can also select graphs including a legend or sensor states. Object s Add some simple geometric shapes to your map. The items shown in this tab are always the same; the range displayed does not depend on the selected object in the Object field above. Dat a Tables Choose from several tables showing sensor lists for the current selected object. You can also choose from several lists showing sensors in a certain state only.
1662
08.10.2013
Top 10 Choose from several tables showing the top 10 of sensors with certain monitoring data, such as least used CPUs, highes bandwidth usage, best availability, slowest websites, etc. Note: In order to provide live previews, PRTG calculates all top 10 lists from your monitoring data when opening this tab. It may take a few seconds before thumbnails are shown. Cust om HTML This can be used, for example, to add external images or applets to your map. In order to actually add custom HTML code to your map, please add this item and then click on it to edit 1663 . You can then copy your custom code into the HTML Before and HTML Aft er fields in the Propert ies box on the right side. No matter which object you choose, you can always drag any object from the Propert ies box on a free area of the map to create a new map item. If you drag it onto an existing map item, it will be replaced, while its Device Tree object attributes and size will remain. You can also select a map item and double click on an object in the Propert ies box to replace the map item. If no item is selected, a double-click on an object will add a new map item. To gain more space for map editing, click on the pin symbol in the upper right corner of the Propert ies box to swing it in. Click it a second time to fix the box again. You can also resize the box by dragging its left border to left or to the right.
Edit Existing Map ItemsProperties Box

Click on a map item to select it. You can then edit its attributes with the fields in the upper part of the Propert ies box on the right side: Top, Left , Widt h, and Height fields Enter position and size values for direct positioning. Click the Save button to save your settings. Alternative: Use the mouse to move and resize a map item. Lay er field The layer number defines if an item will be shown on top of or behind another item, if overlapping. The item with the higher number will be shown on top. Enter a positive integer value and click the Save button to save your settings. Alternative: Use the arrow symbols in a map item's hover menu to Bring t o front or Send t o back an item one layer (see below). HTML Click on the arrow symbol underneath to show the HTML Before and HTML Aft er fields. Any HTML code you enter in these fields will be added before respectively after the map item. Please enter your custom HTML code that embeds an objects and click the Save button. Your HTML object will be inserted. For example, you could enter the code <img src="http:// media.paessler.com/common/img/logoclaim_r1.gif"> to insert an image of the Paessler logo from the Paessler website.
Edit Existing Map ItemsHover Icons

Hover a map item to show the edit icons for it.
08.10.2013
1663
Edit Ic ons of a Maps Objec t
Bring t o front (arrow up sy mbol) Move this item one layer to the front. This is useful when adding several items to a map that overlap each other. Send t o back (arrow down sy mbol) Move this item one layer to the back. This is useful when adding several items to a map that overlap each other. Delet e (t rash sy mbol) Delete this item. Note: Be careful! The item will be deleted immediately without notice and you cannot undo this. Alternative: Select the item and press the Del button on your keyboard. Drop Connect ions (scissors sy mbol) If you have drawn connection lines between two items, you can delete all lines starting from this item. Connection lines will be dropped immediately. Note: If a line between two items is not dropped, you've probably drawn it starting from the other item. Try the scissors symbol on the other item instead.
Edit Existing Map ItemsUsing Cursor Keys

While an object is selected, use the cursor keys to move it by one pixel. Hold the Shift key in combination with the cursor keys to move the object by 10 pixels.
Draw Connection Lines Between Items

You can draw connection lines between any map items via drag and drop. Simply click on the grey handles next to an item and drag a line to another item you want to draw a connection to. A line will be shown immediately. This can be useful to indicate network connections or logical coherences between two items. To delete connection lines, click the scissors symbol in the item's edit icons 1663 .
Ic ons with Colored Lines
1664
08.10.2013
Lines between objects are colored dynamically. They will turn red as long as one of the object's icons shows a red Down status. This will only affect half of the line, at the end where the red sensor is shown. If both objects connected show a red sensor, this will result in a line that is red all over. Note: Currently, this feature is unavailable for objects that do not show a graphical icon. For example, this concerns status icon objects, geographical maps, graphs, data tables, and top lists. Lines will always remain grey at the end of these objects.
Snap to Grid
Select whether to use Snap To Grid or Don't Snap, using the buttons underneath the Device Tree box. This will affect how map items will be positioned when adding or moving them via drag and drop. The setting is active immediately. With snap to grid enabled, you can place items aligned with the grid only.
More
Knowledge Base: Why does my browser show an unresponsive script warning while loading the Maps Designer? http://www.paessler.com/knowledgebase/en/topic/19483
Knowledge Base: Where can I download free political/topographical map images for use in PRTG map editor? http://www.paessler.com/knowledgebase/en/topic/7463
Knowledge Base: How can I setup audible notifications (sound files) in PRTG? http://www.paessler.com/knowledgebase/en/topic/5473
Knowledge Base: How can I add "deep links" into PRTG's interface for map status icons? http://www.paessler.com/knowledgebase/en/topic/3763
Knowledge Base: How can I add or edit map objects used for PRTG's maps? http://www.paessler.com/knowledgebase/en/topic/1703
Knowledge Base: How to setup interactive maps? http://www.paessler.com/knowledgebase/en/topic/2253
Knowledge Base: Can you re-order or remove columns in sensor lists displayed in maps? http://www.paessler.com/knowledgebase/en/topic/5523
08.10.2013
1665
Knowledge Base: How can I show up-to-date weather information, webcam and radar images in PRTG's maps http://www.paessler.com/knowledgebase/en/topic/9263
Knowledge Base: Can I use my own images/icons/logos in PRTG's map editor? http://www.paessler.com/knowledgebase/en/topic/8043
1666
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 10 Maps 3 Maps Settings
7.10.3 M aps Settings

Using the Map tabs you can access all functionalities and settings for a map.
Maps Tabs
Click on the Go t o all maps button at the bottom of the page to return to the list of Maps.
View Map
Click on the View Map tab any time to show a preview of your map.
Map Designer
Click on the Map Designer tab to edit the contents of your map. Please see Maps Designer section.
1660
Settings
Click on the Set t ings tab to open a map's general settings. Note: When using the Add Map dialog, not all of these settings are available. You can change them later by clicking on the Set t ings tab. Basic Map Set t ings Map Name Security Context Enter a meaningful name for the map. Define the user account that will be used for access to monitoring data. The map will only contain objects which the selected user 89 is allowed to view. Please choose a user from the list. The available users depend on your configuration. By default, this is the user that created the map. PRTG Administrator users can change this setting. Define the time zone that will be used for all date-specific options in this map. Select a time zone from the list. This setting affects table maps objects. Enter one or more tags separated by space or comma to include sensors in tables. Only sensors with one of the tags entered here will appear in this map's data tablesincluding sensors which inherit 82 tags from parent objects. Please enter a string or leave the field empty. Note: Use with care! This setting will affect all tables of the current map!
Timezone
Tag Filter
03.05.2013
1667
Map Lay out Map Width Map Height Define the width of the map in pixels. Please enter an integer value. Define the height of the map in pixels. Please enter an integer value. Define if you want to use a background picture for the map. Choose between: On: Use a background image (define below). Off: Do not use a background image. Background Image This option is only visible if a background picture is enabled above. Click on the Choose File button and select an image from your computer or network. Note: Only images in the format JPG, PNG, and GIF are supported. The file size must be smaller than 2 MB. If you try to upload other images, you will get an error message. In a cluster, background images are not automatically deployed to the other nodes! In order to view maps on other nodes, please copy the background pictures manually to \webroot\mapbackground of the program directory on every node. For detailed information on how to find this path, please see Dat a St orage 1912 section. Select a background color for this Map. Either enter a hex color code or choose a color from the color selector. The hex color code field will always display the currently defined color.
Background Picture
Background Color
Public Access Public Access Define if others can see the map. Choose between: No Public Access: Do not allow public access to the map. Only users with both a login to the PRTG web interface and sufficient access rights can see the map. Allow Public Access: Allow access to the map using a unique address. The URL contains a key that you can change below. Secret Key This field is only visible if public access is enabled above. The key is automatically generated. It is part of the public URL for the map. You can also enter a customized string. We recommend using the default value. For more information on public access, please see the Get HTML 1669 section. Note: The characters comma "," and colon ":" are not allowed in the secret key field!
1668
03.05.2013
Get HTML
Your PRTG map is like a standalone HTML page. You can make it accessible to others, if you like. Depending on the Public Access setting 1667 of your map, a visitor will need to provide PRTG user account login data to view the map, or will see the map immediately using a URL containing a secret key. When using this unique key, you can also include your map on another webpage, embedding it via <iframe>. Opt ion 1: Link t o a web page wit h t he map t hat requires login credent ials The shown URL requires login credentials in order to display the map. PRTG will ask the user trying to view the map via this URL for login credentials. Note: In the URL, usually the IP address is given via which the page is available. Maybe a NAT translation is set in your firewall, or you may want to use a domain name or a name from a dynamic DNS service for public access. Please customize URL you use for access to your needs. Opt ion 2: Link t o a web page t hat display s t he map wit hout a login In order to get the shown URL working for public access without a login, enable Allow Public Access in the settings tab 1667 of your map. Note: In the URL, usually the IP address is given via which the page is available. Maybe a NAT translation is set in your firewall, or you may want to use a domain name or a name from a dynamic DNS service for public access. Please customize URL you use for access to your needs.
03.05.2013
1669
Opt ion 3: Show a map inside ot her web pages using an IFRAME For your convenience, this shows source code for adding an iframe to another webpage. It includes a URL for direct access. Just copy the code and paste it into your webpage's code. Also enable Allow Public Access in the settings tab 1667 . Note: In the URL, usually the IP address is given via which the page is available. Maybe a NAT translation is set in your firewall, or you may want to use a domain name or a name from a dynamic DNS service for public access. Please customize URL you use for access to your needs. While a map is shown via these URLs, you can change the refresh interval any time by hovering the arrows symbol in the lower right corner. Choose between 10, 30, or 60 seconds, 10 minutes or Refresh now.
Comments
Delete
You can delete the entire map any time by clicking on the trash symbol on the right.
More
Knowledge Base: How to disable links in public maps? http://www.paessler.com/knowledgebase/en/topic/10283 Dat a Report ing
88
1670
03.05.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup
7.11
Setup
In the setup settings of the PRTG web interface, you can define almost all system settings for PRTG. However, some of the machine-oriented settings are defined using two Windows administration tools (see Ot hers 1672 section below). In the main menu, click on Set up to show the available options.
Setup Ov erv iew for a Cluster Installation Shown in Google Chrome Browser
Account Settings
Account Set t ingsMy Account
1673
Account Set t ingsNot ificat ions Account Set t ingsSchedules

1687
1678
08.10.2013
1671
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup
System Administration
Sy st em Administ rat ionSy st em and Websit e Sy st em Administ rat ionNot ificat ion Delivery Sy st em Administ rat ionProbes
1707 1691
1702
Sy st em Administ rat ionUser Account s Sy st em Administ rat ionUser Groups Sy st em Administ rat ionClust er
1709 1715
1710
PRTG Status
PRTG St at usSy st em St at us PRTG St at usAut o Updat e
1732 1723
PRTG St at usClust er St at us
1735
Optional Downloads and Add-Ons

DownloadsPRTG Ent erprise Console DownloadsApps for iOS & Android DownloadsRemot e Probe Inst aller Chrome Deskt op Not ificat ions
1739 1737
1737
1737
Support
Support Cont act Support
1741
Others
There are some settings that have to be made in the Sy st em Administ rat ion Tools running as Windows applications. For more details, please see sections: PRTG Server Administ rat or PRTG Probe Administ rat or
1837 1836
1857
1672
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 1 Account SettingsMy Account
7.11.1 Account SettingsM y Account

In the My Account settings you can define values regarding your own PRTG user currently logged in. All settings in this section are user specific. Some account control options may not available, but can only be defined by the administrator.
My Ac c ount Settings
My Account Settings
User Account Login Name Enter the login name for the user.
08.10.2013
1673
User Account Display Name Enter a name for the user for display purposes. This will not be used for login. Enter the user's email address. Enter the time zone for the current user. Enter in what format dates will be displayed for the current user. Note: This setting will take effect after the next login. Define the user's password. For security reasons, the account settings page does not contain the password. Choose between: Don't change Specify new password If you choose to specify a new password, enter the old password, and the new password twice. Note: The new password must be at least 8 characters long; no character may occur more than 3 times. It must contain a number and a capital letter. Hash The hash (passhash) value can the used as password substitute when calling functions from PRTG's Application Programming Interface (API) that require an authentication. For more information please see Using t he PRTG API (Applicat ion Programming Int erface) 1871 section.
Email Address Timezone Date Format
Password
Aut o Refresh and Alert ing Auto Refresh Type Specify how PRTG's web pages will be refreshed for the current user. Choose between: Refresh page element s using AJAX (recommended): Automatically refresh the single page elements on the web pages. Refresh whole page: Automatically reload the whole page with every refresh interval. No aut o refresh: Do not automatically refresh web pages.
1674
08.10.2013
Aut o Refresh and Alert ing Auto Refresh Interval (sec) This setting is only relevant when auto refresh is enabled above. Enter the number of seconds that will be waited between two refreshes. We recommend using 30 seconds or more. Minimum value is 20 seconds. Note: Shorter intervals create more CPU load on the server running the PRTG core server. If you experience load problems while using the web interface (or PRTG maps 1655 ), please set a higher interval. Define when an audible alarm will be played for the current user on web pages whenever there are alarms 135 in PRTG. Choose between: Never: Do not play sound files on any web pages. On dashboard pages only : When there are alarms, play a predefined sound on dashboard 165 pages only. The sound will be replayed with every refresh of a dashboard page. On all pages: When there are alarms, play a predefined sound on all web pages. The sound will be replayed with every page refresh. For more information about audible notifications and supported browsers, please see More 1677 section below.
Play Audible Alarms
Web Int erface Homepage URL Define the user's default page loaded after login and when clicking on the Home 165 button in main menu. In order to provide you with a speedy user experience PRTG tries to keep the page size for the page showing the device tree small by automatically folding groups and devices with many items. Define how many groups and devices are shown at maximum before the automatic reduction is performed. We recommend using a value between 10 and 30. In order to provide you with a speedy user experience PRTG tries to keep the page size for the page showing the device tree small by automatically folding groups and devices with many items. Define how many sensors are shown at maximum before the automatic reduction is performed. We recommend using a value between 10 and 30.
Max. Groups/Devices per Group
Max. Sensors per Device
08.10.2013
1675
Account Cont rol Account Type This setting is only shown for administrator users. However, it is not shown if the user you modify the account settings for is a member of a group with administrative rights. Define the account type for the current user. Choose between: Read/Writ e User: The user may change settings. Read Only User: The user may not edit any settings. This is a good choice for public or semi-public logins. Note: This setting cannot be changed for the default administrator user. Allow Acknowledge Alarms This setting is only visible if read only user is enabled above. Acknowledging an alarm is an action which requires write access rights. However, you can explicitly allow this action to read-only users. If enabled, they still do not have write access, but may acknowledge alarms 136 . Choose between: Allow: Allow acknowledging alarms for this user. Deny : The user will not be able to acknowledge alarms. Primary Group This setting is only shown for administrator users. Select the primary group for the current user. Every user has to be member of a primary group to make sure there is no user without group membership. Membership in other user groups is optional. For user experience, there is no difference between the primary and other user groups. This setting is only shown for administrator users. Define the status of the current user. Choose between: Act ive: The current user can login to the account. Inact ive: The current user's login is disabled. Use this option to temporarily deny access for this user. Note: This setting cannot be changed for the default administrator user. Last Login Shows the time stamp of the user's last login. This setting is shown for your information only and cannot be changed here.
Status
User Groups Member of Shows the groups the current user is member of. Access rights to the device tree are defined on group level. This setting is shown for your information only and cannot be changed here.
1676
08.10.2013
Comments
History
In the Hist ory tab all changes in the settings of an object are logged with a timestamp, the PRTG user which conducted the change, and a message. The history log keeps the last 100 entries. Click on the Cont inue button to store your settings. If you change tabs or use the main menu, all changes to the settings will be lost!
More
08.10.2013
1677
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 2 Account SettingsNotifications
7.11.2 Account SettingsNotifications

In the notifications settings you can define and change notifications for the currently logged in PRTG user. They can be triggered for certain sensor states and data.
Notific ations Settings
Note
1609
section.
Notifications Overview
Click on the Not ificat ions tab to show a list of all existing notifications. Using the links next to the notification name, you can perform the following actions: Delet e: Delete this notification (not possible for predefined notifications) Test : Trigger this notification immediately for testing purposes. Note: When using placeholders, they will not be resolved in a test notification, but the variables will be sent instead.
1678
08.10.2013
Pause: Pause this notification. If a notification is paused, no messages will be sent when it is triggered. Clone: Create an exact copy of this notification. It will be added to the notifications list as Clone of ... Used by : Show a list of objects using this notification. Please see also Working wit h Table List s 141 . Additionally, there is multi-edit available. This enables you to change properties of several objects at a time. For more details, please see Mult i-Edit List s 1595 section.
Notifications Settings
Click on the Add new not ificat ion button to add a new notification, or click on the name of an existing notification to edit it. Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default.
Basic Not ificat ion Set t ings Notification Name Enter a meaningful name for the notification, for example, SMS to service team or similar. Select the status of the notification. Choose between: St art ed: This notification will be active. Paused: Pause this notification. If a notification is paused, no messages will be sent when it is triggered. Schedule Define when this notification will be active. Please select None to set it to always active, or choose a schedule from the list. Usually schedules define when this notification will be active; schedules defined as period list set this notification to inactive at the corresponding time spans. The available options depend on your setup. To add or change existing schedules, please see Account Set t ingsSchedules 1687 section. Define if notifications triggered during Pause status will be sent later on. No : Discard all notification triggers received while the notification is paused. Yes: Collect all notification triggers received while the notification is paused. Send out notifications once the pause status ends.
Status
Postpone
08.10.2013
1679
Not ificat ion Summarizat ion Method Define if and how notifications will be summarized if several notification triggers are received in a certain time span. Note: Regardless of the option chosen here, notifications of Execut e HTTP Act ion and Execut e Program are always sent ASAP; they are never summarized. Choose between: Alway s not ify ASAP: Always send out one notification for each notification trigger received. Send first DOWN message ASAP, summarize ot hers: When receiving several Down triggers, send the first notification immediately, but summarize other notifications into one message. Send first DOWN and UP message ASAP, summarize ot hers: When receiving several Down or Up triggers, send each first notification immediately, but summarize other notifications into one message. Send all DOWN messages ASAP, summarize ot hers: When receiving several Down triggers, send out one notification for each trigger received, but summarize notifications for all other triggers into one message. Send all DOWN and UP messages ASAP, summarize ot hers: When receiving several Down or Up triggers, send out one notification for each trigger received, but summarize notifications for all other triggers into one message. Alway s summarize not ificat ions: When receiving several notification triggers, summarize all notifications into one message, regardless of the kind of trigger received. Subject for Summarized Messages Define a subject which will be used when sending summarized notifications. You can use the placeholder %SUMMARYCOUNT for the number of messages which are summarized. Note: The subject you define is only used for Send Email and Amazon Simple Notification Service Message notifications. Define a time span in minutes for which notifications will be collected for summarization. Please enter an integer value. Note: If you define a high value, for example, 60 minutes, PRTG will send out summarized notifications with a delay of up to one hour.
Gather Notifications For (Minutes)
1680
08.10.2013
Inherit Access Right s User Group Access Define which user group(s) will have access to the object you're editing. A table with user groups and right is shown; it contains all user groups from your setup. For each user group you can choose from the following access rights: Inherit ed: Use the settings of the parent object. None: Users in this group cannot see or edit the object. The object does not show up in lists. Read: Users in this group can see the object and review its settings. Writ e: Users in this group can see the object, as well as review and edit its settings. However, they cannot edit access rights settings. Full: Users in this group can see the object, as well as review and edit its settings and edit access rights settings. You can create new user groups in the Sy st em Administ rat ion User Groups 1715 settings.
Notifications SettingsChoose Notification Methods

With the following settings, you can add one or more methods by which a notification message will be sent out. From the list you can only choose one method or combine several methods. Whenever the notification is triggered, it will send out messages or perform actions for all configured methods at a time. To choose a method, add a check mark symbol in front of the respective setting name. You will then see the options as described below. Note: In your message, you can use various placeholders. Some are already filled in by default. For a complete list of available placeholders, please see the More 1610 section below.
Send Email Note: The email footer can be set in the Sy st em Administ rat ionSy st em and Websit e settings. Email Address
1691
Enter one or more recipient email addresses. If entering more addresses, separate them by comma. If you want to send to a PRTG user group only, leave this field empty!
08.10.2013
1681
Send Email Send to User Group From the drop down list, please choose a user group to send an email with the report to all members of this group (you can edit user groups under Sy st em Administ rat ionUser Groups 1715 ). Select None to not use this feature. Note: If you define individual email addresses (see field above) and a user group, the message will be sent to the individual email addresses as well as to the members of the selected user group. In both cases, PRTG will send one message with all recipients in the "To" field of the email. Enter the subject of the email. Several placeholders (variables) are used here by default. Define the kind of email that will be sent. Choose between: Text HTML Message Depending on the format option selected above, you will see a text or HTML message in this field. A complete message about the sensor status is already predefined. You can change it to your liking. To reset this field to its default value, enter a single star symbol * (and nothing else). Click on the Reset t o default link underneath the text box to do so. Define the priority which will be set in the email. Some email clients can show this flag.
Subject
Format
Priority
Add Ent ry t o Event Log Logfile Define the log file the message will be written to. Choose between: Applicat ion: Use the Windows application log file in the event log. PRTG Net work Monit or: Write messages to the PRTG Network Monitor log file in the Windows event log. Event Source This setting is only relevant when using the Applicat ion log file. Enter the source for the event. Usually, this is the name of the application. Select the type of the event. Choose between: Error Warning
Event Type
1682
08.10.2013
Add Ent ry t o Event Log Informat ion Event Log Message Define the message. A message with information about the sensor status is already predefined. Several placeholders (variables) are used here. You can change it to your liking. To reset this field to its default value, enter a single star symbol * (and nothing else).
Send Sy slog Message Host/IP Define the IP address or DNS name of the computer running the syslog server. Enter the port number on which syslog messages are sent. By default, this is port number 514. Note: Only User Datagram Protocol (UDP) is supported. Define the facility information. There are several options available from the list. Define the message. A message with information about the sensor status is already predefined. Several placeholders (variables) are used here. You can change it to your liking. To reset this field to its default value, enter a single star symbol * (and nothing else).
Port
Facility
Message
Send Sy slog MessageSy slog Message Severit y St at us Depending on the status of the sensor triggering the syslog notification the Severit y level of the message will be set automatically: OK Warning Error Severity level: Notice (5) Severity level: Warning (4) Severity level: Error (3)
08.10.2013
1683
Send SNMP Trap For information about the OIDs used in the contents of the traps sent by PRTG, please see the SNMP Trap documentation in the More 1686 section below. Host/IP Define the IP address or DNS name of the computer running the trap receiver. Enter the port number on which trap messages are sent. By default, this is port number 162. Enter the device's community string. By default, this is set to public . Please enter a string or leave the field empty. Enter a code that can help you identify the purpose of the trap. Default value is 0. Please enter an integer value. This ID helps you identify the origin of the trap. For example, enter 1.3.6.1.4.1.32446.1.1.1 Define the message. A message with information about the sensor status is already predefined. Several placeholders (variables) are used here. You can change it to your liking. To reset this field to its default value, enter a single star symbol * (and nothing else). Define the IP address of the agent. Leave this field blank to use the PRTG web server's IP address.
SNMP Port
Community String
Specific Trap Code
Message ID
Message
Agent IP
Send SMS/Pager Message Note: This notification method needs to be set up in the Sy st em Administ rat ion Not ificat ion Delivery 1702 settings first. Note: This notification method will use the central proxy settings defined for your PRTG core server. For details, please see Sy st em Administ rat ionSy st em and Websit e 1698 (section Proxy Configurat ion). Recipient Number Define the number the message will be sent to. The format depends on the SMS provider. Usually, you will use a plus sign, followed by country code and number. For example, enter +1555012345. Define the message. A message with information about the sensor status is already predefined. Several placeholders (variables) are used here. You can change it to your liking. To reset this field to its default value, enter a single star symbol * (and nothing else).
Message
1684
08.10.2013
Execut e HTTP Act ion Note: Regardless of the Not ificat ion Summarizat ion method chosen above, notifications of Execut e HTTP Act ion are always sent as soon as possible (ASAP); they are never summarized. Note: This notification method will use the central proxy settings defined for your PRTG core server. For details, please see Sy st em Administ rat ionSy st em and Websit e 1698 (section Proxy Configurat ion). URL Postdata Enter the URL the request will be sent to. If you want to send postdata to the URL, please enter it here. You can use placeholders here.
Execut e Program Note: Regardless of the Not ificat ion Summarizat ion method chosen above, notifications of Execut e Program are always sent as soon as possible (ASAP); they are never summarized. Program file Select an executable file from the list. It will be run every time the notification is triggered. In this list, files in the corresponding / Not ificat ions/EX E sub-directory of the probe system's PRTG installation are shown. In order for the files to appear in this list, please store them as BAT, CMD, DLL, EXE, PS1, or VBS. In order to find the corresponding path, please see Dat a St orage 1912 section. Note: In a cluster setup, please copy your files to every cluster node installation manually. This makes sure the notification can be executed even when the master node fails. If your custom notification executes an external program, this has to be installed on all cluster nodes as well. Please see also Applicat ion Programming Int erface (API) Definit ion 1871 for detailed information. Enter parameters with which the program file will be started. You can use placeholders here. For example, when using a batch file containing a %1 variable, you can provide a value for this variable here.
Parameter
Send Amazon Simple Not ificat ion Service Message AWS Access Key ID Enter your access key as shown in your login area at aws.amazon.com. Please enter a string.
08.10.2013
1685
Send Amazon Simple Not ificat ion Service Message AWS Secret Access Key Location Enter your secret access key as shown in your login area at aws.amazon.com. Please enter a string. Define the location of your Amazon service. Choose between: US-East US-West EU-West ARN Subject Message Enter the Amazon resource name. Please enter a string. Enter the subject of the message. Define the message. A message with information about the sensor status is already predefined. Several placeholders (variables) are used here. You can change it to your liking. To reset this field to its default value, enter a single star symbol * (and nothing else).
More
Applicat ion Programming Int erface (API) Definit ion Knowledge Base: What placeholders can I use with PRTG? http://www.paessler.com/knowledgebase/en/topic/373 Knowledge Base: Documentation of SNMP Traps Sent by PRTG http://www.paessler.com/knowledgebase/en/topic/1133 Knowledge Base: How can PRTG send instant messages to Jabber, ICQ, MSN, Yahoo, etc., using external software? http://www.paessler.com/knowledgebase/en/topic/14803 Knowledge Base: Which audible notifications are available in PRTG 9? Can I change the default sound? http://www.paessler.com/knowledgebase/en/topic/26303
1871
1686
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 3 Account SettingsSchedules
7.11.3 Account SettingsSchedules

In the schedules settings you can define and change schedules for the currently logged in user. You can use schedules to pause 147 monitoring/notifying at certain times with the period lists option, respectively activate it at certain times with the time table option. You can also use schedules to define the time spans that are to be covered when creating reports 1636 .
Sc hedules Settings
Schedules Settings
Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default. Click on the Schedules tab to show a list of all existing schedules. Using the links next to the notification name, you can perform the following actions: Delet e: Delete this notification (not possible for predefined notifications) Used by : Show a list of objects using this notification. Please see also Working wit h Table List s 141 . Additionally, there is multi-edit available. This enables you to change properties of several objects at a time. For more details, please see Mult i-Edit List s 1595 section. Click on the Add new schedule button or click on the name of an existing notification to edit.
08.10.2013
1687
Edit Sc hedule Time Table
Basic Set t ings Schedule Name Enter a meaningful name for the schedule that describes the defined time span(s) or purpose. Select how you want to define a schedule. Choose between: Use weekday /hour t ime t able: Define a schedule with available checkboxes. Lowest increment is one hour. Note: The time table defines active time slots. Use list of period definit ions: Define a schedule by entering text lines using a specific syntax (see below). Note: The period list defines inactive time slots.
Edit Mode
1688
08.10.2013
Basic Set t ings Time Table This selection is only visible if the time table option is enabled above. Define the schedule. It will be used for monitoring objects, reporting, and notifications. You can set time spans with a precision of one hour by setting check marks. If a box is checked, it means the object is active during this hour, if unchecked, the object will be paused during this hour. You can set check marks individually, or change complete ranges for certain days of the week or time spans. To add ranges of check marks, use the buttons All, Mo , Tu, We, Th, Fr, Sa, and Su, as well as the time buttons on the left side. To remove ranges of check marks, use the buttons All Off, Mo Off, Tu Off, We Off, Th Off, Fr Off, Sa Off, and Su Off, as well as the time Off buttons on the right side. Period List This field is only visible if period definitions are enabled above. Define the date/time ranges in which the objects using this schedule will be inactive (i.e., paused). During other times, the objects will be active. Enter the ranges in the format ww:hh:mmww:hh:mm. For details and examples, see Schedules Settings Period Definition Syntax 1690 below.
08.10.2013
1689
Schedules SettingsPeriod Definition Syntax

Define one or more periods of time during which the object using this schedule will be inactive. In each line, enter one range in the format ww:hh:mm-ww:hh:mm: weekday, hour, minute. Possible values for ww: mo, tu, we, th, fr, sa, su. Possible values for hh: Enter the hour in 24 hours format (no AM/PM allowed), i.e. a number between 00 and 23. Possible values for mm: Enter the minute, i.e. a number between 00 and 59.
Example In the following, find an example of a schedule that pauses an object during the weekend as well as on Wednesday evenings.
fr:19:30-mo:06:05 we:18:45-we:23:00
Any object using this schedule will be paused from Friday, 7:30 p.m. to Monday, 6:05 a.m. as well as on Wednesday from 6:45 p.m. to 11 p.m. It will be active during the other times.
1690
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 4 System AdministrationSystem and Website
7.11.4 Sy stem AdministrationSy stem and Website

In the system and website settings you can define global values regarding the PRTG system, web site appearance, web server settings and performance, auto update, etc.
System & Website Settings

Webserver and Websit e Set t ings Web Server IP Address This is the IP address the PRTG web server is running on. This setting is shown for your information only and cannot be changed here. To change this setting, please use the PRTG Server Administrator 1837 . This is the port number the PRTG web server is running on. This setting is shown for your information only and cannot be changed here. To change this setting, please use the PRTG Server Administrator 1837 . When using the web interface, the site name is shown in the title bar of your browser window. It is also used by default in notification emails. Please enter a string. If your PRTG web interface is (additionally) reachable via a DNS name, please enter it here. It is e.g. used by default in notification emails to generate links. Please enter a string. In order to use Act ive Direct ory Int egrat ion 1869 please enter the name of your local domain. Please enter a string or leave the field empty. Define which user account will be used to configure Active Directory access. This account will be used to query the AD for existing groups. Choose between: Use t he PRTG core service account (usually LOCAL SYSTEM): Use the same Windows user account configured for the "PRTG Core Server Service". In a default installation, this is the "local system" Windows user account. If this account does not have the right to query all groups of your Active Directory you should not use this option.
Web Server Port
PRTG Site Name
DNS Name
Active Directory Domain
Active Directory Access
08.10.2013
1691
Webserver and Websit e Set t ings Use explicit credent ials: Define a user account that will be used by PRTG to authenticate against the Active Directory. This should be a user account with full access to all of your Active Directory groups. Active Directory Access User This field is only visible if the use of explicit credentials is chosen above. Enter the Windows user account name which will be used to authenticate for Active Directory configuration. This field is only visible if the use of explicit credentials is chosen above. Enter the password for the Windows user account which will be used to authenticate for Active Directory configuration.
Active Directory Access Password
Geo Maps Map Service Provider Select if and how you want to integrate the Geo Maps feature into the web interface. If enabled, PRTG uses the first line of the location setting of an object 133 to show it on a geographical map. Please choose a map provider: Do not show maps (disables Geo Maps int egrat ion): Disable Geo Maps integration and do not show geographical maps in the web interface. MapQuest : Use MapQuest to show geographical maps. This is the recommended option. Nokia Maps: Use Nokia Maps to show geographical maps. CloudMade (API key required): Use CloudMade to show geographical maps. Please sign up for an API key on their developer website to use this service. Google St at ic Maps (API key required): Use Google Static Maps to show geographical maps. Please sign up for a Google Maps API v2 key to use this service. Note: As of PRTG version 13 you will need to acquire a Google Maps API v3 key! For more information about the different map providers, please see the More 1700 section below. Map Type This setting is only visible for some map providers. Depending on the chosen provider, several options are shown. Each will show map tiles in a different appearance. Please choose a map type from the list.
1692
08.10.2013
Geo Maps API Key (required) This field is only visible if you selected a provider that requires an API key. Please obtain your personal key and paste it here. For more information on how to get an API key, please see the More 1700 section below. Please enter an alphanumeric string.
Scanning Int ervals Available Intervals Define the intervals available in the drop down list of every object's settings 133 . In the text field, enter one value in each line. Use s, m, h, and d for defining seconds, minutes, hours, and days. By default, there are following scanning intervals defined: 30s: 30 seconds 1m: 1 minute 5m: 5 minutes 10m: 10 minutes 15m: 15 minutes 30m: 30 minutes 1h: 1 hour 4h: 4 hours 6h: 6 hours 12h: 12 hours 1d: 1 day Note: We recommend to not use intervals shorter than 10 seconds to prevent system overload. Intervals below 10 seconds are not officially supported!
Upt ime Threshold Minimum Allowed Uptime Threshold Define which uptime in percent will be regarded as 100 percent. This setting affects the colors shown next to the sensor icons in reports. Select one of the predefined values between 90 % and 99.999 %.
08.10.2013
1693
Email Opt ions Email Templates Choose which templates will be used for all emails sent. Use st andard email t emplat es (Recommended): Use this option if you are not sure what to use. These templates offer the best compatibility with all email clients. Use t emplat es from previous version (for upgrade inst allat ions from V7 only ): This option is provided for update installations from V7 only. Use it if you have updated from PRTG version 7 and really want to continue using the old email templates. This can be useful when using custom HTML templates in PRTG 7 format. Depending on the option selected, the content of the other fields in this section changes. Email Header (HTML) Define the HTML text that will be used as the header for each HTML mail. To reset this field to its default value, enter a single star symbol * (and nothing else). Click on the Reset t o default link underneath the text box to do so. Define the HTML text that will be used as a suffix to every HTML mail. To reset this field to its default value, enter a single star symbol * (and nothing else). Click on the Reset t o default link underneath the text box to do so. Select if a footer will be added to plain text mails. Choose between: Append t ext foot er (default ): Add a text footer to all text mails. Define the text below. Do not append t he foot er Append t ext foot er: Do not add a footer to text mails. Email Footer (Text) Define a text that will be used as a suffix to every plain text mail (if enabled above). You can use several placeholders in email templates. See the More 1700 section below for more information. To reset this field to its default value, enter a single star symbol * (and nothing else). Click on the Reset t o default link underneath the text box to do so. Select what will be done when there are new ToDos between:
139
Email Footer (HTML)
For Text Mails
For New ToDos
. Choose
Send an email t o admin account (default ): Send an email to the default administrator email address defined in the PRTG Server Administrator 1837 . Send an email t o specific address: Define a custom email address ToDo notifications will be sent to.
1694
08.10.2013
Email Opt ions Do not send an email: Do not send out any mail indicating that there is a new ToDo. ToDo Mail Address This option is only visible if a specific address for ToDo mails is enabled above. Enter a valid email address ToDo notifications will be sent to.
Dat a Purging Limit s: Select for how many day s hist oric dat a remains accessible Data purging enables you to automatically delete unnecessary data to free up disk space and improve system performance. You can define different time spans for several kinds of data. For further information on storage locations, please see Dat a St orage 1912 section. Logfile Records Define how long records in the system logfile Log Database.db will be kept. Enter a value in days. All entries older than this value will be deleted from the log file automatically. Keep this value as low as possible to enhance system performance. PRTG creates one web server log file every day. Define how many web server log files will be kept. Enter a value in days. All web server log files files older than this value will be deleted automatically. Define for how many days historic sensor data will be kept for all sensors. It is used to create reports 1636 of monitoring data. Enter a value in days. Depending on the used intervals and the number of sensors in your setup, the file containing this data can become large. For smaller installations (500 sensors or less) a value of 365 should be fine. Historic sensor data is the basis for reports on monitoring data. If you decrease this value, there will be less historic monitoring data available! Define how long toplist records will be kept. Enter a value in days. Define how long ToDo entries will be kept. Enter a value in days. Reports generated in PDF format are stored on disk for later reference. Define the maximum age for these reports. Enter a value in days. All reports older than this value will be deleted automatically.
Web Server Log Records
Historic Sensor Data
Toplist Records ToDo Records Reports
08.10.2013
1695
Dat a Purging Limit s: Select for how many day s hist oric dat a remains accessible Configuration AutoBackups PRTG creates one backup of your configuration every day. Define the maximum age for these backups. Enter a value in days. All configuration backup files older than this value will be deleted automatically. Define how long the screenshots of the HTTP Full Web Page Sensor 511 (PhantomJS browser engine) will be kept. Enter a value in days. PRTG will delete older screenshots with every sensor scan.
Full HTTP Sensor (PhantomJS) Screenshots
Unusual Det ect ion The unusual detection can set sensors to an Unusual status 115 when there are values that are untypical for the time span they're measured in, compared to historic monitoring results. When disabled (both settings to Never), sensors will never be shown as unusual. Note: You can enable and disable unusual detection for any object (e.g. for a device, or an entire group) in the Object Set t ings 133 . Show Unusual When Define when a sensor will be shown as unusual, comparing the weekday. Choose between: Never: Disable unusual detection for weekday average. 24h average is <80% or >120% of weekday average 24h average is <50% or >200% of weekday average 24h average is <20% or >500% of weekday average (recommended) 24h average is <10% or >1,000% of weekday average 24h average is <1% or >10,000% of weekday average Show Unusual When Define when a sensor will be shown as unusual, comparing the hour-of-day. Choose between: Never: Disable unusual detection for hour-of-day average. 24h average is <80% or >120% of hour-of-day average 24h average is <50% or >200% of hour-of-day average 24h average is <20% or >500% of hour-of-day average (recommended) 24h average is <10% or >1,000% of hour-of-day average 24h average is <1% or >10,000% of hour-of-day average
1696
08.10.2013
Unusual Det ect ion Logging Define if unusual events will be written to the log file. Choose between: Do not log unusual event s Writ e unusual event s int o t he log
Similar Sensors Det ect ion Similar sensors detection enables PRTG to analyze sensor data for similarities. The detection will run in the background with low priority. The recommended setting for similar sensors detection is to let PRTG automatically decide how many channels will be analyzed. However, you can also override this setting. Analysis Depth Define the number of channels PRTG will analyze to detect similarities between sensors or turn the analysis off. Choose between: Manage aut omat ically based on sensor count (recommended): The analysis depth depends on the total number of sensors you have configured. PRTG will analyze all channels for up to 500 sensors, and only the primary sensor channels for up to 1,000 sensors. If exceeding 1,000 sensors, the analysis will be turned off. Analy ze primary channels only : Only the primary channels of sensors are analyzed. Be aware of potentially high CPU load of PRTG when choosing this setting for more than 1,000 sensors. Analy ze all channels (higher CPU load): Similarity detection is applied to all channels. Be aware of potentially high CPU load of PRTG when choosing this setting for more than 500 sensors. Turn analy sis off: No similarity detection will take place. Choose this option if you are not interested in the analysis results or you want to keep PRTG's CPU load at a minimum.
Aut o-Discovery Set t ings Specific Hour Auto-discoveries can produce a certain load, so you can define at which hour of the day auto-discoveries 181 should be run when configured on a daily or weekly Discovery Schedule. Choose a full hour between 0:00 and 23:00.
08.10.2013
1697
PRTG Soft ware Aut o-Updat e When a New Version is Available Define how PRTG will react to available software updates. This option will be used with the Aut o Updat e 1732 function. Choose between: Aut omat ically download and inst all t he lat est version: Any new PRTG version will be downloaded and installed automatically as soon as your installation detects that there is a newer version available (a check is performed once per day). Note: Without prior notice, installation will restart the PRTG Windows services and may also include a server restart. Aut omat ically download t he lat est version and alert t he admin: Any new PRTG version will be downloaded automatically as soon as your installation detects that there is a newer version available (a check is performed once per day). After successful download, PRTG will create a ToDo 139 message for the administrator. Alert t he admin only : When PRTG detects that there is a newer version available, it will not download updates automatically, but create a ToDo 139 message only. You can still download updates manually on the Aut o Updat e 1732 page. Release Channel PRTG updates are delivered in different release channels. You can choose between maximum stability, or most early access to new features. Please choose between: St able: Updat ed about once per mont h (most conservat ive opt ion, recommended): These are our best tested versions. Choose this channel for live environments you have to depend on! Preview: Updat ed about once per week: Versions in this channel are already thoroughly tested in our labs, but may still contain limitations in certain monitoring configurations. Choose this channel if you are willing to take a little risk for the benefit of getting new features and bug fixes a little earlier. Canary : Updat ed daily (t est ing only , should not be used on live sy st ems): Updated every night. Use with CAUTION! Software versions in this channel are not tested yet, might contain severe bugs, and are provided for testing purposes only. We strongly recommend to not use those versions in live environments you have to depend on! For more information about the different release channels, please see the blog article linked in the More 1700 section below.
1698
08.10.2013
Proxy Configurat ion Use Proxy Server We recommend using PRTG with a direct internet connection. However, if you need to use a proxy, you can configure according settings here. Choose between: No, use direct connect ion t o t he Int ernet : Do not use a proxy. Use this setting if there is a direct internet connection available to the server running the PRTG core server. Yes, in our net work a proxy is mandat ory : Define proxy settings below. Note: Proxy settings are valid for Aut o-Updat e 1732 , Act ivat e t he Product 56 , obtaining Geo Maps 1603 tiles, and for sending out HTTP and SMS text message Not ificat ions 1681 . Proxy Server This setting is only visible if proxy usage is enabled above. Enter the address of the proxy server that will be used for outbound connections. Please enter a valid address. This setting is only visible if proxy usage is enabled above. Enter the port of the proxy server that will be used for outbound connections. Please enter an integer value. This setting is only visible if proxy usage is enabled above. Determine whether the proxy server needs credentials. Choose between: Yes: Define credentials below. No : Do not use credentials for proxy connections. Username This setting is only visible if proxy credentials are enabled above. Enter a username for proxy authentication. Please enter a string. This setting is only visible if proxy credentials are enabled above. Enter a password for proxy authentication. Please enter a string.
Port
Use Proxy Credentials
Password
User Int erface Graph Type Select how graphs are displayed throughout the web interface and in reports 1636 . Use area chart s (recommended): Display filled graphs. Use line chart s: Display graphs using single lines only. We recommend using area charts, as they're better to read. Note: Graphs containing data from more than one cluster node will always be displayed with line charts automatically.
08.10.2013
1699
User Int erface Performance Strategy Select if you want to enable performance improvements for the web interface. All Feat ures: Show all feat ures and live dat a (recommended): Provide full functionality and show all menu items. More Speed: Limit feat ures and delay display (experiment al): Improve reaction time and speed of the web interface by delaying display of monitoring data and hiding some features. For more information on how to speed up the web interface, please see More 1700 section below. Contact Support Links In a PRTG installation running on a commercial license key, a link to the Cont act Support 1741 form is displayed in the lower right corner, enabling you to send us comments and/or support requests about our software at any time. You can switch this feature off and on. Choose between: Show 'Cont act Support ' links for all users (except read only users): Show support links for all users with write access. The links will never be shown for users set to read only. Hide 'Cont act Support ' links for all users: Do not show support links. This setting is valid for all user accounts. Social Network Links You can follow PRTG on your favorite social network if you want to. If you do not want to see the social network buttons in PRTG, you can hide these. Choose between: Show 'follow' links for social net work t o all users: Links to social networks will be displayed in PRTG (default). Hide 'follow' links for all users: Links to social networks will not be displayed in PRTG.
More
Knowledge Base: What placeholders can I use with PRTG? http://www.paessler.com/knowledgebase/en/topic/373 Knowledge Base: How can I speed up PRTGespecially for large installations? http://www.paessler.com/knowledgebase/en/topic/2733 Knowledge Base: Which provider should I use for PRTG's "Geo Maps" feature?
1700
08.10.2013
http://www.paessler.com/knowledgebase/en/topic/34603 Knowledge Base: Which domains and ports does the GeoMaps feature use? http://www.paessler.com/knowledgebase/en/topic/35823 Knowledge Base: How do I get a Google Maps API key for use in PRTG? http://www.paessler.com/knowledgebase/en/topic/32363 Knowledge Base: Which limitations apply when using the Google Maps API in PRTG? http://www.paessler.com/knowledgebase/en/topic/7913 Knowledge Base: How and where does PRTG store its data? http://www.paessler.com/knowledgebase/en/topic/463 Paessler Blog: Version 12 of PRTG introduces "Continuous Rollout" http://www.paessler.com/blog/2012/04/25/
08.10.2013
1701
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 5 System AdministrationNotification Delivery
7.11.5 Sy stem AdministrationNotification Delivery

In the notification delivery settings you can define global settings for notification delivery. If you do not want to use a specific notification method, just leave the respective fields empty.
Note
1609
section.
Notification Delivery Settings

SMTP Delivery SMTP Delivery Mechanism Define how mails are sent using Simple Mail Transfer Protocol (SMTP). Choose between: Direct delivery using built -in mail relay server (default ): Use the SMTP relay server built into PRTG. This server manages its own email queue. For each email, it will look up the target SMTP server via the MX record of the target domain, and send the email. Use SMTP relay server (recommended inside LANs/NATs): Set up your own SMTP relay server to send emails. Enter data below. Use t wo SMTP relay servers (primary and fallback server): Set up two own SMTP relay serversone primary and one as fallback server. Enter data below. Note: When monitoring inside your NAT or LAN it is often a good idea to use your own LAN-based relay server to deliver notification emails quicker.
1702
09.10.2013
SMTP Delivery Sender Email Enter an email address that will be used as sender of all emails. This setting is global and can only be changed centrally here. Enter a name that will be used as sender of all emails. This setting is global and can only be changed centrally here. Enter the HELO Ident for SMTP. This must be a unique name, preferably the DNS name of the machine running PRTG. See SMTP RFC 2821: The sender-SMTP must ensure that the domain parameter in a HELO command is a valid principal host domain name for the client host. This field is only visible if SMTP relay server is enabled above. Enter the IP address or DNS name of the SMTP relay server. This field is only visible if SMTP relay server is enabled above. Enter the port number the SMTP relay server is running on. Standard value is 25. This field is only visible if SMTP relay server is enabled above. Select the kind of authentication required for the SMTP server. Choose between: No aut hent icat ion is required: Use SMTP without authentication. Use st andard SMTP aut hent icat ion: Use standard authentication. SASL aut hent icat ion is required: Use secure authentication via Simple Authentication and Security Layer (SASL). SMTP Relay Username This field is only visible if SMTP authentication is enabled above. Enter a valid user name. This field is only visible if SMTP authentication is enabled above. Enter a valid password. This field is only visible if SMTP relay server are enabled above. Enter the security level for SMTP connections. Choose between: Never: Use insecure connection with plain text transfer. If support ed by server: Use a secure connection (default).
Sender Name
HELO Ident
SMTP Relay Server
SMTP Relay SMTP Port
SMTP Relay Authentication
SMTP Relay Password
Use Encrypted Connection
09.10.2013
1703
SMTP Delivery SSL Method This setting is only visible if SMTP relay server and encryption are enabled above. It is only relevant for secure connections. Select the SSL or TLS version which is supported by your SMTP device. We recommend using the default value. If you do not get a connection, try with another setting.
SMTP Relay Server (Fallback) SMTP Relay SMTP Port (Fallback) SMTP Relay Authentication (Fallback) SSL Method (Fallback) SMTP Relay Username (Fallback) SSL Method (Fallback) SMTP Relay Username (Fallback) SMTP Relay Password (Fallback) Security (Fallback) These fields are only visible if the option for two SMTP relay servers is enabled above. Please see respective settings for primary SMTP relay server above.
SMS Delivery Note: Although PRTG has built-in support for the Application Programming Interface (API) of some SMS providers, we cannot officially provide support regarding these SMS service providers. If you have technical questions about SMS delivery beyond PRTG, please contact your SMS provider directly. Note: Instead of using a pre-configured provider you can always use a custom URL, enabling you to use extended parameters (this is also an alternative when using providers for which we offer pre-configured options). You need an internet connection to send text messages via the HTTP API. For information about sending SMS via separate hardware using third party software, please see the More 1705 section below. Configuration Mode Define how you want to select an SMS provider. Choose between:
1704
09.10.2013
SMS Delivery Select a SMS provider from a list of providers: Select a provider from a list below. Ent er a cust om URL for a provider not list ed: Use another provider and enter the service URL manually below. Service Provider This field is only visible if the provider list is enabled above. Choose a service provider from the list. PRTG offers a small incomplete list of providers. Note: Some providers might require a port configuration in your firewall. See More 1705 section below for more information. This field is only visible if the provider list is enabled above. Enter a user name for the service provider account. This field is only visible if the provider list is enabled above. Enter a password for the service provider account. This field is only visible if the provider list is enabled above. Some providers need an additional API ID or account information. If provided, enter it here. Please enter a string or leave the field empty. This field is only visible if the custom provider option is enabled above. From the documentation of your SMS provider, please enter the service URL that is used to send SMS messages. Use the following placeholders for the recipient phone number and the text message: %SMSNUMBER, %SMSTEX T. Some SMS providers will not allow SMS messages exceeding a certain amount of characters. PRTG will restrict the number of characters according to the length specified in this field. A value of 0 means the SMS is sent at its full length.
Username
Password
API ID / Account
Custom URL
Maximum Length of Text
Note: The notification 1678 methods "Send SMS/Pager Message" and "Execute HTTP Action" will use the central proxy settings defined for your PRTG core server. For details, please see Sy st em Administ rat ionSy st em and Websit e 1698 (section Proxy Configurat ion). Click on the Save button to store your settings. If you change tabs or use the main menu, all changes to the settings will be lost!
More
Knowledge Base: How can I send SMS text message notifications via a modem or a mobile phone with PRTG? http://www.paessler.com/knowledgebase/en/topic/393
09.10.2013
1705
Knowledge Base: Why do I get a connection timeout message when sending SMS via bulksms? http://www.paessler.com/knowledgebase/en/topic/12253 Knowledge Base: Which URLs does PRTG use for its preconfigured SMS providers? http://www.paessler.com/knowledgebase/en/topic/13123 Knowledge Base: How do I send SMS with PRTG using a Clickatell account? http://www.paessler.com/knowledgebase/en/topic/34213 Knowledge Base: How can PRTG send instant messages to Jabber, ICQ, MSN, Yahoo, etc., using external software? http://www.paessler.com/knowledgebase/en/topic/14803 Knowledge Base: Can GMail / Google Apps be used for SMTP relay? http://www.paessler.com/knowledgebase/en/topic/2823
1706
09.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 6 System AdministrationProbes
7.11.6 Sy stem AdministrationProbes

In the probe management settings you can define the settings for probe connections.
Probes Settings
Probe Connect ion Set t ings Access Keys Enter a list of access keys, one in each line. Every (remote) probe that want to connect to this PRTG installation has to use one of these keys. For information how to set this key for a probe, please see PRTG Probe Administ rat or 1857 (Probe Settings) section. Enter a list of remote probe IPs that will be accepted when connecting to this PRTG installation; each IP address in one line. The local probe (127.0.0.1) is always allowed automatically. Allowed IPs are checked first (before denied IPs). You can use PRTG's syntax for IP address ranges here (for information about the syntax please see Define IP Ranges 1878 section). [Empty]: An empty field does not allow any remote probes (but only the local probe). Please enter IP addresses to allow remote probe connections. any : Enter the word any to automatically allow all remote probe connections. Note: This is recommended for use in Intranets only! Note: If the IP address of your remote probe changes regularly (e.g. due to an internet provider assigning IP addresses dynamically), please enter the potential IP range for this remote probe or use the any option. Deny IPs Enter a list of remote probe IPs that will not be accepted when connecting to this PRTG installation; each IP address in one line. This is useful to explicitly deny connections from certain remote probes you do not want to include in your setup any more (e.g., for a certain time). Access to IP addresses allowed above will be denied if you enter them here. This is useful to allow access to an IP range in the field above, but deny access to a single IP address. You can use PRTG's syntax for IP address ranges here (see Define IP Ranges 1878 section).
Allow IPs
13.06.2013
1707
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 6 System AdministrationProbes
Probe Connect ion Set t ings Deny GIDs Enter a list of GIDs, each global ID (GID) in one line. The access to matching GIDs will be denied. If you remove a remote probe from the device tree or if you deny a remote probe after installation, its global ID (GID) will be automatically entered here. This specific remote probe will not be able to connect anymore. Denying GIDs is more precise than denying IPs, where other remote probes at the same location could be excluded too.
Set t ings from t he PRTG Server Administ rat or program IPs for Probe Connections This is a list of the IP addresses on which the PRTG listens to incoming probe communication. 0.0.0.0 means that the server listens on all local network adapter IPs. This setting is shown for your information only and cannot be changed here. To change this setting, please use the PRTG Server Administrator 1837 . This is the port on which PRTG listens to incoming probe communication. This setting is shown for your information only and cannot be changed here. To change this setting, please use the PRTG Server Administrator 1837 .
Probe Connections Port
Remote Probe Setup

Find more information about setting up remote probes in the Mult iple Probes and Remot e Probes 1887 section.
More
Define IP Ranges
1878
1708
13.06.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 7 System AdministrationCluster
7.11.7 Sy stem AdministrationCluster

In the cluster settings you can define the cluster settings. During Failover Clust er Configurat ion 1902 , the cluster settings were already pre-defined. See the cluster status see if all nodes in your cluster are properly connected.
1735
to
Cluster Settings
Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default. You can set up two, three, four, or five nodes in one cluster. In the table of the cluster settings, the information of each node is written in one line.
Node Set t ings Node Name Node ID Enter the name of the node (for display purposes). The ID is unique for every node. We recommend using the default value. You can set the state for every failover node. Choose between: Act ive: Set the node to be active. Inact ive: Set the node to be not active. It will be disabled in the cluster configuration. It will then be not an active part of the cluster and will not appear in the cluster status 1735 any more. This setting is not available for the master node of a cluster. The master is always set to Act ive. IPs/DNS Names used for Connections Between Nodes Define the IP addresses or DNS names that will be used for the connections between the nodes. You can enter different values for every nodenode connection. For example, in the field #2 => #1, enter the IP address that the second cluster member (this is a failover node) will use to connect to the master node server.
Node State
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! In order to put a cluster node to Maint enance Mode, please see PRTG St at usClust er St at us 1735 . The entire setup process for a cluster requires several different steps. For more information and step-by-step guidance, please see Failover Clust er Configurat ion 1902 section.
27.11.2012
1709
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 8 System AdministrationUser Accounts
7.11.8 Sy stem AdministrationUser Accounts

PRTG administrator users can change all users' account settings and add new users.
User Accounts Overview

To change a user's settings, select it from the list by clicking on the user name. The available setting options are the same as shown in the My Account 1673 settings of the currently logged in user (plus some account control options). To add a new user, click on the New User button. The options are the same as for existing users (with slight differences). To batch-add several users at once in a simple way, please click the Mult iple New Users button. In the dialog box appearing, select an existing user group 1715 from the drop down menu and enter or paste a list of email addresses. They can be separated by space, comma, semicolon, or a new line. Click the Add button to confirm. For each address, PRTG will create a new local user account within the selected user group, carrying the email address as value for Login Name, Username, and Email Address. A new password will be generated automatically and sent to the email address. To add a new user group, click on the New User Group button. The options are the same as for existing groups (with slight differences). Access rights in PRTG are given via user groups. Please make sure a user account is member of the right user group 1715 and give access to this group in your device tree object's settings 133 . Note: Predefined objects cannot be deleted!
User Accounts Settings

User Account Login Name Display Name Enter the login name for the user. Enter a name for the user for display purposes. This will not be used for login. Enter the user's email address. Enter the time zone for the current user. Enter in what format dates will be displayed for the current user. Note: This setting will take effect after the next login.
Email Address Timezone Date Format
1710
08.10.2013
User Account Password Define the user's password. For security reasons, the account settings page does not contain the password. Choose between: Don't change Specify new password If you choose to specify a new password, enter the old password, and the new password twice. Note: The new password must be at least 8 characters long; no character may occur more than 3 times. It must contain a number and a capital letter. Hash The hash (passhash) value can the used as password substitute when calling functions from PRTG's Application Programming Interface (API) that require an authentication. For more information please see Using t he PRTG API (Applicat ion Programming Int erface) 1871 section.
Aut o Refresh and Alert ing Auto Refresh Type Specify how PRTG's web pages will be refreshed for the current user. Choose between: Refresh page element s using AJAX (recommended): Automatically refresh the single page elements on the web pages. Refresh whole page: Automatically reload the whole page with every refresh interval. No aut o refresh: Do not automatically refresh web pages. Auto Refresh Interval (sec) This setting is only relevant when auto refresh is enabled above. Enter the number of seconds that will be waited between two refreshes. We recommend using 30 seconds or more. Minimum value is 20 seconds. Note: Shorter intervals create more CPU load on the server running the PRTG core server. If you experience load problems while using the web interface (or PRTG maps 1655 ), please set a higher interval. Define when an audible alarm will be played for the current user on web pages whenever there are alarms 135 in PRTG. Choose between: Never: Do not play sound files on any web pages.
Play Audible Alarms
08.10.2013
1711
Aut o Refresh and Alert ing On dashboard pages only : When there are alarms, play a predefined sound on dashboard 165 pages only. The sound will be replayed with every refresh of a dashboard page. On all pages: When there are alarms, play a predefined sound on all web pages. The sound will be replayed with every page refresh. For more information about audible notifications and supported browsers, please see More 1677 section below.
Web Int erface Homepage URL Define the user's default page loaded after login and when clicking on the Home 165 button in main menu. In order to provide you with a speedy user experience PRTG tries to keep the page size for the page showing the device tree small by automatically folding groups and devices with many items. Define how many groups and devices are shown at maximum before the automatic reduction is performed. We recommend using a value between 10 and 30. In order to provide you with a speedy user experience PRTG tries to keep the page size for the page showing the device tree small by automatically folding groups and devices with many items. Define how many sensors are shown at maximum before the automatic reduction is performed. We recommend using a value between 10 and 30.
Max. Groups/Devices per Group
Max. Sensors per Device
Account Cont rol Account Type This setting is only shown for administrator users. However, it is not shown if the user you modify the account settings for is a member of a group with administrative rights. Define the account type for the current user. Choose between: Read/Writ e User: The user may change settings. Read Only User: The user may not edit any settings. This is a good choice for public or semi-public logins. Note: This setting cannot be changed for the default administrator user.
1712
08.10.2013
Account Cont rol Allow Acknowledge Alarms This setting is only visible if read only user is enabled above. Acknowledging an alarm is an action which requires write access rights. However, you can explicitly allow this action to read-only users. If enabled, they still do not have write access, but may acknowledge alarms 136 . Choose between: Allow: Allow acknowledging alarms for this user. Deny : The user will not be able to acknowledge alarms. Primary Group This setting is only shown for administrator users. Select the primary group for the current user. Every user has to be member of a primary group to make sure there is no user without group membership. Membership in other user groups is optional. For user experience, there is no difference between the primary and other user groups. This setting is only shown for administrator users. Define the status of the current user. Choose between: Act ive: The current user can login to the account. Inact ive: The current user's login is disabled. Use this option to temporarily deny access for this user. Note: This setting cannot be changed for the default administrator user. Last Login Shows the time stamp of the user's last login. This setting is shown for your information only and cannot be changed here.
Status
User Groups Member of Shows the groups the current user is member of. Access rights to the device tree are defined on group level. This setting is shown for your information only and cannot be changed here.
Comments
08.10.2013
1713
History
In the Hist ory tab all changes in the settings of an object are logged with a timestamp, the PRTG user which conducted the change, and a message. The history log keeps the last 100 entries. Click on the Cont inue button to store your settings. If you change tabs or use the main menu, all changes to the settings will be lost!
More
1714
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 9 System AdministrationUser Groups
7.11.9 Sy stem AdministrationUser Groups

PRTG administrator users can change existing user groups or add new ones, and define the users that are member of a certain group. All the security settings as well as further rights management are conducted via the user groups. This means that group membership controls what a user may do and which objects the user will see when logged in. The actual rights for each object can be defined in an object's settings. There, you can define different rights for each user group. To change a user group's settings, select it from the list by clicking on the group name. To add a new user, click on the New User button. The options are the same as for existing users (with slight differences). To batch-add several users at once in a simple way, please click the Mult iple New Users button. In the dialog box appearing, select an existing user group 1715 from the drop down menu and enter or paste a list of email addresses. They can be separated by space, comma, semicolon, or a new line. Click the Add button to confirm. For each address, PRTG will create a new local user account within the selected user group, carrying the email address as value for Login Name, Username, and Email Address. A new password will be generated automatically and sent to the email address. To add a new user group, click on the New User Group button. The options are the same as for existing groups (with slight differences). By default, there aren't any rights set for a newly created PRTG user group. Initially, users in this group will not see any objects in the PRTG device tree. Please edit your device tree object's settings 133 and set access rights for your newly created user group in the Inherit Access Right s section. Note: The easiest way is to set these rights in the Root Group Set t ings 213 . Note: The multi-edit option is not available for the standard user groups PRTG Administrators and PRTG Users Group. Note: Predefined objects cannot be deleted!
User Groups Settings

User Group Set t ings User Group Name Enter a name for the user group.
08.10.2013
1715
User Group Set t ings Administrative Rights Define if the members of this group will be PRTG administrators. If you enable this option, all members of this group will have full access to all monitoring objects, maps, reports, user accounts and user groups, and they can change the PRTG monitoring configuration. Choose between: Yes: Give full PRTG administrator rights to all members of this group. No : Do not make members of this group administrators. Access to monitoring objects for users that are member of this group will be controlled by the Access Right s settings defined in the Object Set t ings 133 of Probes, Groups, Devices, or Sensors. Note: This option is especially useful in combination with the Active Directory option below. Default Homepage Enter a PRTG internal web page. This will set the default homepage for all new users created with this group. A user will be redirected to this page after logging in. This concerns new users either added by an Act ive Direct ory login or by the Add mult iple users feature. Define if this PRTG user group will be connected to a group in your active directory. Choose between: Yes: Connect this group to an AD group. Choose below. For detailed information, please see Act ive Direct ory Int egrat ion 1869 . No : Do not use Active Directory integration for this group, but choose local user accounts instead. Active Directory Group If a valid Active Directory Domain is set in the Sy st em Administ rat ionSy st em and Websit e 1691 settings and Active Directory integration is enabled above, a drop down menu will appear, showing the groups in your Active Directory. Choose the group whose members will be able to log in to PRTG using their Active Directory domain credentials. All of those AD users will be in the security context of the PRTG group you're about to create/edit. For detailed information, please see Act ive Direct ory Int egrat ion 1869 . If your Active Directory contains more than 99 entries for one of the categories "Local", "Global", or "Universal" group, PRTG will display an input field instead of a drop down menu. This is done due to performance reasons. In the input field, you can enter the group name only. PRTG will then add the prefix automatically.
Use Active Directory
1716
08.10.2013
User Group Set t ings New User Type If Active Directory integration is enabled above, define the default rights for all new users in this user group. If a user logs in for the first time using Active Directory credentials, PRTG will automatically create a new local user account for this user, applying the user type defined here. Choose between: Read/Writ e User: The user may change settings. Read Only User: The user may not edit any settings. This is a good choice for public or semi-public logins. Users May Create These Sensor Types Define which sensor types the members of this group will be able to create. A list of all available types is shown with their name. Select the desired types by adding check marks in front of the respective lines. You can also select and deselect all items by using the check box in the table head. This is of special interest for a Managed Service Provider (MSP).
Members Members This setting is available only if Active Directory integration is disabled above. Define which local user accounts will be a member of this group. To add a user account from the list, add a check mark in front of the user name. The user accounts available depend on your setup.
Primary Users User List Shows a list of all user accounts with this group set as primary group. This is shown for information purposes only. You can change it in a user account's settings 1710 .
Comments
History
08.10.2013
1717
1718
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 10 System AdministrationAdministrative Tools
7.11.10 Sy stem AdministrationAdministrative Tools

With the administrative tools you can start system specific processes for debugging purposes. Use them if Paessler's technical support staff advises you to do so. You can start the respective processes by clicking on the Go! button on the right.
Sy stem Administrativ e Tools
Core Administrative Tools

Core Administ rat ive Tools Create Database Snapshot This will create a snap shot of your PRTG configuration. This action can take up to 100 seconds. Once finished, you will find a ZIP file containing a *.dat file in the Configurat ion Aut o-Backups sub folder of your PRTG data directory 1912 . If you're running a PRTG cluster, this action is executed on the cluster node you're currently logged in to. The ZIP file follows the name pattern PRTG Configuration (Snapshot YYYY-MM-DD HH-MM-SS).zip.
04.01.2013
1719
Core Administ rat ive Tools Write Core Status File This will create status files of your PRTG core server. You will find the two text files in the Logs (Sy st em) sub folder of your PRTG data directory 1912 . If you're running a PRTG cluster, this action is executed on the cluster node you're currently logged in to. The files are named Core Status.txt and Core Memory.txt. They are overwritten each time you click this button. PRTG caches tiles for Geo Maps 1603 and user data for Act ive Direct ory Int egrat ion 1869 . Use this button to delete the cache if you encounter broken geo map tiles, or if you changed a user's password in the Active Directory. This will (re)load the lookup files 1879 from the \lookups\cust om folder. In this folder your customized lookup files are stored. If you have created a new lookup file or changed something in an existing lookup file, it might be necessary to load or to reload these files.
Clear Caches
Load Lookups
Probe Administrative Tools

Probe Administ rat ive Tools Write Probe Status Files This will create status files of your PRTG probes. Status files will be written for the local probe running on the PRTG core server (if you're running a PRTG cluster, on the cluster node you're currently logged in to) as well as for all remote probes configured (if any). On the respective systems, you will find four text files in the Logs (Sy st em) sub folder of the PRTG data directories 1912 . The files follow the name pattern Probe Memory XX.txt, ProbeState XX.txt, ProbeState AXX.txt, and ProbeState BXX.txt. They are overwritten each time you click this button. This will restart all PRTG probes as well as the local probe Windows service. If there are any remote probes 1887 configured, the probe Windows services on the respective remote systems will be restarted as well. In order to start single probes only, please see below. Note: If you're running a PRTG cluster, this action is executed on the cluster node you're currently logged in to. In this case, remote probes are only restarted if you're logged in to the primary master node. The cluster probe Windows service of failover nodes is not restarted if this action is executed on the master node. If you want to restart the cluster probe Windows service of a failover node, please log in to this failover node's web interface and click on the same button there.
Restart All Probes
1720
04.01.2013
Probe Administ rat ive Tools Probe [#Number] "[Name]" Information about the connection status is shown. If the probe is currently connected, the field shows the source IP address and port number used by the probe. For the "Local probe", the IP will always be IP 127.0.0.1. You will also see information about the date when the last data packet was received from the probe. If you want to restart a single probe, please click on the Rest art Probe button. Note: Entries for every single probe are following.
04.01.2013
1721
SetupTopics
Account Set t ingsMy Account
1673
Account Set t ingsNot ificat ions Account Set t ingsSchedules

1687
1678
Sy st em Administ rat ionSy st em and Websit e Sy st em Administ rat ionNot ificat ion Delivery Sy st em Administ rat ionProbes
1707
1691
1702
Sy st em Administ rat ionUser Account s Sy st em Administ rat ionUser Groups Sy st em Administ rat ionClust er
1709 1715
1710
Sy st em Administ rat ionAdminist rat ive Tools PRTG St at usSy st em St at us PRTG St at usAut o Updat e
1732 1723
1719
PRTG St at usClust er St at us
1735
PRTG St at usAct ivat ion St at us Downloads and Add-Ons

1737
1736
Chrome Deskt op Not ificat ions Support Cont act Support

1741
1739
Others
There are some settings that have to be made in the Sy st em Administ rat ion Tools available as native Windows applications. For more details, please see sections: PRTG Server Administ rat or PRTG Probe Administ rat or
1837 1836
1857
1722
04.01.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 11 PRTG StatusSystem Status
7.11.11 PRTG StatusSy stem Status

System Status
Click on the Sy st em St at us tab to view relevant system information you may need for debugging or when the support team asks you to provide system information in order to support you with PRTG.
Soft ware Version and Server Informat ion PRTG Version Shows the exact version of the build your PRTG installation is currently running on. Shows the latest auto-update message available from Soft ware Aut o-Updat e 1732 . For example, the message will indicate any PRTG updates ready to be installed. Shows the exact Windows version build and service packs, the number and kind of CPUs, and the computer name, of the system the PRTG core server is installed on. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to. Note: When running PRTG on virtual systems, not all of the mentioned values may be available. Shows the date and time of the system the PRTG core server is installed on. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to. Shows the current CPU load of the system the PRTG core server is installed on. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to. Shows the username in as.
1673
Auto-Update Status
Operating System
Server Time
Server CPU Load
Username
of the PRTG user you're currently logged
Browser
Shows the name and user agent string of the browser you're currently viewing this page with.
07.02.2013
1723
Licensing Licensee Shows the Name of the license 53 you're using for this installation of PRTG. Licensee (name) and license key together build your license information. Shows the beginning and the end of the license 53 key you're using for this installation of PRTG. Licensee (name) and license key together build your license information. Shows the PRTG edition you're using for this installation of PRTG. This determines how many sensors you can use in your monitoring (see below). Shows the activation status of this installation of PRTG. Usually, activation is done automatically on first start-up. Only if PRTG cannot connect directly to the internet, a manual activation is necessary. For details, please see Act ivat e t he Product 56 . Shows the days remaining for your active maintenance contract. You can buy maintenance for each PRTG license. With an active maintenance contract you may download any available updates and use our premium email support, without additional costs. Shows the number of sensors you can use in your monitoring, with your current edition of PRTG (see above). If you reach the limit, each new sensor that you create will be set to a Pause status automatically. In order to upgrade your license right now, click on the Need more sensors? Click here t o upgrade! button to visit our web shop. Editions that allow an unlimit ed number of sensors do not restrict the number of possible sensors by license, so you can create sensors until the performance limit is reached. This means you can use about 20,000 sensors per core server (depending on your system's performance, sensor types, and scanning intervals); for details, see system requirements linked in the More 1731 section below.
Key
Edition
Activation Status
Software Maintenance
Number of Sensors
Sy st em St art up Log Shows the log information created during the last startup of the PRTG core server. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.
1724
07.02.2013
Clust er St at us This box is only visible if you're running a PRTG cluster. This section lists all cluster nodes configured in your monitoring. Node [Number] Shows the name of the cluster node as well as the node type (primary/secondary node) and status (current master/failover node). Additionally, all connections from this node to the other cluster nodes are shown, as illustrated on the PRTG St at us Clust er St at us 1735 page.
Local St at us This box is only visible if you're running a PRTG cluster. This section lists information about the cluster node you're currently logged in to. Server State Cluster Messages Shows internal summary information about the current node and the communication between the nodes. You might be asked about this by Paessler's technical support staff.
Clust er Connect ions This box is only visible if you're running a PRTG cluster. This section lists information about the connections between the different cluster nodes. State of Local Node Shows Treeversion and size of the Server Volume, both internal system information. For each cluster node, the name and IP address is shown, as well as a state CRC code, the time stamp of the last "keep alive" signal sent, the current size of the buffer, and the remote IP. For each cluster node, the name, IP address, and unique identifier is shown, as well as the connection state, and statistic information about the cluster message system which is used for the communication between the different nodes.
State of Cluster Members
Message State of Cluster Members
07.02.2013
1725
Aut o-Discovery Tasks Currently Running Shows the number of auto-discovery tasks that are currently running. A high number of auto-discovery tasks can negatively influence system performance.
Background Tasks Historic Data Shows if PRTG is re-calculating the historic data cache in the background. If so, you will see the tasks to do until done. Usually, this calculation is done after every core server restart. When using xFlow 1820 or Packet Sniffer 1818 sensors, PRTG stores Toplist data. The data stream received is buffered and written to the data directory of the core system. Depending on the number and size of the data stream as well as the hard disk and system performance of the core system, the buffer size can rise. When reaching a buffer size of 500, Toplist data is dropped which can lead to incorrect Toplist values for the sensors. If you recently updated from an older PRTG version (7 or 8), Toplist data needs to run through a one-time conversion process. While conversion is running you may experience a considerably slow monitoring system. Usually, you will see n/a here.
Toplist Buffer
Toplist Upgrade
Dat abase Object s Shows statistic information about your monitoring configuration. This information might be necessary when contacting Paessler's technical support staff. Probes Groups Devices Sensors User Groups Users Shows the total number of probes Shows the total number of groups Shows the total number of devices Shows the total number of sensors
227
configured. in your configuration. in your configuration. in your configuration.

1715
242
261
278
Shows the total number of user groups Shows the total number of users
1710
in your configuration.
configured.
1726
07.02.2013
Dat abase Object s Notifications Schedules Requests/Second Shows the total number of notifications Shows the total number of schedules
1687 1678
configured.
configured.
Shows a value calculated from the total number of sensors and the average scanning interval configured. This number indicates how many monitoring requests per second are sent from the probe(s) to the devices in your network. There are no general guidelines what is a "good" value here. This depends on the sensor types used as well as on your system's performance. Shows a list with numbers and types of sensors used in your configuration. Note: In the list, internal short names are used for sensor types instead of the official designations.
Sensors
Probes This section lists all probes configured in your monitoring. If there are no remote probes configured, only the "Local probe" appears in the list, which runs mandatorily on the PRTG core server. Note: If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to. Remote probes (if any) will only be shown when you're logged in to the primary master node. When logged in to a failover node, the cluster probe running on this node will appear as "Local probe". Probe [#Number] "[Name]" Information about the connection status is shown. If the probe is currently connected, the field shows the source IP address and port number used by the probe. For the "Local probe", the IP will always be IP 127.0.0.1. You will also see information about the date when the last data packet was received from the probe. If you want to restart a single probe, please go to the Administ rat ive Tools Set t ings 1719 .
Sy st em Set t ings Web Server URL Shows the URL to access the PRTG web interface 94 . If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.
07.02.2013
1727
Sy st em Set t ings Web Server IPs Shows all IP addresses the PRTG web server is running at. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to. Shows the port the PRTG web server is running at. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to. Shows the number of ports used by the PRTG web server. Shows a combination of the two values below.
Web Server Ports
Web Server Port Usage Incoming Probe Connection Binding Incoming Probe Connection IPs
Shows a list of all IP addresses on which your current PRTG installation listens to incoming remote probe connections. This is the same information as shown in the Sy st em Administ rat ion Probes 1707 settings. 0.0.0.0 means that the core server listens on all local network adapter IPs. In order to change this setting, please open the PRTG Server Administ rat or 1837 on the system of the PRTG core server. Shows the port number on which your current PRTG installation listens to incoming remote probe connections. This is the same information as shown in the Sy st em Administ rat ionProbes 1707 settings. Default port is 23560. In order to change this setting, please open the PRTG Server Administ rat or 1837 on the system of the PRTG core server. Shows all source IP addresses that will be accepted by the core server for incoming remote probe connections. This is the same information as shown in the Sy st em Administ rat ionProbes 1707 settings and can be changed there. any means that all remote probe connections are accepted, regardless of the IP address of the remote probe system. Shows all source IP addresses that will be denied by the core server for incoming remote probe connections. This is the same information as shown in the Sy st em Administ rat ionProbes 1707 settings and can be changed there. Denied IPs are superior to allowed IPs. If this field is empty, there are no denied IPs. Note: PRTG automatically adds the IP address of a remote probe system to this list when you delete a remote probe from your device tree 78 .
Incoming Probe Connection Port
Probe Allow IPs
Probe Deny IPs
1728
07.02.2013
Sy st em Set t ings DataPath Shows the path where PRTG stores its configuration, monitoring database, etc. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to. In order to change this setting, please open the PRTG Server Administ rat or 1837 on the system of the PRTG core server (or of the respective cluster node, if applicable).
Web Server Act ivit y Shows statistic information about the web server since last startup. All values are reset when the core server is restarted. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to. Time Since Startup Shows the time that has passed since the PRTG web server was started. Shows the total number of page views on this core server. Shows the total number of geo maps shown on this core server. Shows the total number of HTTP requests to this core server. Shows for how many (percent) of the HTTP requests above the page delivery took longer than 500, 1,000, or 5,000 milliseconds. Shows a calculated number of the HTTP request values above. The lower this number, the faster is your installation's web interface.
Page Views Geo Maps HTTP Requests HTTP Requests > 500/1000/5000 ms Slow Request Ratio
Sy nchronizat ion The core server holds the configuration of the entire monitoring and deploys it to the probes. This section shows statistic information about the synchronization of the core server with the local probe and all connected remote probes (if any), since last startup of the core server. All values shown here are reset when the core server is restarted. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to. Note: Only when logged in to the primary master node you will see synchronization data for remote probe connections.
07.02.2013
1729
Sy nchronizat ion Last Synchronization with a Probe Probe/Core Message Count Sync Cycle Speed Shows the time stamp of the last probe synchronization, and if there is still something to do. Shows the total number of messages sent between core and probe(s), as well as a calculated message speed value. Shows the time necessary for a full synchronization, as well as an evaluation comment of this time (usually, this will be "OK"). Shows the total number of configuration requests and the requests that still have to be sent. Internal debug information. Usually, this value will be 0.
Configuration Requests Sent Configuration Requests Deleted Configuration Requests With Response
Internal debug information. Usually, this value will be 0.
Sy st em Warnings If there are any warnings they will be shown here. Usually "None" will be shown here.
Core Sy st em Memory Shows machine-oriented information regarding the memory usage of the core server system. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.
Thread Informat ion Shows machine-oriented information regarding the threads running on the core server system. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.
1730
07.02.2013
More
Paessler Website: Detailed System Requirements for PRTG Network Monitor http://www.paessler.com/prtg/detailed-requirements Knowledge Base: How can I speed up PRTGespecially for large installations? http://www.paessler.com/knowledgebase/en/topic/2733
07.02.2013
1731
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 12 PRTG StatusAuto-Update
7.11.12 PRTG StatusAuto-Update

Whenever a new version of the software is available from the Paessler website PRTG will download the setup file automatically if a direct internet connection is available. The administrator will then receive a ToDo 139 message with instructions to initiate the update installation. For customers using a Freeware or Trial Edition 17 , automatic software updates are available at any time. Customers using a Commercial Edition 18 need to have an active maintenance contract so updates are available.
Using Auto-Update
Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax interface on a master node. For other user accounts, interfaces, or nodes, not all of the options might be available as described. When using a cluster installation, failover nodes are read-only by default. To view the auto-update page of your PRTG installation, select Set up | Soft ware Aut oUpdat e from main menu. If there is a new version available, you will see detailed information about the available version. Please read these notes carefully! In order to install an available version, click the Inst all Updat e [version number] button. You will be asked to confirm installation and licenseand that's it! Click on the button Show Aut o-Updat e Log to show corresponding log entries.
Automatic Software Update Page
1732
08.10.2013
Manually Install an Interim Update

Not all available updates from Paessler will be pushed to all customers, but they are still available from the website. Sometimes Paessler support may ask you to update to the latest version. In this case please click the Download Updat e [version number] button. PRTG will then connect to the Paessler servers and download the setup file, regardless of the status of the update-check. Note: In order to use this function, a direct internet connection is necessary on the computer running the PRTG core server.
Select Other Release Channel

PRTG is available in three different release channels. For details about continuous rollout and release channels, please see the blog article in the More 1734 section below. St able: Updated about once a month. Best tested versions. We recommended this channel for live environments you have to depend on! Preview: Updated about once a week. Thoroughly tested in our labs, but may still contain limitations in certain monitoring configurations Canary : Updated every night. Use with caut ion! Software versions in this channel are not tested yet, might contain severe bugs, and are provided for testing purposes only. We strongly recommend to not use those versions in live environments you have to depend on! In order to change the release channel you receive updates from, please open the Sy st em Administ rat ionSy st em and Websit e 1698 page by clicking on the Select Ot her Release Channel button and change settings in the PRTG Software Auto-Update section.
Notes
There are a few things we ask you to consider regarding automatic software updates: In order for auto-update to work the machine running the PRTG core server needs direct internet access. If a proxy connection is needed, please configure it in the Sy st em Administ rat ionSy st em and Websit e 1698 settings. For details about the update servers, see More 1734 section below. During installation the core server may be restarted without notice. Existing remote probes will be updated automatically, causing short downtimes in monitoring of remote locations. In rare cases a manual update of remote probes is required after you update the core server. In these cases you will be notified in the device tree, and monitoring of remote locations will be interrupted until you perform the manual update on the system(s) running the remote probe(s). In a cluster installation the update needs to be installed on one node only. The new version will then be deployed to all other cluster nodes automatically (causing a short downtime for the monitoring on the cluster nodes, one after another).
08.10.2013
1733
If you run several individual PRTG core servers that are not in a cluster, for example, in combination with the Ent erprise Console 1744 , an update has to be initiated and confirmed for each single core server. You can disable automatic downloading in the Sy st em Administ rat ionSy st em and Websit e 1698 settings. Updates will then only be downloaded on request, when you click on the Download Updat e [version number] button.
More
Knowledge Base: Which servers does PRTG connect to for Software Auto-Update and for Activation? http://www.paessler.com/knowledgebase/en/topic/32513 Knowledge Base: Which information does PRTG send back to Paessler? http://www.paessler.com/knowledgebase/en/topic/28103 Paessler Blog: Version 12 of PRTG will introduce "Continuous Rollout" http://www.paessler.com/blog/2012/04/25/news/prtg-12-introduces-continuous-rollout
1734
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 13 PRTG StatusCluster Status
7.11.13 PRTG StatusCluster Status

Cluster Status
Click on the Clust er St at us tab to view all nodes connected to the cluster. This tab is only available if you're running PRTG in cluster mode 76 . Following information is shown: Cluster Status with all connected nodes as table and graphic Cluster Log with all log entries concerning cluster connections
Example of a PRTG Cluster Status View
Click on the St art Maint enance Mode link to put a cluster node in maintenance mode. A node in this mode is still connected to the cluster, but its monitoring results are discarded until you click on the St op Maint enance Mode link. You can use this functionality to explicitly exclude a node from monitoring if you know that the monitoring values will not be accurate, for example, because you're reconfiguring things, etc. During maintenance, a cluster node is displayed with a transparent color in the overview graphic. For more information about cluster settings, please see Sy st em Administ rat ionClust er section.
1709
27.11.2012
1735
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 14 PRTG StatusActivation Status
7.11.14 PRTG StatusActivation Status

Activation Status
Click on the Act ivat ion St at us tab to view information about the activation status of your PRTG Network Monitor license. For more details about activation, please see Act ivat e t he Product 56 section.
License Act ivat ion St at us Licensed Edition Shows the edition of the license you are currently using for this installation of PRTG. This determines how many sensors you can use in your monitoring. If you are running a PRTG cluster, this will show information for the system of the cluster node you are currently logged in to. Shows the activation status of your PRTG license. Usually, activation is done automatically on first start-up. The activation status is typically Act ivat ion OK. Only if PRTG cannot connect directly to the internet, a manual activation is necessary. For details, please see Act ivat e t he Product 56 . Shows the last message regarding the activation of your license.
Current activation status of your software license
Last message about activation Current activation stamp
Shows an internal activation stamp code.
1736
09.01.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 15 Optional Downloads and Add-Ons
7.11.15 Optional Downloads and Add-Ons

To see optional downloads, select Set up | Downloads from main menu. Click on the tabs to switch between different options.
Downloads / Add-Ons Tabs
There are the following downloads available: PRTG Enterprise Console Apps for iOS & Android Remote Probe Installer PRTG Add-Ons
1737 1737
1737
1737
PRTG Billing Tool
1738
Chrome Desktop Notifications
1738
PRTG Enterprise Console

Download the Windows Graphical User Interface (GUI) "Enterprise Console" to the current system. Using it, you can access the PRTG interface with a native Windows application. The version of the Enterprise Console must match your version of PRTG. For more information, please see Inst all t he Ent erprise Console 63 section.
Apps for iOS & Android

iPRTG is a native iPhone application that enables you to use the PRTG web interface with the original iFeeling. You can buy iPRTG in the AppStore. PRTG for Android gives you the possibility to monitor PRTG on the go. For more information, please see More 1738 section below.
Remote Probe Installer

With remote probes you can extend your monitoring to distributed networks that are not directly reachable from your PRTG core installation. The version of the remote probe installer must match your version of PRTG. For more information, please see Inst all a PRTG Remot e Probe 58 section.
PRTG Add-Ons
This will display a link to the PRTG add-ons page on Google Code. There you will find a collection of various add-ons for PRTG Network Monitor and their source code. For more information, please see More 1738 section below.
08.10.2013
1737
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 15 Optional Downloads and Add-Ons
PRTG Billing Tool

This will display a link to information and download of the PRTG Billing Tool. The PRTG Billing Tool is an application that can read PRTG sensor data and generate bills in PDF format. We provide this tool as a basis to develop your own billing applications. For more information, please see More 1738 section below.
Chrome Desktop Notifications

This tab is only visible if you're accessing the PRTG web interface with Google Chrome browser. For details, please see Chrome Deskt op Not ificat ions 1739 section.
More
Paessler Website: SmartPhone Apps for PRTG http://www.paessler.com/apps Project Hosting on Google Code: PRTG AddOns http://code.google.com/p/prtg-addons/ Paessler Website: Billing Tool for PRTG http://www.paessler.com/tools/billingtool
1738
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 16 Chrome Desktop Notifications
7.11.16 Chrome Desktop Notifications

While you are logged in to the PRTG web interface with your Chrome browser, PRTG can use it to show notifications on your desktop whenever there are new alarms in your monitoring. Desktop notifications will be shown (by default, in the lower right corner of your desktop) whenever there are new alarms after a page refresh. The notification will display the number of new alarms and the current number of each sensor status. Click on X to close the notification.
Example of a Chrome Desktop Notific ation
In Chrome's default configuration, you have to initially allow those notifications for each installation/profile of Google Chrome. To do so, in the PRTG web interface, please click on Set up 1671 , then click on Chrome Deskt op Not ificat ions.
Chrome Desktop Notific ations in Setup
Chrome Desktop Notifications Settings

On the settings page, you see one of the following status messages. St at us: Click but t on below t o enable Deskt op Not ificat ions Click on the Enable Chrome Deskt op Not ificat ions button to add your PRTG URL to Chrome's list of allowed sites for desktop notifications. On top of your Chrome browser window a message will appear, asking you to allow desktop notifications. Click on Allow to add the web interface's URL to the allowed sites.
Clic k on 'Allow' to enable Chrome Desktop Notific ations
St at us: Sorry , Deskt op Not ificat ions cannot be enabled Desktop Notifications are explicitly blocked for the PRTG web interface's URL in the Chrome options. Please see Notifications Settings in Google Chrome 1739 below.
08.10.2013
1739
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 16 Chrome Desktop Notifications
Deskt op Not ificat ions enabled Chrome Desktop Notifications are successfully activated. In order to disable them, please see Notifications Settings in Google Chrome 1739 below.
Notifications Settings in Google Chrome

To disallow or re-allow your web interface's URL for desktop notifications, please edit your Chrome browser's options: Choose Opt ions | Under t he Hood, in the Privacy section, click on the button Cont ent set t ings... . In the Not ificat ions section, change settings corresponding to your needs. For example, click on Manage except ions... and remove the URL of your PRTG web interface to disable the feature. Or remove a blocked URL to re-enable the feature again.
1740
08.10.2013
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 17 SupportContact Support
7.11.17 SupportContact Support

To open the Cont act Paessler Support / Send Your Feedback t o Paessler window in PRTG, choose Set up | Cont act Support for the main menu. You can open this form also via the footer Cont act Support on any page in PRTG. On the one hand, you can adapt this page as feedback form. Help improve PRTG by providing criticism, praise, bug reports, and feature requests. Any comments are welcome! Your feedback will be handled directly by the Paessler support team. On the other hand, you can use this function in order to ask for support regarding technical issues. To make the support contact more comfortable, PRTG can automatically attach a screenshot in combination with a Support Bundle which contains several selected PRTG log and status files. This information will help the support team a lot in order to analyze any issues you may have encountered with PRTG. Once you are finished, click on Submit t o Paessler Support to send your request, or click on Cancel to return to the page from which you opened the contact form. You can be sure that you will receive an answer by our support team within one or two business days, no matter whether you provide feedback or you have a question. Note: PRTG will try to send your feedback / support question to Paessler as an email using Simple Mail Transfer Protocol (SMTP). Please ensure that your PRTG installation is able to send emails to external destinations!
The Support / Feedbac k Form
21.10.2013
1741
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Setup 17 SupportContact Support
Ask a Question or Give Us Your Feedback

Provide the following information in this section of the contact form: Your Ticket ID PAExxx: If you have already opened a new ticket (either directly via email to support@paessler.com, or via the Knowledge Base, or via the support form on paessler.com), enter its ID here. You can find it in your confirmation email regarding the request we received. You can provide the ID with "PAE" in front or just the number. Otherwise, a new ticket will created. Your Email Address: Enter your email address here. You can provide any of your addresses; however, recommended and default is the email address of your PRTG account. Your Comment s: Leave your comments here. It can be feedback or support questions. Please describe your issue as detailed as possible!
Attach a Screenshot and/or Support Bundle

In order to provide as helpful information as possible, you can attach a screenshot of the current page and various support bundles with useful analytical data about your PRTG installation. In section Screenshot , choose between: Creat e and at t ach screenshot (recommended): This will create a screenshot of the currently displayed page in PRTG. It will be sent with your ticket. A preview will be shown below the screenshot section. Note: If you encounter issues on a specific page in PRTG, call the contact support form on this page in order to get a screenshot of it. Do not at t ach screenshot : No screenshot will be taken. Note: We recommend to attach a screenshot in order to understand your request easier and faster. In section Support Bundle, you can choose between several packages which differ in coverage of information: At t ach Support Bundle Base Pack (recommended): Contains the following information: system status lists of sensors regarding their current states Core state data Probe Health sensor data current log entries At t ach Base Pack plus log files: Contains log files of your PRTG installation in addition to the Base Pack. At t ach Base Pack plus log files and PRTG configurat ion file: Additionally contains the configuration file. Note: Send this package only if our support team told you so! This file contains encrypted passwords readable by Paessler support. Do not at t ach a Support Bundle: No files will be attached. Choose this option only when sending feedback.
1742
21.10.2013
Part 8
Enterprise Console
07.02.2013
1743
Part 8: Enterprise Console |
Enterprise Console
The Enterprise Console (formerly called "Windows GUI") is one alternative interface 73 you can use to connect to the PRTG core server to configure your setup, view monitoring results and keep an eye on your network. It is a native Windows application for fast access to data and monitoring management. The Enterprise Console provides extended popup window functionalities as well as a seamless link to the Ajax web interface 94 where you can change your monitoring configuration and access further functionalities such as reporting, Maps, system setup, etc. Some of these functionalities are shown with an embedded webkit browser, for others an external browser window is opened.
Access Several Core Servers in One Console

As an additional functionality, you can configure access to several PRTG core servers in the Enterprise Console. The console will then show data of your independent core server installations at a glance (for example, the device tree and alarms list), so you can manage your monitoring centrally, also when it is spread across different servers.
Getting Started
With an installation of PRTG Network Monitor, the Enterprise Console is included and installed automatically on the computer running the PRTG core server. If you want to use the Enterprise Console on another computer, please download and install it there, as described in the Inst all t he Ent erprise Console 63 section. Note: The Enterprise Console is mainly designed to review and manage an existing installation of PRTG which has already been set up. If you just started monitoring, we recommend you use the Configuration Guru 32 and the web interface's auto-discovery 181 function and add your network's devices there. For detailed instructions, please see Quick St art Guide seamlessly switch to the Enterprise Console.
28
section. Once finished, you can
More
The following sections introduce the features and concepts of the Enterprise Console.
1744
07.02.2013
Part 8: Enterprise Console |
Enterprise ConsoleTopics
First St art
1746
General Lay out
1747
Menu Tabs and Page Cont ent PRTG Servers Opt ions
1779 1776
1751
Windows Menu St ruct ure Cont ext Menus

1791
1786
Short cut s Overview
1792
Related Topics
94
180
Ajax Web Int erfaceDevice and Sensor Set up Ajax Web Int erfaceAdvanced Procedures Ot her User Int erfaces
1796 1584
07.02.2013
1745
Part 8: Enterprise Console | 1 First Start
8.1
First Start
This section will help you start the Enterprise Console for the first time.
Opening the Enterprise Console

Double click the PRTG Ent erprise Console icon in the Windows start menu to open it. As soon as it opens, the Enterprise Console will try to connect to your PRTG installation, according to the given PRTG server connection settings. In a fresh install of PRTG, the settings for the Enterprise Console installed on the computer running the PRTG core server are already predefined, so you can use the Enterprise Console right away. If you get an error message when opening the Enterprise Console, please check the connection settings. For example, editing the settings is necessary in case the IP address of the server has changed. If you get an error message, please check your connection settings. For detailed information, please see PRTG Servers 1776 (PRTG Server Connect ion) section.
Popup Window
By default, the Enterprise Console runs in the background and shows a popup message whenever there are new alerts, new messages, or new ToDos for your monitoring. The popup window will be one of the first things you see after opening the Enterprise Console.
Example of a Popup Window
This window is shown as always on top. Click on the OK button to close it. You can change the popup behavior in the Enterprise Console settings. For detailed information, please see Opt ions
1780
settings (Sy st emAlert ing ).
1746
07.02.2013
Part 8: Enterprise Console | 2 General Layout
8.2
General Layout
The main layout of the Enterprise Console program consists of different elements which will be shortly described here.
From top to bottom, the main layout consists of: The Windows menu
1748
The page header bar 1748 with the PRTG logo, the viewpoint arrow symbols, the refresh icon, and the sensor states overview. The menu tabs bar and page content The server selection The news feed The status bar
1749 1749 1748
underneath.
1749
and search bar
in the upper right corner.
underneath the page content. at the bottom of the window.
1750
Often, data and settings are displayed directly in the Enterprise Console. For some functionalities and extended setup, a new window of the system's default browser will be opened and the web interface 94 will show up. In this case, you'll be logged in to the web interface automatically via username and hash value 1673 . In your browser, it might be necessary to confirm the certificate used by PRTG's web server. For more information, please see SSL Cert ificat e Warning 99 section. If you configure your Enterprise Console for a connection with more than one PRTG core server, keep an eye on the server selection 1749 bar to choose which server's data you want to access.
21.10.2013
1747
Windows Menu
The Windows menu gives access to general configuration and settings. Find a detailed description in the Windows Menu St ruct ure 1786 section.
Page Header Bar
Enterprise Console's Page Header Bar
The page header consists of the following parts: PRTG Logo Click on the PRTG Network Monitor logo to open the Ajax web interface 94 in the browser configured in the Enterprise Console's Opt ions 1779 . If several PRTG core servers are configured, the browser will load the web interface of the server currently selected in the Devices 1752 tab. Previous Viewpoint / Next Viewpoint (Arrow Sy mbols) The enterprise stores the different views shown while you navigate through the application. Using these arrows (or using the shortcuts Alt+Left and Alt+Right) you can step back and forth in the history, just as known from your browser. Refresh (Arrow Circle Sy mbol) Click on the refresh symbol (F5) any time to refresh the current screen. This will immediately query data for the current screen from all active PRTG core servers, just as the automatic refresh does, which can be configured in the Opt ions 1779 settings. Global Sensor St at us Sy mbols This area shows the aggregated status of all sensors from all active PRTG core servers, divided into different sensor states. Depending on the 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, Warning , Pause, Unusual, or Unknown state. Click on a box to view a list of all sensors in the respective status. For a detailed description, please see Sensor St at es 115 section. Note: When viewing sensor lists, you can show the sensors of one server at a time only. So, the global sensor overview shows the total number of sensors in a certain state on all active servers, but viewing a list of all sensors in a certain state from all servers is not possible for performance reasons.
Menu Tabs Bar and Page Content

You can navigate through your setup using the menu tabs bar. Please take a few minutes to familiarize yourself with all menu items. The page content underneath varies dependent on the selected menu tab. It shows various information about your monitored objects. For a detailed description of all tabs, please see the Menu Tabs and Page Cont ent 1751 section.
1748
21.10.2013
Server Selection
Enterprise Console's Serv er Selec tion and Searc h Bar
In the server selection bar you see all active PRTG core server connections which are configured for the current Windows user account (saved in the registry). The server you select here determines globally which information is shown in all Menu Tabs 1751 (except the Devices tab; the server selection does not apply there). Depending on your selection, Libraries, Sensors, Alarms, Maps, Report s, Logs, ToDos, and Set up options will be shown for the respective server only. Select All PRTG Servers to show consolidated information for all active PRTG core servers which appear in the list. Note: For technical reasons, you cannot show consolidated information from all servers in the Sensors, Set up, and Search Result s tab. In order to use those tabs, please decide on a single PRTG core server from the server selection bar. Select Manage PRTG Servers to add or remove PRTG Servers existing one.
1776
from the list, or to edit an
Search Bar
Select a single PRTG core server from the server selection 1749 bar and enter a key word to search the respective server. In the Search Result s tab, the Enterprise Console will display matching monitoring objects, help topics, and related objects. If you click on a monitoring object (for example, a sensor) in the search results, the Enterprise Console will open this object in the Devices 1752 tab, showing details in the device tree. Note: If you start another search underneath the results within the Search Result s tab, this will open a browser window, showing results. Note: If you have configured a connection in the PRTG Servers 1776 options which uses a Root ID 1778 other than 0, this setting will be ignored while searching. In this case, Search Result s for the entire server (starting at Root ID 0) will be shown.
News Feed Bar

The news feed bar shows latest news by Paessler. Click on the bar to open a popup with an overview about recent articles. You can open a specific article in the web browser by clicking on the particular header or on More... If you do not want to show the news feed in your Enterprise Console, click on the X besides the bar. You can enable it again via View 1789 in the main menu.
21.10.2013
1749
Status Bar
Enterprise Console Status Bar
The status bar shows the version number of your PRTG Enterprise Console and the Paessler logo which leads you to the Paessler website when you click on it. Furthermore, the status bar contains a Cont act Support 1741 link which will open a window to leave feedback or to ask for support.
1750
21.10.2013
Part 8: Enterprise Console | 3 Menu Tabs and Page Content
8.3
Menu Tabs and Page Content

Under the different menu tabs of the Enterprise Console you can navigate through various pages with information about your monitored objects, such as your network's status, monitoring results, etc.
The following sections introduce the available options within the different tabs: Devices Libraries Sensors Alarms Maps
1752
1759
1761
1763
1765
Report s Logs
1769
1767
ToDos Set up
1771
1773
Search Result s
1775
13.06.2013
1751
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 1 Devices
8.3.1
Devices
The Enterprise Console has a tab-like interface. Using the tabs you can navigate through various pages with information about your monitored objects, such as your network's status, monitoring results, etc., as well as access maps, reports, and settings.
Enterprise Console Menu Tabs Bar
There is documentation available for the following tabs: Devices Libraries Sensors Alarms Maps
1752
1759
1761
1763
1765
Report s Logs
1769
1767
ToDos Set up
1771
1773
Search Result s
1775
Devices Menu Tab

The Devices tab will be your starting point for everyday use. The page is split into two parts. On the left hand side, it shows the tree-like device view which lists all configured PRTG core servers with their probes, groups, devices, and the sensors on the devices, in a hierarchical order. Next to each object you see an overview of the number of sensors, grouped by their current status. The first child node of the tree is called Favorit e Devices and Sensors. It contains all devices and sensors that are marked as favorites. In order to add an object to the favorites list, rightclick on it and select the Add t o Favorit es entry from the context menu 148 . For details, please see Priorit y and Favorit es 145 section. Note: For more information about the hierarchical order of the different objects in the device tree, please see Object Hierarchy 78 section. On the right side you see details about the object selected on the left. The information is spread over several tabs.
Enterprise Console Sub-Tabs underneath Dev ic es Tab
1752
21.10.2013
Edit Objects in the Device Tree

Using the Edit menu (or the object's context menu 1791 ) you can access different important functions of the items you have currently selected in the device tree on the left hand side, such as Add devices or sensors to the favorites list (or remove them from the list) Sort all sub nodes of an object alphabetically Move objects up and down in the tree Check now Pause monitoring Access tools and many more For details about the available options, please see Windows Menu St ruct ure .
1786
Select Multiple Items in Device Tree

In the device tree shown on the left, you can select one or more objects, even from different PRTG core servers. Hold down the Ctrl key to select more objects simultaneously. Usually, you will select more than one item in order to view combined graphs, or to apply a command from the Windows Menu 1786 (for example, Check Now or Pause) to several objects. When selecting multiple items, the sub-tabs on the right side will show data for all selected items at a glace. For example, when selecting two sensors, you will see their tables next to each other. Graphs will actually be shown combined! This is a great way to instantly show one chart containing the graphs of all selected objects. Each sensor channel will then be shown as one line. This aggregated view works for all kind of objects. Note: The tab Live Graph will show data for sensors only. Note: Underneath each graph a legend is shown. Hover an entry in the legend to display the according line in the graph above in bold.
21.10.2013
1753
Aggregated Graph View in Enterprise Console
Note: You may need to enlarge the Enterprise Console's window in order to see all tables and graphs.
DevicesOverview
The Overview tab shows general information about the selected object. Depending on the object selected, different information is displayed. For servers, probes, and groups the table shows information in the Name section only, such as priority and parent objects. On the right side, a geographical Map is shown, if enabled in your PRTG configuration as well as in the Enterprise Console's View menu 1789 . For detailed information about geographical maps, please see Geo Maps 1603 section. For devices, the Overview tab shows device details and summary graphs for different time spans, as well as a list of all sensors on this device. For sensors, the Overview tab shows sensor details, current status, and the last value of all sensor channels, as well as sensor graphs for different time spans. You can also edit channel settings in this tab by clicking on a channel's gear icon (for details, please see section Sensor Channels Set t ings 1566 ).
DevicesLive Graph, 2 days, 30 days, 365 days

These tabs are only available if the Large Single Graph (Ctrl+L) view is enabled in the Windows Menu 1789 (View). For Small Mult iple Graphs view please see DevicesGraph 1755 section below.
1754
21.10.2013
Select one of the tabs to display an object's monitoring results as Live Graph (content available for sensors only), or for different time spans in more or less detail (2 day s, 30 day s, 365 day s). In every tab, you will see graphs as well as data tables. While viewing a sensor graph you can hide single sensor channels individually. Simply remove the check mark symbol in front of a channel name underneath the graph, and the according channel's line will disappear. You can also Show all or Hide all channels by clicking on the buttons besides the channel names. The graph view will be reset immediately. Note: The days mentioned here are the default setting. You can change the detail of the different graphs any time in the PRTG System Administrator program. See section PRTG Server Administ rat or 1847 (Memory Usage) for more details. Note: Underneath each graph a legend is shown. Hover an entry in the legend to display the according line in the graph above in bold.
DevicesGraph
This tab is only available if the Small Mult iple Graphs (Ctrl+S) view is enabled in the Windows Menu 1786 (View). For Large Single Graphs view please see above. This will show an overview with single graphs and data tables for live data, 2 days, 30 days, and 365 days. It might be necessary to enlarge the window in order to display all graphs. Note: The days mentioned here are the default setting. You can change the detail of the different graphs any time in the PRTG System Administrator program. See section PRTG Server Administ rat or 1847 (Memory Usage) for more details. Note: Underneath each graph a legend is shown. Hover an entry in the legend to display the according line in the graph above in bold.
DevicesHistoric Data
The Hist oric Dat a tab is available for sensors only (not for probes, groups, or devices). When 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.
21.10.2013
1755
Historic Data Tab of a Ping Sensor
Depending on the File Format option you choose, the results will be shown: HTML web page: Open a new window, showing the historic data report X ML file: A new browser window will open, showing the historic data report as XML file. CSV file: A new browser window will open, showing the historic data report as CSV file. When you click on one of these items, a new window or tab of the external browser configured in the Enterprise Console's Opt ions 1784 will open and PRTG will automatically login and redirect you to the respective web page. If your browser displays a certificate warning, please find more information in the SSL Cert ificat e Warning 99 section. View and functionality are the same as in the web interface. For details about the available Hist oric Dat a report options please see Hist oric Dat a Report s 126 section of the Ajax Web Interface 94 documentation.
DevicesLog
Click on the Log tab to show a table list with all log information on this object. This is a subset of the entries available via the Logs 1769 menu tab. In the list, one hundred entries are shown at a time. Use the arrow symbols above the list to show other items. You can jump to the beginning of the list, or browse through it hundred by hundred. If the list has more than one entry, you can also sort the items by the contents of a certain column. To sort, simply click once or twice on the header of the column you want to sort by.
1756
21.10.2013
DevicesSettings
In the Set t ings tab the currently selected object's settings are loaded from the web interface and displayed. View and functionality are the same as in the web interface. For every type of object and for every sensor, different options are available. For detailed information, please see the following sections (depending on the selected object) in the Ajax Web Interface 94 documentation: Probe Set t ings Group Set t ings Device Set t ings Sensor Set t ings
227
242
261
278
DevicesSettingsMulti-Edit
If you select several objects on the left side, the Set t ings tab will switch into multi-edit mode. Using multi-edit, you can set a check mark for one or more settings. All changes will be applied to all selected objects. The multi-edit dialog displays settings which are common among the selected objects only. If you select sensors only on the left side, the Set t ings tab will display a new tab row with a Channel Set t ings tab. Using this tab you can multi-edit the settings of any channels which are common among the selected sensors, as long as the channels have the same name. Set a check mark for one or more channel settings. All changes will be applied to all selected sensors. Note: You cannot use multi-edit for objects on different PRTG core servers.
DevicesNotifications
In the Not ificat ions tab the currently selected object's settings are loaded from the web interface and displayed. View and functionality are the same as in the web interface. You can set different notification triggers. For detailed information, please see the Sensor Not ificat ions Set t ings Web Interface 94 documentation.
1573
section in the Ajax
Note: You cannot change notification settings for multiple objects at a time. We recommend using the Inherit ance of Set t ings 82 for easy configuration.
DevicesComments
In the Comment s tab the currently selected object's settings are loaded from the web interface and displayed. View and functionality are the same as in the web interface.
21.10.2013
1757
DevicesHistory
In the Hist ory tab all changes in the settings of an object are shown with a timestamp, the PRTG user which conducted the change, and a message.
Drag & Drop Sorting in Device Tree

In the device tree, you can also move probes, groups, and devices simply via drag and drop. Activate it in the Windows menu 1786 Edit | Drag & Drop Sort ing and then drag your objects as you like: You can move devices and groups, or add groups or devices to other groups. You can also move objects via the context menu 1791 . Note: You cannot move objects in the following cases: You cannot move any objects from one PRTG core server to another. You cannot move sensors from one device to another. In order to clone sensors to other devices using drag&drop, please use the Ajax Web Interface 94 . For detailed information, please see Manage Device Tree 211 section. You cannot move devices from one group to another. You cannot move groups from one probe to another. You cannot move probes from one core server to another.
1758
21.10.2013
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 2 Libraries
8.3.2
Libraries
1752
1759
1761
1763
1765
Report s Logs
1769
1767
ToDos Set up
1771
1773
Search Result s
1775
Using Libraries is a great way to keep an eye on your network's status, as you can select which sensors you would like to see there. For a general introduction to Libraries, please see Libraries 1619 section.
Libraries Menu Tab

The page is split into two parts. On the left hand side you see all available libraries from one or several servers, on the right hand side the actual libraries are displayed. Single-click on a library's name to display it. In the tabs above the library, select from Overview 1619 , Management 1626 , Set t ings 1629 , Comment s 1633 , and Hist ory 1634 . Each of these tabs loads the respective functionality of the Ajax Web Interface 94 . Please remember to click the Save button in order to apply your settings. Please find detailed information in the Libraries 1619 section. Underneath the tabs bar, there are different options available to change the current library view: You can set sensor filters (set or remove check marks to include or exclude sensors in a certain state) and change the device tree view (for details about the tree view, please see General Lay out Tree View Lay out 102 section). Double-click on a library's name to open the library in the configured external web browser. You can then edit it or add new libraries on this PRTG server. For more information see Libraries 1619 section.
07.02.2013
1759
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 2 Libraries
Right-click on a map's name to open a context menu Add Library , Edit , Delet e, Open in Web Browser.
1791
. The following options are avaiable:
Libraries Menu TabAdd Library

Click on the Add Library button to add a new library to a core server. Depending on the current setting shown in the server selection 1749 bar in the upper right corner, an (embedded) browser window will be opened immediately (if one specific server is selected), or you will be prompted with a selection window, asking you to choose the core server you want to add the new item to. Choose an installation to open a browser window.
Enterprise Console Serv er Selec tion Dialog
For details about adding a library, please see Libraries St ep By St ep
1622
1760
07.02.2013
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 3 Sensors
8.3.3
Sensors
1752
1759
1761
1763
1765
Report s Logs
1769
1767
ToDos Set up
1771
1773
Search Result s
1775
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. You can filter by object, sensor type, and current sensor state.
Sensors Menu Tab

Note: For technical reasons, this function is available for one server at a time only. If you have configured more than one PRTG core server, please choose one server from the server list in the upper right corner. Click on the Sensors entry in the menu tabs bar to show a table list of all sensors. You can enable a filter to only show certain sensors. To do so, choose from three different drop down menus to build a filter. With each filter you can further decrease the number of sensors shown. By Ty pe The second drop down menu shows all sensor types available in your monitoring setup. Select an entry to only show sensors of this type. The default value is All Ty pes.
13.06.2013
1761
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 3 Sensors
By St at e The third drop down menu shows all possible sensor states. Select an entry to only show sensors that currently show this status. Choose between All St at es, Down, Down (Acknowledged), Down (Part ial), Warning , Up, Paused, Unusual, and Unknown. The default value is All St at es. Note: If you click on a sensor symbol in the page header bar 1748 , you can directly view a sensor list filtered by the selected sensor state for the selected server. If you have filtered out all sensors and the list below shows no entries, try removing some filters by reverting them to the default values. To disable all filters, remove the check mark in front of the Filt er by option at the beginning of the line. Note: In the column Last Value only the last value of the sensor's primary channel will be shown. In the list, one hundred entries are shown at a time. Use the arrow symbols above the list to show other items. You can jump to the beginning of the list, or browse through it hundred by hundred. If the list has more than one entry, you can also sort the items by the contents of a certain column. To sort, simply click once or twice on the header of the column you want to sort by. From this list view, you can select multiple items in order to apply the same action to them, for example, Edit | Check Now. You can select multiple items by the following means (you can also combine them): Click and hold your left mouse key while hovering the lines you want to select Hold the Ctrl key while clicking to toggle the selection status of a single line Click a line and hold the Shift key while clicking another line to select all lines in between.
1762
13.06.2013
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 4 Alarms
8.3.4
Alarms
1752
1759
1761
1763
1765
Report s Logs
1769
1767
ToDos Set up
1771
1773
Search Result s
1775
Alarms Menu Tab

In the Alarms tab the alarms of all active PRTG core servers can be displayed. To do so, select All PRTG Servers from the server selection in the upper right corner. The Alarm list shows all sensors that are currently in a Down, Down (Part ial), 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. Using the options Error, Warning , and Unusual, you can hide and show sensors in the respective status by removing and adding a check mark. When choosing Error, this includes sensors in the states Down, Down (Part ial), and Down (Acknowledged). If the list has more than one entry, you can also sort the items by the contents of a certain column. To sort, simply click once or twice on the header of the column you want to sort by. From this list view, you can select multiple items in order to apply the same action to them, for example, Edit | Check Now. You can select multiple items by the following means (you can also combine them): Click and hold your left mouse key while hovering the lines you want to select
07.02.2013
1763
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 4 Alarms
Hold the Ctrl key while clicking to toggle the selection status of a single line Click a line and hold the Shift key while clicking another line to select all lines in between.
Acknowledge Alarm
An acknowledged alarm will show up in the alarms list as "acknowledged" (see Sensor St at es 115 ) and will not trigger 1573 any more notifications 1609 . Note: If the alarm condition clears, the sensor will usually return into an Up status immediately with the next sensor scan. In order to acknowledge an alarm, right-click on a sensor and choose Acknowledge Alarm... from the context menu, enter a message and click the OK button. The message will appear in the sensor's last message value. You can choose between: Acknowledge Indefinit ely ... , acknowledge For 5 Minut es... , For 15 Minut es... , For 1 Hour... , For 3 Hours... , For 1 Day ... , or Unt il... . If you choose Unt il... a popup window will appear where you can define a date. If the alarm condition still exists after this date, the sensor will show a Down status again. Only users 1710 with write access rights may acknowledge alarms. Read-only users can be given the right to acknowledge alarms, too.
1764
07.02.2013
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 5 Maps
8.3.5
M aps
1752
1759
1761
1763
1765
Report s Logs
1769
1767
ToDos Set up
1771
1773
Search Result s
1775
Maps Menu Tab

The page is split into two parts. On the left hand side you see all available maps from one or several servers, on the right hand side the actual maps are displayed. Single-click on a map's name to display it. In the tabs above the map, select from View Map, Maps Designer 1660 , Set t ings 1667 , Get HTML 1669 , and Comment s 1670 . Each of these tabs loads the respective functionality of the Ajax Web Interface 94 . Please remember to click the Save button in order to apply your settings. Please find detailed information in the Maps 1655 section. Double-click on a map's name to open the map in the configured external web browser. You can then edit it using the Maps Designer 1660 , or add new maps on this PRTG server. For more information see Maps 1655 section. Right-click on a map's name to open a context menu Add Map, Delet e, Clone, Open in Web Browser.
1791
. The following options are available:
Maps Menu TabAdd Map

Click on the Add Map button to add a new map to a core server.
07.02.2013
1765
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 5 Maps
Depending on the current setting shown in the server selection 1749 bar in the upper right corner, an (embedded) browser window will be opened immediately (if one specific server is selected), or you will be prompted with a selection window, asking you to choose the core server you want to add the new item to. Choose an installation to open a browser window.
For details about adding a map, please see Maps St ep By St ep
1658
1766
07.02.2013
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 6 Reports
8.3.6
Reports
1752
1759
1761
1763
1765
Report s Logs
1769
1767
ToDos Set up
1771
1773
Search Result s
1775
Reports Menu Tab

In the Report s tab you see all available reports from one or several servers, in one list. If the list has more than one entry, you can also sort the items by the contents of a certain column. To sort, simply click once or twice on the header of the column you want to sort by. Choose one report and double click on it's name. The page will be split into two parts. On the left hand side you still see all available reports from one or several servers, on the right hand side the options for the currently selected report are displayed. Single-click on a report's name to display its options. In the tabs above the report, select from Run Now 1642 , St ored Report s 1644 , Set t ings 1645 , Select Sensors Manually 1652 , Sensors Select ed by Tag 1654 , and Comment s 1654 . Each of these tabs loads the respective functionality of the Ajax Web Interface 94 . Please remember to click the Save button in order to apply your settings. Please find detailed information in the Report s 1636 section. Right-click on a report's name to open a context menu 1791 . The following options are available: Add Report , Delet e, Clone, Open in Web Browser. Double-click on any report's name on the left side to return to the initial list view of all reports.
07.02.2013
1767
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 6 Reports
Reports Menu TabAdd Report

Click on the Add Report button to add a new report to a core server. Depending on the current setting shown in the server selection 1749 bar in the upper right corner, an (embedded) browser window will be opened immediately (if one specific server is selected), or you will be prompted with a selection window, asking you to choose the core server you want to add the new item to. Choose an installation to open a browser window.
For details about adding a report, please see Report s St ep By St ep
1639
1768
07.02.2013
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 7 Logs
8.3.7
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.
Enterprise Console Logs
There are two possibilities to call the logs list: Either you click on the Log tab while viewing an object's details in the Devices 1756 menu tab, or you choose the Logs entry from the menu tabs bar.
Logs Menu Tab

1752
1759
1761
1763
1765
Report s Logs
1769
1767
ToDos Set up
1771
1773
Search Result s
1775
Click the Logs entry in the menu tabs bar to show a list of all log entries of a PRTG core server.
07.02.2013
1769
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 7 Logs
You can either view the entries of one or all servers. If you have configured more than one PRTG core server and you want to view entries from all servers in your PRTG Servers 1776 setup, simply select All PRTG Servers from the server selection in the upper right corner. The background color of a row indicates the value listed in the St at us column. It is shown green for Up, yellow for Warning , red for Down, and white for all other values. You can enable a filter to only show certain log entries of a certain event. The drop down menu shows all possible event types. Select an entry to only show events of the respective event type. Choose between All Event s, Up & Down, Down, Warning , Unusual, Up, Paused & Resumed, Probe Relat ed, Aut o Discovery , Not ificat ions, and St at us Messages. The default value is All Event s. If you have filtered out all sensors and the list below shows no entries, try another filter or revert to All Event s. In the list, one hundred entries are shown at a time. Use the arrow symbols above the list to show other items. You can jump to the beginning of the list, or browse through it hundred by hundred. If the list has more than one entry, you can also sort the items by the contents of a certain column. To sort, simply click once or twice on the header of the column you want to sort by.
1770
07.02.2013
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 8 ToDos
8.3.8
ToDos
1752
1759
1761
1763
1765
Report s Logs
1769
1767
ToDos Set up
1771
1773
Search Result s
1775
ToDos Menu Tab

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. The list shows all available ToDos.
07.02.2013
1771
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 8 ToDos
You can either view the entries of one or all servers. If you have configured more than one PRTG core server and you want to view entries from all servers in your PRTG Servers 1776 setup, simply select All PRTG Servers from the server selection in the upper right corner. Note: 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 Sy st em Administ rat ionSy st em and Websit e 1691 (Email Options) settings of each PRTG core server.
Acknowledge ToDos
Every ToDo should be viewed and acknowledged. Acknowledged ToDos will no longer appear in the Enterprise Console's ToDos list. In order to acknowledge a single ToDo, select it and from the main menu, select Edit | Acknowledge select ed ToDo object (you can also right-click on the respective Todo to view the context menu with the same option). In order to acknowledge all ToDos in the list, select Edit | Acknowledge all ToDos from the main menu (you can also right-click any Todo to view the context menu with the same option).
View ToDos in Web Interface

Double click on any ToDo to view the ToDos list of the respective PRTG core server in the Ajax Web Int erface 94 . When you click on one of these items, a new window or tab of the external browser configured in the Enterprise Console's Opt ions 1784 will open and PRTG will automatically login and redirect you to the respective web page. If your browser displays a certificate warning, please find more information in the SSL Cert ificat e Warning 99 section.
1772
07.02.2013
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 9 Setup
8.3.9
Setup
1752
1759
1761
1763
1765
Report s Logs
1769
1767
ToDos Set up
1771
1773
Search Result s
1775
Setup Menu Tab

Note: For technical reasons, this function is available for one server at a time only. If you have configured more than one PRTG core server, please choose one server from the server list in the upper right corner. In the Set up tab you can access all options available in the Set up 1671 menu of the Ajax web interface. Please note that settings for user accounts and user groups are arranged a little different in the Enterprise Console. For more information please refer to the respective section in the web interface's documentation. Account Settings: My Account
1673
Not ificat ions Schedules

1687
1678
System Administration:
12.02.2013
1773
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 9 Setup
Sy st em & Websit e
1691
Not ificat ion Delivery Probes

1707
1702
Administ rat ive Tools Clust er

1709
1719
(available in a cluster
76
setup only)
User Accounts: You see a list of configured user accounts. Select one to change settings. For details, please see User Account s 1710 section. User Groups: You see a list of configured user groups. Select one to change settings. For details, please see User Groups 1715 section. PRTG Status: Sy st em St at us Clust er St at us Aut o Updat e
1732 1723
1735
(available in a cluster
76
setup only)
Optional Downloads and Add-Ons: PRTG Ent erprise Console Apps for iOS & Android Remot e Probe Inst aller
1737
1737
1737
1774
12.02.2013
Part 8: Enterprise Console | 3 Menu Tabs and Page Content 10 Search Results
8.3.10 Search Results

1752
1759
1761
1763
1765
Report s Logs
1769
1767
ToDos Set up
1771
1773
Search Result s
1775
Search Results Menu Tab

Note: For technical reasons, this function is available for one server at a time only. If you have configured more than one PRTG core server, please choose one server from the server list in the upper right corner. The Search Result s tab is only visible if you did a search using the search box in the upper right corner. For your search, all matching objects on one PRTG core server are shown. Click on a monitoring object in the results to show it in the Enterprise Console's Devices 1752 tab. Other objects, for example, chapters from the help file, are loaded in an external browser. When you click on one of these items, a new window or tab of the external browser configured in the Enterprise Console's Opt ions 1784 will open and PRTG will automatically login and redirect you to the respective web page. If your browser displays a certificate warning, please find more information in the SSL Cert ificat e Warning 99 section.
07.02.2013
1775
Part 8: Enterprise Console | 4 PRTG Servers
8.4
PRTG Servers
The Enterprise Console connects to the web server API running on every PRTG core server installation. It supports saving the configuration for a connection to one or more PRTG core servers. In a full PRTG installation, there is already a connection predefined. Note: For a successful connection, the program versions of Enterprise Console and PRTG core server have to match. When connecting to several servers please make sure they all run on the same software version.
PRTG Servers List

From the main menu, select File | All PRTG Servers to view a list of all servers configured for the currently logged in Windows user account. You can also access this list by clicking on the PRTG Servers entry above the device tree, or by selecting the Manage PRTG Servers option from the server selection in the upper right corner.
PRTG Serv ers List in Enterprise Console
The list shows the server or display name, as well as login information used. In the St at us column you see an overall sensor status for this server connection. If there is any Background Act ivit y on the respective server, which can potentially affect performance and response times, this is displayed as well. In the list, set a check mark for every PRTG server you want to poll with every update interval. If a server is not reachable, the Enterprise Console will deactivate it automatically after several unsuccessful connection attempts. When opening the Enterprise Console, it will automatically re-establish the connection to all active servers.
Add or Edit a PRTG Server Connection

In the icons bar above the server list, please click the Add button to add a new server connection configuration. Use the Delet e button to remove an entry from the list. To change existing settings, choose an existing server from the list and click the Edit button. When adding or editing, a dialog box will appear, allowing you to enter connection information. Note: Connection settings are stored for each Windows user individually, in the registry, under the following node: HKEY_CURRENT_USER\Software\Paessler\PRTG Network Monitor\WinGUI
1776
07.02.2013
PRTG Serv er Connec tion Settings in Enterprise Console
Server IP/DNS name Enter the IP address or DNS name of the PRTG web server the Enterprise Console will connect to. This is the same address or name as defined in the web server settings for the core server. For detailed information please see PRTG Server Administ rat or 1837 (Web Server) section. Please make sure that the set values match. Please make sure that the server is reachable (especially when using Network Address Translation (NAT)) and no firewall settings are blocking the connection. Port Enter the port on which the PRTG web server is running. This is the same port as defined in the web server settings for the core server. For detailed information please see PRTG Server Administ rat or 1837 (Web Server) section. Please make sure that the set values match. Please make sure that the server is reachable (especially when using Network Address Translation (NAT)) and no firewall settings are blocking the connection. Login Name Enter the login name that will be used to login to the web server. This can be the administrator login or the login of another PRTG user. In a new installation, the login name is prt gadmin by default. For detailed information about user accounts please see Sy st em Administ rat ionUser Account s 1710 section. Password Enter the password for the login name entered above. In a new installation, the password is prt gadmin by default.
07.02.2013
1777
Root ID Enter the ID of the object that will be considered the root of the device tree. Default value is 0, which is the Root group of your configuration. If you enter an other object's ID here, the device tree will start at this object, only showing all other objects below in the hierarchy. This is useful to only view a part of the device tree, which is loaded much faster. You can create several connections that only differ in the Root ID value in order to quickly switch between different views within your configuration, choosing different PRTG core server connections in the Enterprise Console's Devices 1752 tab. Display Name (opt ional) Optionally enter a name that will be displayed in the Server list. If you leave this field blank, the Server IP/DNS name setting will be displayed there. Click the OK button to save your settings.
1778
07.02.2013
Part 8: Enterprise Console | 5 Options
8.5
Options
From the Windows menu settings dialog.
1786
of the Enterprise Console, select File | Opt ions... to open the
You can choose from these options on the left hand side: System
1779
SystemAlerting Tools
1782
1780
Select External Browser Proxy Settings

1785
1784
System
From the Windows menu 1786 of the Enterprise Console, select File | Opt ions... to open the settings dialog. Please select a setting on the left and change the respective values on the right side. Click the OK button to save your settings. Change general system settings for the Enterprise Console.
Enterprise Console Options
St art Wit h Windows By default this setting is enabled. With this setting enabled, the Enterprise Console will start up automatically when this computer is started. Show in Tray By default this setting is enabled.
07.02.2013
1779
With this setting enabled, a PRTG icon will be shown in the Windows tray. On mouse over, it will show a balloon info with the most important status information about your monitoring; with a right-click you can access a menu with access to the most important functions. In order to use any alerting functionalities (see SystemAlerting 1780 section), you must enable this option. If the tray icon is not shown, no alerting from the Enterprise Console will be available. Clear Tray Blink Not ificat ion aut omat ically Whenever there are new entries in the Alarms 1763 list, the tray icon will start blinking. If you enable this option, the tray icon will stop blinking automatically as soon as there are no more alarms. With this option disabled, it will keep blinking, even if all alarms should be cleared meanwhile. Rest ore last Viewpoint aft er Applicat ion St art If this option is enabled, the Enterprise Console saves information about the currently shown view (for example, sensor details, a certain graph, or a Map). It is written to the registry 1785 when you close or exit the program. When you open the Enterprise Console again, it will try to restore the same view. Only if the object is not available any more (due to changes on the server, or due to unavailability of a server), the default view will be loaded. Updat e Int erval (s) Define the number of seconds that will be waited before the screen is refreshed. Default value is 60. Language Choose the language for this program from the drop down menu. Default is English. Depending on your installation, you may be able to choose other languages here. This setting will influence the language of the Enterprise Console only.
SystemAlerting
From the Windows menu 1786 of the Enterprise Console, select File | Opt ions... to open the settings dialog. Please select a setting on the left and change the respective values on the right side. Click the OK button to save your settings. You can define what the Enterprise Console will do in case of new Alarms, Log Ent ries, or ToDos. The settings are the same for all of these three cases, but you can individually define them for each case. On the left side, please select either Alert ing for new Alarms, Alert ing for new Log Ent ries, or Alert ing for new ToDos and define the settings as follows.
1780
07.02.2013
Note: All alerting options only take effect when the Show in Tray option is enabled in the system 1779 settings above; if the tray icon is disabled, there will be no alerting from the Enterprise Console.
Enterprise Console Sy stem Settings for Alerting
Blink Tray Icon The tray icon will blink if there are new items to be alerted for. You can additionally set the Clear Tray Blink Not ificat ion aut omat ically option in the system 1779 settings above. Balloon Info in Tray Show a balloon info next to the PRTG tray icon if there are new items to be alerted for. Popup Message Show a popup message window if there are new items to be alerted for. Note: The popup window will be always on top until it's closed. Play Sound Play an audible notification if there are new items to be alerted for. There is a default sound defined. To change it, please click on the folder symbol and select any standard WAV file from your hard disk drive. PRTG already comes with a small set of sounds you can choose from. Note: The sound file will be played only on the computer running the Enterprise Console. Open GUI
07.02.2013
1781
Open the Enterprise Console if there are new items to be alerted for.
Tools
From the Windows menu 1786 of the Enterprise Console, select File | Opt ions... to open the settings dialog. Please select a setting on the left and change the respective values on the right side. Click the OK button to save your settings. In the Tools settings you can define commands that will be available in the Windows Menu and context menu 1791 of groups, devices, and sensors. A command to initiate a remote desktop connection is already predefined.
1786
Note: In order for the tool function to work with your Windows version, you may need to run the Enterprise Console as administrator. Please click the Add button to add a new command, or choose an existing one from the list and click the Edit button to change the settings. Use the Delet e button to remove an entry from the list.
Enterprise Console Tools Settings
Name Enter a custom name for your command as it will show up in the context menu. Command Enter the command you want to execute on the local machine. This can be, for example the name of a program or script, with or without path, according to your system's configuration. Paramet ers Enter the parameters with which the command will be called.
1782
07.02.2013
You can use the placeholders (variables) shown in the window. Other placeholders are not possible. During runtime, these placeholders will be replaced by the respective values set for the object you have selected. For example, the %id placeholder will be replaced by the ID of a group, a device, or a sensor, depending on which object you're executing the command for. Paramet ersAvailable placeholders The following placeholders (variables) are available in the Enterprise Console.
Placeholder
Available For Groups
Available For Devices
Available For Sensors
Will Be Resolved To
%id
X X
X X X
X X X
The object's ID as shown in brackets behind the name The object's Name value. The sensor's or device's IP Address/DNS Name value The sensor's Last Message value The sensor's Last Result value The sensor's Ty pe value
%name %host
%message
X X X
%value %type
If a placeholder is used in combination with an object it is not available for, it will simply not be resolved, but the placeholder itself will be returned. Note: To see the output of all placeholders for different objects you can create a simple test tool that displays the output in a command line window. Just create a tool with the command cmd and the following content in the Paramet ers field:
/K echo.id: %id && echo.name: %name && echo.host: %host && echo.message: %message && echo.value: %value && echo.type: %type
Then, click an object in the device tree and run the tool from the Tools option in the menu (either Windows 1786 or context menu 1791 ). Short cut
07.02.2013
1783
Select a key shortcut for the command. Choose an F-Key from the list or select None to not use a key.
Select External Browser

From the Windows menu 1786 of the Enterprise Console, select File | Opt ions... to open the settings dialog. Please select a setting on the left and change the respective values on the right side. Click the OK button to save your settings. With this settings you can define which browser the Enterprise Console will use when you select a command which requires opening an external browser window, for example when calling View | Open Web GUI... . You can only select browsers installed on the system running the Enterprise Console; other browser options are disabled.
Enterprise Console Options Selec t External Browser
By default, the system's default browser is opened. To change the Enterprise Console's behavior, choose between: Use sy st em default browser (browser.exe ) Use IE (Version: x) Note: Only Microsoft Internet Explorer 9 or 10 is supported by the Ajax web interface! You cannot use it with Internet Explorer 8 or earlier and Opera Browser! We recommend using Google Chrome 27 or later (recommended) or Mozilla Firefox 21 or later as external browser. Use Firefox (Version: x) Use Chrome (Version: x) Use Safari (Version: x)
1784
07.02.2013
Proxy Settings
From the Windows menu 1786 of the Enterprise Console, select File | Opt ions... to open the settings dialog. Please select a setting on the left and change the respective values on the right side. Click the OK button to save your settings. If the connection to the PRTG core servers requires a proxy connection, you can set it here.
Enterprise Console Options Proxy Settings
Choose between: No Proxy Use a direct connection to the servers. Use Sy st em Set t ings Use your Windows default settings, configured in Internet Explorer. To view these settings, open the Internet Explorer on your system and select Tools | Int ernet Opt ions from the menu. Select the Connect ions tab and click on the LAN set t ings button. Manual Proxy Configurat ion Manually enter a proxy configuration. Please enter the IP address/DNS name of the proxy, a port number, as well as username and password (if required by the proxy). Note: Only basic authentication is available!
Settings Storage
For each individual Windows user account, the settings of the Enterprise Console are stored in the Windows registry. For details, please see Dat a St orage 1912 .
07.02.2013
1785
Part 8: Enterprise Console | 6 Windows Menu Structure
8.6
Windows Menu Structure

The Windows menu of the Enterprise Console has four main menu items: File Edit
1786
1786
View Help
1789
1790
File
All PRTG Servers Show a list of all configured PRTG core server connections. For detailed instructions, please see PRTG Servers 1776 settings. Opt ions... Open the dialog to set options and to configure one or more PRTG core server connections. For detailed instructions, please see Opt ions 1779 settings. Close or Exit This menu item appears as either Close or Exit , depending on whether the tray icon is enabled or disabled in the Opt ions 1779 settings. Close will close the Enterprise Console, but alerting will still be available via the tray icon. You can also double click on the tray icon to reopen the Enterprise Console. Exit will completely shut down the Enterprise Console. This option is only available if the tray icon is not running. Close and Exit This menu item is only shown if the Show in Tray option is enabled in the Opt ions 1779 settings. It will completely shut down the Enterprise Console and tray icon, so no tray alerts are shown any more.
Edit
The content of the Edit menu varies, depending on whether and which objects are selected within the Devices 1752 , Sensors 1761 , or Alarms 1763 tab. Note: Some of the options will open the Ajax web interface. When you click on one of these items, a new window or tab of the external browser configured in the Enterprise Console's Opt ions 1784 will open and PRTG will automatically login and redirect you to the respective web page. If your browser displays a certificate warning, please find more information in the SSL Cert ificat e Warning 99 section. Check Now This will perform an immediate scan for the selected object. Det ail This will calls the overview tab for the selected object.
1786
21.10.2013
Edit Here you can access the pages for editing Set t ings... , Not ificat ions, Access Right s... , and Management (not for sensors) of the selected object. In addition, you can Rename... this object. Add Group... This option is available only when a probe or group (not the Root group) is selected. This will open the Ajax web interface which guides you through adding a new group to the selected probe or group. For detailed instructions, please see Add a Group 194 . Add Aut o-Discovery Group... This option is available only when a probe or group (not the Root group) is selected. This will open an assistant which guides you through adding such a group. For detailed instruction, please see section Aut o-Discovery 181 . Add Device... This option is available only when a probe or group (not the Root group) is selected. This will open the Ajax web interface which guides you through adding a new device to the selected probe or group. For detailed instructions, please see Add a Device 200 . Add Sensor... This option is available only when a device is selected. This will open the Ajax web interface which guides you through adding a new sensor to the selected device. For detailed instructions, please see Add a Sensor 209 . Run Aut o-Discovery This option is available only when a device is selected. If you select this option, an automatic search is started, adding new sensors to the selected device. The search is running in the background. If found, you will see new sensors after a few minutes automatically. For more information, please see Aut o-Discovery 182 (Run Aut o-Discovery Now). Creat e Device Templat e... This option is available only when a device is selected. This will open the Ajax web interface which guides you through creating a device template; this will then be available in autodiscovery 181 . For detailed instructions, please see Creat e Device Templat e 1600 . Sort Alphabet ically This option is available only when a probe, a single group, or a device is selected. This will sort direct children of the selected node such as groups, devices, or sensors in alphabetical order. The ordering will be stored in the monitoring configuration and cannot be revoked. Check Now For all selected objects from the device tree (use the Ctrl key to select multiple objects), perform an immediate scan. This will poll all selected devices and query new data for all sensors on them. If you choose this option for a probe or a group, data for all sensors in the object hierarchy 78 underneath will be queried. Acknowledge Alarm... This option is available only when a sensor in a Down or Down (Part ial) status is selected. For details on how to acknowledge an alarm, please see Alarms 1764 section. Delet e This will delete the selected object(s). You will be asked for confirmation before anything is actually deleted. Clone... This option is available only when a single group, device, or sensor is selected. This will open the Ajax web interface which guides you through cloning the selected object. For detailed instructions, please see Clone Object 1592 .
21.10.2013
1787
Move This will move the selected object(s) of the device tree (use the Ctrl or Shift key to select multiple objects). Choose between Top, Up, Down, and Bot t om to move the object(s) to the top or bottom of the mother node, resp. one entry up or down. If you have selected several objects which are not neighbors to move them, then the first object in the list will be moved up resp. down and the others will be attached below this object. You can also move the selected object(s) to another group with To Ot her Group... A popup will appear in this case with information about the selected object and the sub-objects which will also be moved. Please choose a target group from the list. Note: Please see section Devices 1758 for details about allowed movements. Pause For all selected objects from the device tree (use the Ctrl key to select multiple objects), you can pause and resume monitoring, or set a sensor to error for testing purposes. Hover to see available options. You can choose between: Pause Indefinit ely , Resume from pause, pause For 5 Minut es, For 15 Minut es, For 1 Hour, For 3 Hours, For 1 Day , Pause Unt il... , or Set Sensor t o Error. The last option only takes effect when a sensor is chosen. If you choose Pause Unt il... a popup window will appear where you can define a date. Monitoring will be resumed after this date. Rename... Rename the selected object. A popup will appear. Please enter a new name and confirm with the OK button. Priorit y /Favorit e With this option you can set the priority for any object and you can add devices and sensors to favorites. For details, please see section Priorit y and Favorit es 145 . Hist oric Dat a This will open the historic data tab of the selected object. You can choose between Last 2 day s... , Last 30 day s... , and Last 365 day s... ., or when selected one sensor Live Dat a... and View Hist oric Dat a... . You can also create a report. For detailed instructions, please see Hist oric Dat a Report s 127 (Menu). When selected one or more sensors (hold the Ctrl or Shift key to select multiple items), it is possible to call the Compare Sensors 123 function. The graphs of all chosen sensors will be added to comparison automatically. You can add additional sensors in the appearing comparison dialog. Drag & Drop Sort ing In order to use the option to sort all objects in the device tree via drag and drop, please enable this option. By default, this option is disabled to avoid accidental moves of objects. In this case, a dialog box appears when you try to drag an object. You can disable the dialog box message by clicking the respective check box which is shown together with the message. For details, please see section Devices 1758 .
1788
21.10.2013
Device Tools Call a tool command. All placeholders (variables) configured in a tool command will be resolved for the currently selected object. Hover to see all available tools configured in your Opt ions 1782 settings (Tools). By default, a Remot e Deskt op tool is pre-configured which tries to initiate a remote desktop connection to the IP address or DNS name of the selected object (this will usually work for devices, of course). For devices, additional options are available. They allow you to connect to the Service URL value defined in the device's settings 1757 , or open the IP address/DNS name of the device via the protocols HTTP, HTTPS, and FTP. For each of these functions, your system's default programs will be used. Usually, this is your browser. You can also install a remote probe on a device via Remot e Probe Quick Set up 1891 . Note: In order for the tool function to work with your Windows version, you may need to run the Enterprise Console as administrator. Send link by email You can send the link to the selected probe by email. This will open a new email using your system's standard email client. It will contain a direct link to the selected probe's details page. Open in Web Browser This will open the currently selected object in the Ajax web interface. This option is not available if multiple objects are selected. The default browser can be set in the Opt ions settings. Note: This option is available in the Cont ext Menus 1791 and under View 1789 .
1784
View
Refresh This will immediately query data for the current screen from the PRTG core server, just as the automatic refresh does, which can be configured in the Opt ions 1779 settings. Open Web GUI... This will open the start page of the Ajax web interface in the external browser. The default browser can be set in the Opt ions 1784 settings. Large Single Graph Change the view in Devices 1752 menu tab to large single graphs. This will display live graphs, and graphs for three other time spans, in different tabs. Small Mult iple Graphs Change the view in Devices 1752 menu tab to multiple small graphs. This will display live graphs, and graphs for three other time spans. This will display all graphs in one tab. Show Geo Maps Choose if you want to show geographical maps in the Enterprise Console. Show News Feed Choose if you want to show the news feed in the Enterprise Console. Next Viewpoint Go forward to the next viewpoint (only available if you went back to a previous viewpoint before). This is similar to a browser's function to go forth in history. Previous Viewpoint Go backwards to the previous viewpoint. This is similar to a browser's function to go back in history.
21.10.2013
1789
Open in Web Browser This will open the currently selected object in the Ajax web interface. This option is not available if multiple objects are selected. The default browser can be set in the Opt ions settings.
1784
Help
This menu provides web site links to the HTML manual, the Paessler Knowledge Base, and the PRTG Net work Monit or homepage. You can start the Configurat ion Guru 32 and display program information when you select About ... .
See Also
Short cut s Overview
1792
1790
21.10.2013
Part 8: Enterprise Console | 7 Context Menus
8.7
Context Menus
For every object in the Enterprise Console, there are context menus available which appear when you right-click on object. These context menus vary depending on the selected object and always contain a sub-set of the options available in the Windows menu. For detailed explanations, please see Windows Menu St ruct ure 1786 .
Context Menu in the Enterprise Console
19.07.2013
1791
Part 8: Enterprise Console | 8 Shortcuts Overview
8.8
Shortcuts Overview
The following shortcut keys are available in the Enterprise Console: Alt +X : File | Close or Exit With the Show in Tray option enabled in the Opt ions otherwise Exit .
1779
settings, this will be Close;
Ct rl+Alt +X : File | Close and Exit This menu item is only shown if the Show in Tray option is enabled in the Opt ions settings. Alt +Right : Next Viewpoint Alt +Left : Ct rl+C: Edit | Check Now Ct rl+E: Edit | Pause | Set Sensor to Error Ct rl+P: Edit | Pause | Indefinitely Ct rl+R: Edit | Pause | Resume Ct rl+L: View | Large Single Graph Ct rl+S : View | Small Multi Graphs Ct rl+H: View | Hide Google Map Ct rl+Del: Edit | Acknowledge all ToDos (available only while in ToDos tab) F5: View | Refresh F6: [Context Menu] | Tools | Custom tool command, if available F7: [Context Menu] | Tools | Custom tool command, if available F8: [Context Menu] | Tools | Custom tool command, if available F9: [Context Menu] | Tools | Custom tool command (default: Remot e Deskt op) F10: [Context Menu] | Tools | Custom tool command, if available F11: [Context Menu] | Tools | Custom tool command, if available F12: [Context Menu] | Tools | Custom tool command, if available
1779
1792
27.11.2012
Part 8: Enterprise Console | 8 Shortcuts Overview
See Also
Windows Menu St ruct ure
1786
27.11.2012
1793
Part 9
Other User Interfaces
19.07.2013
1795
Part 9: Other User Interfaces |
Other User Interfaces

This chapter introduces other available user interfaces besides PRTG's Ajax web interface and Enterprise Console. There are special interfaces optimized for mobile access, including apps for mobile devices. Read more in the following sections.
PRTG's Different User Interfac es
Other User InterfacesTopics

Mobile Web GUI
1797
Smart phone Apps
1801
Related Topics
94
180
Ajax Web Int erfaceDevice and Sensor Set up Ajax Web Int erfaceAdvanced Procedures Ent erprise Console
1744 1584
1796
19.07.2013
Part 9: Other User Interfaces | 1 Mobile Web GUI
9.1
Mobile Web GUI

The Mobile Web GUI is slim interface to view your monitoring results while on the go. It is optimized for both small screens and low bandwidth usage in order to provide an easy and fast access to your PRTG core server when connecting with mobile devices. You can view sensor lists, data tables, and graphs with live data.
Mobile Web GUI on Different Mobile Dev ic es
Compared to the Ajax Web GUI 94 , this interface comes with limited functionality and is primarily provided for quick review of data while on the go. Nevertheless, you can acknowledge alarms, pause or resume monitoring, and interactively view geo maps as well as sensors and other lists. This interface is based on jQuery Mobile 1.0, supporting all major mobile operating systems and browsers.
Loading the Web Interface

Make sure your PRTG core installation is accessible via the internet. In your mobile device, enter the IP address or URL of the system PRTG is installed on. When using a cluster, you can connect to any node accessible. If you see a certificate warning in your browser, you can usually just confirm it. For more information please see SSL Cert ificat e Warning 99 .
Login Screen
After loading the web interface, the login screen is shown.
19.07.2013
1797
Mobile Web GUI Login
Enter your credentials, choose the Mobile Web GUI (Limit ed funct ionalit y , opt imized for mobile access) option, and click on Login. For detailed information about different credentials, please see the Login 96 section for the Ajax Web GUI.
General Layout
The home screen of the Mobile Web GUI shows the sensor overview as well as all available main menu entries. Click/tab on menu items to get to groups, devices, and sensor data. You will be guided through a sequence of sub and sub-sub screens. Whenever you get lost, click/ tab on the house symbol in the upper left corner to get back to the home screen.
1798
19.07.2013
Mobile Web GUI Home Sc reen
There are also different sensor top lists available underneath the Sensors menu entry. Note: Most of the functionality is read-only, because this interface is intended for viewing data. In order to change your monitoring configuration or settings, please switch to the Ajax Web Int erface 94 . If you would like to have more options on your mobile devices, take a look at our Smart phone Apps 1801 .
Using the Mobile Web GUI

The device tree and lists of sensors, alarms, logs, and ToDos are available as usual, but in a view optimized for mobile screens. In addition, monitoring data for all objects can be viewed. This section will not explain the GUI in detail, because the concepts are the same as throughout the Ajax web interface 94 . In the following, find a list with the main differences compared to the full Ajax interface: There are no context menus available, but actions such as acknowledge an alarm, scan now, pause, etc. can be initiated directly on an objects detail page, using the respective buttons.
19.07.2013
1799
Reports and Maps are accessible in view only mode. You cannot edit system settings. To save bandwidth, an automatic page refresh is only activated after dedicated confirmation. You can switch from the Mobile Web GUI to the Ajax web interface at any time by using the Swit ch t o AJAX GUI option. You will just need a few minutes to get familiar with this interface, because the structure is basically the same as you know it from PRTG's Ajax web interface. Have fun monitoring while on the go!
1800
19.07.2013
Part 9: Other User Interfaces | 2 Smartphone Apps
9.2
Smartphone Apps
There are PRTG apps for iOS and for Android devices. You can connect to your PRTG installation with these apps while on the go. Use them as an alternative to the Mobile Web GUI 1797 interface.
iPRTG for iOS

iPRTG is the iApp for PRTG Network Monitor. Use it on the iPhone, iPad, and iPod touch.
Maps on iPad
Don't let monitoring your network tie you to your desk! With iPRTG your network monitor is where your iPhone is. iPRTG is the iOS App for network administrators using the PRTG Network Monitor software to monitor and administrate their network. iPRTG is a clear and simple viewer for the entire network monitoring environment. Your iOS device requests the monitoring data directly from your PRTG server and displays it in an 'iPhonic' way.
09.10.2013
1801
iPRTG on iPhone
In order to use iPRTG, your core server must be reachable from the internet. You can view monitoring data and perform certain actions, such as acknowledge alarms, pause or resume monitoring, etc. Note: The app currently does not support PRTG cluster 76 setups! In order to get the app, please see More
1805
section below.
PRTG for Android

PRTG for Android is the Android app for PRTG Network Monitor. Use it on your phone, your tablet, or on a Kindle Fire.
1802
09.10.2013
PRTG for Android Main Menu Bar
The features include: Multiple accounts support to query different server/login combinations. Switch easily between different accounts to quickly view monitoring data of several installations and/or accounts. The app can check all accounts, or only specific ones, automatically in the configured polling interval and notify you in your device's status bar whenever there are alarms for one of them. Configure when you want to be notified: when Alarms > 0, or when there is a certain number of new alarms, or when alarms count raised since last check. Configure notifications via the system status bar with ringtone and/or vibration (triggered for new notifications). You can exclude "Warning" or "Unusual" states from alarms count, and set up notifications based on priority. PRTG for Android works with your PRTG core server to show you your device tree, sensor lists, sensor data, etc., in an Android familiar way. You can add sensor gauges as well as the global sensor status as widgets to your home screen. The data display automatically adapts to your screen size, so you can see as much information as possible at a glance. Many features of PRTG's web interface are available to perform actions with the app: acknowledging alarms, pausing and resuming monitoring, setting priorities and favorites, running device auto-discovery, scanning the network status instantly, etc. With QR code scanning, you can jump directly to sensor. The app provides additional network tools such as ping, traceroute, DNS, raw HTTP, and MAC address lookups. You can use these tools also without connecting to a PRTG server.
09.10.2013
1803
Notific ation Settings
In order to use PRTG for Android (except for the additional network tools), your core server must be reachable from the internet.
PRTG for Android Sensors Ov erv iew
For further information and the download link, please see section More
1805
below.
1804
09.10.2013
Home Sc reen Widgets
More
More information and a video about iPRTG http://www.paessler.com/iprtg More information about PRTG for Android http://www.paessler.com/androidapp
09.10.2013
1805
Part 10
Sensor Technologies
27.11.2012
1807
Part 10: Sensor Technologies |
10
Sensor Technologies
This chapter introduces different technologies that PRTG uses for monitoring, in order to give you a little more background information. Please read more in the following sections.
Sensor TechnologiesTopics
Monit oring via SNMP Monit oring via WMI Monit oring via SSH
1809
1813
1816
Monit oring Bandwidt h via Packet Sniffing Monit oring Bandwidt h via Flows
1820
1818
Bandwidt h Monit oring Comparison Monit oring Qualit y of Service Monit oring Email Round Trip Monit oring Backups
1831 1825
1823
1829
Monit oring Virt ual Environment s Monit oring Dat abases

1833
1832
1808
27.11.2012
Part 10: Sensor Technologies | 1 Monitoring via SNMP
10.1
Monitoring via SNMP

Monitoring via Simple Network Management Protocol (SNMP) is the most basic method of gathering bandwidth and network usage data.
How SNMP Monitoring Works

SNMP can be used to monitor bandwidth usage of routers and switches on a port-by-port basis, as well as device readings such as memory, CPU load, etc. The queried devices must support SNMP.
Network Monitoring v ia SNMP
When this technology is used, PRTG sends small data packets to devices, for example, querying routers, switches, and servers for the traffic counters of each port. These are triggering reply packets from the device. Compared to PRTG's other bandwidth monitoring techologies via flows, packet sniffing, or WMI, the SNMP option creates the least CPU and network load.
Reasons to Choose SNMP Monitoring

SNMP is the most commonly used method mainly because it is easy to set up and requires minimal bandwidth and CPU cycles. If your network devices support SNMP and/or if you want to monitor large networks with several hundred or thousands of sensors, we recommend you start with SNMP. Besides network usage monitoring, another well-known feature of SNMP is the ability to also watch other network parameters such as CPU load, disk usage, temperature, as well monitoring many other readings, depending on the queried device.
SNMP Network Issues

In order to use Simple Network Management Protocol (SNMP) for monitoring purposes, it is imperative that UDP packets are allowed to travel from the machine running PRTG to the device you want to monitor and back, which is usually the case in LANs and Intranets. For connections across the internet, to a Demilitarized Zone (DMZ), or for Wide Area Network (WAN) connections, some changes to the traversed firewalls may be necessary. Keep in mind that SNMP V1 and V2c are not secure protocols and should not be used across the internet or insecure data connections. Only SNMP version 3 supports encryption.
08.10.2013
1809
Understanding SNMP Sensors

To better understand and set up SNMP sensors, you may want to learn more about the principle of Object Identifiers (OID) and Management Information Base (MIB). For more information about this, please refer to the Knowledge Base article in the More 1812 section below. For an overview and details about all SNMP sensors, please see the List of Available Sensor Ty pes 281 section.
SNMP Versions
PRTG supports three versions of the SNMP protocol: Version 1, version 2c, and version 3. SNMP Version 1 This is the oldest and most basic version of SNMP. Pro: Supported by most SNMP-compatible devices; simple to set up. Contra: Limited security as it only uses a simple password (community string) and data is sent in clear text (unencrypted). It should therefore only be used inside LANs behind firewalls, not in WANs; only supports 32-bit counters which is not enough for high-load (gigabits/second) bandwidth monitoring. SNMP Version 2c This version adds 64-bit counters. Pro: Supports 64-bit counters to monitor bandwidth usage in networks with gigabits/second loads. Contra: Limited security (same as with SNMP V1). SNMP Version 3 This version adds authentication and encryption to SNMP. Pro: Offers user accounts and authentication for multiple users and optional data packet encryption, increasing available security; plus all advantages of Version 2c. Contra: Difficult to configure. Not suitable for large networks (see below for more information).
1810
08.10.2013
It is important to know that if you select an SNMP version which is not supported by the server or device you want to monitor, you will receive an error message. Unfortunately, in most cases, these error messages do not explicitly mention the possibility that you could be using the incorrect SNMP version. These messages provide minimum information only, such as cannot connect or similar. Similar error occur when community strings, usernames, or passwords don't match.
SNMP Overload and Limitations of the SNMP System

SNMP V1 and V2 scale directly with the performance of the hardware and the speed of the network. In our labs we were able to monitor 30,000 SNMP V1 sensors at a 60 second interval with one PRTG server (core and local probe) plus two remote probes with 10,000 sensors each. However, SNMP V3 has performance limitations due to the SSL encryption. The main limiting factor is CPU power (as well as the other general limits for PRTG). Because of this limitation, you can monitor only a limited number of sensors per second using SNMP V3. Currently, PRTG is able to handle roughly 40 requests per second and computer core, depending on your system. This means that, on a common 1.x GHz computer with two cores, you can run about 5,000 SNMP v3 sensors with a 60 seconds scanning interval; on a system with four cores, you can monitor around 10,000 sensors with 60 seconds interval. The CPU load is at about 50% then. We do not recommend more. Furthermore, the PRTG core server and probes should run on different computers. If you experience increased values in the Interval Delay SNMP or Open Requests channels of the Probe Healt h 767 sensor (values above 0 % indicate that the SNMP requests cannot be performed at the desired interval), you need to distribute the load over multiple probes. SNMP V1 and V2 do not have this limitation. If you run into SNMP overload problems you have three options: Increase the monitoring interval of the SNMP V3 sensors. Distribute the SNMP V3 sensors over two or more probes. Switch to SNMP V1 or V2 if you can go without encryption.
What is the SNMP Community String?

The SNMP Community String is similar to a user ID or password that allows access to a router's or other device's statistics. PRTG Network Monitor sends the community string along with all SNMP requests. If the correct community string is provided, the device responds with the requested information. If the community string is incorrect, the device simply discards the request and does not respond. Note: SNMP community strings are only used by devices that support SNMP V1 and SNMP V2c protocols. SNMP V3 uses safer username/password authentication, along with an encryption key.
08.10.2013
1811
By convention, most SNMP V1/V2c equipment ships with a read-only community string set to the value public . It is standard practice for network managers to change all the community strings to customized values during device setup.
More
Tools: Paessler MIB Importer and SNMP Tester http://www.paessler.com/tools/ Knowledge Base: How do SNMP, MIBs and OIDs work? http://www.paessler.com/knowledgebase/en/topic/653 Paessler White Papers: Introducing SNMP and Putting SNMP into Practice http://www.paessler.com/press/whitepapers/introducing_snmp German: Paessler White Paper: Einfhrung in SNMP und SNMP praktisch anwenden http://www.de.paessler.com/press/whitepapers/introducing_snmp Knowledge Base: My SNMP sensors don't work. What can I do? http://www.paessler.com/knowledgebase/en/topic/46863
1812
08.10.2013
Part 10: Sensor Technologies | 2 Monitoring via WMI
10.2
Monitoring via WMI

Windows Management Instrumentation (WMI) is Microsoft's base technology for monitoring and managing Windows based systems. PRTG uses this technology to access data of various Windows configuration parameters and status values. However, sensors using the WMI protocol generally have a high impact on the system performance. In addition to strict WMI sensors, there are sensors which use another approach to monitor Windows systems with less influence on the system performance.
Monitoring Windows Systems: Performance Counters

Besides sensors which monitor Windows systems only via WMI, PRTG provides sensor types which use a hybrid approach. These sensors first try to query data via Windows Performance Counters using Remote Registry Service. Querying Performance Counters needs less system resources than monitoring via WMI. These Windows sensors use WMI as a fallback if Performance Counters are not available or cannot be read out. When running in fallback mode, PRTG re-tries to connect to Performance Counters after 24 hours. This is the default approach and can be changed in the Windows Compat ibilit y Opt ions in the Device Set t ings 261 . Though, it can be the case sometimes that these Performance Counters differ from the direct method. Note: You can identify these hybrid sensors by looking at their categories, for example, in the add sensor dialog. Search direct ly for "windows" and select "Performance Counters" as Technology Used. Among them are various sensors with "Windows" in the name, as well as some Hyper-V sensors.
How WMI Works

WMI allows accessing data of many Windows configuration parameters, as well as current system status values. Access can be local or remote via a network connection. WMI is based on COM and DCOM and is integrated in Windows 2000, XP, 2003, Vista, 2008, Windows 7, and Windows 8 (add-ons are available for Windows 9x and NT4). PRTG officially supports WMI for Windows XP or later. In order to monitor remote machines, PRTG's WMI sensor needs Active Directory account credentials to have access to the WMI interface. You can enter these credentials in PRTG for the parent device or group, or in the Root 213 group. The sensor will then inherit these settings. Note: Sensors using the Windows Management Instrumentation (WMI) protocol generally have high impact on the system performance! Try to stay below 200 WMI sensors per probe 73 . Above this number, please consider using multiple Remot e Probes 1888 for load balancing. For an overview and details about all WMI sensors, please see the List of Available Sensor Ty pes 282 section.
19.07.2013
1813
Limitations of WMI on Windows Vista and Windows Server 2008 R1

You should be aware that performance of WMI based monitoring is drastically limited when the monitoring station or the monitored client runs on Windows Vista or Windows Server 2008 R1. When it comes to network monitoring via WMI, Windows XP and Windows 2003 are up to 70 times faster than Windows 2008 or Vista. Note: These are not limitations of PRTG, but arise from the WMI functionality built into the Windows operating systems mentioned. The results of our tests are: On Windows XP/Windows 2003/Windows 7/Windows 2008 R2 you can run about 10,000 WMI sensors with one minute interval under optimal conditions (such as running the core and the target systems exclusively under Windows 2003 and being located within the same LAN segment). Actual performance can be significantly less depending on network topology and WMI health of the target systems - we have seen configurations that could not go beyond 500 sensors (and even less). On Windows Vista/Windows 2008 R1 you can run about 300 WMI sensors with one minute interval. The more Windows Vista/Windows 2008/Windows 7 client systems you have in your network the more WMI monitoring performance will be affected. System performance (CPU, memory etc.) of virtualization does not strongly affect WMI monitoring performance. If you want to use WMI for network monitoring of more than 20 or 30 systems, please consider the following rules: Do not use Windows Vista or Windows 2008 R1 as monitoring stations for WMI-based network monitoring. If possible use Windows 2003 R2 Server for WMI based network monitoring (followed by XP and Windows 7/2008 R2). If you cannot run PRTG on Windows XP/Windows 2003 consider setting up a remote probe with XP for the WMI monitoring. (You still get far better WMI monitoring performance with a remote probe on a virtual machine running Windows XP or Windows 2003 than on any bare metal system running Windows Vista/Windows 2008 R1.) Consider switching to SNMP-based monitoring for large networks. Using SNMP you can easily monitor 10 times as many nodes as with WMI (on the same hardware).
More
Knowledge Base: General introduction to WMI and PRTG http://www.paessler.com/knowledgebase/en/topic/1043
1814
19.07.2013
Tool: Paessler WMI Tester. A useful freeware tool to test WMI connections. Tests the accessibility of WMI (Windows Management Instrumentation) counters in a quick and easy manner. http://www.paessler.com/tools/wmitester
CEO's Blog: Don't Use Windows Vista And Windows 2008 R1 for Network Monitoring via WMI! http://www.paessler.com/blog/2010/09/22/
19.07.2013
1815
Part 10: Sensor Technologies | 3 Monitoring via SSH
10.3
Monitoring via SSH

Monitoring via Secure Shell (SSH) enables you to gather performance and system data from many Linux and Unix distributions, as well as from certain Mac OS X systems. If your system is supported this monitoring works natively without the need of additional software on the target systems.
How Monitoring via SSH Works

In order to monitor remote machines via SSH, PRTG needs credentials (preferably root access) of the devices. If you use PRTG's SSH sensors, you can enter the necessary credentials in PRTG for the parent device or group, or in the Root 213 group, in the Credentials for Linux (SSH/ WBEM) Systems section within the Set t ings 133 tab. The sensors will then inherit these settings. With each scanning interval, PRTG will login to your devices and query data by executing specific commands. For an overview and details about all SSH sensors, please see the List of Available Sensor Ty pes 284 section.
Limitations When Using SSH Monitoring

Due to the plurality of Linux/Unix derivatives, PRTG's SSH sensors cannot support all distributions on the market. Also, only certain Mac OS systems are supported. For a detailed list please see the More 1817 section below.
Authentication via SSH Private Key

PRTG supports authentication via password or via private key. When using a private key, please ensure the following: Provide the key in OpenSSH RSA format. The key may not be encrypted! PRTG does not support password protected keys. The key must be provided as RSA key, you cannot use DSA keys with PRTG! When providing an unencrypted RSA private key in OpenSSH RSA format, please copy the entire key, including the
-----BEGIN RSA PRIVATE KEY-----
and
-----END RSA PRIVATE KEY-----
lines, into the according text field in PRTG and Save your settings. Once pasted and saved, the private key will be shown as
1816
27.11.2012
Part 10: Sensor Technologies | 3 Monitoring via SSH
***************************
Please make sure there exists a corresponding public key on the target device. For a detailed description how to convert and use an existing SSH key, please see the More 1817 section below.
More
Knowledge Base: Which Linux or Mac OS distributions are supported by the Linux/Unix sensors (SSH, SNMP, WBEM)? http://www.paessler.com/knowledgebase/en/topic/6733 Knowledge Base: How can I use private keys for my SSH sensors with PRTG? http://www.paessler.com/knowledgebase/en/topic/32883 Knowledge Base: How do I enable SSH on my Mac OS X system? http://www.paessler.com/knowledgebase/en/topic/33113
27.11.2012
1817
Part 10: Sensor Technologies | 4 Monitoring Bandwidth via Packet Sniffing
10.4
Monitoring Bandwidth via Packet Sniffing

Packet Sniffing should come into consideration if your network device(s) do not support SNMP or xFlow to measure bandwidth usage and if you need to differentiate the bandwidth usage by network protocol and/or IP addresses. Note: Packet Sniffer Sensors support Toplists (Top Talkers, Top Connections, etc.), see Toplist s 1586 section.
How Packet Sniffing works

If you need to know what applications or IP addresses are causing the traffic in your network, you can use a packet sniffer. This will look at every single data packet traveling through your network for accounting purposes.
Monitoring with PRTG v ia Pac ket Sniffer Sensors
PRTG can analyze the packets passing the network card of a PC or it can be connected to the so-called monitoring port of a switch. In order to calculate bandwidth usage, PRTG inspects all network data packets either passing the PC's network card (shown on the left side) or the data packets sent by a monitoring port of a switch (right side) with its built-in packet sniffer. Using remote probes you can set up packet sniffers anywhere in your network (see Add Remot e Probe 1887 section). Comparing the four bandwidth monitoring technologies provided by PRTG (SNMP, WMI, xFlow and packet sniffer) this one creates the most CPU and network load and should thus only be used in small to medium networks, on dedicated computers for larger networks or for individual computers.
Reasons To Choose Packet Sniffing

It is important to understand that the packet sniffer can only access and inspect data packets that actually flow through the network interface(s) of the machine running the PRTG probe software. This is fine if you only want to monitor the traffic of this machine (e.g. your web server). In switched networks, only the traffic for a specific machine is sent to each machine's network card, so PRTG can usually not discern the traffic of the other machines in the network.
1818
27.11.2012
Part 10: Sensor Technologies | 4 Monitoring Bandwidth via Packet Sniffing
If you also want to monitor the traffic of other devices in your network, you must use a switch that offers a "monitoring port" or "port mirroring" configuration (Cisco calls it "SPAN"). In this case the switch sends a copy to the monitoring port of all data packets traveling through the switch. As soon as you connect one of the PRTG probe system's network cards to the switch's monitoring port, PRTG is able to analyze the complete traffic that passes through the switch. Another option is to set up the PC running PRTG as the gateway for all other computers in the network.
Set Up Packet Sniffer Sensors

Find details on how to set up the different flow sensors in the following sections: Packet Sniffer Sensor
692
Packet Sniffer (Cust om) Sensor
699
Header Based Packet Sniffing

For packet sniffing, PRTG looks at the IPs and ports of source and destination to assess the protocol. This is a very fast method which saves system resources. Note: At times, this method is not fully accurate. For example it is not possible to identify HTTP traffic on ports other than 80, 8080 and 443 as HTTP. HTTP traffic on non-standard ports would not be accounted as such.
More
Tool: Paessler Card Packet Counter: Shows short term statistics about the network data packets passing a local network card. http://www.paessler.com/tools/
27.11.2012
1819
Part 10: Sensor Technologies | 5 Monitoring Bandwidth via Flows
10.5
Monitoring Bandwidth via Flows

Using Flow protocols you can monitor the bandwidth usage of all packets going through a device. In PRTG, you can view Toplist s 1586 for all xFlow (including IPFIX) sensors.
How xFlow Monitoring works

You can measure bandwidth usage by IP address or by application in a network, using one of the xFlow (including IPFIX) protocols. They are the best choice especially for networks with high traffic (connections with 100s of megabit or gigabits). For xFlow monitoring the router gathers bandwidth usage data (flows), aggregates them and sends information about these flows to PRTG using UDP packets. When sampling is used (mandatory for sFlow) only information about every n-th packet is sent to PRTG which reduces CPU load a lot. Because the switch already performs a pre-aggregation of traffic data, the flow of data to PRTG is much smaller than the monitored traffic. This makes xFlow the ideal option for high traffic networks that need to differentiate the bandwidth usage by network protocol and/or IP addresses.
NetFlow and IPFIX Monitoring

The NetFlow (and IPFIX) protocol is mainly used by Cisco devices. Once configured, the router sends for each data flow a NetFlow or IPFIX packet to the monitoring system running on a PRTG probe. There the data can be filtered and evaluated. There are different NetFlow and IPFIX sensors available: The basic ones offer predefined channel definitions, the custom variants enable you to define your own channels. The advantage of using NetFlow or IPFIX: Generates little CPU load on the router itself (according to Cisco 10,000 active flows create about 7% additional CPU load; 45,000 active flows account for about 20% additional CPU load). Generates less CPU load on the PRTG core system, compared to packet sniffer sensors. Note: You must enable NetFlow or IPFIX export on the device you want to monitor. The device must send a flow data stream to the IP address of the PRTG probe system on which the NetFlow or IPFIX sensor is set up. Juniper jFlow monitoring is reported to work as well, using NetFlow v5 sensors.
sFlow Monitoring
sFlow works similar to NetFlow monitoring. The router sends data flow packets to the monitoring system running on a PRTG probe. The most obvious difference between the two flow protocols: With sFlow, not all of the traffic is analysed, but only every n-th packet. It is like having a river of traffic and you take a cup of water out of it ever so often and analyze it. The advantage is clear: There is less data to analyze, there is less CPU load needed and less monitoring traffic is generated. Yet you can get a good insight into your network's bandwidth usage. Note: Currently, PRTG supports sFlow version 5.
1820
08.10.2013
Set Up Flow Sensors

Find details on how to set up the different flow sensors in the following sections: Net Flow V5 Sensor
652
Net Flow V5 (Cust om) Sensor Net Flow V9 Sensor

668
660
Net Flow V9 (Cust om) Sensor IPFIX Sensor

600
676
IPFIX (Cust om) Sensor sFlow Sensor

822
608
sFlow (Cust om) Sensor jFlow V5 Sensor

616
830
jFlow V5 (Cust om) Sensor
624
Limitations
On a powerful 2008 PC (Dual Core, 2.5 Ghz), you can process about 100,000 flows per second for one xFlow stream. Using sampling the number of actual flows can be much higher. When using complex filters, the value can be much lower. For example, with a router sending about 2,000 flows/second (which corresponds to mixed traffic at gigabit/sec level without sampling) you can expect to configure up to 50 NetFlow sensors operating properly. PRTG internally monitors its own NetFlow processing, and you will see a decreased values in the Core/Probe Healt h sensor's Health channel as soon as NetFlow packets are not processed due to an overload (you find this sensor on the Local Probe device). If you experience an overload please consider using sampling or setting up multiple probes and distribute the NetFlow streams to them. We do not recommend adding more than 400 NetFlow sensors per PRTG probe. This sensor type cannot be used in cluster mode. You can set it up on a local probe or remote probe only, not on a cluster probe.
More
Knowledge Base: Can I add custom channels to standard Packet Sniffer and NetFlow sensors? http://www.paessler.com/knowledgebase/en/topic/2143
Knowledge Base: What filter rules can be used for custom Packet Sniffing or xFlow (NetFlow/ sFlow) sensors? http://www.paessler.com/knowledgebase/en/topic/483
08.10.2013
1821
Knowledge Base: How do the channel definitions for custom Packet Sniffing or xFlow (NetFlow/sFlow) sensors work? http://www.paessler.com/knowledgebase/en/topic/473
Knowledge Base: Does my Cisco device (Router/Switch) support NetFlow Export? http://www.paessler.com/knowledgebase/en/topic/5333
Knowledge Base: Do you have any configuration tips for Cisco routers and PRTG? http://www.paessler.com/knowledgebase/en/topic/563
Knowledge Base: Is it possible to monitor Cisco ASA Firewalls using Netflow 9 and PRTG? http://www.paessler.com/knowledgebase/en/topic/633
Knowledge Base: How to monitor Cisco ASA Firewalls using NetFlow 9 and PRTG? http://www.paessler.com/knowledgebase/en/topic/1423
Tools: NetFlow Generator and NetFlow Tester http://www.paessler.com/tools/
1822
08.10.2013
Part 10: Sensor Technologies | 6 Bandwidth Monitoring Comparison
10.6
Bandwidth Monitoring Comparison

The following table shows the differences between PRTG's four methods available for bandwidth monitoring:
WMI
SNMP
Packet Sniffer
xFlow (Netflow, sFlow, jFlow) Can be complex (e.g. the switch must be configured) Yes
Setup
Medium
Easy
Easy to Complex (depending on filter rules used) Yes
Traffic can be No filtered Differentiate bandwidth usage by protocol or IPs PRTG can show Toplists (Top Talker, Top Connections , Top Protocols etc.) Filter bandwidth usage by IP No
No
No
Yes
Yes
No
No
Yes
Yes
No
No
Yes
Yes
Filter No bandwidth usage by MAC address Filter bandwidth usage by physical network port Yes
No
Yes
No
Yes
No
No
27.11.2012
1823
Part 10: Sensor Technologies | 6 Bandwidth Monitoring Comparison
WMI
SNMP
Packet Sniffer
xFlow (Netflow, sFlow, jFlow) No
Monitor network parameters other than bandwidth usage CPU load on the machine running PRTG Excess bandwidth usage of monitoring
Yes
Yes
No
Low
Low
Higher, depends Higher, depends on on the amount of the amount of traffic traffic
Small
Small
None (except when monitoring switch ports are used)
Depends on the traffic
More
Knowledge Base: Should I use SNMP, xFlow (NetFlow/sFlow) or Packet Sniffing for my monitoring? http://www.paessler.com/knowledgebase/en/topic/923
Knowledge Base: How do I discern excessive bandwidth usage with PRTG? http://www.paessler.com/knowledgebase/en/topic/2923
1824
27.11.2012
Part 10: Sensor Technologies | 7 Monitoring Quality of Service and VoIP
10.7
Monitoring Quality of Service and VoIP

PRTG can monitor the Quality of Service in a network with its own QoS sensor as well as Cisco IP Service Level Agreement (SLA). Slight variations of network parameters like jitter, packet loss, or packet delay variation (PDV) usually have only little effect on TCP based services (e.g. HTTP, SMTP, etc.). But for UDP based services like Voice over IP (VoIP) and video streaming a steady stream of data packets is crucial. The sound quality of a VoIP call drops dramatically when UDP packets are not received in a timely fashion, or if packets are lost or out-of-order. As a rule of thumb for good quality of service (in a VoIP perspective) you would want low measurements for jitter (less than 20 to 50 ms) and PDV (less than 100 ms) and preferably zero measurements for packet loss, duplicated packets, or packets in wrong order. For Quality of Service measurements, three sensors are available: QoS (Qualit y of Service) Sensor 771 Monitors VoIP relevant network parameters by testing network connection quality between two probes. QoS (Qualit y of Service) Round Trip Sensor 777 Monitors VoIP relevant network parameters by testing network connection quality between two probes. Traffic is measured bidirectional. Cisco IP SLA Sensor 322 Monitors VoIP relevant network parameters through IP SLA results from Cisco devices (via SNMP).
QoS (Quality of Service) Sensor

The QoS Sensor is used to monitor the quality of a network connection by measuring the following parameters: Jitter in ms according to RFC 3550 Packet delay variation (PDV) in ms according to RFC 3393 Lost packets in % Out-of-order packets in % Duplicated packets in % The measurements are taken by sending UDP packets between two probes. This means that you can test any network connection in your network by simply placing a remote probe 1887 on (or near) each 'end' of the connection and measuring the connection quality between them. This is the perfect tool to find network issues that can affect VoIP sound quality or video streaming 'hiccups'.
19.07.2013
1825
Monitoring Quality of Serv ic e with PRTG
As mentioned before, measurements are taken between two probes. So the first step is to place two PCs running a remote probe on (or near) both ends of the connection that you want to monitor. As an alternative, the local probe on the PC running the PRTG core can also be used as one end. If any firewalls, packet filters or Network Address Translation (NAT) systems are en route, you must configure them as necessary so that the UDP packets can reach the target probe. In PRTG, create a new QoS sensor on a Probe Device. Please find details about settings in the QoS (Qualit y of Service) Sensor 771 section. With the settings for number and for size of the packets you can configure the test data stream. 1,000 packets of 172 bytes each is a good start, but if your applications use larger packets you may want to enter other values here. Try to configure the test streams with parameters similar to that of the UDP services you are using across this connection.
Cisco IP SLA Sensor

Wikipedia describes IP SLA as a feature included in the Cisco IOS Software that can allow administrators the ability to Analyze IP Service Levels for IP applications and services. IP SLA uses active traffic-monitoring technology to monitor continuous traffic on the network. This is a reliable method in measuring over head network performance. IP-SLA is mostly used to monitor the sound quality of VoIP traffic. If you haven't done so already, please add a device in PRTG for the Cisco device that you want to monitor. Then create a new Cisco IP SLA sensor on this device. Please find details about settings in the Cisco IP SLA Sensor 322 section.
1826
19.07.2013
This feature is only available in the more expensive Cisco devices. If you don't have IP SLA capable routers/switches you can still get similar information with PRTG's QoS sensor (see above 1825 ) which does not require any special hardwarejust two PCs running Windows. If you do own hardware which supports IP SLA then PRTG brings you probably the least-cost monitoring solution for IP SLA. Most vendors charge extra for IP SLA support (a thousand bucks and more). Following Paessler's long term policy we simply include this as one of our sensor types. With PRTG you can even use the Freeware Edition to monitor IP SLA! PRTG monitors the following parameters: Calculated Planning Impairment Factor (ICPIF), Mean Opinion Score (MOS), Average Jitter, Packets Lost, Packets Out Of Sequence, Packets Late, Average Round Trip Time (RTT), DNS RTT, TCP RTT, Transaction RTT. Especially two of these parameters are interesting for VoIP: Mean Opinion Score (MOS) and Calculated Planning Impairment Factor (ICPIF).
Voice over IP
For Mean Opinion Score (MOS) measurements, Cisco conducted a panel test where a wide range of listeners judged the quality of voice samples sent using particular codecs, on a scale of 1 (poor quality) to 5 (excellent quality). The Cisco device calculated the corresponding value for the current network connection based on the network parameter measurements like jitter and packet loss. The values and their meanings are:
MOS
Qualit y
Expect ed Qualit y Impairment Imperceptible Perceptible, but not annoying Slightly annoying Annoying Very annoying
5 4 3 2 1
Excellent Good Fair Poor Bad
The second interesting parameter ICPIF is the sum of measured impairment factors minus a user-defined access Advantage Factor that is intended to represent the user's expectations, based on how the call was placed (for example, a mobile call versus a land-line call) (quoted from Cisco's website).
19.07.2013
1827
Upper Limit for ICPIF 5 10 20 30 45 55
VoIP Call Communicat ion Qualit y Very good Good Adequate Limiting case Exceptional limiting case Customers likely to react strongly (complaints, change of network operator)
More
Paessler Knowledge Base: Where can I find more information about Cisco IP SLAs, VoIP, and QoS? http://www.paessler.com/knowledgebase/en/topic/11093
1828
19.07.2013
Part 10: Sensor Technologies | 8 Monitoring Email Round Trip
10.8
Monitoring Email Round Trip

Email Round Trip sensors ensure the end-to-end delivery of emails and make it possible to monitor availability and performance of a complete email delivery process. There are two sensor types for this task: SMTP&POP3 Round Trip Sensor SMTP&IMAP Round Trip Sensor
870
862
Both initially deliver an email to a mail server using SMTP. Afterwards the receiving mailbox is scanned using Post Office Protocol version 3 (POP3) or Internet Message Access Protocol (IMAP) until the email arrives. The test email contains a unique code in the topic which is used to identify the email, such as PRTG8 Roundtrip Mail: {6D136420-5A3E-46CF-871A1DAF0C4F3D5D}. When PRTG successfully received an email in this email round trip cycle, it marks the respective message for deletion on the mail server. Usually, a mail server will then delete this email. For best performance, we recommend using a dedicated email accounts for email round trip sensors.
Monitoring an Email Round Trip
In the scenario shown above, there are three steps in the round trip: St ep 1 PRTG delivers an email via the SMTP protocol to a mail server (just like an email client). St ep 2 The SMTP server delivers the email to a POP3/IMAP server (which can be located at a remote site, in your local LAN or on the same server as well).
03.05.2013
1829
Part 10: Sensor Technologies | 8 Monitoring Email Round Trip
St ep 3 Every few seconds PRTG connects to the POP3/IMAP server until the test email arrives.
Recommended Configuration
Here is a simple concept to check delivery of email out of and into your organization: 1. Create a dedicated email account for this test in your mail system. 2. Set up an external email account (hosted mail server, free mail service, etc.) and configure it to send all emails back to this dedicated email account in your organization (which you created in Step 1). 3. Set up PRTG's round trip sensor to send an email to the external email account (which you created in Step 2) using your LAN's mail server and then check for the email account on your mail system (which you created in Step 1) for arrival of the email. With this technique you are testing multiple aspects of your email server setup. As long as the sensor shows a green light, this means: Your email server accepts emails via SMTP. Emails are being sent to the outside world (internet connection works, MX lookups work etc.). Emails from external mail server can be delivered into your mail system (this includes aspects like the fact that the MX records for your domain are correct, your mail server can be reached from the outside world, your email filtering is working etc.). Emails can be retrieved using POP3 (or IMAP). Note: Please use dedicated email accounts with this sensor type. If you use more sensors of this type, please make sure that each sensor uses its own email accounts.
Conclusion
These two sensor types are a great tool to ensure delivery of email from and to your mail servers. Compared to the standard SMTP, POP3 and IMAP sensors - which only check the availability of these services - the two roundtrip sensor types actually monitor the complete transaction from accepting the mail on the first email server to delivery of the mail on the final POP3/IMAP server.
1830
03.05.2013
Part 10: Sensor Technologies | 9 Monitoring Backups
10.9
Monitoring Backups
Monitoring your backup software enables you to be sure that your recent backups succeeded. With PRTG you can check the email notifications of various backup jobs. You only need two things for backup monitoring: 1. Configure your backup software to send emails to a dedicated email account, and 2. configure PRTG's IMAP Sensor
577
for backup monitoring.
PRTG will analyze the backup emails for you and set the status of the IMAP sensor accordingly. This way you will see the states of all your backup jobs at a glance.
Bac kup Monitoring v ia Email
Setting up Backup Monitoring

Please refer to our Knowledge Base for a step-by-step tutorial to monitor your backup jobs: Monit oring Backup Solut ions via Email http://www.paessler.com/knowledgebase/en/topic/47023
03.05.2013
1831
Part 10: Sensor Technologies | 10 Monitoring Virtual Environments
10.10 Monitoring Virtual Environments
WORK IN PROGRESS Sorry, this section is not finished yet. Please see future versions of this manual for new content.
1832
03.05.2013
Part 10: Sensor Technologies | 11 Monitoring Databases
10.11 Monitoring Databases

Monitoring your databases enables you to ensure that, on the one hand, database queries are processed in time, and, on the other hand, that the database itself performs within the defined parameters. Furthermore, database monitoring with PRTG makes it possible to be alerted via a corresponding sensor status if database queries return an unexpected result value. PRTG comes with built-in native sensors for the most common databases: Microsoft SQL servers MySQL servers Oracle SQL servers However, it is possible to monitor many other database servers. For this concern, PRTG uses the ActiveX Data Objects (ADO) interface in combination with the PowerShell scripting language. There are two types of database sensors: Sensors monit oring dat abases direct ly 1833 : They monitor from the user perspective, sending a request to the database server and receiving values. These values can optionally be compared to the expected values to ensure they match. Sensors monit oring dat abase performance 1834 : They have a more abstract view on database servers and monitor performance counters via Windows Management Instrumentation (WMI).
Sensors Monitoring Databases Directly

PRTG provides several sensors which can "look into" the content of databases. Sensors of this type connect to the database server and show the response time. In addition, these sensors can read out the number of records and a value, depending on an SQL query. The following sensors are available for this kind of monitoring: Microsoft SQL Sensor 2005, 2008, and 2012). My SQL Sensor
645 637
: can monitor Microsoft SQL servers (MSDE, SQL Server 7, 2000,
: can monitor MySQL servers (3.23, 4.0, 4.1, 5.0, and 5.1)
Oracle SQL Sensor 684 : can monitor Oracle SQL servers (7.3, 8.0, 8i, 9i, 10g, and 11g). Note: You have to provide all necessary information manually, in contrast to the other SQL sensors listed above. ADO SQL Sensor 301 : can monitor almost all available database servers, as well as data files via an ActiveX Data Objects (ADO) connection and a PowerShell script. For these sensors you can define a valid SQL statement that will be sent to the database server. With every scanning interval, the sensor will execute the query against the database and a corresponding value will be returned. You can indicate in the sensor settings whether you want to post-process this result and specify the intended sensor behavior for the received value ("Warning" status, "Down" status).
19.07.2013
1833
Part 10: Sensor Technologies | 11 Monitoring Databases
Sensors Monitoring Database Performance

Performance sensors for database servers have a more "abstract" view on databases and regard performance "from the outside". They do not read out any values of the database, neither do they send SQL queries to databases. This sensor type is only available for Microsoft SQL servers. These sensors monitor Microsoft SQL servers' performance via Windows Management Instrumentation (WMI). You can manually set up different performance counters for your server instances, for example, general statistics, access methods, buffer and memory manager, locks, and SQL statistics. Microsoft SQL Server performance sensors are available for Microsoft SQL Server 2008 and 2012: WMI Microsoft SQL Server 2008 Sensor WMI Microsoft SQL Server 2012 Sensor
1471
1479
1834
19.07.2013
Part 11
System Administration Tools
27.11.2012
1835
Part 11: System Administration Tools |
11
System Administration Tools

Using the two applications PRTG Server Administ rat or and PRTG Probe Administ rat or from the Windows start menu, you can edit administrative settings that affect your PRTG installation, the local probe running with it, or a remote probe installation. All settings will require a restart of the Windows services for changes to take effect. Please see these following sections.
System Administration ProgramsTopics

PRTG Server Administ rat or PRTG Probe Administ rat or
1837
1857
Related Topics
Set up
1671
Failover Clust er St ep by St ep
1905
1836
27.11.2012
Part 11: System Administration Tools | 1 PRTG Server Administrator
11.1
PRTG Server Administrator

In the PRTG Server Administrator program you can define different system-oriented settings that affect your PRTG installation, as well as restart services and view log information. Note: To get familiar with the different components of PRTG, we recommend reading the Archit ect ure 73 section. Note: All settings made here are only valid for the local installation running on the computer you're opening the program on. In order to change settings for another installation, for example, another cluster node installation, please log in to this computer and open the program there. From the PRTG Net work Monit or group in Windows start menu, please select PRTG Server Administ rat or to open the application. You can choose from these options in different tabs: Web Server Core Server Cluster
1842 1837
1840
Memory Usage Administrator License

1851
1847
1850
Start/Stop Logs
1854
1853
About
1856
When closing the program using the Ok button, you are asked to restart the core server Windows service in order to save the settings. Please confirm by clicking the Yes button. Otherwise the changes are ignored.
PRTG Serv er Administrator
Web Server
Edit IPs, ports, access methods and language for the Ajax interfaces.
94
and Mobile Web GUI
1797
web
07.02.2013
1837
Web ServerSelect TCP Port for PRTG's Web Server

PRTG is running a web server in order to provide the web and Windows interface. Please specify on which port this web server will run. HTTPS (Port 443) This is the recommended setting. Use a secure HTTPS connection that is encrypted via SSL on port 443. Note: Although the connection is secure, you will see an SSL Cert ificat e Warning 99 in your browser when logging in to the PRTG web interface, because the default certificate is unknown to your browser. You can install another SSL certificate for PRTG later. Please see Using Your Own SSL Cert ificat e 1914 . Note: If port 80 is free, PRTG will reserve it as well. When users try to connect on port 80 via HTTP, they will then be redirected to port 443 via HTTPS. You can change this behavior using a registry setting.
HTTPS using Cust om TCP Port Use a secure HTTPS connection that is encrypted via SSL on a custom port.
1838
07.02.2013
This option is intended for systems with an existing web server on the standard port. Enter the desired TCP port number you want the PRTG web server to run on. Note: Although the connection is secure, you will see an SSL Cert ificat e Warning 99 in your browser when logging in to the PRTG web interface, because the default certificate is unknown to your browser. You can install another SSL certificate for PRTG later. Please see Using Your Own SSL Cert ificat e 1914 . Note: If port 80 is free, PRTG will reserve it as well. When users try to connect on port 80 via HTTP, they will then be redirected to the custom port via HTTPS. You can change this behavior using a registry setting.
HTTP (Port 80) This setting is not recommended for WAN connections. Use a standard web server without SSL encryption on port 80. Note: If used on the internet, attackers could potentially spy on credentials you enter into PRTG. We strongly recommend using this option in a LAN only.
HTTP using TCP Port This setting is not recommended for WAN connections. Use a standard web server without SSL encryption on a custom port. This option is intended for systems with an existing web server on the standard port. Enter the desired TCP port number you want the PRTG web server to run on. Note: If used on the internet, attackers could potentially spy on credentials you enter into PRTG. We strongly recommend using this option in a LAN only.
Web ServerSelect IP Address for PRTG's Web Server

PRTG is running a web server in order to provide access via the web and Windows interface. Please specify which IP address this web server will run on. Note: Later, you can log into PRTG by simply pointing your browser to the specified IP address. Localhost Use 127.0.0.1 only. PRTG's web and Windows interface will only be accessible from the computer PRTG is installed on. Note: Either the selected port or at least one port in the range from 8080 to 8089 has to be available on 127.0.0.1.
07.02.2013
1839
Note: If you run PRTG on localhost, please do not use the DNS name http://localhost to log in to the web server, as this may considerably slow down PRTG's web interface. Please use your local IP address or http://127.0.0.1 instead.
All IPs Use all IP addresses available on this computer and enable access to the web server for all of these addresses. Note: The TCP port selected above must be free on every available IP address.
Specify IPs Select specific IP addresses on which the PRTG Web server will run on. A list specific to your system is shown. Add a check mark in front of every IP address you want the PRTG web server to be available at. Note: Either the selected port or at least one port in the range from 8080 to 8089 has to be available on the specified IP address. Note: Regardless of the selected setting above, one port in the range from 8080 to 8180 has to be available on the specified IP address so PRTG can create reports. The report engine will try to connect to the core server on one of these ports. Note: If PRTG does not find a network card on startup it will switch the IP setting to Localhost . This setting will remain, even if a network card is available later on. If you disabled or removed the network card on the machine running the PRTG core server, please re-check this setting.
Select System Language

Choose the language for this program from the drop down menu. Default is English. Depending on your installation, you may be able to choose other languages here. This setting will influence the language of this program, as well as the Ajax Web GUI 1797 web interfaces.
94
and the Mobile
Core Server
Define settings for the core server.
1840
07.02.2013
Core ServerProbe Connection Management

In this section you can define how PRTG handles incoming connections from probes. Choose between several options. Accept connect ions from t he Local Probe only This is the default setting. Only local probe connections will be accepted by the PRTG core server. You cannot use remote probes
1887
with this setting enabled.
Accept connect ions from remot e probes on all IPs Incoming connections from remote probes will always be accepted, no matter on which IP address of the core server they come in. Accept connect ions from remot e probes on select ed IPs only
07.02.2013
1841
Incoming connections from remote probes address(es) of the core server.
1896
will only be accepted on the selected IP
In the list, select the IP addresses by adding a check mark in front the IPs.
Core ServerProbe Connections Port

In this section you can define on which TCP port number PRTG listens to for incoming probe connections. Enter a port number. We recommend using the default value.
Core ServerLocal Storage of Data Files and Monitoring Database

Define the data folder to which PRTG will store configuration and monitoring data. Define a path or click on the Revert t o default folder to reset to default. Note: Before changing the path, make sure you stop both services and copy all data to the new location.
Cluster
In the Clust er tab you can manually change how the current core installation will behave in a cluster. Before changing settings here, please read Failover Clust er Configurat ion 1902 section.
1842
07.02.2013
ClusterCluster Settings
Depending on the current cluster settings you will see different information here. In the Clust er Mode field shows which cluster mode the current installation is running. This setting is shown for your information only and cannot be changed here. Possible values are St andalone (no cluster mode), Clust er Mode: Mast er Node, or Clust er Mode: Failover Node. The Clust er Access Key field is shown only when running in a cluster mode. This setting is shown for your information only and cannot be changed here. The Own Node ID field is shown only when running in a cluster mode. This setting is shown for your information only and cannot be changed here.
ClusterCluster Mode Actions

Depending on the current cluster settings you will see different buttons active here. Creat e a PRTG Clust er...
07.02.2013
1843
Start creating a cluster by clicking this button. The current PRTG core server will then be the Mast er Node of your cluster. After you click this button, please confirm converting this installation into a master node by clicking on the Yes button.
Conv ert This Installation Into a Cluster Master Node
A new popup window will appear.
1844
07.02.2013
Enter a Clust er Port . This is the port on which the internal communication between the different cluster nodes is sent. Make sure connections between cluster nodes are possible on the selected port. Enter or paste a Clust er Access Key . This is a unique access key. All nodes in a cluster have to be configured with the same cluster access key in order to join the cluster. Connection attempts with the wrong access key will be rejected. We recommend using the default value. Save the Clust er Access Key so you have it at hand when configuring your Failover Node (s). After confirming your settings you will be asked to restart Windows services. Please do so in order for your changes to take effect. Join a PRTG Clust er... Add this installation to an existing cluster which already has a Mast er Node, by clicking this button. The current PRTG core server will then be a Failover Node in the cluster. Note: This button is also available if you're currently running your PRTG installation in Clust er Mode: Mast er Node. This option will then change your master node to a failover node! After you click this button, please confirm converting this installation into a failover node by clicking on the Yes button.
Conv ert This Installation Into a Cluster Failov er Node
07.02.2013
1845
Enter the cluster's Mast er IP address/DNS name. It must be reachable from the machine running the failover node. Enter the other settings as defined in your Mast er Node's settings. Please make sure you use the same settings on all nodes in your cluster. Enter a Clust er Port . This is the port on which the internal communication between the different cluster nodes is sent. Make sure connections between cluster nodes are possible on the selected port. Enter or paste a Clust er Access Key . This is a unique access key. All nodes in a cluster have to be configured with the same cluster access key in order to join the cluster. Connection attempts with the wrong access key will be rejected. After confirming your settings you will be asked to restart Windows services. Please do so in order for your changes to take effect. Change PRTG Clust er Set t ings...
If you're running your PRTG installation in cluster mode, you can change the settings here. A new window will appear.
1846
07.02.2013
Enter a Clust er Port . This is the port on which the internal communication between the different cluster nodes is sent. Make sure connections between cluster nodes are possible on the selected port. Enter or paste a Clust er Access Key . This is a unique access key. All nodes in a cluster have to be configured with the same cluster access key in order to join the cluster. Connection attempts with the wrong access key will be rejected. Please make sure you use the same settings on all nodes in your cluster. After confirming your settings you will be asked to restart Windows services. Please do so in order for your changes to take effect. Revert t o St andalone... If you're currently running your PRTG installation in cluster mode, you can change it to St andalone mode. If you do so, this node will no longer be part of a cluster. After confirming your settings you will be asked to restart Windows services. Please do so in order for your changes to take effect. Mast er Heart beat This section is only visible if you're running your PRTG installation in cluster mode. The current master can execute an external executable file on a regular basis. We call this a "heartbeat". This can be used, for example, to report the IP address of the current master node to a dynamic DNS provider, so a DNS name is always redirected to the current PRTG master node in case the original master node fails and a failover node (running at a different IP address) takes over the master role. Choose between: No heart beat : Do not execute a file on a regular basis. Run t he following ext ernal execut able file every 5 minut es: Click on the ... button to choose a file you want to execute. This can be, for example, a command line tool, or a batch file. It will be executed on the current master node only, with a fixed interval of five minutes. The interval cannot be changed. Note: Please make sure the selected file is available under the same (local) path on all failover nodes. In case one of your failover nodes becomes current master, the heartbeat can only be executed reliably if the respective executable file exists on all of your failover nodes.
Memory Usage
PRTG shows several graphs in the objects' detail pages 118 in the web interface. These are kept in RAM memory for fast display without causing extra CPU load or disk usage. The longer the time frames and the shorter the intervals are, the more memory will be used for this. You can adapt the details for all four graphs. This setting will also change the caption of the objects' tabs in the web interface 94 and Enterprise Console 1744 .
07.02.2013
1847
Live The live graph is available for sensors only. For the live graph, no fixed time span is given, but you can define how many values will be displayed. The actual time span covered by the live graph depends on the scanning interval set for the sensor you're viewing and is calculated automatically. By default, 120 Values is set, which results in a graph covering a time span of two hours, if a scanning interval of 60 seconds is set for the sensor. Other scanning intervals will result in graphs covering different time spans. Choose between: 60 Values: This corresponds to a live graph covering a time span of one hour if a 1 minute scanning interval is set. Uses least RAM memory. We recommend this setting for installations with 10,000 sensors or more. 120 Values: This corresponds to a live graph covering a time span of two hours if a 1 minute scanning interval is set. 240 Values: This corresponds to a live graph covering a time span of four hours if a 1 minute scanning interval is set. 480 Values: This corresponds to a live graph covering a time span of eight hours if a 1 minute scanning interval is set. 960 Values: This corresponds to a live graph covering a time span of 16 hours if a 1 minute scanning interval is set. Uses most RAM memory.
1848
07.02.2013
Graph 1 By default, this is the 2 day s graph in the web interface. You can change it to more or less detail by choosing a time span and a monitoring interval average associated with it. Monitoring results will be averaged regardless of the actual scanning interval set for the sensors. Choose between: 1 day wit h 1 minut e averages: Results in 1440 values. 1 day wit h 5 minut es averages: Results in 288 values. 1 day wit h 15 minut es averages: Results in 96 values. Uses least RAM memory. We recommend this setting for installations with 10,000 sensors or more. 2 day s wit h 1 minut e averages: Results in 2880 values. Uses most RAM memory. 2 day s wit h 5 minut es averages: Results in 576 values. 2 day s wit h 15 minut es averages: Results in 192 values. 4 day s wit h 1 hour averages: Results in 96 values. Uses least RAM memory. We recommend this setting for installations with 10,000 sensors or more. Graph 2 By default, this is the 30 day s graph in the web interface. You can change it to more or less detail by choosing a time span covered and a monitoring interval average associated with it. Choose between: 10 day s wit h 1 hour averages: Results in 240 values. 20 day s wit h 1 hour averages: Results in 480 values. 30 day s wit h 1 hour averages: Results in 720 values. 30 day s wit h 6 hour averages: Results in 120 values. Uses least RAM memory. We recommend this setting for installations with 10,000 sensors or more. 40 day s wit h 1 hour averages: Results in 960 values. 40 day s wit h 6 hour averages: Results in 160 values. 60 day s wit h 1 hour averages: Results in 1440 values. Uses most RAM memory. 60 day s wit h 6 hour averages: Results in 240 values. Graph 3 By default, this is the 365 day s graph in the web interface. You can change it to more or less detail by choosing a time span covered and a monitoring interval average associated with it. Choose between: 100 day s wit h 1 day averages: Results in 100 values. Uses least RAM memory. We recommend this setting for installations with 10,000 sensors or more. 200 day s wit h 1 day averages: Results in 200 values.
07.02.2013
1849
365 day s wit h 1 day averages: Results in 365 values. 400 day s wit h 1 day averages: Results in 400 values. 750 day s wit h 1 day averages: Results in 750 values. Uses most RAM memory. Recalculat e Cached Dat a PRTG writes monitoring data to the disk constantly and keeps the graphs for your graph tabs in memory. If PRTG is ended unexpectedly, the graph cache may get corrupted. In this case, graphs may be shown empty or show wrong data. If you experience graph display problems, a graph recalculation will fix the problem. Enable the Recalculat e cache now option. After you close the window with Ok and confirm restart of the Windows service, PRTG will delete the data cache file and recalculate it automatically. Note: Directly after this action your graphs will be empty. They will be re-filled successively while recalculation in the background progresses. Until recalculation is finished, performance of the PRTG web interface may be affected due to high disk I/O activity.
Administrator
1850
07.02.2013
Enter the administrator's contact email address and define login credentials for PRTG. Email Address Enter a valid administrator's email address. By default, PRTG will send notifications and important messages to this address.
Login Name Enter a name for the PRTG System Administrator login; this is your default login. It is used when logging in to the PRTG Web- or Windows interface. The default login name is prt gadmin
Password Enter a password for the PRTG System Administrator login; this is your default login. It is used when logging in to the PRTG Web- or Windows interface. The default password is prt gadmin
Confirm Password Re-enter the password for the PRTG System Administrator login. The default password is prt gadmin
License
To use a PRTG license with this installation of PRTG, please enter the license information you have received from Paessler via email. To avoid typing errors, please copy and paste both the License Name and the License Key from the email. Both must be transferred exactly as shown in the email.
07.02.2013
1851
PRTG Serv er Administrator Lic ense 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 Edit ion field you will see an accepted license key. Note: You have to use the right edition for your license key. For example, the installer for trial and Freeware edition does not accept any commercial keys. For more information, please see Ent er a License Key 53 section.
1852
07.02.2013
Start/Stop
You can stop and start the core server Windows service manually. Click the St op Core Server button to stop the service, and St art Core Server to start it again. Both actions usually take from a few seconds up to several minutes to complete. Note: If you want to schedule an automatic restart of Windows services for both core server and probe service, please do so using the PRTG Probe Administ rat or. For more details see PRTG Probe Administ rat or 1860 (Start/Stop) section.
07.02.2013
1853
Logs
You can view several logs of your PRTG installation. The following buttons are available: View Today 's Webserver Log Directly view the content of the web server log for the current date. View Core Server Sy st em Log Directly view the content of the core server system log. Depending on the number of entries, it may take a few seconds until the logs are shown. Open Log Folder... Open the log file directory on your hard disk drive to access older web log files, etc. Send Logs t o Paessler... Open an assistant to send log files to the Paessler support team. Please see below.
1854
07.02.2013
LogsSend Logs to Paessler
Send Logs to Paessler
When opening a support ticket, Paessler support may ask you to send log files for further analysis. Using the Send Logs t o Paessler... button, PRTG will automatically collect, compress and send your log files. Note: This button is available when using a commercial license only. Name Please enter your name. Email Please enter your valid email address. Ticket No. This field is optional. If you have already opened a ticket at Paessler support, please provide the ticket number you received. Your files will then be associated with your ticket automatically. Please enter the ticket number starting with PAE followed by four or more digits. If you do not have a ticket number, please leave the field empty. Note: You should usually contact the support team before sending any files.
07.02.2013
1855
Configurat ion Define if your configuration file will be included in the data. Passwords are usually encrypted, but there may be some passwords stored as plain text. Short ened Define if your log files will be shortened (this is the default setting). Sometimes we will ask you to send full log files. In this case, please uncheck this box.
Click on the Send button to start data upload. Please make sure FTP and HTTP connections are allowed on this machine.
About
Displays version information for installed PRTG programs. Click on the Open Support Ticket button to ask the Paessler support team for help. This will open a new web browser window.
1856
07.02.2013
Part 11: System Administration Tools | 2 PRTG Probe Administrator
11.2
PRTG Probe Administrator

In the PRTG Probe Administrator program, you can define different system-oriented settings that affect your PRTG installation, as well as restart services and define the data storage location. Note: To get familiar with the different components of PRTG, we recommend reading the Archit ect ure 73 section. Note: All settings made here are only valid for the local installation running on the computer you're opening the program on. In order to change settings for another installation, for example, another remote probe installation, please log in to this computer and open the program there. From the PRTG Net work Monit or group in Windows start menu, please select PRTG Probe Administ rat or to open the application. You can choose from these options in different tabs: Probe Settings
1857
Outgoing IP Settings Start/Stop

1860
1859
Logs / Directory About

1865
1863
When closing the program using the Ok button, you are asked to restart the probe Windows service in order to save the settings. Please confirm by clicking the Yes button.
Probe Settings
Define general settings regarding the probe and probe connections.
27.11.2012
1857
PRTG Probe Administrator (here: Loc al Probe on Core Serv er)
Probe SettingsProbe Settings

Name of Probe Enter a name for the probe. It will appear in the device tree in the web interface. Reconnect Time Define the time that will be waited until the probe tries to reconnect to the core server in case the connection fails.
Probe SettingsConnection to PRTG Core Server

These settings will affect how the probe will connect to the core server. A probe is either a local probe or a remote probe. PRTG will automatically detect the type of probe and show the correct setting options. When y ou opened t his t ool on t he PRTG core server This probe is configured as the local probe of the PRTG core installation. It will connect to the core via 127.0.0.1.
1858
27.11.2012
Define the Port number under which probe and core server will communicate. We recommend using the default value. The Probe GID is a unique identifier for the probe and should not be changed. No access key is needed for local probe connections. When y ou opened t his t ool on a machine running a Remot e Probe This probe is configured as remote probe. Enter the Server IP address or DNS name and the port for the connection to the core server. Define the Port number under which probe and core server will communicate. We recommend using the default value. The Probe GID is a unique identifier for the probe and should not be changed. Except when substituting an existing probe, you must change it to the old probe's GID. To do so, click on the Edit GID... button and confirm the warning with Yes. You can then change the value. The Probe Access key must match one of the access keys configured in your PRTG core server installation. If it doesn't, the remote probe will not be able to connect to the core server. Please see Sy st em Administ rat ionProbes 1707 (Probe Connection Settings) section for more information. Note: Also check the allowed and denied IPs there to make sure the core server accepts the IP address of the remote probe.
Probe SettingsLanguage
Choose the language for this program from the drop down menu. Default is English. Depending on your installation, you may be able to choose other languages here.
Outgoing IP Settings
Define the IP address used for outgoing monitoring requests. If there is more than one IP on the current system available, you can specify the IP address that will be used for outgoing monitoring requests of certain sensor types. The setting is valid for all monitoring requests sent from this PRTG probe. This setting will be used for sensors using the following connection types: HTTP, DNS, FTP, IMAP, POP3, Port, Remote Desktop, SMTP, and SNMP. This is useful for devices that expect a certain IP address when queried. Default setting is aut o . PRTG will select an IP address automatically.
27.11.2012
1859
PRTG Probe Administrator Outgoing IP Settings
Outgoing IP SettingsIPv4: Outgoing IP for Monitoring Requests

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

Define the IP address for outgoing requests using the IPv6 protocol. The list shows all IP addresses available on the current system. Choose a specific IP address or select aut o . For details about the basic concept of IPv6 in PRTG, please see IPv6 92 section.
Start/Stop
Start or stop the probe Windows service and schedule system restarts.
1860
27.11.2012
Start/StopPRTG Probe Service

You can stop and start the probe Windows service manually. Click the St op Probe Service button to stop the service, and St art Probe Service to start it again. Both actions usually take from a few seconds up to several minutes to complete.
Start/StopRestart Options
For best performance we recommend to restart the Windows servers PRTG is running on from time to time. In order for PRTG to do this automatically you can schedule an automatic reboot. There are the following options: Do not perform scheduled reboot /service rest art Do not perform any scheduled reboot or restart of services automatically. We recommend a manual restart every few weeks. Perform scheduled rest art of PRTG services Restart both core server and probe service.
27.11.2012
1861
Please enter a schedule below. Perform scheduled sy st em reboot (recommended) This is the recommended setting, although not set by default. Please enter a schedule below. We recommend restarting Windows servers once a month for best performance. [Schedule] When scheduling an automatic service restart or reboot, define a schedule. The options are: Once per Week: Select a weekday and time below. Once per Mont h: Select a day of month and time below. When selecting Last , the report will always run on the last day of the month, regardless of how many days the month has. When selecting a date that does not exist in every month, e.g. the 30th in May, PRTG will automatically run the report on the last day of this month. Note: A Windows warning message will be displayed 10 minutes before reboot to inform a logged in user. The actual restart time can differ up to 30 minutes from the settings entered here!
1862
27.11.2012
Logs / Directory
Pat h for probe dat a st orage Note: This setting is relevant merely for probe only installations, for example, when running a remote probe on the system. For an installation of PRTG core server and probe, i.e. a full PRTG installation, the path setting in this window is overridden by the path defined in the settings of PRTG Server Administ rat or 1840 . Define the data folder to which PRTG will store configuration and monitoring data. Note: Before changing the path, make sure you stop both services and copy all data to the new location. Log You can view the log of your PRTG probe. The following buttons are available: Open Log File... Directly view the content of the probe system log. Depending on the number of entries, it may take a few seconds until the logs are shown.
27.11.2012
1863
Open Log Direct ory ... Open the log file directory on your hard disk drive. Send Logs t o Paessler... Open an assistant to send log files to the Paessler support team. Please see below.
Logs / DirectorySend Logs to Paessler
Send Logs to Paessler
When opening a support ticket, Paessler support may ask you to send log files for further analysis. Using the Send Logs t o Paessler... button, PRTG will automatically collect, compress and send your log files. Note: This button is available when using a commercial license only. Name Please enter your name. Email Please enter your valid email address. Ticket No. This field is optional.
1864
27.11.2012
If you have already opened a ticket at Paessler support, please provide the ticket number you received. Your files will then be associated with your ticket automatically. Please enter the ticket number starting with PAE followed by four or more digits. If you do not have a ticket number, please leave the field empty. Note: You should usually contact the support team before sending any files. Configurat ion Define if your configuration file will be included in the data. Passwords are usually encrypted, but there may be some passwords stored as plain text. Short ened Define if your log files will be shortened (this is the default setting). Sometimes we will ask you to send full log files. In this case, please uncheck this box.
Click on the Send button to start data upload. Please make sure FTP and HTTP connections are allowed on this machine.
About
27.11.2012
1865
Displays version information for installed PRTG programs. Click on the Open Support Ticket button to ask the Paessler support team for help. This will open a new web browser window.
1866
27.11.2012
Part 12
Advanced Topics
27.11.2012
1867
Part 12: Advanced Topics |
12
Advanced Topics
In this section topics are covered that address more advanced PRTG users. If you already gained some experience with PRTG, you might want to learn more about the topics following.
Advanced Topics
Act ive Direct ory Int egrat ion
1869
Applicat ion Programming Int erface (API) Definit ion
1871
1872
Channel Definit ions for xFlow, IPFIX , and Packet Sniffer Sensors Define IP Ranges Define Lookups
1878
1876
1879
Regular Expressions Add Remot e Probe
1886
1887
Failover Clust er Configurat ion Dat a St orage

1912
1902
Using Your Own SSL Cert ificat e Calculat ing Percent iles
1916
1914
1868
27.11.2012
Part 12: Advanced Topics | 1 Active Directory Integration
12.1
Active Directory Integration

PRTG offers a detailed rights management via different user groups. For detailed information please see User Access Right s 89 . In order to make user management easier, you can integrate an existing Active Directory into PRTG in four steps. During this process, you will connect an Active Directory (AD) group with a user group in PRTG. All members of your AD group will then be able to log into PRTG using their AD domain credentials. Note: You cannot add single AD users to PRTG, but only allow access for entire groups. A PRTG user will be created automatically for each AD user who logs in to PRTG successfully.
Step 1: Prepare Your Active Directory

In your Active Directory, please make sure that users you want to give access to PRTG are member of the same AD group. You can also organize users in different groups, for example, one group whose members will have administrator rights within PRTG, and another one whose members will have read-only rights within PRTG.
Step 2: Prepare Your PRTG Server

Make sure that the computer running PRTG is member of the domain you want to integrate it to. You can check this setting in your machine's Sy st em Propert ies (for example, Cont rol Panel | Sy st em and Securit y | Sy st em, click on Change set t ings link).
Step 3: Add Domain and Credentials (optional) to System Settings

In the PRTG web interface 1691 settings.
94 ,
switch to the Sy st em Administ rat ionSy st em and Websit e
In the Active Directory Domain field, enter the name of your local domain. Note: You can only integrate one AD domain into PRTG. Optional: PRTG will use the same Windows user account used to run the "PRTG Core Server Service". By default, this is the "local system" Windows user account. If this user does not have sufficient rights to query a list of all existing groups from the Active Directory, you should provide credentials of a user account with full AD access by using the Use explicit credent ials option. Save your settings.
Step 4: Add a New User Group

Switch to the User Groups tab (see Sy st em Administ rat ionUser Groups Click on the Add User Group button to add a new PRTG user group. In the dialog appearing, enter a meaningful name and set the Use Active Directory setting to Yes.
1715
).
03.05.2013
1869
Part 12: Advanced Topics | 1 Active Directory Integration
From the Active Directory Group drop down menu, select the group of your Active Directory whose members will have access to PRTG. If you have a very large Active Directory, you will see an input field instead of a drop down. In this case, you can enter the group name only; PRTG will add the prefix automatically. With the New User Type setting, define the rights a user from the selected Active Directory group will have when logging in to PRTG for the first time. You can choose between Read/ Writ e User or Read Only User (latter is useful to show data only to a large group of users). Save your settings.
Done
That's it. All users in this Active Directory group can now log in to PRTG using their AD domain credentials. Their user accounts will use the PRTG security context of the PRTG user group you just created.
Notes and Limitations

Active Directory users can log in to the web interface 96 using their Windows username and password (please do not enter any domain information in PRTG's Login Name field). When such a user logs in, PRTG will automatically create a corresponding local account on the PRTG core server. Credentials are synchronized every hour. All requests to the Active Directory servers are cached for one hour, for performance reasons. If a password is changed in the Active Directory, you must either wait for 1 hour or clear the cache manually by clicking on the Clear Caches button on the Sy st em Administ rat ionAdminist rat ive Tools 1719 page in the Set up 1671 menu). By default, there aren't any rights set for the new PRTG user group. Initially, users in this group will not see any objects in the PRTG device tree. Please edit your device tree object's settings 133 and set access rights for your newly created user group in the Inherit Access Right s section. Note: The easiest way is to set these rights in the Root Group Set t ings 213 . PRTG only supports explicit group rights. If your AD uses groups which are member of another group, PRTG will not regard inherited implicit rights of the parent group and therefore refuse login for members of those groups. PRTG will ignore AD information about Organizational Units (OUs). These values cannot be read by PRTG. PRTG does not support SSO (single sign-on).
1870
03.05.2013
Part 12: Advanced Topics | 2 Application Programming Interface (API) Definition
12.2
Application Programming Interface (API) Definition

The PRTG Application Programming Interface (API) enables you to access monitoring data and manipulate objects using HTTP requests, run your own written sensors and notifications, and customize the web interface.
Detailed HTTP API Documentation

An interactive documentation of the API is integrated into your PRTG installation: Login to the web interface 96 and select Set up | PRTG API from the main menu.
PRTG API Doc umentation
In different tabs, the documentation provides information about: HTTP API: Access monitoring data and manipulate monitoring objects using HTTP requests (includes an interactive query builder) Cust om Sensors: Create your own sensors for customized monitoring Cust om Not ificat ions: Create your own notifications to send alarms to external systems Websit e St y ling : Customize the look and feel by adding your own CSS statements You can also have a look at Paessler's PRTG demo installation's API documentation. But only the documentation that comes with your PRTG installation fits exactly the PRTG version you are using.
More
API Documentation in Paessler's PRTG Demo Installation http://prtg.paessler.com/api.htm?username=demo&password=demodemo
27.11.2012
1871
Part 12: Advanced Topics | 3 Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors
12.3
Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors

Filter rules are used for the include, exclude, and channel definition fields of Packet Sniffer, xFlow, and IPFIX sensors. They are based on the following format:
field[filter]
Valid Fields for All Sensors

IP Possible values: IP address or DNS name (see Valid Data Formats Port any number SourceIP Possible values: IP address or DNS name (see Valid Data Formats SourcePort any number Dest inat ionIP Possible values: IP address or DNS name (see Valid Data Formats Dest inat ionPort any number Prot ocol Possible Protocol values: TCP, UDP, ICMP, OSPFIGP, or any number) TOS Type Of Service (any number) DSCP Differentiated Services Code Point (any number)
1875 1875 1875
below)
below)
below)
Additional Fields for Packet Sniffer Sensors Only

MAC physical address (see Examples SourceMAC physical address Dest inat ionMAC physical address Et herTy pe Possible EtherType values: IPV4, ARP, RARP, APPLE, AARP, IPV6, IPXold, IPX, or any number VlanPCP IEEE 802.1Q VLAN Priority Code Point
1875
below)
1872
08.10.2013
VlanID IEEE 802.1Q VLAN Identifier TrafficClass IPv6 Traffic Class (corresponds to TOS used with IPv4) FlowLabel IPv6 Flow Label
Additional Fields for NetFlow v5 and jFlow v5 Sensors Only

Int erface any number ASI any number InboundInt erface any number Out boundInt erface any number SenderIP IP of the sending device. This is helpful if several devices send flow data on the same port, and you want to divide the traffic of each device into a different sensor channel. Possible values: IP address or DNS name (see Valid Data Formats 1875 below) SourceASI any number Dest inat ionASI any number
Additional Fields for xFlow v9 and IPFIX Sensors Only

Int erface any number ASI any number InboundInt erface any number Out boundInt erface any number SenderIP IP of the sending device. This is helpful if several devices send flow data on the same port, and you want to divide the traffic of each device into a different sensor channel. Possible values: IP address or DNS name (see Valid Data Formats 1875 below) SourceASI any number
08.10.2013
1873
Dest inat ionASI any number MAC physical address SourceMAC physical address Dest inat ionMAC physical address Mask "Mask" values represent subnet masks in the form of a single number (number of contiguous bits). Dest inat ionMask "Mask" values represent subnet masks in the form of a single number (number of contiguous bits). Next Hop (IP address) Possible values: IP address or DNS name (see Valid Data Formats VLAN "VLAN" values represent a VLAN identifier (any number). SourceVLAN "VLAN" values represent a VLAN identifier (any number). Dest inat ionVLAN "VLAN" values represent a VLAN identifier (any number).
1875
below)
Additional Fields for sFlow Sensors Only

Int erface any number InboundInt erface any number Out boundInt erface any number SenderIP IP of the sending device. This is helpful if several devices send flow data on the same port, and you want to divide the traffic of each device into a different sensor channel. Possible values: IP address or DNS name (see Valid Data Formats 1875 below) MAC physical address SourceMAC physical address Dest inat ionMAC physical address
1874
08.10.2013
Valid Data Formats

IP fields support wildcards (*), range (10-20) and hostmask ( /10, /255.255.0.0) syntax, as well as DNS names. Number fields support range (80-88) syntax. Protocol and EtherType fields support numbers and a list of predefined constants. For detailed information on IP ranges, please see Define IP Ranges section.
1878
Examples
All of the following filter rules are valid examples:
SourceIP[10.0.0.1] SourceIP[10.*.*.*] SourceIP[10.0.0.0/10] DestinationIP[10.0.0.120-130] DestinationPort[80-88] Protocol[UDP] MAC[00-60-50-X0-00-01] DSCP[46]
Complex expressions can be created using parentheses ( ) and the words and, or, or and not . For example, this is a valid filter rule:
Protocol[TCP] and not (DestinationIP[10.0.0.1] or SourceIP[10.0.0.120-130])
Related Topics
Channel Definit ions for xFlow, IPFIX , and Packet Sniffer Sensors Monit oring Bandwidt h via Packet Sniffing Monit oring Bandwidt h via Flows
1820 1818 1876
08.10.2013
1875
Part 12: Advanced Topics | 4 Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors
12.4
Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors

When adding Custom xFlow sensors, Custom IPFIX, or Custom Packet Sniffing sensors, you will notice a field entitled Channel Definit ion. In this field you need to provide the channel definitions in the following syntax (one entry per channel):
#<id>:<Name> <Rule>
Syntax
<id> needs to be 1 or greater and must be unique for the sensor (i.e., each channel definition must have a unique ID). Note: The maximum channel ID you can use is 2147483648 (2^31). Higher IDs are not supported. We recommend using channel IDs 1, 2, 3, etc. The <id> is linked to the historic data: As soon as it has been changed, the history for this particular channel is lost. One rule can span multiple lines. The next rule starts with a # as first character in a line. <name> is the channel's display name. The rules are processed top to bottom (the number doesn't matter) and the data is accounted to the first match. One Ot her channel is added automatically. Behind the name a optional [<unit >] can be used to override the automatic unit based on the source sensors. The <Rule> syntax is identical to the one described in the Filt er Rules for xFlow and Packet Sniffer Sensors 1872 section. Since data is accounted to the first match, please make sure to start with the most specific rule at the top getting less specific to the bottom. Note: We recommend writing the rule list in an external editor and paste it into the respective PRTG field. Otherwise, if the rules contain an error, the entries will be removed when adding the rules in case!
Example
General example:
#5:HTTP Protocol[TCP] and (SourcePort[80] or DestinationPort[80] or SourcePort[8080] or DestinationPort[8080])
1876
08.10.2013
Part 12: Advanced Topics | 4 Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors
Channel definition example for differentiating by protocol:

#1:TCP Protocol[TCP]
#2:UDP Protocol[UDP]
#3:ICMP Protocol[ICMP]
Related Topics
Filt er Rules for xFlow, IPFIX , and Packet Sniffer Sensors Monit oring Bandwidt h via Packet Sniffing Monit oring Bandwidt h via Flows
1820 1818 1872
More
Knowledge Base: Can I add custom channels to standard Packet Sniffer and NetFlow sensors? http://www.paessler.com/knowledgebase/en/topic/2143
08.10.2013
1877
Part 12: Advanced Topics | 5 Define IP Ranges
12.5
Define IP Ranges
In some setting fields, you can either enter a host name or single IP address, or you can define IP ranges. PRTG follows a common syntax for this. IP ranges are available, for example, for xFlow and Packet Sniffer sensors 279 , and for probes settings 1707 . Note: For the syntax available for PRTG's automatic network discovery, please see Aut oDiscovery 183 (IP Selection Method setting).
Available Options
Opt ion Simple
Descript ion Enter a fixed IP address. Enter a hostname. PRTG will resolve it to an IP address in your network. Enter a hostmask. A hostmask defines the relevant bits of the IP address. Enter an IP address range. Please replace each of a, b, c , d by either * (asterisk) for any value; corresponds to 0-255 or x-y for any range between 0 and 255.
Sy nt ax
Example(s)
a.b.c.d
10.0.10.9
Hostname
hostname
device-xyz
Hostmask
a.b.c.d/h or a.b.c.d/e.f.g.h
10.0.0.0/255
Range
a.b.c.d
10.0.0.1-20 or 10.*.0.* or 10.0.050.*
1878
27.11.2012
Part 12: Advanced Topics | 6 Define Lookups
12.6
Define Lookups
PRTG uses lookups for some sensor types with custom channels. In general, lookups map status values as returned by a device (usually integers) to more informative expressions that show you the status of a monitored device as a clear message. Additionally, lookups can define the sensor status 115 that will be shown for certain status codes (similar as sensor channel limits 1568 can define a sensor status, too). For example, for a printer, PRTG can show a sensor in a yellow Warning 115 status with channel values like "Toner Low" instead of simple status codes. Lookups can be customized individually; you can define your own texts that will be shown in a sensor's channel. Note: Lookups do not change data in PRTG's database, but they merely change the way sensor channels are shown. Any change to lookup definition files will apply to historic as well as live data.
Requirement: Channel Unit "Custom"

Note: All channels with enabled Value Lookup need to use the channel Unit "Custom". For details, refer to section Sensor Channels Set t ings 1568 .
Gauges of Lookup Channels

PRTG can display gauges for channels which use lookups. We recommend staying below 120 lookup values in order to display informative gauges for primary channels. Non-primary channels have an upper limit of around 40 lookup values.
A Gauge Showing the Status of a Lookup Channel
Lookups Directory and Format

Lookups are defined in XML format in files ending in .ovl. PRTG's standard lookup files are located in the PRTG program directory 1912 in a sub folder named lookups. These files are maintained by PRTG itself. In each of the files lookups are defined for one or more sensors. Furthermore, the lookups folder contains a sub folder named cust om to store your customized lookups. The files follow a basic principle: For each numeric value you can define:
08.10.2013
1879
A message that will be looked up and shown instead of the value The status the sensor will show
Example
The following code illustrates the lookup definition for the toner status of the SNMP HP LaserJet Hardware 963 sensor:
<?xml version="1.0" encoding="UTF-8"?>
<ValueLookup id="oid.paessler.hplaserjet.tonerstatus" desiredValue="1" xmlns:xsi="http://www.w3.o <Lookups> <SingleInt state="Ok" value="0"> Toner Okay </SingleInt> <SingleInt state="Warning" value="1"> Toner Low </SingleInt> <SingleInt state="Error" value="2"> No Toner Cartridge Loaded </SingleInt> </Lookups> </ValueLookup>
The schema in the example provides an insight how lookups are defined: The <?xml> tag in the first line defines the content as XML. The <ValueLookup> tag in the second line contains: The ID which will be shown in the Sensor Channels Set t ings
1566
The desiredValue 1883 attribute contains the value which will be used for the calculation of the "Coverage". In this example, 1 is defined. The xsi attributes refer to PRTG's predefined XML schema definitions (which allow easy editing of lookup files with supported editors). We recommend using the default value. Between the tags <Lookups> and </Lookups> the particular lookups for the sensor data are defined: A lookup entry starts with a tag containing the type of the status value, the lookup type (in this example, this is always <SingleInt >). Separated by whitespace, the st at e attribute defines the status the sensor will show. Allowed values are: Ok, Warning , Error, and None ("None" will trigger no status change). The value attribute defines which numeric value will trigger the lookup. This is the value that PRTG will receive from the device.
1880
08.10.2013
The t ext defines the substitution text that will be shown instead of the value. For example, a status message. The same way all other possible lookups are defined. The lookup definitions are closed by the tag </Lookups>. The file closes with </ValueLookup>. In our example, the lookup file will have the following effect:
Value as Report ed from HP Print er 0 1 2
Value Shown in PRTG (Sensor Channel)
Sensor St at us Shown by PRTG
Toner Okay Toner Low No Toner Cartridge Loaded
Up Warning Down
The XML Schema

An overall schema of the XML files containing the lookups definitions can be sketched like this:
<?xml version="1.0" encoding="UTF-8"?> <ValueLookup id="..." desiredValue="..." xmlns="..." xsi="..."> <Lookups> <SingleInt state="..." value="..."> status text </SingleInt> <BitField state="..." value="..."> status text </BitField> <Range state="..." from="..." to="..."> status text </Range> [several other lookup definitions]
</Lookups> </ValueLookup>
08.10.2013
1881
Element
Descript ion
At t ribut es, Value Assignment , and Cont ent version and encoding are "1.0" resp. "UTF-8" content: <ValueLookup>contentValueL ookup</ValueLookup>
<?xml> content
This is the XML declaration. Every XML file begins with it.
<ValueLookup> contentValueLookup </ValueLookup>
Defines the ID of the channel, what desiredValue is used, and links to PRTG's predefined schema definitions, which allow easy editing of lookup files with supported editors.
id: specifies how the name of the lookup file is shown in the Sensor Channels Set t ings 1566 desiredValue below
1883
: please see
xmlns:xsi/xsi: refers to predefined XML schema definition contentValueLookup: lookup definitions <Lookups>contentLookups</ Lookups> <Lookups> contentLookups </Lookups> Defines the particular lookups for the sensor data. contentLookups: one or more lookup entries, see below
<SingleInt > status text </SingleInt > <Bit Field> status text </Bit Field> <Range> status text </Range>
Each element defines one lookup entry. There can be one or more entries in this format. SingleInt, BitField, and Range are lookup types 1883 .
st at e: defines the state the sensor will show; allowed values: Ok, Warning , Error, None value: defines the value which triggers the lookup. Please enter an integer value. Note: Range needs always both values "from" and "to". status text: defines a st at us t ext that will be used as substitution text and shown instead the integer value. For example, a status message.
Since all the XML files containing lookup definitions are delivered in a pre-given schema as indicated above, it will be easy and comprehensible for you to customize lookups.
1882
08.10.2013
Customizing Lookups
There is a subfolder named lookups\cust om located in the PRTG program directory 1912 . To customize lookups copy the desired lookup file from the lookups folder to the cust om folder or create a new file there. When using the same ID in the ValueLookup tag, the files in the lookups\cust om folder have a higher priority than the original files in the lookups folder. This way, your customizations will be handled preferably by PRTG instead of the original lookup settings. Open the file with an XML editor and edit the lookups following your personal preferences. You can define your own messages as well as you can customize sensor states for the particular return values. For example, if you do not want an "Error" status (i.e. a sensor Down status) for the return value "2" but only a warning, then you can replace "Error" with "Warning". Note: The possible states are given in the LookupSt at e.xsd file in the custom directory. Following the schema of the XML files that are delivered with PRTG enables you to edit the lookups in a safe way.
desiredValue Attribute
It is necessary to define a desiredValue in the lookup files. The desiredValue corresponds to a status value triggering a lookup. PRTG calculates the percentage of time this specific state has been monitored. The result is displayed for all data tables and graphs that show averaged values. Considering the example above where the desiredValue is "1", PRTG will calculate the percentage of time the toner status has been "Warning". If in a time span of five minutes four of five sensor scans returned a "Warning" status, PRTG would show an average of 80% for this time span, because in 80% of the time the sensor showed a "Warning".
Lookup Types: SingleInt, BitField, Range

Beside the lookup type SingleInt as seen above, there are two other lookup types: Bit Field and Range. Using these types you can define lookup values beyond simple integers.
08.10.2013
1883
Lookup Ty pe SingleInt
Descript ion Uses an int eger to define a lookup for one status value.
Sy nt ax
value="int" Should only be used if you have basic knowledge about bitmasks. Please see More 1885 below for a general introduction. Note: Every value has to equal a power of two (e.g., 1, 2, 4, 8, 16, 32, 64, etc.). from="int" to="int"
BitField Uses a bit field for multiple status values.
Range Uses an inter range from-t o to define a lookup for several status values.
Note: Using ranges, the parameters "from" and "to" always have to be defined. If you want to query only one single value in a range file, this value must be set as parameter for "from" and "to" (e.g., from="2" to="2").
Note: You can use only one kind of lookup type in one lookup file. For example, only SingleInts, BitField, or Ranges. Different lookup types in one file are not allowed.
Define Lookup Files in Sensor Channel Settings

For each sensor with a custom channel you can define a lookup file that will be used. This is done in a sensor's channel settings with an option called "Value Lookup". This option is visible for many SNMP sensors, some applicat ion sensors, and always for the following sensor types: EX E/Script Sensor
415
EX E/Script Advanced Sensor SNMP Cust om Sensor

914
424
(if a Cust om unit is defined)
For details, please see the Sensor Channel Set t ings
1566
section.
Loading Lookups
You can (re)load the defined lookups in the custom folder by clicking the Load Lookups button. This button can be found in PRTG under Set up | Sy st em Administ rat ion | Administ rat ive Tools 1719 .
1884
08.10.2013
DebuggingWhat will happen if...?

A return value is defined in the lookups that never will be returned by a device because the value is not assigned: The value will never be triggered, so PRTG will simply ignore this entry. PRTG receives a return value that is not defined for lookups: No substituion message can be found. PRTG will just show the return value. Different lookup types are in one lookup file: This is not allowed. PRTG will not consider different types.
More
Wikipedia: Masks (computing) http://en.wikipedia.org/wiki/Bit_mask
08.10.2013
1885
Part 12: Advanced Topics | 7 Regular Expressions
12.7
Regular Expressions
For some sensors, you can use regular expressions to match a search pattern. PRTG will use PCRE-RegExp. In the following, we will provide examples for the most common patterns.
Common Search Patterns

Find matches containing the word error or alarm:
\b(error|alarm)\b
Find matches containing the words error and alarm in any order:
(?=.*\berror\b)(?=.*\balarm\b).*
Find matches containing all of the words t ree, flower, leaf, and bug , in any order:
(?=.*\btree\b)(?=.*\bflower\b)(?=.*\bleaf\b)(?=.*\bbug\b).*
Example
The search pattern
(?=.*\berror\b)(?=.*\balarm\b).*
will match the following expressions: alarm error error alarm I am an error and I evoke an alarm I am an alarm and I indicate an error An alarm combined with an error indeed! An error combined with an alarm, too!
More
Regex Tester: Test Regular expressions interactively http://www.regexpal.com Wikipedia: Regular expression http://en.wikipedia.org/wiki/Regular_expression
1886
08.10.2013
Part 12: Advanced Topics | 8 Add Remote Probe
12.8
Add Remote Probe

To monitor different sub-networks that are separated by a firewall, to keep an eye on remote locations, or for several other scenarios, you can extend your monitoring by installing one or more Remot e Probes.
Monitoring Remote Loc ations v ia Remote Probes
Extend your Monitoring Now

Installing remote probes is easy and done in a few minutes. Please see the sections linked below for further instructions. Background: Remot e Probes and Mult iple Probes Installing: Remot e Probe Quick Inst all Step by Step: Remot e Probe Set up
1896 1891 1888
More
Video Tutorial: Core Server and Remote Probes http://www.paessler.com/support/video_tutorials/distributed_monitoring
03.05.2013
1887
Part 12: Advanced Topics | 8 Add Remote Probe 1 Remote Probes and Multiple Probes
12.8.1 Remote Probes and M ultiple Probes

Upon installation, PRTG creates the first probe automatically, called the Local Probe. It runs on the same machine as the PRTG core server and monitors all devices from this system, using the sensors you have configured. Working with only one local probe should suffice for Local Area Network (LAN) monitoring and if you want to monitor one location only.
Scenarios Requiring Remote Probes

However, there are several situations making it necessary to work with Remot e Probes in the same LAN or in remote locations. Among these situations are the following: You have more than one location and you need to make sure that services are available from all locations. Your network is separated in several LANs by firewalls, and the local probe cannot monitor specific services across the firewalls. You need to monitor systems in a Virtual Private Network (VPN) across public or in-secure data lines. You want to sniff packets on another computer. You want to monitor NetFlow data on another computer. You experience performance issues with CPU intensive sensors like packet sniffer or NetFlow sensors and need to distribute the load over more than one PC. The following chart shows an example for a remote probe scenario.
Monitoring a Distrubuted Network with PRTG (Illustration Also Av ailable as Video Tutorial)
The PRTG core server inside the Corporate LAN (bottom right) is able to monitor: Services inside the Corporate LAN using the Local Probe. Services behind a firewall in the Corporate LAN using Remot e Probe 1. Secured services inside the Branch Office (top left) using Remot e Probe 2.
1888
03.05.2013
Secured services on Mail Server and Web Server using Remot e Probe 3 and Remot e Probe 4 installed directly on these servers. Public services on the internet using any of the probes.
How Probes Work

As soon as a probe is started, it automatically connects to its core server 74 , downloads the sensor configuration, and begins its monitoring tasks. The core server sends new configuration data to a probe as soon as the monitoring configuration is changed by the user. Probes monitor autonomously and send the monitoring results back to the core server for each check they have performed. If the connections between core and probe fails for any reason (for example, a reboot of the computer running the core server) the probe continues its monitoring and stores the results. During a connection loss a buffer stores a maximum of 500,000 sensor results in RAM memory of the remote probe system (up to 50 - 200 MB). This means that for 100 sensors with one minute interval the monitoring results of up to 3 days can be buffered (or 52 minutes for 10,000 sensors with one minute interval). The probe automatically reconnects to the core as soon as it is available again and transmits all monitoring results gathered during the connection loss. The connection between probe and core is initiated by the probe, secured using Secure Sockets Layer (SSL). This means that the data sent back and forth between core and probe is not visible to someone capturing data packets. The core server provides an open TCP/IP port and waits for connection attempts from probes. If a new probe connects for the first time the administrator will receive a ToDo and will then see the new probe in the device tree. As a security precaution, the probe must be manually acknowledged by the administrator in the ToDos list before any sensors can be created and monitored. The administrator can also deny a probe which will then be disconnected. No further connection attempts will be accepted and the probe IP is added to the Deny IPs list in the probes system settings (see Sy st em Administ rat ionProbes 1707 section). This ensures that unauthorized probes cannot connect to a core server. Because the probe initiates the connection, you must ensure that a connection can be established from the outside world onto your core server. For example, you may need to open any necessary ports in your firewall and you may need to specify a Network Address Translation (NAT) rule for your network. The process is the same as if you wanted to allow access to the web server provided by the PRTG core server via port 443, for example.
Automatic Probe Update

Whenever a new version of PRTG is installed on the core server, all remote probes will automatically download and install the updated version of the probe as soon as they reconnect to the updated core installation.
03.05.2013
1889
The local probe has already been updated during the core installation. All remote probes are automatically downloading the new binaries using the SSL-secured probe/core connection. The download of the 4 MB file takes between a few seconds (in a LAN) and a few minutes (via internet connections), depending on the available bandwidth. As soon as the update has been downloaded the probe disconnects, installs the update and reconnects to the core server. This takes between 20 and 100 seconds. Please note that during the update phase the monitoring of the local probe can be affected due to the bandwidth required for the downloads.
More
Remot e Probe Quick Inst all Remot e Probe Set up
1896 1891
1890
03.05.2013
Part 12: Advanced Topics | 8 Add Remote Probe 2 Remote Probe Quick Setup
12.8.2 Remote Probe Quick Setup

PRTG provides an easy, semi-automatic install mechanism for a new Remote Probe. You can perform a remote installation of a probe directly in PRTG's web interface by right-clicking on a device in the PRTG device tree. Note: This is an experimental feature. It is possible that direct installation does not work in all situations. In this case, please see Debugging 1895 and Remot e Probe Set up Using Inst aller 1896 . In order to install a Remote Probe directly from the web interface, follow the steps below: Step 1: Meeting Requirements Step 2: Preparing Core Server Step 3: Providing Credentials
1891
1891
1893
Step 4: Installing Remote Probe
1893
Step 5: Approving New Remote Probe
1894
Please look carefully at the requirements in the first three steps.
Step 1: Meeting Requirements

There are some conditions which have to be met in order to install a probe remotely on another computer. Please ensure the following: The target computer must be running with operating system Windows (XP or later). The target computer must be accessible through Remote Procedure Call (RPC). This is usually the case when your PRTG server and the target computer are located in the same LAN segment. Otherwise, open Windows services.msc on the target computer. Start the Remote Procedure Call (RPC) service. You cannot install a remote probe on a probe device. You have to permit programs to communicate through your Windows Firewall. Open the settings of your Firewall and choose Allow programs t o communicat e t hrough Windows Firewall. Mark the checkbox for Remot e Service Management , and the checkbox Public in the corresponding line. You cannot install a remote probe on the computer where PRTG's Core Server runs. The IP address setting for probe connections to the core server must not be 127.0.0.1. Please see Step 2 1891 how to prepare the Core Server.
Step 2: Preparing Core Server

Before remote probes can connect to the core server, you have to edit the relevant settings in the PRTG Server Administ rat or 1837 .
13.06.2013
1891
Core Serv er Settings in PRTG Serv er Administrator Tool
By default, a core server accepts connections from t he Local Probe only (this is, IP address 127.0.0.1). This setting does not allow for remote probes. It is the most secure setting. In order to allow external probes to connect, please change to the Core Server tab, and in the Probe Connect ion Management section, choose one of the following options: Accept connect ions from remot e probes on all IPs: We recommend using this setting for easy setup (this is, IP address 0.0.0.0). Accept connect ions from remot e probes on select ed IPs only : Specify the IP addresses that will accept incoming connections. As Probe Connect ions Port , you can leave the standard port number, even when configuring several probes. Please make sure this port is not blocked by firewall rules on your core server's side. When you are done, click OK to save your settings. The core server process must be restarted so that the changes take effect. For detailed information about these settings, please see PRTG Server Administ rat or (Core Server) section.
1840
1892
13.06.2013
Step 3: Providing Credentials

If not done yet, add a device 261 to PRTG that represents the target computer where you want to install the remote probe on. You have to set the correct Windows credentials for this device. Open the Device Set t ings
261
In the Credent ials for Windows Sy st ems section, provide Domain or Comput er Name, Username, and Password for the target computer. You can also inherit
82
the credentials from its parents' settings.
Please make sure that this user account has administration rights on the target computer.
Step 4: Installing Remote Probe

In the device tree overview, open the context menu Choose Device Tools > Inst all Remot e Probe... . The install assistant will appear on a new page.
156
of the target device.
Remote Probe Install Assistant
13.06.2013
1893
The install assistant is divided into four sections: Experimental feature notice and short introduction Det ails: overview about the device, this is, name, status, priority, parent probe, parent group, and sensor states in place with their number Prerequisit es: for details, see Step 1
1891
St art Probe Inst allat ion: time estimation for installation and installation start button If prerequisites are not met, you cannot start the installation process. Open requirements will be highlighted in red. Please correct these to continue!
Installation Unable to Start due to Unmet Prerequisites
If all prerequisites are met, you can install the remote probe on the target computer by clicking the button Inst all Remot e Probe on "[device name]". Wait until the process has ended. If installation was successful, the following message will appear in the St art Probe Inst allat ion section: Done. Result is: OK. Note: Every time you start an installation, no matter if it is successful or not, a key will be added automatically to Access key s in Probes Set t ings 1707 .
Step 5: Approving New Remote Probe

If installation was successful, further instructions are given after the result message. As indicated, go back to the device tree 102 and acknowledge the new probe. The approval button will appear at the bottom of the devices list.
1894
13.06.2013
Approv ing New Remote Probe
Click on Approve new probe to acknowledge the created remote probe. You can also discard the new probe by clicking Deny new probe. Note: When denying or removing a remote probe, this device's global ID (GID) will be entered to Deny GIDs in Probes Set t ings 1707 . Note: Denying the remote probe in the PRTG device tree does not uninstall the probe, but only denies access to the core server. The probe will continue to run on the target system until you uninstall it manually. After approving, the approval button will turn into a Working status. Please wait while the probe connects. Once approved, PRTG automatically creates a set of sensors for the probe to ensure that bottle-necks on the probe will always be noticed. We recommend keeping these sensors. You are able now to create groups, devices and sensors for monitoring via the new probe.
Debugging
Please be aware that installing a remote probe from PRTG's web interface is an experimental feature. Thus, it can be the case that this approach is not possible in all situations. However, please follow the steps of this chapter closely when encountering problems with the Remote Probe Quick Install. Especially consider the conditions as described in Step 1 1891 of this chapter like Windows Firewall settings. If the quick installation procedure described in this section does not work with your setup, please install your remote probes manually; see section Remot e Probe Set up Using Inst aller 1896 .
13.06.2013
1895
Part 12: Advanced Topics | 8 Add Remote Probe 3 Remote Probe Setup Using Installer
12.8.3 Remote Probe Setup Using Installer

This section will guide you through the steps to set up a remote probe using the Remote Probe Installer. For a semi-automatic installation of a Remote Probe directly from PRTG's web interface, see section Remot e Probe Quick Set up 1891 . Step 1: Prepare Core Server
1896
Step 2: Settings in Web Interface
1898
Step 3: Download and Install Remote Probe
1898
Step 4: Configure Remote Probe Connection
1899
Step 5: Approve New Probe and Start Monitoring Debugging Probe Connection Problems
1900
1900
There are preparations to do on the core server, so it accepts incoming remote probe connections. Then you log in to the computer you want to install the remote probe on, download the installer from your PRTG web interface, and install it.
Step 1: Prepare Core Server

Before remote probes can connect to the core server you must edit the relevant settings in the PRTG Server Administ rat or 1840 .
1896
13.06.2013
Core Serv er Settings in PRTG Serv er Administrator
By default, a core server accepts connections from t he Local Probe only . This setting does not allow remote probes, which is the most secure setting. In order to allow external probes to connect, please change to the Core Server tab, and in the Probe Connect ion Management section, choose one of the following options: Accept connect ions from remot e probes on all IPs: We recommend using this setting for easy setup. Accept connect ions from remot e probes on select ed IPs only : Specify the IP addresses that will accept incoming connections. As Probe Connect ions Port , you can leave the standard port number, even when configuring several probes. Please make sure this port is not blocked by firewall rules on your core server's side. You have to configure the same port number in your remote probe's settings, so please save it for later use. When you are done, click OK to save your settings. The core server process must be restarted so that the changes take effect. For detailed information about these settings, please see PRTG Server Administ rat or (Core Server) section.
1840
13.06.2013
1897
Step 2: Settings in Web Interface

Login to the Ajax web interface 96 . From the main menu, select Set up | Sy st em Administ rat ion | Probes to access the probes settings.
Probes Settings in Sy stem Administration
From the Access key s field, copy one access key you will use for the remote probe connection. You can also enter a new access key with arbitrary signs and length if you like. In any case save the correct access key for later use. In the Allow IPs field, enter the IP address of the computer you will install a remote probe on. To make things easier, you can also enter the word any ; this will set the core server to accept remote probes connecting from any IP address. Note: If you use any , please make sure you write the word in lower case only! Any other variations will not be recognized! Make sure the IP address of the computer you will install a remote probe on is not listed in the Deny IPs field. For detailed information about these settings, please see Sy st em Administ rat ionProbes section.
1707
Step 3: Download and Install Remote Probe

From the computer you want to install a remote probe on, connect to the Ajax web interface 96 , download the setup file and install it. For detailed instructions, please see Inst all a PRTG Remot e Probe 58 section. Note: You cannot install a remote probe on a system already running a PRTG core installation.
1898
13.06.2013
At the end of the remote probe installation the PRTG Probe Administ rat or will be started (or you can start it manually from the Windows start menu later).
Step 4: Configure Remote Probe Connection

In the PRTG Probe Administ rat or 1857 on the Windows system you have installed the remote probe on, please configure the connection to the core server.
Remote Probe Settings in PRTG Probe Administrator
In the Connect ion t o PRTG Core Server section, you can then edit the following settings: Server: Enter the IP address or DNS name of the core server the remote probe will connect to. If Network Address Translation (NAT) is used, this must be the IP address that is externally visible, as the remote probe will connect from outside of your network. Port : Enter the port number the remote probe will connect to on the core server. This number must match the one set in Step 1 1896 . Probe Access Key and Confirm Access Key : Enter the access key the probe will send to the core server. You have saved this key in Step 2 1898 . This key has to match exactly the one shown in the web interface's probes settings, so a connection can be established. For detailed information about these settings, please see PRTG Probe Administ rat or section. Click the Ok button to confirm your settings and to start the probe service.
1857
13.06.2013
1899
Step 5: Approve New Probe and Start Monitoring

When a new probe connects to the core server for the first time, a new ToDo 139 will be created and the probe will show up as a new object in the device tree of your setup.
Approv e New Probe
Please click on Approve new probe to fully enable the probe. You have to do this once for every new probe. Once approved, PRTG automatically creates a set of sensors for the probe to ensure that bottle-necks on the probe will always be noticed. We recommend keeping these sensors. You can now create groups, devices and sensors for monitoring via the new probe. You can also discard the new probe by clicking Deny new probe. Note: When denying or removing a remote probe, this device's global ID (GID) will be entered to Deny GIDs in Probes Set t ings 1707 . Note: Denying the remote probe in the PRTG device tree does not uninstall the probe, but only denies access to the core server. The probe will continue to run on the target system until you uninstall it manually.
Debugging Probe Connection Problems

If you have trouble with the setup of remote probes please look at the probe's log files. The probe process writes log files with a file name in the format PRTG Probe Log (x).log . Please open the one with the most recent date. For a correct connection the probe log should look similar to this:
1900
13.06.2013
11.08.2012 16:15:15 PRTG Probe Server V12.3.2.5101 11.08.2012 16:15:15 Starting Probe on "WINXPVMWARE" 11.08.2012 16:15:15 Data Path: C:\documents and settings\All Users\a[...] 11.08.2012 16:15:15 Local IP: 0.0.0.0 11.08.2012 16:15:15 Core Server IP and Port: 10.0.2.167:23560 11.08.2012 16:15:15 Probe ID: -1 11.08.2012 16:17:01 Connected to 10.0.2.167:23560 11.08.2012 16:17:06 Login OK: Welcome to PRTG
If the connection fails, for example, due to an incorrect Access Key , or due to incorrect IP settings (see St ep 2 1898 ), you will see:
11.08.2012 16:31:02 Try to connect... 11.08.2012 16:31:02 Connected to 10.0.2.167:23560 11.08.2012 16:31:07 Login NOT OK: Access key not correct!
13.06.2013
1901
Part 12: Advanced Topics | 9 Failover Cluster Configuration
12.9
Failover Cluster Configuration

PRTG offers single failover clustering in all licenseseven using the freeware edition. A single failover cluster consists of two servers ("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 Failov er Cluster
For setting up a cluster you need two or more servers and there is one core installation 47 necessary on each of themwith different settings configured for each type of node. In return, you benefit from seamless high-available monitoring with automatic failover and/or multilocation monitoring. In a cluster, you can run: 1 Mast er Node On the master node, you set up your devices and configuration. Also notifications, reporting, and many other things are handled by the master node. Up t o 4 Failover Nodes You can install one, two, three, or four additional nodes for fail-safe, gapless monitoring. Each of these nodes can monitor the devices in your network independently, collecting their own monitoring data. The data can be reviewed in a summarized way, enabling you to compare monitoring data from different nodes. Note: During an outage of one node, you will see data gaps for the time of the outage on that node. However, data for that time span will still be available on all other cluster nodes.
Before Getting Started

Configuring a cluster with one failover node is the most common way to set up a seamless network monitoring with PRTG. You will need two servers running any Windows version (XP/2003 or later); your servers can be real hardware (recommended!) or virtual machines. Please make sure the following: Your servers must be up and running. Your servers must be similar in regard to the system performance and speed (CPU, RAM memory, etc.).
1902
08.10.2013
In a cluster setup, each of the cluster nodes will individually monitor the devices added to the Clust er Probe. This means that monitoring load will increase with every cluster node. Please make sure your devices and network can handle these additional requests. Often, a larger scanning interval for your entire monitoring is a good idea. For example, you could set a scanning interval of 5 minutes in the Root Group Set t ings 213 . We recommend installing PRTG on dedicated real-hardware systems for best performance. Please bear in mind that a server running a cluster node may in rare cases be rebooted automatically without notice (e.g. for special software updates). Both servers must be visible for each other through the network. Communication between the two servers must be possible in both directions. Please make sure that no software- or hardware firewall is blocking communication. All communication between nodes in the cluster is directed through one specific TCP port. You will define it during cluster setup (by default, it is TCP port 23570). A Failover Master will send notifications in case the Primary Master is not connected to the cluster. In order for mails to be delivered in this case, please make sure you configure the Not ificat ion Delivery 1702 settings in a way they can be used to deliver emails from your Failover Node as well (for example, using the option to set up a secondary Simple Mail Transfer Protocol (SMTP) server). Make your servers safe! From every cluster node, there is full access to all stored credentials as well as other configuration data and the monitoring results of the cluster. Also, PRTG software updates can be deployed through every node. So, please make sure you take security precautions to avoid security attacks (hackers, Trojans, etc.) You should secure every node server the same careful way as the master node server. Run the nodes in your cluster either on 32-bit or 64-bit Windows versions only. Avoid using both 32-bit and 64-bit versions in the same cluster, as this configuration is not supported and may result in an unstable system. Also, ZIP compression for the cluster communication will be disabled and you may encounter higher network traffic between your cluster nodes. If you run cluster nodes on Windows systems with different timezone settings and use Schedules 1687 to pause monitoring of defined sensors, schedules will apply at the local time of each node. Because of this, the overall status of a particular sensor will be shown as Paused every time the schedule matches a node's local system time. Please use the same timezone setting on each Windows with a cluster node in order to avoid this behavior.
Start Now!
Ready to get started? Please go to Failover Clust er St ep by St ep
1905
More
Knowledge Base: What's the Clustering Feature in PRTG? http://www.paessler.com/knowledgebase/en/topic/6403 Knowledge Base: What are the bandwidth requirements for running a PRTG Cluster? http://www.paessler.com/knowledgebase/en/topic/8223
08.10.2013
1903
Knowledge Base: What is a Failover Master and how does it behave? http://www.paessler.com/knowledgebase/en/topic/7663 Knowledge Base: I need help with my PRTG cluster configuration. Where do I find step-by-step instructions? http://www.paessler.com/knowledgebase/en/topic/41913 Knowledge Base: PRTG Cluster: How do I convert a (temporary) Failover Master node to be the Primary Master node? http://www.paessler.com/knowledgebase/en/topic/34853
1904
08.10.2013
Part 12: Advanced Topics | 9 Failover Cluster Configuration 1 Failover Cluster Step by Step
12.9.1 Failover Cluster Step by Step

This section will guide you through a step-by-step process to set up a failover cluster. Please follow these instructions carefully, in order to successfully integrate two or more PRTG installations into one failover cluster. Note: Before getting started, please make sure you've read the information in section Failover Clust er Configurat ion 1902 .
Step 1: Install Core Servers

We will start with setting up a single failover cluster, consisting of two PRTG core server installations, each running on an individual server. Please use your license key twice to install the PRTG core server on two different computers. If you already run an installation of PRTG, this will be your future Master Node. In this case, please install a second core server on another computer only. Make sure you use the same license key for both installations. Before you begin to set up a cluster, please make sure you run exactly the same PRTG version (build number) on all (future) nodes (install updates for existing installations, if necessary). Note: Once the cluster is established, any updates you install on one node will be deployed to all other cluster nodes automatically. For details about the installation process, please see Inst all a PRTG Core Server
47 .
Step 2: Configure Master Node

Decide which of your PRTG core server installations will be your future Master Node. If you already run an installation of PRTG in your network for some time, this should be your master, so your existing monitoring configuration is being kept. On the Master Node server, from the Start menu, open the PRTG Server Administ rat or program. In the Cluster tab, click on the following button: Creat e a PRTG Clust er... Start creating a cluster by clicking this button. The current PRTG core server will then be the Mast er Node of your cluster. After you click this button, please confirm converting this installation into a master node by clicking on the Yes button.
1842
27.11.2012
1905
Conv ert This Installation Into a Cluster Master Node
Enter a Clust er Port . This is the port on which the internal communication between the different cluster nodes is sent. Make sure connections between cluster nodes are possible on the selected port.
1906
27.11.2012
Enter or paste a Clust er Access Key . This is a unique access key. All nodes in a cluster have to be configured with the same cluster access key in order to join the cluster. Connection attempts with the wrong access key will be rejected. We recommend using the default value. Save the Clust er Access Key so you have it at hand when configuring your Failover Node (s). After confirming your settings you will be asked to restart Windows services. Please do so in order for your changes to take effect.
Step 3: Configure Failover Node

On the server that will be your Failover Node, from the Start menu, open the PRTG Server Administ rat or 1842 program. In the Cluster tab, click on the following button: Join a PRTG Clust er... Add this installation to an existing cluster which already has a Mast er Node, by clicking this button. The current PRTG core server will then be a Failover Node in the cluster. Note: This button is also available if you're currently running your PRTG installation in Clust er Mode: Mast er Node. This option will then change your master node to a failover node! After you click this button, please confirm converting this installation into a failover node by clicking on the Yes button.
27.11.2012
1907
Conv ert This Installation Into a Cluster Failov er Node
Enter the cluster's Mast er IP address/DNS name. It must be reachable from the machine running the failover node. Enter the other settings as defined in your Mast er Node's settings. Please make sure you use the same settings on all nodes in your cluster.
1908
27.11.2012
Enter a Clust er Port . This is the port on which the internal communication between the different cluster nodes is sent. Make sure connections between cluster nodes are possible on the selected port. Enter or paste a Clust er Access Key . This is a unique access key. All nodes in a cluster have to be configured with the same cluster access key in order to join the cluster. Connection attempts with the wrong access key will be rejected. After confirming your settings you will be asked to restart Windows services. Please do so in order for your changes to take effect.
Step 4: Confirm Failover Node

Now you need to confirm the new failover node by setting it to Act ive in the master node's settings. In a browser window, log into PRTGs web interface
96
of the Master Node server.
In the Sy st em Administ rat ionClust er 1709 settings, you will see your Master Node server in the first line of the cluster list and your Failover Node server below.
Sy stem Setup Cluster Settings
For the Failover Node, set the radio button for Node St at e to Act ive and Save the changes. The nodes will now connect and exchange configuration data. This may take a few minutes.
Step 5: Check Cluster Connection

In two browser windows, log into PRTGs web interfaces of both of your PRTG installations. Open the cluster status page in both windows by clicking on the narrow cluster information bars at the top of each window. You should see a cluster status with your two nodes in a Connect ed state after a few minutes.
27.11.2012
1909
PRTG Cluster Status
PRTG Cluster Status
Step 6: Trouble Shooting

Having any problems? If your nodes cannot connect, please see the Cluster Log entries on the PRTG St at usClust er St at us
1735
page of the web interface
the core server log file, a text file in the logs directory of your PRTG data folder (see Dat a St orage 1912 ). In the latest entries of these logs, you can see messages about any errors that might have occurred. These will give you hints on where to find a solution. If you encounter connection problems between the two cluster nodes, please make sure that no software- or hardware firewall is blocking communication on the cluster port defined during cluster setup. Communication between the nodes must be possible in both directions in order for the cluster to work properly.
Step 7: Done! Move Sensors to the Cluster Probe Now

Thats it. Youve now successfully set up your failover cluster. All devices that are created or moved under the Clust er Probe will be monitored by both servers. In order t o monit or y our exist ing configurat ion via all clust er nodes, on y our mast er node, please move y our groups, devices, and sensors from t he local probe t o t he clust er probe! Objects, including their settings, will then be transferred to all cluster nodes automatically.
1910
27.11.2012
Add More Failover Nodes

If you want to add an additional failover node to your cluster, you will need an additional license key for two and three failover nodes, and two additional license keys to run four failover nodes. Note: In a cluster, only core servers running on the same size of license 17 can be combined. For example, you can use several "PRTG Unlimited" licenses or several "PRTG 1000" licenses in one cluster. To add another failover node to your cluster, please set up a new PRTG core server installation on a new server, using an additional license key. Then proceed with St ep 3 1907 and following. Note: Use a second license key to set up both your second and third failover node, and use a third license key to set up your fourth failover node. The licenses "Site" and "Corporate" can be used to install an unlimited number of core servers. Each failover cluster is technically limited to five cluster nodes: As a maximum, you can run one master node and four failover nodes in one cluster.
More
Knowledge Base: My PRTG Cluster is messed up. How can I start over? http://www.paessler.com/knowledgebase/en/topic/41903
Advanced Topics
Act ive Direct ory Int egrat ion
1869
Applicat ion Programming Int erface (API) Definit ion
1871
1872
Channel Definit ions for xFlow, IPFIX , and Packet Sniffer Sensors Define IP Ranges Define Lookups
1878
1876
1879
Regular Expressions Add Remot e Probe
1886
1887
Failover Clust er Configurat ion Dat a St orage

1912
1902
Using Your Own SSL Cert ificat e Calculat ing Percent iles
1916
1914
27.11.2012
1911
Part 12: Advanced Topics | 10 Data Storage
12.10 Data Storage

PRTG stores the monitoring configuration, monitoring data, logs, ToDos, and reports as well as support and debug data into different folders on the core server or the system running a Remot e Probe 1887 . Additionally, there is data from PRTG in the program directory and the Windows registry. Data can be found in different locations. For a detailed information please see the article linked in the More 1913 section below.
PRTG Program Directory

32 bit systems:
%programfiles%\PRTG Network Monitor
64 bit systems:
%programfiles(x86)%\PRTG Network Monitor
Note: These are the default paths. If you specified another installation directory, you will find your data there.
PRTG Data Folder

%ALLUSERSPROFILE%\Application data\Paessler\PRTG Network Monitor
Note: This is the default path. If you specified a custom path for data storage, please look it up in the PRTG Server Administ rat or 1840 : Open this application and switch to the Core Server tab. You will find the path there.
Windows Registry
System settings on 32 bit systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Paessler\PRTG Network Monitor
System settings on 64 bit systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Paessler\PRTG Network Monitor
Enterprise Console settings:

HKEY_CURRENT_USER\Software\Paessler\PRTG Network Monitor\WinGUI
1912
27.11.2012
Part 12: Advanced Topics | 10 Data Storage
More
Knowledge Base: How PRTG Network Monitor Stores its Data http://www.paessler.com/knowledgebase/en/topic/463
27.11.2012
1913
Part 12: Advanced Topics | 11 Using Your Own SSL Certificate with PRTG's Web Server
12.11 Using Your Own SSL Certificate with PRTG's Web Server
This section will give you a brief overview on how to use your own trusted SSL certificate files with the PRTG web server.
What is SSL?
PRTG supports Secure Sockets Layer (SSL) to encrypt all data entered and shown in the Web Int erface 94 , in the Ent erprise Console 1744 , or in the Smart phone Apps 1801 . That ensures that no sensitive information can be intercepted when sending data between the PRTG core server and your client software. By default PRTG is already delivered with an SSL certificate so you can use secure connections to your PRTG core server. However, these certificate files are not signed by a valid authority, which is why browsers show an SSL Cert ificat e Warning 99 when you try to access the web interface. Despite this warning your connection is still encrypted successfully. To remove the browser warning you can obtain a certificate that is valid for your own domain name and signed by a valid authority. The certificate must be provided in the correct format and can then be copied to your PRTG program directory (see Dat a St orage 1912 ).
PRTG Needs PEM Encoded Format and Unencrypted Key

There are many different issuers for certificates, and there are different formats certificates can be provided in. PRTG needs three different files, named correctly, containing data in the expected encoding and format: prt g.crt : This is the certificate for your PRTG server. It has to be stored in PEM encoded format. prt g.key : This is the private key matching your server certificate. It has to be stored in PEM encoded format and may not be encrypted! Please make sure that you provide this file in decrypted format! The best way to check this is to open the file in a text editor. If you find a line containing the word "ENCRYPTED", the file still needs to be decrypted before you can use it with PRTG. Please decrypt using an SSL tool (e.g. OpenSSL) and your key password. root .pem: This is the public root certificate of your certificate's issuer. It has to be stored in PEM encoded format and must contain all necessary root certificates of your issuer in one file. If there is more than one PEM encoded root certificate, please use a text editor to copy all of them into a single file (the order does not matter). Once ready, copy these three files to the /cert sub folder of your PRTG program directory (please backup existing files) and restart your PRTG core server service (see PRTG Server Administ rat or 1853 ). Note: PRTG services won't restart if the files are not provided in exactly the expected format!
1914
09.10.2013
Part 12: Advanced Topics | 11 Using Your Own SSL Certificate with PRTG's Web Server
For detailed instructions and examples, installation descriptions for various certificates (including Wildcard certificates), as well as links to certificate tools and converters, please see the More 1915 section below.
More
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
09.10.2013
1915
Part 12: Advanced Topics | 12 Calculating Percentiles
12.12 Calculating Percentiles

Wikipedia describes a percentile as the value of a variable below which a certain percent of observations fall. Providers often use it in their billing models, e.g. when determining the used bandwidth. With percentile calculation, you can cut off an x percent of peak values from an amount of values. In PRTG, you can calculate percentiles when creating general reports (see Report s 1636 section), or creating historic data reports of a certain sensor (see Hist oric Dat a Report s 126 section). If you activate the Percent ile Result s option in your reports' settings, the according values will be added to the tables. You can customize the following settings: Percent ile: Enter the percentile number you want to calculate. If you choose, for example, to calculate the 95th percentile, enter "95" here and 5 % of peak values will be discarded. Percent ile Average: This is the averaging interval in seconds, which is used for percentile calculation. Default value is 300 which is equivalent to 5 minutes. Percent ile Mode: Choose between Discret e and Cont inuous. Continuous percentile interpolates between discrete values, whereas discrete percentile chooses the next smaller discrete value. Discret e percentile means that the value must be a member of the data set. For this kind of calculation you require a discrete distribution. The median of a discrete distribution can not be defined, as such, meaning that the 50th discrete percentile may not necessarily be the median if the value does not belong to an odd number of measurements. Discrete percentiles, as such, should not be used for billing applications. Cont inuous percentile basically means that the measurements are treated as a statistical population and the value is determined by interpolating a value when it isn't present. This means that values are interpolated between actual measurements that are varying around the "perfect" center of the measurements.
More
Knowledge Base: What are percentiles? http://www.paessler.com/knowledgebase/en/topic/9563
1916
08.10.2013
Part 13
Appendix
27.11.2012
1917
Part 13: Appendix |
13
Appendix
Please find further information in the following sections. Glossary
1919
List of Abbreviat ions
1923
Support and Troubleshoot ing Legal Not ices

1927
1926
1918
27.11.2012
Part 13: Appendix | 1 Glossary
13.1
Glossary
This section explains special words used in the context of PRTG Network Monitor. Note: Here, only explanations are given. For information on where to find detailed instructions for a specific key word, please see the Index section.
Channel
The monitoring data of a sensor 1922 is shown in sensor channels. For example, for sensors that measure network traffic, there is one channel each for traffic in and traffic out. You can set various triggers for each channel, enabling you to set sensor status changes or notifications based on the monitoring data received.
Cluster
PRTG can be configured as a failover cluster for fail-safe monitoring. In a cluster, one or more core servers 1919 work together in one configuration. Every node can monitor all devices in a network for gapless monitoring, additionally enabling you to compare monitoring results measured from different perspectives.
Cluster Node
Sometimes used as synonym for Node
1921
Cluster Probe
When running PRTG in cluster mode, a cluster probe is automatically created. All objects 1921 created on the cluster probe, or below it in the device tree 1920 , are monitored by all nodes in the cluster. Create or move objects 1921 there to monitor them fail-safely. If one node fails, the other nodes will continue to monitor them. You can add groups 1920 and devices 1920 to the probe. On a PRTG installation, the cluster probe runs as part of this installation's local probe 1920 . Remote probes 1921 cannot be connected to a cluster probe, but only to one local probe of one PRTG installation.
Core Server
The central unit of PRTG. It receives monitoring data from the probe(s) 1921 and handles reporting and notifications, provides the web server for the user interfaces, and many other things. In a cluster 1919 , one core server is installed on every node.
Dashboard
In the Home menu of the web interface there are several pre-configured dashboards available which show a quick overview of the overall status of your monitoring configuration. Custom dashboards can be created using the Maps 1921 function.
27.11.2012
1919
Device
A device in PRTG represents a physical device in the network. For an easily understandable tree structure, you usually create one PRTG device for each physical device you want to monitor (exceptions apply to some sensors that can only be created on the local probe 1920 device, and for sensor types that are not bound to a certain device, such as HTTP sensors, which are also usually created on the local probe). You can add one or more sensors 1922 on every device.
Device Tree
PRTG's configuration is represented in a hierarchical tree structure, called device tree, containing all objects 1921 . While building the tree, you can relate to your network's topology to make your monitoring setup easy to understand.
Failover Master (Node)

If the primary master 1921 node fails, a failover node 1920 is promoted to current failover master and takes over the master role until the primary master node re-joins the cluster 1919 .
Failover Node
In a cluster 1919 a failover node monitors all sensors 1922 on the cluster probe 1919 , providing monitoring data for the core server 1919 . Additionally, it serves as a backup in case the master node 1921 fails.
Group
A group is an organizational unit in your PRTG tree structure that helps to arrange your devices. To existing groups, you can add devices, or additional sub-groups. This way you can model your physical network's topology within the PRTG configuration.
Library
Libraries are a way to show parts of your device tree 1920 in a different layout or with different filters enabled. There is an editor available that allows creating libraries directly in your browser.
Local Probe
The local probe is installed together with the core server 1919 . All objects 1921 created on the local probe, or below it in the device tree 1920 , are monitored by the local core system. You can add groups 1920 and devices 1920 to the probe.
1920
27.11.2012
Map
Maps (sometimes referred to as "dashboard 1919 ") are a way to present monitoring the way you want to arrange it. There is an editor available that allows creating maps directly in your browser.
Master Node
In a cluster 1919 , the master node controls the settings and cluster management. It also takes over notifications. All changes to the monitoring configuration are made on the master node.
Node
In a cluster 1919 there is one master node 1921 and one or more failover nodes 1920 . On each node, one PRTG core server 1919 installation is running independently. All nodes are connected to each other, exchanging configuration and monitoring data.
Object
All different items in the device tree 1920 are generally referred to as objects. An object can be a probe 1921 , a group 1920 , a device 1920 , or a sensor 1922 .
Primary Master (Node)

The primary master node in a cluster 1919 is the node 1921 that is master by configuration. Only if it fails, one of the failover nodes 1920 becomes failover master 1920 and takes over the master role until the primary master node re-joins the cluster.
Probe
On a probe, the actual monitoring takes place. A probe can run as local probe 1920 on the local system where the core server 1919 is installed. There are also cluster probes 1919 and remote probes 1921 .
Remote Probe
A remote probe is a small piece of software installed on a computer in the local or remote network. It scans the network from there and sends monitoring results to the core server 1919 . Once the connection is established, the remote probe is shown in the PRTG tree structure. All objects 1921 created on the remote probe, or below it in the device tree 1920 , are monitored by the remote system running the remote probe. You can add groups 1920 and devices 1920 to the probe. In cluster 1919 , remote probes can only be connected to the master node 1921 , not to one of the failover nodes 1920 .
27.11.2012
1921
Sensor
A sensor monitors one aspect of a device 1920 . For example, monitoring if a device responds to a Ping request is done by one sensor. Monitoring the traffic of one ethernet port of a router device is done by another sensor. For monitoring the CPU load of the local system yet another sensor is set up, and so on. A sensor's data is shown in channels 1919 .
Sensor Tree
Sometimes used as synonym for device tree
1920
ToDo
ToDos are created by the system and contain important messages or action steps to take for the administrator. Every ToDo should be acknowledged. You can access the list of ToDos from the main menu.
xFlow
Paessler designates all kinds of flow protocols as xFlow. Currently, PRTG supports NetFlow V5 and V9, sFlow V5, and jFlow V5.
1922
27.11.2012
Part 13: Appendix | 2 List of Abbreviations
13.2
List of Abbreviations
In the following, please find a list of the most common abbreviations used in this documentation. ADO: ActiveX Data Objects (ADO) ADSL: Asymmetric Digital Subscriber Line (ADSL) AJAX: Asynchronous Java Script and XML (AJAX) API: Application Programming Interface (API) CoS: Class of Service (CoS) CSV: Comma Seperated Values (CSV) DHCP: Dynamic Host Configuration Protocol (DHCP) DMZ: Demilitarized Zone (DMZ) DSCP: Differentiated Services Code Point (DSCP) DNS: Domain Name Service (DNS) GUI: Graphical User Interface (GUI) GUID: Globally Unique Identifier (GUID) HTTP: Hypertext Transfer Protocol (HTTP) ICMP: Internet Control Message Protocol (ICMP) IMAP: Internet Message Access Protocol (IMAP) IPsec: Internet Protocol Security (IPsec) JSON: JavaScript Object Notation (JSON) LAN: Local Area Network (LAN) LDAP: Lightweight Directory Access Protocol (LDAP) MoID: Managed Object ID (MoID) MIB: Management Information Base (MIB)
05.12.2012
1923
MOS: Mean Opinion Score (MOS) NAT: Network Address Translation (NAT) NTLM: NT LAN Manager (NTLM) PDF: Portable Document Format (PDF) PDV: Packet Delay Variation (PDV) POP3: Post Office Protocol version 3 (POP3) QoS: Quality of Service (QoS) RADIUS: Remote Authentication Dial-In User Service (RADIUS) REST: Representational State Transfer (REST) RMON: Remote Monitoring (RMON) RPC: Remote Procedure Call (RPC) SASL: Simple Authentication and Security Layer (SASL) SLA: Service Level Agreement (SLA) S.M.A.R.T.: Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) SMB: Server Message Block (SMB) SMTP: Simple Mail Transfer Protocol (SMTP) SNMP: Simple Network Management Protocol (SNMP) SNTP: Simple Network Time Protocol (SNTP) SOAP: Simple Object Access Protocol (SOAP) SPAN: Switched Port Analyzer (SPAN) SQL: Structured Query Language (SQL) SSH: Secure Shell (SSH) SSL: Secure Sockets Layer (SSL) TFTP: Trivial File Transfer Protocol (TFTP)
1924
05.12.2012
UNC: Uniform Naming Convention (UNC) UPnP: Universal Plug and Play (UPnP) UUID: Universally Unique Identifier (UUID) VoIP: Voice over IP (VoIP) VPN: Virtual Private Network (VPN) WAN: Wide Area Network (WAN) WBEM: Web-Based Enterprise Management (WBEM) WMI: Windows Management Instrumentation (WMI) WQL: Windows Management Instrumentation Query Language (WQL) WSUS: Windows Server Update Services (WSUS) XML: Extensible Markup Language (XML)
05.12.2012
1925
Part 13: Appendix | 3 Support and Troubleshooting
13.3
Support and Troubleshooting

Need help with PRTG? There are several ways to get support and trouble shooting.
Video Tutorials
A video says more than a thousand wordswatch tutorials for PRTG from Paessler and other PRTG users. http://www.paessler.com/support/video_tutorials
Paessler Knowledge Base

In the Knowledge Base you can search in hundreds of articles about PRTG. You can post your own questions and answers, too! http://www.paessler.com/knowledgebase/
Open a Support Ticket

Users that have purchased a license can open support tickets which will usually be answered by Paessler's staff in less than 24 hours on business days. https://service.paessler.com/en/openticket/
1926
27.11.2012
Part 13: Appendix | 4 Legal Notices
13.4
Legal Notices
Build using Indy Internet Direct (http://www.indyproject.org/). This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). Uses the net-SNMP library, see "netsnmp-license.txt". Uses the DelphiZip library distributed under the GNU LESSER GENERAL PUBLIC LICENSE (http://www.delphizip.net/). Uses FastMM (http://sourceforge.net/ projects/fastmm/), TPLockBox (http://sourceforge.net/projects/tplockbox) and Delphi Chromium Embedded (http://code.google.com/p/delphichromiumembedded/) under the Mozilla Public License 1.1 (MPL 1.1, available from http://www.mozilla.org/MPL/MPL-1.1.html). Soundfiles from http://www.soundsnap.com. Uses Public Domain regional maps from the "CIA World Factbook" webpage of the CIA (https://www.cia.gov/library/publications/the-worldfactbook/docs/refmaps.html). Uses the "wkhtmltopdf" (http://code.google.com/p/ wkhtmltopdf/) library distributed under the GNU LESSER GENERAL PUBLIC LICENSE (see wkhtmltopdf_lgpl-3.0.txt). Icons from http://www.androidicons.com. All trademarks and names mentioned herein belong to their respective owners. Last manual export: Donnerstag, 24. Oktober 2013 13:16:06
27.11.2012
1927
Index
Index
-22 days tab 118
Basic Concepts 72 Billing Tool 1737 Bulk edit 1595
-CCertificate Trusted SSL 1914 Change Trigger 1573 Check Now Context Menu 148 Chrome Desktop Notifications 1739 Clone Context Menu 148 Cluster Basic Concept 76 Maintenance Mode 1723 Status 1723 Cluster Connection 1709 Configure Cluster 52, 1709 Dependencies 85 Device 261 Geographical Map 1603 Group 242 License Key 53 Map 1655 Notification 1609, 1678 Notification Delivery 1702 Notification Trigger 1573 Object Arrangement 1591 Probe 58, 227, 1707, 1857 PRTG Server 1837 Reboot (automatic) 1857 Report 1636 Root Group 213 Schedule 1687 Sensor 278 Sensor Channel 1566 System 1671, 1691 User Account 1673, 1710 User Group 1715 Website 1691 Continuous (Percentiles) 1916 Create Device Template Context Menu 148 Create Objects 193 1929
-330 days tab 118 365 days tab 118
-AAccount Settings 1673, 1710 Account Type 1673 Activation 56 Add Device 200 Group 194 Sensor 209 Ajax Web Interface 94 Alarm Acknowledge 1763 List 1763 Alarms 165 Android App PRTGdroid 1801 API 1871 Architecture Basic Concept 73 Audible Alarms 1673 Auto-Discovery Quick Start 32 Settings 181 Automatic Folding 1673 Refresh 1673 Restart Options (Probe System) Automatic Software Update 1732 Averaging 126, 1636
1857
-BBandwidth Monitoring Overview 1823
Index
-DData Folder 1912 Reporting 88 Storage 1912 Data Purging 1691 Date Format 1673 Decimal Places 1566 Dependencies 85 Device add 200 arrange 1591 clone 1592 Multi-Edit 1595 Template 1600 Device Tools Context Menu 148 Devices 165 Discrete (Percentiles) 1916 Down 115 Down (Acknowledged) 115 Down (Partial) 115 Download 41 Downloads Add-Ons 1737 Apps for iOS & Android 1737 Billing Tool 1737 Google Chrome 1737 Remote Probe Installer 1737 Windows Enterprise Console 1737
-FFavorites Context Menu 148 Flow Channel Definitions 1876 Filter Rules 1872 IP Ranges 1878 Technology 1820 Toplists 1586
-GGeneral Web Interface Layout 102 Geo Map Type 1691 Geographical Map 1603 Google Chrome Desktop Notifications 1739 Code 1563 Maps 1603 Graph Settings 1691 Type 1691 Group add 194 arrange 1591 clone 1592
-HHash 1673 Header 102 Help Center 165 Historic Data Context Menu 148 Home 165 Homepage 1673 HTML GUI 1797 HTTP Proxy 1702
-EEdit Context Menu 148 Email Address 1673 Email Round Trip Technology 1829 Email Templates 1691 Enterprise Console 1744 Error Limit 1566 Escalation 1573
-I ICMP Echo 726 Inheritance of Settings Install Core Server 47
82
1930
Index
Install Download 41 Enterprise Console Uninstall 67 Update 43 Intervals 1691 iPhone App iPRTG 1801
-N63 None 115 Notification 1609, 1678 Delivery 1702 Escalation 1573 Multi-Edit 1595 Trigger 1573 Notifications Chrome Desktop 1739 Notifying 87
-LLatency 1573 Libraries 1619 Context Menus 1635 Management 1626 Multi-Edit 1595 Node 1629 Settings 1629 Limits Error 1566 Warning 1566 Line Color 1566 Width 1566 Live Data tab 118 Login Name 1673 Logout 165 Logs 165 Lookups 1879
-OObject Hierarchy 78 Off Notification 1573 OK 115 On Notification 1573 Overview tab 118
-PPacket Sniffer Channel Definitions 1876 IP Ranges 1878 Packet Sniffing Filter Rules 1872 Technology 1818 Toplists 1586 Passhash 1673 Password 1673 Pause Context Menu 148 Paused 115 Peak Filter (Spike Filter) 1566 Percentile 1916 Percentiles 126, 1636 Performance Strategy 1691 Priority Context Menu 148 Probe arrange 1591 Probe Administrator 1857 Probe Connection 1707 Probes IP Ranges 1878 1931
-M Maintenance Mode 1723 Management Tab 211 Maps 165, 1655 audible alert 1660 automatic rotation 1655 Designer 1660 edit 1660 Line Color 1660 Multi-Edit 1595 Mini HTML 1797 Monitoring Data 1912 Move Context Menu 148 Multi-Edit 1595
Index
-RRefresh 165, 1673 Registry Data 1912 Remote Probe 1887 Remote Registry 1322 Rename Context Menu 148 Reports 165, 1636 Data 88 Multi-Edit 1595 Restart Options (Probe System)
1857
SMS Delivery 1702 SMTP Delivery 1702 SNMP Lookups 1879 Technology 1809 Sort Alphabetically Context Menu 148 Sound Alarms 1673 Speed Trigger 1573 Spike Filter 1566 SSL 1914 State Trigger 1573 System Status 1723
-SSchedule 1687 Multi-Edit 1595 Scheduled Reboot (Probe System) Scheduling 86 Search Box 165 Send Link by email Context Menu 148 Sensor add 209 arrange 1591 Behavior 115 Channel Settings 1566 clone 1592 compare 123 Multi-Edit 1595 Notification Trigger 1573 Settings 278 Status 115 Type 279 Sensors 165 Server Administrator 1837 Session Expiry 1691 Settings Context Menu 148 Setup 165 Shift 1660 SMART 1445 Smart Phone Apps iPRTG 1801 PRTGdroid 1801 1932
-TTags 84 Threshold Trigger 1573 Timezone 1673 ToDo Email Address 1691 ToDos 165 Toplists 1586 Tree View Zoom 102 Trigger Change 1573 Latency 1573 Speed 1573 State 1573 Threshold 1573 Volume 1573
1857
-U Unknown 115 Unusual 115 Unusual Detection 1691 Update 43 Uptime Threshold 1691 User Access Rights 89 Username 1673
-VValue Mapping Lookups 1879
Index
Vertical Axis Scaling 1566 VoIP Technology 1825 Volume Trigger 1573
-WWarning 115 Warning Limit 1566 Web Interface 94 Web Server Certificate 1914 IP Address 1691 Port 1691 Windows GUI 1744 Menu Structure 1786 Menu Tab 1751 Options 1779 WMI Technology 1813
1933
Last change to this manual (YYYY-MM-DD): 24.10.2013
1934
30.12.1899

PRTG Manual

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PRTG Manual

Încărcat de

Drepturi de autor:

Formate disponibile

PRTG Net work Monit or User Manual 2013 Paessler AG All rights reserved.

Part 2 Quick Start Guide

Part 3 Installing the Software

Part 4 Understanding Basic Concepts

Part 5 Ajax Web InterfaceBasic Procedures

Part 6 Ajax Web InterfaceDevice and Sensor Setup

Part 7 Ajax Web InterfaceAdvanced Procedures

Part 8 Enterprise Console

Part 9 Other User Interfaces

Part 10 Sensor Technologies

1820 1823 1825 1829 1831 1832 1833

Part 11 Sy stem Administration Tools

Part 12 Advanced Topics

Part 1: Welcome to PRTG Network Monitor |

Welcome to PRTG Network Monitor

Why Network Monitoring is Important

Monitoring Networks with PRTG Network Monitor

Part 1: Welcome to PRTG Network Monitor | 1 About this Document

About this Document

section. For more

Part 1: Welcome to PRTG Network Monitor | 2 Key Features

What PRTG Can Be Used For

What PRTG Includes

Part 1: Welcome to PRTG Network Monitor | 2 Key Features

Part 1: Welcome to PRTG Network Monitor | 3 New in This Version

New in This Version

Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses

Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses

Part 1: Welcome to PRTG Network Monitor | 5 System Requirements

Planning an Installation With Hundreds of Sensors or More?

Part 1: Welcome to PRTG Network Monitor | 5 System Requirements

Detailed Sy stem Requirements

Supported Operating Systems

Large Inst allat ion A

DELL Alienware Intel Core2 QuadCore 2.6 GHz 8 GB

Windows 7 64-Bit 20,000 SNMP 100 Other 400 switches 48 ports

Inst allat ion Corresponds To

400 switches 48 ports

Scanning Int erval

Average CPU Load While Monit oring*

Average CPU Load While Generat ing Report s*

Average Memory Used

Average Dat a Writ t en t o Disk Per Year

Average Net work Load 80 kbit/s

Running PRTG on Virtual Machines

VMware Server 2.0

XEN Server 5.0

Parallels Virtuozzo Containers

Cloud Hosting Platforms (Amazon EC2, TheRackspaceCloud, and others)

regarding running PRTG on VMware.

Web Browser Requirements

Requirements for Monitored Devices

Requirements for the Enterprise Console

Requirements for Mobile Web GUI

Requirements for Smart Phones

Part 2: Quick Start Guide |

Quick Start Guide

Welc ome Sc reen

Quick Start GuideTopics

Part 2: Quick Start Guide | 1 ONEDownload, Installation, and First Login

ONEDownload, Installation, and First Login

PRTG Download at Paessler Website

Part 2: Quick Start Guide | 1 ONEDownload, Installation, and First Login