Prt g Manual

PRTG Manual
© 2024 Paessler AG
All rights reserved. No parts of this work may be reproduced in any form or by any means—graphic, electronic, or
mechanical, including photocopying, recording, taping, or information storage and retrieval systems—without the
written permission of the publisher.
Products that are referred to in this document may be either trademarks and/or registered trademarks of the
respective owners. The publisher and the author make no claim to these trademarks.
While every precaution has been taken in the preparation of this document, the publisher and the author assume
no responsibility for errors or omissions, or for damages resulting from the use of information contained in this
document or from the use of programs and source code that may accompany it. In no event shall the publisher and
the author be liable for any loss of profit or any other commercial damage caused or alleged to have been caused
directly or indirectly by this document.
Printed: May 2024 in Nuremberg

Contents
Part 1 Welcome to PRTG ......................................................................................................... 13
1.1 About this Document ..................................................................................................... 16

1.2 Key Features ................................................................................................................ 17
1.3 New in this Version ....................................................................................................... 20
1.4 Available Licenses ......................................................................................................... 21
1.5 System Requirements ................................................................................................... 23
1.6 Introduction: Monitoring with PRTG ................................................................................. 34
Part 2 Quick Start Guide .......................................................................................................... 38
2.1 Step 1: Download, Installation, and First Login ................................................................. 40

2.2 Step 2: Smart Setup ...................................................................................................... 42
Part 3 Using PRTG Hosted Monitor ........................................................................................... 49
3.1 Create a PRTG Hosted Monitor Instance ......................................................................... 51

3.2 Manage a PRTG Hosted Monitor Subscription ................................................................. 64
3.3 Use Multi-Factor Authentication with PRTG Hosted Monitor .............................................. 82
Part 4 Installing the Software ..................................................................................................... 92
4.1 Download PRTG ............................................................................................................ 94

4.2 Update From Previous Versions ...................................................................................... 95
4.3 Install a PRTG Core Server ............................................................................................. 97
4.4 Install a Cluster ........................................................................................................... 104
4.5 Enter a License Key .................................................................................................... 105
4.6 Activate the Product .................................................................................................... 107
4.7 Install a Remote Probe ................................................................................................. 109
4.8 Uninstall PRTG Products ............................................................................................. 122
Part 5 Understanding Basic Concepts ...................................................................................... 125
5.1 Architecture and User Interfaces ................................................................................... 127

5.2 Failover Cluster ........................................................................................................... 132
5.3 Object Hierarchy ......................................................................................................... 136
5.4 Inheritance of Settings ................................................................................................. 140
5.5 Tags ........................................................................................................................... 142
5.6 Dependencies ............................................................................................................. 144
5.7 Scheduling .................................................................................................................. 145
5.8 Notifying ..................................................................................................................... 146
5.9 Access Rights Management ......................................................................................... 149
5.10 Data Reporting ............................................................................................................ 153
5.11 IPv6 Support ............................................................................................................... 154
Part 6 Basic Procedures ......................................................................................................... 155
6.1 Login .......................................................................................................................... 157

6.2 Welcome Page ........................................................................................................... 161
6.2.1 Customer Service .................................................................................................. 165
3
6.3 General Layout ............................................................................................................ 168
6.4 Sensor States ............................................................................................................. 184
6.5 Historic Data Reports ................................................................................................... 188
6.6 Similar Sensors ........................................................................................................... 195
6.7 Recommended Sensors ............................................................................................... 200
6.8 Object Settings ........................................................................................................... 204
6.9 Alarms ....................................................................................................................... 205
6.10 System Information ...................................................................................................... 208
6.11 Logs ........................................................................................................................... 213
6.12 Tickets ....................................................................................................................... 216
6.13 Working with Table Lists .............................................................................................. 221
6.14 Object Selector ........................................................................................................... 225
6.15 Priority and Favorites ................................................................................................... 227
6.16 Pause ........................................................................................................................ 230
6.17 Context Menus ............................................................................................................ 232
6.18 Hover Popup ............................................................................................................... 251
6.19 Main Menu Structure ................................................................................................... 253
Part 7 Device and Sensor Setup .............................................................................................. 268
7.1 Auto-Discovery ............................................................................................................ 270

7.2 Create Objects Manually .............................................................................................. 273
7.2.1 Add an Auto-Discovery Group ................................................................................. 274
7.2.2 Add a Group ......................................................................................................... 329
7.2.3 Add a Device ........................................................................................................ 379
7.2.4 Add a Sensor ........................................................................................................ 430
7.3 Manage Device Tree .................................................................................................... 434
7.4 Root Group Settings .................................................................................................... 436
7.5 Probe Settings ............................................................................................................ 474
7.6 Group Settings ............................................................................................................ 541
7.7 Device Settings ........................................................................................................... 612
7.8 Sensor Settings .......................................................................................................... 682
7.8.1 Active Directory Replication Errors Sensor ............................................................... 684
7.8.2 ADO SQL v2 Sensor .............................................................................................. 690
7.8.3 Application Server Health (Autonomous) Sensor ....................................................... 703
7.8.4 AWS Alarm v2 Sensor ........................................................................................... 708
7.8.5 AWS Cost Sensor ................................................................................................. 714
7.8.6 AWS EBS v2 Sensor ............................................................................................. 722
7.8.7 AWS EC2 v2 Sensor ............................................................................................. 729
7.8.8 AWS ELB v2 Sensor ............................................................................................. 736
7.8.9 AWS RDS v2 Sensor ............................................................................................. 743
7.8.10 Beckhoff IPC System Health Sensor ....................................................................... 750
7.8.11 Business Process Sensor ...................................................................................... 755
7.8.12 Cisco IP SLA Sensor ............................................................................................. 763
7.8.13 Cisco Meraki License Sensor ................................................................................. 769
7.8.14 Cisco Meraki Network Health Sensor ...................................................................... 774
7.8.15 Citrix XenServer Host Sensor .................................................................................. 780
7.8.16 Citrix XenServer Virtual Machine Sensor .................................................................. 786
7.8.17 Cloud HTTP v2 Sensor ........................................................................................... 792
7.8.18 Cloud Ping v2 Sensor ............................................................................................ 801
7.8.19 Cluster Health Sensor ............................................................................................ 809
7.8.20 Common SaaS Sensor .......................................................................................... 813
7.8.21 Core Health Sensor ............................................................................................... 818
4
7.8.22 Core Health (Autonomous) Sensor .......................................................................... 824
7.8.23 Dell EMC Unity Enclosure Health v2 Sensor ............................................................ 830
7.8.24 Dell EMC Unity File System v2 Sensor ................................................................... 836
7.8.25 Dell EMC Unity Storage Capacity v2 Sensor ............................................................ 841
7.8.26 Dell EMC Unity Storage LUN v2 Sensor .................................................................. 846
7.8.27 Dell EMC Unity Storage Pool v2 Sensor .................................................................. 851
7.8.28 Dell EMC Unity VMware Datastore v2 Sensor .......................................................... 857
7.8.29 Dell PowerVault MDi Logical Disk Sensor ................................................................ 862
7.8.30 Dell PowerVault MDi Physical Disk Sensor ............................................................. 867
7.8.31 DHCP Sensor ....................................................................................................... 872
7.8.32 DICOM Bandwidth Sensor ...................................................................................... 879
7.8.33 DICOM C-Echo Sensor .......................................................................................... 885
7.8.34 DICOM Query/Retrieve Sensor ............................................................................... 891
7.8.35 DNS v2 Sensor ..................................................................................................... 898
7.8.36 Docker Container Status Sensor ............................................................................. 904
7.8.37 Enterprise Virtual Array Sensor .............................................................................. 910
7.8.38 Event Log (Windows API) Sensor ........................................................................... 915
7.8.39 Exchange Backup (PowerShell) Sensor .................................................................. 924
7.8.40 Exchange Database (PowerShell) Sensor ................................................................ 930
7.8.41 Exchange Database DAG (PowerShell) Sensor ........................................................ 936
7.8.42 Exchange Mail Queue (PowerShell) Sensor ............................................................. 943
7.8.43 Exchange Mailbox (PowerShell) Sensor .................................................................. 949
7.8.44 Exchange Public Folder (PowerShell) Sensor .......................................................... 955
7.8.45 EXE/Script Sensor ................................................................................................ 961
7.8.46 EXE/Script Advanced Sensor ................................................................................. 971
7.8.47 File Sensor ........................................................................................................... 980
7.8.48 File Content Sensor ............................................................................................... 986
7.8.49 Folder Sensor ....................................................................................................... 993
7.8.50 FortiGate System Statistics Sensor ...................................................................... 1000
7.8.51 FortiGate VPN Overview Sensor ............................................................................ 1005
7.8.52 FTP Sensor ........................................................................................................ 1010
7.8.53 FTP Server File Count Sensor ............................................................................... 1016
7.8.54 HL7 Sensor ......................................................................................................... 1023
7.8.55 HPE 3PAR Common Provisioning Group Sensor .................................................... 1029
7.8.56 HPE 3PAR Drive Enclosure Sensor ....................................................................... 1035
7.8.57 HPE 3PAR Virtual Volume Sensor ........................................................................ 1041
7.8.58 HTTP Sensor ...................................................................................................... 1047
7.8.59 HTTP v2 Sensor .................................................................................................. 1054
7.8.60 HTTP Advanced Sensor ....................................................................................... 1061
7.8.61 HTTP Apache ModStatus PerfStats Sensor ........................................................... 1074
7.8.62 HTTP Apache ModStatus Totals Sensor ................................................................ 1080
7.8.63 HTTP Content Sensor .......................................................................................... 1086
7.8.64 HTTP Data Advanced Sensor ................................................................................ 1094
7.8.65 HTTP Full Web Page Sensor ................................................................................ 1103
7.8.66 HTTP IoT Push Data Advanced Sensor .................................................................. 1111
7.8.67 HTTP Push Count Sensor .................................................................................... 1118
7.8.68 HTTP Push Data Sensor ...................................................................................... 1124
7.8.69 HTTP Push Data Advanced Sensor ....................................................................... 1132
7.8.70 HTTP Transaction Sensor ..................................................................................... 1140
7.8.71 HTTP XML/REST Value Sensor ............................................................................ 1151
7.8.72 Hyper-V Cluster Shared Volume Disk Free Sensor ................................................. 1162
7.8.73 Hyper-V Host Server Sensor ................................................................................. 1168
7.8.74 Hyper-V Virtual Machine Sensor ........................................................................... 1173
7.8.75 Hyper-V Virtual Network Adapter Sensor ............................................................... 1179
7.8.76 Hyper-V Virtual Storage Device Sensor .................................................................. 1185
5
7.8.77 IMAP Sensor ...................................................................................................... 1191
7.8.78 IP on DNS Blacklist Sensor .................................................................................. 1204
7.8.79 IPFIX Sensor ....................................................................................................... 1209
7.8.80 IPFIX (Custom) Sensor ......................................................................................... 1218
7.8.81 IPMI System Health Sensor ................................................................................. 1226
7.8.82 jFlow v5 Sensor ................................................................................................... 1231
7.8.83 jFlow v5 (Custom) Sensor ..................................................................................... 1241
7.8.84 LDAP Sensor ...................................................................................................... 1250
7.8.85 Local Folder Sensor ............................................................................................. 1255
7.8.86 Microsoft 365 Mailbox Sensor ............................................................................... 1262
7.8.87 Microsoft 365 Service Status Sensor ..................................................................... 1272
7.8.88 Microsoft 365 Service Status Advanced Sensor ...................................................... 1277
7.8.89 Microsoft Azure SQL Database Sensor ................................................................. 1282
7.8.90 Microsoft Azure Storage Account Sensor .............................................................. 1289
7.8.91 Microsoft Azure Subscription Cost Sensor ............................................................. 1295
7.8.92 Microsoft Azure Virtual Machine Sensor ................................................................ 1301
7.8.93 Microsoft SQL v2 Sensor ...................................................................................... 1307
7.8.94 Modbus RTU Custom Sensor ............................................................................... 1320
7.8.95 Modbus TCP Custom Sensor ............................................................................... 1329
7.8.96 MQTT Round Trip Sensor ..................................................................................... 1337
7.8.97 MQTT Statistics Sensor ....................................................................................... 1342
7.8.98 MQTT Subscribe Custom Sensor .......................................................................... 1347
7.8.99 Multi-Platform Probe Connection Health (Autonomous) Sensor (BETA) ..................... 1354
7.8.100 Multi-Platform Probe Health Sensor ....................................................................... 1358
7.8.101 MySQL v2 Sensor ............................................................................................... 1363
7.8.102 NetApp Aggregate Sensor .................................................................................... 1376
7.8.103 NetApp Aggregate v2 Sensor ................................................................................ 1383
7.8.104 NetApp I/O Sensor .............................................................................................. 1389
7.8.105 NetApp I/O v2 Sensor .......................................................................................... 1397
7.8.106 NetApp LIF Sensor .............................................................................................. 1403
7.8.107 NetApp LIF v2 Sensor .......................................................................................... 1410
7.8.108 NetApp LUN Sensor ............................................................................................ 1416
7.8.109 NetApp LUN v2 Sensor ........................................................................................ 1423
7.8.110 NetApp NIC Sensor ............................................................................................. 1429
7.8.111 NetApp NIC v2 Sensor ......................................................................................... 1436
7.8.112 NetApp Physical Disk Sensor ............................................................................... 1442
7.8.113 NetApp Physical Disk v2 Sensor ........................................................................... 1449
7.8.114 NetApp SnapMirror Sensor ................................................................................... 1455
7.8.115 NetApp SnapMirror v2 Sensor ............................................................................... 1462
7.8.116 NetApp System Health Sensor ............................................................................. 1468
7.8.117 NetApp System Health v2 Sensor ......................................................................... 1476
7.8.118 NetApp Volume Sensor ........................................................................................ 1483
7.8.119 NetApp Volume v2 Sensor .................................................................................... 1490
7.8.120 NetFlow v5 Sensor ............................................................................................... 1497
7.8.121 NetFlow v5 (Custom) Sensor ................................................................................ 1507
7.8.122 NetFlow v9 Sensor ............................................................................................... 1516
7.8.123 NetFlow v9 (Custom) Sensor ................................................................................ 1526
7.8.124 Network Share Sensor ......................................................................................... 1535
7.8.125 OPC UA Certificate Sensor .................................................................................. 1542
7.8.126 OPC UA Custom Sensor ...................................................................................... 1547
7.8.127 OPC UA Server Status Sensor ............................................................................. 1553
7.8.128 Oracle SQL v2 Sensor ......................................................................................... 1558
7.8.129 Oracle Tablespace Sensor ................................................................................... 1571
7.8.130 Packet Sniffer Sensor .......................................................................................... 1578
7.8.131 Packet Sniffer (Custom) Sensor ............................................................................ 1586
6
7.8.132 PerfCounter Custom Sensor ................................................................................. 1595
7.8.133 PerfCounter IIS Application Pool Sensor ................................................................ 1601
7.8.134 Ping Sensor ........................................................................................................ 1606
7.8.135 Ping v2 Sensor .................................................................................................... 1612
7.8.136 Ping Jitter Sensor ................................................................................................ 1618
7.8.137 POP3 Sensor ...................................................................................................... 1623
7.8.138 Port Sensor ........................................................................................................ 1630
7.8.139 Port v2 Sensor (BETA) ......................................................................................... 1638
7.8.140 Port Range Sensor .............................................................................................. 1644
7.8.141 PostgreSQL Sensor ............................................................................................. 1649
7.8.142 Probe Health Sensor ............................................................................................ 1661
7.8.143 Python Script Advanced Sensor ............................................................................ 1667
7.8.144 QoS (Quality of Service) One Way Sensor ............................................................. 1675
7.8.145 QoS (Quality of Service) Round Trip Sensor ........................................................... 1682
7.8.146 RADIUS v2 Sensor .............................................................................................. 1690
7.8.147 RDP (Remote Desktop) Sensor ............................................................................ 1696
7.8.148 Redfish Power Supply Sensor ............................................................................... 1700
7.8.149 Redfish System Health Sensor ............................................................................. 1706
7.8.150 Redfish Virtual Disk Sensor .................................................................................. 1713
7.8.151 REST Custom Sensor .......................................................................................... 1719
7.8.152 REST Custom v2 Sensor (BETA) .......................................................................... 1739
7.8.153 Script v2 Sensor (BETA) ...................................................................................... 1761
7.8.154 Sensor Factory Sensor ........................................................................................ 1768
7.8.155 sFlow Sensor ...................................................................................................... 1781
7.8.156 sFlow (Custom) Sensor ........................................................................................ 1791
7.8.157 SFTP Secure File Transfer Protocol Sensor ........................................................... 1799
7.8.158 Share Disk Free Sensor ....................................................................................... 1805
7.8.159 SIP Options Ping Sensor ..................................................................................... 1809
7.8.160 SMTP Sensor ..................................................................................................... 1814
7.8.161 SMTP&IMAP Round Trip Sensor ........................................................................... 1821
7.8.162 SMTP&POP3 Round Trip Sensor .......................................................................... 1831
7.8.163 SNMP APC Hardware Sensor ............................................................................... 1840
7.8.164 SNMP Buffalo TS System Health Sensor ............................................................... 1845
7.8.165 SNMP Cisco ADSL Sensor .................................................................................. 1850
7.8.166 SNMP Cisco ASA VPN Connections Sensor ......................................................... 1854
7.8.167 SNMP Cisco ASA VPN Traffic Sensor ................................................................... 1858
7.8.168 SNMP Cisco ASA VPN Users Sensor ................................................................... 1863
7.8.169 SNMP Cisco CBQoS Sensor ................................................................................ 1867
7.8.170 SNMP Cisco System Health Sensor ..................................................................... 1872
7.8.171 SNMP Cisco UCS Blade Sensor ........................................................................... 1877
7.8.172 SNMP Cisco UCS Chassis Sensor ....................................................................... 1882
7.8.173 SNMP Cisco UCS Physical Disk Sensor ............................................................... 1887
7.8.174 SNMP Cisco UCS System Health Sensor ............................................................. 1891
7.8.175 SNMP CPU Load Sensor ..................................................................................... 1897
7.8.176 SNMP Custom Sensor ......................................................................................... 1901
7.8.177 SNMP Custom Advanced Sensor .......................................................................... 1907
7.8.178 SNMP Custom String Sensor ............................................................................... 1913
7.8.179 SNMP Custom String Lookup Sensor .................................................................... 1922
7.8.180 SNMP Custom Table Sensor ................................................................................ 1928
7.8.181 SNMP Custom v2 Sensor (BETA) ......................................................................... 1935
7.8.182 SNMP Dell EqualLogic Logical Disk Sensor ........................................................... 1941
7.8.183 SNMP Dell EqualLogic Member Health Sensor ...................................................... 1946
7.8.184 SNMP Dell EqualLogic Physical Disk Sensor ........................................................ 1952
7.8.185 SNMP Dell Hardware Sensor ................................................................................ 1957
7.8.186 SNMP Dell PowerEdge Physical Disk Sensor ........................................................ 1962
7
7.8.187 SNMP Dell PowerEdge System Health Sensor ...................................................... 1967
7.8.188 SNMP Disk Free Sensor ...................................................................................... 1974
7.8.189 SNMP Disk Free v2 Sensor (BETA) ...................................................................... 1978
7.8.190 SNMP Fujitsu System Health v2 Sensor ................................................................ 1983
7.8.191 SNMP Hardware Status Sensor ............................................................................ 1989
7.8.192 SNMP HP LaserJet Hardware Sensor .................................................................... 1993
7.8.193 SNMP HPE BladeSystem Blade Sensor ............................................................... 1998
7.8.194 SNMP HPE BladeSystem Enclosure System Health Sensor ................................... 2002
7.8.195 SNMP HPE ProLiant Logical Disk Sensor ............................................................. 2006
7.8.196 SNMP HPE ProLiant Memory Controller Sensor ..................................................... 2011
7.8.197 SNMP HPE ProLiant Network Interface Sensor ...................................................... 2017
7.8.198 SNMP HPE ProLiant Physical Disk Sensor ........................................................... 2022
7.8.199 SNMP HPE ProLiant System Health Sensor .......................................................... 2028
7.8.200 SNMP IBM System X Logical Disk Sensor ............................................................ 2035
7.8.201 SNMP IBM System X Physical Disk Sensor .......................................................... 2039
7.8.202 SNMP IBM System X Physical Memory Sensor ..................................................... 2043
7.8.203 SNMP IBM System X System Health Sensor ......................................................... 2048
7.8.204 SNMP interSeptor Pro Environment Sensor ........................................................... 2053
7.8.205 SNMP Juniper NS System Health Sensor .............................................................. 2057
7.8.206 SNMP LenovoEMC Physical Disk Sensor .............................................................. 2061
7.8.207 SNMP LenovoEMC System Health Sensor ............................................................ 2065
7.8.208 SNMP Library Sensor .......................................................................................... 2069
7.8.209 SNMP Linux Disk Free Sensor ............................................................................. 2078
7.8.210 SNMP Linux Load Average Sensor ........................................................................ 2086
7.8.211 SNMP Linux Meminfo Sensor ............................................................................... 2090
7.8.212 SNMP Linux Physical Disk Sensor ....................................................................... 2095
7.8.213 SNMP Memory Sensor ........................................................................................ 2099
7.8.214 SNMP NetApp Disk Free Sensor .......................................................................... 2103
7.8.215 SNMP NetApp Enclosure Sensor .......................................................................... 2108
7.8.216 SNMP NetApp I/O Sensor .................................................................................... 2113
7.8.217 SNMP NetApp License Sensor ............................................................................. 2117
7.8.218 SNMP NetApp Logical Unit Sensor ....................................................................... 2121
7.8.219 SNMP NetApp Network Interface Sensor ............................................................... 2126
7.8.220 SNMP NetApp System Health Sensor ................................................................... 2130
7.8.221 SNMP Nutanix Cluster Health Sensor ................................................................... 2135
7.8.222 SNMP Nutanix Hypervisor Sensor ......................................................................... 2140
7.8.223 SNMP Poseidon Environment Sensor .................................................................... 2146
7.8.224 SNMP Printer Sensor .......................................................................................... 2150
7.8.225 SNMP QNAP Logical Disk Sensor ........................................................................ 2155
7.8.226 SNMP QNAP Physical Disk Sensor ...................................................................... 2159
7.8.227 SNMP QNAP System Health Sensor .................................................................... 2164
7.8.228 SNMP Rittal CMC III Hardware Status Sensor ........................................................ 2168
7.8.229 SNMP RMON Sensor .......................................................................................... 2172
7.8.230 SNMP SonicWall System Health Sensor ............................................................... 2177
7.8.231 SNMP SonicWall VPN Traffic Sensor .................................................................... 2181
7.8.232 SNMP Synology Logical Disk Sensor .................................................................... 2186
7.8.233 SNMP Synology Physical Disk Sensor ................................................................. 2190
7.8.234 SNMP Synology System Health Sensor ................................................................ 2194
7.8.235 SNMP System Uptime Sensor ............................................................................. 2199
7.8.236 SNMP Traffic Sensor ........................................................................................... 2203
7.8.237 SNMP Traffic v2 Sensor (BETA) ............................................................................ 2210
7.8.238 SNMP Trap Receiver Sensor ................................................................................ 2219
7.8.239 SNMP Uptime v2 Sensor ...................................................................................... 2229
7.8.240 SNMP Windows Service Sensor ........................................................................... 2234
7.8.241 SNTP Sensor ...................................................................................................... 2238
8
7.8.242 Soffico Orchestra Channel Health Sensor .............................................................. 2242
7.8.243 Soffico Orchestra Scenario Sensor ........................................................................ 2247
7.8.244 SSH Disk Free Sensor ......................................................................................... 2252
7.8.245 SSH INodes Free Sensor ..................................................................................... 2262
7.8.246 SSH Load Average Sensor ................................................................................... 2268
7.8.247 SSH Meminfo Sensor .......................................................................................... 2274
7.8.248 SSH Remote Ping Sensor .................................................................................... 2280
7.8.249 SSH SAN Enclosure Sensor ................................................................................ 2287
7.8.250 SSH SAN Logical Disk Sensor ............................................................................. 2294
7.8.251 SSH SAN Physical Disk Sensor ........................................................................... 2301
7.8.252 SSH SAN System Health Sensor ......................................................................... 2308
7.8.253 SSH Script Sensor .............................................................................................. 2316
7.8.254 SSH Script Advanced Sensor ............................................................................... 2326
7.8.255 SSL Certificate Sensor ......................................................................................... 2334
7.8.256 SSL Security Check Sensor ................................................................................. 2342
7.8.257 Syslog Receiver Sensor ....................................................................................... 2348
7.8.258 System Health Sensor ......................................................................................... 2357
7.8.259 System Health v2 Sensor ..................................................................................... 2361
7.8.260 TFTP Sensor ....................................................................................................... 2366
7.8.261 Traceroute Hop Count Sensor ............................................................................... 2370
7.8.262 Veeam Backup Job Status Sensor ........................................................................ 2375
7.8.263 Veeam Backup Job Status Advanced Sensor ......................................................... 2380
7.8.264 VMware Datastore (SOAP) Sensor ....................................................................... 2386
7.8.265 VMware Host Hardware (WBEM) Sensor ............................................................... 2392
7.8.266 VMware Host Hardware Status (SOAP) Sensor ...................................................... 2397
7.8.267 VMware Host Performance (SOAP) Sensor ........................................................... 2403
7.8.268 VMware Virtual Machine (SOAP) Sensor ............................................................... 2409
7.8.269 Windows CPU Load Sensor ................................................................................. 2415
7.8.270 Windows IIS Application Sensor ........................................................................... 2420
7.8.271 Windows MSMQ Queue Length Sensor ................................................................. 2425
7.8.272 Windows Network Card Sensor ............................................................................. 2431
7.8.273 Windows Pagefile Sensor ..................................................................................... 2438
7.8.274 Windows Physical Disk I/O Sensor ....................................................................... 2443
7.8.275 Windows Print Queue Sensor ............................................................................... 2450
7.8.276 Windows Process Sensor .................................................................................... 2459
7.8.277 Windows SMTP Service Received Sensor .............................................................. 2465
7.8.278 Windows SMTP Service Sent Sensor .................................................................... 2470
7.8.279 Windows System Uptime Sensor .......................................................................... 2475
7.8.280 Windows Updates Status (PowerShell) Sensor ...................................................... 2480
7.8.281 WMI Battery Sensor ............................................................................................ 2488
7.8.282 WMI Custom Sensor ........................................................................................... 2493
7.8.283 WMI Custom String Sensor .................................................................................. 2499
7.8.284 WMI Disk Health Sensor ...................................................................................... 2507
7.8.285 WMI Event Log Sensor ........................................................................................ 2512
7.8.286 WMI Exchange Server Sensor .............................................................................. 2521
7.8.287 WMI Exchange Transport Queue Sensor ............................................................... 2526
7.8.288 WMI File Sensor ................................................................................................. 2533
7.8.289 WMI Free Disk Space (Multi Disk) Sensor ............................................................. 2538
7.8.290 WMI HDD Health Sensor ...................................................................................... 2546
7.8.291 WMI Logical Disk I/O Sensor ................................................................................ 2553
7.8.292 WMI Memory Sensor ........................................................................................... 2559
7.8.293 WMI Microsoft SQL Server 2005 Sensor (Deprecated) ............................................ 2564
7.8.294 WMI Microsoft SQL Server 2008 Sensor ................................................................ 2572
9
7.8.300 WMI Remote Ping Sensor .................................................................................... 2614
7.8.301 WMI Security Center Sensor ................................................................................ 2619
7.8.302 WMI Service Sensor ............................................................................................ 2624
7.8.303 WMI Share Sensor .............................................................................................. 2630
7.8.304 WMI SharePoint Process Sensor .......................................................................... 2637
7.8.305 WMI Storage Pool Sensor .................................................................................... 2642
7.8.306 WMI Terminal Services (Windows 2008+) Sensor ................................................... 2647
7.8.307 WMI Terminal Services (Windows XP/Vista/2003) Sensor ....................................... 2652
7.8.308 WMI UTC Time Sensor ........................................................................................ 2657
7.8.309 WMI Vital System Data v2 Sensor ........................................................................ 2661
7.8.310 WMI Volume Sensor ............................................................................................ 2667
7.8.311 WSUS Statistics Sensor ...................................................................................... 2672
7.8.312 Zoom Service Status Sensor ................................................................................ 2679
7.9 Additional Sensor Types (Custom Sensors) ................................................................. 2687
7.10 Channel Settings ....................................................................................................... 2692
7.11 Notification Triggers Settings ...................................................................................... 2704
Part 8 Advanced Procedures ................................................................................................. 2716
8.1 Toplists ..................................................................................................................... 2718

8.2 Move Objects ............................................................................................................ 2723
8.3 Clone Object ............................................................................................................. 2725
8.4 Multi-Edit .................................................................................................................. 2729
8.5 Create Device Template .............................................................................................. 2735
8.6 Show Dependencies .................................................................................................. 2738
8.7 Geo Maps ................................................................................................................. 2741
8.8 Notifications .............................................................................................................. 2745
8.9 Libraries .................................................................................................................... 2748
8.9.1 Library Management ............................................................................................ 2751
8.9.2 Libraries and Node Settings .................................................................................. 2754
8.9.3 Library Context Menus ......................................................................................... 2761
8.10 Reports ..................................................................................................................... 2764
8.10.1 Run Reports ........................................................................................................ 2769
8.10.2 Report Settings ................................................................................................... 2774
8.11 Maps ........................................................................................................................ 2786
8.11.1 Map Designer ...................................................................................................... 2790
8.11.2 Maps Settings ..................................................................................................... 2802
8.11.3 Map Rotation ...................................................................................................... 2807
8.12 Setup ....................................................................................................................... 2809
8.12.1 Account Settings ................................................................................................. 2811
8.12.1.1 My Account ......................................................................................................................................... 2811
8.12.1.2 Notification Templates ......................................................................................................................... 2818
8.12.1.3 Notification Contacts ........................................................................................................................... 2851
8.12.1.4 Schedules ........................................................................................................................................... 2856
8.12.1.5 API Keys .............................................................................................................................................. 2861
8.12.2 System Administration ......................................................................................... 2865
8.12.2.1 User Interface ..................................................................................................................................... 2865
8.12.2.2 Monitoring ............................................................................................................................................ 2879
8.12.2.3 Notification Delivery ............................................................................................................................. 2887
8.12.2.4 Core & Probes ..................................................................................................................................... 2897
8.12.2.5 User Accounts .................................................................................................................................... 2911
8.12.2.6 User Groups ........................................................................................................................................ 2922
10
8.12.2.7 Administrative Tools ............................................................................................................................ 2928
8.12.2.8 Cluster ................................................................................................................................................. 2933
8.12.2.9 Single Sign-On ..................................................................................................................................... 2935
8.12.2.10 Maintainer Mode .................................................................................................................................. 2941
8.12.3 PRTG Status ...................................................................................................... 2945
8.12.3.1 System Status ..................................................................................................................................... 2945
8.12.3.2 Cluster Status ...................................................................................................................................... 2970
8.12.4 License Information .............................................................................................. 2972
8.12.5 Auto-Update ........................................................................................................ 2979
8.12.6 Optional Downloads ............................................................................................. 2984
8.12.7 Help and Support Center ...................................................................................... 2986
8.12.8 Contact Support .................................................................................................. 2987
Part 9 PRTG MultiBoard ........................................................................................................ 2993
Part 10 PRTG Apps for Mobile Network Monitoring .................................................................... 2997
Part 11 Desktop Notifications .................................................................................................. 3002
Part 12 Sensor Technologies ................................................................................................... 3005
12.1 Monitoring via SNMP .................................................................................................. 3007

12.2 Monitoring via WMI .................................................................................................... 3014
12.3 Monitoring via SSH .................................................................................................... 3017
12.4 Monitoring Bandwidth via Packet Sniffing ..................................................................... 3019
12.5 Monitoring Bandwidth via Flows ................................................................................... 3021
12.6 Bandwidth Monitoring Comparison ............................................................................... 3024
12.7 Monitoring Quality of Service ....................................................................................... 3026
12.8 Monitoring Backups ................................................................................................... 3031
12.9 Monitoring Virtual Environments .................................................................................. 3032
12.10 Monitoring Databases ................................................................................................ 3038
12.11 Monitoring via HTTP ................................................................................................... 3042
Part 13 PRTG Administration Tool ........................................................................................... 3049
13.1 PRTG Administration Tool on PRTG Core Server Systems ............................................ 3051
13.2 PRTG Administration Tool on Remote Probe Systems .................................................. 3077
Part 14 Advanced Topics ........................................................................................................ 3089
14.1 Active Directory Integration ......................................................................................... 3091

14.2 Application Programming Interface (API) Definition ........................................................ 3094
14.2.1 HTTP API ........................................................................................................... 3095
14.2.2 Live Data ............................................................................................................ 3098
14.2.2.1 Single Object Property ......................................................................................................................... 3099
14.2.2.2 Single Object Status ............................................................................................................................ 3102
14.2.2.3 Multiple Object Property or Status ....................................................................................................... 3109
14.2.2.4 System Information .............................................................................................................................. 3125
14.2.3 Live Graphs ......................................................................................................... 3129
14.2.4 Historic Data ....................................................................................................... 3132
14.2.5 Object Manipulation ............................................................................................. 3135
14.2.6 Custom Sensors ................................................................................................. 3142
14.2.7 Custom Notifications ............................................................................................ 3156
14.2.8 Mini Probe API .................................................................................................... 3158
14.3 Filter Rules for Flow, IPFIX, and Packet Sniffer Sensors ................................................ 3178
11
14.4 Channel Definitions for Flow, IPFIX, and Packet Sniffer Sensors ..................................... 3183
14.5 Define IP Address Ranges .......................................................................................... 3185
14.6 Define Lookups .......................................................................................................... 3186
14.7 Regular Expressions .................................................................................................. 3198
14.8 Calculating Percentiles ............................................................................................... 3200
14.9 Add Remote Probe .................................................................................................... 3201
14.9.1 Remote Probes and Multiple Probes ..................................................................... 3203
14.9.2 Classic Remote Probe Setup via Device Tools ........................................................ 3207
14.10 Failover Cluster Configuration ...................................................................................... 3213
14.11 Data Storage ............................................................................................................. 3218
Part 15 Appendix ................................................................................................................... 3224
15.1 Abbreviations ............................................................................................................. 3226

15.2 Available Sensor Types .............................................................................................. 3237
15.3 Default Ports ............................................................................................................. 3324
15.4 Differences between PRTG Network Monitor and PRTG Hosted Monitor .......................... 3329
15.5 Escape Special Characters and Whitespaces in Parameters ......................................... 3348
15.6 Glossary ................................................................................................................... 3349
15.7 Icons ........................................................................................................................ 3358
15.8 Legal Notices ............................................................................................................ 3359
15.9 Placeholders for Notifications ...................................................................................... 3361
15.10 Standard Lookup Files ............................................................................................... 3371
15.11 Supported AWS Regions and Their Codes ................................................................... 3386
12
Part 1
Welcome to PRTG
9/19/2023 13
1 Welcome to PRTG
Welcome to PRTG. You have chosen a software product that comes with a comprehensive set of
features to monitor your entire network.
A Standard Installation of PRTG
Why Network Monitoring is Important

Today, nearly every business relies on a computer and network infrastructure for internet, internal
management, telephone, and email. A complex set of servers and network equipment is required to
make sure that business data flows seamlessly between employees, offices, and customers. The
economic success of an organization is tightly connected to a hitch-free flow of data.
That is why your computer network has to work successfully: reliability, speed, and efficiency are
crucial. But, like all other technical objects, network devices fail from time to time and can potentially
cause trouble and loss of sales, no matter what migration efforts have been made up front.
You need to take three key steps to maintain network uptime, reliability, and speed:
1. Set up a well-planned network with reliable components.

2. Create recovery plans for the event of device failure.
3. Monitor the network to get informed about failures when they occur or are about to occur.
14
Monitoring Networks with PRTG
PRTG is a comprehensive network monitoring application for Windows-based systems. It is suitable for
networks of all sizes 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 much more.
PRTG monitors network availability and bandwidth usage, as well as various other network parameters
such as quality of service, memory load, and CPU usage, even on remote machines. PRTG 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 monitors a network that uses Simple Network Management Protocol (SNMP), Windows
Management Instrumentation (WMI), packet sniffer, Cisco NetFlow, IPFIX, sFlow, jFlow, and many other
industry standard protocols. It runs on a Windows-based machine in your network for 24 hours a day.
PRTG constantly records the network usage parameters and the availability of network systems. The
recorded data is stored in an internal database for later analysis.
15
1.1 About this Document
This document introduces you to PRTG Network Monitor and Paessler PRTG Enterprise Monitor, both
from now on referred to as PRTG. Everything you need to know to use PRTG or PRTG Hosted Monitor is
in this document:
§ Plan monitoring results
§ Achieve the best monitoring results
§ Use a cluster for fail-safe monitoring
§ Set up devices, sensors, dependencies, and much more
This document is also a reference for all settings in PRTG. While there is short contextual help in the
PRTG web interface, this document provides more comprehensive information about available options.
Whenever possible, links to more detailed resources are provided, such as articles in our Knowledge
Base.
This document does not give an in-depth explanation of monitoring protocols and file formats. It also only
briefly addresses the use of the application programming interface (API) built into PRTG.
§ To use PRTG right away, see section Quick Start Guide 39 .

§ To learn more about monitoring with PRTG, see section Introduction: Monitoring with PRTG 34 .
§ For more information, browse the manual content or use the manual search with keywords and choose
the section that you want to read.
For an overview of the icons and abbreviations that are used in this document, see section
Appendix 3225 .
16
1.2 Key Features
PRTG offers two options to monitor your network: PRTG Network Monitor and PRTG Hosted Monitor.
§ PRTG Network Monitor: The PRTG core server and local probe run in your network.
§ PRTG Hosted Monitor: Paessler runs the PRTG core server and hosted probe for you in the cloud.
The PRTG web interface is the same for both PRTG Hosted Monitor and PRTG Network Monitor.
Areas of Application
PRTG can monitor:
§ Uptimes, downtimes, and slow servers
§ System health of hardware devices
§ Network devices and bandwidth
17
§ Applications
§ Virtual servers
§ Service level agreements (SLA)
§ System usage (for example CPU load, free memory, and free disk space)
§ Database performance and table values
§ Email servers
§ Physical network environments
§ Cloud services
It can also:
§ Classify network traffic and content by source or destination
§ Measure Quality of Service (QoS) and Voice over IP (VoIP) parameters
§ Collect system information for hardware
§ Detect unusual activity between network components and warns about potential security issues
§ Detect unusual behavior by devices or users
§ Assess the real usage of network and hardware
§ Fail-safe monitor a cluster
Key Features
§ High performance: The database system stores raw monitoring results as well as logs, Toplists, and
tickets. This outperforms Structured Query Language (SQL) servers for monitoring data. You can
distribute high loads among several probes and also access the database through the PRTG API.
§ Low system requirements : To run PRTG Network Monitor, an average PC that is not older than 2
23
years is enough. Even a netbook can monitor more than a thousand sensors.
PRTG Hosted Monitor requires no hardware for the PRTG core server.
§ High security standards: Secure Sockets Layer (SSL)/Transport Layer Security (TLS) secured
connections and web servers, secure ciphers, personalized user rights management, and much more.
For more information, see the Knowledge Base: What security features does PRTG include?
§ SSL/TLS-secured web server with HTTP and HTTPS support for the PRTG web interface. This acts as
a Single Page Application (SPA) to avoid time-intensive page reloading.
§ Email relay server for automatic email delivery.
§ Customizable alerts for specific needs:
ú Various notification methods: email, push, SMS text messages, Syslog messages and Simple
Network Management Protocol (SNMP) traps, HTTP requests, event logs, Amazon Simple
Notification Service (SNS), executing scripts.
ú Multiple ways to trigger notifications: status alerts, limit alerts, threshold alerts, multiple condition
alerts, escalation alerts.
ú Gradual dependencies to avoid alarm floods, acknowledging certain alarms to avoid further
notifications, and alert scheduling.
18
§ In-depth report generator to create reports on demand or scheduled reports in HTML, as .pdf, .csv, or
.xml. Several report templates are available by default.
§ Graphics engine for user-friendly live graphs and historic data graphs.
§ Network analysis modules to automatically find network devices and sensors.
§ Distributed monitoring to monitor several networks in different locations.
§ Special features for managed service providers (MSP) to monitor customer networks and increase the
quality of service.
§ Data publishing with real-time dashboards 2786 , including live performance and status information.
Design these dashboards with many different objects and integrate external objects as well.
§ Multiple languages: English, German, Spanish, French, Portuguese, Dutch, Japanese, Russian, and
Simplified Chinese.
§ Customization: The PRTG API lets you develop your own features. Additionally, you can create
custom sensors, notifications, and device templates according to your specific needs.
PRTG supports monitoring for up to several thousand sensors per installation, depending on various
parameters. It can also work with remote probes to distribute high monitoring loads, to monitor multiple
sites or network segments from one central core installation, and to monitor non-Windows systems. It is
also possible to configure fail-safe monitoring with a cluster to perform automatic failovers.
More
KNOWLEDGE BASE
What security features does PRTG include?

§ https://kb.paessler.com/en/topic/61108
19
1.3 New in this Version
The continuous development and rollout of PRTG constantly expands its functionalities. Instead of
delivering only a few versions with massive changes in every update each year, PRTG is automatically
and consistently improved with new features and fixes.
PRTG Network Monitor has three release channels:
§ Stable: Best tested version for live systems. It is updated about once every 8 weeks. Use it on live
systems.
§ Preview: Offers the latest features and fixes and is updated twice between stable releases. Consider
this version a "beta", so do not use this version on live systems that you depend on.
§ Canary: Provides nightly builds and is updated very often. It is not extensively tested. Never use it on
live systems that you depend on.
With the release channels, you can choose from maximum stability, early access to new features, or a
mix of both.
PRTG Hosted Monitor does not have release channels. Instead, we roll out the latest Stable version
to PRTG Hosted Monitor instances in stages.
For an overview of all changes in the different versions, see the Paessler website: Release notes for
the "stable" release channel
More
PAESSLER WEBSITE
Release notes for the "stable" release channel

§ https://www.paessler.com/prtg/history/stable
PRTG version history
§ https://www.paessler.com/prtg/history
20
1.4 Available Licenses
PRTG licenses count by sensors 138 . Three different license editions are available.
Edition Description
Trial edition The trial edition is intended for evaluation purposes:

§ Allows you to use an unlimited number of sensors.
§ Supports all available sensors.
§ For PRTG Network Monitor, you must request a trial license key. Click
the Free Download button on the Paessler website to see the license
details and the key.
§ The trial edition of PRTG Network Monitor is limited to 30 days and
automatically turns into a freeware edition afterward.
PRTG Hosted Monitor provides a 10-day trial. Afterward, your

instance is deleted. Upgrade to a commercial edition to keep your
instance.
Each PRTG Network Monitor license includes one single failover

cluster 132 that consists of two cluster nodes. A cluster with two or
three failover nodes requires an additional license key. A cluster with four
failover nodes requires two additional license keys.
After the trial period, the PRTG Network Monitor trial edition
automatically turns into a freeware edition that lets you use up to 100
sensors for free.
Freeware edition The freeware edition is a good solution for starters or for private use:
§ Free for personal and commercial use.
§ Allows you to use up to 100 sensors.
If you want to use the freeware edition, install the trial edition first and
get a trial license key. After the trial period, the trial edition
automatically turns into a freeware edition that lets you use up to 100
sensors for free.
The freeware edition is not available in PRTG Hosted Monitor.
Commercial edition There are several types of commercial edition available that suit the
demands of smaller as well as larger customers and organizations:
§ Allows you to use a maximum number of sensors (consider our
recommendations 28 ).
21
Edition Description
Each PRTG Network Monitor license includes one single failover

cluster 132 that consists of two cluster nodes. A cluster with two or
three failover nodes requires an additional license key. A cluster with four
failover nodes requires two additional license keys.
For more information about available commercial licenses, see the
Paessler website: Pricing.
More
PAESSLER WEBSITE
Download PRTG and get a trial license key

§ https://www.paessler.com/prtg/download
Pricing
§ https://www.paessler.com/prtg/pricing
22
1.5 System Requirements
There are different aspects that you need to consider regarding the system requirements for PRTG. Meet
these requirements to avoid issues while you monitor your network.
In this section:
§ Basic System Requirements 23
ú Requirements for the PRTG Core Server 23
ú Requirements for Remote Probes 24
ú General Performance Impact Considerations 25
ú Running PRTG in Virtual Environments 26
ú Running PRTG in a Cluster 27
ú Large PRTG Installations 27
§ Detailed System Requirements 27
ú Supported Operating Systems for the PRTG Core Server and Remote Probes 27
ú Hardware and Network Size Requirements for the PRTG Core Server 28
ú Hardware and Network Size Requirements for Classic Remote Probes 29
ú Hardware and Network Size Requirements for Multi-Platform Probes 29
ú Performance Impact Considerations Based on Sensor Types 30
ú Supported Web Browsers 31
§ Further System Requirements 31
ú Screen Resolution 31
ú Requirements for Monitored Devices 32
ú Requirements for Smartphones and Tablets 32
Basic System Requirements

PRTG consists of two main system parts 127 : PRTG core server and probes.
§ If you want to use PRTG Network Monitor, you need to install PRTG on a system that meets the basic
system requirements for the PRTG core server 23 .
If you want to use PRTG Hosted Monitor, you need to install at least one remote probe on a system
that meets the basic system requirements for remote probes 24 .
Requirements for the PRTG Core Server

For more information, see the hardware and network size requirements 28 for the PRTG core server.
For installations of the PRTG core server 128 , you need to meet the following requirements.
23
Category Requirements
Hardware We recommend that you use x64 server hardware or a properly configured
virtual environment 26 .
Operating system We recommend that you use Microsoft Windows Server 2022, Microsoft
Windows Server 2019, or Microsoft Windows Server 2016.
Microsoft .NET It is required that .NET 4.7.2 or later of the Microsoft .NET Framework is
Framework installed on the PRTG core server system or the remote probe system.
For new installations of the PRTG core server or classic remote probes,
we recommend .NET Framework 4.8.
For more information, see the Knowledge Base: Which .NET version
does PRTG require?
Web browser The following browsers are officially supported by the PRTG web interface:
§ Google Chrome 75
§ Mozilla Firefox 67
§ Microsoft Edge 79
§ Safari 11 or iOS (Safari) 11
For security and performance reasons, we strongly recommend that

you always use the latest version of Google Chrome to access the
PRTG web interface.
PRTG Hosted Monitor does not require any hardware for the PRTG core server, but it needs at least
one remote probe installation to monitor your local network.
Requirements for Remote Probes

For more information, see the hardware and network size requirements 29 for remote probes.
For installations of classic remote probes 3203 , you need to meet the following requirements:
Category Requirement
Hardware We recommend that you use compatible x86 hardware or a properly

configured virtual environment 26 .
Operating system We recommend that you use Microsoft Windows Server 2022, Microsoft
Windows Server 2019, Microsoft Windows Server 2016, or Microsoft
Windows 10.
24
does PRTG require?
Stable network Remote probes require a stable network connection between the PRTG
connection core server and the remote probe.
Remote probes that connect to a PRTG Hosted Monitor instance
need a reliable internet connection. Unstable connections, for
example via 3G, might work but you might lose monitoring data if the
connection is unreliable.
For more information on system requirements for the multi-platform probe, see the see the Multi-
Platform Probe for PRTG manual.
General Performance Impact Considerations
Category Performance Impact Considerations
Hardware resources For a PRTG core server to work properly, it is crucial to have a certain
amount of hardware resources available. If the server runs out of
resources, PRTG sends warning and emergency messages to the
primary email address of the PRTG System Administrator user.
You receive warning messages if the available disk space falls below
1 GB or if the available memory falls below 500 MB, and emergency
messages if the available disk space or memory fall below 50 MB. In this
case, react immediately and free up system resources.
Sensors Ping and SNMP sensors create much less load than complex sensors
like flow sensors, VMware sensors, Sensor Factory sensors, WMI
sensors. or Syslog Receiver or SNMP Trap Receiver sensors, for
example.
There are also limitations for some sensors that do not depend on
hardware resources, for example, WMI and SNMP v3 sensors. You
can overcome these limitations if you distribute the sensors between
remote probes.
For clusters, we recommend that you stay below 2,500 sensors per
cluster.
25
Category Performance Impact Considerations
Channels We recommend that you use sensors with less than 50 channels. Note
that sensors with more than 50 channels are not officially supported.
PRTG will try to display all channels but it will limit usability and have a
high impact on system performance.
Scanning interval For a single PRTG core server setup without a cluster, we recommend
that you mainly use 1-minute scanning intervals for up to 2,000 sensors
and 5-minute intervals if you have more sensors.
To give you an impression: To monitor 5,000 sensors with a 1-minute
scanning interval, PRTG takes 7.2 million measurements and
evaluates, notifies, and stores them. This adds 700 MB of additional data
to the database every single day.
CPU-intensive features Try to limit the use of the following features:

§ Many quickly refreshed maps 2786
§ Frequent generation of huge reports 2764
§ Heavy usage of packet sniffing 3019 , Sensor Factory sensors, and

Toplists 2718
§ Frequent automatically scheduled auto-discoveries 270 for large network
segments
§ Constant queries of monitoring data via the PRTG API 3094
Network connection The quality of your network also plays an important role. When you
quality monitor via User Datagram Protocol (UDP), for example, a high packet
loss rate can lead to frequent timeouts. Remote probes that connect via
unstable (WAN) connections can lead to delays as well.
Running PRTG in Virtual Environments

You can run the PRTG core server and remote probes on virtualized platforms. However, PRTG consists
of a lot of different components that all rely on the performance and the stability of the probe system
where virtual environments add even more layers of complexity. This needs to be considered when you
want to set up your PRTG installation in a way that you can achieve the same level of performance as on
a physical server.
Most PRTG installations from 500 to 5,000 sensors do not need any specific optimization regarding your
virtual infrastructure.
If you run larger installations of PRTG with more than 5,000 sensors, we strongly recommend that you
follow the instructions in our Best Practice Guide: Running large installations of PRTG in a virtual
environment.
Particularly for virtual systems, make sure that you have a unique Windows security identifier per
system.
26
Running PRTG in a Cluster
We recommend a single failover cluster 132 for fail-safe monitoring. This consists of two PRTG core
servers that each work as a cluster node.
In a cluster, the monitoring load doubles with each cluster node, so the performance of each additional
cluster node is halved. Therefore, in a single failover cluster, divide our recommended numbers from
earlier in the section in half.
This feature is not available in PRTG Hosted Monitor.
Large PRTG Installations

The maximum number of sensors you can monitor with one PRTG Network Monitor installation mainly
depends on the monitoring technology and the scanning intervals you use. In general, we recommend
that you use a dedicated physical machine to run both the PRTG core server and remote probes.
Running large installations of PRTG in a virtual environment is possible if you follow some specific rules
and guidelines to achieve the required level of performance.
For more information, see section Detailed System Requirements 27 .
For more information, see the Knowledge Base: How can I speed up PRTG—especially for large
installations?
PRTG Hosted Monitor is restricted to a maximum of 10,000 sensors. More sensors are not
possible.
Detailed System Requirements
Supported Operating Systems for the PRTG Core Server and Remote Probes
Supported operating The 32-bit and 64-bit versions of the following operating systems are
systems officially supported for the PRTG core server service and PRTG probe
service:
§ Microsoft Windows Server 2022*
§ Microsoft Windows 11
§ Microsoft Windows 10
* Windows servers in Core mode or Minimal Server Interface are not

officially supported.
27
Operating system version The version (32-bit or 64-bit) of the PRTG core server depends on the
version of your operating system.
does PRTG require?
The .NET framework is imperative if you want to monitor VMware and
XenServer virtual environments. Many other sensors also need an
installed Microsoft .NET Framework.
Disabled FIPS mode Make sure that the Federal Information Processing Standards (FIPS)
mode (Windows security option "System Cryptography: Use FIPS-
compliant algorithms for encryption, hashing, and signing.") is disabled on
Windows systems that run the PRTG core server service or PRTG probe
service. FIPS-compliant encryption can cause issues with sensors that
use the .NET framework.
For more information, see the Knowledge Base: What security
features does PRTG include?
PRTG Hosted Monitor is restricted to a maximum of 10,000 sensors. More sensors are not
possible.
Hardware and Network Size Requirements for the PRTG Core Server
Hardware requirements for the PRTG core server service mainly depend on the sensors and scanning
intervals that you use. Your network size can also influence the performance of your monitoring.
Sensors per CPU cores RAM Disk Concurrently Number of

PRTG core space active remote
server administrator probes
sessions
Up to 500 4 4 GB 100 GB < 30 < 30
Up to 1,000 6 6 GB 500 GB < 30 < 30
Up to 2,500 8 8 GB 750 GB < 20 < 60
Up to 5,000 8 12 GB 1,000 GB < 20 < 60
28
Sensors per CPU cores RAM Disk Concurrently Number of
PRTG core space active remote
server administrator probes
sessions
Up to 10,000 10 - 12 16 GB 1,500 GB < 15 < 80
> 10,000 We recommend that you set up additional PRTG core servers. For more
information on scaling, you can also contact the Paessler Presales team.
Hardware and Network Size Requirements for Classic Remote Probes

Hardware requirements for the PRTG probe service mainly depend on the sensors and scanning intervals
that you use. Your network size can also influence performance of your monitoring.
Sensors per classic CPU cores RAM Disk space

remote probe
Up to 200 2 2 GB 40 GB
200 - 2,000 4 4 GB 40 GB
2,000 - 5,000 6 6 GB 40 GB
> 5,000 We recommend that you set up additional remote probes. For more
information on scaling, you can also contact the Paessler Presales
team.
A remote probe system does not have any special disk requirements (< 1 GB). In general, we
recommend at least 40 GB.
Hardware and Network Size Requirements for Multi-Platform Probes

Hardware requirements for the multi-platform probe mainly depend on the operating system, sensors,
and scanning intervals that you use. Your network size can also influence performance of your
monitoring.
Multi-platform probes currently support the following non-Windows systems: Ubuntu Linux, Debian
Linux, RHEL/CentOS, and Raspberry PI OS.
29
Sensors per multi-platform CPU cores RAM Disk space
probe
Up to 200 2 1 GB 8 GB
200 - 2,000 4 2 GB 8 GB
2,000 - 5,000 6 2 GB 8 GB
> 5,000 We recommend that you set up additional multi-platform probes. For
more information on scaling, you can also contact the Paessler
Presales team.
For more information about concrete hardware examples you can use with the multi-platform probe,
see the Multi-Platform Probe for PRTG manual.
Performance Impact Considerations Based on Sensor Types

You can find the performance impact 2962 of a specific sensor on the Overview tab of the sensor or in the
Add Sensor 430 dialog.
For an overview list of all sensors, including their performance impact, see section Available Sensor
Types 3237 .
In general, consider the following rules for the different sensor types:
Sensor Type Performance Impact Considerations
SNMP v1 and v2, Ping, We recommend that you use these sensor types for scenarios with
Port, and HTTP thousands of sensors.
SNMP v3 SNMP v3 has performance limitations because of the use of encryption.

Furthermore, keep in mind that SNMP v3, unlike SNMP v1 and v2c, does
not scale with more CPU power. Because of this limitation, PRTG can
only handle a limited number of requests per second so that you can use
only a limited number of sensors using SNMP v3.
WMI Try to keep the number of WMI sensors per probe below 120 sensors
(with a 60-second scanning interval), or below 600 sensors (with a 300-
second scanning interval).
Flow The maximum number of flow sensors depends on the traffic pattern, the
number of flow packets per second that the probe receives, as well as the
performance of the probe system.
30
Sensor Type Performance Impact Considerations
Packet Sniffer This sensor type creates the highest CPU load on the probe system. We
only recommend this technology for monitoring low traffic connections (<
50 Mbit/s steady stream). If the traffic often exceeds 10 Mbit/s, use a
dedicated remote probe.
VMware monitoring Monitoring VMware is limited to about 30 sensors at a 60-second

scanning interval, or 100 sensors at a 5-minute scanning interval. On
probes that run on at least Windows Server 2016, you can use more
VMware sensors. These limitations come from the VMware platform.
For more information, see the Knowledge Base: How can I increase
the connection limit on VMware systems? PE121
You can overcome these limitations if you distribute the sensors between remote probes.
Supported Web Browsers

Microsoft Internet Explorer 11, older versions of Microsoft Edge 79, as well as other browsers that
are not officially supported, have issues with some functionalities of the PRTG web interface.
However, you can access the PRTG web interface with any browser.
Deprecated Internet Explorer versions as well as some mobile browsers might not be able to display
all features of the PRTG web interface.
Mozilla Firefox Mozilla Firefox is potentially vulnerable to cross-site scripting (XSS)

attacks. These XSS exploits are possible if you click, for example,
phishing links in emails that contain malicious code, and you are logged
in to PRTG with Mozilla Firefox.
For more information, see the Knowledge Base: How secure is it to
access the PRTG web interface with Firefox?
Plugins Plugins can also have an effect when you view the PRTG web interface.
Make sure that you add exceptions for PRTG in the plugins' settings,
particularly if you use ad blockers.
For more information, see the Knowledge Base: The logs page in the
PRTG web interface does not load. What can I do?
Further System Requirements
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 pixels or higher.
31
Requirements for Monitored Devices
SNMP monitoring The target devices must support SNMP v1, v2c, or v3. An SNMP-
compatible software must be installed on the device. You must enable
SNMP on the device and you must grant the PRTG core server system
access to the SNMP interface.
For more information, see section Monitoring via SNMP 3007 .
Windows/WMI To monitor via WMI, you need a Windows network. Use only the officially
monitoring supported operating systems 27 when you monitor via WMI.
For more information, see section Monitoring via WMI 3014 .
Flow monitoring The target devices must be able to send NetFlow (NetFlow v5, NetFlow
v9, or IPFIX) data packets or sFlow v5 packets to the probe system.
For more information, see section Monitoring Bandwidth via Flows 3021
.
Packet sniffer monitoring PRTG can only analyze data packets that pass the network card of the
local machine. Switches with monitoring ports are necessary for network-
wide monitoring in switched networks.
For more information, see section Monitoring Bandwidth via Packet
Sniffing 3019 .
Other sensor types You can find specific sensor and device requirements (for example,
modules, components, device configurations) in the corresponding sensor
section and in the Add Sensor dialog.
Requirements for Smartphones and Tablets

You can optionally use the PRTG apps for iOS and Android.
For more information and system requirements, see section PRTG Apps for Mobile Network
Monitoring 2998 .
More
KNOWLEDGE BASE
Which .NET version does PRTG require?


32
How can I increase the connection limit on VMware systems? PE121
How secure is it to access the PRTG web interface with Firefox?

The logs page in the PRTG web interface does not load. What can I do?
How can I speed up PRTG—especially for large installations?

How do I run PRTG under a different Windows user account than the local system account?
What do I have to consider when I want to do a regular cleanup of my PRTG environment?

PAESSLER WEBSITE
System requirements for PRTG Network Monitor

§ https://www.paessler.com/prtg/system-requirements
33
1.6 Introduction: Monitoring with PRTG
This section shows you how to prepare your IT infrastructure so that you can monitor it with PRTG.
In this section:
§ What PRTG Does 34
§ How to Monitor with PRTG 35
§ What PRTG Monitors 35
§ How to Prepare Monitoring 36
§ Which Hardware Do I Want to Monitor 36
To immediately start monitoring with PRTG, go to section Quick Start Guide 39 .
What PRTG Does

PRTG is a unified monitoring tool that can monitor almost any object that has an IP address. It consists
of the PRTG core server 128 and one or more probes 128 :
§ The PRTG core server is responsible for configuration, data management, PRTG web server, and more.
§ Probes collect data and monitor processes on devices 138 via sensors 138 .
PRTG Architecture
Sensors are the building blocks of PRTG. A sensor can tell you about one or more aspects of a device:
§ Uptime
§ Load
§ Interface throughput
34
§ Bandwidth usage
§ Loading times
§ Speed
§ Hardware status
§ Temperature
§ Quality
§ Resource consumption
§ User counts
§ Record counts
§ Log events
§ Database requests
How to Monitor with PRTG

PRTG obtains monitoring data from target devices in the following ways:
§ Polls or queries sensor data: PRTG actively gathers data from a device in regular intervals. This
includes, for example, device status, resource usage, and performance metrics. Most sensors use this
method. PRTG can also consume and collect sensor data based on interfaces with, for example,
HTTP or HTTPS requests, port checks, email checks, File Transfer Protocol (FTP) downloads, and
database requests.
§ Listens for or receives sensor data: PRTG passively receives data from a device or application. This
includes, for example, unexpected events, Syslogs and Simple Network Management Protocol
(SNMP) traps, detailed data flow 3024 , and event log messages.
Most of the monitoring data that PRTG collects is actively queried. It is the basis for statistical sampling
to see how a device or application performs over time.
For more information, see section Sensor Technologies 3006 .
What PRTG Monitors

PRTG comes with hundreds of sensors 3237 .They range from platform-specific sensors to generic
hardware and bandwidth sensors. Some of them are preconfigured to immediately gather monitoring data
from their target devices. You can also create custom sensors or write custom scripts that return data
from applications. Visit the PRTG Sensor Hub 3284 to learn more about ready-to-use custom sensors.
35
For more information, see section Available Sensor Types 3237 .
How to Prepare Monitoring

The first step in comprehensive monitoring is to make a plan. Think about the following questions:
§ What do I need to monitor in my IT infrastructure?
§ How can I retrieve the needed information? Which technologies and credentials are required?
§ Which notification methods do I want to use to receive alerts if something is wrong?
Which Hardware Do I Want to Monitor?

We recommend that you start with your Business Critical Tier-1. This usually includes the core network
and other infrastructure that all network devices depend upon:
§ Key infrastructure, such as core routers, switches, VPN and firewalls
36
§ Basic network services, such as Dynamic Host Configuration Protocol (DHCP) and Domain Name
System (DNS)
§ Authentication, like Lightweight Directory Access Protocol (LDAP)
Use the following list to help you plan the monitoring of your IT infrastructure with PRTG:
1. Core infrastructure
a. Routers, switches, firewalls
b. Core network services: DNS, Active Directory (AD), LDAP servers

2. For your hardware devices, you need statistics on availability, usage, and performance.
3. PRTG retrieves data via standard protocols:
a. Ping, SNMP; web queries via HTTP and HTTPS; email via Post Office Protocol version 3 (POP3),
Internet Message Access Protocol (IMAP), Simple Mail Transfer Protocol (SMTP)
b. Hardware parameters via SNMP, Secure Shell (SSH), Simple Object Access Protocol (SOAP)
c. Bandwidth usage via Flow (NetFlow, jFlow, sFlow, IPFIX), packet sniffing, SNMP
d. Windows systems via Windows Management Instrumentation (WMI)
e. Other interfaces via SSH and scripts (for example, PowerShell and Python)
More
KNOWLEDGE BASE
My SNMP sensors don’t work. What can I do?

My WMI sensors don't work. What can I do?

My HTTP sensors don't work. What can I do?

How can I send SMS text message notifications via a modem or a mobile phone with PRTG?
How can I use push notifications with PRTG?

VIDEO TUTORIAL
SNMP Trap receiver and syslog receiver sensors

§ https://www.paessler.com/support/videos-and-webinars/videos/syslog-receiver
Notifications
§ https://www.paessler.com/support/videos-and-webinars/videos/notifications
37
Part 2
Quick Start Guide
38 12/29/2023
2 Quick Start Guide
Welcome to PRTG. This section gives you a quick start into monitoring with PRTG.
Welcome Page
To set up your network monitoring, download the PRTG installer from the Paessler website and follow the
steps in the installation wizard, or set up a PRTG Hosted Monitor instance on
https://www.paessler.com/prtg-hosted-monitor and install a remote probe in your LAN. Provide some
information about your network in the smart setup 42 and PRTG immediately starts to monitor your
network. You can adjust the setup to your needs later on.
In this section:
§ Step 1: Download, Installation, and First Login 40
§ Step 2: Smart Setup 42
39
2.1 Step 1: Download, Installation, and First Login
To use PRTG Network Monitor, download it from the Paessler website and install it on a Windows
system.
For information on how to set up a PRTG Hosted Monitor instance, see section Create a PRTG
Hosted Monitor Instance.
Download PRTG
Download the latest stable version of PRTG from the Paessler website as a trial version 21 . Buy and
manage your license at the Paessler shop.
Install PRTG
Double-click the setup file on the system that you want to use as the PRTG core server. Follow the
installation wizard 97 and install the software.
At the end of the installation, open the PRTG web interface with one of the officially supported
browsers 23 .
Because of scripting incompatibilities, you might not be able to use all functionalities of the PRTG
web interface with Internet Explorer 10 or earlier and other older browsers. If you cannot access the
PRTG web interface, open the URL of PRTG in a different supported browser.
Login
After you installed PRTG Network Monitor, open the PRTG web interface with a supported browser. You
see the login screen.
40
Login Screen
PRTG automatically fills in the credentials of the predefined PRTG System Administrator user. The login
name and the initial password is prtgadmin. Click Log in to proceed.
See the next step 42 for more information about the initial configuration of PRTG. 42
More
VIDEO TUTORIAL
All video tutorials

§ https://www.paessler.com/support/videos-and-webinars/videos
41
2.2 Step 2: Smart Setup
PRTG automatically starts the smart setup on a new PRTG installation. This setup assistant guides you
through the initial setup of your network monitoring system. The smart setup reappears until you have
completed all steps. You can skip the introduction altogether right at the beginning.
First Start
When you log in for the first time, you see the device tree 168 . PRTG Network Monitor already includes
several devices 138 with sensors 138 that monitor your network, sorted into different groups 137 . PRTG
automatically creates the device tree during the installation process via the auto-discovery 270 feature.
PRTG scans your network by pinging IP addresses in the subnet of your PRTG core server and adds all
reachable devices to your specific network monitoring structure.
The smart setup scans only for devices with IP addresses in private network ranges. You can
manually start an auto-discovery for other subnets later.
Device Tree after Initial Auto-Discovery
In the upper-right corner of the PRTG web interface, you can see the smart setup assistant. They guide
you through 5 setup steps during which you can enter more information about your network. PRTG runs
another auto-discovery with this information to add additional devices and sensors to your monitoring.
You can still edit the settings that you provided during the smart setup later on to adjust the monitoring
to your needs.
42
Start Your Introduction to PRTG
Click OK! to start a guided tour.
If you click Skip introduction, the smart setup assistant never appears again. We strongly
recommend that you take the guided tour if you are new to PRTG.
The steps to take are:
§ Step 1: Provide Credentials 43
§ Step 2: Enter Location Information 45
§ Step 3: Change Your PRTG Login Password 45
§ Step 4: Confirm Your Email Address 46
§ Step 5: Switch to SSL/TLS 47 (if you access PRTG from a different system)
Step 1: Provide Credentials

Your smart setup assistant asks you to provide credentials for devices in your network. Click OK, Show
Me!, follow the animated mouse pointer, and open the Settings tab of the root group.
Have Your Credentials Ready
On the Settings tab, enter various administrator credentials for your network environment. With these
credentials, PRTG can automatically add a large number of additional devices and sensors to your
device tree. This way, you do not need to manually add every single device.
43
Provide Your Credentials
§ To monitor your Windows clients and servers via Windows Management Instrumentation (WMI), enter
Windows administrator credentials for your network. We recommend that you use domain
administrator credentials if you use an Active Directory. For a general introduction to the technology
behind WMI, see section Monitoring via WMI 3014 .
§ If you have systems that run on Linux, Solaris, or macOS, enter root access credentials for these
systems. For a general introduction to Secure Shell (SSH) monitoring, see section Monitoring via
SSH 3017 .
§ If you use the virtual environments VMware or Citrix XenServer, enter root access credentials for these
systems. For a general introduction to the monitoring of virtual environments, see section Monitoring
Virtual Environments 3032 .
§ To monitor hardware like routers or switches, the Simple Network Management Protocol (SNMP) is
the most commonly used protocol. Usually, all SNMP-enabled devices use the same settings by
default: SNMP v2c, the community string public, and SNMP port 161. For a general introduction to the
technology behind SNMP, see section Monitoring via SNMP 3007 .
§ You can also enter credentials for database management systems or credentials for Amazon Web
Services (AWS) monitoring.
PRTG stores these credentials in the root group of your device tree. All dependent devices automatically
inherit these credentials and use them for monitoring. You can disable the inheritance of settings 140 at
any level if you want to enter other credentials instead.
44
For more information about the available options, see section Root Group Settings 438 .
Click OK, Done! to finish this setup step. Click OK, Do It! to start a detailed auto-discovery.
Start a Detailed Auto-Discovery
Step 2: Enter Location Information

While PRTG runs a new auto-discovery in your network with the provided credentials, the setup assistant
asks you to provide the location of your PRTG core server. This information is displayed in geographical
maps 2741 . Enter your location and confirm with OK, Done!. Click OK, Show Me! to get back to the device
tree.
Enter Your Location
For more information about the available options, see section Root Group Settings 438 .
Step 3: Change Your PRTG Login Password

Back in the device tree, the setup assistant in PRTG Network Monitor asks you to change your
password. Click OK, Show Me! and follow the assistant to your account settings. By default, PRTG uses
the PRTG System Administrator user account with the login name prtgadmin and the password
prtgadmin. So we strongly recommend that you change the password to protect PRTG from
unauthorized access.
45
Start the Passw ord Change
Enter your New Password and confirm it under Confirm Password. The password must meet the
following requirements:
§ At least eight characters long
§ At least one numeral
§ At least one capitalized letter
Click OK, Done! to save your new password.
Change the Default Passw ord
For more information about the available options, see section My Account 2812 .
Step 4: Confirm Your Email Address

To complete the smart setup, check whether the email address that you entered during the installation is
correct.
A correct email address is mandatory for PRTG to reach you via email notifications when there are
alarms and for other important messages.
Click OK, Done! and follow the assistant back to the device tree.
46
Verify Your Email Address
For more information about the available options, see section My Account 2811 .
Step 5: Switch to SSL/TLS

For PRTG Network Monitor, if you access the PRTG web interface from a system other than the system
where you installed PRTG, the setup assistant asks you to switch to a Secure Sockets Layer
(SSL)/Transport Layer Security (TLS) secured connection. We strongly recommend that you run the
PRTG web interface secured with SSL/TLS, especially if you make your PRTG web interface available
from the internet. Otherwise, your passwords are sent over your network without encryption.
§ Click OK, Switch Now! to get more information about using SSL/TLS for the PRTG web server.
§ In the new window, click Yes, switch to SSL/TLS to switch to an SSL/TLS-secured connection.
§ PRTG must restart its services to apply the changes. The PRTG web interface is reachable under an
HTTPS URL afterward.
§ When the PRTG web interface reloads, it most likely shows a certificate warning. Confirm the
certificate warning to proceed to the login screen.
For more information, see the Knowledge Base: Why does my browser show an SSL certificate
warning when I open the PRTG web interface?
Sw itch to a Secure Connection
For more information, see section User Interface 2865 .
47
You Are Done
Finish the Smart Setup
While you went through the smart setup, PRTG created additional devices and sensors for you. The first
monitoring values are also available.
To become familiar with the PRTG web interface, we recommend that you read on in section
General Layout 168 .
More
KNOWLEDGE BASE
Why does my browser show an SSL certificate warning when I open the PRTG web interface?
VIDEO TUTORIAL
Smart setup
§ https://www.paessler.com/support/videos-and-webinars/videos/installation_of_prtg_network_monitor
48
Part 3
Using PRTG Hosted Monitor
5/9/2023 49
3 Using PRTG Hosted Monitor
The following sections show you how to create a PRTG Hosted Monitor instance, how to manage a
PRTG Hosted Monitor subscription, and how to use multi-factor authentication.
In this section:
§ Create a PRTG Hosted Monitor Instance 51
§ Manage a PRTG Hosted Monitor Subscription 64
§ Use Multi-Factor Authentication with PRTG Hosted Monitor 82
See the Paessler website for PRTG Hosted Monitor – Service description and FAQ – PRTG Hosted
Monitor.
More
PAESSLER WEBSITE
PRTG Hosted Monitor – Service description

§ https://www.paessler.com/prtg-hosted-monitor
FAQ – PRTG Hosted Monitor

§ https://www.paessler.com/prtg/prtg-hosted-monitor/faq
50
3.1 Create a PRTG Hosted Monitor Instance
To create a PRTG Hosted Monitor instance, open a web browser and go to the PRTG Hosted Monitor
Customer Portal.
We recommend that you use Google Chrome 75.
Free Trial
In this section:
§ Create a PRTG Hosted Monitor Instance 52
§ Smart Setup for PRTG Hosted Monitor 63
51
Create a PRTG Hosted Monitor Instance
1. On the PRTG Hosted Monitor Customer Portal, click Free Trial to create your PRTG Hosted Monitor
instance. PRTG Hosted Monitor automatically assigns a domain name to your instance. You can
change the domain name 67 at any time.
Sign Up to PRTG Hosted Monitor
2. You can sign up with your Google, Amazon, or Windows account via single sign-on (SSO) (Auth0).
PRTG Hosted Monitor connects to and then automatically uses this account for the login. Click the
respective button and follow the instructions. Alternatively, you can sign up via email. Enter a valid
Email address and a Password. The password must meet the following requirements:
§ At least 8 characters long
§ At least one uppercase letter
§ At least one lowercase letter
52
§ At least one numeral
3. Make sure that you agree to the terms and conditions and privacy policy. Click Sign Up to register for
your PRTG Hosted Monitor instance. You then see that a verification email has been sent to your
inbox.
Verify Email Address Notification
4. Go to your inbox and open the email.
Verify Email Address
53
5. Click Verify Email Address to verify your email address and to go to the login screen.
Login Screen
6. Enter your credentials and click Log In to log in to PRTG Hosted Monitor.
Add New Subscription
54
7. Click Add New Subscription.
55
Subscription Setup
56
8. Select the region in which PRTG Hosted Monitor hosts your instance.
9. Select a subscription plan that fits your requirements and click Checkout.
The billing account will be charged after the free 10-day trial period.
Order Overview
10. You see an overview of your order. Click Proceed To Checkout.
Account Details
57
11. Optionally enter your first name and last name and click Next.
Billing Address
12. Enter your billing information. Then click Next
58
13. To enable data sharing, click .
Data Sharing
59
14. Enter your billing information. Then click Next.
Account and Billing Details Overview
60
15. You see an overview of your account and billing details. Click Subscribe to finish.
Subscription Progress
61
14. The Subscription Overview page opens and shows the progress of the PRTG Hosted Monitor
installation.
PRTG Hosted Monitor Instance Ready
15. Your PRTG Hosted Monitor instance is now ready. Click Open PRTG to open your PRTG Hosted
Monitor instance in the PRTG web interface.
16. Enter your credentials on the login screen 54 .
Welcome
Your PRTG Hosted Monitor instance is now up and running. To open the device tree, click View Results,
or click Devices in the main menu bar.
62
PRTG Hosted Monitor automatically creates a hosted probe that runs on the hosted instance. It shows
several health values of the instance and you can instantly monitor all servers, services, and devices that
are publicly available via the internet with the hosted probe.
Smart Setup for PRTG Hosted Monitor

A Paessler employee guides you through the smart setup. In particular, you must install a remote probe,
which is required for monitoring your LAN. We strongly recommend that you do so.
Smart Setup: Install a Remote Probe
Click Install Remote Probe to start the installation.
The multi-platform probe is currently not compatible with PRTG Hosted Monitor.
For more information, see section Install a Remote Probe.
For more information about other steps of the smart setup, see section Step 2: Smart Setup for
PRTG Network Monitor.
63
3.2 Manage a PRTG Hosted Monitor Subscription
PRTG Hosted Monitor offers subscription plans that you can tailor to your needs and that you can
manage via the PRTG Hosted Monitor Customer Portal. To manage your subscription, open a web
browser, go to the PRTG Hosted Monitor Customer Portal, and log in.
Login Screen
Provide the credentials that you entered when you signed up, the code that is shown, and click Log In, or
use single sign-on (SSO) and continue with your Google, Amazon, or Microsoft account via the
respective button.
In this section:
§ Subscription Overview 65
64
§ Manage Subscription 67
ú Change PRTG Subdomain 69
ú Change PRTG Timezone 69
ú Change Multi Factor Authentication in PRTG 70
ú Data Sharing Options 71
ú Request Hosting Transfer 71
ú Restart Instance 71
ú Cancel Subscription 71
ú Change Subscription 72
§ Account Settings 73
ú Reset Password 74
ú Billing Details 75
ú Payment Details 76
§ Invoices 77
§ Upload 78
ú Upload Device Templates 79
ú Upload Custom Files 79
§ Logout 80
Subscription Overview
Subscription Overview
65
Here you see an overview of your PRTG Hosted Monitor subscription. Click Add New Subscription to
upgrade to a commercial subscription, for example. Click Open PRTG to open your PRTG Hosted
Monitor instance in the PRTG web interface. Or click Manage to manage your subscription.
66
Manage Subscription
67
68
Change PRTG Subdomain
Here you can change your subdomain. The domain name can be anywhere from 4 to 60 characters long.
1. Enter a new domain name such as myfirstdomain. If you enter myfirstdomain as the domain name,
for example, your PRTG Hosted Monitor instance is reachable under myfirstdomain.my-prtg.com.
If you have remote probes, you must manually change the domain name for the PRTG core
server. This corresponds to the Server (IPv4 Address or DNS Name) setting in the PRTG
Administration Tool.
Domain Change
2. Click Got It to continue. You can see the progress in the status bar.
This can take a few minutes.
Domain Change Progress
When the change is complete, the PRTG Hosted Monitor instance is ready.
Instance Ready
Change PRTG Timezone
Here you can change the time zone.
69
Time Zone Options
Select a time zone from the dropdown list. You see the following message.
Time Zone Changed
Change Multi Factor Authentication in PRTG
To enable multi-factor authentication for all users of your PRTG Hosted Monitor instance, click .
Change Multi Factor Authentication in PRTG
70
After you enable this option, multi-factor authentication is activated for all users of your PRTG
Hosted Monitor instance and they are asked to scan a QR code with a Time-based One-time
Password algorithm (TOTP) application and to enter the current one-time password (OTP) to finish the
setup. For more information, see the Knowledge Base: Can I enable multi-factor authentication for my
PRTG Hosted Monitor instance?
Data Sharing Options
To define the depth of information that you want to share with Paessler for product improvement and
optimization purposes, you can choose among the given options.
Data Sharing Options
Request Hosting Transfer
To request a transfer of your hosting region on your PRTG Hosted Monitor instance, click Request
Transfer.
Restart Instance
To restart your PRTG Hosted Monitor instance, click Restart.
Restart Instance
Cancel Subscription
71
1. Click Cancel Subscription to cancel your PRTG Hosted Monitor subscription.
Cancel Subscription
2. Click Got It to finalize the cancellation. You see the following message.
Subscription Cancelled
Change Subscription
72
1. Click Change Subscription to select a new PRTG Hosted Monitor subscription and to open the
payment checkout dialog. You see an overview of your order.
Change Subscription
2. Click Proceed To Checkout and follow the steps to enter your name, billing address, and credit card
information if you did not do so during the creation of your PRTG Hosted Monitor instance.
Account Settings
Click your account in the upper-right corner of the PRTG Hosted Monitor Customer Portal to open your
account settings. Here you can view your profile, change your password, or enable or disable multi-factor
authentication.
For more information, see section Use Multi-Factor Authentication with PRTG Hosted Monitor 82 .
73
Account Overview
Reset Password
1. Click Reset Password to change the password for your PRTG Hosted Monitor account. PRTG then
notifies you that an email has been sent to your inbox.
74
2. Go to your inbox and open the email. Click Change Password to go to the change password screen.
Change Passw ord
3. Enter your new password, then enter it again to confirm it.
Billing Details
75
1. Click Edit Billing Details to change your billing address.
Billing and Shipping Addresses
2. Select the billing address that you want to change.

3. Enter the new information and select Update to change it.
Payment Details
When you purchase a PRTG Hosted Monitor subscription, you need your payment information.
76
1. Enter your payment details and billing details here to save them for later use or edit details you
already entered.
Add a Payment Method
2. Click Add to add the new payment details.
Invoices
Here you can view and download all of your invoices.
77
Invoices
Upload
Here you can upload custom device templates 79 and custom files 79 .
Upload
78
Upload Device Templates
1. Click Select your PRTG subscription to select the subscription for which you want to upload files.
2. Click Select the device templates that you want to upload to select one or more device templates.
Device Templates
3. Enable the check box next to one or more device template names to select them.
You can also click Readme to open the README.md file of the device template in GitLab.
4. Click outside of the dropdown list to continue.
Upload File
5. Click Upload to upload the device templates.
Device Template Upload Successful
Upload Custom Files
79
Custom Files
1. Click next to the type of file that you want to upload and browse for the path to the file in the File
Explorer.
2. Select the file and click Open.
Custom File
3. Click Upload to upload the custom device template files.
Custom File Upload Successful
Logout
Click Logout in the upper-right corner to log out of your PRTG Hosted Monitor account.
80
More
KNOWLEDGE BASE
Can I enable multi-factor authentication for my PRTG Hosted Monitor instance?

81
3.3 Use Multi-Factor Authentication with PRTG Hosted Monitor
You can use multi-factor authentication with PRTG Hosted Monitor. In combination with an authenticator
app that supports the Time-based One-time Password algorithm (TOTP), such as Google Authenticator,
you can make your PRTG Hosted Monitor instance even more secure.
Multi-factor authentication is only available in PRTG Hosted Monitor. For more information, see the
Knowledge Base: Can I enable multi-factor authentication for my PRTG Hosted Monitor instance?
In this section:
§ Initial Setup 82
§ Manually Enter the QR Code 87
§ Log In With Multi-Factor Authentication 87
§ Disable Multi-Factor Authentication 88
§ Use The Recovery Code 89
Initial Setup
To set up multi-factor authentication for your PRTG Hosted Monitor instance, open a web browser, go to
the PRTG Hosted Monitor Customer Portal, and log in. Then click your account in the upper-right corner.
You can only enable multi-factor authentication for your own user account here. To enable or disable
multi-factor authentication for all users of your PRTG Hosted Monitor instance, go to Manage
Subscription. For more information, see section Manage a PRTG Hosted Monitor Subscription 70 .
82
Account Overview
83
1. To enable multi-factor authentication, click .
If you enable multi-factor authentication for the first time, you must log in again.
Login Screen
84
2. Provide the credentials you entered when you signed up and click Log In, or use single sign-on (SSO)
and continue with your Google, Amazon, or Windows account via the respective button.
Scan QR Code
85
3. Scan the QR code with your authenticator app and enter the passcode from the authenticator app in
the field below the QR code.
If your authenticator app is unable to scan the code, see Manually Enter the QR Code 87 for
more information.
Recovery Code
4. You receive a recovery code. Make sure to save it somewhere safe. Click the check box to confirm
that you have safely recorded the code.
5. Click to log in to the PRTG Hosted Monitor Customer Portal.
If you lose your recovery code, contact the Paessler support team.
86
Manually Enter the QR Code
1. If your authenticator app is unable to scan the QR code, click Trouble scanning?
Manually Enter the QR Code
2. Follow the instructions in your authenticator app to manually enter the code.
3. Enter the one-time passcode that your authenticator app generates in the Enter your passcode here
field.
4. Click to continue.
Log In With Multi-Factor Authentication

After you set up multi-factor authentication, the next time you log in to the PRTG Hosted Monitor
Customer Portal, you see an additional login screen.
87
1. Enter the 6-digit code from your authenticator app.
2. Select the check box next to Remember this browser if you do not want to enter the code in this
browser every time you log in.
This applies for 30 days. If you clear your browsing data such as cookies during this time, it no
longer applies.
3. Click to continue.
If you lose your device, see Use The Recovery Code 89 for more information.
Disable Multi-Factor Authentication

To disable multi-factor authentication, follow these steps:
1. Log in to the PRTG Hosted Monitor Customer Portal.

2. Click your account in the upper-right corner.
3. Click under Multi-Factor Authentication.
You see the following message.
88
Multi-Factor Authentication Now Disabled
The next time you log in to the PRTG Hosted Monitor Customer Portal, multi-factor authentication is no
longer enabled.
Use The Recovery Code

1. If you lose your device, click Use the recovery code on the login screen.
89
You see the following screen.
Enter Recovery Code
2. Enter your recovery code and click to continue.

The recovery code must contain 24 alphanumeric characters.
90
3. You receive a new recovery code.
Recovery Code
4. Make sure to save the recovery code somewhere safe. Click the check box to confirm that you have
safely recorded the code.
5. Click to log in to the PRTG Hosted Monitor Customer Portal.
If you lose your recovery code, contact the Paessler support team.
More
KNOWLEDGE BASE
Can I enable multi-factor authentication for my PRTG Hosted Monitor instance?

91
Part 4
Installing the Software
92 11/15/2023
4 Installing the Software
The following sections show you how to download and install PRTG Network Monitor.
If you want to use PRTG Hosted Monitor, go straight to section Create a PRTG Hosted Monitor
Instance to get started.
In this section:
§ Download PRTG 94
§ Update from Previous Versions 95
§ Install a PRTG Core Server 97
§ Install a Cluster 104
§ Enter a License Key 105
§ Activate the Product 107
§ Install a Remote Probe 109
§ Uninstall PRTG Products 122
93
4.1 Download PRTG
Download the latest stable version of PRTG from the Paessler website as a trial version 21 . Buy and
manage your license at the Paessler shop.
Dow nload PRTG
Once you have installed PRTG, the auto-update 2979 automatically downloads and installs new
software versions.
94
4.2 Update From Previous Versions
If you have a previous PRTG version installed, there are several things you need to consider before you
update to the newest PRTG version. See also the system requirements 23 for all requirements.
While in most cases, your monitoring data and configuration are maintained when you update
PRTG, we still recommend that you have a backup of both. For more information, see the
Knowledge Base: How do I back up all data and configuration of my PRTG installation?
In certain cases, antivirus software like Windows Defender interferes with the PRTG installer. This
might cause high CPU load on the PRTG core server, which might prevent an update. Temporarily
disable Windows Defender and other antivirus software if you have issues when you install PRTG
updates.
On PRTG Hosted Monitor instances, updates are managed automatically, so you do not need to do
them manually.
In this section:
§ Update to PRTG 22.2.77 95
§ Update from PRTG 16.1.22 or later 95
§ Update from Older PRTG Products 96
Update to PRTG 22.2.77

As of PRTG 22.2.77, PRTG is signed with renewed certificates. To seamlessly update to any version as
of PRTG 22.2.77, an intermediate update is required for the PRTG core server and all probes if you run a
version previous to PRTG 22.1.75. If you auto-update from previous versions which are lower than PRTG
22.1.75, PRTG automatically installs an intermediate version first. The intermediate version you receive
via auto-update or from the Paessler support team is PRTG 22.1.75.1594. You must perform an
additional auto-update to install the newest version. PRTG notifies you with a ticket 216 about this. Your
configuration is kept.
We recommend that you use the auto-update to install the newest PRTG version.
Update from PRTG 16.1.22 or later

If you run any version as of PRTG 16.1.22 or later, install 97 the newest version on top of the previous
version. Your configuration is kept. PRTG automatically updates classic remote probes 3203 as well. If you
have configured PRTG as a failover cluster 132 , you only need to install an update on any cluster node
(master node or failover node). PRTG automatically deploys the new version to the cluster.
We recommend that you use the auto-update 2979 to install the newest version. Always make sure that
you have a proper backup of your monitoring data.
Important notes:
§ PRTG 19.3.52: PRTG does not run on Windows XP anymore. Make sure that you install PRTG on an
officially supported operating system 27 .
§ PRTG 19.1.48: Sensors that require the .NET framework need .NET 4.7.2 or later. For more
information, see the Knowledge Base: Which .NET version does PRTG require?
95
§ PRTG 18.3.43: PRTG does not run on Windows Server 2003 R2 anymore. Make sure that you install
PRTG on an officially supported operating system.
§ PRTG 17.3.34: This version comes with a completely rewritten PRTG web interface. If you have
customized the PRTG web interface with one of the dedicated files in a previous version, all your
customizations are lost as soon as you install PRTG 17.3.34. You must redo your changes to keep
the customizations.
§ PRTG 16.3.26: The Mobile Web GUI was removed from PRTG.
§ PRTG 16.2.25: Several sensors were removed from PRTG.
Update from Older PRTG Products

For more information on updating from older PRTG versions, see the Knowledge Base: How do I update
from older versions?
More
KNOWLEDGE BASE
How do I back up all data and configuration of my PRTG installation?


Why do I get an error message when trying to restart Windows Server 2019 after a PRTG update?
How do I update from older versions?

96
4.3 Install a PRTG Core Server
Installing PRTG Network Monitor works like other Windows-based applications. To install PRTG, run the
installation setup program from the .zip file that you downloaded.
1. Confirm the question of the Windows User Account Control with Yes to allow PRTG to install. The
installation dialog guides you through the installation process.
Window s User Account Control Confirmation Request
2. Select a language for the installation and click OK. The available language options depend on both
your Windows version and the setup file.
Setup Language Selection
97
3. Accept the license agreement and click Next.
Setup Dialog: License Agreement
4. Enter your email address to make sure you receive important system alerts and click Next.
Setup Dialog: Your Email Address
98
5. Select if you want to use the Express or the Custom installation mode and click Next. If you select
the Express installation mode, you can directly proceed with step 9.
Setup Dialog: Installation Mode
6. This page is only visible if you use the Custom installation mode. You can change the paths to the
PRTG program directory and PRTG data directory 3218 , if necessary. Click Next.
Setup Dialog: Location for Installation and Data Storage
99
7. This page is only visible if you use the Custom installation mode. Select if you want to run an auto-
discovery 270 of your network or if you want to skip the auto-discovery. Click Next.
Setup Dialog: Run or Skip Auto-Discovery
100
8. This page is only visible if you select Run auto-discovery. You can enter a Simple Network
Management Protocol (SNMP) community string. The default SNMP community string is public.
Click Next.
Setup Dialog: Auto-Discovery Configuration
101
9. PRTG is installed on your system.
Setup: Installing PRTG
10. Click Finish to complete the setup of PRTG.
After installation, you can open the PRTG web interface 156 in your system's default browser. Make sure
that a supported browser 23 is available on the system.
In some cases, antivirus software like Windows Defender interferes with the PRTG installer. This
might cause high CPU load on the PRTG core server, which might prevent a successful installation.
Temporarily disable Windows Defender and other antivirus software in these cases.
Enter License Information

PRTG validates your license information during the installation process by connecting to the activation
server. If there are issues with the license information, PRTG asks you to veryify your License Key and
License Name on the first login.
Enter both License Key and License Name exactly as received from Paessler.
Setup Dialog: Enter License Information
102
For more information, see section Enter a License Key 105 .
If you think that you have correctly entered your license information but get a License Invalid message,
contact sales@paessler.com.
You can find the label License Owner in some documents from the Paessler shop. License Owner is
the same as License Name. PRTG might ask you for this information during installation or when you
change your license key 105 .
When you update a commercial version with a new trial installer, PRTG ignores the new trial license
key.
More
KNOWLEDGE BASE
I cannot open the PRTG web interface via the desktop shortcut anymore. What can I do?
How can I establish a secure web interface connection to PRTG?

PRTG blocks port 80 although I'm using SSL on port 443. How to free port 80?
PAESSLER WEBSITE
Terms and conditions of Paessler AG

§ https://www.paessler.com/terms-conditions
Privacy policy
§ https://www.paessler.com/privacy-policy
103
4.4 Install a Cluster
PRTG offers one single failover cluster in all licenses, including the freeware edition. A single failover
cluster consists of two machines, master node and failover node. Each machine runs one installation of
PRTG. They are connected to each other and exchange configuration and monitoring data. You can run
a cluster with up to five cluster nodes.
Illustration of a Single Failover Cluster
For more information, see section Failover Cluster Configuration 3213 .
More
KNOWLEDGE BASE
What is the clustering feature in PRTG?

104
4.5 Enter a License Key
The license information consists of a License Key and the License Name. The License Key is a string
that consists of 10 blocks with six characters each.
Paessler PRTG Enterprise Monitor subscription licenses do not have a License Name.
License Information Example
License Key P10000-FFSEJ3-ZHGRD5-UR1CS9-U73FG2-G645F1-YVF1D0-

H83234-T0YUK0-A39KV2
License Name Example Organization
Your License Information

For the trial edition and freeware edition, you receive the required license information on the Paessler
web page when you download the trial edition of PRTG. When you install the trial edition, you usually do
not need to manually enter your license key, as the installation setup program extracts all the necessary
information from the file name. If the installer cannot extract the information from the file name or if other
issues occur, you might need to enter your license information manually.
For the commercial edition, you receive your license information from Paessler via email or in a license
document in the Paessler Software Shop and Customer Service Portal. When you install the commercial
edition, PRTG asks you to enter your license information during the setup process. We recommend that
you copy and paste the information.
If there are issues with the license information, PRTG asks you to verify your License Key and
License Name on the first login.
You can find the label License Owner in some documents from the Paessler shop. License Owner is
the same as License Name. PRTG might ask you for this information during installation or when you
change your license key 105 .
For more information about the different licenses, see section Available Licenses 21 .
Change License Key

Because PRTG already asks for a license key during installation, you usually do not need to manually
enter one afterward. However, there are still scenarios where you need to change your license key and
activate the respective license. For example, you must provide your commercial edition license key if
you want to upgrade from a freeware edition or trial edition, or if you want to upgrade your commercial
edition license to one with a higher sensor count.
To enter a new license key, follow these steps:
1. Log in to the PRTG web interface 127 .

2. Select Setup | License Information from the main menu bar 266 .
105
3. Click Change License Key. The Update Your License page appears where you can activate your new
license.
4. Select the activation type Automatic (online activation with optional HTTP proxy) if your PRTG core
server can connect to the internet.
Without internet access, you must select Manual (offline activation). The activation process
works a bit differently in this case and requires manual interaction. See section License Information 2976
for more information.
5. Enter your license information and click Update License.

6. PRTG connects to the Paessler activation server on port 443 and validates your license.
If everything works fine, you see the message Activation was successful as License Status at the top of
the page.
The PRTG core server needs an internet connection on port 443 to activate. If a proxy connection is
needed, see step 3 2976 on the Update Your License page. If the activation fails, you can also try an
offline activation.
For more information, see section License Information 2975 .
Update Your License: Click Change License Key
More
KNOWLEDGE BASE
How do I upgrade to a later edition of PRTG?

The automatic license activation of my PRTG Enterprise Monitor license does not work. What can I do?
106
4.6 Activate the Product
PRTG Network Monitor automatically activates your license via the internet during the installation
process. If PRTG cannot access the activation server, you must manually activate your license.
You must complete the product activation process once to use PRTG, otherwise it does not run. Do
not forget to activate your commercial license when you want to upgrade your trial edition or
freeware edition installation.
Online Activation
Because PRTG already asks for a license key during installation, you usually do not need to manually
enter one afterward. However, there are still scenarios where you need to change your license key and
activate the respective license. For example, you must provide your commercial edition license key if
you want to upgrade from a freeware edition or trial edition, or if you want to upgrade your commercial
edition license to one with a higher sensor count.
To enter a new license key, follow these steps:
1. Log in to the PRTG web interface 127 .

2. Select Setup | License Information from the main menu bar 266 .
3. Click Change License Key. The Update Your License page appears where you can activate your new
license.
4. Select the activation type Automatic (online activation with optional HTTP proxy) if your PRTG core
server can connect to the internet.
Without internet access, you must select Manual (offline activation). The activation process
works a bit differently in this case and requires manual interaction. See section License Information 2976
5. Enter your license information and click Update License.
6. PRTG connects to the Paessler activation server on port 443 and validates your license.
If everything works fine, you see the message Activation was successful as License Status at the top of
the page.
The PRTG core server needs an internet connection on port 443 to activate. If a proxy connection is
needed, see step 3 2976 on the Update Your License page. If the activation fails, you can also try an
offline activation.
Offline Activation
The following process only applies to PRTG Network Monitor. If you use PRTG Enterprise Monitor,
see the Paessler website: How to use PRTG Enterprise Monitor in an offline environment in 5 steps.
If no internet connection is available, you must activate PRTG manually:
1. In the PRTG web interface, select Setup | License Information from the main menu bar.
107
2. Click Change License Key. The Update Your License page appears where you can activate your
license.
3. Select the activation type Manual (offline activation).

4. Enter your license information and follow the instructions of step 3b 2977 and step 4 2977 on the Update
Your License page.
5. Click Update License.
If the activation was successful, you see the message Activation was successful as License Status at
the top of the page.
If your PRTG core server is offline, you need to manually activate your license each time. This
makes sure that you can install updates, for example. Your maintenance information has to be the
same as in the PRTG installer, so you need to activate your license offline before you install an update.
More
KNOWLEDGE BASE
Which servers does PRTG connect to for software auto-update, activation, etc.?
PAESSLER WEBSITE
How to use PRTG Enterprise Monitor in an offline environment in 5 steps
§ https://www.paessler.com/support/how-to/prtg-enterprise-monitor-offline
108
4.7 Install a Remote Probe
Remote probes can extend your monitoring with PRTG:
§ Monitor different subnetworks that are separated from your PRTG core server by a firewall, and keep
an eye on remote locations. You can install one or more remote probes 3203 .
§ Distribute monitoring load by taking it from the PRTG core server system and putting it on one or more
remote probe systems.
You need a classic remote probe if you want to monitor your local network with a PRTG Hosted
Monitor instance.
There are three types of remote probes:
1. Classic remote probe 3349

2. Multi-platform probe 3352
3. Mini probe 3352
You can use multi-platform probes to extend your monitoring to non-Windows systems. For more
information about multi-platform probes, see the Multi-Platform Probe for PRTG manual.
If you run PRTG in a cluster, see Cluster and Remote Probes Outside the LAN 112 in this section.
If you have issues after the installation, see section Debugging Classic Remote Probe Connection
Issues 118 .
For a partially automatic installation of a classic remote probe directly from the device tree in the
PRTG web interface, see section Classic Remote Probe Setup via Device Tools 3207 . For a quick
installation guide, see the Paessler website: How to install a PRTG remote probe in 4 steps.
Steps to Take
To install a classic remote probe with the Classic Remote Probe Installer, follow these steps:
§ Step 1: Meet the Requirements 109
§ Step 2: Prepare the PRTG Core Server 110
§ Step 3: Download the Classic Remote Probe Installer from the PRTG Web Interface 112
§ Step 4: Install a New Classic Remote Probe 113
§ Step 5: Approve the New Remote Probe 116
Step 1: Meet the Requirements

To install a classic remote probe on a target system, make sure that you meet the following
requirements:
§ The target system runs on at least Windows 7.
§ The target system is accessible via remote procedure call (RPC). This is usually the case when your
PRTG core server and the target system are located in the same LAN segment. Otherwise, open
Windows services.msc on the target system and start the RPC service.
109
§ Programs are allowed to communicate through your Windows Firewall. Open the settings of your
firewall and select Allow an app through firewall. Mark the check box for Remote Service Management,
and the check box Public in the corresponding line.
§ Because the remote probe initiates the connection, you must make sure that a connection to your
PRTG core server from the outside can be established. The process is the same as if you wanted to
allow access to the PRTG web server provided by the PRTG core server via port 80 or 443. In most
cases, this means that you will require an allow or allow-nat network address translation (NAT) rule
that enables a remote probe to reach the PRTG core server via the Transmission Control Protocol
(TCP) port 23560. Then, the remote probe uses a dynamic port from the high port range (49152 -
65535) for outgoing connections.
If you need to set a different port, which we do not recommend, see the Knowledge Base: How can I
customize ports for core-probe connections used by PRTG?
You cannot install a remote probe on a system that already has a probe installed.
For more information on the requirements for remote probes, see section System Requirements 24 .
If you are using PRTG Hosted Monitor, start from Step 3: Download the Classic Remote Probe
Installer from the PRTG Web Interface 112 .
Step 2: Prepare the PRTG Core Server.

Because remote probes need to connect to your PRTG core server, PRTG needs to accept
incoming remote probe connections. So, with PRTG Network Monitor, first prepare your PRTG core
server before you install a remote probe.
Edit the relevant settings in section Core & Probes 2897 . From the main menu in the PRTG web
interface 127 , select Setup | System Administration | Core & Probes to access the probe settings and go
to the Probe Connection Settings.
110
Probe Connection Settings in System Administration
Step 2.1: Probe Connection IP Addresses
By default, a PRTG core server accepts connections from the local probe only (IP address 127.0.0.1).
This setting is the most secure setting, but it does not allow any remote probes to connect to your
PRTG core server.
To accept remote probes, select one of the following settings:
§ All IP addresses available on this computer: Any IP address on your PRTG core server system
accepts incoming probe connections.
§ Specify IP addresses: Specify IP addresses that accept incoming connections.
Step 2.2: Allow IP Addresses
In the Allow IP Addresses field, you can enter the IP address of the target system on which you want to
install a remote probe. You can also enter the word any. This sets the PRTG core server to accept
remote probe connections from any IP address.
If you use any, make sure that you only write the word in lower case. Other variations are not valid.
111
Other settings are not required. For more information about the fields for Access Keys, Deny IP
Addresses, and Deny GIDs, see section Core & Probes 2900 .
When you are done, click Save to save your settings.
If you change this setting, PRTG needs to restart the PRTG core server to apply your changes. After
you click Save, a dialog box appears that asks you to confirm the restart. Click OK to trigger the
restart. During the restart, all users of the PRTG web interface, the PRTG app for desktop 2994 , or the
PRTG Apps for Mobile Network Monitoring 2998 are disconnected and reconnected.
To edit the core–probe connection settings, you can also use the PRTG Administration Tool 3051 on
your PRTG core server.
Cluster and Remote Probes Outside the LAN
If you run PRTG as a cluster and you want to run remote probes outside your local network, you
must make sure that your cluster nodes and the addresses that they use are reachable from the
outside. Check your cluster node settings under Cluster 2933 before you install a remote probe outside
your local network. Enter valid Domain Name System (DNS) names or IP addresses for both cluster
nodes to reach each other and for remote probes to individually reach all cluster nodes. Remote probes
outside your LAN cannot connect to your cluster nodes if they use local addresses.
If you already have a remote probe installed outside your LAN and the remote probe is disconnected
because of this, follow these steps:
1. Uninstall the remote probe.

2. Update the cluster node settings 2933 with addresses that are reachable from outside your LAN.
3. Restart the PRTG core servers.
4. Install the remote probe again. It then obtains the IP address or DNS name entries that it can reach.
See also section Failover Cluster Configuration 3215 , section Remote Probes in a Cluster.
Step 3: Download the Classic Remote Probe Installer from the PRTG Web Interface
1. On the Windows system on which you want to install a classic remote probe, log in to the PRTG web
interface.
2. From the main menu bar, select Setup | Optional Downloads | Classic Remote Probe Installer.
3. Click Add Remote Probe to start the installation assistant.
The Add Remote Probe button is also available in the device tree.
4. Wait until the installation is completed. The classic remote probe then automatically connects to
your PRTG core server.
5. In the appearing dialog window, click Prepare and Download to start the download.
6. Save the setup program to your local disk.
In the installation approach with the assistant, PRTG guides you through the installation process. If you
Download the Classic Remote Probe Installer directly, you must install the classic remote probe without
the assistant.
112
If you connect remote probes to PRTG Network Monitor, prepare 110 your Probe Connection Settings
first.
Add Remote Probe Assistant
The PRTG version numbers of the PRTG core server service and PRTG probe service must match.
PRTG automatically updates classic remote probes when you install a new version on the PRTG
core server. If PRTG advises you to manually update your classic remote probe, open a web browser on
the remote system and download the classic remote probe installer as described in this section.
Step 4: Install a New Classic Remote Probe

1. Execute the setup program that you downloaded.
2. Confirm the Windows User Account Control dialog with Yes to allow the installation. The usual
software installation wizard guides you through the installation process.
3. Click Install to start the installation process.
113
Remote Probe Setup Installing
Wait until the installation is complete. The remote probe then automatically connects to your PRTG core
server.
114
Remote Probe Setup Connecting to the PRTG Core Server
If the remote probe successfully connects to your PRTG core server, you can complete the setup of your
new remote probe.
To allow your new remote probe to connect to a PRTG Hosted Monitor instance, PRTG
automatically sets the Allow IP Addresses field in Core & Probes 2900 to any. You can also use any
for PRTG Network Monitor, but we recommend that you use this setting in intranets only. If any is not an
option for you, cancel it in the Allow IP Addresses field and enter the IP address of your remote probe
instead.
115
Remote Probe Setup Successful
4. Click Continue to finish the remote probe installation.

5. Click Finish to exit the installation wizard.
The remote probe is now installed on your computer as a Windows service.
Step 5: Approve the New Remote Probe

In the installation assistant, click Installation Done.
116
Confirm that Installation is Done
If you successfully installed the remote probe from a PRTG Hosted Monitor installation, you see the
following dialog box.
Approve Remote Probe for PRTG Hosted Monitor
Click Approve and auto-discover to include the new remote probe and network in your device tree and to
start the auto-discovery 270 . It discovers devices and automatically creates suitable sensors. Optionally,
click Approve to only approve the remote probe without the auto-discovery. The remote probe appears in
your device tree.
117
For unwanted remote probe connections, click Cancel. A new window appears in the lower-right corner.
Deny Remote Probe
Click Deny to deny the new remote probe.
If you deny or remove a remote probe, PRTG automatically adds the global ID (GID) of this device to
the Deny GIDs list in Core & Probes 2898 . PRTG automatically denies future remote probe
connections from this device.
If you deny the remote probe in the device tree, it does not uninstall the remote probe, but only
denies access to the PRTG core server. The remote probe continues to run on the target system
until you uninstall it manually.
Once approved, PRTG automatically opens the new remote probe in the device tree and creates a set of
sensors for the remote probe to make sure you can immediately detect bottlenecks on the remote probe
system. We recommend that you keep these sensors. You can now create groups, devices, and
sensors for monitoring via the new remote probe.
You do not need to approve classic remote probes after updates.
When a new remote probe connects to the PRTG core server for the first time, you receive a new ToDo
ticket.
PRTG automatically updates classic remote probes but, in rare cases, you must manually update
classic remote probes. You receive a ToDo ticket 216 in this case. Follow the steps above 112 to
manually update classic remote probes.
Debugging Classic Remote Probe Connection Issues

If you have issues with the connection between the PRTG core server and classic remote probe, make
sure that you meet the following requirements:
§ Recheck if you fulfilled all the requirements as described in step 1 109 of this section like the Windows
Firewall settings.
§ The IP address of the computer on which you want to install a remote probe is not listed in the Deny
IP Addresses field in Core & Probes 2898 .
§ You can also take a look at the log files of the classic remote probe. The probe process writes log files
with a file name in the format PRTG Probe Log (x).log. Open the one with the most recent date.
For a correct connection, the log should look similar to this:
118
11/6/2023 1:21:58 PM PRTG Probe V23.4.90.1235
11/6/2023 1:21:58 PM System time zone: (UTC+01:00) Amsterdam, Berlin, Bern, Rome,
Stockholm, Vienna
11/6/2023 1:21:58 PM libeay32.dll=1.0.2.11
11/6/2023 1:21:58 PM ssleay32.dll=1.0.2.11
11/6/2023 1:21:58 PM PRTG Probe "example-DNS" starting on "example-
DNS" (GID={AAAA1111-22BB-33CC-DD44-EEEEEE555555})
11/6/2023 1:21:58 PM Memory Manager: NexusMM4
11/6/2023 1:21:58 PM OS: Microsoft Windows 10 Enterprise (10.0 Build 15063), 4 CPUs
(Quad x64 Model 78 Step 3), code page "Windows-1252", on "NVME SAMSUNG MZFLV256"
11/6/2023 1:21:58 PM Data Path: C:\ProgramData\Paessler\PRTG Network Monitor\
11/6/2023 1:21:58 PM System Path: C:\Program Files (x86)\PRTG Network Monitor\
11/6/2023 1:21:58 PM Local IP: 0.0.0.0
11/6/2023 1:21:58 PM Core Server IP: example-DNS.exampledomain.com
11/6/2023 1:21:58 PM Core Server Port: 23560
11/6/2023 1:21:58 PM SSL Enabled
11/6/2023 1:21:58 PM Probe GID: {AAAA1111-22BB-33CC-DD44-EEEEEE555555}
[...]
11/6/2023 1:21:58 PM Start Connection
11/6/2023 1:21:58 PM Start Done
11/6/2023 1:21:58 PM (14608):Initializing WMIConnectionPool
11/6/2023 1:21:58 PM (14608):WMIConnectionPool maximum number of concurrent
establishings is set to: 20
11/6/2023 1:22:03 PM Connect from to example-DNS.exampledomain.com:23560
11/6/2023 1:22:03 PM TCP connected from 10.49.12.51:55199 to example-
DNS.exampledomain.com:23560
11/6/2023 1:22:03 PM State changed to connected (example-DNS.exampledomain.com:23560)
11/6/2023 1:22:03 PM Reconnect
11/6/2023 1:22:04 PM Connected
11/6/2023 1:22:10 PM Send Login
11/6/2023 1:22:10 PM Local: 11/6/2023 1:22:10 PM UTC: 11/6/2023 12:22:10 PM
11/6/2023 1:22:10 PM MarkUnused
11/6/2023 1:22:10 PM Login OK: Welcome to PRTG
If the connection fails, for example because of an incorrect Access Key, or because of incorrect IP
address settings (see step 2 110 ), you see:
11/6/2023 1:42:02 PM Try to connect...
11/6/2023 1:42:02 PM Connected to 10.0.2.167:23560
11/6/2023 1:42:07 PM Login NOT OK: Access key not correct!
If you need to adjust any settings for the connection to the PRTG core server, use the PRTG
Administration Tool 3077 on the remote probe system.
119
Remote Probe Settings in PRTG Administration Tool
Under Connection to PRTG Core Server, you can then edit the following settings:
§ Server (IPv4 Address or DNS Name): Enter the IP address or Domain Name System (DNS) name of
the PRTG core server that the remote probe is to connect to. If you use network address translation
(NAT) rules, you must enter the IP address that is externally visible, because the remote probe
connects from outside your network.
§ Access Key and Confirm Access Key: Enter the access key that the remote probe is to send to the
PRTG core server. You must define this access key on the PRTG core server in Core & Probes 2898 .
Make sure that the access keys match.
Click Save & Close to confirm your settings and to (re)start the PRTG probe service.
For more information about these settings, see section PRTG Administration Tool 3077 .
120
More
KNOWLEDGE BASE
How can I customize ports for core-probe connections used by PRTG?

I cannot open the PRTG web interface via the desktop shortcut anymore. What can I do?
What is the multi-platform probe and how can I use it?

PAESSLER WEBSITE
How to connect PRTG through a firewall in 4 steps

§ https://www.paessler.com/support/how-to/firewall
How to install a PRTG remote probe in 4 steps

§ https://www.paessler.com/support/how-to/remote-probe-installation
121
4.8 Uninstall PRTG Products
Whether you uninstall an entire PRTG installation or a remote probe installation, take the following steps.
Use the Windows uninstall routines to remove the software from your system.
For more information on how to uninstall a multi-platform probe, see the Multi-Platform Probe for
PRTG manual.
Step 1
From the Windows Start menu, run Uninstall PRTG Network Monitor or open your Windows Control
Panel and select the desired entry in the Programs and Features section. To uninstall a remote probe,
only the second option applies. Depending on the installed products, not all uninstall programs are
available.
Step 2
If asked, confirm the question of the Windows User Account Control with Yes to allow the program to
uninstall. The software uninstall dialog guides you through the uninstall process.
Step 3
Confirm the removal of the software with Yes.
Uninstall PRTG Netw ork Monitor Step 1
Step 4
Wait while the software is removed.
122
Step 5
Confirm a system restart with Yes.
123
Step 6
After the system restart, the software is removed, but there is still some custom data in the PRTG
program directory. If you have uninstalled an entire PRTG installation or a remote probe installation, your
monitoring data is still stored on the system. To completely remove all PRTG data, delete the PRTG
Network Monitor folder as well as the Paessler\PRTG Network Monitor folder in the PRTG data directory.
For more information, see section Data Storage 3218 .
Step 7
During the installation of PRTG, a component called Npcap is also installed on your system. After you
uninstall PRTG, you need to manually uninstall this feature. To do so, open your Windows Control Panel
and select Npcap 0.9983 in the Programs and Features section. Click Uninstall to remove this feature
from your Windows system.
If you updated to PRTG 19.2.50, you also need to manually uninstall the Npcap loopback adapter.
For more information, see the Knowledge Base: I have issues with additional services after updating
to PRTG 19.2.50. What can I do?
More
KNOWLEDGE BASE
I have issues with additional services after updating to PRTG 19.2.50. What can I do?
Can we remotely and silently uninstall a classic remote probe?

Multi-Platform Probe for PRTG
· Multi-Platform Probe for PRTG (PDF)
124
Part 5
Understanding Basic Concepts
1/9/2023 125
5 Understanding Basic Concepts
There are a number of basic concepts that are essential for understanding the functionality of PRTG. This
includes, for example, the underlying architecture of the monitoring system, the hierarchy of objects, the
inheritance of settings, the access rights management, and notifications.
In this section:
§ Architecture and User Interfaces 127
§ Failover Cluster 132
§ Object Hierarchy 136
§ Inheritance of Settings 140
§ Tags 142
§ Dependencies 144
§ Scheduling 145
§ Notifying 146
§ Access Rights Management 149
§ Data Reporting 153
§ IPv6 Support 154
126
5.1 Architecture and User Interfaces
In this section, you can find an overview of the components of PRTG and how it works.
Overview
You can classify the components of PRTG into three main categories: system parts, user interfaces,
and basic system administration tools.
Category Components
System Parts PRTG core server 128

This is the central part of a PRTG installation. The PRTG core server
includes the data storage, the web server, the report engine, the
notification system, and more. The PRTG core server is configured as a
Windows service that permanently runs.
Probes 128
This is the part of PRTG that performs the actual monitoring. There are
local probes, remote probes, and cluster probes in PRTG Network
Monitor, and there are hosted probes and remote probes in PRTG Hosted
Monitor. Probes forward all monitoring data to the central PRTG core
server. Probes are configured as services that permanently run.
We assume that all systems on which the PRTG core server with the
local probe or any remote probes run are secure. It is every system
administrator's responsibility to make sure that only authorized persons
can access these systems. For this reason, we highly recommend that
you use dedicated machines for your PRTG system parts.
User Interfaces PRTG web interface

With the Asynchronous JavaScript and XML (AJAX) based PRTG web
interface, you can configure devices and sensors, review monitoring
results, and configure the system administration and user management.
PRTG app for desktop 2994
The PRTG app for desktop is a cross-platform application that you can
use as an alternative interface for fast access to data and monitoring
management. With the PRTG app for desktop, you can connect to
several independent PRTG core servers or PRTG Hosted Monitor
instances to display their data and centrally manage your monitoring.
PRTG apps for mobile network monitoring 2998
With the PRTG apps for iOS and Android, you can monitor your network
on the go and receive push notifications in case of alerts.
System Administration PRTG Administration Tool on PRTG Core Server Systems 3051
Tools With the PRTG Administration Tool on the PRTG core server system, you
can configure basic PRTG core server settings in PRTG Network Monitor
such as the PRTG System Administrator user login, web server IP
addresses and the web server port, probe connection settings, the cluster
mode, the system language, and more.
127
Category Components
PRTG Administration Tool on Remote Probe Systems 3077

With the PRTG Administration Tool on the remote probe system, you can
configure basic remote probe settings such as the name of the remote
probe, IP address and server connection settings, and more.
PRTG Core Server

The PRTG core server is the heart of PRTG. It performs the following tasks:
§ Configuration management for target devices (for example, servers, workstations, printers, switches,
routers, or virtual machines (VM))
§ Management and configuration of connected probes
§ Cluster management
§ Database for monitoring results
§ Notification management including a mail server for email delivery
§ Report generation and scheduling
§ User account management
§ Data purging (for example, deleting data that is older than 365 days)
§ Web server and application programming interface (API) server
In a cluster 132 , the master node is responsible for all of these tasks.
The built-in and secure web server, for which you require no additional Microsoft Internet Information
Services (IIS) or Apache, supports HTTP as well as HTTPS (secured with Secure Sockets Layer
(SSL)/Transport Layer Security (TLS)). It serves the PRTG web interface when you access it via a
browser and also answers PRTG API calls.
The PRTG core server is configured as a Windows service that permanently runs. A logged-in user
is not required.
Probes
On the probe, PRTG performs the actual monitoring via the sensors that you created on a device (for
example, a computer, a router, a server, a firewall, and more). The probe receives its configuration from
the PRTG core server, runs the monitoring processes, and delivers monitoring results back to the PRTG
core server.
For PRTG Network Monitor, there is always a local probe that runs on the PRTG core server
system.
For PRTG Hosted Monitor instances, there is always a hosted probe that runs on the PRTG core
server system that Paessler hosts for you.
128
PRTG Core Server and Local Probe That Monitors a LAN
The actual monitoring is performed by probe processes that run on one or more systems.
The probes are configured as a Windows service that permanently runs. A logged-in user is not
required.
Probe Type Description
Local probe During the installation, PRTG automatically creates the local probe. In a
single-probe installation, which is the default setup, the local probe
performs all monitoring.
For PRTG Network Monitor, the PRTG core server with the local probe
inside the corporate LAN can monitor services and servers in the entire
LAN.
Hosted probe When you create a PRTG Hosted Monitor instance, the system
automatically creates the hosted probe. The hosted probe shows
monitoring values of the hosted instance and can monitor devices,
servers, and services that are publicly available in the internet like
websites.
Cluster probes In a cluster, a cluster probe runs on all cluster nodes. All devices that you
create on the cluster probe are monitored by all cluster nodes, so data
from different perspectives is available and monitoring continues even if
one of the cluster nodes fails.
Remote probes You can create additional remote probes to monitor multiple locations, to
monitor a LAN with PRTG Hosted Monitor, or for several other scenarios.
Remote probes use SSL/TLS-secured connections to the PRTG core
server. With remote probes, you can securely monitor services and
systems inside remote networks that are not publicly available or that are
secured by firewalls.
129
Probe Type Description
There are three types of remote probes: classic remote probes, multi-
platform probes, and mini probes.
For more information, see section Add Remote Probe 3201 .
For more information, see the video tutorial: Distributed monitoring
with PRTG.
Classic remote probes Classic remote probes extend your monitoring to other Windows systems
in your local or remote network.
For more information, see section Install a Remote Probe 109 .
Multi-platform probes You can install multi-platform probes on Linux systems in your local or
remote network. The multi-platform probe scans the network and sends
monitoring results to the PRTG core server 127 via a NATS server.
For more information, see the Multi-Platform Probe for PRTG manual.
Mini probes Mini probes let you create small probes on any device, not only on
Windows systems.
For more information, see section Mini Probe API 3158 .
Multi-platform probes You can install multi-platform probes on Linux systems in your local or
remote network. The multi-platform probe scans the network and sends
monitoring results to the PRTG core server 128 via a NATS server.
For more information, see the Knowledge Base: What is the multi-
platform probe and how can I use it?
More
PAESSLER WEBSITE
Getting started with PRTG

§ https://www.paessler.com/support/getting-started

VIDEO TUTORIAL
Distributed monitoring with PRTG

§ https://www.paessler.com/support/videos-and-webinars/videos/distributed_monitoring
130
What is a sensor?
§ https://www.paessler.com/support/videos-and-webinars/videos/what-is-a-sensor
131
5.2 Failover Cluster
A cluster consists of two or more PRTG core servers that work together to form a high-availability
monitoring system.
Cluster Concept
A cluster consists of at least two cluster nodes: one master node and one or more failover nodes, where
up to four failover nodes are possible. Each cluster node is a full PRTG core server installation that can
perform all of the monitoring and alerting on its own.
132
Cluster w ith Tw o Cluster Nodes
See the following table for more information on how a cluster works:
Feature Description
Connection and Cluster nodes are connected to each other with two TCP/IP connections.
communication They communicate in both directions and a single cluster node only
needs to connect to one other cluster node to integrate itself into the
cluster.
133
Feature Description
Object configuration During normal operation, you configure devices, sensors, and all other
monitoring objects on the master node. The master node automatically
distributes the configuration among all other cluster nodes in real time.
Fail-safe monitoring All devices that you create on the cluster probe are monitored by all
cluster nodes, so data from different perspectives is available and
monitoring continues even if one of the cluster nodes fails.
If the master node fails, one of the failover nodes takes over and controls
the cluster until the master node is back. This ensures continuous data
collection.
Active-active mode A cluster works in active-active mode. This means that all cluster nodes
permanently monitor the network according to the common configuration
that they receive from the master node. Each cluster node stores the
results in its own database. PRTG also distributes the storage of
monitoring results among the cluster.
PRTG updates You only need to install PRTG updates on one cluster node. This cluster
node automatically deploys the new version to all other cluster nodes.
Notification handling If one or more cluster nodes discover downtime or threshold breaches,
only one installation, either the primary master node or the failover master
node, sends out notifications, for example, via email, SMS text message,
or push message. Because of this, there is no notification flood from all
cluster nodes in case of failures.
Data gaps During the outage of a cluster node, it cannot collect monitoring data. The
data of this single cluster node shows gaps. However, monitoring data for
the time of the outage is still available on the other cluster nodes.
There is no functionality to fill these gaps with the data of other
cluster nodes.
Monitoring results review Because the monitoring configuration is centrally managed, you can only
change it on the primary master node. However, you can review the
monitoring results of any of the failover nodes in read-only mode if you log
in to the PRTG web interface.
Remote probes If you use classic remote probes in a cluster 3215 , each remote probe
connects to each cluster node and sends the data to all cluster nodes.
You can define the Cluster Connectivity of each remote probe in its
settings 536 .
You cannot add multi-platform probes to a cluster. For more
information about the multi-platform probe, see the Multi-Platform
Probe for PRTG manual.
134
Performance Considerations for Clusters
Monitoring traffic and load on the network is multiplied by the number of used cluster nodes.
Furthermore, the devices on the cluster probe are monitored by all cluster nodes, so the monitoring load
increases on these devices as well.
For most usage scenarios, this does not pose a problem, but always keep in mind the system
requirements 27 . As a rule of thumb, each additional cluster node means that you need to divide the
number of sensors that you can use by two.
PRTG does not officially support more than 5,000 sensors per cluster. Contact the Paessler
Presales team if you exceed this limit. For possible alternatives to a cluster, see the Knowledge
Base: Are there alternatives to the cluster when running a large installation?
Cluster Setup
For more information, see section Failover Cluster Configuration 3213 .
More
KNOWLEDGE BASE
What is the clustering feature in PRTG?

In which web interface do I log in to if the master node fails?

What are the bandwidth requirements for running a cluster?

Are there alternatives to the cluster when running a large installation?


PAESSLER WEBSITE

VIDEO TUTORIAL
How to set up a PRTG cluster

§ https://www.paessler.com/support/videos-and-webinars/videos/how-to-set-up-a-cluster
135
5.3 Object Hierarchy
PRTG arranges all objects in the monitoring configuration in a tree-like hierarchy. You can arrange the
objects in groups that monitor similar devices, services, or particular locations. You can also use this
hierarchical order to define common settings for larger groups of objects. The settings of the root group,
for example, apply to all other objects underneath in the object hierarchy by default.
For more information, see section Inheritance of Settings 140 .
Object Hierarchy in PRTG
Root Group
The root group is the topmost instance in PRTG. It contains all other objects in your setup. We
recommend that you adjust all default settings for the root group 436 . This is because all other objects in
the device tree inherit 140 these standard settings by default so that you do not need to set up the same
configuration for each object anew.
136
Probe
Each group is part of a probe (this excludes root group). This is where the actual monitoring takes place.
All objects that you add to a probe are monitored via that probe. In PRTG Network Monitor, every PRTG
core server installation automatically installs the local probe.
In PRTG Hosted Monitor, every instance has the hosted probe.
In a failover cluster 132 , there is an additional cluster probe that runs on all cluster nodes. All devices that
you create on the cluster probe are monitored by all cluster nodes, so data from different perspectives is
available and monitoring continues even if one of the cluster nodes fails.
You can add additional probes and remote probes to your configuration to also monitor remote devices
from outside your network.
Group
On each probe, there are one or more groups that have structural purposes. Use groups to arrange
similar objects so that they inherit the same settings. To a group, you add devices. You can arrange
your devices in different nested groups to reflect the structure of your network.
Here you can see a sample configuration of a device tree with the local probe, several groups, devices,
and their sensors:
Object Hierarchy in the Device Tree
137
Device
You can add devices that you want to monitor to each probe or group. Each device in your configuration
represents real hardware or a virtual device in your network, for example:
§ Web or file servers
§ Client computers (Windows, Linux, or macOS)
§ Routers or network switches
§ Almost every device in your network that has its own IP address
You can add devices with the same IP address or Domain Name System (DNS) name multiple
times. This way, you can get a more detailed overview when you use a large number of sensors or
you can use different device settings for different groups of sensors. The sensors on all of these devices
then query the same real hardware device in your network.
PRTG additionally adds the probe device to the local probe. This is an internal system device with
several sensors. It has access to the probe system and monitors the system's health parameters.
PRTG automatically analyzes the devices that you add and recommends appropriate sensors on the
Overview tab of the device. To create recommended sensors, click Add These Sensors in the
Recommended Sensors table.
For more information about the Overview tab, see the Knowledge Base: What options do I have to
review my monitoring data in detail?
You can turn off the sensor recommendation in the system administration settings under
Monitoring 2884 .
Sensor
On each device, you can create a number of sensors. Every sensor monitors one single aspect of a
device, for example:
§ A network service like Simple Mail Transfer Protocol (SMTP), File Transfer Protocol (FTP), or HTTP
§ The traffic on a network switch
§ The CPU load of a device
§ The memory usage of a device
§ The traffic on one network card
§ A NetFlow device
§ The system health of a device
§ And much more
For more information, see the video tutorial: What is a sensor?
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 channel can contain, for example:
138
§ Downtime and uptime of a device
§ Traffic in, Traffic out, or Traffic sum of a bandwidth device (for example, a router)
§ Mail traffic of a NetFlow device
§ CPU load of a device
§ Loading time, Download bandwidth, or Time to first byte of a web page
§ Response time of a ping request to a device
§ And much more
More
VIDEO TUTORIAL
What is a sensor?
§ https://www.paessler.com/support/videos-and-webinars/videos/what-is-a-sensor
139
5.4 Inheritance of Settings
The hierarchically structured 136 device tree organizes the devices in your network. This object hierarchy
is the basis for the inheritance of settings. Objects in the device tree can inherit their settings from a
higher level. For example, you can change the scanning interval of all sensors by editing the interval
setting of the root group (if you define no other setting underneath in the object hierarchy).
Inheritance to Child Objects

You can override the inheritance of settings to child objects at any level of the object hierarchy if you set
a different value for a specific probe, group, device, or sensor. All objects underneath inherit these new
settings. Object settings from higher levels do not inherit the new settings.
Settings that are inherited to all objects include:
§ Scanning intervals
§ Notification triggers 2704
§ Credentials for different systems
§ Compatibility settings for specific sensor types
§ Channel and unit configurations
§ Access rights 149
§ Tags 142
§ Paused status 184 : If an object is paused by the user or by a schedule, PRTG sets all sensors on this
object to the Paused status as well
There is one exception for devices and sensors. Sensors always inherit the IP Address/DNS Name
of a device and the compatibility settings. You cannot change these settings at sensor level.
Here you can see the Credentials for Windows Systems setting that the object inherits from the parent:
Inherited Credentials for Window s Systems
Click next to inherit from [parent object] to override the parent object's settings and enter new
settings for this object and all objects underneath in the object hierarchy.
140
Credentials for Window s Systems
Click Save for your settings to take effect. If you click after you enter your settings, the object
inherits the parent object's settings again and your object-specific settings do not take effect.
Default Settings in Root Group

For all settings except passwords, PRTG already includes a set of default values. The following settings,
for example, are inherited by all sensors from the root group:
§ A default scanning interval of one minute
§ SNMP v1 with the community string set to public (this is the default setting for most devices)
§ The dependency type Use parent (default)
§ And more
Before you set up your monitoring, we recommend that you review the root group settings and set the
default values to suit your setup. This includes the credentials for the different systems in your network
that you want to monitor (Windows, Linux, virtual servers, different vendors, and more).
For more information, see section Root Group Settings 436 .
Inheritance of Notification Triggers

If you add notification triggers at probe, group, or device level, these are also inherited to all sensors
underneath in the object hierarchy unless you manually disable the inheritance.
For more information, see section Notification Triggers Settings 2704 .
141
5.5 Tags
For every object in your setup, you can define tags in the object settings 204 to additionally categorize
these objects. Although some tags are predefined when you add objects 273 , you can add further tags.
For example, you can mark all bandwidth sensors that are especially important for you with the tag
bandwidthimportant.
View and Edit Tags in Basic Sensor Settings
To confirm a tag, use the Enter key, the Spacebar key, or a comma.
If you multi-edit tags, PRTG overwrites existing tags.
It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (())
or angle brackets (<>).
For performance reasons, it can take some minutes until you can filter for new tags that you added.
Inheritance of Tags
Tags in object settings are automatically inherited 140 by all other objects underneath in the object
hierarchy 136 . You can view inherited tags in section Parent Tags in the settings of a sensor, device, or
group.
For example, a device with the tag netflow automatically passes on this tag to all sensors that you add
to the device. This is useful, for example, if you include sensors by tag in reports settings 2776 . PRTG
adds all sensors with the tag netflow to the report so that you do not need to manually tag every single
sensor.
142
You cannot disable the inheritance of tags.
Filter by Tags
You can use one or more tags to filter table lists 221 for specific objects, or to add sensors to libraries 2748
and reports 2764 .
When you filter by tags, you can also use the plus sign (+) or the minus sign (-) to categorize tags as
must have or must not have.
§ Use a tag with a leading + to specify that objects with this tag must be included.
§ Use a tag with a leading – to specify that objects with this tag must not be included.
§ Use tags without a leading plus or minus sign to specify that objects need to have at least one of
these tags to be included.
The filter only shows an object if all three conditions are met. The order of the tags in a tag field does not
matter.
Examples
Here are some examples that show how to filter by tags:
§ If you enter –netflow, the table list, library, or report includes all objects that do not have this tag. With
the tags +netflow or netflow, you filter for objects that have this tag.
§ If you enter +netflow –bandwidthimportant, the table list, library, or report includes all objects that have
the tag 'netflow', but excludes all objects that have the tag 'bandwidthimportant'.
§ If you enter netflow bandwidthimportant, the table list, library, or report includes all objects that have
either the tag 'netflow' or the tag 'bandwidthimportant' or both tags.
Tag Display Limits

For performance reasons, PRTG has a display limit of 1,000 tags when you select Sensors | By Tag in
the main menu bar 257 . If you have more than 1,000 tags, PRTG shows no tags here. You can, however,
still use tags for filters and searches, for example.
143
5.6 Dependencies
You can use dependencies to pause sensors based on the status 184 of a different (master) sensor to
avoid false alarms and incorrect downtime recording. A dependency stops the monitoring of one sensor
or a set of sensors as soon as the parent sensor shows the Down status or if the parent sensor shows
the Paused status because of another dependency. This means, for example, that you can stop
monitoring remote network services when the corresponding firewall is down because of connection
problems.
When you use the auto-discovery 270 feature, PRTG sets the Ping sensor of a device as the master
object for the device by default. This means that monitoring for the entire device is paused if the Ping
sensor shows the Down status or if it shows the Paused status because of a dependency. Usually, it
makes little sense to monitor any other parameters while the Ping sensor indicates that the device is
unavailable.
You do not trigger a status change by dependency 144 if you manually pause a master object or if
you pause it by schedule 145 . For more information, see the Knowledge Base: Why will dependent
objects not automatically pause when I pause the master object?
If a sensor shows the Paused status because of a dependency, the objects that use the sensor as
parent also show the Paused status.
To view the list of dependencies, select Devices | Dependencies and the corresponding dependencies
path from the main menu bar 254 . From there you can also access the dependencies graph 2738 that
visualizes all dependencies in your network.
Dependencies Graph
For more information about the dependency settings, see the settings of the object 204 for which you
want to set a dependency, section Schedules, Dependencies, and Maintenance Window.
More
KNOWLEDGE BASE
Why will dependent objects not automatically pause when I pause the master object?
144
5.7 Scheduling
With schedules, you can specify active and inactive time spans for monitoring. For example, you can
choose to monitor only on Sundays between 16:00 and 20:00. If you use scheduling, PRTG
automatically pauses 230 specific objects outside of the scheduled active times. A sensor in the Paused
status 184 does not collect monitoring data, does not change its status, and does not trigger any
notifications 146 . You can also pause monitoring for planned system maintenance windows to avoid false
alarms. You can apply different schedules to every object. PRTG also uses schedules for reports and
notifications.
You do not trigger a status change by dependency 144 if you manually pause a master object or if
you pause it by schedule 145 . For more information, see the Knowledge Base: Why will dependent
objects not automatically pause when I pause the master object?
Available Default Schedules in Device Settings
Schedules are user account specific. To change the predefined schedules or to add your own schedules,
see section Schedules 2856 .
If you use a cluster with cluster nodes in different time zones, the schedule applies at the local time
of each cluster node. For more information, see section Failover Cluster Configuration 3213 .
More
KNOWLEDGE BASE
145
5.8 Notifying
PRTG keeps you or other responsible people informed about the status of the network. There are several
methods that you can use to stay up to date.
Internal Sensor Alerts

Alerts are an important part of monitoring that informs you when there are issues, when values exceed
limits, or when a sensor status changes, for example. Some sensors display internal alerts in case of
errors, for example, disconnected probes or socket and timeout errors. There are also sensors whose
internal sensor alerts you can modify. To see if you can modify an alert, check the sensor's settings for
customizable options.
Here is an example of a sensor that is in the Down status 184 because of an internal sensor alert.
Probe Health Sensor w ith Disconnected Probe Alert
HTTP sensors, for example, show preconfigured internal alerts based on specific HTTP status codes.
For more information, see the Knowledge Base: Which HTTP status code leads to which HTTP
sensor status?
Channel Limits
There are also alerts that are triggered by limits that you can set in the channel settings 2692 of a sensor.
PRTG triggers a sensor status 184 change when a sensor measures values that exceed or fall below a
defined limit. For example, you can set an SNMP CPU Load sensor to the Down status when it
measures values that you consider critical. This sensor then appears in the alarms 205 list as well.
This type of alert only applies when a value breaches the configured limits. If the value is normal
again in the next sensor scan, the sensor shows the Up status again.
The value type that you need to configure for limits depends on the type of data that the channel
returns. You can set absolute values or delta values 2701 .
For more information, see the video tutorial: How to set channel limits.
146
Lookups for Channels
PRTG also uses lookups for some sensors. In general, lookups make data more human friendly because
they map status values that a device returns, usually integers, to more informative expressions in words
that show you the status of a target device in plain text.
SNMP HP LaserJet Hardw are Gauge
Additionally, lookups can define the sensor status in combination with specific status codes. For
example, a sensor can show the Unknown status if a channel value, provided by lookups, indicates that
the device is Inactive, instead of displaying a numeric value like -1.
You can also modify preconfigured lookups or create your own custom lookups.
For more information, see section Define Lookups 3186 .
Notifications
PRTG can send a notification 2745 when it discovers, for example, downtime, an overloaded system,
threshold breaches, or similar situations. Notifications use various methods 2825 to notify you of issues.
After you create notification templates 2818 in the system settings, you can select the templates on the
Notification Triggers tab of probes, groups, devices, and sensors, as well as the root group.
The status or the data of a sensor can also trigger notifications. With this mechanism, you can configure
custom external alerts. Which notification triggers 2704 are available depends on the kind of object you
edit. You can define notification triggers that are activated by an 'on change' event. Some sensors offer
the option to trigger a notification whenever sensor values change.
For more information, see section Notifications 2745 .
Alarms
The alarms list shows all sensors that are in the Down, Down (Partial), Down (Acknowledged), Warning,
or Unusual status. Sensors in the Up, Paused, or Unknown states do not appear here.
For more information, see section Alarms 205 .
147
Logs
The logs list shows the log file that includes all monitoring events. PRTG documents the activity of every
single object, so you can use this data to check if your setup works as expected.
For more information, see section Logs 213 .
Tickets
The tickets list shows tickets with important system information or actions that you need to take. We
recommend that you view every ticket and take appropriate action. By default, PRTG sends an email to
the PRTG System Administrator user for every new ticket that the system or a user creates. If a ticket is
assigned to a specific user, this user also receives an email by default.
For more information, see section Tickets 216 .
More
KNOWLEDGE BASE
Which HTTP status code leads to which HTTP sensor status?

VIDEO TUTORIAL
How to set channel limits

§ https://www.paessler.com/support/videos-and-webinars/videos/how-to-set-channel-limits
148
5.9 Access Rights Management
With the access rights management, you can define which user in which user group can access which
objects in your PRTG installation, and you can manage all user access rights and group access rights.
You can create a nearly unlimited number of other users, which you can organize in a nearly unlimited
number of user groups. Each user group can have separate access rights 149 for each object in the
device tree except channels, as well as for libraries, maps, and reports. Objects can also inherit 140
access rights according to the object hierarchy 136 .
User Access Rights Overview

Each user also has specific access rights. There are administrators who are user group members with
administrative rights, read/write users, and read-only users. You can define the user type in the user
account settings (read-only user or read/write user).
For more information, see section User Accounts 2911 .
User Access Rights in User Accounts Settings
Individual user access rights, combined with the access rights of the groups that the user is a member
of, determine the access rights for device tree objects, libraries, maps, and reports. In general, group
access rights override user access rights unless a user is a read-only user. Read-only users always
have only read access.
You can define the group access rights for each object in the device tree via the corresponding context
menus 232 or in the object settings 204 .
Group Access Rights Overview

The following classes of group access rights are available, in hierarchical order (from the lowest group
access right to the highest group access right).
The access rights apply to device tree objects and to libraries, maps, and reports.
149
Group Access Rights Description
No access The members of the user group cannot see or access the object. They
also cannot see or access logs, tickets, or alarms for the object.
Read access The members of the user group can only view the object and its settings.
Read-only users who have been explicitly allowed to acknowledge
alarms and read/write users in a user group that has read access
can still acknowledge alarms. For more information, see section User
Accounts 2916 .
Write access The members of the user group can view the object and edit its settings.
They can also add and delete objects, acknowledge alarms, edit
notification templates, notification contacts, and schedules.
Full access The members of the user group can view the object and edit its settings.
They can also add and delete objects, acknowledge alarms, edit
notification templates, notification contacts, and schedules. In addition,
they can edit group access rights for objects.
If a user group has administrative rights, all user group members always have full access to every object
in the device tree, library, map, and report, and all other functionalities and features of PRTG.
Group access rights that you define directly on an object, for example a device, override inherited
rights. If you do not define group access rights directly on an object, PRTG checks the next object
that is higher up in the object hierarchy for group access rights until there is no higher-level object
available.
Different Access Rights Depending on User Groups
Users are either members of PRTG user groups or of Active Directory groups. They cannot be
members of both types of user group. We recommend that you use only one type of user group to
minimize administration.
150
Group Access Rights in Combination with User Access Rights
The following table shows the correlation between group access rights and user access rights. The table
applies to both PRTG user groups and Active Directory groups, as well as to both PRTG users and
Active Directory users. The column headings show the group access rights to an object. The row
headings show the type of user.
Group Access Rights and User Access Rights Combined
User group has read User group has write User group has full Administrator
access to an object access to an object access to an group
object
Read-only Read access Read access Read access n/a

user
Read/write Read access Write access Full access Full access

user
Administrator Full access Full access Full access Full access
The following rules apply:
§ Read-only users
ú always have only read access, no matter what access rights you define for the user groups they are
members of.
ú can never see or use the ticket system.
ú can acknowledge alarms and change their own password in their user account settings, if an
administrator allows them to.
ú can never be members of user groups with administrative rights.
§ Read/write users
ú can use the ticket system if the user group they are members of has access to the ticket system.
ú can acknowledge alarms.
ú can change their own password.
ú can have full access to device tree objects, libraries, maps, and reports, if the user group they are
members of has full access to the respective object.
ú always have administrative rights if they are members of a group with administrative rights.
§ Administrators
ú are members of groups with administrative rights.
ú have no access restrictions at all.
151
ú can also manage user accounts, user groups, and cluster setups.
ú can change the monitoring configuration of PRTG.
If a user is a member of more than one user group, the group access rights of the user group with
the highest access rights apply.
152
5.10 Data Reporting
With PRTG, you can view, analyze, and review monitoring data for specific time spans. There are several
ways to create customized data reporting.
View Historic Sensor Data

To get an overview of a single sensor's historic data, you can generate historic data reports via the
sensor's Historic Data tab.
For more information, see section Historic Data Reports 188 .
Generate Reports
In addition to reports about a single sensor's historic data, you can also create comprehensive and
detailed reports for all monitoring data.
For more information, see section Reports 2764 .
Export Data with the PRTG API

You can also export all raw monitoring data to .xml or .csv files and generate your own reports with any
third-party software.
For more information, see section Application Programming Interface (API) Definition 3094 .
Make Data Available

You can make monitoring data available to others via a specific read-only user, or you can create public
HTML pages to display your monitoring data via the Maps feature.
For more information, see section Access Rights Management 149 and section Maps 2786 .
153
5.11 IPv6 Support
PRTG supports the IPv6 protocol for most sensors. You can choose whether you want to query data
from your network devices via an IPv4 or IPv6 connection. Specify your preference in the device
settings 612 . The sensors you add to the device use the protocol that you select.
In the IPv6: Outgoing IP for Monitoring Requests setting of the PRTG Administration Tool 3068 , you can
additionally select the IPv6 address that PRTG uses for outgoing monitoring requests. The same option
is also available for IPv4.
Not all sensors are IPv6 compatible. Incompatible sensors are not selectable on IPv6 devices. For
an overview list of all sensors, including the IP version that they support, see section Available
Sensor Types 3237 .
The hosted probe of a PRTG Hosted Monitor instance does not support the IPv6 protocol. If you
want to use sensors that support IPv6, add them to a remote probe device.
154
Part 6
Basic Procedures
3/5/2024 155
6 Basic Procedures
The following sections introduce the basic features and concepts of PRTG:
§ Login 157
§ Welcome Page 161
ú Customer Service 165
§ General Layout 168
§ Sensor States 184
§ Historic Data Reports 188
§ Similar Sensors 195
§ Recommended Sensors 200
§ Object Settings 204
§ Alarms 205
§ System Information 208
§ Logs 213
§ Tickets 216
§ Working with Table Lists 221
§ Object Selector 225
§ Priority and Favorites 227
§ Pause 230
§ Context Menus 232
§ Hover Popup 251
§ Main Menu Structure 253
156
6.1 Login
For PRTG Network Monitor, you can log in to the PRTG web interface once the PRTG core server is
installed. In your browser, open the IP address or Domain Name System (DNS) name of the PRTG core
server system and click Log in.
You can look up and change the web server settings of PRTG Network Monitor at any time in the PRTG
Administration Tool 3051 on the PRTG core server system. In particular, when you access PRTG from the
internet, you should use a Secure Sockets Layer (SSL)/Transport Layer Security (TLS) secured
connection. To secure your connection, click Switch to SSL/TLS under Enable SSL/TLS for the PRTG
web interface on the welcome screen.
Load the PRTG Web Interface

In a web browser, enter the IP address or URL of the PRTG core server system. If you use a cluster,
connect to the master node. You can also double-click the PRTG Network Monitor desktop icon on the
PRTG core server system.
If you run PRTG on localhost, do not use the DNS name http://localhost to log in to the PRTG web
server, as this might considerably slow down the PRTG web interface. Use your local IP address or
http://127.0.0.1 instead.
If you see an SSL certificate warning in your browser, you can usually confirm it.
For more information, see the Knowledge Base: Why does my browser show an SSL certificate
warning when I open the PRTG web interface?
Login Screen
After loading the PRTG web interface, the login screen is visible. You can either log in as the predefined
PRTG System Administrator user or as any other user. As an administrator, you can use all
functionalities of the PRTG web interface. Administrators can create additional users 2911 with
administrative rights or users with more restricted user access rights (for example, read-only users).
157
Login Screen
Log In as Predefined Administrator (First Time Login)

This option is not available in PRTG Hosted Monitor.
When you log in for the first time, the login name and password for the predefined PRTG System
Administrator user account are both prtgadmin. PRTG automatically fills in the default credentials and
shows the password in plain text.
After login, you should change the default password. To do so, go to Setup | Account Settings | My
Account and specify a new password in section User Account Settings.
If you are not logged in to the PRTG web interface, you can change the credentials for the predefined
user account at any time in the PRTG Administration Tool.
If you enter a different login name or change your password, the password is no longer shown in
plain text.
158
Log In as User
If you received user credentials from your system administrator, enter them in the login screen to log in
to the PRTG web interface. This also applies if you use other administrator credentials.
Login Options
§ Log in: Log in to the fully featured PRTG web interface. We recommend that you use this option for
PRTG whenever possible. It offers the full functionality of PRTG. Use Google Chrome 75 or Mozilla
Firefox 67 for best performance.
Make sure that a supported browser 23 is available on the system.
§ Download apps for Windows, macOS, iOS, Android (optional): Opens Setup | Optional
Downloads in the PRTG web interface. You can optionally download 2984 the PRTG apps 2998 for iOS or
Android or the PRTG app for desktop 2994 .
If you use this download option, you require your login name and password for the login (or the
default credentials).
Only Google Chrome 75 and Mozilla Firefox 67 are fully compatible with the PRTG web interface.
Enter specific credentials or use the default credentials that PRTG fills in automatically. Click Log in to
proceed to the PRTG web interface.
Recover Password
If you cannot remember your PRTG Network Monitor password, click the Forgot password? link. The
Password Recovery page opens. Enter your Login Name, click Request a New Password, and PRTG
sends an email to the primary email address of your user account. Click the link in the email to set a
new password. The link is valid for 60 minutes. Enter a New Password, then enter it again under Confirm
Password. Click Set New Password to change your password.
The password must be at least 8 characters long and must contain a capital letter and a number.
When the password is successfully reset, all active user sessions of this user account are logged
out. Log in again with the new password.
Login Screen with Single Sign-On (SSO)

After you configure SSO 2935 , you see a new button on the login screen of the PRTG web interface.
159
Log in w ith SSO
Click Log in with single sign-on to continue with the login procedure of the single sign-on provider. After
finishing the login procedure, you will be transferred back to PRTG.
More
KNOWLEDGE BASE
160
6.2 Welcome Page
After you completed the smart setup 42 , you see the Welcome page by default when you log in to the
PRTG web interface. The collected information about your PRTG installation makes the page a good
starting point for your daily monitoring activities. You can set a different home page in your account
settings 2816 . Of course, you can also use the Maps 2786 feature to create customized dashboards that
you can use as your home page.
This documentation refers to an administrator that accesses the PRTG web interface on a master
node. Other user accounts, interfaces, or failover nodes might not have all of the options in the way
described here. In a cluster, note that failover nodes are read-only by default.
Welcome to PRTG
Sensor Overview
The Welcome page displays various information about your PRTG installation and is similar to a
dashboard. It keeps you informed about all sensors and alarms:
Sensor Overview on the Welcome Page
161
§ Click Sensors to open the top 10 lists 257 for sensors.
§ Click View All Alarms to open a list of alarms 205 in your installation.
§ Click a sensor status 184 to open a list of all sensors with the corresponding status.
My PRTG Section
In the My PRTG section, you can directly access different pages in the PRTG web interface.
My PRTG Section on the Welcome Page
Option Description
View Results Open the device tree 168 that shows your monitoring results.
Install PRTG Apps Open the download page for the PRTG apps for iOS or Android 2984 .
Install PRTG MultiBoard Open the download page for PRTG MultiBoard 2984 .
Get Help and Support Open the Help and Support Center 2986 from where you can access the
PRTG Manual, the Knowledge Base, and video tutorials. You can also
open support tickets 2987 and contact our customer service 165 from this
page.
Manage Subscription This option is only visible if you use PRTG Hosted Monitor.
Open your PRTG Hosted Monitor dashboard and manage your

subscriptions.
162
Other Sections
Other sections are, for example, the License Status section, the Yesterday's Activity section, the
Paessler Blog section, and the Update Available section.
License Status Section and Yesterday's Activity Section on the Welcome Page
Section Description
License Status Shows the number of your remaining maintenance days for PRTG
Network Monitor and the number of sensors that you can still add with
your license. Click <%B_Manage_License%> to open the Paessler shop
and manage your license. Click Get More Sensors to open the Paessler
shop and upgrade your license. See also section License Information 2972 .
For technical reasons, the number of available sensors that is

displayed here does not include sensors in the Paused status
because they do not count towards the maximum number of sensors that
your license allows. Add the number of your sensors that are in the
Paused status to the displayed number to know exactly how many
sensors are still available on your installation.
If you use a PRTG Network Monitor license with an unlimited number
of sensors, PRTG takes 10,000 sensors as the starting point to
calculate the number of available sensors that is displayed here. Consider
the system requirements 23 for a recommended PRTG core server setup
and click Recommended Setup for more information.
Yesterday's Activity Shows what your PRTG core server or PRTG Hosted Monitor instance did
for you on the day before. Hover over the mini graph to show the number
of sensor scans on a specific day. See also the Activity History in section
System Status 2958 . Click Show Tickets under My Open Tickets to display
all open tickets that are assigned to you.
163
Section Description
Paessler Blog Shows recent information about PRTG and Paessler. Click the heading of
an article to open it on the Paessler website.
Update Available This section is only visible if an update is available. It shows the version
number of your PRTG Network Monitor installation and the version
number of the latest available PRTG version. You see the label NEW if a
newer version is available. Click Install Update to open the Auto-
Update 2979 page.
Further options
There are some further options on the Welcome page, for example, you can set a secure password or
enable SSL/TLS for the PRTG web interface.
Further Options on the Welcome Page
§ If your PRTG Network Monitor installation is not Secure Sockets Layer (SSL)/Transport Layer Security
(TLS) secured, PRTG asks you to enable SSL/TLS for the PRTG web interface. Click Switch to
SSL/TLS and in the Do you want to switch to SSL/TLS? dialog, click Yes, switch to SSL/TLS to
enable SSL/TLS. See also section User Interface 2865 . Click to remove this note.
§ If you still use the default password of the PRTG System Administrator user (prtgadmin) for PRTG
Network Monitor, PRTG asks you to set a secure password if your PRTG web interface is publicly
available. Click Change Default Password to define a new password. See also section User
Accounts 2914 . Click to remove this note.
§ In the video section, you find informative videos about monitoring with PRTG. Click a video to open it
and play it on the Paessler website.
164
6.2.1 Customer Service
If you have any questions about license purchases or upgrades, you can directly contact the Paessler
Customer Service from the Help and Support Center 2986 in the PRTG web interface. We readily assist
you with quotes or information about licenses, and guide you through the purchasing process. Our
Customer Service team is also happy to send you the contact information of a knowledgeable PRTG
partner in your region or research any technical specifications you might need beforehand.
PRTG securely transmits your feedback or questions to Paessler via the PRTG Cloud. Make sure
that your PRTG core server has access to the internet and can reach the URL
https://api.prtgcloud.com:443 for successful transmission.
165
Contact Paessler Customer Service Form
166
Ask a Question or Give Us Your Feedback
Provide the following information in this section of the Contact Paessler Customer Service form.
Field Description
Your Name Enter your full name for contact information.
Your Email Address Enter an email address with which we can reach you.
Your Country Select the country in which you run PRTG so that we can provide you
with contact information for a partner nearby.
Your Phone Number Enter a phone number with which we can reach you.
How Can We Help? Select the scope of your question.
Emotional State If you want to, you can indicate your feelings about PRTG and your
purchase process.
Describe Your Question Provide a short description that indicates the topic of your request.
in One Sentence
Do You Have Any Further Enter your comments here. This can be feedback or any questions for our
Comments? customer service.
Click OK to send your question or feedback to our customer service. Click Cancel to close the customer
service contact form without sending it.
If you have technical questions about your setup, contact the Paessler support team 2987 .
167
6.3 General Layout
This section provides a general overview of the structure of the PRTG web interface. The central focus is
the Devices view, which you can select via the main menu bar 254 . The Devices view presents the device
tree and your monitoring results.
In this section:
§ Welcome Page 168
§ Device Tree View Layout 168
§ Navigation 171
§ Global Header Area 172
§ Page Header Bar 174
§ Page Content 175
§ Switch Device Tree View 178
§ Classic Device Tree View 178
§ Extended Device Tree Views 179
§ Add Button 182
§ Default Objects in the Device Tree 182
§ Priority and Favorites 183
Welcome Page
When you log in to the PRTG web interface, you see the Welcome page 161 by default. You can set a
different home page in your account settings 2816 .
Click View Results to open the device tree.
Device Tree View Layout

Click View Results on the Welcome page or select Devices from the main menu bar to display the
device tree.
Device Tree
168
Device Tree
From top to bottom, the device tree page has several areas that are covered in further detail in this
section. For a general overview of the device tree page, see the table below.
Global Header Area
Global Header Area
Item Description
Global header This area contains the main menu bar at the very top, the global status bar,
area 172 breadcrumbs that show the path to the selected object, a quick search box,
and the logout button.
Page Header Bar
Page Header Bar
Item Description
Page header bar 174

This area contains the page heading with the name of the selected object,
several tabs with settings, and quick action buttons.
Page Content
169
Page Content
Item Description
Page content 175

This area contains information about the selected object and all other objects
underneath in the device tree hierarchy, the object's status bar, a quick
search box, the QR code that links to the URL of the selected page, and
graphs for different time spans.
View Options
View Options
Item Description
Viewing options 178 These are part of the page content. Here you can adjust how your device tree
is displayed.
Footer Section
Footer Section
170
Item Description
Page footer This area shows information about the version of PRTG, the logged in user
account, and the time (depending on the time zone settings 2918 for the logged
in user).
Pause ( ) A timer counts down how much time remains until the next automatic page
refresh. Click Pause to pause the refresh timer and click Resume to resume.
Resume ( ) If you open a different page while the refresh timer is paused, the timer
resumes automatically and starts with the defined Refresh Interval (Sec.) that
Auto-Update ( ) you can configure in your account settings.
Contact support ( ) Long table lists 221 that are set to display 1000 items at a time are
excluded from the automatic refresh to ensure system performance.
Help ( )
Click Auto-Update for quick access to the auto-update 2979 settings if a new
version is available. To open the Contact Support form 2987 , click Contact
support. For context-sensitive help, click Help.
If you run PRTG in a cluster, you also see a cluster-related element. It shows
the name of the cluster node that you are logged in to and displays whether
this is a master node or a failover node. Click the bar to show the cluster
status 2970 . On a failover node, you can review all data, but PRTG does not
save changes in the settings. To change the settings, log in to the master
node.
Navigation
To navigate the PRTG web interface, the following options are available:
§ The main menu bar provides access to all important aspects of the software.
§ The quick search is often the fastest way to find a specific object (for example, a sensor or a device).
§ The clickable breadcrumbs show the path to a selected object in the object hierarchy.
§ Click an object to see its details. In the page heading of the page header bar, you always see the
name of the object that you have selected.
§ Use the page tabs to switch between various subpages.
§ Right-click objects to open their context menu 232 .

§ Hover over objects to display tool tips. Hover longer to open a quick-access window (hover popup 251 ).
§ Drill down into the object hierarchy of probes, groups, devices, and sensors in the device tree. To do
so, click a subobject of the displayed object (for example, click a sensor on the Overview tab of a
device).
These navigation options offer complete access to the functionality of PRTG.
In the following sections, we describe the different areas of the PRTG web interface.
171
Global Header Area
Global Header Area
Global Header Area
The global header area of the PRTG web interface provides important, very condensed information about
your installation and offers access to all content and settings. The following table lists the elements that
make up the global header area.
Main Menu Bar
Main Menu Bar
Item Description
Main menu bar To navigate the PRTG web interface, the main menu bar is the best starting
point. We recommend that you take a few minutes to familiarize yourself with
the main menu bar and its submenus.
For more information, see section Main Menu Structure 253 .
New Alarms
New Alarms
Item Description
New alarms, New The information boxes show how many new alarms, new log entries, and
log entries, Updated updated tickets have occurred. Click the respective box to view the lists of
tickets alarms 205 , logs 213 , or tickets 216 .
Global Sensor Status Symbols
Global Sensor Status Symbols
172
Item Description
Global sensor This area shows the accumulated states of all configured sensors, grouped
status symbols into the different sensor states. You see boxes with numbers that show the
amount of sensors that are in the respective status. For example, you can see
how many sensors are in the Up, Down, or Warning status. Click a box to view
a list of all sensors that are in the respective status.
For more information, see section Sensor States 184 .
Search Box
Search Box
Item Description
Search ( ) You can start a Search or Log out in the top-right corner.
Log out ( ) To search for an object, enter a name, parts of a name, an IP address, a
Domain Name System (DNS) name, or a tag in the search box and confirm
with the Enter key. PRTG performs a string search in your entire monitoring
setup, including groups, devices, sensors, libraries, maps, reports, tickets,
and object comments.
A page with items and online help articles that are related to the search term
opens.
Breadcrumbs
Breadcrumbs
Item Description
Breadcrumbs Below the main menu bar, PRTG shows a path that retraces the steps back to
the Welcome page (or your defined starting page). Use these breadcrumbs to
navigate back to where you came from.
If you click on a breadcrumb item, a dropdown list opens that shows all
objects on the same level. You can either search for an object or select one
directly. For example, you can directly access all other sensors on a device,
other devices within a group, and other groups on the same probe. Other
probes in your root group are also available.
173
Page Header Bar
Page Header Bar
The page header bar below the global header area consists of the following elements.
Page Heading
Page Heading
Item Description
Page heading The page heading displays the selected object's type and name. In the
screenshot, this is the group that is called Root. Here you can define the
Priority star ( object's priority as well. To do so, click one of the five stars on Priority star
) next to the object's name (this setting is not available for the root group).
For more information, see section Priority and Favorites 227 .
Quick Action Buttons
174
Item Description
Quick action On the right-hand side, there is a row of icons for several actions. Depending
buttons on the selected page, you can Pause and Resume the object. You can also
open the Settings of the object, Add a ticket, Send a link to the selected page
Pause ( ) per email, or Perform an immediate scan.
Resume ( ) Click on Context menu to open the context menu of the selected object for
further options.
Settings of the
object ( ) For more information, see section Context Menus 232 .
Add a ticket ( )
Send a link to the
selected page per
email ( )
Perform an
immediate scan (
)
Context menu ( )
Tabs General Layout
Tabs General Layout
Item Description
Tabs Via tabs, you can navigate to the various subpages of an object, for example,
to its monitoring data or settings.
For more information, see section Object Settings 204 and the Knowledge
Base: What options do I have to review my monitoring data in detail?
Page Content
The page content of the general layout varies depending on the selected object. It shows information
about the object and all other objects underneath in the object hierarchy. The deeper down in the
hierarchy you can find a selected object, the more detailed is the displayed information.
175
Page Content
Sensor Status Bar
Sensor Status Bar
Item Description
Sensor status bar This element is visible when you view a probe, a group (including the root
group), or a device. It is not available on the Overview tab of a sensor. The
sensor status bar shows the accumulated states of all sensors for the
selected object, grouped into different sensor states. They show the
number of sensors that are in the respective status.
For example, you can see how many sensors are in the Up, Down, or
Warning status. You can hide sensors that are in a certain status by
clicking the respective status icon. To show the sensors again, click the
status icon again.
For more information on sensor states, see section Sensor States 184
.
View Options
View Options
176
Item Description
Viewing options This element is only visible when you view a probe or a group. It is not
available when you view device or sensor details. For a detailed
description, see Switch Device Tree View 178 below.
Device Tree Search
Device Tree Search
Item Description
Device tree search In the search box to the right of the viewing options, enter a keyword to
search the device tree for matching items. The device tree highlights
matching devices and sensors by graying out all others. This gives you a
quick overview of sensors that monitor a specific part of your network. For
example, you can enter the keyword firewall to highlight devices and
sensors that match this string.
Add Button
Item Description
Add ( ) Click Add to add new objects to your monitoring setup. For a detailed
description, see Add Button 182 below.
Object Status
Object Status
177
Item Description
Object status, Scanning This element displays the status of the selected object, the interval in
interval, Object ID, QR which PRTG scans the object, the ID of the object, and the QR code for
code the selected page. If you use a PRTG app for iOS or Android 2998 , you can
scan the code to directly view the object on your mobile device. Click the
QR code to enlarge it for scanning.
Depending on the object type, this element shows additional information:

§ All objects underneath the root group show their dependency 144 .
§ Groups and devices display the time that has elapsed since the last
execution of the auto-discovery 270 on the selected object.
§ Devices show their DNS name or IP address as defined in the device
settings 612 and the time that has elapsed since the last execution of
the sensor recommendation 200 on this device.
§ Sensors show additional monitoring statistics as well as their
performance impact 2962 .
Switch Device Tree View

Wherever a probe or group is displayed, you can choose between a number of viewing options.
Device Tree Viewing Options
Device Tree View ing Options
Classic Device Tree View
Collapsed Device w ith Summarized Up and Unusual States and Individual Dow n States
Via the Switch Device Tree View in the page header bar, you can adjust how much information is
included next to each object. Use it to switch from a very condensed view ( ) to a very spacious view (
). Use to switch the device tree to a list view.
In the classic device tree view, you can collapse devices, groups, and probes. Click left of the object
name to summarize the sensors according to their respective status. By default, sensors in the Down,
Down (Partial), or Down (Acknowledged) status are summarized if there are more than ten sensors with
the same status, otherwise they are displayed individually.
178
Extended Device Tree Views
There are two additional options to the classic device tree view with which you can display the status of
all sensors of your entire installation in a single overview. Click to change to the sunburst view. To
change to the tree map view, click .
Sunburst View
The sunburst view displays your entire installation as a circle diagram. The groups are represented as
inner circles, and all devices that belong to a group are shown as 'cake slices' that are attached to the
outside of a circle element.
The sunburst is interactive:
§ You can click elements to open the Overview tab of your monitoring objects.
§ You can zoom in and out with your mouse wheel while pressing the Ctrl key.
179
Sunburst View
Tree Map View
The tree map view displays all devices of your entire installation as tiles that are sorted into a square and
that are arranged according to the groups they belong to. Each device dynamically changes color to
reflect the overall status of the sensors on the device.
180
Tree Map View
The following aspects apply to both the sunburst view and the tree map view:
Colors
A device or group can have different colors, depending on the states of the sensors that are on the device
or in the group. The sensor states are ranked according to their priority, for example, the Down status
has a higher priority than the Warning status, which has a higher priority than the Up status.
For an overview of the colors and their states, see section Sensor States 184 .
Size by: Sensors / Size by: Priority
181
You can adjust the size of the different squares according to the number of sensors that run on a device
or in a group, or the sensors' priority 227 , or both. Select the check boxes in the page header bar to
change the square size.
Check Boxes for Adjusting the

Square Size
Add Button
Hover over to add new objects to your monitoring setup. An assistant appears and guides you
through the necessary steps.
The content of the menu varies depending on the selected object.
Add Button Menu
See the following sections for more information:
§ Add Remote Probe 3201
§ Add an Auto-Discovery Group 274
§ Add a Group 329
§ Add a Device 379
§ Add a Sensor 430
Default Objects in the Device Tree

By default, PRTG Network Monitor creates a probe device on the local probe or on the hosted probe
(PRTG Hosted Monitor). The probe device represents the probe system. PRTG automatically monitors
the system health of the PRTG core server and each probe to discover overload that might distort
monitoring results. To monitor the status of the probe system, PRTG automatically creates the following
sensors:
§ Core Health
§ Probe Health
§ System Health
§ Some device-specific sensors for disk usage and bandwidth.
In a cluster, PRTG also creates a cluster probe device with a Cluster Health sensor that monitors the
system health of the cluster.
182
Priority and Favorites
You can mark a device or sensor as a favorite. To do so, click to the right of the respective object in
the device tree. The flag turns dark gray. To remove an object from your favorites, click . The flag turns
transparent again.
One-Click Favorites in the Device Tree
The favorite flag for sensors is available for the L or XL viewing options.
A quick way to set the priority of an object is via the five stars in the page header bar 174 next to the
object name. Click the stars to adjust the priority. means top priority, means lowest
priority.
One-Click Favorite and Priority in the Page Header Bar
You can also add any device or sensor to your favorites in the page header bar of the respective object.
To do so, click for a device or for a sensor. Click for a device or for a sensor to remove the
respective object from your favorites.
More
KNOWLEDGE BASE
What options do I have to review my monitoring data in detail?

183
6.4 Sensor States
The color of a sensor or object indicates its status. In the table below, you find a list of states that a
sensor or object can show. This list also reflects the priority of the sensor states whenever PRTG shows
summarized sensor states, for example, in the device tree 168 or in geographical maps 2741 . For example,
if all sensors on a device show the Up status and one of the sensors changes to the Down status, the
device shows the Down status as well because this status has a higher priority. The device is then
displayed accordingly in the extended device tree views 179 .
The Down and Down (Partial) states are considered to be equal regarding status priority.
In the device tree, hover over an object's name to view the total number of alarms for the object. In
geographical maps, hover over over the location marker to view the total number of alarms at this
location.
Status Icon Status Name Meaning
Down At least one sensor on this object (or at this

/ location) shows the Down status.
§ PRTG is unable to reach the device or the
sensor has detected an error. For more
information, see section Sensor Behavior for
the Warning and Down States 186 .
In this case, the sensor does not record
any data in its channels while it shows
the Down status.
§ There is an error limit in the channel
settings 2692 or the sensor shows the Down
status because of a lookup 3186 .
In this case, the sensor continues to
record data in all channels although it
shows the Down status.
Down (Partial) In a cluster, at least one cluster node reports

that this sensor shows the Down status, while at
least one other cluster node reports that the
same sensor shows the Up status.
This status is not available for sensors on
remote probes in a failover cluster 132 .
Down (Acknowledged) At least one sensor on this object (or at this

/ location) showed the Down status and a user
acknowledged this status via Acknowledge
Alarm in the context menu 232 .
§ There is no sensor in the Down status.
For acknowledged alarms, PRTG does not

send further notifications 2745 .
184
If you pause and resume a sensor in the

Down (Acknowledged) status, it shows the
Down status again.
Warning At least one sensor on this object (or at this

/ location) shows the Warning status.
§ The sensor detected an error and shows the
Warning status but the sensor is trying to
reach the target device again. The sensor
might soon change to the Down status. For
more information, see Sensor Behavior for the
Warning and Down States 186 .
§ There is a warning limit in the channel settings
or the sensor shows the Warning status
because of a lookup.
§ There is no sensor in the Down or Down
(Acknowledged) status.
Unusual At least one sensor on this object (or at this

/ location) shows the Unusual status.
§ The sensor reports unusual values for this
weekday and this time of the day. The unusual
detection is based on the sensor's historic
average data. You can configure or disable the
unusual detection in the system
administration settings under Monitoring 2881 .
§ You can also disable the unusual detection for

specific groups.
For more information, see section Group
Settings 608 .
§ There is no sensor in the Down, Down
(Acknowledged), or Warning status.
Up All sensors on this object (or at this location)

/ show the Up status.
§ The last scan was okay and the sensors
receive data.
(Acknowledged), Warning, Paused, or
Unusual status.
Paused All sensors on this object (or at this location)

/ show the Paused status.
185
§ The sensor is paused for a specific time span,

indefinitely, or because of a dependency 144 .
(Acknowledged), Warning, Unusual, or Up
status.
A sensor in the Paused status does not

count towards the maximum number of
sensors that your license allows.
Unknown All sensors on this object (or at this location)

/ show the Unknown status.
§ The sensor has not received any data yet or
there is an error in (network) communication,
likely on the probe system. If sensors
continuously show this status, you might need
to restart PRTG.
For more information about extended
troubleshooting, see the Knowledge
Base: What to check if sensors are gray? and
My sensors show the Unknown status after a
PRTG core server restart. What can I do?
(Acknowledged), Warning, Unusual, Paused,
or Up status.
Sensor Behavior for the Warning and Down States

The Down status indicates that there is an issue with an object, for example, a device. There are various
reasons for the Down status, for example, an interruption in the physical connection to the device or an
internet connection outage.
After a failed request, PRTG tries to contact the device again before it sets a sensor to the Down status
(this is true for almost all sensors):
1. If a request to a device fails for the first time, the sensor changes to the Warning status. PRTG
repeats the request and immediately attempts to rescan the device.
2. If the second request also fails, the sensor changes to the Down status by default until the device is
reachable again. You can change this behavior in the scanning interval 466 settings of any object in
the device tree. 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 immediately informed about any network issues.
This behavior does not apply to the Warning or Down states that result from warning limits or error
limits in the channel settings. This behavior also does not apply to channels that use lookups.
186
More
KNOWLEDGE BASE
What to check if sensors are gray?

My sensors show the Unknown status after a PRTG core server restart. What can I do?
VIDEO TUTORIAL
Sensor states
§ https://www.paessler.com/support/videos-and-webinars/videos/sensor-states
187
6.5 Historic Data Reports
For quick reviews of a sensor's monitoring data, use historic data reports as an alternative to the
comprehensive reports 2764 feature. You can run and view a historic data report for each sensor on
demand. Additionally, you can export a sensor's historic data as an .xml file or a .csv file to your
computer to further process the data with third-party applications.
There are two ways to open historic data reports: Either click the Historic Data tab of a sensor or select
Sensors | View Historic Data from the main menu bar 257 .
Historic Data Tab of a Ping Sensor
Historic Data (Sensor Tab)

Probe, group, device, and sensor pages have tabs that you can use to navigate between different
options. For example, you can view your network's status, view monitoring results, or change settings.
Tabs Bar for Sensors
The Historic Data tab is only available for sensors, not for probes, groups, or devices. When you open
the Historic Data tab of a sensor, no sensor selection is available. If you want to select a different sensor
for the report, select Sensors | View Historic Data from the main menu bar.
188
Historic Monitoring Data (Sensors Main Menu)
When you open historic data reports via Sensors | View Historic Data from the main menu bar, PRTG
asks you to select the sensor for which you want to create a report with the object selector 225 .
Historic Data Report Settings
Historic Data Report Settings
Setting Description
Sensor This setting is only visible if you open View Historic Data from the main
menu bar.
To select the sensor for which you want to create the report, click to
open the object selector.
For more information, see section Object Selector 225 .
Start Specify the start date and time for the data that you want to review. Use
the date time picker to enter the date and time.
You cannot generate the historic data report if monitoring data was
deleted 2909 after the specified start date. Set the start of the report to
a date for which data is available.
189
Setting Description
End Specify the end date and time for the data that you want to review. Use
Quick Range You can use several buttons to select start and end dates more quickly.
Click any of these buttons to change the Start and End values:
§ 1 Day, 2 Days, 7 Days, or 14 Days: Set the date range 223 to the
respective day or days. The current time of the current day is the end
date.
§ Today, Yesterday, Last Week (Mo-Su), Last Week (Su-Sa), Last
Month, 2 Months, 6 Months, 12 Months: Set the date range to the last
matching period. It starts at 00:00 and ends at 00:00 of the following
day.
Averaging Interval With this option, you can activate and configure averaging. Select an
interval for which PRTG calculates the average value:
§ No interval (display raw data): PRTG performs no averaging and
displays only raw data.
PRTG stores raw data for up to 40 days. After this time, PRTG
calculates averages again.
§ 15 seconds, 30 seconds, or 60 seconds/1 minute
§ 2 minutes, 5 minutes, 10 minutes, 15 minutes, 20 minutes, or 60

minutes/1 hour
§ 2 hours, 4 hours, 6 hours, 12 hours, or 24 hours/1 day
A shorter interval results in a more detailed historic data report for the
sensor.
The best settings for you depend on the scanning interval of the sensor,
the selected time period, and the intended use for the historic data report.
Try different settings and compare the results. See also Automatic
Averaging 193 in this section.
Channels in Graph This setting is only visible if you view historic data via the Historic Data
tab of a sensor.
Select the channels that you want to include in the graph of the historic
data report. You can select individual channels via the respective check
boxes, and show or hide all channels via the Show all or Hide all buttons.
In the graph, PRTG then only shows the data of selected channels.
The historic data report table always shows the data of all channels.
Cluster Node This setting is only visible if the sensor runs on a cluster probe.
190
Setting Description
Select the cluster node's data that PRTG includes in the historic data
report:
§ All nodes: Include the data of all cluster nodes in the report.
§ [Several specific nodes]: Use a specific cluster node's data for the
report. The cluster nodes you see are specific to your setup.
File Format Select the output format for the report:

§ HTML web page: Display the result directly as an HTML web page. This
is also a good option if you want to check the results before you export
them to a different file format.
§ .xml file: Export the data as an .xml file. Your browser usually shows a
download dialog when you use this option.
§ .csv file: Export the data as a .csv file, for example, to import it into
Microsoft Excel. Your browser usually shows a download dialog when
you use this option.
Percentile Handling
Percentile Handling
Setting Description
Percentile Results Define if you want to include an additional percentile calculation 3200 of
your data in the historic report:
§ Do not show percentiles: PRTG does not use a percentile formula to
calculate your monitoring results. It only shows the standard values.
191
Setting Description
§ Show percentiles: PRTG displays an additional percentile calculation

for the primary channel in the value table for each scanning interval.
Example of a Historic Data Report w ith Percentile Calculation for the Primary Channel
Percentile Type This setting is only visible if you select Show percentiles above.
Enter the percentile type that you want PRTG to use for the calculation. If
you choose, for example, to calculate the 95th percentile, enter 95 here
and 5% of peak values are discarded. Enter an integer.
Percentile Averaging This setting is only visible if you select Show percentiles above.
Interval
Enter a value to define the averaging interval on which PRTG bases the
percentile calculation. The default value is 300 seconds (5 minutes). This
means that PRTG takes 5-minute averages as basic values for the
percentile calculation. Enter an integer.
Percentile Mode This setting is only visible if you select Show percentiles above.
Select the mode for percentile calculation:

§ Discrete: PRTG takes discrete values to calculate percentile results.
§ Continuous: PRTG interpolates between discrete values and bases the

calculation on interpolated values.
192
Click Start to generate a historic data report.
You cannot generate the historic data report if monitoring data was deleted 2909 after the specified
start date. Set the start of the report to a date for which data is available.
Remarks for Reports

§ Any sensor graph in your report only shows channels that you select via the Show in graphs option in
the channel settings 2692 .
§ Reports show statistics for the uptime (the Up and Down states184 in percent) and for requests (Good
and Failed in percent). PRTG rounds values between 5% and 95%, as well as 100% and 0%, to whole
numbers without decimal places. Other values are shown with 3 decimal places.
§ Because PRTG rounds values, the statistics in the report section Sensor Status History can differ from
the values in the report section Uptime Stats by a few seconds.
§ PRTG limits data reporting to 5 requests per minute.
§ Reports cannot show uptime or downtime data for the Sensor Factory sensor.
§ Create reports that include an appropriate amount of data. Reports might not work as expected if
PRTG has to process too many sensors with short scanning intervals. Adjust your report size and the
time span that the report covers, if necessary.
Automatic Averaging
For performance reasons, PRTG automatically averages monitoring data when it calculates data for large
periods of time.
Period of Time in Report Minimum Level of Detail (Averaging Interval)
Up to 40 days Any
40 to 500 days 60 minutes/1 hour or longer
Reports for periods that are longer than 500 days are not possible. If you enter a longer period,
PRTG automatically shortens it to 365 days.
In some cases, the generated report might contain a period of time that differs from the defined start
and end date for the report because of internal averaging processes. When averaging intervals are
longer than 1 hour and do not equal 24 hours, and when they are combined with specific periods of
time, the resulting data points might be asynchronous to the periods of time. Consider this behavior
particularly if you use application programming interface (API) calls 3094 to generate reports.
More
KNOWLEDGE BASE
Why is there missing data in historic data reports?

193
How does PRTG compute CPU Index, Traffic Index and Response Time Index?
194
6.6 Similar Sensors
With PRTG, you can detect relationships between different components in your network. For example,
you can detect extraordinarily high CPU load that correlates with extraordinarily high traffic at a specific
time of a day or week. This can give you a hint to further investigate that part of your network.
What Is Similarity?
The similarity calculation is based on the values that are saved in the sensor history. If measured values
change in the same way, the Similar Sensors Detection feature detects it and shows you the sensors for
which it found similar data relations. PRTG shows all sensors that reach 85% to 100% similarity.
The analysis of similar sensors is a heuristic calculation that shows interconnections and correlations in
your network. The analysis is completely automated. It is based on mathematics and fuzzy logic and
optimizes your sensor usage by tracking redundant monitoring of some aspects of your system.
Similar Sensors Detection

You can adjust the depth of the similar sensors detection or turn it off under Setup | System
Administration | Monitoring.
Similar Sensors Detection Settings
You can also enable or disable the similar sensors detection for specific probes, groups, and devices,
and specify inheritance 140 in the object's settings 204 , section Advanced Network Analysis.
Activation of the Similar Sensors Detection
195
There are two options to view similar sensors:
§ Via the Overview tab of sensors that includes a Similar Sensors section 196 where PRTG lists
channels that show similarities to channels of the selected sensor.
§ Via Sensors | Simulate Error Status in the main menu bar where you get an overview 198 of all similar
sensors.
To edit the list of similar sensors results, use the available filters 199 .
Similar Sensors (Sensor Overview Tab)

On the Overview tab of a sensor, PRTG lists channels that show similarities to channels of the selected
sensor. The table is empty if PRTG detects no similarities to the selected sensor.
PRTG shows similar sensors here when channels have 85% similarity or more. The similar sensors
detection saves up to 15 entries per sensor.
196
Similar Sensors Section on a Sensor's Overview Tab
The Similar Sensors section provides the following information.
Column Header Description
Similarity Shows the similarity between two channels in percent.
Channel Shows a channel of the selected sensor.
Similar Channel Shows a channel of a sensor that is similar to the channel of the selected
sensor that you can see in the Channel column in the same row.
197
PRTG does not show the Similar Sensors section when the analysis is disabled or when you
exceed 1,000 sensors and select the Manage automatically based on sensor count (default) option
as Analysis Depth in the Monitoring 2883 settings. In this case, you see the following notice:
Similar Sensors Detection Notice
Similar Sensors Overview (Sensors Menu)

This page shows the results of the similar sensors detection from the entire monitoring database. PRTG
lists all channels with similarities here. Above the table, there are several filter options to display similar
sensors as required. Select the object of interest, the degree of similarity, and display back references.
For more information, see section Working with Table Lists 221 .
The analysis of similar sensors requires sensor data from at least seven days to have enough data
for comparison. If not enough data is available, no data is shown on the Similar Sensors Overview or
in the Similar Sensors section on a sensor's Overview tab.
PRTG shows similar sensors here when channels have at least 85% similarity. Furthermore, the
analysis saves up to 15 entries per sensor.
Similar Sensors Overview
You can click the column headers to sort the list. The Similar Sensors Overview provides the following
information.
198
Original Channel Shows channels that other channels are compared to. Click the column
header to sort the list according to the order in the device tree in
ascending or descending order.
Similarity Shows the similarity between two channels in percent. Click the
column header to sort the list according to the similarities in ascending
or descending order.
Similar Channel Shows a channel that is similar compared to the original channel. Click
the column header to sort the list according to the order in the device
tree in ascending or descending order.
PRTG does not show the Similar Sensors Overview item in the main menu bar if you disable the
analysis or if you exceed 1,000 sensors and select the Manage automatically based on sensor
count (default) option as Analysis Depth in the Monitoring 2883 settings.
Adjust the Similar Sensors Overview to Your Needs

You can use various filters to adjust the results in the Similar Sensors Overview. Click Show Filters and
edit the filters that appear.
Filters for the Similar Sensors Analysis
Filter Description
Filter By Object Select the device, probe, or group that you want the Similar Sensors
Detection to cover. This way, you can apply the analysis to the parts of
your network that you are interested in.
Filter By Maximum Select a degree of similarity from 85% to 100%.

Similarity
Inverted Relationships If you select Show, PRTG shows all similarity relationships, that is, A
matches B and B matches A.
If you select Hide, PRTG only shows A matches B relationships. This
reduces the number of displayed similar sensors.
199
6.7 Recommended Sensors
With the Recommended Sensors Detection feature, PRTG can explore any device and check which
sensors you have already created. If it finds useful sensors that you have not created yet, you see a list
of recommended sensors for your device.
You cannot use this feature on the hosted probe of a PRTG Hosted Monitor instance. You can use
this feature on remote probes.
The recommended sensors detection does not apply to the user group setting 2924 Allowed Sensors.
Therefore, read/write users can also add all recommended sensors.
Recommended Sensors on Device Overview Tab
Get Sensor Recommendations

By default, PRTG recommends sensors for any device that you add and shows the suggested sensors
for the device on its Overview tab, as long as your installation includes less than 5,000 sensors in total.
To add the recommended sensors, click Add These Sensors.
You can see the time that has passed since the last sensor recommendation in the page header bar 174
on the Overview tab of a device.
If you want to manually start the recommended sensors detection on any device, follow the steps below.
200
Step 1: Select the Device
Open the Overview tab of the device that you want to analyze.
Step 2: Recommend Now

To start the analysis of your device, click Recommend Now or right-click the device and select
Recommend Now from the context menu 240 .
If you do not see the Recommend Now option, make sure that the Recommended Sensors
Detection in the Monitoring 2884 settings. Probe devices do not support this option.
Depending on the complexity of your device, it can take some time until you see the results of the
analysis.
Recommended Sensors Investigation
PRTG runs the recommended sensors detection with low priority in the background to prevent potential
performance issues. Because of this, the recommended sensors detection can take more time than
expected if PRTG needs resources to ensure the gapless monitoring of your network. By default, the
recommended sensors detection starts automatically when you add a new device, when you do not have
more than 5,000 sensors, or when the last analysis was executed more than 30 days ago. You can
change these settings under Setup | System Administration | Monitoring, section Recommended
Sensors Detection.
To recommend Simple Network Management Protocol (SNMP) sensors 3237 for a device, the
detection engine uses the SNMP version that you defined in the Credentials for SNMP Devices
section of the device settings 630 .
Step 3: Get the Results

After PRTG analyzed your device, it suggests a list of sensors that are useful for a more comprehensive
monitoring.
201
List of Recommended Sensors
The list of recommended sensors provides the following information.
Priority Shows which priority 227 the suggested sensors have when you add them.
The recommended sensors table is sorted by priority, beginning with the
top priority ( ) in the first row.
You can manually change the priority of a sensor after you add it.
Sensors Shows the suggested sensors and the number of sensors of one type
that PRTG recommends for this device. For example, you might want to
add an SNMP Traffic sensor multiple times for several network interfaces.
Total Sensors Shows the total number of suggested sensors per table row. These
sensors have the same priority.
Links Displays an Add These Sensors button for every table row. Click to
automatically add the sensors in this table row to the device.
The recommended sensors detection checks if a certain sensor exists on your device and
recommends that you add this sensor if it does not exist. If this sensor existed previously on the
device, but you deleted it, PRTG suggests this sensor again. In this case, ignore the recommendation of
this sensor or follow step 4 202 .
Step 4: Add Recommended Sensors

Click Add These Sensors in a table row to add all sensors in this row to the analyzed device.
If you want to add all suggested sensors regardless of their priority, click every Add These Sensors
button in the Recommended Sensors table. If you want to add only some of the sensors of a certain
priority, click Add These Sensors, then delete 246 or pause 230 the sensors you do not need afterward.
202
Settings for the Recommended Sensors Detection
You can also adjust the settings for the recommended sensors detection or disable it under Setup |
System Administration | Monitoring.
Recommended Sensors Detection Settings
If you use the Manage automatically based on sensor count (default) setting, PRTG uses an intelligent
assistant to count the number of sensors you have and decides whether to start the detection of
recommended sensors or not. The detection does not start if your PRTG installation includes 5,000
sensors or more to prevent performance issues. We recommend that you use this option so that you do
not miss any important monitoring data about your network and so that you do not risk performance
issues.
Disable the recommended sensors detection if you encounter performance issues or if you do not
want to display this information on device Overview tabs.
Auto-discovery
You can also use the auto-discovery to find suitable sensors. You can start the auto-discovery when you
add a new device 385 , you can manually start 271 it at any time, or you can choose if you want PRTG to
analyze a whole section 617 of your network, for example, devices that are covered by a certain IP
address range.
The auto-discovery has a higher priority than the detection of recommended sensors. If both are
active, PRTG queues the sensor recommendation and executes the auto-discovery first.
203
6.8 Object Settings
General Settings
On the Settings tab, you can define all settings for the selected object. The available options vary
depending on the kind of object that you select. See the following sections for information about the
object types:
§ Root Group Settings 436
§ Probe Settings 474
§ Group Settings 541
§ Device Settings 612
§ Sensor Settings
You cannot open channel settings 2692 via tabs. Go to a sensor's Overview tab to edit the channel
settings.
Notification Triggers Settings

On the Notification Triggers tab, you can set notification triggers for every object. If you use these
settings for a probe, group, or device, they are inherited to all sensors on these objects. The available
notification trigger options are the same for all objects.
Comments
On the Comments tab, you can enter free text for each object. You can use this function for
documentation purposes or to leave information for other users.
History
On the History tab, all changes in the settings of an object are logged with a time stamp, the name of
the user who made the change, and a message. The history log retains the last 100 entries.
On some pages, you can click in the page header bar 174 to access the history of subordinate
objects. This includes system administration 2865 settings and account settings 2811 , reports 2764 ,
libraries 2748 , and maps 2786 . For more information, see section Logs 213 .
204
6.9 Alarms
The alarms list shows all sensors that are in the Down, Down (Partial), Down (Acknowledged), Warning,
or Unusual status. Sensors in the Up, Paused, or Unknown states do not appear here.
By default, table lists 221 that show alarms are sorted by priority 227 . Click a column header to sort
the list items by a different category.
Alarms List
There are two ways to display the alarms list. Either click the Alarms tab of a probe, group, or device, or
click Alarms in the main menu bar 253 .
Alarms (Object Tab)

Probe, group, device, and sensor pages have tabs that you can use to navigate between the different
Tabs Bar for Groups and Probes
Click the Alarms tab of a probe, group, or device to show a table list of all sensors on the selected object
that show the Down, Down (Partial), Down (Acknowledged), Warning, or Unusual status 184 . This list is a
subset of the entries that are available via the Alarms | All option in the main menu bar.
The Alarms tab is not available for sensors.
Alarms (Main Menu Bar)

Click Alarms in the main menu bar to show a table list of all sensors in your installation that show the
Down, Down (Partial), Down (Acknowledged), Warning, or Unusual status. You can also show these
sensors as gauges or only show a subset of sensors in specific states. Hover over Alarms to show
further options:
205
Option Description
All Open a list of all sensors that are in the Down, Down (Partial), Down
(Acknowledged), Warning, or Unusual status.
Show as Gauges Open a page with the gauges of all sensors that are in the Down, Down
(Partial), Down (Acknowledged), Warning, or Unusual status. The size of
the gauges corresponds to the sensor's priority.
Errors Only Open a list of all sensors that are in the Down, Down (Partial), or Down
Warnings Only Open a list of all sensors that are in the Warning status.
Unusuals Only Open a list of all sensors that are in the Unusual status.
Acknowledge Alarm
An acknowledged alarm shows the Down (Acknowledged) status. It does not trigger 2704 any more
notifications 2745 .
If the alarm condition clears, the sensor usually returns to the Up status with the next sensor scan.
If a sensor in the Down (Acknowledged) status was paused and resumed, it shows the Down status
again.
To acknowledge an alarm, right-click a sensor that shows the Down status. From the context menu 232 ,
select Acknowledge Alarm, then select a time span, optionally enter a message, and click OK. The
message appears in the last message value of the sensor.
The time spans that you can select are: Acknowledge Indefinitely, acknowledge For 5 Minutes, For 15
Minutes, For 1 Hour, For 3 Hours, For 1 Day, or Until. If you select Until, provide the following
information:
Field Description
Selected Objects Shows the sensors for which you want to acknowledge the alarm. You
can acknowledge alarms for more than one sensor using multi-edit 2729 .
Message Enter a text, for example, the reason why you acknowledge the alarm.
Enter a string or leave the field empty.
Until Select the date when the Down (Acknowledged) status ends. Use the
date time picker to enter the date and time.
206
Field Description
If the alarm condition still exists after the specified date, the sensor
shows the Down status again.
To return the sensor to the Down status before the specified date,
you can Pause and then Resume the sensor via the context
menu 246 .
By default, only read/write users 2911 or administrators can acknowledge alarms. However, you can
give read-only users the right to acknowledge alarms, too. See the system administration settings,
section User Accounts 2914 .
More
KNOWLEDGE BASE
Which audible notifications are available in the PRTG web interface and in the PRTG app for desktop?
207
6.10 System Information
With the System Information feature, you can see what is going on in the systems that you have in your
network. To see the system information for a device, click the device's System Information tab.
System Information Tab on a Window s Device
The system information shows
§ basic system data of your device like the BIOS serial number or MAC and IP addresses,
§ all connected hardware types and their properties,
§ the software you have installed, including version and vendor information,
§ the users that are connected to your system and their domains,
§ a list of all active or stopped Windows system services including their properties, and
§ a list of all processes that are running on your system, including their ID and start time.
System information is available for all devices that run with an officially supported Windows operating
system 27 . You can also retrieve system information from devices that run with Linux or Unix, and from
all other devices that have the Simple Network Management Protocol (SNMP) enabled.
Prerequisites
You already meet the main prerequisites for retrieving system information if you already monitor a device
with sensors that use Windows Management Instrumentation (WMI) or the Simple Network Management
Protocol (SNMP). PRTG automatically displays the data on the respective device's System Information
tab. To retrieve all available system information, enable both WMI and SNMP on the device.
208
The System Information feature is enabled by default. To retrieve the data, PRTG automatically uses
the credentials for Windows systems 621 and the credentials for SNMP devices 630 that you entered
in the device settings or that the device inherits 136 from a parent object like the root group. Consider this
when you monitor devices that are outside of your local network, especially when you use SNMP v1 or
SNMP v2c, which do not provide encryption.
Meet the following prerequisites if you do not yet use WMI or SNMP sensors:
Option Description
Valid credentials Specify valid credentials for Windows systems and for SNMP devices in
the device settings 612 .
Remote Registry Enable the Remote Registry service on the target computer, for example,
Windows service via services.msc, and set the Startup Type to Automatic.
Remote Procedure Call Enable the RPC Windows service on the target computer, for example,
(RPC) Windows service via services.msc, and set the Startup Type to Automatic.
WMI Enable WMI on both the probe system and the target system. In
particular, configure the firewall of the target system to allow WMI.
For more information, see section Monitoring via WMI 3014 and the
Knowledge Base: My WMI sensors don't work. What can I do?
SNMP Enable SNMP on the target system. PRTG automatically uses the SNMP
Compatibility Options as defined in the device settings 612 or as inherited
from a parent object like the root group.
For more information, see section Monitoring via SNMP 3007 and the
Knowledge Base: My SNMP sensors don’t work. What can I do?
It is not necessary to meet every single prerequisite but then some tables do not show all data or
they can even remain empty. For example, if you do not enable SNMP on the target device, you get
less information for the System table.
The first data usually comes in after a few minutes. If PRTG cannot retrieve some data, for example,
because of a misconfiguration, the respective System Information table shows an error message.
For more information, see the Knowledge Base: How can PRTG get data for System Information
tables?
System information for your devices is only for informational purposes. We cannot guarantee that
the data displayed in PRTG fully corresponds to the device parameters.
209
Error Messages: No Data Available
System Information (Device Tab)

Tabs Bar for Devices
Select a device and click the System Information tab.
The System Information feature is enabled by default. If you do not see the System Information tab,
you need to enable System Information in the device settings under Advanced Network Analysis.
You can also inherit the setting from an object that is higher in the object hierarchy 136 .
Advanced Netw ork Analysis
Analyze Your Systems

On the System Information tab, PRTG displays a table for each system information category for the
device.
210
Category System Information Request
Method
(WMI or
SNMP)
System Shows system data of the device like the BIOS serial number, IP WMI and
addresses, MAC addresses, and the Windows version. SNMP
Hardware Shows hardware that is connected to the device like disk drives, WMI and
CD/DVD, video controllers, processors, network adapters, sound SNMP
devices, printers, and memory. You can see the Class and the
Caption of a hardware device. In the Properties column, you get more
information about the hardware, for example, the description.
Software Shows the installed software and the Version number of the device. In WMI and
the Properties column, you get more information about the software, SNMP
for example, the size.
PRTG uses Uninstall registry keys to retrieve the list of installed
software, so the displayed software might differ from the software
that the target Windows system shows under Programs and
Features.
The System Information scan for software on the probe device
uses the credentials of the probe system and ignores credentials
that you specified on the Settings tab.
Users Shows the user accounts that are connected to the device and their WMI
Domain.
Services Shows the available Windows services on the device. You can see WMI
the State of the service (running, stopped) and the start type (Startup
Type automatic, manual, or disabled). In the Properties column, you
can get more information about a service, for example, the
description.
Processes Shows the processes that are running on the device as listed on the WMI and
Processes tab of the Windows Task Manager. You can also see the SNMP
Start Time (only WMI) and Process ID of a process.
You can sort each table list 221 via the column headers.
Click in the upper-right corner of a table to retrieve new information for this System Information
category. The time stamp shows the time that has passed since the last table refresh.
Table Refresh
211
PRTG automatically retrieves data for the tables System, Hardware, and Software once every 24 hours.
The tables Users, Services, and Processes refresh each time you open the System Information tab.
PRTG also updates all system information tables when the PRTG core server is restarted, for example,
after an update.
PRTG can perform up to 24 system information scans at the same time, so it can take some time
until you see data in the tables after a server restart.
Data Storage
PRTG stores data files with the retrieved system information in the corresponding \System Information
Database subfolders of the PRTG data directory 3219 .
If you delete a device, the system information files of this device remain in these subfolders unless
you manually delete them.
PRTG uses the following subfolders for System Information data.
Subfolder Description
hardware Data for the Hardware table
loggedonusers Data for the Users table
processes Data for the Processes table
services Data for the Services table
software Data for the Software table
system Data for the System table
More
KNOWLEDGE BASE


How can PRTG get data for System Information tables?


212
6.11 Logs
Logs show all past activities and events in your monitoring setup. With the logs, you can, for example,
review past user activities, system events, or check whether messages were sent. In a typical setup, a
huge amount of log data is produced. Because PRTG records the activity of every single object, you can
use this information to check if your setup works as required.
You can choose from several filters to navigate the log entries.
List w ith Log Entries
There are two ways to open the logs list. Either click the Log tab of a probe, group, device, or sensor, or
click Logs in the main menu bar 262 .
Log (Object Tab)

Tabs Bar for Groups and Probes
Click the Log tab to show a table list with all log information for the selected object. This is a more
detailed log than the system log that is available via the Logs | All option in the main menu bar.
Logs (Main Menu Bar)

Click Logs in the main menu bar to show a table list of all system log entries in your installation. Hover
over Logs for further options:
213
Option Description
All Open a list with log information about all objects in your installation. The
list begins with the most recent log entry.
Status Changes Open a list with log information about specific status changes. Hover over
Status Changes to choose from the following sensor states:
§ Up & Down
§ Down
§ Warning
§ Unusual
§ Up
§ Paused/Resumed
§ Acknowledged Alarms
System Events Open a list with log information about specific system event types. Hover
over System Events to choose from the following event types:
§ Report Related
§ Cluster Related
This event type only appears if you have a cluster.
§ Auto-Discovery Related
§ Notifications Related
§ Status Message Related
Object History Open a list with log information about changes to the PRTG setup and
deletions of subordinate system objects. The Object History has several
tabs. To view the changes to all related settings and deletions of objects,
use the following tabs:
§ My Account
§ System Administration
§ Notification Templates
§ Schedules
§ User Accounts
§ User Groups
§ Reports
§ Schedules
§ Maps
214
Option Description
You can also navigate to a corresponding page, for example, you can
select Setup | Account Settings | My Account from the main menu
bar, and click in the page header bar 174 to directly go to the related
object history tab.
More
KNOWLEDGE BASE
The logs page in the PRTG web interface does not load. What can I do?
215
6.12 Tickets
PRTG has its own ticket system. A ticket includes information about recent events in your PRTG
installation that need a closer look. Each ticket is a task for a particular user or user group.
List of Tickets
Each task has a life cycle in the ticket system. The task's life cycle starts when a ticket is created. The
users who are responsible then take care of this issue. Once the issue has been resolved, the ticket can
be closed and the life cycle of the task ends. PRTG automatically creates tickets, for example, when the
auto-discovery 270 has finished, and you can create tickets for every kind of issue as well. In addition,
you can set up notifications 2745 that open a ticket when an issue occurs.
Every ticket has a unique ID, a priority, and a status. You can open, resolve, or close a ticket.
PRTG can also send an email 220 to you whenever a ticket is assigned to you or if one of your tickets
has been changed.
Except for administrator groups, you can disable the ticket system for particular user groups under
Setup | System Administration | User Groups. You can also disable ticket emails 220 for every user
account.
Ticket Types
There are three types of tickets:
Type Description
User Tickets User tickets are created by users, for example, to assign monitoring-related
tasks to a particular user account 2911 or user group 2922 .
ToDo Tickets ToDo tickets are created by PRTG to show important system information and to
inform you about specific system events. ToDo tickets are assigned to the
predefined PRTG Administrators group. You cannot change the user group to
which PRTG assigns ToDo tickets and you cannot disable ToDo tickets.
Users that belong to an administrator group do not receive new ToDo tickets
and notifications about changes by default, only the predefined PRTG
System Administrator user does. You cannot change this behavior.
216
Type Description
See the following examples for cases in which PRTG creates a ToDo ticket:
§ The auto-discovery created new devices or sensors.
In the ticket, PRTG only lists the device templates that it used to create
the sensors.
§ A new probe has connected to the PRTG core server and you must
acknowledge it.
§ A new cluster node has connected to the cluster and you must acknowledge
it.
§ A new version of the software is available.
§ A new report is ready for review.
§ In a few other situations, for example, the system is running out of disk space,
there are license issues, or an error occurs.
The related object of ToDo tickets is System.
Notification Notification tickets are created via notifications that you set in the notification
Tickets template settings 2818 .
Ticket States
Tickets can have three different states:
Sym State Description

bol
Open New tickets are open as long as the issue that is described in the ticket
exists.
Resolved The issue that is described in the ticket does not persist any longer because a
user resolved it.
Closed A user resolved the ticket, the solution to the issue was reviewed for
correctness, and the ticket does not require any other action.
Tickets (Main Menu)

This option is only available in the main menu bar if the user group to which the logged in user
belongs is allowed to use the ticket system. You can disable a user group's access to the ticket
system in the user group settings under Setup | System Administration | User Groups. Read-only users
never have access to the ticket system and cannot see the Tickets option in the main menu bar.
217
You have several options to display a list of tickets that is filtered to your needs. In the main menu bar,
click Tickets to show all open tickets that are assigned to you. Hover over Tickets to show other
available filter options:
Option Description
My Tickets Click to show all open tickets that are assigned to you. Hover over My Tickets to
show other options to filter these tickets according to their status: Open,
Resolved, Closed, or All.
All Tickets Click to show all open tickets of all users. Hover over All Tickets to show other
options to filter these tickets according to their status: Open, Resolved, Closed,
or All.
ToDo Tickets Click to show all open tickets of the ToDo type 216 . Hover over ToDo Tickets to
show other options to filter these tickets according to their status: Open,
Resolved, Closed, or All.
Click Open to show all open ToDo tickets. Hover over Open to show other options
to filter these tickets according to their event type: All, Report Related, Auto-
Discovery Related, Probe Related, Cluster Related, System Errors, or New
Software Version.
Add a User Ticket

From the main menu bar, select Tickets | Add Ticket, or hover over and click Add Ticket. This opens
the Add Ticket dialog.
Step 1: Select the object to which the new ticket is related via the object selector 225 . Click OK.
You can skip step 1 if you use an object's context menu 232 in the device tree to open the ticket.
Step 2: Provide the following information and click OK to create a user ticket:
§ Subject: Enter a subject for the ticket that indicates the topic of the issue.
§ Assigned to: From the dropdown list, select a user or a user group that is responsible for this issue.
§ Priority: Define a priority 227 from the lowest priority ( ) to the top priority ( ).
§ Comments: Enter a message. This message should describe the issue in detail.
After you open a new user ticket, a corresponding list of tickets appears. In this table list 221 , you can
sort the items by clicking the column headers. Additionally, several search options are available in the
filter directly above the table:
Option Description
Status all, open, resolved, closed
218
Option Description
Type Tickets, User Tickets, ToDo Tickets, Notification Tickets
Assigned To Show only tickets that are assigned to a specific user or user group:
§ anyone: Apply no user filter and show all tickets.
§ me: Show tickets that are assigned to you (the user who is logged in).
§ Groups: Show tickets that are assigned to a specific user group. The
displayed user groups are specific to your setup.
§ Users: Show tickets that are assigned to a specific user. The displayed users
are specific to your setup.
§ Disallowed: Display users or user groups that do not have access rights to the
selected object. This is for your information only. You cannot select disallowed
users or user groups.
Related To Specify the relationship to a monitoring object. Select groups, probes, devices,
or sensors with the object selector.
ToDo tickets are related to System.
Changed Between Define a time span to view tickets that changed during this time. Use the date
time picker to enter the date and time.
Click the subject of a ticket to open the ticket.
An Open ToDo Ticket w ith Instructions
Actions
The following actions are available for a specific ticket:
219
Action Description
Edit ( ) Open a dialog where you can change the subject and the priority of the ticket, as well
as assign the ticket to a different user. You can optionally add a message to this
ticket. Click OK to apply your changes.
Assign ( ) Open a dialog where you can give the ticket to a different user or user group. Select a
user or a user group via the dropdown list. You can optionally add a message to this
ticket. Click OK to apply your changes.
Resolve ( ) Open a dialog where you can resolve the ticket. The status resolved indicates that
the issue that is described in this ticket does not persist anymore. You can
optionally add a message to this ticket that indicates, for example, what was done to
resolve the issue. Click OK to apply your changes.
Close ( ) Open a dialog where you can close the ticket after the issue was resolved and
reviewed. You can optionally add a message to this ticket. Click OK to apply your
changes.
Reopen ( ) Open a dialog where you can reopen a ticket after it was resolved or closed. Do so,
for example, if the solution to the issue was not correct. You can optionally add a
message to this ticket that indicates, for example, why you have opened the ticket
again. Click OK to apply your changes.
Only user group members that have the respective access rights 149 can view and edit tickets that
are related to a certain monitoring object.
Tickets as Emails
You can receive all tickets that are assigned to you or to your user group as emails. PRTG also notifies
you via email each time a ticket that is assigned to you or to your user group is edited. This way, you
are always informed about new notifications (if you enabled this setting), important system information (if
you are an administrator), or the communication between other users.
You can disable the setting Email Notifications in the user account settings under Setup | System
Administration | User Accounts. If you select Do not receive any emails from the ticket system for a
specific user account, this particular user does not receive ticket emails anymore.
If you defined to receive tickets as emails and you are the predefined PRTG System Administrator
user, you receive emails for ToDo tickets as well, although ToDo tickets are usually opened by the
PRTG System Administrator user.
220
6.13 Working with Table Lists
In the PRTG web interface, you often see table lists, for example, sensor or device lists. Table lists are
also available in libraries 2748 , maps 2786 , reports 2764 , notifications 2745 , and schedules 2856 , as well as in
logs 213 and tickets 216 . All of these table lists are similar in layout and functionality.
Example of a Table List
Table List Options

See the following table for ways to work with table lists:
Feature Display Description
Paging The content of a table list is

displayed on several pages. Click
the respective paging button at the
end of a list to view other pages or
to go to the beginning or the end of
the list.
New Window Click the respective button to open

the table list in a new window.
Date Range Use the date and time picker to

show table list entries within a
specific time period. Click the first
field to select a start date and the
second field to select an end date.
Click Done to apply the selected
date and time.
221
Select Range When you view log lists, click

Select Range in the upper-left
corner of the table list to select the
time period for which you want to
show log entries. Choose from
Today, Yesterday, and several other
time periods. Select Unlimited to
disable this filter again.
For more information, see
section Date Ranges 223 .
Items Click Items in the upper-right corner

of a table list to select how many
rows are shown on each page. You
can choose between 50, 100, 500,
and 1000.
Sorting Click a column header to sort the

list items by the respective
category. You can click all column
headers that include arrow icons to
sort the list, for example, by Status,
Last Value, Priority, and more. The
sorting options vary depending on
the content of the table list.
Show XML Click the respective button to

download the selected page in XML
format. Your browser usually shows
a download dialog.
Filtering You can filter table lists via the

Show Filters option directly above a
list. The filter options vary depending
on the content of the table list.
Use the filter options, for example,
to show specific objects in the list.
Click Any object in the Filter By
Object section to select an object
from the device tree with the object
selector 225 .
222
Enter one or more tags 142 into the

field Filter By Tags to filter the list
for corresponding objects. You can
use the plus sign (+) and the minus
sign (-) to categorize tags as must
have this tag or does not need this
tag.
For performance reasons, it can

take some minutes until you
can filter for new tags that you
added.
Date Ranges
Range Description Example (Based on 14.01.2023)
Today Start: 00:00 of today 2023-01-14 (00:00) - 2023-01-15 (00:00)

End: 00:00 of tomorrow
Yesterday Start: 00:00 of yesterday 2023-01-13 (00:00) - 2023-01-14 (00:00)

End: 00:00 of today
7 days Start: 00:00 of 7 days ago 2023-01-07 (00:00) - 2023-01-15 (00:00)
30 days Start: 00:00 of the same 2022-12-14 (00:00) - 2023-01-15 (00:00)

day last month
6 months Start: 00:00 of the same 2022-07-14 (00:00) - 2023-01-15 (00:00)

day 6 months ago
12 months Start: 00:00 of the same 2022-01-14 (00:00) - 2023-01-15 (00:00)

day 12 months ago
223
Range Description Example (Based on 14.01.2023)
Unlimited Start: 00:00 of the same 2016-01-14 (00:00) - 2023-01-15 (00:00)

day 7 years ago (historic
data 188 for logs is limited
to 750 days)
224
6.14 Object Selector
For some features, you need to select an object, for example, when you want to create historic data
reports. In this case, PRTG uses the object selector with which you can browse all objects in your
installation to select an object in two steps.
Object Selector
Step 1: Browse Device Tree

On the left-hand side, you see your specific device tree setup with all probes, groups, and devices. Click
to collapse an object. Click to expand the object again and show its subobjects.
Click a device to view its sensors on the right-hand side.
You can also directly search for an object in the device tree. To do so, enter a probe name, group name,
or device name into the Search box on the left-hand side. You can also use a substring for the search.
Step 2: Select or Find Object

Select a device on the left-hand side to see the sensors on this device on the right-hand side. PRTG
displays the name of the sensor as well as the sensor type. Hover over a sensor to view its parent
objects.
You can also directly search for a sensor in the sensor list. To do so, enter the sensor name, group
name, device name, or tag into the Find box on the right-hand side.
225
Select a sensor and click OK.
226
6.15 Priority and Favorites
You can set priorities for all your monitoring objects and also mark devices or sensors as favorites. Both
settings affect how PRTG displays your objects.
PRTG stores priority and favorites settings for the entire installation. The settings are not user
specific.
Priority for All Objects

The priority setting affects the order by which PRTG lists your objects in table lists 221 . PRTG lists
objects with a higher priority first. Furthermore, a device displays gauges for sensors with a high priority
on its Overview tab.
To change the priority settings, right-click an object to open its context menu 232 and select
Priority/Favorite. You can choose from the top priority with 5 stars ( ) to the lowest priority with
one star ( ). By default, PRTG sets all objects to the medium priority with 3 stars ( ). In
the page header bar 174 and in table lists, you can directly set a priority via the star icons.
Context Menu: Priority
For a sensor, select a priority of 4 or 5 stars to display its the gauge of its primary channel on the
Overview tab of its parent device.
For a map, select a priority of 5 stars to display it as a menu item under Home in the main menu
bar 253 .
Favorites for Devices and Sensors

To open a list of all your favorite devices or sensors, select Devices | Favorite Devices or Sensors |
Favorite Sensors from the main menu bar. These lists are sorted by priority as well.
You can mark any device or sensor as a favorite to add it to the favorites list. Right-click an object to
open its context menu. Select Priority/Favorite | Add to Favorites. PRTG adds a dark gray flag icon ( )
next to the object's name in the device tree to mark the object as a favorite.
227
Context Menu:
Priority/Favorites (Add)
To remove an object from the favorites list, select Priority/Favorite | Remove from Favorites from the
context menu. The flag icon turns transparent ( ).
Context Menu: Priority/Favorites

(Remove)
There is also the option to add a device or sensor to your favorites with one click in the device tree. Click
the flag icon to the right of the respective object name. To make an object a favorite, click . The flag
turns dark gray. To remove an object from your favorites, click . The flag turns transparent.
One-Click Adding to Favorites in the Device Tree
228
Priority and Favorites in the Page Header Bar
You can also add any device or sensor to your favorites on the respective object's Overview tab. To do
so, click in the page header bar of a device or in the page header bar of a sensor. Click for a
device or for a sensor to remove the respective object from your favorites.
One-Click Favorite and Priority in the Page Header Bar
It is also possible to set the priority of an object via the five stars in the page header bar.
means top priority, means lowest priority.
229
6.16 Pause
Several options are available to pause monitoring. You can pause monitoring for a single sensor or for an
entire device, group, or probe.
Pause by Intention (Manually or by Schedule)

Navigate to an object in the device tree 168 and select Pause from the context menu 232 .
You can select Pause Indefinitely, or you can pause the object For 5 Minutes, For 15 Minutes, For 1
Hour, For 3 Hours, For 1 Day, or Until a specific date. If you select Until, you can additionally define a
time period. Use the date time picker to enter the date and time. The object automatically resumes
monitoring after this time period.
You can also set up a One-time Maintenance Window to automatically pause an object at a specified
time. In the dialog that appears, define the start and end date of the maintenance window. Use the date
time picker to enter the date and time.
To cancel an active maintenance window before the defined end date, change the time entry under
Maintenance Ends to a date in the past.
If you select from an object's hover popup 251 , the object is paused indefinitely until you resume
monitoring again.
When you select a pause option, a dialog appears in which you can optionally enter a message. PRTG
shows the message in the object's status message as long as the object is in the Paused status.
Confirm with OK to pause the object.
Pause Message Prompt
230
You can also pause monitoring via schedules 2856 . If you pause a master sensor by schedule or
manually, you do not trigger a status change by dependency 231 .
For more information, see the Knowledge Base: Why will dependent objects not automatically
pause when I pause the master object?
While a sensor is in the Paused status 184 , it does not collect any monitoring data, it does not
change its status, and it does not trigger any notifications 146 . An object also keeps the Paused status
after a restart of PRTG.
Pause by Hierarchy
If you pause monitoring for an object in the device tree, PRTG pauses all objects underneath in the
object hierarchy 136 as well. For example, if you pause a group, PRTG also pauses all sensors on all
devices in this group. After you pause an object, you can resume monitoring at any time by selecting
Resume from the context menu.
You cannot resume monitoring for single child objects that are paused by a parent object. You can
only resume the object that you originally set to the Paused status.
Pause by Dependency
There is a way to automatically pause objects by dependency. If you have a master sensor, for example,
a master Ping sensor for a device, PRTG can automatically pause all dependent sensors on the device if
the master sensor shows the Down status.
For more information, see section Dependencies 144 .
More
KNOWLEDGE BASE
231
6.17 Context Menus
Right-click an object to view a context menu with many options for direct access to monitoring data and
functions. The content of the context menu varies depending on the type of object.
To view your browser's context menu, press the Ctrl key (Google Chrome) or the Shift key (Mozilla
Firefox) while right-clicking. You then see the context menu of your browser instead of the context
menu of PRTG. This is not possible with Internet Explorer.
In this section:
§ Probe Context Menu 232
§ Group Context Menu 236
§ Device Context Menu 240
§ Sensor Context Menu 246
Probe Context Menu

The Probe Context Menu contains actions for your local probe, hosted probe, cluster probe, or remote
probe 137 .
Probe Context Menu
Action Description
Scan Now Perform an immediate scan of the object. This queries data for all objects
underneath in the object hierarchy 136 .
232
Action Description
Details Show the Overview tab of the object.
For more information about the Overview tab, see the Knowledge
Edit Hover over Edit to show the Edit menu. The following actions are
available:
Edit Context Menu
§ Settings: Open a dialog to edit the probe settings 474 .

§ Notification Triggers: Open the Notification Triggers 232 tab of the
object.
§ Access Rights: Open a dialog to edit the access rights 149 for the
object.
§ Rename: Open a dialog to edit the name of the object.
§ Management: Open the Management tab 434 of the object.
Add Group Open a dialog that guides you through the process of adding a new group.
For more information, see section Add a Group 329 .
Add Auto-Discovery Open a dialog that guides you through the process of adding a new auto-
Group discovery group. PRTG creates a new group and runs an auto-discovery
in your network to automatically add devices and sensors.
For more information, see section Add an Auto-Discovery Group 274 .
This option is not available on the hosted probe of a PRTG Hosted

Monitor instance.
Add Device Open a dialog that guides you through the process of adding a new
device.
For more information, see section Add a Device 379 .
Sort Alphabetically Sort direct child objects in alphabetical order.
233
Action Description
PRTG stores the sorting order in the monitoring configuration. You

cannot undo it.
Delete Delete the object. PRTG asks for confirmation before it actually deletes
an object.
You cannot delete local probes or hosted probes.
Move Hover over Move to open the Move menu. The following actions are
available:
Move Context Menu
§ Top: Move the object to the top of the parent object.
§ Up: Move the object one entry up.
§ Down: Move the object one entry down.
§ Bottom: Move the object to the bottom of the parent object.
Pause Hover over Pause to open the Pause menu. The following actions are
available:
or
Resume
Pause Context Menu
§ If the object already shows the Paused status or if it shows the

184
Down status because of a simulated error, the Resume option appears.

Click Resume to restart monitoring on the object. Use the date time
picker to enter the date and time. The object automatically resumes
234
Action Description
§ You can also set up a One-time Maintenance Window to automatically

pause the object at a specified time. In the dialog that appears, define
the start and end date of the maintenance window. Use the date time
picker to enter the date and time.
To cancel an active maintenance window before the defined end date,
change the time entry under Maintenance Ends to a date in the past.
§ If the object already shows the Paused status 184 or if it shows the
Click Resume to restart monitoring on the object.
Priority Hover over Priority to open the Priority menu. Define the priority of the
object.
Priority Context Menu
Historic Data Hover over Historic Data to open the Historic Data menu. The following
actions are available:
Historic Data Context Menu
§ Open the historic data tabs for the specified time interval: Last 2 days,
Last 30 days, or Last 365 days.
For more information, see the Knowledge Base: What options do I
have to review my monitoring data in detail?
§ Create Report: Open a dialog to add a new report.
When you create a report via the context menu, PRTG
automatically includes the selected probe in the report.
For more information, see the Paessler website: How to set up
reports in PRTG in 5 easy steps.
235
Action Description
Send Link by Email Send a link to the object by email. Click to create a new email with your
system's standard email client. The email contains a direct link to the
Overview tab of the object.
Add Ticket Open the Add Ticket dialog.
Group Context Menu

The Group Context Menu contains actions for your groups 137 .
The context menu of the root group differs from the other groups' menu.
Group Context Menu
Action Description
236
Action Description
available:
Edit Context Menu
§ Settings: Open a dialog to edit group settings 541 for the group.
object.
object.
Add Group Open a dialog that guides you through the process of adding a new group.
For more information, see section Add a Group 329 .
Add Auto-Discovery Open a dialog that guides you through the process of adding a new auto-
Group discovery group. PRTG creates a new group and runs an auto-discovery
in your network to automatically add devices and sensors.

Monitor instance.
Add Device Open a dialog that guides you through the process of adding a new
device.
For more information, see section Add a Device 379 .
Auto-Discovery This option is only available for auto-discovery groups or devices that have
the auto-discovery feature enabled 544 .
237
Action Description
Hover over Auto-Discovery to show the Auto-Discovery menu. The

following actions are available:
Auto-Discovery Context Menu
§ Run Auto-Discovery: Immediately start a search to automatically add

new devices and sensors to the group. The search runs in the
background and uses the options you set for the Auto-Discovery
Level 544 in the group settings under Auto-Discovery Settings. If there
are new devices and sensors, you see them after a few minutes.
For more information, see section Auto-Discovery 271 .
§ Run Auto-Discovery with Template: Open a dialog to start an automatic
search with a standard, detailed, or custom device template.
If you select this option from the context menu, the options you set
for the Auto-Discovery Level in the object settings do not apply.

Monitor instance.

cannot undo it.
an object.
Clone Open a dialog that guides you through the process of cloning the object.
For more information, see section Clone Object 2725 .
available:
238
Action Description
Move Context Menu
§ To Other Group: Move the object to a different group to become a

subgroup.
available:
or
Resume
Pause Context Menu
§ If the object already shows the Paused status or if it shows the

184

239
Action Description

Priority Hover over Priority to open the Priority menu. Define the priority of the
object.

Device Context Menu

The Device Context Menu contains actions for your devices 138 .
240
Device Context Menu
Action Description
available:
Edit Context Menu
§ Settings: Open a dialog to edit device settings 612 for the device.
241
Action Description

object.
object.
Add Sensor Open a dialog that guides you through the process of adding a new
sensor to the device.
For more information, see section Add a Sensor 430 .
Auto-Discovery This option is only available for auto-discovery groups or devices that have
the auto-discovery feature enabled 544 .
Hover over Auto-Discovery to show the Auto-Discovery menu. The

following actions are available:
§ Run Auto-Discovery: Immediately start a search to automatically add
new sensors to the device. The search runs in the background and
uses the options you set for the Auto-Discovery Level in the device
settings under Auto-Discovery Settings. If there are new sensors, you
see them after a few minutes.
If you set the option No auto-discovery for the Auto-Discovery Level in

the device settings and start the auto-discovery from the context
menu, PRTG runs it with the standard device identification and changes
the device setting to Standard auto-discovery (default).
§ Run Auto-Discovery with Template: Open a dialog to start an automatic

search with a standard, detailed, or custom device template.
If you select this option from the context menu, the options you set
for the Auto-Discovery Level in the object settings do not apply.

Monitor instance.
Create Device Template Open a dialog that guides you through the process of creating a new
device template. The template is then available for the auto-discovery.
For more information, see section Create Device Template 2735 .
Recommend Now This option is only available if the Recommended Sensors Detection 2884 is
enabled.
242
Action Description
Start an analysis to get sensor recommendations for the device. When

PRTG finishes the analysis of the device, you see the recommended
sensors in a table list on the device's Overview tab where you can directly
add the respective sensors.

cannot undo it.
an object.
available:
Move Context Menu
§ To Other Group: Move the object to a different group.
available:
or
Resume
243
Action Description
Pause Context Menu


Priority/Favorite Hover over Priority/Favorite to open the Priority/Favorite menu. Define the
priority of the object, add the object to the favorites list, or remove it from
the favorites list.
244
Action Description
Device Tools Hover over Device Tools to open the Device Tools menu. The following

Monitor instance.
Device Tools Menu
§ Go to Service URL: Open the service page that you defined in the
device settings 612 . If no service URL is available for the device, you can
enter an address in the dialog that appears.
§ New Window with HTTP: Open a new browser window with HTTP and
the IP address or Domain Name System (DNS) name of the device.
§ New Window with HTTPS: Open a new browser window with HTTPS
and the IP address or DNS name of the device.
§ New Window with FTP: Open a new browser window with the File
Transfer Protocol (FTP) and the IP address or DNS name of the device.
§ Remote Desktop: Download an .rdp file. When you execute this file, a
remote desktop starts with the IP address or DNS name of the device.
In Firefox, you must use mstsc.exe (Microsoft Terminal Service) to
open the file.
§ Traceroute: Start a traceroute on the device. PRTG displays the route
and measures transit delays of packets across the IP network.
§ Install Remote Probe: Open a dialog to install a classic remote probe
on the device. For more information, see section Classic Remote Probe
Setup via Device Tools 3207 .
This option is only available on devices on local probes.
Find Duplicates In your configuration, search for devices with the same IP address or DNS
name as the selected device.
245
Action Description

Sensor Context Menu

The Sensor Context Menu contains actions for your sensors 138 .
Sensor Context Menu
Action Description
Scan Now Perform an immediate scan of the object.
available:
§ Settings: Open a dialog to edit settings for the sensor.

object.
object.
246
Action Description
Acknowledge Alarm This option is only available in the sensor context menu when you select
a sensor in the Down or Down (Partial) status.
You can acknowledge an alarm for the sensor. A sensor with an

acknowledged alarm shows the Down (Acknowledged) status and does
not trigger 2704 any more notifications 2745 . The following actions are
available:
Acknow ledge Alarm Context Menu
§ Acknowledge Indefinitely
§ Acknowledge the alarm for a certain period of time:
ú For 5 Minutes
ú For 15 Minutes
ú For 1 Hour
ú For 3 Hours
ú For 1 Day
ú Until: Define a custom time period to acknowledge the alarm. Use

If the alarm condition still exists after this time period, the sensor
shows the Down status again.
When the alarm condition clears, the sensor usually returns to the
Up status immediately with the next sensor scan.
For more information about acknowledging an alarm, see section
Alarms 206 .
an object.
247
Action Description
available:
Move Context Menu
available:
or
Resume
Pause Context Menu

248
Action Description
Simulate Error Status Manually set the sensor to the Down status. If the sensor already shows
the Down status because of a simulated error, the Resume option
appears. Click Resume to restart monitoring.
The Simulate Error Status option does not work for sensors that run
on mini probes.
Priority/Favorite Hover over Priority/Favorite to open the Priority/Favorite menu. Define the
priority of the object, add the object to the favorites list, or remove it from
the favorites list.
§ View Historic Data: Open the Historic Data tab 188 .


More
KNOWLEDGE BASE

249
PAESSLER WEBSITE
How to set up reports in PRTG in 5 easy steps

§ https://www.paessler.com/support/how-to/reports
250
6.18 Hover Popup
When you rest the mouse pointer over an object's icon in the device tree 168 or in table lists 221 , for
example, a hover popup window appears and shows details about this object. The hover popup contains
information from the object's Overview tab as well as several graphs. The exact information that PRTG
provides depends on the type of object.
Hover Popup Example: Core Health Sensor
The hover popup only appears if your browser window that shows the PRTG web interface is the
active window on your desktop. The hover popup disappears with every (automatic) page refresh.

In the top-right corner of the hover popup window, you can see several quick action buttons with which
you can view or edit the object. These are the most important options from the object's context menu 232 .
The available buttons depend on the type of object that you hover over.
Action Description
Details ( ) Show the Overview tab of the object.
251
Action Description
Settings ( ) Open the object's settings.
Notification Triggers ( ) Show the Notification Triggers tab of the object.
Rename ( ) Open a dialog to edit the name of the object.
Pause Indefinitely ( ) Indefinitely pause the object and all objects underneath in the object
hierarchy 136 . If you want to resume monitoring, you must manually
resume the paused object.
Resume ( ) Resume monitoring for the object and all objects underneath in the object
hierarchy.
Delete ( ) Delete the object. PRTG asks for confirmation before it actually deletes
an object.
Scan Now ( ) Perform an immediate scan of the object. This queries data for all objects
underneath in the object hierarchy.
Add to Favorites ( ) Make the object a favorite 227 and add it to your favorites list.
Remove from Favorites ( Remove the object from your favorites list.
)
More
KNOWLEDGE BASE

252
6.19 Main Menu Structure
You can access all functions via the main menu bar. In this section, you find information about the most
important menu items. You can either directly click a menu item or you can hover over it to show more
options.
Main Menu Bar
In this section:
§ Home 253
§ Devices 254
§ Libraries 256
§ Sensors 257
§ Alarms 260
§ Maps 260
§ Reports 261
§ Logs 262
§ Tickets 263
§ Setup 265
§ Search Box 267
§ Logout 267
Home
Click to open your home page. The default home page is the Welcome page 168 . Hover over Home to
show other options.
Main Menu: Home
253
Option Description
Sample Dashboard Open a preconfigured dashboard to view monitoring data in a different

layout. This dashboard is one of the default maps 2786 that PRTG
automatically creates with a new installation.
The Home menu shows maps that have a 5-star priority 227 (
) To show a map here, give it 5 stars on the Maps overview
via the main menu bar 260 . You can include up to 10 map entries in the
menu. For more information, see section Home Menu 2788 .
You can change the appearance of the default dashboard with the
Map Designer 2790 . To not show the sample dashboard in the menu,
define a priority that is lower than 5 stars for this map.
Switch Cluster Node This option is only available if PRTG runs in a failover cluster 132 .
Show available cluster nodes. Hover over Switch Cluster Node to show
other options. Follow the menu path that is specific to your setup to
select a different cluster node. The current master node is shown in bold
letters. Click a cluster node's name to leave the current cluster node, to
connect to the other cluster node, and to show the same page there.
Welcome to PRTG Open the Welcome page that shows the Paessler news feed and various
information about your PRTG installation. It also provides links to major
sections of the PRTG web interface.
This is the default home page of the PRTG web interface.
Make This My Home Change the page that is loaded when you click Home in the main menu
Page bar. Select this option on any page to set its URL as your home page.
This setting is user sensitive. The default home page is /welcome.htm.
You can also change the home page under Home Page URL in the
My Account 2811 settings.
Devices
Click to show the device tree. Hover over Devices to show other options.
254
Main Menu: Devices
Option Description
All Open the Overview tab of the root group 136 that shows the device tree 168 .
Favorite Devices Open a table list 221 of all devices that you marked as favorites 227 . Click
to show a printable list of the QR codes of all your favorite devices.
To mark any device as a favorite device, select Priority/Favorite | Add
to Favorites from its context menu, or click on a device's Overview
tab.
Device List Open a list of all devices in your setup.
Dependencies Open an overview list of the dependencies 144 configured for the objects in
your setup. You can select dependencies and define master
dependencies in the Schedules, Dependencies, and Maintenance
Window object settings 204 (not available for the root group).
Add Group Start a dialog that guides you through the process of adding a new group
to your setup.
For more information, see section Create Objects Manually 273 .
You can also create new groups by selecting Add Group from a
probe's or group's context menu.
Add Auto-Discovery Start a dialog that guides you through the process of adding a new auto-
Group discovery group to your setup. PRTG creates a new group and runs an
auto-discovery in your network to automatically add devices and sensors
to this group.
255
Option Description
You can also create new auto-discovery groups by selecting Add

Auto-Discovery Group from a probe's or group's context menu.

Monitor instance.
Add Device Start a dialog that guides you through the process of adding a new device
to a group. During the process, you can choose if PRTG runs an auto-
discovery for the new device to automatically add sensors.
For more information, see section Create Objects Manually 273 .
You can also create new devices by selecting Add Device from a
group's context menu.
Libraries
Click to open the Libraries list where you can view or add custom device tree views of your network
status and monitoring data. Hover over Libraries to show other options.
For more information, see section Libraries 2748 .
Main Menu: Libraries
Option Description
All Open the Libraries list where you can view or add custom device tree
views of your network status and monitoring data.
Add Library Open a dialog to create a new library.
Select Library Open a library. Hover over Select Library to show more options. Follow
the alphabetical menu path that is specific to your setup to view your
libraries. Click a library to open it.
256
Sensors
Click to open a list of all sensors 138 . Hover over Sensors in the main menu bar to show other options.
Main Menu: Sensors
Option Description
All Open a table list of all sensors 138 . In list, you can sort the items via the
column headers.
The column Last Value shows only the last value of the sensor's
primary channel.
Add Sensor Start a dialog that guides you through the process of adding a new sensor
to a device. For more information, see section Add a Sensor 430 . During
the process, you can also choose to create a new device via the Add a
Device 379 dialog, which you can also open directly from the Devices
menu 254 .
257
Option Description
Favorite Sensors Open a list of all sensors that you marked as favorites.
To mark any sensor as a favorite sensor, select Priority/Favorite |
Add to Favorites from its context menu or click on a sensor's
Overview tab.
Top 10 Lists Open a dashboard view with different top 10 lists that show the highest
uptime or downtime, ping response times, the bandwidth usage, website
response times, the CPU usage, the disk usage, the memory usage, and
the system uptime. Click to show top 10 lists for all sensors. Hover over
Top 10 Lists to show other options. Follow the menu path that is specific
to your setup to only view top 10 lists for a specific probe or group.
The shown sensors are selected by default tags.
By Current Value Open a list of sensors filtered by value. Hover over By Current Value to
show other options. Follow the menu path to view lists of sensors with the
Fastest Value or the Slowest Value for
§ Ping
§ Port
§ Web Pages
§ IMAP/POP3/SMTP
§ FTP
as well as a list of sensors with the Highest Value or the Lowest Value
regarding
§ Bandwidth
§ CPU
§ Disk
§ Memory
The shown sensors are selected by default tags.
By Current Status Open a list of sensors filtered by status. Hover over By Current Status to
show other options. Follow the menu path to view lists of all sensors in a
specific status.
For more information, see section Sensor States 184 .
By Uptime/Downtime Open a list of sensors filtered by different parameters. Hover over By

Uptime/Downtime to show other options. Follow the menu path to view
lists of all sensors sorted by
258
Option Description
§ Best Uptime (%)
§ Highest Uptime (Time)
§ Worst Downtime (%)
§ Highest Downtime (Time)
By Type Open a list of sensors filtered by sensor type 3237 . Hover over By Type to
show other options. Follow the alphabetical menu path that is specific to
your setup to view a sensor list that contains only sensors of one specific
sensor type.
By Tag Open a list of sensors filtered by tag 142 . Hover over By Tag to show other
options. Follow the alphabetical menu path that is specific to your setup
to see available tags. Select a tag to view a list that contains only
sensors marked with this tag.
If you have more than 1,000 tags, no tags are shown here. For more
information, see section Tags 143 .
By Performance Impact Open a list of sensors filtered by performance impact 2962 . Follow the
menu path to view a sensor list that contains only sensors with a specific
level of impact on the performance of the probe:
§ Very High
§ High
§ Medium
§ Low
§ Very Low
For an overview list of all sensors, including their performance impact,

see section Available Sensor Types 3237 .
Cross Reference Open the sensor cross reference to show information about all sensors
including priority and favorite 227 status, scanning interval 466 , access
rights 149 , notification trigger settings 204 , schedules 145 , and
dependencies 144 . Click to show a sensor cross reference for all sensors.
Hover over Cross Reference to show other options. Follow the menu path
that is specific to your setup to view cross reference information for
sensors by type or tag.
View Historic Data Open a dialog to generate historic sensor data reports.
For more information, see section Historic Data Reports 188 .
Similar Sensors Overview Open an overview with a list of similar sensors.
259
Option Description
For more information, see section Similar Sensors 195 .
Alarms
Click to open a list of all sensors that show the Down, Down (Partial), Down (Acknowledged), Warning,
or Unusual status. Hover over Alarms to show other options.
Main Menu: Alarms
Option Description
All Open a list of all sensors that are in the Down, Down (Partial), Down
(Acknowledged), Warning, or Unusual status.
Show as Gauges Open a page with the gauges of all sensors that are in the Down, Down
(Partial), Down (Acknowledged), Warning, or Unusual status. The size of
the gauges corresponds to the sensor's priority.
Errors Only Open a list of all sensors that are in the Down, Down (Partial), or Down
Warnings Only Open a list of all sensors that are in the Warning status.
Unusuals Only Open a list of all sensors that are in the Unusual status.
Maps
Click to open the Maps overview where you can view or add custom views of your network status and
monitoring data. Hover over Maps to show other options.
260
For more information, see section Maps 2786 .
Main Menu: Maps
Option Description
All Open the Maps list where you can view or add custom views of your
network status and monitoring data.
Add Map Open a dialog to create a new map.
Select Map Hover over Select Map to show a list of your maps. Click a map to open
it.
Reports
Click to open the Reports overview where you can view or add reports about your monitoring data. Hover
over Reports to show other options.
For more information, see section Reports 2764 .
Main Menu: Reports
Option Description
All Open the Reports list where you can view or add reports about your
monitoring data.
261
Option Description
Add Report Open a dialog to create a new report.
Select Report Hover over Select Report to show a list of your reports about monitoring
data. Click a report to open it.
Configuration Reports Hover over Configuration Reports to see the available configuration
reports 2767 . Select an item to create reports for maps, reports, users and
user groups, and system configuration to document changes to the
configuration.
Logs
Click to show log information for all objects in your configuration. Hover over Logs to show other options.
Logs for monitoring objects, such as sensors, are available as long as you define Log File Records
in the Historic Data Purging settings under Setup | System Administration | Core & Probes.
Main Menu: Logs
Option Description
All Open a list with log information about all objects in your installation. The
list begins with the most recent log entry.
Status Changes Open a list with log information about specific status changes. Hover over
Status Changes to choose from the following sensor states:
§ Up & Down
§ Down
§ Warning
§ Unusual
262
Option Description
§ Up
§ Paused/Resumed
§ Acknowledged Alarms
System Events Open a list with log information about specific system event types. Hover
over System Events to choose from the following event types:
§ Report Related
§ Cluster Related
This event type only appears if you have a cluster.
§ Auto-Discovery Related
§ Notifications Related
§ Status Message Related
Object History Open a list with log information about changes to the PRTG setup and
deletions of subordinate system objects. The Object History has several
tabs. To view the changes to all related settings and deletions of objects,
use the following tabs:
§ My Account
§ System Administration
§ Notification Templates
§ Schedules
§ User Accounts
§ User Groups
§ Reports
§ Schedules
§ Maps
You can also navigate to a corresponding page, for example, you can
select Setup | Account Settings | My Account from the main menu
bar, and click in the page header bar 174 to directly go to the related
object history tab.
Tickets
Click to show all open tickets that are assigned to you. Hover over Tickets to show other options.
263
Main Menu: Tickets
Option Description
My Tickets Open a list of all open tickets that are assigned to you. Hover over My
Tickets to show other options to filter these tickets according to their
status.
All Tickets Open a list of all open tickets of all users. Hover over All Tickets to show
other options to filter these tickets according to their status.
All Tickets Open a list of open tickets of the type ToDo. Hover over All Tickets to
show other options to filter these tickets according to their status.
Add Ticket Open the Add Ticket dialog to create a user ticket.
For more information about available options, see section Tickets 216
Setup
Click to show the setup page. Hover over Setup to show other options.
For more information, see section Setup 2809 .
264
Main Menu: Setup
Option Description
Overview Open the setup page 2809 .
Account Settings Open the My Account 2811 settings. Hover over Account Settings to
directly show and open the account settings tabs:
§ My Account 2811
§ Notification Templates 2818
§ Notification Contacts 2851
§ Schedules 2856
System Administration Open the System Administration 2865 settings. Hover over System
Administration to directly show and open the system administration tabs:
§ Manage Subscription
§ User Interface 2865
§ Monitoring 2879
§ Notification Delivery 2887
265
Option Description
§ Core & Probes 2897
§ Cluster 2933
§ User Accounts 2911
§ User Groups 2922
§ Administrative Tools 2928
§ Single Sign-On 2935
PRTG Status Open the System Status 2945 page. If you run PRTG in a cluster, hover
over PRTG Status to show other options:
§ System Status 2945
§ Cluster Status 2970
License Information Open the license information 2972 page.
Auto-Update Open information about the Software Auto-Update 2979 status of your
PRTG installation. On this page, you can also download and install
available updates. Hover over Auto-Update to show other options:
§ Status 2979 : View the update status and manually check for the latest
update.
§ Settings 2979 : Define your update settings.
Optional Downloads Open the download page 2984 for additional downloads. Hover over Optional
Downloads to show other options:
§ PRTG Apps 2984
§ PRTG app for desktop 2984
§ Classic Remote Probe Installer 2984
PRTG API Open the Application Programming Interface (API) Definition 3094 .
Help and Support Center Open the Help and Support Center 2986 from where you can access the
PRTG Manual, the Knowledge Base, and video tutorials. You can also
open support tickets 2987 and contact our customer service 165 from this
page.
266
Option Description
Contact Support Open the Contact Paessler Support / Send Your Feedback to
Paessler 2987 form.
Search Box
Main Menu: Search Box
Click the Search box to find objects in your monitoring setup. Enter your search term and press the
Enter key. PRTG performs a string search in your entire monitoring setup, including groups, devices,
sensors, libraries, maps, reports, tickets, and object comments, as well as in the PRTG Manual. You
see all search results on a new page.
You can only search for names that are actually displayed. To search for a specific user, for
example, use their display name. You cannot search for the user's login name or email address.
PRTG uses different logical operators for the search in tickets and for the search in other objects.
For the ticket search, PRTG uses the logical operator OR. If you search for a string like 'operating
system', for example, you receive results for all tickets that contain either 'operating' or 'system' or both.
For all other objects, PRTG uses the logical operator AND. So you receive results for all other objects
that contain both 'operating' and 'system'.
Logout
Click to log out of PRTG and return to the login screen 157 .
267
Part 7
Device and Sensor Setup
268 4/19/2023
7 Device and Sensor Setup
In this section:
§ Auto-Discovery 270
§ Create Objects Manually 273
ú Add an Auto-Discovery Group 274
ú Add a Group 329
ú Add a Device 379
ú Add a Sensor 430
§ Manage Device Tree 434
§ Root Group Settings 436
§ Probe Settings 474
§ Group Settings 541
§ Device Settings 612
§ Sensor Settings
§ Additional Sensor Types (Custom Sensors) 2687
§ Channel Settings 2692
§ Notification Triggers Settings 2704
269
7.1 Auto-Discovery
The auto-discovery automatically creates a set of sensors for all of the devices that are in your network.
The auto-discovery is primarily intended for devices that are in the same network as your probes.
Unless you skip the auto-discovery during the installation process, PRTG runs an initial auto-
discovery as soon as you finish the installation of PRTG. It automatically shows you the devices that
are available in your network as well as suitable sensors for monitoring.
How the Auto-Discovery Works

The auto-discovery has three steps:
1. Scan a network segment for devices via ping (at the group level only).
2. Assess the device type for all of the devices that it discovered in step 1 (via the Simple Network
Management Protocol (SNMP), Windows Management Instrumentation (WMI), and other protocols).
3. Create sensor sets that match the discovered device types from step 2. It does this based on built-in
device templates that have recommended sensors for many device types. Optionally, it can also
create sensor sets via device templates that users created 2735 .
You can use auto-discovery groups 274 to use the auto-discovery for a range of IP addresses or for
individual devices that you manually created. You can run the auto-discovery one time, on demand via
the context menu, or via schedule at every hour, day, or week. If you run the auto-discovery at group level
daily or weekly, it automatically creates new devices when they connect to the network and it adds
suitable sensors.
PRTG creates a notifying ticket 216 when it discovers at least one new device or sensor. You also
receive a ticket if an error occurs. By default, PRTG also sends tickets via email. You can change
this in the My Account 2817 settings.
HTTP sensors' names indicate the protocol that they use to access the target device (HTTP, HTTP
(8080), and HTTPS). This distinguishes HTTP sensors from each other if the auto-discovery adds
more than one HTTP sensor to a device.
Restrictions
Note the following restrictions of the auto-discovery:
§ PRTG cannot discover devices that are not reachable via ping. This is because step 1 scans for
devices via ping. If, for example, a firewall blocks echo requests, PRTG cannot discover a device
behind the firewall.
§ Define credentials for objects that are higher in the object hierarchy, for example, in the settings of
136
the parent device. If possible, we recommend that you define these settings in the root group 436 .
§ If a device has more than one IP address, it might show up more than once in the auto-discovery
results, even though PRTG tries to identify these situations.
§ Auto-discovery on group level does not create new sensors on devices that already exist, but only on
newly discovered devices. If you want to automatically add sensors to a device, run the auto-discovery
on the device via its context menu 240 .
270
§ Frequent auto-discoveries of large network segments can lead to performance issues. Because of this
we recommend that you only schedule regular auto-discoveries where necessary.
For more information, see the Knowledge Base: Why can automatic auto-discoveries evoke
performance issues?
§ PRTG automatically adds suitable device icons to discovered devices. PRTG uses a device's MAC
address for this purpose, which it determines via the Address Resolution Protocol (ARP). This only
works via IPv4 and not via IPv6. Usually, ARP works only in the local network unless your router
supports ARP and you configure it accordingly.
§ The auto-discovery does not apply the user group setting 2924 Allowed Sensors. Therefore, the auto-
discovery adds all sensors that are defined in the used device templates.
Run the Auto-Discovery Now

You can run an auto-discovery at any time on a specific device. To do so, right-click the device and
select Auto-Discovery | Run Auto-Discovery from the context menu. PRTG immediately starts to search
for new sensors to add to the device. If you use the auto-discovery for an auto-discovery group, PRTG
adds devices with suitable sensors, if it finds any. If you use it for a device, PRTG adds new sensors, if
found. In the corresponding page header bar 174 , you can always see when PRTG ran the last auto-
discovery on a selected group or device.
Auto-discovery for groups is not available on hosted probes.
The auto-discovery also adds manually deleted devices or sensors again. If you do not want this to
happen, you must always create objects manually 273 .
Auto-Discovery in Progress
While the auto-discovery is in progress, you might experience a lower system performance than usual,
because PRTG is working in the background to discover your network. Depending on the IP address
ranges defined (up to 65,536 addresses), the discovery might run for up to several days before it is
complete. You can review the status of the discovery process as follows:
§ In the device tree, next to the group or device name, you can see a percentage value that shows the
progress of the auto-discovery.
§ During the auto-discovery, the PRTG web interface displays a box in the lower-right corner that shows
the number of active auto-discovery tasks.
§ To stop an auto-discovery, right-click the group or device, and select Pause | For 5 Minutes from the
context menu. PRTG pauses 230 monitoring for 5 minutes and stops the auto-discovery tasks.
Disable Initial Auto-Discovery

To disable the initial auto-discovery for a fresh PRTG installation, run the installer in a command prompt
and add /NoInitialAutoDisco=1 as a parameter. This might be useful for performance reasons or if you
prefer to manually add devices and sensors to your installation.
More
KNOWLEDGE BASE
Why can automatic auto-discoveries evoke performance issues?

271
How can I turn off auto-discovery?
How does auto-discovery with SNMP Traffic sensors work?

272
7.2 Create Objects Manually
We recommend that you use the auto-discovery 270 feature to create a basic monitoring setup for your
network. Afterward, you can manually add devices that were not discovered, or arrange 2723 detected
devices in groups.
In this section
§ Add a Group 329
§ Add a Device 379
§ Add a Sensor 430
Add a Remote Probe

273
7.2.1 Add an Auto-Discovery Group
There are several ways to manually add an auto-discovery group:
§ Select Devices | Add Auto-Discovery Group from the main menu bar 254 . A dialog appears that guides
you through the process of starting an automatic detection of devices and sensors in your network.
§ Hover over and select Add Auto-Discovery Group from the menu.
§ Select Add Auto-Discovery Group from the context menu 232 of the probe or group to which you want
to add the new auto-discovery group. This skips step 1 and leads you directly to step 2 277 .
In this section:
§ Step 1: Select a Parent 276
§ Step 2: Define Auto-Discovery Group Settings 277
§ Basic Group Settings 278
§ Auto-Discovery Settings 279
§ Inherited Settings 286
§ Credentials for Windows Systems 286
§ Credentials for Linux/Solaris/macOS (SSH/WBEM) Systems 289
§ Credentials for VMware/XenServer 293
§ Credentials for SNMP Devices 295
§ Credentials for Database Management Systems 300
§ Credentials for AWS 301
§ Credentials for Script Sensors 302
§ Credentials for Cisco Meraki 304
§ Credentials for Dell EMC 304
§ Credentials for FortiGate 306
§ Credentials for HPE 3PAR 306
§ Credentials for HTTP 308
§ Credentials for Microsoft Azure 310
§ Credentials for MQTT 312
§ Credentials for NetApp 315
§ Credentials for OPC UA 317
274
§ Credentials for Soffico Orchestra 320
§ Credentials for Redfish 322
§ Credentials for REST API 324
§ Credentials for Veeam 325
§ Access Rights 326
Add an Auto-Discovery Group

The Add an Auto-Discovery Group dialog appears when you add a new auto-discovery group to a parent
group. It only shows the settings that are required to create the auto-discovery group. Therefore, you do
not see all settings in this dialog.
You can change all settings on the Settings tab of the auto-discovery group later. For more
information, see section Group Settings 541 .
275
Step 1: Select a Parent
Add Auto-Discovery Group Assistant Step 1
Select the probe or group that you want to add the new auto-discovery group to. Click OK.
276
Step 2: Define Auto-Discovery Group Settings
Add Auto-Discovery Group Assistant Step 2
277
Basic Group Settings
Setting Description
Group Name Enter a name to identify the group. By default, PRTG shows this name in
the device tree 168 , as well as in alarms 205 , logs 213 , notifications 2745 ,
reports 2764 , maps 2786 , libraries 2748 , and tickets 216 .
If the name contains angle brackets (<>), PRTG replaces them with
braces ({}) for security reasons. For more information, see the
Knowledge Base: What security features does PRTG include?
Tags Enter one or more tags. Confirm each tag with the Spacebar key, a
comma, or the Enter key. You can use tags to group objects and use
tag-filtered views later on. Tags are not case-sensitive. Tags are
automatically inherited 142 .
It is not possible to enter tags with a leading plus (+) or minus (-)
sign, nor tags with parentheses (()) or angle brackets (<>).
For performance reasons, it can take some minutes until you can
filter for new tags that you added.
278
Auto-Discovery Settings
279
280
Setting Description
Auto-Discovery Level Select the level of detail for the auto-discovery 270 :
§ No auto-discovery: Select this option if you only want to manually
create devices and sensors.
§ Standard auto-discovery (default): Create a set of standard sensors for
standard monitoring. This option works fine for most installations.
§ Detailed auto-discovery: Create all standard sensors and additional

sensors from detailed variants of device templates. As a result, you
might get many sensors. This option is suitable for small network
segments and whenever you want to monitor the maximum number of
sensors available.
§ Auto-discovery with specific device templates: Customize the auto-
discovery and select or combine standard, detailed, and custom device
templates. Select one or more templates from the Device Templates
list.
Auto-discoveries can be resource intensive. They are primarily
intended for devices on the same network as your probes.
Device Templates This setting is only visible if you select Auto-discovery with specific device
templates above.
Select one or more device templates by enabling a check box in front of

the template name. PRTG uses the device templates that you select for
the auto-discovery on the device:
§ ADSL
§ Amazon CloudWatch
§ Buffalo TeraStation NAS
§ Cisco ASA VPN
§ Cisco Device (Generic)
§ Dell EqualLogic
§ Dell MDi Disk
§ DNS Server
§ Environment Jacarta
§ Environment Poseidon
§ FTP Server
§ Generic Device (Ping Only)
§ Generic Device (SNMP Enabled)
§ Generic Device (SNMP Enabled, Detailed)
§ HTTP Web Server
281
Setting Description
§ Hyper-V Host Server
§ IPMI-enabled Device
§ Juniper NS Device
§ Linux/UNIX Device (SNMP or SSH Enabled)
§ Mail Server (Generic)
§ Mail Server (MS Exchange)
§ Microsoft SharePoint 2010
§ NAS LenovoEMC
§ NAS QNAP
§ NAS Synology
§ NetApp
§ NTP Server
§ Printer (HP)
§ Printer (Generic)
§ RDP Server
§ RMON-compatible Device
§ Server (Cisco UCS)
§ Server (Compaq/HP Agents)
§ Server (Dell)
§ Server (Fujitsu)
§ Server (IBM)
§ SonicWall
§ SSL Security Check
§ Switch (Cisco Catalyst)
§ Switch (Cisco IOS Based)
§ Switch (HP Procurve)
§ UNIX/Linux Device
§ UPS Health (APC)
§ UPS Health (Generic)
§ UPS Health (Liebert)
§ VMware ESXi / vCenter Server
§ Web Server
282
Setting Description
§ Windows (Detailed via WMI)
§ Windows (via Remote PowerShell)
§ Windows (via WMI)
§ Windows IIS (via SNMP)
§ XenServer Hosts
§ XenServer Virtual Machines
Once the auto-discovery is finished, PRTG creates a new ticket 216 and
lists the device templates that it used to create new sensors.
Schedule Select when PRTG runs the auto-discovery:

§ Once: Run the auto-discovery only once. PRTG adds new devices and
sensors once. If you select this option, you must manually start the
auto-discovery 271 .
§ Hourly: Run the auto-discovery for new devices and sensors every 60
minutes.
Use this option with caution. Frequent auto-discoveries might
cause performance issues, in particular when PRTG scans large
network segments every hour.
§ Daily: Run the auto-discovery for new devices and sensors every 24
hours. The first auto-discovery runs immediately. All other discoveries
start at the time that you define in the Monitoring 2885 settings, section
Auto-Discovery.
§ Weekly: Run the auto-discovery for new devices and sensors every 7
days. The first auto-discovery runs immediately. All other discoveries
start at the time that you define in the Monitoring settings, section
Auto-Discovery.
For performance reasons, PRTG sets Schedule to Once on all
devices that the scheduled auto-discovery creates.
Auto-Discovery Scanning Select how you want to define the IP address range for the auto-
Method discovery:
§ Class C base IP address with start/end (IPv4) (default): Enter an IPv4
class C address range.
§ List of individual IP addresses and DNS names (IPv4): Enter a list of
individual IPv4 addresses or Domain Name System (DNS) names.
§ IP address and subnet (IPv4): Enter an IPv4 address and subnet mask.
§ IP address with octet range (IPv4): Enter an IPv4 address range for
every IP octet individually. With this, you can define very customizable
IP address ranges.
individual IPv6 addresses or DNS names.
283
Setting Description
§ Use computers from the Active Directory (maximum 1000 computers):

Search in the Active Directory for computers to perform the auto-
discovery.
Make sure that you specify your Active Directory domain in the
Core & Probes 2907 settings.
PRTG can only discover subnets with up to 65,536 IP addresses. If

you define a range with a higher number of addresses, the discovery
stops before it is completed.
IPv4 Base This setting is only visible if you select Class C base IP address with
start/end (IPv4) (default) above.
Enter a class C network as the IP base for the auto-discovery. Enter the
first three octets of an IPv4 address, for example, 192.168.0.
IPv4 Range Start This setting is only visible if you select Class C base IP address with
Enter the IP octet of the class C network (specified above) from which
PRTG starts the auto-discovery. This completes the IP base to an IPv4
address. For example, enter 1 to discover from 192.168.0.1 onwards.
IPv4 Range End This setting is only visible if you select Class C base IP address with
Enter the IP octet of the class C network (specified above) at which PRTG
stops the auto-discovery. This completes the IP base to an IPv4 address.
For example, enter 254 to discover up to 192.168.0.254.
IPv4/DNS Name List This setting is only visible if you select List of individual IP addresses and
IPv6/DNS Name List DNS names (IPv4) or List of individual IP addresses and DNS names
(IPv6) above.
Enter a list of IP addresses or DNS names that the auto-discovery scans.

Enter each address on a separate line.
IPv4 and Subnet (IPv4) This setting is only visible if you select IP address and subnet (IPv4)
above.
Enter an expression in the format address/subnet, for example,

192.168.3.0/255.255.255.0. You can also use the short form like
192.168.3.0/24. PRTG scans the complete host range (without network
and broadcast address) that is defined by the IP address and the subnet
mask.
284
Setting Description
IP Address with Octet This setting is only visible if you select IP address with octet range (IPv4)
Range 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. PRTG calculates all permutations of all ranges. For
example, 10.0.1-10.1-100 results in 1,000 IP addresses that PRTG scans
during the auto-discovery.
Organizational Unit This setting is only visible if you select Use computers from the Active
Directory (maximum 1000 computers) above.
Enter an organizational unit (OU) to restrict the Active Directory search to

computers that are part of this OU. For top-level OUs, use the
distinguished name (DN) format without OU= and without the domain
components (DCS). If you leave this field empty, there are not any
restrictions.
Example:
§ For the DN OU=Domain Controllers,DC=example,DC=com, enter only
Domain Controllers.
If you have sub-OUs, use the DN format without the leading OU= and
without the DCS.
Examples:
§ For the DN OU=webserver,OU=production,DC=example,DC=com, enter
only webserver,OU=production.
§ For the DN
OU=intranet,OU=webserver,OU=production,DC=example,DC=com,
enter only intranet,OU=webserver,OU=production.
Make sure that the OU contains computer accounts. If the OU is
empty, you receive an error message.
Do not enter the domain components. PRTG automatically uses the
domain components from the domain name you enter in the Core &
Probes 2907 settings.
Name Resolution Select how to monitor newly discovered devices. This only affects new
devices. This does not change the setting for other devices. Depending on
your selection, the IP Address/DNS Name field of an added device 614
shows the DNS name or IP address that PRTG uses to access the target
device:
§ Use DNS names (default): Monitor newly discovered devices via their
DNS names (if available) We recommend that you use this option.
§ Use IP addresses: Monitor newly discovered devices via their IP
addresses.
285
Setting Description
This setting does not affect how PRTG shows the devices in the
device tree.
Handling of Already Select how to handle known devices:

Known Devices
§ Skip auto-discovery for existing devices/IP addresses (default): Do not
rescan existing devices or IP addresses. PRTG only adds devices with
new IP addresses or DNS names. PRTG does not add devices that that
already exist in your configuration for example, in other groups. We
recommend that you use this option.
§ Perform auto-discovery for existing devices/IP addresses: Rescan
devices that have existing IP addresses with every auto-discovery.
PRTG adds devices that already exist in other groups to this group and
runs the auto-discovery on the newly added devices.
The auto-discovery does not run on devices that already exist in
the group. If you want to run the auto-discovery for these devices,
you must manually start the auto-discovery on them.
In certain cases, the IP resolution might not work and might result in
PRTG not adding a device if it has the same local IP address as it
does in a different LAN.
Inherited Settings
By default, all of these settings are inherited from objects that are higher in the hierarchy. We
recommend that you change them centrally in the root group settings 436 if necessary. To change a
setting for this object only, click under the corresponding setting name to disable the inheritance
and to display its options.
Credentials for Windows Systems

Click to interrupt the inheritance 140 .
The settings you define in this section apply to the following sensors:
§ Active Directory Replication § Windows MSMQ Queue § WMI Memory

Errors Length
§ WMI Microsoft SQL Server
§ Event Log (Windows API) § Windows Network Card 2005 (Deprecated)
§ Exchange Backup § Windows Pagefile § WMI Microsoft SQL Server
(PowerShell) 2008
§ Windows Physical Disk I/O
§ Exchange Database § WMI Microsoft SQL Server
§ Windows Print Queue
(PowerShell) 2012
§ Windows Process
286
§ Exchange Database DAG § Windows SMTP Service § WMI Microsoft SQL Server
(PowerShell) Received 2014
§ Exchange Mail Queue § Windows SMTP Service Sent § WMI Microsoft SQL Server
(PowerShell) 2016
§ Windows System Uptime
§ Exchange Mailbox § WMI Microsoft SQL Server
§ Windows Updates Status
(PowerShell) 2017
(PowerShell)
§ Exchange Public Folder § WMI Microsoft SQL Server
§ WMI Battery
(PowerShell) 2019
§ WMI Custom
§ File § WMI Remote Ping
§ WMI Custom String
§ File Content § WMI Security Center
§ WMI Disk Health
§ Folder § WMI Service
§ WMI Event Log
§ Hyper-V Cluster Shared § WMI Share
Volume Disk Free § WMI Exchange Server
§ WMI SharePoint Process
§ Hyper-V Host Server § WMI Exchange Transport
§ WMI Storage Pool
§ Hyper-V Virtual Machine
Queue
§ WMI Terminal Services
§ WMI File
§ Hyper-V Virtual Network (Windows 2008+)
Adapter § WMI Free Disk Space (Multi
§ Hyper-V Virtual Storage
Disk) (Windows XP/Vista/2003)
Device § WMI HDD Health
§ WMI UTC Time
§ PerfCounter Custom § WMI Logical Disk I/O
§ WMI Vital System Data v2
§ PerfCounter IIS Application
§ WMI Volume
Pool
§ WSUS Statistics
§ Share Disk Free
§ Windows CPU Load
§ Windows IIS Application
287
Setting Description
Domain or Computer Enter the domain or computer name of the user account with which you
Name want to access the Windows system. PRTG uses this account for
Windows Management Instrumentation (WMI) sensors and other
Windows sensors.
If you want to use a Windows local user account on the target device,
enter the computer name. If you want to use a Windows domain user
account (recommended), enter the domain name. PRTG automatically
adds a prefix to use the NT LAN Manager (NTLM) protocol if you do not
explicitly define it. Do not leave this field empty.
User Name Enter the user name for access to the Windows system. Usually, you
use credentials with administrator rights.
Password Enter the password for access to the Windows system. Usually, you use
credentials with administrator rights.
288
Credentials for Linux/Solaris/macOS (SSH/WBEM) Systems
§ SFTP Secure File Transfer Protocol
§ SSH Disk Free
§ SSH INodes Free
§ SSH Load Average
§ SSH Meminfo
§ SSH Remote Ping
§ SSH SAN Enclosure
§ SSH SAN Logical Disk
§ SSH SAN Physical Disk
§ SSH SAN System Health
§ SSH Script
§ SSH Script Advanced
§ VMware Host Hardware (WBEM)
289
290
Setting Description
User Name Enter the user name for access to the Linux/Solaris/macOS system via
Secure Shell (SSH) and Web-based Enterprise Management (WBEM).
Usually, you use credentials with administrator rights.
Authentication Method Select the authentication method for the login:
§ Password (default): Provide the password for the login.
§ Private key: Provide an RSA private key for authentication.
PRTG can only handle keys in the OpenSSH format that are not
encrypted. You cannot use password-protected keys.
PRTG only supports RSA keys. It does not support DSA keys.
For more information, see section Monitoring via SSH 3017 .
Password This setting is only visible if you select Password (default) above.
Enter a password for access to the Linux/Solaris/macOS system via SSH

and WBEM. Usually, you use credentials with administrator rights.
Private Key This setting is only visible if you select Private key above.
Paste the entire RSA private key, including the BEGIN and END lines.
Make sure that a corresponding public key exists on the target device.

If you do not insert a private key for the first time but if you want to
change the private key, you need to restart the PRTG core server
service 2929 for the private key change to take effect.
WBEM Protocol Select the protocol that you want to use for the connection to the system
via WBEM:
§ HTTP: Use an unsecure connection for WBEM.
§ HTTPS (default): Use a Secure Sockets Layer (SSL)/Transport Layer

Security (TLS) secured connection for WBEM.
This setting is only relevant if you use WBEM sensors.
WBEM Port Select if you want to use one of the default ports for the connection to the
system via WBEM or if you want to set a custom port:
291
Setting Description
§ Default: Use one of the default ports. The default port for unsecure
connections is 5988 and the default port for secure connections is
5989.
§ Custom: Use a custom port.
Custom WBEM Port This setting is only visible if you select Custom above.
Enter a custom WBEM port. Enter an integer.
SSH Port Enter the port for SSH connections. Enter an integer. The default port is
22.
By default, PRTG automatically uses this setting for all SSH
sensors 3237 unless you define a different port number in the sensor
settings.
SSH Rights Elevation Select the rights that you want to use to run the command on the target
system:
§ Run the command as the connecting user (default): Use the rights of
the user who establishes the SSH connection.
§ Run the command as a different user using 'sudo' (with password): Use
the rights of a different user with a password required for sudo to run
commands on the target system, for example, as a root user.
§ Run the command as a different user using 'sudo' (without password):
Use the rights of a different user without a password required for sudo to
run commands on the target system, for example, as a root user.
§ Run the command as a different user using 'su': Use the rights of a
different user with su to run commands on the target system.
Target System User This setting is only visible if you select an option that includes sudo or su
Name above.
Enter a user name to run the specified command on the target system as
a different user than the root user. If you leave this field empty, you run
the command as a root user. Make sure that you set the Linux password
even if you use a public key or a private key for authentication. This is not
necessary if the user is allowed to run the command without a password.
Password This setting is only visible if you select an option that includes sudo or su
with password above.
Enter the password to run the sudo command or the su command.
292
Setting Description
SSH Connection Mode Select the connection mode that you want to use to access data with
SSH sensors 3017 :
§ Default: This is the default connection mode for SSH sensors. It
provides the best performance and security.
§ Compatibility mode (deprecated): Use this only if the default connection
mode does not work on the target system. The compatibility mode is
the connection mode that PRTG used in previous versions and it is
deprecated.
We strongly recommend that you use the default connection mode.
You can also individually select the connection mode for each SSH
sensor in the sensor settings.
Credentials for VMware/XenServer

§ Citrix XenServer Host
§ Citrix XenServer Virtual Machine
§ VMware Datastore (SOAP)
§ VMware Host Hardware Status (SOAP)
§ VMware Host Performance (SOAP)
§ VMware Virtual Machine (SOAP)
293
Credentials for VMw are/XenServer
Setting Description
User Name Enter the user name for access to VMware ESXi, vCenter Server, or Citrix
XenServer. Usually, you use credentials with administrator rights.
Password Enter the password for access to VMware ESXi, vCenter Server, or Citrix
Single sign-on (SSO) passwords for vSphere do not support special
characters. For more information, see the VMware sensors sections.
VMware Protocol Select the protocol for the connection to VMware ESXi, vCenter Server, or
Citrix XenServer:
Security (TLS) secured connection.
§ HTTP: Use an unsecure connection.
Session Handling Select if you want to reuse a session for VMware sensors:
294
Setting Description
§ Reuse a session for multiple scans (default): Select this option if you
want a VMware sensor to reuse a single session for multiple sensor
scans to query data. With this option, the sensor does not need to log
in and out for each sensor scan. We recommend that you use this
option because it reduces network load and log entries on the target
device. This can increase performance.
§ Create a new session for each scan: If you select this option, PRTG
does not reuse a session and a VMware sensor has to log in and out
for each sensor scan. This can decrease performance.
Credentials for SNMP Devices

§ Cisco IP SLA § SNMP Fujitsu System Health § SNMP NetApp Enclosure

v2
§ SNMP APC Hardware § SNMP NetApp I/O
§ SNMP Hardware Status
§ SNMP Buffalo TS System § SNMP NetApp License
Health § SNMP HP LaserJet Hardware
§ SNMP NetApp Logical Unit
§ SNMP Cisco ADSL § SNMP HPE BladeSystem
§ SNMP NetApp Network
Blade
§ SNMP Cisco ASA VPN Interface
Connections § SNMP HPE BladeSystem
§ SNMP NetApp System
Enclosure Health
§ SNMP Cisco ASA VPN Health
Traffic § SNMP HPE ProLiant Logical
§ SNMP Nutanix Cluster Health
Disk
§ SNMP Cisco ASA VPN
§ SNMP Nutanix Hypervisor
Users § SNMP HPE ProLiant Memory
Controller § SNMP Poseidon Environment
§ SNMP Cisco CBQoS
§ SNMP HPE ProLiant Network § SNMP Printer
§ SNMP Cisco System Health
Interface
§ SNMP QNAP Logical Disk
§ SNMP Cisco UCS Blade
§ SNMP HPE ProLiant
Physical Disk § SNMP QNAP Physical Disk
§ SNMP Cisco UCS Chassis
§ SNMP HPE ProLiant System § SNMP QNAP System Health
§ SNMP Cisco UCS Physical
Disk Health
§ SNMP Rittal CMC III
§ SNMP Cisco UCS System § SNMP IBM System X Logical Hardware Status
Health Disk
§ SNMP RMON
§ SNMP CPU Load § SNMP IBM System X
§ SNMP SonicWall System
Physical Disk
§ SNMP Custom
Health
§ SNMP IBM System X
§ SNMP SonicWall VPN Traffic
§ SNMP Custom Advanced Physical Memory
295
§ SNMP Custom String § SNMP IBM System X System § SNMP Synology Logical Disk
Health
§ SNMP Custom String Lookup § SNMP Synology Physical
§ SNMP interSeptor Pro Disk
§ SNMP Custom Table
Environment
§ SNMP Synology System
§ SNMP Dell EqualLogic
§ SNMP Juniper NS System Health
Logical Disk Health
§ SNMP System Uptime
§ SNMP LenovoEMC Physical
Member Health § SNMP Traffic
Disk
§ SNMP Dell EqualLogic § SNMP Trap Receiver
§ SNMP LenovoEMC System
Physical Disk Health § SNMP Windows Service
§ SNMP Dell Hardware
§ SNMP Library
§ SNMP Dell PowerEdge
§ SNMP Linux Disk Free
Physical Disk
§ SNMP Linux Load Average
System Health § SNMP Linux Meminfo
§ SNMP Disk Free § SNMP Linux Physical Disk
§ SNMP Memory
§ SNMP NetApp Disk Free
296
Setting Description
SNMP Version Select the Simple Network Management Protocol (SNMP) version for the
connection to the target SNMP device:
§ SNMP v1: Use SNMP v1 for the connection. SNMP v1 only offers clear-
text data transmission.
SNMP v1 does not support 64-bit counters. This might result in
invalid data when you monitor traffic via SNMP.
§ SNMP v2c (default): Use SNMP v2c for the connection. SNMP v2c also
only offers clear-text data transmission but it supports 64-bit counters.
297
Setting Description
§ SNMP v3: Use SNMP v3 for the connection. SNMP v3 provides secure
authentication and data encryption.
SNMP v3 has performance limitations because of the use of
encryption. The main limiting factor is CPU power. Also keep in
mind that SNMP v3, unlike SNMP v1 and v2c, does not scale with more
CPU power. Because of this limitation, PRTG can only handle a limited
number of requests per second so that you can use only a limited
number of sensors using SNMP v3. If you see an increase in Interval
Delay or Open Requests with the Probe Health sensor, distribute the
load over multiple probes 3203 . SNMP v1 and SNMP v2c do not have this
limitation.
Community String This setting is only visible if you select SNMP v1 or SNMP v2c (default)
above.
Enter the community string of your device. This is like a clear-text

password for simple authentication.
We recommend that you use the default value.
Authentication Method This setting is only visible if you select SNMP v3 above.
Select the authentication method:

§ MD5 (default): Use message-digest algorithm 5 (MD5) for
authentication.
§ SHA: Use Secure Hash Algorithm (SHA) for authentication.
§ SHA-224: Use SHA-224 for authentication.
If you do not want to use authentication but you need SNMP v3, for
example, because your device requires context, you can leave the
Password field empty. In this case, PRTG uses
SNMP_SEC_LEVEL_NOAUTH and it entirely deactivates authentication.
The authentication method that you select must match the
authentication method of your device.
User Name This setting is only visible if you select SNMP v3 above.
Enter the user name for access to the target SNMP device.
The user name that you enter must match the user name of your
device.
298
Setting Description
Password This setting is only visible if you select SNMP v3 above.
Enter the password for access to the target SNMP device.

The password that you enter must match the password of your
device.
Encryption Type This setting is only visible if you select SNMP v3 above.
Select an encryption type:

§ DES (default): Use Data Encryption Standard (DES) as the encryption
algorithm.
§ AES: Use Advanced Encryption Standard (AES) as the encryption
algorithm.
§ AES-192: Use AES-192 as the encryption algorithm.
The encryption type that you select must match the encryption type
of your device.
Encryption Key This setting is only visible if you select SNMP v3 above.
Enter an encryption key. If you provide a key, PRTG encrypts SNMP data
packets with the encryption algorithm that you selected above. Enter a
string or leave the field empty.
The encryption key that you enter must match the encryption key of
your device. If the encryption keys do not match, you do not get an
error message.
Context Name This setting is only visible if you select SNMP v3 above.
Enter a context name only if the configuration of the device requires it.
Context is a collection of management information that is accessible by
an SNMP device. Enter a string.
SNMP Port Enter the port for the connection to the SNMP target device. Enter an
integer. The default port is 161.
Timeout (Sec.) Enter a timeout in seconds for the request. Enter an integer. The
maximum timeout value is 300 seconds (5 minutes).
299
Credentials for Database Management Systems
§ ADO SQL v2
§ Microsoft SQL v2
§ MySQL v2
§ Oracle SQL v2
§ PostgreSQL
Setting Description
Port Select the port that PRTG uses for connections to the monitored
databases:
300
Setting Description
§ Default: PRTG automatically determines the type of the database and

uses the corresponding default port to connect. PRTG uses the
following default ports:
ú Microsoft SQL: 1433
ú MySQL: 3306
ú Oracle SQL: 1521
ú PostgreSQL: 5432
§ Custom port for all database sensors: Select this option if your
database management systems do not use the default ports. Enter a
custom port for database connections below.
Custom Port Enter a custom port for database connections. Enter an integer.
PRTG uses this custom port for all database sensors and for
connections to all your databases.
Authentication Method Select the authentication method for the connection to the Structured
Query Language (SQL) database:
§ Windows authentication with impersonation (default): PRTG uses the
Windows credentials that you define in settings that are higher in the
object hierarchy 136 for the database connection.
The user whose credentials PRTG uses needs to have permission
to log in to the probe system with a database sensor. This is
necessary for the impersonation.
§ SQL server authentication: Use explicit credentials for database
connections. Enter a user name and password below.
User Name This setting is only visible if you select SQL server authentication above.
Enter the user name for the database connection.
Password This setting is only visible if you select SQL server authentication above.
Enter the password for the database connection.
Credentials for AWS

301
§ AWS Alarm v2
§ AWS Cost
§ AWS EBS v2
§ AWS EC2 v2
§ AWS ELB v2
§ AWS RDS v2
For more information about the permissions that are necessary to query the AWS API, see the
Knowledge Base: How do I set permissions for the Amazon Web Services (AWS) API key to use
certain sensors in PRTG?
Credentials for AWS
Setting Description
Access Key Enter the Amazon Web Services (AWS) access key.
Secret Key Enter the AWS secret key.
Credentials for Script Sensors

§ EXE/Script
§ EXE/Script Advanced
§ Python Script Advanced
302
§ SSH Script
Setting Description
Placeholder 1 Enter a description for Placeholder 1, for example information about the
Description purpose or content of the placeholder.
Placeholder 1 Enter a value for the placeholder. PRTG inserts the value for the script
execution if you add %scriptplaceholder1 in the argument list. PRTG
does not display the value in the sensor log or the sensor's settings.
303
Setting Description
Credentials for Cisco Meraki

§ Cisco Meraki License
§ Cisco Meraki Network Health
Setting Description
API Key Enter an API key that the sensor uses for authentication against the
Cisco Meraki Dashboard API.
Meraki Dashboard API Enter the endpoint for the Cisco Meraki Dashboard API. The default
Endpoint api.meraki.com should be valid for most use cases.
See the Cisco Meraki Dashboard API documentation for other
possible choices.
Credentials for Dell EMC

304
§ Dell EMC Unity Enclosure Health v2
§ Dell EMC Unity File System v2
§ Dell EMC Unity Storage Capacity v2
§ Dell EMC Unity Storage LUN v2
§ Dell EMC Unity Storage Pool v2
§ Dell EMC Unity VMware Datastore v2
Setting Description
User Name Enter the user name for access to the Dell EMC system.
Password Enter the password for access to the Dell EMC system.
Port Enter the port for the connection to the Dell EMC system. The default port
for secure connections is 443.
305
Credentials for FortiGate
§ FortiGate System Statistics
§ FortiGate VPN Overview
Setting Description
API Token Enter the API token for access to the FortiGate system.
Port Enter the port for the connection to the FortiGate system. The default port
Credentials for HPE 3PAR

§ HPE 3PAR Common Provisioning Group
§ HPE 3PAR Drive Enclosure
§ HPE 3PAR Virtual Volume
306
Setting Description
User Name Enter the user name for access to the HPE 3PAR system.
307
Setting Description
Password Enter the password for access to the HPE 3PAR system.
Protocol Select the protocol that you want to use for the connection to the HPE
3PAR system:
WSAPI Port Enter the Web Services API (WSAPI) port for the connection to the HPE
3PAR system. The default port for secure connections is 8080 and the
default port for unsecure connections is 8008.
For more information, see the Knowledge Base: Where can I find the
Web Services API (WSAPI) port for the connection to the HPE 3PAR
system?
SSH Port Enter the SSH port for the connection to the HPE 3PAR system. The
default port for secure connections is 22.
Credentials for HTTP

The settings you define in this section apply to the following sensor:
§ HTTP v2
308
Setting Description
Authentication Method Select the authentication method for access to the server:
§ None (default): Use no authentication.
§ Basic authentication: Use basic authentication.
§ Bearer authentication: Use an OAuth2 bearer token.
User Name This setting is only visible if you select Basic authentication above.
Enter the user name for access to the server.
Password This setting is only visible if you select Basic authentication above.
Enter the password for access to the server.
Bearer Token This setting is only visible if you select Bearer authentication above.
Enter a bearer token for access to the server.
309
Setting Description
Placeholder 1 Enter a value for the placeholder. PRTG inserts the value for the HTTP
request if you add %httpplaceholder1 in the URL, POST Body, and
Custom Headers fields of the HTTP v2 sensor. PRTG does not display the
value in the sensor log or the sensor's settings.
Credentials for Microsoft Azure

310
§ Microsoft Azure SQL Database
§ Microsoft Azure Storage Account
§ Microsoft Azure Subscription Cost
§ Microsoft Azure Virtual Machine
The sensors use the credentials to authenticate with Microsoft Entra ID.
For more information about the credentials and permissions that are necessary use the Microsoft
Azure sensors, see the Knowledge Base: How do I obtain credentials and create custom roles for
the Microsoft Azure sensors?
Setting Description
Tenant ID Enter the Microsoft Entra tenant ID.

A tenant ID must be a 32-digit sequence in hexadecimal notation.
311
Setting Description
Client ID Enter the Microsoft Entra client ID.
Client Secret Enter the Microsoft Entra client secret.
Subscription ID Enter the Microsoft Entra subscription ID.
Credentials for MQTT

§ MQTT Round Trip
§ MQTT Statistics
§ MQTT Subscribe Custom
312
Setting Description
Authentication Method Select if you want to connect without credentials or define credentials for
access to the MQTT broker:
§ None (default): Connect without credentials.
§ User name and password: Define credentials for the connection.
User Name This setting is only visible if you select User name and password above.
Enter the user name for access to the Message Queue Telemetry
Transport (MQTT) broker.
313
Setting Description
Password This setting is only visible if you select User name and password above.
Enter the password for access to the MQTT broker.
Port Enter the port for the connection to the MQTT broker. The default port for
secure connections is 8883 and the default port for unsecure connections
is 1883.
Transport-Level Security Select if you want to use a Secure Sockets Layer (SSL)/Transport Layer
Security (TLS) secured connection:
§ Do not use transport-level security (default): Establish the connection
without connection security.
§ Use transport-level security: Establish the connection with the
strongest SSL/TLS method that the target device provides.
Server Authentication This setting is only visible if you select Use transport-level security above.
Select if you want to use a certificate for server authentication:

§ Disable (default): Do not use a certificate for server authentication.
§ Enable: Use a certificate for server authentication.
CA Certificate This setting is only visible if you select Enable above.
Paste the certificate authority (CA) certificate for the verification of the
MQTT broker.
The certificate must be in Privacy-Enhanced Mail (PEM) format.
Client Authentication This setting is only visible if you select Use transport-level security above.
Select if you want to use a certificate for client authentication:

§ Disable (default): Do not use a certificate for client authentication.
§ Enable: Use a certificate for client authentication.
Client Certificate This setting is only visible if you select Enable above.
Paste the certificate that you created for authenticating the sensor
against the MQTT broker.
The certificate must be in PEM format.
Client Key This setting is only visible if you select Enable above.
Enter the client key for access to the MQTT broker.
314
Setting Description
The client key must be in PEM format and it must be encrypted

using the Client Key Password.
Client Key Password This setting is only visible if you select Enable above.
Enter the password for the client key.
Credentials for NetApp

§ NetApp Aggregate v2
§ NetApp I/O v2
§ NetApp LIF v2
§ NetApp LUN v2
§ NetApp NIC v2
§ NetApp Physical Disk v2
§ NetApp SnapMirror v2
§ NetApp System Health v2
§ NetApp Volume v2
The sensors use the credentials for access to the ONTAP System Manager.
315
Setting Description
User Name Enter a user name for access to the ONTAP System Manager.
Password Enter the password for access to the ONTAP System Manager.
Port Enter the port for the connection to the ONTAP System Manager. The
316
Setting Description
Protocol Select the protocol that you want to use for the connection to the ONTAP
System Manager:
§ HTTPS (default): Use HTTPS for the connection.
§ HTTP: Use HTTP for the connection.
Credentials for OPC UA

§ Beckhoff IPC System Health
§ OPC UA Certificate
§ OPC UA Custom
§ OPC UA Server Status
317
Setting Description
Port Enter the port for the connection to the OPC Unified Architecture (OPC
UA) server. The default port for secure connections is 4840.
Server Path Enter the path of the OPC UA server endpoint if you run more than one
server under the same IP address or DNS name.
Security Mode Select if you want to use encryption:

§ None (default): Do not use encryption.
§ Sign: Sign messages between the sensor and the OPC UA server.
318
Setting Description
§ Sign & Encrypt: Sign and encrypt messages between the sensor and
the OPC UA server.
Security Policy This setting is only visible if you select Sign or Sign & Encrypt above.
Select if you want to use a security policy and define which policy you
want to use:
§ None (default): Do not use a security policy.
§ Basic256Sha256: Use the Basic256Sha256 security policy.
§ Basic256: Use the Basic256 security policy.
Client Certificate This setting is only visible if you select Sign or Sign & Encrypt above.
Enter the certificate that you created for authenticating the sensor against
the OPC UA server.
The certificate must meet the following requirements:
§ The key size must be 2048-bit or 4096-bit.
§ The secure hash algorithm must be SHA256.
§ DataEncipherment must be part of the KeyUsage certificate extension.
§ A uniform resource indicator (URI) must be set in subjectAltName.
§ The certificate must be in Privacy-Enhanced Mail (PEM) format.
Client Key This setting is only visible if you select Sign or Sign & Encrypt above.
Enter the client key for access to the OPC UA server.

Client Key Password This setting is only visible if you select Sign or Sign & Encrypt above.
access to the OPC UA server:
§ Anonymous (default): Connect without credentials.
319
Setting Description
Most OPC UA servers do not support User name and password

authentication without a client certificate. To use User name and
password authentication, select Sign or Sign & Encrypt under Security
Mode and Basic256Sha256 or Basic256 under Security Policy and enter
the Client Certificate, Client Key, and Client Key Password that you want
to use.
If you select None (default) under Security Mode and use User name
and password authentication, PRTG sends the unencrypted
password to the OPC UA server.
Enter the user name for access to the OPC UA server.
Enter the password for access to the OPC UA server.
Credentials for Soffico Orchestra

§ Soffico Orchestra Channel Health
§ Soffico Orchestra Scenario
320
Setting Description
access to the Orchestra platform:
Enter the user name for access to the Orchestra platform.
321
Setting Description
Enter the password for access to the Orchestra platform.
Port Enter the port for the connection to the Orchestra platform. The default
port for secure connections is 8443 and the default port for unsecure
connections is 8019.
Protocol Select the protocol that you want to use for the connection to the
Orchestra platform:
Credentials for Redfish

§ Redfish Power Supply
§ Redfish System Health
§ Redfish Virtual Disk
322
Setting Description
User Name Enter the user name for access to the Redfish system.
Password Enter the password for access to the Redfish system.
Protocol Select the protocol that you want to use for the connection to the Redfish
system:
Port Enter the port for the connection to the Redfish system. The default port
323
Credentials for REST API
§ REST Custom v2
Setting Description
Authentication Method Select the authentication method for access to the Representational
State Transfer (REST) application programming interface (API):
Enter the user name for access to the REST API.
Enter the password for access to the REST API.
Enter a bearer token for access to the REST API.
324
Setting Description
Placeholder 1 Enter a value for the placeholder. PRTG inserts the value for the REST
API request if you add %restplaceholder1 in the Request URL, POST
Body, and Custom Headers fields of the REST Custom v2 sensor. PRTG
Credentials for Veeam

§ Veeam Backup Job Status
§ Veeam Backup Job Status Advanced
325
Setting Description
User Name Enter the user name for access to the Veeam Backup Enterprise
Manager.
Password Enter the password for access to the Veeam Backup Enterprise
Manager.
Port Enter the port for the connection to the Veeam Backup Enterprise
Manager. The default port for secure connections is 9398.
Access Rights
326
Access Rights
Setting Description
User Group Access Select the user groups 2922 that have access to the object. You see a
table with user groups and group access rights. The table contains all
user groups in your setup. For each user group, you can choose from the
following group access rights:
§ Inherited: Inherit the access rights settings of the parent object.
§ No access: Users in this user group cannot see or edit the object. The
object neither shows up in lists nor in the device tree.
There is one exception: If a user in this user group has access to a
child object, the parent object is visible in the device tree but users
in this user group cannot access it.
§ Read access: Users in this group can see the object and view its
monitoring results. They cannot edit any settings.
§ Write access: Users in this group can see the object, view its
monitoring results, and edit its settings. They cannot edit its access
rights settings.
§ Full access: Users in this group can see the object, view its monitoring
results, edit its settings, and edit its access rights settings.
To automatically set all child objects to inherit this object's access rights,
select the Revert access rights of child objects to "inherited" option.
For more information on access rights, see section Access Rights
Management 149 .
327
Click OK to save your settings. If you close the dialog without saving, all changes to the settings are
lost.
More
KNOWLEDGE BASE
Where can I find the Web Services API (WSAPI) port for the connection to the HPE 3PAR system?
How do I set permissions for the Amazon Web Services (AWS) API key to use certain sensors in
PRTG?
How do I obtain credentials and set permissions for the Microsoft 365 Service Status sensors?
How do I obtain credentials and create custom roles for the Microsoft Azure sensors?
328
7.2.2 Add a Group
There are several ways to manually add a group:
§ Select Devices | Add Group from the main menu bar 254 . A dialog appears that guides you through the
process of adding a new group.
§ Hover over and select Add Group from the menu.

§ Select Add Group from the context menu 232 of the probe or group to which you want to add the new
group. This skips step 1 and leads you directly to step 2 332 .
In this section:
§ Add a Group 330
§ Step 2: Define Group Settings 332
329
Add a Group
The Add a Group dialog appears when you add a new group to a parent group. It only shows the settings
that are required to create the group. Therefore, you do not see all settings in this dialog.
You can change all settings on the Settings tab of the group later. For more information, see section
Group Settings 541 .
330
Add Group Assistant Step 1
Select the probe or group that you want to add the new group to. Click OK.
331
Step 2: Define Group Settings
Add Group Assistant Step 2
332
Setting Description
333
Auto-Discovery
Setting Description
sensors available.
list.

minutes.
Auto-Discovery.
334
Setting Description
Auto-Discovery.
templates above.

§ ADSL
§ Cisco ASA VPN
§ Dell EqualLogic
§ Dell MDi Disk
§ DNS Server
§ FTP Server
§ HTTP Web Server
§ NAS LenovoEMC
335
Setting Description
§ NAS QNAP
§ NAS Synology
§ NetApp
§ NTP Server
§ Printer (HP)
§ RDP Server
§ Server (Dell)
§ Server (Fujitsu)
§ Server (IBM)
§ SonicWall
§ UPS Health (APC)
§ Web Server
§ XenServer Hosts
336
Inherited Settings


Errors Length
(PowerShell) 2008
(PowerShell) 2012
§ Windows Process
§ Exchange Database DAG § WMI Microsoft SQL Server
(PowerShell) § Windows SMTP Service 2014
§ Exchange Mail Queue
Received § WMI Microsoft SQL Server
(PowerShell) § Windows SMTP Service Sent 2016
§ Exchange Mailbox § Windows System Uptime § WMI Microsoft SQL Server
(PowerShell) 2017
§ Exchange Public Folder (PowerShell) § WMI Microsoft SQL Server
(PowerShell) 2019
§ WMI Battery
§ WMI Custom
§ WMI Disk Health
Volume Disk Free § WMI Event Log
§ Hyper-V Host Server § WMI Exchange Server
§ WMI Storage Pool
§ Hyper-V Virtual Machine § WMI Exchange Transport
Queue § WMI Terminal Services
Adapter § WMI File
§ Hyper-V Virtual Storage § WMI Free Disk Space (Multi (Windows XP/Vista/2003)
Device Disk)
§ WMI UTC Time
§ PerfCounter Custom § WMI HDD Health
337
§ PerfCounter IIS Application § WMI Logical Disk I/O § WMI Vital System Data v2
Pool
§ WMI Volume
§ Share Disk Free
§ WSUS Statistics
§ Windows CPU Load
Setting Description
Windows sensors.
338
Setting Description

§ SSH Disk Free
§ SSH INodes Free
§ SSH Load Average
§ SSH Meminfo
§ SSH Remote Ping
§ SSH Script
339
340
Setting Description


via WBEM:

341
Setting Description
5989.
22.
settings.
system:
Name above.
342
Setting Description
SSH sensors 3017 :
deprecated.

343
Setting Description
Citrix XenServer:
344
Setting Description


v2
Blade
Enclosure Health
Disk
§ SNMP Cisco CBQoS
Interface
Disk Health
Health Disk
§ SNMP RMON
Physical Disk
§ SNMP Custom
Health
345
Health
Environment
Logical Disk Health
Disk
§ SNMP Library
Physical Disk
§ SNMP Memory
346
Setting Description
347
Setting Description
limitation.
above.


authentication.
device.
348
Setting Description

device.

algorithm.
algorithm.
of your device.
error message.
349
§ ADO SQL v2
§ Microsoft SQL v2
§ MySQL v2
§ Oracle SQL v2
§ PostgreSQL
Setting Description
databases:
350
Setting Description

ú MySQL: 3306
ú Oracle SQL: 1521
ú PostgreSQL: 5432
Credentials for AWS

351
§ AWS Alarm v2
§ AWS Cost
§ AWS EBS v2
§ AWS EC2 v2
§ AWS ELB v2
§ AWS RDS v2
Credentials for AWS
Setting Description

§ EXE/Script
352
§ SSH Script
Setting Description
353
Setting Description

Setting Description
possible choices.

354
Setting Description
355
Setting Description

356
Setting Description
357
Setting Description
3PAR system:
system?

§ HTTP v2
358
Setting Description
359
Setting Description

360
Setting Description

361
Setting Description

§ MQTT Round Trip
§ MQTT Statistics
362
Setting Description
363
Setting Description
is 1883.

MQTT broker.

364
Setting Description


§ NetApp I/O v2
§ NetApp LIF v2
§ NetApp LUN v2
§ NetApp NIC v2
§ NetApp Volume v2
365
Setting Description
366
Setting Description
System Manager:

§ OPC UA Custom
367
Setting Description

368
Setting Description
the OPC UA server.
want to use:
the OPC UA server.

369
Setting Description

to use.

370
Setting Description
371
Setting Description
Orchestra platform:

372
Setting Description
system:
373
§ REST Custom v2
Setting Description
374
Setting Description

375
Setting Description
Manager.
Manager.
Access Rights
376
Access Rights
Setting Description
rights settings.
Management 149 .
377
lost.
More
KNOWLEDGE BASE
PRTG?
378
7.2.3 Add a Device
There are several ways to manually add a device:
§ Select Devices | Add Device from the main menu bar 254 . A dialog appears that guides you through the
process of adding a new device.
§ Hover over and select Add Device from the menu.

§ Select Add Device from the context menu 236 of the group to which you want to add the new device.
This skips step 1 and leads you directly to step 2 382 .
In this section:
§ Add a Device 380
§ Step 2: Define Device Settings 382
§ Basic Device Settings 383
§ Additional Device Information 384
379
Add a Device
The Add a Device dialog appears when you add a new device to a group. It only shows the settings that
are required to create the device. Therefore, you do not see all settings in this dialog.
You can change all settings on the Settings tab of the device later. For more information, see
section Device Settings 612 .
380
Add Device Assistant Step 1
Select the group that you want to add the new device to. Click OK.
381
Step 2: Define Device Settings
Add Device Assistant Step 2
382
Basic Device Settings
Setting Description
Device Name Enter a name to identify the device. By default, PRTG shows this name in
IP Version Select the IP protocol that PRTG uses to connect to the device:
§ IPv4: Use IP version 4 for all requests to the device.
The setting is valid for all sensors that you create on the device.
IPv4 Address/DNS Name This setting is only visible if you select IPv4 above.
383
Setting Description
Enter the IP address or Domain Name System (DNS) name for the
device. Most sensors that you create on this device inherit this setting
and try to connect to this address for monitoring.
Some sensors have their own setting for the IP address/DNS name
to which they connect.
Additional Device Information
384
Setting Description
Device Icon Select a device icon. PRTG shows it in the device tree.
Setting Description
sensors available.
list.

385
Setting Description
minutes.
Auto-Discovery.
Auto-Discovery.
templates above.

§ ADSL
§ Cisco ASA VPN
§ Dell EqualLogic
§ Dell MDi Disk
§ DNS Server
§ FTP Server
§ HTTP Web Server
386
Setting Description
§ NAS LenovoEMC
§ NAS QNAP
§ NAS Synology
§ NetApp
§ NTP Server
§ Printer (HP)
§ RDP Server
§ Server (Dell)
§ Server (Fujitsu)
§ Server (IBM)
§ SonicWall
§ UPS Health (APC)
§ Web Server
387
Setting Description
§ XenServer Hosts
Inherited Settings


Errors Length
(PowerShell) 2008
(PowerShell) 2012
§ Windows Process
(PowerShell) § Windows SMTP Service 2014
Received § WMI Microsoft SQL Server
(PowerShell) § Windows SMTP Service Sent 2016
§ Exchange Mailbox § Windows System Uptime § WMI Microsoft SQL Server
(PowerShell) 2017
§ Exchange Public Folder (PowerShell) § WMI Microsoft SQL Server
(PowerShell) 2019
§ WMI Battery
388
§ File Content § WMI Custom § WMI Security Center
§ Folder § WMI Custom String § WMI Service
§ Hyper-V Cluster Shared § WMI Disk Health § WMI Share

Volume Disk Free
§ WMI Event Log § WMI SharePoint Process
§ WMI Exchange Server § WMI Storage Pool
§ WMI Exchange Transport § WMI Terminal Services
§ Hyper-V Virtual Network Queue (Windows 2008+)
Adapter
§ WMI File § WMI Terminal Services
§ Hyper-V Virtual Storage (Windows XP/Vista/2003)
§ WMI Free Disk Space (Multi
Device
Disk) § WMI UTC Time
§ PerfCounter Custom
§ WMI HDD Health § WMI Vital System Data v2
§ WMI Logical Disk I/O § WMI Volume
Pool
§ WSUS Statistics
§ Share Disk Free
§ Windows CPU Load
389
Setting Description
Windows sensors.
390
§ SSH Disk Free
§ SSH INodes Free
§ SSH Load Average
§ SSH Meminfo
§ SSH Remote Ping
§ SSH Script
391
392
Setting Description


via WBEM:

393
Setting Description
5989.
22.
settings.
system:
Name above.
394
Setting Description
SSH sensors 3017 :
deprecated.

395
Setting Description
Citrix XenServer:
396
Setting Description


v2
Blade
Enclosure Health
Disk
§ SNMP Cisco CBQoS
Interface
Disk Health
Health Disk
§ SNMP RMON
Physical Disk
§ SNMP Custom
Health
397
Health
Environment
Logical Disk Health
Disk
§ SNMP Library
Physical Disk
§ SNMP Memory
398
Setting Description
399
Setting Description
limitation.
above.


authentication.
device.
400
Setting Description

device.

algorithm.
algorithm.
of your device.
error message.
401
§ ADO SQL v2
§ Microsoft SQL v2
§ MySQL v2
§ Oracle SQL v2
§ PostgreSQL
Setting Description
databases:
402
Setting Description

ú MySQL: 3306
ú Oracle SQL: 1521
ú PostgreSQL: 5432
Credentials for AWS

403
§ AWS Alarm v2
§ AWS Cost
§ AWS EBS v2
§ AWS EC2 v2
§ AWS ELB v2
§ AWS RDS v2
Credentials for AWS
Setting Description

§ EXE/Script
404
§ SSH Script
Setting Description
405
Setting Description

Setting Description
possible choices.

406
Setting Description
407
Setting Description

408
Setting Description
409
Setting Description
3PAR system:
system?

§ HTTP v2
410
Setting Description
411
Setting Description

412
Setting Description

413
Setting Description

§ MQTT Round Trip
§ MQTT Statistics
414
Setting Description
is 1883.

MQTT broker.

415
Setting Description


§ NetApp I/O v2
§ NetApp LIF v2
§ NetApp LUN v2
§ NetApp NIC v2
§ NetApp Volume v2
416
Setting Description
417
Setting Description
System Manager:

§ OPC UA Custom
418
Setting Description

419
Setting Description
the OPC UA server.
want to use:
the OPC UA server.

420
Setting Description

to use.

421
Setting Description
422
Setting Description
Orchestra platform:

423
Setting Description
system:
424
§ REST Custom v2
Setting Description
425
Setting Description

426
Setting Description
Manager.
Manager.
Access Rights
427
Access Rights
Setting Description
rights settings.
Management 149 .
428
lost.
More
KNOWLEDGE BASE
PRTG?
429
7.2.4 Add a Sensor
There are several ways to manually add a sensor:
§ Select Sensors | Add Sensor from the main menu bar 257 . A dialog appears that guides you through
the process of adding a new sensor.
§ Hover over and select Add Sensor from the menu.

§ Select Add Sensor from the context menu 240 of a device to which you want to add the new sensor.
This skips step 1 and leads you directly to step 2 432 .
§ Click the Add Sensor button at the end of a device's sensor list on the device tree screen or above the
geographical map on the right.
Preparation: Select a Device
Add Sensor Assistant
1. Select Add sensor to a device.

2. Select the device you want to add the new sensor to.
3. Click Continue.
430
The Add Sensor dialog appears.
Step 1: Choose Sensor
Add Sensor Dialog
In the Add Sensor dialog, the following actions are available:
§ Choose appropriate criteria to filter the sensors.

ú Select the type of parameter that you want to monitor via Monitor What?
ú Specify the type of target system that you want to monitor and see what sensors are available for
this type of hardware via Target System Type?
ú Select the technology that you want to use for monitoring (for example SNMP or WMI) via
Technology Used?
§ Enter (parts of) the name into the search box.
§ Go through the list of the most used sensor types.

PRTG suggests sensors for the selected device. This recommendation is automatically calculated
based on the current user's sensor usage. It shows the ten most commonly used sensors if there
are already enough sensors for the recommendation to use.
§ Go through the list of all matching sensor types.

If you cannot find a suitable sensor, search for custom sensors in our PRTG Sensor Hub. To do so,
click Looking for more sensor types? above the search box or below the list of sensors.
For more information, see section Available Sensor Types 3284 , section PRTG Sensor Hub.
§ Click the sensor box to select the sensor.
431
If you are unsure which sensor provides the information that you need, we recommend that you use
the filter categories to reduce the amount of matching sensor types.
Also consider whether a sensor’s performance impact 2962 is high or low. To do so, check the bar in
the lower-left corner of the sensor box. For more information, see the Knowledge Base: How can I
speed up PRTG—especially for large installations? (especially section 4 - Sensor Type and Monitoring).
Types 3237 .
Sensor w ith Very Low Performance Impact and w ith High Performance Impact
For more information about a sensor, click to see the section of the respective sensor.
Step 2: Define Sensor Settings

The Add Sensor 430 dialog appears when you manually add a new sensor to a device. It only shows the
settings that are required to create the sensor. You can change nearly all settings on the sensor's
Settings tab after creation.
Enable check boxes in front of the respective lines to select the items. Use the check box in the
table header to select all items or to cancel the selection. In large tables, use the search function in
the upper-right corner.
Then, the sensor settings dialog opens where you can define the sensor settings and create the sensor.
The settings that you select during sensor creation are valid for all sensors that you create when you
finish the dialog.
More
KNOWLEDGE BASE
How can I change the number of entries in most used sensor types?

432
PAESSLER WEBSITE
You can find useful scripts for sensors in the PRTG Sensor Hub
§ https://www.paessler.com/sensor-hub
433
7.3 Manage Device Tree
In the device tree, click the Management tab to enter a different view of your devices and sensors. While
in this view, you can move monitoring objects via drag-and-drop. You can also select objects to view and
edit their settings. Any changes that you make in this view immediately take effect. To arrange objects in
the tree, you have the following options.
Move or Clone a Sensor

You can change the position of a sensor on the same device or you can clone a sensor to a different
device:
§ On the same device, drag any sensor and drop it where you want it. The sensor moves to this position
and the other sensors line up underneath it.
§ Drag any sensor from a device and drop it on a different device to clone a sensor. This creates the
same sensor with the same settings on the new device. The original sensor does not change.
Cloned sensors initially show the Paused status 230 to give you the chance to change any
settings before monitoring starts. Check the settings and resume 230 monitoring.
You cannot clone fixed objects such as the root group, a probe device, or PRTG system-internal
sensors.
To clone entire groups or devices, use the clone object 2725 feature in the object's context menu 232 .
Move a Group or Device

You can change the position of a group or a device via drag-and-drop:
§ On the same probe or group, drag any group or device and move it up or down the device tree. A small
red arrow appears that shows the future position. When you drop the group or device, it moves to this
position and the other probes, groups, and devices line up underneath it.
§ Drag any group or device from one probe or group and drop it on a different probe or group. A small red
arrow appears that shows the future position. When you drop the group or device, it moves to the new
probe or group and the other groups and devices line up underneath it. This way, you can change the
probe that a group or device is part of or you can add groups or devices to other groups.
You cannot move the local probe, the hosted probe, or remote probes.
Multi-Edit Object Settings

You can use multi-edit for object settings:
§ Hold down the Ctrl key and select multiple objects of the same type, for example, multiple groups,
devices, or sensors.
§ In the dialog that appears, select the properties that you want to edit, change the respective settings,
and click Save. The changes are applied to all selected objects.
The dialog is the same as described in section Multi-Edit 2731 .
Related Topics
For other ways to arrange objects, see
434
§ Move Objects 2723
§ Create Device Template 2735
§ Clone Object 2725
435
7.4 Root Group Settings
The root group is the highest instance in the object hierarchy and it is the parent to most other objects.
Therefore, most objects inherit settings from the root group. So, before you create your own sensors, it is
a good idea to review the root group's settings to make sure that they suit your needs.
If necessary, you can override every setting for every single child object. To do so, disable the
respective inherit from option of an object.
Root Group Settings

The following settings are available on the Settings tab. All of the settings that you define here can be
inherited to all other objects in your setup.
In this section:
§ Location 438
§ Credentials for Microsoft 365 454
§ Windows Compatibility Options 457
§ SNMP Compatibility Options 459
§ Proxy Settings 464
§ Scanning Interval 466
§ Schedules, Dependencies, and Maintenance Window 468
§ Channel Unit Configuration 470
§ Advanced Network Analysis 471
436
Setting Description
Group Name Enter a name to identify the group. By default, PRTG displays it in the
device tree 168 .
Monitoring Status Select the monitoring status of the group:

§ Started (default): Monitor the group.
§ Paused: Pause monitoring for the group. All sensors on all devices in
the group are in the Paused status 230 until you change this setting.
437
Location
Location
Setting Description
Location (for Geo Maps) If you want to use Geo Maps 2741 , enter a location in the first line.
Geographical maps then display objects like devices or groups with a
status icon using a color code similar to the sensor status icons 184
(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, as PRTG automatically
parses latitude and longitude, for example, enter 49.452778 11.077778, or
enter 49.452778 any 11.077778 text.
A minus sign (-) in the first line hides an object from a geographical map.
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 the coordinates in the second line.
This geographical marker then shows the object with the label in the
geographical map.
The preview map always has a road map layout regardless of the
map layout you set in User Interface 2869 .


Errors Length
§ Windows Pagefile
438
§ Exchange Backup § Windows Physical Disk I/O § WMI Microsoft SQL Server
(PowerShell) 2008
§ Windows Process
(PowerShell) 2012
§ Windows SMTP Service
(PowerShell) Received 2014
§ Windows SMTP Service Sent
§ Exchange Mail Queue § WMI Microsoft SQL Server
(PowerShell) § Windows System Uptime 2016
§ Exchange Mailbox § Windows Updates Status § WMI Microsoft SQL Server
(PowerShell) (PowerShell) 2017
§ Exchange Public Folder § WMI Battery § WMI Microsoft SQL Server
(PowerShell) 2019
§ WMI Custom
§ WMI Disk Health
§ WMI Event Log
Volume Disk Free § WMI Exchange Server
§ Hyper-V Host Server § WMI Exchange Transport
Queue § WMI Storage Pool
§ WMI File § WMI Terminal Services
Adapter § WMI Free Disk Space (Multi
Disk) § WMI Terminal Services
§ Hyper-V Virtual Storage (Windows XP/Vista/2003)
Device § WMI HDD Health
§ WMI UTC Time
§ PerfCounter Custom § WMI Logical Disk I/O
§ WMI Vital System Data v2
§ WMI Volume
Pool
§ WSUS Statistics
§ Share Disk Free
§ Windows CPU Load
439
Setting Description
Windows sensors.

§ SSH Disk Free
440
§ SSH INodes Free
§ SSH Load Average
§ SSH Meminfo
§ SSH Remote Ping
§ SSH Script
441
442
Setting Description
§ Password: Provide the password for the login.
Password This setting is only visible if you select Password above.


via WBEM:

443
Setting Description
5989.
22.
settings.
system:
Use the rights of a different user without a password required for sudo
to run commands on the target system, for example, as a root user.
Name above.
444
Setting Description
SSH sensors 3017 :
deprecated.

445
Setting Description
Citrix XenServer:
446
Setting Description


v2
Blade
Enclosure Health
Disk
§ SNMP Cisco CBQoS
Interface
Disk Health
Health Disk
§ SNMP RMON
Physical Disk
§ SNMP Custom
Health
§ SNMP Synology Logical Disk
§ SNMP Custom String
447
§ SNMP Custom String Lookup § SNMP IBM System X System § SNMP Synology Physical
Health Disk
§ SNMP interSeptor Pro § SNMP Synology System
Environment Health
Logical Disk
§ SNMP Juniper NS System § SNMP System Uptime
Health
Disk
Physical Disk
§ SNMP Windows Service
Health
§ SNMP Library
Physical Disk
System Health § SNMP Linux Load Average
§ SNMP Disk Free § SNMP Linux Meminfo
§ SNMP Linux Physical Disk
§ SNMP Memory
448
Setting Description
449
Setting Description
limitation.
above.


authentication.
device.
450
Setting Description

device.

algorithm.
algorithm.
of your device.
error message.
451
§ ADO SQL v2
§ Microsoft SQL v2
§ MySQL v2
§ Oracle SQL v2
§ PostgreSQL
Setting Description
databases:
ú MySQL: 3306
ú Oracle SQL: 1521
452
Setting Description
ú PostgreSQL: 5432
Credentials for AWS

§ AWS Alarm v2
§ AWS Cost
§ AWS EBS v2
§ AWS EC2 v2
§ AWS ELB v2
§ AWS RDS v2
453
Credentials for AWS
Setting Description
Credentials for Microsoft 365

§ Microsoft 365 Mailbox
§ Microsoft 365 Service Status
§ Microsoft 365 Service Status Advanced
For more information about the credentials and the permissions that are necessary to use the
Microsoft 365 Service Status sensor and the Microsoft 365 Service Status Advanced sensor, see
the Knowledge Base: How do I obtain credentials and set permissions for the Microsoft 365 Service
Status sensors?
Microsoft 365 Mailbox sensor, see the Knowledge Base: How do I obtain credentials and set
permissions for the Microsoft 365 Mailbox sensor?
454
Setting Description
OpenID Connect Select if you want to manually enter the authorization endpoint URL and
Configuration token endpoint URL that PRTG uses to access Microsoft Graph:
§ Automatic (default): PRTG automatically determines the authorization
endpoint URL and the token endpoint URL.
§ Manual: Manually enter the authorization endpoint URL and the token
endpoint URL.
Authorization Endpoint Enter the authorization endpoint URL including the server.
Authorization endpoint URL example:
455
Setting Description
https://login.microsoftonline.com/<tenant-
ID>/oauth2/v2.0/authorize
Make sure to replace <tenant-ID> with the directory (tenant) ID from

Microsoft Entra ID.
Token Endpoint Enter the token endpoint URL including the server.
Token endpoint URL example:
ID>/oauth2/v2.0/token

Microsoft Entra ID.

§ EXE/Script
§ SSH Script
Setting Description
456
Setting Description
Windows Compatibility Options

If you experience problems when you monitor via Windows sensors, use the following compatibility
options for troubleshooting.
457
Window s Compatibility Options
Setting Description
Preferred Data Source This setting only applies to hybrid sensors that use both performance
counters and Windows Management Instrumentation (WMI).
Define the method that Windows sensors use to query data:
§ Performance counters and WMI as fallback: Try to query data via
performance counters. If this is not possible, establish a connection via
WMI.
§ Performance counters only: Query data via performance counters only.

If this is not possible, the sensor returns no data.
§ WMI only (default): Query data via WMI only. If this is not possible, the
sensor returns no data.
Timeout Method Select the time that the sensor waits for the return of the WMI query
before the sensor cancels the query and shows an error message:
§ Use 1.5× scanning interval (default): Multiply the scanning interval of
the sensor by 1.5 and use the resulting value.
§ Set manually: Manually enter a timeout value.

If you experience ongoing timeout errors, try increasing the
timeout value.
Timeout (Sec.) This setting is only visible if you select Set manually above.
458
Setting Description
Enter the time the sensor waits for the return of its WMI query before it
cancels it and shows an error message. Enter an integer. The maximum
timeout value is 900 seconds (15 minutes).
SNMP Compatibility Options

If you experience problems when you monitor via Simple Network Management Protocol (SNMP)
sensors, use the following compatibility options for troubleshooting.
459
460
Setting Description
SNMP Delay (ms) Enter the time in milliseconds (ms) that PRTG waits between two SNMP
requests. You can define a delay between 0 and 100. Enter an integer.
If you experience SNMP connection failures, try increasing the
delay.
Failed Requests Select if an SNMP sensor tries again after a request fails:
§ Retry (default): Try again if an SNMP request fails. This can prevent
false error messages because of temporary timeout failures.
§ Do not retry: Do not retry if an SNMP request fails. If you select this
option, an SNMP sensor shows a Down status earlier.
Overflow Values Select how PRTG handles overflow values. Some devices do not correctly
handle internal buffer overflows. This can cause false peaks. PRTG can
handle overflow values in two ways:
§ Ignore (default): Ignore overflow values and do not include them in the
monitoring data. We recommend that you use this option.
§ Handle overflow values as valid results: Regard all overflow values as
regular data and include them in the monitoring data.
If you experience problems because of strange peaks in your data
graphs, change this option. Peaks might indicate that the target
device resets counters without an overflow. PRTG interprets such
behavior as overflow that results in data peaks. Select the option Ignore
(default) in this case. For more information, see the Knowledge Base:
What is the Overflow Values setting in the SNMP Compatibility Options?
Zero Values Select how PRTG handles zero values. Some devices send incorrect
zero values. This can cause false peaks. PRTG can handle zero values in
two ways:
§ Ignore (default): Ignore zero values and do not include them in the
If you experience problems, try changing this option.
§ Handle zero values as valid results for delta sensors: Regard all zero
values as regular data and include them in the monitoring data.
32-bit/64-bit Counters Select the type of traffic counters that PRTG searches for on a device:
§ Use 64-bit counters if available (default): The interface scan uses 64-bit
traffic counters, if available. This can avoid buffer overflows in the
devices.
461
Setting Description
§ Use 32-bit counters only: The interface scan always uses 32-bit traffic
counters, even if 64-bit counters are available. This can make
monitoring more reliable for some devices.
Request Mode Select the request method that PRTG uses for SNMP sensors:
§ Use multi get (default): Bundle multiple SNMP requests into one
request. We recommend that you use this option.
§ Use single get: Use one request for each SNMP value. This can
increase compatibility with older devices.
PRTG uses paging for SNMP requests. This means that if a sensor
must query more than 20 object identifiers (OID), it automatically
polls the OIDs in packages of 20 OIDs each.
Walk Mode Select the kind of SNMP walk that PRTG uses for SNMP sensors:
§ Use GETBULK requests (default): Request the next x OIDs in one
SNMP request. The default value is 10. It is dynamic based on the
response size.
This option only works with devices that support SNMP as of
version v2c. Make sure that you set the correct SNMP Version in
the Credentials for SNMP Devices settings of the parent device or
inherit it from objects that are higher in the object hierarchy 136 .
§ Use GETNEXT requests: Request one OID at a time. This can increase
compatibility with older devices or with devices that have insufficient
SNMP BULKWALK support.
Port Name Template Select how PRTG displays the name of SNMP sensors. Enter a template
that uses several variables. When you add new sensors, PRTG scans
the interface for available counters at certain OIDs. At each OID, several
fields with interface descriptions are usually available. They are different
for every device and OID. PRTG uses the information in these fields to
name the sensors. If a field is empty or if it is not available, PRTG adds
an empty string to the name. By default, the port name template is
([port]) [ifalias] [ifsensor], which creates a name like (001) Ethernet1
Traffic. You can use and combine any field names that are available at an
OID of your device, for example:
§ [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.
§ [ifdescr]: A textual string containing information about the target device
or interface, for example, manufacturer, product name, or version.
462
Setting Description
§ [ifspeed]: An estimate of the monitored interface's current bandwidth

(Kbit/s).
§ [ifsensor]: The type of the sensor, this is Traffic or RMON. This helps to
differentiate between SNMP Traffic and SNMP RMON sensors.
For more information about SNMP sensor names, see the
Knowledge Base: How can I change the defaults for names
automatically generated for new SNMP sensors?
Port Name Update Select how PRTG reacts if you change the names of ports in your
physical device (for example, a switch or router):
§ Keep port names (use this if you edit the names in PRTG) (default): Do
not automatically adjust sensor names. This is the best option if you
want to manually change names in PRTG.
§ Automatically update sensor names if port names change in the
device: If PRTG detects port name changes in your physical device, it
tries to automatically adjust the sensor names accordingly.
For more information about automatic name updates, see the
Knowledge Base: Automatically update port name and number for
SNMP Traffic sensors when the device changes them.
Port Identification Select the field that PRTG uses for SNMP interface identification:
§ Automatic identification (default): Try the ifAlias field first to identify an
SNMP interface and then try ifDescr.
PRTG does not automatically try ifName.
§ Use IfAlias: For most devices, ifAlias is the best field to use for unique
interface names.
§ Use IfDescr: Use this option if the port order of your device changes
after a restart, and if no ifAlias field is available. For example, this is
the best option for Cisco ASA devices.
If you use 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 no unique ifAlias is
available.
If you use this option, it is important that your device returns
unique interface names in the ifName field.
§ Do not update ports: Use this option to disable the automatic port
identification.
Start Interface Index This setting only applies to SNMP Traffic sensors and to Cisco IP
SLA sensors.
Enter the index at which PRTG starts to query the interface range during
sensor creation. Enter 0 for the automatic mode.
463
Setting Description
End Interface Index This setting only applies to SNMP Traffic sensors and to Cisco IP
SLA sensors.
Enter the index at which PRTG stops querying the interface range during
Proxy Settings
§ AWS Alarm v2 § HPE 3PAR Common § NetApp Aggregate v2

Provisioning Group
§ AWS Cost § NetApp I/O v2
§ AWS EBS v2 § NetApp LIF v2
§ AWS EC2 v2 § NetApp LUN v2
§ HTTP
§ AWS ELB v2 § NetApp NIC v2
§ HTTP v2
§ AWS RDS v2 § NetApp Physical Disk v2
§ HTTP Advanced
§ Cisco Meraki License § NetApp SnapMirror v2
§ HTTP Apache ModStatus
§ Cisco Meraki Network Health § NetApp System Health v2
PerfStats
§ Cloud HTTP v2 § NetApp Volume v2
§ Cloud Ping v2 Totals § Redfish Power Supply
§ Dell EMC Unity Enclosure § HTTP Content § Redfish Virtual Disk

Health v2 § HTTP Data Advanced § Redfish Power Supply
§ Dell EMC Unity File System
§ HTTP Transaction § REST Custom
v2
§ Microsoft 365 Mailbox § REST Custom v2
§ Dell EMC Unity Storage
Capacity v2 § Microsoft 365 Service Status § Soffico Orchestra Channel
§ Dell EMC Unity Storage LUN § Microsoft 365 Service Status
Health
v2 Advanced § Soffico Orchestra Scenario
§ Dell EMC Unity Storage Pool § Microsoft Azure SQL § Veeam Backup Job Status
v2 Database
§ Dell EMC Unity VMware § Microsoft Azure Storage Advanced
Datastore v2 Account
§ Zoom Service Status
§ FortiGate System Statistics § Microsoft Azure Subscription
Cost
464
§ FortiGate VPN Overview § Microsoft Azure Virtual
Machine
The proxy settings determine how a sensor connects to a URL. You can enter data for an HTTP proxy
server that sensors use when they connect via HTTP or HTTPS.
This setting only applies to sensors and how they monitor. For more information on how to change
the proxy settings for the PRTG core server, see section Core & Probes 2898 .
The SSL Certificate sensor and the SSL Security Check sensor do not support HTTP proxies but
you can configure connections via SOCKS proxies in the sensors' settings:
Proxy Settings
Setting Description
IP Address/DNS Name Enter the IP address or Domain Name System (DNS) name of the proxy
server. If you leave this field empty, sensors do not use a proxy.
PRTG currently supports only HTTP proxies.
Port Enter the port number of the proxy. The default port is 8080. Enter an
integer.
465
Setting Description
User Name If the proxy requires authentication, enter the user name for the proxy
login. Enter a string or leave the field empty.
Only basic authentication is available.
Password If the proxy requires authentication, enter the password for the proxy
Scanning Interval
Scanning Interval
Setting Description
Scanning Interval Select a scanning interval from the dropdown list that determines the
amount of time that the sensor waits between two scans:
§ 30 seconds
§ 60 seconds
§ 5 minutes
§ 10 minutes
§ 15 minutes
§ 30 minutes
§ 1 hour
§ 4 hours
§ 6 hours
§ 12 hours
466
Setting Description
§ 24 hours
You can change the available intervals in the system

administration 2880 of PRTG Network Monitor.
If a Sensor Query Fails Select the number of scanning intervals that the sensor has time to reach
and to check a device again if a sensor query fails. Depending on the
option that you select, the sensor can try to reach and to check a device
again several times before the sensor shows the Down status 184 . This
can avoid false alarms if the target device only has temporary issues. For
previous scanning intervals with failed requests, the sensor shows the
Warning status.
The following options are available:
§ Set sensor to down status immediately: Set the sensor to the Down
status immediately after the first request fails.
§ Set sensor to warning status for 1 interval, then set to down status
(default): Set the sensor to the Warning status after the first request
fails. If the second request also fails, the sensor shows the Down
status.
§ Set sensor to warning status for 2 intervals, then set to down status:
Set the sensor to the Down status only after the third request fails.
Set the sensor to the Down status only after the fourth request fails.
Set the sensor to the Down status only after the fifth request fails.
Set the sensor to the Down status only after the sixth request fails.
Sensors that monitor via Windows Management Instrumentation
(WMI) always wait at least one scanning interval before they show
the Down status. It is not possible to immediately set a WMI sensor to
the Down status, so the first option does not apply to these sensors. All
other options can apply.
If you define error limits for a sensor's channels, the sensor
immediately shows the Down status. None of the interval options
apply.
If a channel uses lookup 3186 values, the sensor immediately shows
the Down status. None of the interval options apply.
467
Schedules, Dependencies, and Maintenance Window
Setting Description
Schedule Select a schedule from the list. You can use schedules to monitor during
a certain time span (days or hours) every week:
§ None
§ Saturdays
§ Sundays
§ Weekdays
§ Weekdays Eight-To-Eight (08:00 - 20:00)
§ Weekdays Nights (17:00 - 09:00)
§ Weekdays Nine-To-Five (09:00 - 17:00)
§ Weekends
You can create schedules, edit schedules, or pause monitoring for a

specific time span. For more information, see section Schedules 2858 .
Maintenance Window Select if you want to set up a one-time maintenance window:

§ Do not set up a one-time maintenance window (default): Do not set up
a one-time maintenance window. Monitoring is always active.
§ Set up a one-time maintenance window: Set up a one-time
maintenance window and pause monitoring for the selected object and
all child objects. You can define a time span for the pause below.
To close an active one-time maintenance window before the end
date, select Do not set up a one-time maintenance window (default).
468
Setting Description
Maintenance Begins This setting is only visible if you select Set up a one-time maintenance
window above.
Use the date time picker to enter the start date and time of the one-time
maintenance window.
Maintenance Ends This setting is only visible if you select Set up a one-time maintenance
window above.
Use the date time picker to enter the end date and time of the one-time
maintenance window.
Access Rights
Access Rights
469
Setting Description
rights settings.
Management 149 .
Channel Unit Configuration
470
Setting Description
Channel Unit Types For each type of channel, select the unit in which PRTG displays the
data. If you define this setting on probe, group, or device level, you can
inherit these settings to all sensors underneath. You can set units for the
following channel types (if available):
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
Custom channel types are only available on sensor level.
Which channel units are available depends on the sensor type and
the available parameters. If no configurable channels are available,
this field shows No configurable channels.
Advanced Network Analysis
Setting Description
Unusual Detection Select if you want to use the unusual detection 2881 for sensors:
471
Setting Description
§ Enable (default): Activates the unusual detection for this object and, by
default, for all objects underneath in the object hierarchy 136 . Sensors
that are affected by this setting show the Unusual status if PRTG
detects unusual activity.
§ Disable: Does not activate the unusual detection. PRTG ignores
unusual values for sensors that are affected by this setting. These
sensors do not show the Unusual status.
You can configure the behavior of the unusual detection or
completely disable it in the system settings 2881 .
Similar Sensors Select if you want to activate the similar sensors 195 analysis:
Detection
§ Enable (default): Activates the similar sensors detection for this object
and, by default, for all objects underneath in the object hierarchy. PRTG
considers all sensors that are affected by this setting during the
similarity analysis.
§ Disable: Does not activate the similar sensors detection. PRTG does
not consider sensors that are affected by this setting during the
You can configure the depth of the analysis of the similar sensors
detection or completely disable it in the system settings 2883 .
System Information Select if you want to retrieve and show system information 208 for your
devices:
§ Enable (default): Activates the system information feature for this object
and, by default, for all objects underneath in the hierarchy.
§ Disable: Does not activate the system information feature.
The System Information feature is enabled by default. To retrieve the

data, PRTG automatically uses the credentials for Windows
systems 621 and the credentials for SNMP devices 630 that you entered in
the device settings or that the device inherits 136 from a parent object like
the root group. Consider this when you monitor devices that are outside of
your local network, especially when you use SNMP v1 or SNMP v2c,
which do not provide encryption.
This setting is not available on the hosted probe of a PRTG Hosted

Monitor instance.
Save your settings. If you change tabs or use the main menu without saving, all changes to the
settings are lost.
More
KNOWLEDGE BASE
472
PRTG?

How can I change the defaults for names automatically generated for new SNMP sensors?
Automatically update port name and number for SNMP Traffic sensors when the device changes them
473
7.5 Probe Settings
The following settings are available on the Settings tab of a probe.
We recommend that you define as many settings as possible in the root group settings 436 so that
you can inherit them to all other objects in the object hierarchy 136 .
In this section:
§ Basic Probe Settings 475
§ Location 476
474
§ Administrative Probe Settings 536
§ Scheduled Restart Settings 538
Basic Probe Settings
Basic Probe Settings
Setting Description
Probe Name Enter a name to identify the probe. By default, PRTG shows this name in
475
Setting Description
comma, or the Enter key. You can use tags to group objects and use tag-
filtered views later on. Tags are not case-sensitive. Tags are automatically
inherited 142 .
Monitoring Status Select the monitoring status of the probe:

§ Started (default): Monitor the probe.
§ Paused: Pause monitoring for the probe. All sensors on all devices on
the probe are in the Paused status 230 until you change this setting.
Priority Select a priority 227 for the probe. This setting determines the position of
the probe in lists. The highest priority is at the top of a list. You can
choose from the lowest priority ( ) to the highest priority (
).
Inherited Settings
Location
476
Location
Setting Description
enter 49.452778 any 11.077778 text.
geographical map.


Errors Length
477
§ Event Log (Windows API) § Windows Network Card § WMI Microsoft SQL Server
2005 (Deprecated)
§ Exchange Backup § Windows Pagefile
(PowerShell) § WMI Microsoft SQL Server
2008
§ Exchange Database
§ Windows Process 2012
§ Exchange Database DAG
(PowerShell) § Windows SMTP Service § WMI Microsoft SQL Server
Received 2014
(PowerShell) § Windows SMTP Service Sent § WMI Microsoft SQL Server
2016
§ Exchange Mailbox § Windows System Uptime
§ Windows Updates Status 2017
§ Exchange Public Folder (PowerShell)
§ WMI Battery 2019
§ File
§ WMI Custom § WMI Remote Ping
§ File Content
§ WMI Custom String § WMI Security Center
§ Folder
§ WMI Disk Health § WMI Service
§ Hyper-V Cluster Shared
Volume Disk Free § WMI Event Log § WMI Share
§ Hyper-V Host Server § WMI Exchange Server § WMI SharePoint Process
§ Hyper-V Virtual Machine § WMI Exchange Transport § WMI Storage Pool

Queue
§ Hyper-V Virtual Network § WMI Terminal Services
Adapter § WMI File (Windows 2008+)
§ Hyper-V Virtual Storage § WMI Free Disk Space (Multi § WMI Terminal Services
Device Disk) (Windows XP/Vista/2003)
§ PerfCounter Custom § WMI HDD Health § WMI UTC Time
Pool
§ WMI Volume
§ Share Disk Free
§ WSUS Statistics
§ Windows CPU Load
478
Setting Description
Windows sensors.
479
§ SSH Disk Free
§ SSH INodes Free
§ SSH Load Average
§ SSH Meminfo
§ SSH Remote Ping
§ SSH Script
480
481
Setting Description


via WBEM:

482
Setting Description
5989.
22.
settings.
system:
Name above.
483
Setting Description
SSH sensors 3017 :
deprecated.

484
Setting Description
Citrix XenServer:
485
Setting Description


v2
Blade
Enclosure Health
Disk
§ SNMP Cisco CBQoS
Interface
Disk Health
Health Disk
§ SNMP RMON
Physical Disk
§ SNMP Custom
Health
486
Health
Environment
Logical Disk Health
Disk
§ SNMP Library
Physical Disk
§ SNMP Memory
487
Setting Description
488
Setting Description
limitation.
above.


authentication.
device.
489
Setting Description

device.

algorithm.
algorithm.
of your device.
error message.
490
§ ADO SQL v2
§ Microsoft SQL v2
§ MySQL v2
§ Oracle SQL v2
§ PostgreSQL
Setting Description
databases:
491
Setting Description

ú MySQL: 3306
ú Oracle SQL: 1521
ú PostgreSQL: 5432
Credentials for AWS

492
§ AWS Alarm v2
§ AWS Cost
§ AWS EBS v2
§ AWS EC2 v2
§ AWS ELB v2
§ AWS RDS v2
Credentials for AWS
Setting Description

493
Status sensors?
Setting Description

494
Setting Description
endpoint URL.

Microsoft Entra ID.

Microsoft Entra ID.

§ EXE/Script
§ SSH Script
495
Setting Description
496
Setting Description

Setting Description
possible choices.

497
Setting Description

498
Setting Description

499
Setting Description
500
Setting Description
3PAR system:
system?

§ HTTP v2
501
Setting Description
502
Setting Description

503
Setting Description

504
Setting Description

§ MQTT Round Trip
§ MQTT Statistics
505
Setting Description
is 1883.

MQTT broker.

506
Setting Description


§ NetApp I/O v2
§ NetApp LIF v2
§ NetApp LUN v2
§ NetApp NIC v2
§ NetApp Volume v2
507
Setting Description
508
Setting Description
System Manager:

§ OPC UA Custom
509
Setting Description

510
Setting Description
the OPC UA server.
want to use:
the OPC UA server.

511
Setting Description

to use.

512
Setting Description
513
Setting Description
Orchestra platform:

514
Setting Description
system:
515
§ REST Custom v2
Setting Description
516
Setting Description

517
Setting Description
Manager.
Manager.

518
Setting Description

WMI.

timeout value.
519
Setting Description

520
521
Setting Description
delay.
device resets counters without an overflow. PRTG interprets such behavior
as overflow that results in data peaks. Select the option Ignore (default) in
this case. For more information, see the Knowledge Base: What is the
Overflow Values setting in the SNMP Compatibility Options?
Zero Values Select how PRTG handles zero values. Some devices send incorrect zero
values. This can cause false peaks. PRTG can handle zero values in two
ways:
devices.
522
Setting Description
response size.
that uses several variables. When you add new sensors, PRTG scans the
interface for available counters at certain OIDs. At each OID, several fields
with interface descriptions are usually available. They are different for
every device and OID. PRTG uses the information in these fields to name
the sensors. If a field is empty or if it is not available, PRTG adds an
empty string to the name. By default, the port name template is ([port])
[ifalias] [ifsensor], which creates a name like (001) Ethernet1 Traffic. You
can use and combine any field names that are available at an OID of your

the local device.
523
Setting Description

(Kbit/s).
For more information about SNMP sensor names, see the Knowledge
Base: How can I change the defaults for names automatically
generated for new SNMP sensors?
§ Automatically update sensor names if port names change in the device:
If PRTG detects port name changes in your physical device, it tries to
automatically adjust the sensor names accordingly.
interface names.
after a restart, and if no ifAlias field is available. For example, this is the
best option for Cisco ASA devices.
If you use this option, it is important that your device returns unique
interface names in the ifDescr field.
available.
interface names in the ifName field.
identification.
SLA sensors.
524
Setting Description
SLA sensors.
Proxy Settings

Provisioning Group
§ HTTP
§ HTTP v2
§ HTTP Advanced
PerfStats

v2
Health
v2 Database
525
§ FortiGate System Statistics § Microsoft Azure Subscription § Zoom Service Status
Cost
§ Microsoft Azure Virtual
Machine
Proxy Settings
Setting Description
526
Setting Description
integer.
Scanning Interval
Scanning Interval
Setting Description
§ 30 seconds
§ 60 seconds
§ 5 minutes
527
Setting Description
§ 10 minutes
§ 15 minutes
§ 30 minutes
§ 1 hour
§ 4 hours
§ 6 hours
§ 12 hours
§ 24 hours

Warning status.
status.
528
Setting Description

apply.
Cluster Monitoring Exclusion

Setting Description
Exclude Cluster Nodes This setting is only visible if you have a failover cluster 132 .
Sometimes you want to keep a cluster node from monitoring the sensors
that run on this probe, group, or device, for example, if a device is not
reachable from every cluster node. Select the cluster nodes that you do
not want to include in sensor scans. By default, all objects underneath
the probe inherit 140 this setting.

You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The
corresponding settings from the parent objects are always active. However, you can define additional
schedules, dependencies, and maintenance windows. They are active at the same time as the parent
objects' settings.
529
Setting Description
§ None
§ Saturdays
§ Sundays
§ Weekdays
§ Weekends

530
Setting Description


window above.
maintenance window.
window above.
maintenance window.
Dependency Type Select a dependency type. You can use dependencies to pause
monitoring for an object depending on the status of a different object:
§ Use parent (default): Use the dependency type of the parent object.
§ Select a sensor: Use the dependency type of the parent object.

Additionally, pause the current object if a specific sensor is in the Down
status or in the Paused status because of another dependency.
You do not trigger a status change by dependency if you manually

pause a master sensor or if you pause it by schedule.
To test your dependencies 2738 , select Simulate Error Status from the
context menu of an object that other objects depend on. A few
seconds later, all dependent objects are paused. You can check all
dependencies under Devices | Dependencies in the main menu bar.
Dependency This setting is only visible if you select Select a sensor above.
Click and use the object selector 225 to select a sensor on which the
current object will depend.
Dependency Delay This setting is only visible if you select Select a sensor above.
(Sec.)
Define a time span in seconds for the dependency delay.
531
Setting Description
After the master sensor for this dependency returns to the Up status,
PRTG additionally delays the monitoring of the dependent objects by the
time span you define. This can prevent false alarms, for example, after a
server restart or to give systems more time for all services to start. Enter
an integer.
Access Rights
Access Rights
532
Setting Description
rights settings.
Management 149 .

533
Setting Description
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
534
Setting Description
Detection
535
Setting Description
devices:


Monitor instance.
Administrative Probe Settings

Define the IP address to use for outgoing monitoring requests.
§ If more than one IP is available on the system, you can specify the IP address that PRTG uses for the
outgoing monitoring requests of certain sensors.
§ This setting is for sensors that use the following connection types: HTTP, Domain Name System
(DNS), File Transfer Protocol (FTP), Internet Message Access Protocol (IMAP), Post Office Protocol
version 3 (POP3), port, remote desktop, Simple Mail Transfer Protocol (SMTP), and Simple Network
Management Protocol (SNMP).
§ The setting is valid for all monitoring requests that this probe sends.
§ This setting is useful for devices that expect a certain IP address when they are queried.
§ The default setting is auto. PRTG automatically selects an IP address.
This feature does not support all sensors for technical reasons.
If you change this setting, some sensors might stop working. For example, sensors might show the
Down status if the selected IP address is blocked on the way to or directly on the target device.
536
Administrative Probe Settings
Setting Description
Outgoing IPv4 Define the IP address for outgoing requests that use the IPv4 protocol.
The list shows all available IP addresses on the system. Choose a
specific IP address or select auto.
Outgoing IPv6 Define the IP address for outgoing requests that use the IPv6 protocol.
The list shows all available IP addresses on the system. Choose a
For more information, see section IPv6 Support 154 .
Cluster Connectivity This setting is only visible if you have a failover cluster 132 .
Define if the remote probe connects to all cluster nodes or only to the
primary master node:
§ Remote probe sends data only to primary master node: The remote
probe only connects to the primary master node. You are not able to
review monitoring data on failover nodes. Consider this option if you
have bandwidth limitations in your network or if the remote probe
cannot access your failover nodes.
537
Setting Description
§ Remote probe sends data to all cluster nodes: The remote probe
connects to all cluster nodes and sends monitoring data to the failover
nodes in addition to the primary master node. The remote probe is
visible on all of your cluster nodes as soon as it automatically connects
to the correct IP addresses and ports of the failover nodes. If the
primary master node fails, you can still see monitoring data of the
remote probe.
PRTG does not notify you if a remote probe is disconnected from a
cluster node. Therefore, explicitly check on a cluster node if remote
probes are connected (for example, via the device tree in the PRTG web
interface on a cluster node).
Scheduled Restart Settings

This setting is not available on the hosted probe of a PRTG Hosted Monitor instance.
Setting Description
Restart Options Define if you want to schedule an automatic restart:

§ No scheduled system or service restart: Do not automatically perform a
scheduled restart of services. We recommend that you manually restart
the PRTG core server system every few weeks. You can initiate a
restart of the PRTG probe service in the Administrative Tools 2928 in the
PRTG web interface.
§ Scheduled restart of PRTG services: Restart the PRTG probe service
on the probe system. If you select this option on the local probe, the
PRTG core server service restarts as well. Define a schedule under
Restart Schedule.
538
Setting Description
§ Scheduled system restart (recommended): Define a schedule under

Restart Schedule. We recommend that you restart probe systems
once a month for best performance.
Restart Schedule This setting is only visible if you select a schedule option above.
Choose how often you want to restart the PRTG probe service or the
probe system:
§ Once per week: Select a day and a time below.
§ Once per month (recommended): Select a day of the month and a time
below.
Day Select a day of the week (Monday to Sunday) or month (1st to 30th or
Last). If you select Last, PRTG restarts the PRTG core server system on
the last day of the month, regardless of how many days the month has.
Time This setting is only visible if you select a schedule option above.
Select a time for the planned restart.

You get a Windows warning message 10 minutes before the restart
to inform you about the restart if you are logged in to PRTG. The
actual restart time can differ by up to 30 minutes from the time you enter
here.
settings are lost.
More
KNOWLEDGE BASE

PRTG?
539

540
7.6 Group Settings
The following settings are available on the Settings tab of a group.
This documentation does not refer to the settings of the root group. For more information, see
section Root Group Settings 436 .
In this section:
§ Location 549
541
§ Number of Sensors Limitation 609
542
Setting Description
Monitoring Status Select the monitoring status of the group:

§ Started (default): Monitor the group.
§ Paused: Pause monitoring for the group. All sensors on all devices in
the group are in the Paused status 230 until you change this setting.
Parent Tags Shows the tags 142 that this group inherits 142 from its parent probe 137 .
This setting is for your information only. You cannot change it.
Priority Select a priority 227 for the group. This setting determines the position of
the group in lists. The highest priority is at the top of a list. You can
).
543
Setting Description
sensors available.
list.
Device Templates This setting is only visible if you select Auto-discovery with specific
device templates above.

§ ADSL
§ Cisco ASA VPN
544
Setting Description
§ Dell EqualLogic
§ Dell MDi Disk
§ DNS Server
§ FTP Server
§ HTTP Web Server
§ NAS LenovoEMC
§ NAS QNAP
§ NAS Synology
§ NetApp
§ NTP Server
§ Printer (HP)
§ RDP Server
§ Server (Dell)
§ Server (Fujitsu)
§ Server (IBM)
§ SonicWall
545
Setting Description
§ UPS Health (APC)
§ Web Server
§ XenServer Hosts
minutes.
Auto-Discovery.
Auto-Discovery.
546
Setting Description
IP Address Selection Select how you want to define the IP address range for the auto-
Method discovery:
§ Class C base IP address with start/end (IPv4) (default): Enter an IPv4
class C address range.
individual IPv4 addresses or Domain Name System (DNS) names.
§ IP address and subnet (IPv4): Enter an IPv4 address and subnet mask.
§ IP address with octet range (IPv4): Enter an IPv4 address range for
every IP octet individually. With this, you can define very customizable
IP address ranges.
individual IPv6 addresses or DNS names.
§ Use computers from the Active Directory (maximum 1000 computers):
Search in the Active Directory for computers to perform the auto-
discovery.
Make sure that you specify your Active Directory domain in the
Core & Probes 2907 settings.
PRTG can only discover subnets with up to 65,536 IP addresses. If
you define a range with a higher number of addresses, the discovery
stops before it is completed.
IPv4 Base This setting is only visible if you select Class C base IP address with
Enter a class C network as the IP base for the auto-discovery. Enter the
first three octets of an IPv4 address, for example, 192.168.0.
IPv4 Range Start This setting is only visible if you select Class C base IP address with
Enter the IP octet of the class C network (specified above) from which
PRTG starts the auto-discovery. This completes the IP base to an IPv4
address. For example, enter 1 to discover from 192.168.0.1 onwards.
IPv4 Range End This setting is only visible if you select Class C base IP address with
Enter the IP octet of the class C network (specified above) at which

PRTG stops the auto-discovery. This completes the IP base to an IPv4
address. For example, enter 254 to discover up to 192.168.0.254.
IPv4/DNS Name List This setting is only visible if you select List of individual IP addresses and
IPv6/DNS Name List DNS names (IPv4) or List of individual IP addresses and DNS names
(IPv6) above.
547
Setting Description
Enter a list of IP addresses or DNS names that the auto-discovery scans.

Enter each address on a separate line.
IPv4 and Subnet (IPv4) This setting is only visible if you select IP address and subnet (IPv4)
above.
Enter an expression in the format address/subnet, for example,

192.168.3.0/255.255.255.0. You can also use the short form like
192.168.3.0/24. PRTG scans the complete host range (without network
and broadcast address) that is defined by the IP address and the subnet
mask.
IP Address with Octet This setting is only visible if you select IP address with octet range (IPv4)
Range 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. PRTG calculates all permutations of all ranges. For
example, 10.0.1-10.1-100 results in 1,000 IP addresses that PRTG scans
during the auto-discovery.
Organizational Unit This setting is only visible if you select Use computers from the Active
Directory (maximum 1000 computers) above.
Enter an organizational unit (OU) to restrict the Active Directory search to

computers that are part of this OU. For top-level OUs, use the
distinguished name (DN) format without OU= and without the domain
components (DCS). If you leave this field empty, there are not any
restrictions.
Example:
§ For the DN OU=Domain Controllers,DC=example,DC=com, enter only
Domain Controllers.
If you have sub-OUs, use the DN format without the leading OU= and
without the DCS.
Examples:
§ For the DN OU=webserver,OU=production,DC=example,DC=com,
enter only webserver,OU=production.
§ For the DN
OU=intranet,OU=webserver,OU=production,DC=example,DC=com,
enter only intranet,OU=webserver,OU=production.
Make sure that the OU contains computer accounts. If the OU is
empty, you receive an error message.
548
Setting Description
Do not enter the domain components. PRTG automatically uses the

domain components from the domain name you enter in the Core &
Probes 2907 settings.
Name Resolution Select how to monitor newly discovered devices. This only affects new
devices. This does not change the setting for other devices. Depending
on your selection, the IP Address/DNS Name field of an added device 614
shows the DNS name or IP address that PRTG uses to access the target
device:
§ Use DNS names (default): Monitor newly discovered devices via their
DNS names (if available) We recommend that you use this option.
§ Use IP addresses: Monitor newly discovered devices via their IP
addresses.
This setting does not affect how PRTG shows the devices in the
device tree.
Device Rescan Select how to handle known devices:

§ Skip auto-discovery for existing devices/IP addresses (default): Do not
rescan existing devices or IP addresses. PRTG only adds devices with
new IP addresses or DNS names. PRTG does not add devices that
that already exist in your configuration for example, in other groups.
We recommend that you use this option.
§ Perform auto-discovery for existing devices/IP addresses: Rescan
devices that have existing IP addresses with every auto-discovery.
PRTG adds devices that already exist in other groups to this group and
runs the auto-discovery on the newly added devices.
The auto-discovery does not run on devices that already exist in
the group. If you want to run the auto-discovery for these devices,
you must manually start the auto-discovery on them.
In certain cases, the IP resolution might not work and might result in
PRTG not adding a device if it has the same local IP address as it
does in a different LAN.
Inherited Settings
Location
549
Location
Setting Description
enter 49.452778 any 11.077778 text.
geographical map.


Errors Length
550
2005 (Deprecated)
2008
Received 2014
2016
§ WMI Battery 2019
§ File
§ File Content
§ Folder

Queue
Pool
§ WMI Volume
§ Share Disk Free
§ WSUS Statistics
§ Windows CPU Load
551
Setting Description
Windows sensors.
552
§ SSH Disk Free
§ SSH INodes Free
§ SSH Load Average
§ SSH Meminfo
§ SSH Remote Ping
§ SSH Script
553
554
Setting Description
§ Password: Provide the password for the login.
Password This setting is only visible if you select Password above.


via WBEM:

555
Setting Description
5989.
22.
settings.
system:
Name above.
556
Setting Description
SSH sensors 3017 :
deprecated.

557
Setting Description
Citrix XenServer:
558
Setting Description


v2
Blade
Enclosure Health
Disk
§ SNMP Cisco CBQoS
Interface
Disk Health
Health Disk
§ SNMP RMON
Physical Disk
§ SNMP Custom
Health
559
Health
Environment
Logical Disk Health
Disk
§ SNMP Library
Physical Disk
§ SNMP Memory
560
Setting Description
561
Setting Description
limitation.
above.


authentication.
device.
562
Setting Description

device.

algorithm.
algorithm.
of your device.
error message.
563
§ ADO SQL v2
§ Microsoft SQL v2
§ MySQL v2
§ Oracle SQL v2
§ PostgreSQL
Setting Description
databases:
564
Setting Description

ú MySQL: 3306
ú Oracle SQL: 1521
ú PostgreSQL: 5432
Credentials for AWS

565
§ AWS Alarm v2
§ AWS Cost
§ AWS EBS v2
§ AWS EC2 v2
§ AWS ELB v2
§ AWS RDS v2
Credentials for AWS
Setting Description

566
Status sensors?
Setting Description

567
Setting Description
endpoint URL.

Microsoft Entra ID.

Microsoft Entra ID.

§ EXE/Script
§ SSH Script
568
Setting Description
569
Setting Description

Setting Description
possible choices.

570
Setting Description
571
Setting Description

572
Setting Description
573
Setting Description
3PAR system:
system?

§ HTTP v2
574
Setting Description
575
Setting Description

576
Setting Description

577
Setting Description

§ MQTT Round Trip
§ MQTT Statistics
578
Setting Description
579
Setting Description
is 1883.

MQTT broker.

580
Setting Description


§ NetApp I/O v2
§ NetApp LIF v2
§ NetApp LUN v2
§ NetApp NIC v2
§ NetApp Volume v2
581
Setting Description
582
Setting Description
System Manager:

§ OPC UA Custom
583
Setting Description

584
Setting Description
the OPC UA server.
want to use:
the OPC UA server.

585
Setting Description

to use.

586
Setting Description
587
Setting Description
Orchestra platform:

588
Setting Description
system:
589
§ REST Custom v2
Setting Description
590
Setting Description

591
Setting Description
Manager.
Manager.

592
Setting Description

WMI.
WMI.
sensor returns no data. We recommend that you use this option.
593
Setting Description

timeout value.

594
595
Setting Description
delay.
ways:
devices.
596
Setting Description
response size.

the local device.
597
Setting Description

(Kbit/s).
interface names.
available.
identification.
SLA sensors.
598
Setting Description
SLA sensors.
Proxy Settings

Provisioning Group
§ HTTP
§ HTTP v2
§ HTTP Advanced
PerfStats

v2
Health
v2 Database
599
Cost
Machine
Proxy Settings
Setting Description
600
Setting Description
integer.
Scanning Interval
Scanning Interval
Setting Description
§ 30 seconds
§ 60 seconds
§ 5 minutes
601
Setting Description
§ 10 minutes
§ 15 minutes
§ 30 minutes
§ 1 hour
§ 4 hours
§ 6 hours
§ 12 hours
§ 24 hours

Warning status.
status.
602
Setting Description

apply.

Setting Description
§ None
§ Saturdays
§ Sundays
603
Setting Description
§ Weekdays
§ Weekends


window above.
maintenance window.
window above.
maintenance window.

Additionally, pause the current object if a specific sensor is in the
Down status or in the Paused status because of another dependency.
604
Setting Description
Dependency Delay (Sec.) This setting is only visible if you select Select a sensor above.

an integer.
Access Rights
Access Rights
605
Setting Description
rights settings.
Management 149 .

606
Setting Description
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
607
Setting Description
Detection
608
Setting Description
devices:


Monitor instance.
Number of Sensors Limitation
Number of Sensors Limitation
Setting Description
Sensor Limit Define a limit for the maximum number of sensors in this group, including
subgroups:
§ Allow unlimited number of sensors: Do not limit the number of sensors
for this group. Any number of sensors are allowed in this group and its
subgroups.
609
Setting Description
§ Limit number of sensors: Set a limit for the number of sensors in this
group. Only a defined number of sensors are allowed in this group and
its subgroups. If the amount of sensors exceeds the limit, PRTG sets
the surplus sensors to the Paused status.
Maximum Number of This setting is only visible if you select Limit number of sensors above.
Sensors
Define how many sensors are allowed in this group and its subgroups.
Sensors that exceed this group sensor limit are set to the Paused state.
Enter an integer.
Sensors that are in the Paused state count for this group limit as well
(for example, manually paused sensors or sensors that are paused
by dependency or schedule), but not for the number of available sensors
in your license.
Manually paused sensors override the sensor message exceeds
group sensor limit.
settings are lost.
More
KNOWLEDGE BASE

PRTG?

610
611
7.7 Device Settings
The following settings are available on the Settings tab of a device.
For device settings, you can also use multi-edit. This enables you to change the settings of many
devices at the same time.
For more information, see section Multi-Edit 2729 .
In this section:
§ Basic Device Settings 614
§ Additional Device Information 616
§ Location 620
612
613
614
Setting Description
Device Name Enter a name to identify the device. By default, PRTG shows this name in
Monitoring Status Select the monitoring status of the device:

§ Started (default): Monitor the device.
§ Paused: Pause monitoring for the device. All sensors on the device are
in the Paused status 230 until you change this setting.
IP Version Select the IP protocol that PRTG uses to connect to the device:
The setting is valid for all sensors that you create on the device.
Parent Tags Shows tags 142 that this device inherits 142 from its parent group 137 and
its parent probe 137 .
615
Setting Description
We recommend that you use the default value. You can also add
additional tags.
Priority Select a priority 227 for the device. This setting determines the position of
the group in lists. The highest priority is at the top of a list. You can
).
616
Setting Description
Device Icon Select a device icon. PRTG shows it in the device tree.
Service URL Specify a URL to open directly when you select Device Tools | Go to
Service URL from the context menu 240 of the device. For example, you
can configure this option to open the address
http://www.example.com/service.html. Enter a valid URL or leave the field
empty.
Setting Description
sensors available.
list.
617
Setting Description


minutes.
Auto-Discovery.
Auto-Discovery.
templates above.

§ ADSL
§ Cisco ASA VPN
§ Dell EqualLogic
§ Dell MDi Disk
§ DNS Server
§ FTP Server
618
Setting Description
§ HTTP Web Server
§ NAS LenovoEMC
§ NAS QNAP
§ NAS Synology
§ NetApp
§ NTP Server
§ Printer (HP)
§ RDP Server
§ Server (Dell)
§ Server (Fujitsu)
§ Server (IBM)
§ SonicWall
§ UPS Health (APC)
619
Setting Description
§ Web Server
§ XenServer Hosts
Inherited Settings
Location
620
Location
Setting Description
enter 49.452778 any 11.077778 text.
geographical map.


Errors Length
621
2005 (Deprecated)
2008
Received 2014
2016
§ WMI Battery 2019
§ File
§ File Content
§ Folder

Queue
Pool
§ WMI Volume
§ Share Disk Free
§ WSUS Statistics
§ Windows CPU Load
622
Setting Description
Windows sensors.
623
§ SSH Disk Free
§ SSH INodes Free
§ SSH Load Average
§ SSH Meminfo
§ SSH Remote Ping
§ SSH Script
624
625
Setting Description


via WBEM:

626
Setting Description
5989.
22.
settings.
system:
Name above.
627
Setting Description
SSH sensors 3017 :
deprecated.

628
Setting Description
Citrix XenServer:
629
Setting Description


v2
Blade
Enclosure Health
Disk
§ SNMP Cisco CBQoS
Interface
Disk Health
Health Disk
§ SNMP RMON
Physical Disk
§ SNMP Custom
Health
630
Health
Environment
Logical Disk Health
Disk
§ SNMP Library
Physical Disk
§ SNMP Memory
631
Setting Description
632
Setting Description
limitation.
above.


authentication.
device.
633
Setting Description

device.

algorithm.
algorithm.
of your device.
error message.
634
§ ADO SQL v2
§ Microsoft SQL v2
§ MySQL v2
§ Oracle SQL v2
§ PostgreSQL
Setting Description
databases:
635
Setting Description

ú MySQL: 3306
ú Oracle SQL: 1521
ú PostgreSQL: 5432
Credentials for AWS

636
§ AWS Alarm v2
§ AWS Cost
§ AWS EBS v2
§ AWS EC2 v2
§ AWS ELB v2
§ AWS RDS v2
Credentials for AWS
Setting Description

637
Status sensors?
Setting Description

638
Setting Description
endpoint URL.

Microsoft Entra ID.

Microsoft Entra ID.

§ EXE/Script
§ SSH Script
639
Setting Description
640
Setting Description

Setting Description
possible choices.

641
Setting Description
642
Setting Description

643
Setting Description
644
Setting Description
3PAR system:
system?

§ HTTP v2
645
Setting Description
646
Setting Description

647
Setting Description

648
Setting Description

§ MQTT Round Trip
§ MQTT Statistics
649
Setting Description
650
Setting Description
is 1883.

MQTT broker.

651
Setting Description


§ NetApp I/O v2
§ NetApp LIF v2
§ NetApp LUN v2
§ NetApp NIC v2
§ NetApp Volume v2
652
Setting Description
653
Setting Description
System Manager:

§ OPC UA Custom
654
Setting Description

655
Setting Description
the OPC UA server.
want to use:
the OPC UA server.

656
Setting Description

to use.

657
Setting Description
658
Setting Description
Orchestra platform:

659
Setting Description
system:
660
§ REST Custom v2
Setting Description
661
Setting Description

662
Setting Description
Manager.
Manager.

663
Setting Description

WMI.

timeout value.
664
Setting Description

665
666
Setting Description
delay.
ways:
devices.
667
Setting Description
response size.

the local device.
668
Setting Description

(Kbit/s).
interface names.
available.
identification.
SLA sensors.
669
Setting Description
SLA sensors.
Proxy Settings

Provisioning Group
§ HTTP
§ HTTP v2
§ HTTP Advanced
PerfStats

v2
Health
v2 Database
670
Cost
Machine
Proxy Settings
Setting Description
671
Setting Description
integer.
Scanning Interval
Scanning Interval
Setting Description
§ 30 seconds
§ 60 seconds
§ 5 minutes
672
Setting Description
§ 10 minutes
§ 15 minutes
§ 30 minutes
§ 1 hour
§ 4 hours
§ 6 hours
§ 12 hours
§ 24 hours

Warning status.
status.
673
Setting Description

apply.

Setting Description
§ None
§ Saturdays
§ Sundays
674
Setting Description
§ Weekdays
§ Weekends


window above.
maintenance window.
window above.
maintenance window.

Additionally, pause the current object if a specific sensor is in the Down
status or in the Paused status because of another dependency.
675
Setting Description
Dependency Delay This setting is only visible if you select Select a sensor above.
(Sec.)
an integer.
Access Rights
Access Rights
676
Setting Description
rights settings.
Management 149 .

677
Setting Description
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
678
Setting Description
Detection
679
Setting Description
devices:


Monitor instance.
settings are lost.
More
KNOWLEDGE BASE

PRTG?
680
681
7.8 Sensor Settings
There is a dedicated section for every sensor with details about the available settings.
Basic Sensor Settings

Every sensor has the same basic settings.
Setting Description
Sensor Name Enter a name to identify the sensor. By default, PRTG shows this name
in the device tree, as well as in alarms, logs, notifications, reports, maps,
libraries, and tickets.
Parent Tags The tags that the sensor inherits from its parent device, parent group, and
parent probe.
automatically inherited.
Every sensor has default tags. For more information, see the specific
sensor settings section.
682
Setting Description
Priority Select a priority for the sensor. This setting determines the position of the
sensor in lists. The highest priority is at the top of a list. Choose from the
lowest priority ( ) to the highest priority ( ).
For more information, see section Available Sensor Types.
For sensor settings, multi-edit is also available. This lets you to change properties of many sensors
at the same time. For more information, see section Multi-Edit.
To detect unexpected correlations between your network components, PRTG provides a similar sensors
analysis.
Usually, a sensor connects to the IP Address/DNS Name of the parent device. See the device
settings for details. For some sensors, you can explicitly define the monitoring target in the sensor
settings.
683
7.8.1 Active Directory Replication Errors Sensor
The Active Directory Replication Errors sensor checks a Windows domain controller (DC) for replication
errors.
Active Directory Replication Errors Sensor
For a detailed list and descriptions of the channels that this sensor can show, see section Channel
List 688 .
Sensor in Other Languages

§ Dutch: Active Directory Replicatie Fouten
§ French: Active Directory erreurs de réplication
§ German: Active Directory Replikationsfehler
§ Japanese: AD
§ Portuguese: Erros de replicação Active Directory
§ Russian: Active Directory

§ Simplified Chinese:
§ Spanish: Errores de replicación Active Directory
684
Remarks
Consider the following remarks 685 and requirements for this sensor:
Remark Description
Performance impact § This sensor has a high performance impact. We recommend that you
use no more than 200 of this sensor on each probe.
Member of Windows § This sensor only works if the probe system is part of the domain whose
domain Active Directory you want to monitor.
.NET 4.7.2 or later § This sensor requires .NET 4.7.2 or later from Microsoft on the probe
system. In a cluster, install it on every cluster node. If the sensor
shows the error PE087, additionally install .NET 3.5 on the probe
system.
If the framework is missing, you cannot create this sensor.
does PRTG require?
Windows Server § We recommend Windows Server 2016 on the probe system for best
performance of this sensor.
Parent device § This sensor requires that the parent device is a DC.
Credentials § This sensor requires credentials for Windows systems.
§ Otherwise, the sensor cannot correctly connect.
§ We recommend that you use Windows domain credentials.
If you use local credentials, make sure that the same Windows user
accounts (with the same user name and password) exist on both the
probe system and the target system.
IPv6 § This sensor supports IPv6.
Lookups § This sensor uses lookups to determine the status values of one or more
channels.
Hosted probe You cannot add this sensor to the hosted probe of a PRTG Hosted
Monitor instance. If you want to use this sensor, add it to a remote
probe device.
685
The sensor has the following default tags that are automatically predefined in the sensor's settings when
you add the sensor:
§ ptfsensor
For more information about basic sensor settings, see section Sensor Settings 682 .
Sensor Settings
Sensor Settings
Setting Description
Replication Neighbor The replication neighbor whose replication connection this sensor
monitors.
Naming Context Select the Active Directory naming context that you want to monitor:
§ Configuration (default): Includes information about partitions, sites,
services, or the Active Directory schema.
§ Schema: Includes the information by which objects, classes, and
attributes that are used in the Active Directory are defined.
§ DomainDnsZones: Includes information about the domain controllers
that are in the domain.
§ Domain: Includes domain information that is replicated to this domain's
domain controllers, for example information about computers or users.
The probe system must be part of the domain whose naming
context you want to monitor.
686
Setting Description
§ ForestDnsZones: Includes information about domain controllers in the

forest.
You cannot change this value after sensor creation.
Debug Options
Debug Options
Setting Description
Result Handling Define what PRTG does with the sensor result:
§ Discard result (default): Do not store the sensor result.
§ Store result: Store the last sensor result in the \Logs\sensors subfolder
of the PRTG data directory on the probe system. The file names are
Result of Sensor [ID].txt and Result of Sensor [ID].Data.txt. This setting
is for debugging purposes. PRTG overwrites these files with each
scanning interval.
In a cluster, PRTG stores the result in the PRTG data directory of the
master node.
Sensor Display
Sensor Display
Setting Description
Primary Channel Select a channel from the list to define it as the primary channel. In the
device tree, PRTG displays the last value of the primary channel below
the sensor's name. The available options depend on what channels are
687
Setting Description
available for this sensor.

You can set a different primary channel later by clicking below a
channel gauge on the sensor's Overview tab.
Graph Type Define how this sensor shows different channels:
§ Show channels independently (default): Show a graph for each channel.
§ Stack channels on top of each other: Stack channels on top of each

other to create a multi-channel graph. This generates a graph that
visualizes the different components of your total traffic.
You cannot use this option in combination with manual Vertical
Axis Scaling (available in the channel settings).
Stack Unit This setting is only visible if you select Stack channels on top of each
other above.
Select a unit from the list. PRTG stacks all channels with this unit 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
recommend that you change them centrally in the root group settings if necessary. To change a setting
for this object only, click under the corresponding setting name to disable the inheritance and to
display its options.
For more information, see section Inheritance of Settings.
Channel List
Which channels the sensor actually shows might depend on the target device, the available
components, and the sensor setup.
Setting Description
Consecutive Sync The number of consecutive synchronization failures

Failures
Downtime In the channel table on the Overview tab, this channel never shows any
values. PRTG uses this channel in graphs and reports to show the
amount of time in which the sensor was in the Down status
688
Setting Description
Is Deleted Source If the source is deleted

§ Up status: No
§ Down status: Yes
Last Sync Attempt The time of the last synchronization attempt
Last Sync Result The result of the last synchronization

This channel is the primary channel by default.
Last Sync Success The time of the last synchronization success
Modified Consecutive The number of modified, consecutive synchronization failures

Sync Failures
Pending Replication The number of pending replication operations

Operations
Scheduled Sync If the scheduled synchronization is disabled

Disabled
§ Up status: No
§ Down status: Yes
More
KNOWLEDGE BASE


How do I monitor Active Directory (AD) replication without domain admin rights?
689
7.8.2 ADO SQL v2 Sensor
The ADO SQL v2 sensor monitors a database via an ActiveX Data Objects (ADO) connection and it
executes a Structured Query Language (SQL) query.
This sensor can monitor any data source that is available via Object Linking and Embedding,
Database (OLE DB) or Open Database Connectivity (ODBC).
ADO SQL v2 Sensor
List 700 .

§ Dutch: ADO SQL v2
§ French: ADO SQL v2
§ German: ADO SQL v2
§ Japanese: ADO SQL v2
§ Portuguese: ADO SQL v2
§ Russian: ADO SQL v2
§ Simplified Chinese: ADO SQL v2
§ Spanish: ADO SQL v2
Remarks
690
Remark Description
SQL query storage § This sensor requires that you store the SQL query in a file on the probe
system. In a cluster, copy the file to every cluster node.
For more information, see the Knowledge Base: Why do I have to

store SQL sensor queries and custom scripts in files on the probe
computer?
system. In a cluster, install it on every cluster node.
does PRTG require?
ODBC connection § If you use an ODBC connection, define the ODBC connection in the
Windows ODBC Connection Manager first. If it is a 64-bit Windows,
define the ODBC connection as an ODBC 32-bit connection.
Lookups § This sensor can use lookups . Select Lookup as Channel #x Unit
697
and define the lookup file in Channel #x Lookup.
Credentials § Define the credentials for database management systems in settings

that are higher in the object hierarchy.
Knowledge Base § Knowledge Base: How to set up the SQL v2 sensors in PRTG? Is there
a guide?
§ Knowledge Base: How can I monitor strings from an SQL database and
show a sensor status depending on it?
§ Knowledge Base: How can I monitor error tables in SQL databases?
§ Knowledge Base: Why do I have to store SQL sensor queries and

custom scripts in files on the probe computer?
probe device.
691
you add the sensor:
§ sqlsensor
Database Specific
Database Specific
Setting Description
Connection String Enter the connection string that this sensor uses to connect to the
database. A connection string can look like this, for example:
Provider=SQLOLEDB.1;Data Source=10.0.0.200\SQLEXPRESS;User
ID=user;Password=userpass;Initial Catalog=Northwind
For ODBC connections, you must enter MSDASQL as provider, for

example Provider=MSDASQL;DSN=_my_odbc_sqlserver.
You can use the placeholders %dbloginuser and %dbloginpassword.
PRTG replaces them with the credentials for database management
systems of the parent device.
692
Data
Sensor Display
Setting Description
SQL Query File Select the SQL query file that includes a valid SQL statement that the
sensor executes on the server with every scanning interval. The list
contains SQL scripts from the \Custom Sensors\sql subfolder of the
PRTG program directory on the probe system. Store your script there. If
you use the script on a cluster probe, you must store the script on all
cluster nodes.
A correct expression in the file could be: SELECT AVG(UnitPrice) FROM
Products. If you want to use transactions, separate the individual steps
with semicolons ";".
Note that with each request, PRTG transfers the full result set, so
use filters and limits in your query.
The demo script Demo Serveruptime.sql is available by default. You
can use it to monitor the uptime of the target server.
See also the Knowledge Base: Why do I have to store SQL sensor
queries and custom scripts in files on the probe computer?
Input Parameter Handling Define if you want to pass a parameter to the SQL query file:
§ Do not use imput parameter (default): Execute the SQL query file
without using variables.
§ Use input parameter: Execute an SQL query file that contains a
variable. Provide the parameter that you want to use in the query below.
Input Parameter This setting is only visible if you select Use input parameter above.
693
Setting Description
Enter the parameter that you want to pass to the SQL query file. This
parameter replaces the variables @prtg, :prtg, or ? in the SQL query,
considering the general rules for SQL variables.
You can also use PRTG placeholders for custom sensors (command-line
parameters) as input parameters, for example, %sensorid or %deviceid.
For more information, see section Custom Sensors.
Provide strings as they are and do not surround them with quotation
marks. PRTG automatically and correctly inserts string parameters
into the query.
Transaction Handling Define if you want to use transactions and if they affect the database
content:
§ Do not use transaction (default): Do not execute transactions.
§ Use transaction and always roll back: The query does not change data
in the database. In the SQL query file, separate the single steps of the
transaction with semicolons.
§ Use transaction and commit on success: The query changes data in
the database. The changes only apply if all execution steps succeed
without any errors. In the SQL query file, separate the single steps of
the transaction with semicolons.
Data Processing Define whether the sensor processes data from the database:
§ Only execute query: Only show information about the number of
affected rows and the execution time of the query. Affected rows are
rows that were changed by the query (for example, created, deleted, or
edited).
§ Count table rows: Execute a SELECT statement and monitor how

many rows of the data table this statement returns.
§ Process data table: Read and analyze the data table. If you select this
option, the sensor counts rows with SELECT statements as well.
DBNull Handling This setting is only visible if you select Process data table for the setting
Data Processing during sensor creation.
Define the sensor behavior if the query returns DBNull:

§ Error: Show the Down status if the query returns DBNull.
§ Number 0: Recognize the result DBNull as a valid value and interpret it

as the number 0.
694
Setting Description
Select Channel Value by This setting is only visible if you select Process data table for the setting
Define how to select the desired cell in the database table:

§ Column number: Determine the channel value by using the value in row
0 of the column whose number you specify in Channel #x Column
Number.
§ Column name: Determine the channel value by using the value in row 0
of the column whose name you specify in Channel #x Column Name.
§ Row number: Determine the channel value by using the value in column
0 of the row whose number you specify in Channel #x Row Number.
§ Key value pair: Determine the channel value by searching in column 0
for the key you specify in Channel #x Key and by returning the value in
column 1 of the same row where the key value was found.
Defining how the desired cell in the database table is selected is
necessary to configure the cells that are used in the channels.
The option you select here also defines the method of how to
optionally determine a value for the sensor message. For more
information, see setting Use Data Table Value in Message.
For an example for channel value selection, see section Monitoring
Databases.
Channel #2 - #10 This setting is only visible if you select Process data table above.
You can define up to 10 channels. You must define at least one channel,
so you see all available settings for Channel #1. Specify how to handle all
other possible channels:
§ Disable: Do not create this channel.
§ Enable: Create this channel.
It is not possible to enable or disable channels after sensor creation.
Channel #x Name This setting is only visible if you select Process data table above.
Enter a name for the channel. Enter a string. The sensor dynamically
generates channels with this name as identifier.
695
Setting Description
Channel #x Column This setting is only visible if you select Process data table for the setting
Number Data Processing during sensor creation and if you select Column number
for the setting Select Channel Value by.
Provide the number of the column to use to determine the channel value
in row 0. Enter an integer.
Name Data Processing during sensor creation and if you select Column name
Provide the name of the column to use to determine the channel value in
row 0. Enter an integer.
Channel #x Row Number This setting is only visible if you select Process data table for the setting
Data Processing during sensor creation and if you select Row number for
the setting Select Channel Value by.
Channel #x Key This setting is only visible if you select Process data table for the setting
Data Processing during sensor creation and if you select Key value pair
Provide the key to search for in column 0 of the data table. The value in
column 1 of the same row where the key value was found to use to
determine the channel value. Enter a string.
Channel #x Mode This setting is only visible if you select Process data table above.
Define how to display the determined value in the channel:

§ Absolute (default): Show the value as the sensor retrieves it from the
data table.
§ Difference: The sensor calculates and shows the difference between the
last and the current value returned from the data table.
This mode is not compatible with the unit Lookup.
This mode only works if the difference between the last and the
current value is positive and increases with each scanning interval.
This mode does not support negative and decreasing values.
§ Absolute (recommended): Show the value as the sensor retrieves it
from the data table.
696
Setting Description
This setting is only visible if you select Process data table above.
Channel #x Unit
Define the unit of the channel value:
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
For more information about the available units, see section Custom
Sensors.
To use lookups with this channel, select Lookup and define the
lookup file in Channel #x Lookup. Do not use Custom if you use
lookups with this sensor.
It is not possible to use the unit Lookup in combination with the
Difference mode. You are not able to create the sensor in this case.
Channel #x Custom Unit This setting is only visible if you select the channel unit Custom above.
Define a unit for the channel value. Enter a string.
697
Setting Description
Channel #x Lookup This setting is only visible if you select the channel unit Lookup above.
Select a lookup file that you want to use with this channel.
Use Data Table Value in This setting is only visible if you select Process data table for the setting
Message Data Processing during sensor creation.
Define if the sensor message shows a value from the data table:
§ Disable: Do not use a custom sensor message.
§ Enable: Define a custom sensor message with a defined value of the

data table. Define the value selection below.
The method of how to determine a value for the sensor message is
defined in the setting Select Channel Value by above.
Message Column This setting is only visible if you select Process data table for the setting
Number Data Processing during sensor creation, if you select Column name for
the setting Select Channel Value by, and if you select Enable above.
Enter the number of a column. The sensor message shows the value in
row 0 of this column. Enter an integer.
Message Column Name This setting is only visible if you select Process data table for the setting
Data Processing during sensor creation, if you select Column name for
Enter the name of a column. The sensor message shows the value in row
0 of this column. Enter a string.
Columns start with index 0.
Message Row Number This setting is only visible if you select Process data table for the setting
Data Processing during sensor creation, if you select Row number for the
setting Select Channel Value by, and if you select Enable above.
0 of this column. Enter the number of a row. The sensor message shows
the value in column 0 of this row. Enter an integer.
Rows start with index 0.
Message Key This setting is only visible if you select Process data table for the setting
Data Processing during sensor creation, if you select Key value pair for
698
Setting Description
Enter a key to search for in column 0 of the data table. The sensor
message shows the value in column 1 of the row where the key was
found. Enter a string.
Message This setting is only visible if you select Enable above.
Define the sensor message. Enter a string. Use the placeholder {0} at the
position where you want to display the value.
Example: The message is {0}
PRTG does not support the number sign (#) in sensor messages. If a
message contains a number sign, PRTG clips the message at this
point.
If Message Changes This setting is only visible if you select Process data table for the setting
Define what the sensor does when its message changes:

§ Ignore (default): Do nothing.
§ Trigger 'change' notification: Send an internal message that indicates a

change.
In combination with a change trigger, you can use this to trigger a
notification if a change occurs.
Result of Sensor [ID].txt, Result of Sensor [ID].Data.txt, and Result of
Sensor [ID].log. This setting is for debugging purposes. PRTG
overwrites these files with each scanning interval.
master node.
Sensor Display
Sensor Display
699
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Affected Rows The number of rows that were addressed by the query (including SELECT
statements if you process data tables)
700
Channel Description
Execution Time The execution time of the entire request (including connection buildup,
query execution, transaction handling, disconnection)
Query Execution Time The execution time of the specified query
SQL Variables
You can use the following variables in the SQL query file to be replaced by an input parameter. This is
useful if you have various SQL sensors with queries that differ in only one parameter.
§ Microsoft SQL, MySQL, PostgreSQL: @prtg
§ Oracle SQL: :prtg
§ ADO SQL: ? (question mark)
@prtg, :prtg, and ? are common SQL query parameters and they are used in a parameterized SQL
query. This means that the query and the parameter are forwarded without any changes to the
database. This leads to some restrictions on the database side. For example, you cannot use variables
as placeholders for table names or as lists in IN operators.
Examples for variables usage:
SELECT * FROM Table WHERE name = @prtg
SELECT @prtg FROM Table
More
KNOWLEDGE BASE
How to set up the SQL v2 sensors in PRTG? Is there a guide?

How can I monitor strings from an SQL database and show a sensor status depending on it?
How can I monitor error tables in SQL databases?

Why do I have to store SQL sensor queries and custom scripts in files on the probe computer?

701
How do I monitor the size of a Microsoft SQL Server database?

702
7.8.3 Application Server Health (Autonomous) Sensor
The Application Server Health (Autonomous) sensor monitors the health of the PRTG application server
and checks various parameters that can affect the quality of the monitoring results.
Application Server Health (Autonomous) Sensor
List 705 .

§ Dutch: Application Server Health (Autonoom)
§ French: État du serveur d’application (autonome)
§ German: Zustand des PRTG Application Servers (Autonom)
§ Japanese: ( )
§ Portuguese: Funcionamento do servidor de aplicativos (autônomo)
703
§ Russian: ( )
§ Simplified Chinese: ( )
§ Spanish: Salud de servidor de aplicaciones (autónomo)
Remarks
Remark Description
Performance impact § This sensor has a very low performance impact.
Limits § This sensor has predefined limits for several metrics.
Sensor creation § PRTG automatically creates this sensor. You cannot add it manually.
New UI and API § This sensor is part of the new UI and API. For more information, see
the Knowledge Base: I want to use the new UI and new API. What do I
need to know?
you add the sensor:
§ appserverhealthsensor
704
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
705
Channel Description
API Requests The number of API requests
Average CPU Utilization The CPU usage of the PRTG application server process (%)
(%)
Core Messages The number of messages that the PRTG application server receives from
the PRTG core server
CPU Utilization of The CPU usage of the PRTG application server garbage collector (%)
Garbage Collector (%)
Dropped API Requests The number of API requests per second that were dropped due to
timeouts
This channel has default limits:
§ Upper error limit: 5
§ Upper warning limit: 1
Free Memory (%) The free system memory of the PRTG application server system (%)
Health The sums of the PRTG application server state as a value between 100%
(healthy) and 0% (unhealthy). Investigate if values are frequently under
100%.
Heap Size (%) The heap size of the memory that the PRTG application server uses (%)
Process Memory Usage The memory usage of the PRTG application server process
Response Time The average response time of the new API
Response Time 95th The 95th percentile of the response time of the new API
Percentile
Routines The number of concurrently running routines in the PRTG application

server
Sessions The number of active user sessions
706
Channel Description
Stack Size (%) The relative stack size of the memory that the PRTG application server
uses (%)
More
KNOWLEDGE BASE
I want to use the new UI and new API. What do I need to know?
707
7.8.4 AWS Alarm v2 Sensor
The AWS Alarm v2 sensor monitors the status of an Amazon Web Services (AWS) alarm by reading its
data from Amazon CloudWatch via the AWS API.
If you use the same Identity and Access Management (IAM) policy that you use for this sensor, you
must update it. For more information, see the Knowledge Base: How do I set permissions for the
Amazon Web Services (AWS) API key to use certain sensors in PRTG?
If you monitor an AWS alarm that is based on a metric math expression, this sensor does not
create an additional channel that monitors the math expression.
AWS Alarm v2 Sensor
For a list of regions that this sensor supports, see section Supported AWS Regions and Their
Codes.
List 712 .

§ Dutch: AWS Alarm v2
§ French: Alarme AWS v2
§ German: AWS Alarm v2
§ Japanese: AWS Alarm v2
§ Portuguese: Alarme da AWS v2
§ Russian: AWS v2
708
§ Simplified Chinese: AWS v2
§ Spanish: Alarma AWS v2
Remarks
Remark Description
Permissions for the AWS § This sensor requires permissions for the AWS API key.
API key
For more information, see the Knowledge Base: How do I set
permissions for the Amazon Web Services (AWS) API key to use
Credentials § This sensor requires credentials for AWS.
Alarms § This sensor supports MetricAlarm and CompositeAlarm.
Performance impact § This sensor has a low performance impact.
channels.
Pricing § Amazon can charge you based on the number of API calls that the
sensor sends to the Amazon servers. For more information, see
Amazon CloudWatch Pricing – Amazon Web Services (AWS).
Add Sensor dialog § It can take up to several minutes before objects appear in the Add
Sensor dialog.
Scanning interval § This sensor has a fixed minimum scanning interval for performance
reasons. You cannot use a shorter scanning interval. Consequently,
shorter scanning intervals in the Monitoring settings are not available for
this sensor.
§ The minimum scanning interval of this sensor is 1 minute.
§ The recommended scanning interval of this sensor is 5 minutes.
709
you add the sensor:
§ alarm
§ aws
§ cloudwatch
§ cloudwatchsensor
AWS Alarm Specific
AWS Alarm Specific
Setting Description
Name The name of the AWS alarm that this sensor monitors.
Type The type of the AWS alarm that this sensor monitors.
Description The description of the AWS alarm that this sensor monitors.
Region The region in which the AWS alarm that this sensor monitors occurs.
710
Setting Description
For a list of regions that this sensor supports, see section Supported
AWS Regions and Their Codes.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
711
Debug Options
Debug Options
Setting Description
of the PRTG data directory on the probe system. The file name is
Result of Sensor [ID].log. This setting is for debugging purposes. PRTG
overwrites this file with each scanning interval.
This option is not available when the sensor runs on the hosted probe
of a PRTG Hosted Monitor instance.
master node.
Inherited Settings
Channel List
Channel Description
Alarm State The alarm status

712
Channel Description
[Metric] The metric on which the alarm is based
More
KNOWLEDGE BASE
PRTG?

713
7.8.5 AWS Cost Sensor
The AWS Cost sensor monitors the cost of an Amazon Web Services (AWS) account by reading its
data from the AWS Cost Explorer API.
AWS Cost Sensor
List 719 .

§ Dutch: AWS Kosten
§ French: Coût AWS
§ German: AWS Kosten
§ Japanese: AWS Cost
§ Portuguese: Custo da AWS
§ Russian: AWS
714
§ Simplified Chinese: AWS
§ Spanish: Costo AWS
Remarks
Remark Description
AWS Cost Explorer § This sensor requires that you activate the AWS Cost Explorer in your
AWS account.
IAM User and Role § This sensor requires that you enable IAM User and Role Access to
Access to Billing Billing Information in your AWS account.
Information
API key
§ The AWS API key requires the following permissions to query data
from the AWS API:
ú "ce:GetCostAndUsage"
ú "ce:GetCostForecast"
ú "ce:GetDimensionValues"
ú "ce:GetCostAndUsageWithResources"
ú "ce:GetUsageForecast"

Sensor creation § After sensor creation, the first data is available after 24 hours. Forecast
data is available after a few days.
this sensor.
§ The minimum scanning interval of this sensor is 1 hour.
715
Remark Description
§ The recommended scanning interval of this sensor is 6 hours. You can

use a shorter scanning interval but it could create extra costs.
Pricing § Amazon charges you for each API call that this sensor sends to the
Amazon servers. For more information, see AWS Cost Management
Pricing | Amazon Simple Storage Service.
Sensor creation § You can only set up this sensor for one AWS account per PRTG
installation.
Knowledge Base § Knowledge Base: What settings do I have to define in my AWS

account to set up the AWS Cost sensor?
§ Knowledge Base: How do I set permissions for the Amazon Web
Services (AWS) API key to use certain sensors in PRTG?
you add the sensor:
§ aws
§ awscost
§ cost
716
AWS Cost Specific
AWS Cost Specific
Setting Description
Additional Cost Types PRTG creates two default channels for blended monthly and yearly cost.
If you select this option, you can select additional cost types for which
PRTG creates additional channels.
§ Enable
§ Disable
Select Additional Cost This setting is only visible if you select Enable above.
Types
Select additional cost types:
§ Amortized cost
§ Net amortized cost
§ Unblended cost
§ Net unblended cost
PRTG creates two overview channels (monthly and yearly) for every
additional cost type that you select.
Additional Forecast PRTG does not automatically create additional forecast channels. If you
Types select this option, you can select additional forecast types to create
additional forecast channels:
§ Enable
§ Disable
Select Additional This setting is only visible if you select Enable above.
Forecast Types
Select additional forecast types:
§ Blended cost (default)
§ Amortized cost
§ Net amortized cost
§ Unblended cost
717
Setting Description
§ Net unblended cost
PRTG creates two overview channels (monthly and yearly) for every
additional forecast type that you select. Every forecast type that you
select creates additional fees. Deselect a forecast type if you no longer
want the according channels to create additional fees. You can still see
the channels, but they do not receive data anymore.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
718
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Amortized Monthly The amortized cost per month
Amortized Yearly The amortized cost per year
719
Channel Description
Forecast Amortized The forecast for amortized cost per month

Monthly
Forecast Amortized The forecast for amortized cost per year

Yearly
Forecast Monthly The forecast for cost per month
Forecast Net Amortized The forecast for net amortized cost per month
Monthly
Forecast Net Amortized The forecast for net amortized cost per year
Yearly
Forecast Net Unblended The forecast for net unblended cost per month
Monthly
Forecast Net Unblended The forecast for net unblended cost per year
Yearly
Forecast Unblended The forecast for unblended cost per month

Monthly
Forecast Unblended The forecast for unblended cost per year

Yearly
Forecast Yearly The forecast for cost per year
Monthly Cost The monthly cost

Net Amortized Monthly The net amortized cost per month
Net Amortized Yearly The net amortized cost per year
Net Unblended Monthly The net unblended cost per month
Net Unblended Yearly The net unblended cost per year
720
Channel Description
Unblended Monthly The unblended cost per month
Unblended Yearly The unblended cost per year
Yearly Cost The cost per year
More
KNOWLEDGE BASE
What settings do I have to define in my AWS account to set up the AWS Cost sensor?
PRTG?

721
7.8.6 AWS EBS v2 Sensor
The AWS EBS v2 sensor monitors the performance of an Amazon Web Services (AWS) Elastic Block
Store (EBS) volume by reading its data from Amazon CloudWatch via the AWS API.
AWS EBS v2 Sensor
For a list of metrics that this sensor supports, see section Supported Metrics 726 .
For a list of dimensions that this sensor supports, see section Supported Dimensions 727 .
Codes.
List 727 .
722
§ Dutch: AWS EBS v2
§ French: AWS EBS v2
§ German: AWS EBS v2
§ Japanese: AWS EBS v2
§ Portuguese: AWS EBS v2
§ Russian: AWS EBS v2
§ Simplified Chinese: AWS EBS v2
§ Spanish: AWS EBS v2
Remarks
Remark Description
API key
channels.
Sensor dialog.
this sensor.
723
Remark Description
you add the sensor:
§ aws
§ cloudwatch
§ cloudwatchsensor
§ ebs
AWS EBS Specific
AWS EBS Specific
Setting Description
ID The ID of the AWS EBS volume that this sensor monitors.
Name The name of the AWS EBS volume that this sensor monitors.
724
Setting Description
Region The region in which the AWS EBS instance runs.
Sensor Display
Sensor Display
Setting Description

other above.
procedure to do so.
725
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Supported Metrics
The AWS EBS v2 sensor supports the following metrics:
§ BurstBalance (Average)
§ VolumeIdleTime (Sum)
§ VolumeQueueLength (Average)
§ VolumeReadBytes (Sum)
§ VolumeReadOps (Sum)
§ VolumeTotalReadTime (Average)
§ VolumeTotalWriteTime (Average)
§ VolumeWriteBytes (Sum)
726
§ VolumeWriteOps (Sum)
Supported Dimensions
The AWS EBS v2 sensor supports the following dimensions:
§ Volume
Channel List
Channel Description
Average Queue Length The average queue lengths
Average Read Latency The average read latency
Average Write Latency The average write latency
Burst Balance The burst balance
Read Bandwidth The read bandwidth
Read Throughput The read throughput in IOPS
Time Spent Idle The time spent idle (%)
Volume State The volume status

§ Up status: Available, In Use
§ Warning status: Creating, Deleting, Deleted
§ Down status: Error
§ Unknown status: Not Set
Write Bandwidth The write bandwidth
Write Throughput The write throughput in IOPS
727
More
KNOWLEDGE BASE
PRTG?
728
7.8.7 AWS EC2 v2 Sensor
The AWS EC2 v2 sensor monitors the performance of an Amazon Web Services (AWS) Elastic
Compute Cloud (EC2) instance by reading its data from Amazon CloudWatch via the AWS API.
AWS EC2 v2 Sensor
Codes.
List 734 .
729
§ Dutch: AWS EC2 v2
§ French: AWS EC2 v2
§ German: AWS EC2 v2
§ Japanese: AWS EC2 v2
§ Portuguese: AWS EC2 v2
§ Russian: AWS EC2 v2
§ Simplified Chinese: AWS EC2 v2
§ Spanish: AWS EC2 v2
Remarks
Remark Description
API key
channels.
Sensor dialog.
this sensor.
§ The minimum scanning interval of this sensor is 5 minutes.
730
Remark Description
you add the sensor:
§ aws
§ cloudwatch
§ cloudwatchsensor
§ ec2
AWS EC2 Specific
AWS EC2 Specific
Setting Description
ID The ID of the AWS EC2 instance that this sensor monitors.
Name The name of the AWS EC2 instance that this sensor monitors.
731
Setting Description
Region The region in which the AWS EC2 instance runs.
Sensor Display
Sensor Display
Setting Description

other above.
procedure to do so.
732
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Supported Metrics
The AWS EC2 v2 sensor supports the following metrics:
§ CPUCreditBalance (Average)
§ CPUCreditUsage (Average)
§ CPUUtilization (Average)
§ DiskReadBytes (Average)
§ DiskReadOps (Average)
§ DiskWriteBytes (Average)
§ DiskWriteOps (Average)
§ NetworkIn (Average)
733
§ NetworkOut (Average)
§ StatusCheckFailed (Average)
§ StatusCheckFailed_Instance (Average)
§ StatusCheckFailed_System (Average)
The AWS EC2 v2 sensor supports the following dimensions:
§ Instance
Channel List
Channel Description
CPU Credit Balance The CPU credit balance
CPU Credit Usage The CPU credit usage
CPU Utilization The CPU usage

Disk Read The disk read speed
Disk Read Ops The number of disk read operations
Disk Write The disk write speed
Disk Write Ops The number of disk write operations
Instance Status The AWS EC2 instance status

§ Up status: Passed
§ Down status: Failed
Network In The incoming network load
734
Channel Description
Network Out The outgoing network load
System Status The AWS EC2 system status

§ Up status: Passed
More
KNOWLEDGE BASE
PRTG?

735
7.8.8 AWS ELB v2 Sensor
The AWS ELB v2 sensor monitors the performance of an Amazon Web Services (AWS) Elastic Load
Balancing (ELB) load balancer by reading its data from Amazon CloudWatch via the AWS API.
AWS ELB v2 Sensor
Codes.
List 741 .
736
§ Dutch: AWS ELB v2
§ French: AWS ELB v2
§ German: AWS ELB v2
§ Japanese: AWS ELB v2
§ Portuguese: AWS ELB v2
§ Russian: AWS ELB v2
§ Simplified Chinese: AWS ELB v2
§ Spanish: AWS ELB v2
Remarks
Remark Description
API key
Load balancers § This sensor supports Application Load Balancer and Network Load
Balancer.
Sensor dialog.
this sensor.
737
Remark Description
you add the sensor:
§ aws
§ cloudwatch
§ cloudwatchsensor
§ elb
AWS ELB Specific
AWS ELB Specific
Setting Description
ID The ID of the AWS ELB load balancer that this sensor monitors.
738
Setting Description
Name The name of the AWS ELB load balancer that this sensor monitors.
Type The type of the AWS ELB load balancer that this sensor monitors.
Region The region in which the AWS ELB load balancer runs.
Sensor Display
Sensor Display
Setting Description



other above.
procedure to do so.
739
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Supported Metrics
The AWS ELB v2 sensor supports the following metrics:
§ ActiveConnectionCount (Sum)
§ ActiveFlowCount (Average)
§ ConsumedLCUs (Sum)
§ HealthyHostCount (Minimum)
§ HTTPCode_ELB_4XX_Count (Sum)
§ HTTPCode_ELB_5XX_Count (Sum)
§ HTTPCode_Target_4XX_Count (Sum)
§ HTTPCode_Target_5XX_Count (Sum)
740
§ NewConnectionCount (Sum)
§ NewFlowCount (Sum)
§ PeakBytesPerSecond (Maximum)
§ RuleEvaluations (Sum)
§ TargetConnectionErrorCount (Sum)
§ TargetResponseTime (Average)
§ TCP_Client_Reset_Count (Sum)
§ TCP_ELB_Reset_Count (Sum)
§ TCP_Target_Reset_Count (Sum)
§ UnhealthyHostCount (Maximum)
The AWS ELB v2 sensor supports the following dimensions:
§ Load Balancer
Channel List
Channel Description
Active Connection Count The number of concurrent active TCP connections
Active Flow Count The number of concurrent flows
Consumed LCU's The number of LCU used by the load balancer
ELB 4XX Count The number of HTTP 4XX client error codes
ELB 5XX Count The number of HTTP 5XX server error codes
Healthy Host Count The number of targets that are considered healthy
New Connection Count The number of new TCP connections
741
Channel Description
New Flow Count The number of new flows
Peak Bytes The highest average throughput
Processed Bytes The number of bytes processed
Rule Evaluations The number of rules processed
Target 4XX Count The number of HTTP response codes generated by the targets
Target 5XX Count The number of HTTP response codes generated by the targets
Target Connection Error The number of connections that were not successfully established
Count
Target Response Time The response time of the target
TCP Client Reset Count The number of RST packets sent from a client to a target
TCP ELB Reset Count The number of RST packets generated by the load balancer
TCP Target Reset Count The number of RST packets sent from a target to a client
Unhealthy Host Count The number of targets that are considered unhealthy
More
KNOWLEDGE BASE
PRTG?

742
7.8.9 AWS RDS v2 Sensor
The AWS RDS v2 sensor monitors the performance of a Amazon Web Services (AWS) Relational
Database Service (RDS) database by reading its data from Amazon CloudWatch via the AWS API.
AWS RDS v2 Sensor
Codes.
743
List 748 .

§ Dutch: AWS RDS v2
§ French: AWS RDS v2
§ German: AWS RDS v2
§ Japanese: AWS RDS v2
§ Portuguese: AWS RDS v2
§ Russian: AWS RDS v2
§ Simplified Chinese: AWS RDS v2
§ Spanish: AWS RDS v2
Remarks
Remark Description
API key
Sensor dialog.
this sensor.
§ The minimum scanning interval of this sensor is 5 minutes.
744
Remark Description
you add the sensor:
§ aws
§ cloudwatch
§ cloudwatchsensor
§ rds
AWS RDS Specific
AWS RDS Specific
Setting Description
Database Identifier The database identifier of the AWS RDS database that this sensor
monitors.
745
Setting Description
Engine The engine family name of the AWS RDS database that this sensor
monitors.
Region The region in which the AWS RDS instance runs.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
746
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Supported Metrics
The AWS RDS v2 sensor supports the following metrics:
§ BinLogDiskUsage (MB)
§ CPUUtilization (Average)
§ CPUCreditUsage (Average)
§ CPUCreditBalance (Average)
§ DatabaseConnections (Count)
§ DiskQueueDepth (Count)
§ FreeableMemory (MB)
§ FreeStorageSpace (MB)
747
§ NetworkReceiveThroughput (Byte/Second)
§ NetworkTransmitThroughput (Byte/Second)
§ ReadIOPS (Count/Second)
§ ReadLatency (Milliseconds)
§ ReadThroughput (Byte/Second)
§ ReplicaLag (Milliseconds)
§ SwapUsage (MB)
§ WriteIOPS (Count/Second)
§ WriteLatency (Milliseconds)
§ WriteThroughput (Byte/Second)
The AWS RDS v2 sensor supports the following dimensions:
§ DBInstanceIdentifier
Channel List
Channel Description
Bin Log Disk Usage The bin log disk usage
CPU Credit Balance The CPU credit balance
CPU Credit Usage The CPU credit usage

Database Connections The average number of database connections in use
Disk Queue Depth The number of outstanding read and write requests waiting to access the
disk
748
Channel Description
Free Storage Space The amount of available storage space
Freeable Memory The freeable memory
Network Receive The incoming (receive) network traffic

Throughput
Network Transmit The outgoing (transmit) network traffic

Throughput
Read IOPS The average number of disk read IOPS
Read Latency The read latency
Read Throughput The average number of bytes read from disk
Replica Lag The amount of time a read replica DB instance lags behind the source DB
instance
Swap Usage The swap usage
Write IOPS The average number of disk write IOPS
Write Latency The average amount of time taken per disk read and write operation
Write Throughput The number of disk write operations
More
KNOWLEDGE BASE
PRTG?

749
7.8.10 Beckhoff IPC System Health Sensor
The Beckhoff IPC System Health sensor monitors the system health of a Beckhoff Industrial PC (IPC) via
OPC Unified Architecture (OPC UA).
Beckhoff IPC System Health Sensor
List 753 .

§ Dutch: Beckhoff IPC Systeemstatus
§ French: Beckhoff IPC état du système
§ German: Beckhoff IPC Systemzustand
§ Japanese: Beckhoff IPC
§ Portuguese: Saúde do sistema Beckhoff IPC
§ Russian: Beckhoff IPC

§ Simplified Chinese: Beckhoff IPC
§ Spanish: Salud del sistema Beckhoff IPC
750
Remarks
Remark Description
Valid port § This sensor requires a valid port.
Credentials § This sensor requires credentials for OPC UA in the settings of the
parent device.
channels.
Multi-platform probe § You can add this sensor to a multi-platform probe.
you add the sensor:
§ opcua
751
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
752
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Available Memory The available memory
Available Memory % The available memory (%)
CPU % The CPU load (%)
CPU Temperature The CPU temperature
Mainboard Temperature The mainboard temperature
753
Channel Description
RAID Controller Status The RAID controller status

§ Up status: Good
§ Warning status: Offline
§ Unknown status: Power Off
More
KNOWLEDGE BASE

754
7.8.11 Business Process Sensor
The Business Process sensor gives you a summarized status of entire business processes while
monitoring several process components. This means that you can create a customized sensor with
channels based on data from other sensors ("source sensors") that are specific to your network.
If you want to process values from other sensors and you want to perform calculations with these
values, for example, use the Sensor Factory 1768 sensor.
Business Process Sensor
List 762 .

§ Dutch: Bedrijfs Proces
§ French: Processus métier
§ German: Business Process
§ Japanese:
§ Portuguese: Processo empresarial
§ Russian: -
755
§ Spanish: Proceso empresarial
Remarks
Remark Description
Channels § This sensor does not officially support more than 50 channels.
Performance impact § This sensor has a medium performance impact.
channels.
Knowledge Base § Knowledge Base: How does the Business Process sensor calculate
summarized sensor states?
you add the sensor:
§ businessprocesssensor
§ factorysensor
756
Business Process Specific Settings
Business Process Specific Settings
Setting Description
Channel Name Enter a name for the channel. To add a new channel to this sensor, click
the Enter Channel Name field, enter a name for the channel, and confirm
with the Enter or Tab key.
It might take several sensor scans until new channel names or
changes to channel names become visible.
Error Threshold % Set a percentage limit to define when the channel displays the Down
status. Enter an integer. The default value is 50%.
This value depends on how many objects you feed into a Business
Process channel.
If the percentage of source objects in the "up" condition is less than the
error threshold defines, the channel and the Global State channel of the
Business Process sensor show the Down status.
PRTG maps the following sensor states to the "up" condition for a
Business Process channel:
§ Up
§ Warning
§ Unusual
§ Down (Partial)
757
Setting Description
PRTG maps all other sensor states to the "down" condition (see Up
and Down Conditions 759 ).
For example, if you define 4 source sensors for a channel, an error
threshold of 50% means that 3 source sensors must be in the "down"
condition to set this channel to the Down status. So, 50% means that
more than half of the source sensors must not be in the "up" condition to
set the sensor to the Down status.
For more information, an illustration of the business process
mechanisms, and some use cases for the Business Process sensor,
see the table below 759 and the Knowledge Base: How can I use the
Business Process sensor?
Warning Threshold % Set a percentage limit to define when the channel displays the Warning
status. Enter an integer. The default value is 75%.
This value depends on how many objects you feed into a Business
Process channel.
If the percentage of source objects in the "up" condition is less than the
threshold defines, the channel and the Global State channel of the
Business Process sensor show the Warning status.
PRTG maps the following sensor states to the "up" condition for a
Business Process channel:
§ Up
§ Warning
§ Unusual
§ Down (Partial)
PRTG maps all other sensor states to the "down" condition (see Up
and Down Conditions 759 ).
For example, if you define 4 source sensors for a channel, a warning
threshold of 75% means that all 4 source sensors must be in the "down"
condition to set this channel to the Warning status. So, 75% means that
more than three out of four of the source sensors must not be in the "up"
condition to set the sensor to the Warning status.
For more information, an illustration of the business process
mechanisms, and some use cases for the Business Process sensor,
see the table below 759 and the Knowledge Base: How can I use the
Business Process sensor?
Objects Enter the objects that you want to have in a channel by clicking . This
way, you can select the desired objects from the device tree with the
object selector. You can also start to type the object's ID, name, or a tag.
PRTG then suggests the possible objects.
758
Setting Description
You can add sensors, devices, groups, and probes to a channel. Each
object you add is weighted equally, no matter if it is a single sensor or a
device with many sensors. To give more weight to a specific object, add it
several times. For example, add the object twice to give double weight to
it, add it three times to give it triple weight.
A probe, group, or device is in the "up" condition as long as it

does not contain any sensors in the "down" condition .
Up and Down Conditions

The Business Process "up" and "down" conditions are different from the normal Up and Down
sensor states. This is necessary for the Business Process sensor to calculate summarized states and
to show a calculated result for an entire business process. This table illustrates which sensor status
leads to which Business Process condition.
The Relation Between Object States And Business Process Conditions
Channel Object Business Process Reason: Why does a specific sensor status correspond to
Status Condition a specific Business Process condition?
Up Up The monitored object works, so everything is fine.
Up The sensor might show a warning, but the monitored object

Warning
still works.
Down Up This status is available in a cluster and is displayed if at

(Partial) least one cluster node reports the sensor as in the Up
status and at least one cluster node reports it as in the
Down status. With at least one Up report, the monitored
object is supposed to be working and meets the Business
Process "up" condition.
Up The sensor might show unusual values, but the monitored

Unusual
object works.
Up The sensor is still waiting for more monitoring data to

Collecting
definitely decide on the sensor status, but so far the
monitored object works. This PRTG internal status is
visualized as the Unknown status in the PRTG web
interface.
Dow The monitored object does not work.

Down
n
759
Channel Object Business Process Reason: Why does a specific sensor status correspond to
Status Condition a specific Business Process condition?
Dow The sensor does not know if the monitored object works, for
Unknown
n example because it has not yet received any data or
because it has not received any data for a certain amount of
time.
Dow The sensor has not yet received any monitoring data from
None
n the monitored object. This PRTG internal status is
visualized as the Unknown status in the PRTG web
interface.
Dow The monitored object does not work and monitoring has
Paused
n been paused, for example actively by the user, by
inheritance, or by schedules. It might be convenient to
exclude regularly or frequently paused objects from your
business process monitoring, so you do not give more
weight than necessary to a Business Process "down"
condition because of issues you already know about.
Dow The monitored object does not work and someone already
Down
n knows.
(Acknowledged)
If you encounter issues with your Business Process sensor and want to contact the Paessler
support team, send us your exact configuration. Click in the upper-right corner of the Business
Process Specific Settings table to copy your configuration:
The Business Process Sensor Configuration Clipboard
760
A window opens that contains your configuration. Copy the highlighted text and paste it into the support
form to send it to the Paessler support team.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
761
Channel List
Channel Description
[Channel] The summarized status of the objects contained in each channel

according to the individually defined error and warning thresholds
§ Up status: Up
§ Warning status: Warning
§ Down status: Down
§ Unknown status: Inactive
The Business Process sensor never shows values in the Downtime
channel because they cannot be calculated for this sensor.
Global State The overall and summarized status of all channels in the Global State
channel
§ Up status: Up
§ Unknown status: Inactive
More
KNOWLEDGE BASE
How does the Business Process sensor calculate summarized sensor states?

How can I use the Business Process sensor?

How can I avoid numerous notifications for branch offices?

762
7.8.12 Cisco IP SLA Sensor
The Cisco IP SLA sensor monitors Voice over IP (VoIP) network parameters using IP service level
agreements (SLA) from Cisco via the Simple Network Management Protocol (SNMP).
Cisco IP SLA Sensor
List 767 .

§ Dutch: Cisco IP SLA
§ French: Cisco IP SLA
§ German: Cisco IP SLA
§ Japanese: Cisco IP SLA
763
§ Portuguese: Cisco IP SLA
§ Russian: Cisco IP SLA
§ Simplified Chinese: Cisco IP SLA
§ Spanish: Cisco IP SLA
Remarks
Remark Description
IPv4 § This sensor only supports IPv4.
channels.
Object identifiers (OID) § If the object identifiers (OID) that this sensor uses are not available on
the target device, the sensor shows the error message: No such object
(SNMP error # 222). If this occurs, open the SNMP Compatibility
Options setting of the parent device or group and set the Request Mode
to Use single get.
Sensor creation § If there is a very large number of IP SLAs available during sensor
creation, we recommend that you limit the result set by using the Start
Interface Index and End Interface Index options in the SNMP
Compatibility Options setting of the parent device or group.
you add the sensor:
§ ipslasensor
764
IP SLA Specific
IP SLA Specific
Setting Description
ID
The ID of the SLA that this sensor monitors.

This sensor can support the following operations with the specified type
IDs:
§ echo (1)
§ pathEcho (2)
§ fileIO (3)
§ script (4)
§ udpEcho (5)
§ tcpConnect (6)
§ http (7)
§ dns (8)
§ jitter (9)
§ dlsw (10)
§ dhcp (11)
§ ftp (12)
§ icmp-jitter (16)
§ path-jitter (23)
765
Setting Description
The numbers are the IDs of the SLA types as reported by the target
device. PRTG translates them into the corresponding strings. These
IDs are independent of the IDs that you see in the Add Sensor dialog. If
the target device returns other values, this sensor shows an error
message that says that it cannot find the type.
Packet loss values are summarized but have no explicit channel for
source-destination or destination-source values.
Type The type of the SLA that this sensor monitors.
Name (Tag) The name of the SLA that this sensor monitors.
Owner The owner of the SLA that this sensor monitors.
Frequency The frequency of the SLA that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


766
Setting Description
other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Avg. Jitter The average jitter
Avg. Jitter Destination - The average jitter between destination and source
Source
Avg. Jitter Source - The average jitter between source and destination
Destination
Avg. Latency Destination The average latency between destination and source
- Source
Avg. Latency Source - The average latency between source and destination
Destination
Average Round Trip Time The average RTT

(RTT)
767
Channel Description
ICPIF The ICPIF
Late Packets The number of late packets
Max. Latency The maximum latency between destination and source

Destination - Source
Max. Latency Source - The maximum latency between source and destination
Destination
Max. RTT The maximum RTT
Min. Latency Destination The minimum latency between destination and source
- Source
Min. Latency Source - The minimum latency between source and destination
Destination
Min. RTT The minimum RTT
MOS The MOS
Packets Lost The number of lost packets
Packets Lost % The number of lost packets (%)
Packets Out of The number of out-of-sequence packets

Sequence
More
KNOWLEDGE BASE

768
7.8.13 Cisco Meraki License Sensor
The Cisco Meraki License sensor monitors Meraki licenses of an organization via the Cisco Meraki
Dashboard API.
Cisco Meraki License Sensor
List 773 .

§ Dutch: Cisco Meraki Licentie
§ French: Cisco Meraki licence
§ German: Cisco Meraki Lizenz
§ Japanese: Cisco Meraki
§ Portuguese: Licença da Cisco Meraki
§ Russian: Cisco Meraki

§ Simplified Chinese: Cisco Meraki
§ Spanish: Licencia Cisco Meraki
Remarks
769
Remark Description
Enabled organization API § This sensor requires that you enable the access of an organization to
access the Cisco Meraki Dashboard API.
§ If the API access for an organization is disabled, you must enable it
manually. For more information, see Cisco Meraki Dashboard API:
Enable API Access.
API key § This sensor requires an API key with Cisco Meraki Dashboard API
permissions.
The API key that this sensor uses must inherit the permissions of a
Cisco Meraki Dashboard Administrator account with at least Read-
only admin permissions.
The API key inherits the permissions of the Cisco Meraki Dashboard
Administrator account that was used to generate the API key.
Credentials § This sensor requires credentials for Cisco Meraki.
Scanning interval § The minimum scanning interval of this sensor is 10 seconds.
§ The recommended scanning interval of this sensor is 6 hours.
you add the sensor:
770
§ cisco
§ license
§ meraki
Cisco Meraki Specific
Setting Description
Organization The name of the organization that the monitored licenses belong to.
Sensor Display
Sensor Display
Setting Description


771
Setting Description
other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
772
Channel List
Channel Description
Days to Expiration The days to expiration

§ Lower error limit: 30 days
§ Lower warning limit: 90 days
License Count The number of licenses
License Model The license model of the monitored license

§ Up status: Co-Termination, Per-Device
§ Warning status: Unknown
More
KNOWLEDGE BASE

773
7.8.14 Cisco Meraki Network Health Sensor
The Cisco Meraki Network Health sensor monitors the health of Cisco Meraki network devices via the
Cisco Meraki Netw ork Health Sensor
List 778 .

§ Dutch: Cisco Meraki Netwerk Status
§ French: Cisco Meraki état du réseau
§ German: Cisco Meraki Netzwerkzustand
§ Japanese: Cisco Meraki
774
§ Portuguese: Cisco Meraki Network Health
§ Russian: Cisco Meraki

§ Simplified Chinese: Cisco Meraki
§ Spanish: Salud de la red Cisco Meraki
Remarks
Remark Description
Enabled organization API § This sensor requires that you enable the access of an organization to
access the Cisco Meraki Dashboard API.
§ If the API access for an organization is disabled, you must enable it
manually. For more information, see Cisco Meraki Dashboard API:
Enable API Access.
Credentials § This sensor requires credentials for Cisco Meraki.
you add the sensor:
§ cisco
775
§ meraki
Setting Description
Network The name of the network that this sensor monitors.
Organization The name of the organization that the monitored network belongs to.
Sensor Display
Sensor Display
Setting Description


776
Setting Description
other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
777
Channel List
Channel Description
IOT "Alerting" IOT devices in alerting status
IOT "Dormant" IOT devices in dormant status
IOT "Offline" IOT devices in offline status
IOT "Online" IOT devices in online status
MR "Alerting" Meraki Radios (MR) devices in alerting status
MR "Dormant" MR devices in dormant status
MR "Offline" MR devices in offline status
MR "Online" MR devices in online status
MS "Alerting" Meraki Switching (MS) devices in alerting status
MS "Dormant" MS devices in dormant status
MS "Offline" MS devices in offline status
MS "Online" MS devices in online status
MX "Alerting" Meraki Security (MX) devices in alerting status
MX "Dormant" MX devices in dormant status
MX "Offline" MX devices in offline status
MX "Online" MX devices in online status
Uplinks "Active" Uplinks in active status
778
Channel Description
Uplinks "Failed" Uplinks in failed status
Uplinks "Not Connected" Uplinks in not connected status
Uplinks "Ready" Uplinks in ready status
More
KNOWLEDGE BASE

779
7.8.15 Citrix XenServer Host Sensor
The Citrix XenServer Host sensor monitors a Xen host server via HTTP.
Citrix XenServer Host Sensor
List 784 .

§ Dutch: Citrix XenServer Host
§ French: Citrix XenServer serveur hôte
§ German: Citrix XenServer Host
§ Japanese: Citrix XenServer
§ Portuguese: Host Citrix XenServer
§ Russian: Citrix XenServer

§ Simplified Chinese: Citrix XenServer
780
§ Spanish: Host Citrix XenServer
Remarks
Remark Description
does PRTG require?
Parent device § This sensor requires that the parent device is a Citrix XenServer as of
version 5.0.
§ This sensor requires that the parent device represents one host server
of your XenServer pool.
Credentials § This sensor requires credentials for VMware/XenServer.
TLS 1.2 § This sensor does not fully support Transport Layer Security (TLS) 1.2
connections. You cannot add it to XenServers with the security protocol
setting "TLS 1.2 only".
Add Sensor dialog § PRTG also includes hosts that do not run in the Add Sensor dialog.
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 VMs or host servers, create
respective sensors on a device that represents one host server of your pool. Internal processes make
sure that monitoring takes place and continues independently from the physical host.
In the device tree, the sensors for VMs always remain on the host you originally created them on,
also if they are currently running on a different host.
781
you add the sensor:
§ xenhostsensor
Host Settings
Host Settings
Setting Description
UUID The universally unique identifier (UUID) of the host that this sensor
monitors.
PRTG shows this value for reference purposes only. We strongly

recommend that you only change it if the Paessler support team
explicitly asks you to do so. Wrong usage can result in incorrect
monitoring data.
Name The name of the host that this sensor monitors.
782
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

783
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
CPU [Value] Usage The CPU usage

Load Average The load average amount
VMs Running The number of running VMs
Total Memory Free The total memory available
784
Channel Description
Total Memory Used The total memory used
More
KNOWLEDGE BASE


Does PRTG impair my Citrix environment?

785
7.8.16 Citrix XenServer Virtual Machine Sensor
The Citrix XenServer Virtual Machine sensor monitors a virtual machine (VM) on a XenServer via HTTP.
Citrix XenServer Virtual Machine Sensor
List 790 .

§ Dutch: Citrix XenServer Virtuele Machine
§ French: Citrix XenServer machine virtuelle
§ German: Citrix XenServer Virtuelle Maschine
§ Japanese: Citrix XenServer
§ Portuguese: Máquina virtual Citrix XenServer
§ Russian: Citrix XenServer

§ Simplified Chinese: Citrix XenServer
§ Spanish: Máquina virtual Citrix XenServer
Remarks
786
Remark Description

does PRTG require?
Parent device § This sensor requires that the parent device is a Citrix XenServer as of
version 5.0.
§ This sensor requires that the parent device represents one host server
of your XenServer pool.
Credentials § This sensor requires credentials for VMware/XenServer.
TLS 1.2 § This sensor does not fully support Transport Layer Security (TLS) 1.2
connections. You cannot add it to XenServers with the security protocol
setting "TLS 1.2 only".
Add Sensor dialog § PRTG requests a full list of all VMs that are configured on the Citrix
XenServer, including VMs that do not run. Therefore, it might take a few
seconds before the Add Sensor dialog loads.
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 VMs or host servers, create
respective sensors on a device that represents one host server of your pool. Internal processes make
sure that monitoring takes place and continues independently from the physical host.
In the device tree, the sensors for VMs always remain on the host you originally created them on,
also if they are currently running on a different host.
787
you add the sensor:
§ xenvmsensor
Virtual Machine Settings
Setting Description
UUID The universally unique identifier (UUID) of the VM that this sensor
monitors.

monitoring data.
Name The name of the VM that this sensor monitors.
788
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

789
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
CPU [Value] Usage The CPU usage

Memory Available The available memory
Memory Used The used memory
VM Balloon Driver Target The balloon driver target size
790
More
KNOWLEDGE BASE


791
7.8.17 Cloud HTTP v2 Sensor
The Cloud HTTP v2 sensor monitors the loading time of a web server via HTTP from different locations
worldwide via the PRTG Cloud. The locations are distributed among four continents around the globe.
Cloud HTTP v2 Sensor
List 798 .

§ Dutch: Cloud HTTP v2
§ French: Cloud HTTP v2
§ German: Cloud HTTP v2
§ Japanese: HTTP v2
§ Portuguese: Cloud HTTP v2
§ Russian: Cloud HTTP v2
§ Simplified Chinese: Cloud HTTP v2
792
§ Spanish: Nube HTTP v2
Remarks
Remark Description
Internet access § The probe system requires access to the internet and must be able to
reach https://api.prtgcloud.com:443 to communicate with the PRTG
Cloud.
§ This sensor requires that the address in the settings of the parent
device is reachable via the internet.
Smart URL replacement § This sensor supports smart URL replacement 797 .
channels.
Probe system § To monitor a probe system, enter the URL of the probe system that is
reachable via the internet as Custom URL in the Cloud HTTP
Specific 794 settings or add a device with the URL in the settings of the
device.
Inheritance § This sensor inherits proxy settings from the parent device.
Scanning interval § The minimum scanning interval of this sensor is 1 minute.
Knowledge Base § Knowledge Base: What is the PRTG Cloud Bot?
793
you add the sensor:
§ cloud
§ cloudhttpsensor
§ http
Cloud HTTP Specific
Cloud HTTP Specific
794
Setting Description
URL Select if you want to inherit the URL from the parent device or if you want
to enter a custom URL:
§ Inherit (default)
§ Custom
Custom URL This setting is only visible if you select Custom above.
Enter the URL that you want to monitor.

The URL must be valid and URL encoded.
You can enter a URL that leads to a web page, for example, to
measure the page source code's loading time, or you can enter the
URL of an image or other page asset to measure this element's
availability and loading time.
PRTG uses a smart URL replacement with which you can use the
parent device's IP address or Domain Name System (DNS) name
setting as part of the URL. For more information, see section Smart URL
Replacement 797 .
Request Method Select an HTTP request method to determine how the sensor requests
the URL:
§ GET (default): Directly request the web page. We recommend that you
use this setting for a simple check of a web page.
§ POST: Send post form data to the URL.
§ HEAD: Only request the HTTP header from the server without the
actual web page.
This setting saves bandwidth because it transfers less data.
However, we do not recommend this setting because the
measured request time is not the request time that the users
experience and you might not be notified of slow results or timeouts.
Postdata This setting is only visible if you select POST above.
Enter the data part for the POST request.
Region Select the regions from which you want to check the service:
§ Asia Pacific (Singapore)
§ Asia Pacific (Sydney)
§ Europe (Ireland)
§ US East (Northern Virginia)
§ US West (Northern California)
795
Setting Description
PRTG creates two channels for every region that you select.
Timeout (Sec.) Enter a timeout in seconds for the ping. If the reply takes longer than this
value, PRTG cancels the request and shows an error message. Enter an
integer. You can enter a value between 1 and 30 seconds.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
796
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Smart URL Replacement

Instead of entering a complete address in the URL field of an HTTP sensor, you can only enter the
protocol followed by a colon and three forward slashes (this means that you can enter either http:/// or
https:///, or even a simple forward slash / as the equivalent for http:///). PRTG automatically fills in the
parent device's IP Address/DNS Name in front of the third forward slash.
Whether this results in a valid URL or not depends on the IP address or Domain Name System (DNS)
name of the parent device. In combination with cloning devices, you can use smart URL replacement to
create many similar devices.
For example, if you create a device with the DNS name www.example.com and you add an HTTP sensor
to it, you can provide values in the following ways:
§ If you enter https:/// in the URL field, PRTG automatically creates the URL https://www.example.com/
797
§ If you enter /help in the URL field, PRTG automatically creates and monitor the URL
http://www.example.com/help
§ It is also possible to provide a port number in the URL field. It is taken over by the device's DNS name
and is internally added, for example, http://:8080/
Smart URL replacement does not work for sensors that run on the probe device.
Channel List
Channel Description
Asia Pacific (Singapore) The response time of the target server at the location
§ Upper error limit: 5000 msec
§ Upper warning limit: 3333 msec
Asia Pacific (Singapore) - The response code of the target server at the location
HTTP Response Code
Asia Pacific (Singapore) - If the PRTG Cloud query was successful or not
PRTG Cloud Response
§ Up status: OK
Asia Pacific (Sydney) The response time of the target server at the location

Asia Pacific (Sydney) - The response code of the target server at the location
HTTP Response Code
Asia Pacific (Sydney) - If the PRTG Cloud query was successful or not
PRTG Cloud Response
§ Up status: OK
798
Channel Description
Europe (Ireland) The response time of the target server at the location
Europe (Ireland) - HTTP The response code of the target server at the location
Response Code
Europe (Ireland) - PRTG If the PRTG Cloud query was successful or not
Cloud Response
§ Up status: OK
Global Average The average global loading time

US East (Northern The response time of the target server at the location
Virginia)
US East (Northern The response code of the target server at the location
Virginia) - HTTP
Response Code
US East (Northern If the PRTG Cloud query was successful or not

Virginia) - PRTG Cloud
§ Up status: OK
Response
US West (Northern The response time of the target server at the location
California)
799
Channel Description
US West (Northern The response code of the target server at the location
California) - HTTP
Response Code
US West (Northern If the PRTG Cloud query was successful or not

California) - PRTG Cloud
§ Up status: OK
Response
More
KNOWLEDGE BASE
What is the PRTG Cloud Bot?


800
7.8.18 Cloud Ping v2 Sensor
The Cloud Ping v2 sensor monitors the Transmission Control Protocol (TCP) ping times to its parent
device from different locations worldwide via the PRTG Cloud. The locations are distributed among four
continents around the globe.
Cloud Ping v2 Sensor
List 806 .

§ Dutch: Cloud Ping v2
§ French: Cloud Ping v2
§ German: Cloud Ping v2
§ Japanese: Ping v2
§ Portuguese: Cloud Ping v2
§ Russian: Cloud Ping v2
§ Simplified Chinese: Cloud Ping v2
§ Spanish: Nube ping v2
801
Remarks
Remark Description
Internet access § The probe system requires access to the internet and must be able to
reach https://api.prtgcloud.com:443 to communicate with the PRTG
Cloud.
§ This sensor requires that the address in the settings of the parent
device is reachable via the internet.
Localhost § You cannot use this sensor to monitor localhost (127.0.0.1).
Probe system § To monitor the probe system, enter the IP address or the fully qualified
domain name (FQDN) of the probe system that is reachable via the
internet as Custom Target Address in the Cloud Ping Specific 803
settings or add a device with the IP address or the DNS name of the
probe system.
TCP § This sensor uses Transmission Control Protocol (TCP) ping.
Inheritance § This sensor inherits proxy settings from the parent device.
Knowledge Base § Knowledge Base: What is the PRTG Cloud Bot?
802
you add the sensor:
§ cloud
§ cloudpingsensor
§ ping
Cloud Ping Specific
Cloud Ping Specific
803
Setting Description
Target Address Select if you want to inherit the IP address or the FQDN from the parent
device or if you want to enter a custom target address:
§ Inherit (default)
§ Custom
Custom Target Address This setting is only visible if you select Custom above.
Enter the IP address or the FQDN of the target device.
Port Enter the number of the port that this sensor uses for TCP ping. The
default port is 80.
This sensor does not support port 25.
Ping Count Enter the number of pings that PRTG sends in a row to the parent device
in one scanning interval. Enter an integer. The minimum value is 1. The
maximum value is 10.
Region Select the regions from which you want to check the service:
§ Europe (Ireland)
Timeout (Sec.) Enter a timeout in seconds per ping. You can enter a value between 1
and 30 seconds.
The actual timeout duration depends on the number of pings that you
entered under Ping Count. PRTG calculates this value by multiplying
Ping Count by Timeout (Sec.).
Sensor Display
Sensor Display
804
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
805
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Asia Pacific (Singapore) The response time of the target server at the location
Asia Pacific (Singapore) - If the PRTG Cloud query was successful or not
PRTG Cloud Response
§ Up status: OK
Asia Pacific (Sydney) The response time of the target server at the location
Asia Pacific (Sydney) - If the PRTG Cloud query was successful or not
PRTG Cloud Response
§ Up status: OK
806
Channel Description
Europe (Ireland) The response time of the target server at the location

Europe (Ireland) - PRTG If the PRTG Cloud query was successful or not
Cloud Response
§ Up status: OK
Global Average The average global response time

US East (Northern The response time of the target server at the location
Virginia)
US East (Northern If the PRTG Cloud query was successful or not

Virginia) - PRTG Cloud
§ Up status: OK
Response
US West (Northern The response time of the target server at the location
California)
US West (Northern If the PRTG Cloud query was successful or not

California) - PRTG Cloud
§ Up status: OK
Response
807
Channel Description
More
KNOWLEDGE BASE
What is the PRTG Cloud Bot?


808
7.8.19 Cluster Health Sensor
The Cluster Health sensor monitors the health of a failover cluster and indicates the system health status
of PRTG.
Cluster Health Sensor
List 811 .

§ Dutch: Cluster Status
§ French: État du cluster
§ German: Cluster-Zustand
§ Japanese:
§ Portuguese: Funcionamento do cluster
§ Russian:
§ Spanish: Salud de clúster
809
Remarks
Remark Description
Sensor creation § PRTG automatically creates this sensor with a cluster installation. You
cannot manually delete it or add it.
Down status § If at least one cluster node is disconnected, this sensor shows the
Down status by default.
Cluster node states § You can review the states of each cluster node on this sensor's
Overview tab.
Cluster node data § You can choose the cluster node for which you want to show data (or
for all cluster nodes) on the monitoring data review tabs. For more
information, see the Knowledge Base: What options do I have to review
my monitoring data in detail?
you add the sensor:
§ clusterhealthsensor
810
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
811
Channel Description
Cluster Messages In The number of ingoing cluster messages per minute
Cluster Messages Out The number of outgoing cluster messages per minute
Cluster Nodes The number of disconnected cluster nodes

Disconnected
This channel has a default limit:
Connects The number of connects per minute
Outbound Cluster The number of outbound cluster connections

Connections
More
KNOWLEDGE BASE

812
7.8.20 Common SaaS Sensor
The Common SaaS sensor monitors the availability of several software as a service (SaaS) providers.
With this sensor, you can get alarms if your cloud services are not reachable.
Common SaaS Sensor
List 816 .

§ Dutch: Algemene SaaS
§ French: SaaS courants
§ German: Verbreitete SaaS-Dienste
§ Japanese: Common SaaS
§ Portuguese: SaaS Comuns
§ Russian: SaaS
§ Simplified Chinese: SaaS
813
§ Spanish: SaaS común
Remarks
Remark Description
Internet access § This sensor requires that the probe system has access to the internet.
Scanning interval § This sensor has a fixed scanning interval of 15 minutes. You cannot
change it.
Sensor creation § PRTG automatically creates this sensor on every probe device. If the
probe system has no connection to the internet, manually pause or
delete this sensor to avoid error messages.
you add the sensor:
§ commonsaas
§ saas
814
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

815
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Available Services The available services (%)

§ Lower error limit: 50
§ Lower warning limit: 90
Bing The response time of the SaaS provider
816
Channel Description
Dropbox The response time of the SaaS provider
Facebook The response time of the SaaS provider
GitHub The response time of the SaaS provider
Google Apps The response time of the SaaS provider
Office 365 The response time of the SaaS provider
Salesforce The response time of the SaaS provider
Twitter The response time of the SaaS provider
Youtube The response time of the SaaS provider
More
KNOWLEDGE BASE

817
7.8.21 Core Health Sensor
The Core Health sensor is a probe-dependent sensor that monitors internal PRTG parameters. It shows
the status of the PRTG core server and checks various parameters of the PRTG core server that have an
impact on the stability of the system.
Core Health Sensor
List 820 .

§ Dutch: Core Status
§ French: État du serveur central
§ German: Serverzustand
§ Japanese:
§ Portuguese: Funcionamento do servidor central
818
§ Russian:
§ Spanish: Salud de servidor central
Remarks
Remark Description
Sensor creation § PRTG automatically creates this sensor. You cannot delete it.
Sensor usage § You can only set up this sensor on a local probe device.
Memory information § You can also find information related to PRTG core server system
memory under Setup | PRTG Status.
you add the sensor:
§ corehealthsensor
819
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
820
Channel Description
Age of Code The time that has passed since the last update of your PRTG core server.
Update regularly to get the best security and stability for PRTG, as well
as the latest features. We recommend that you use the auto-update to
automatically get new versions.
§ Upper warning limit: 7776000 seconds
Committed Memory The amount of memory committed to the PRTG core server as reported
by the memory manager
Configuration Last Saved The time passed since the configuration file was last saved successfully.
PRTG saves the configuration every 24 hours. If the configuration cannot
be saved, PRTG creates a ticket as soon as the saving process has
failed, and warns you via this channel after 26 hours. None of your
changes to PRTG can be saved if this happens. In this case, restart your
PRTG core server to save the file.
CPU Load The CPU load (%). Extensive CPU load can lead to false, incomplete, and
incorrect monitoring results. This value should usually stay below 50%.
Free Page File Memory The amount of free page file memory that is 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 running processes. If it gets too low, the system can break down,
and at least some applications throw Out of memory errors.
Free Physical Memory The amount of free physical memory that is available on the system. This
is the RAM that is physically built into the computer. If it gets too low, the
system becomes very slow and PRTG no longer works in a useful way.
Some sensors might not be displayed correctly and show the Unknown
status.
821
Channel Description
Free Virtual Memory The address space on the system that PRTG can access. PRTG cannot
use more memory than reported here, which is independent from free
page file and physical memory. On a 32-bit operating system, the
maximum is 2 GB (3 GB with special settings under Windows). On a 64-
bit operating system, it is 4 GB if PRTG runs as a 32-bit version, and
unlimited if it runs as a 64-bit version (PRTG core server only). If the free
virtual memory gets too low, PRTG throws Out of memory errors or the
message not enough storage to process this command. This message is
visible in the Core log.
Handles The counter for the data structures of the operating system. It is
responsible for internal resource management. Investigate obviously
increasing values that occur repeatedly.
Health The sum of the PRTG core server state as a value between 100%
(healthy) and 0% (failing). Investigate frequent or repeated health values
below 100%.
Maintenance Days The remaining maintenance days of your PRTG Network Monitor license.
If your maintenance is going to expire soon, act in time to make sure that
you continue to get updates and access to new features for PRTG
Network Monitor.
PRTG Hosted Monitor shows a fixed value here for technical reasons.
Notifications in Send The number of notifications that are in the send queue
Queue
Number of State Objects The number of user-specific state objects that are found in the memory of
the PRTG core server system
Probe Messages per The number of messages sent from all probes to the PRTG core server
Second
Raw Data Buffer The amount of raw data that is temporarily stored on the physical memory
during I/O operations on the disk. Usually, this value should be 0 (or very
low). Investigate increasing values.
822
Channel Description
Threads The number of program parts that are running simultaneously. This
number can increase with heavy load. Usually, this number should not
exceed 100.
More
KNOWLEDGE BASE

823
7.8.22 Core Health (Autonomous) Sensor
The Core Health (Autonomous) sensor is a probe-independent sensor that monitors internal PRTG
parameters. It shows the status of the PRTG core server and checks various parameters of the PRTG
core server that have an impact on the stability of the system.
The Core Health (Autonomous) sensor has the same functionality as the Core Health 818 sensor.
The only difference is that the Core Health (Autonomous) sensor runs independently of the probe.
This means that if the probe disconnects, this sensor still monitors the status of the PRTG core server.
Core Health (Autonomous) Sensor
List 826 .

§ Dutch: Core Health (autonoom)
§ French: État du serveur central (autonome)
§ German: Serverzustand (Autonom)
§ Japanese: ( )
824
§ Portuguese: Funcionamento do servidor central (autônomo)
§ Russian: ( )
§ Spanish: Salud de servidor central (autónomo)
Remarks
Remark Description
Sensor creation § You cannot add this sensor to a probe.
Memory information § You can also find information related to PRTG core server system
memory under Setup | PRTG Status.
you add the sensor:
§ autonomous
§ corehealthsensor
825
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
826
Channel Description
Age of Code The time that has passed since the last update of your PRTG core server.
Update regularly to get the best security and stability for PRTG, as well
as the latest features. We recommend that you use the auto-update to
automatically get new versions.
Committed Memory The amount of memory committed to the PRTG core server as reported
by the memory manager
Configuration Last Saved The time passed since the configuration file was last saved successfully.
PRTG saves the configuration every 24 hours. If the configuration cannot
be saved, PRTG creates a ticket as soon as the saving process has
failed, and warns you via this channel after 26 hours. None of your
changes to PRTG can be saved if this happens. In this case, restart your
PRTG core server to save the file.
CPU Load The CPU load (%). Extensive CPU load can lead to false, incomplete, and
Free Page File Memory The amount of free page file memory that is 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 running processes. If it gets too low, the system can break down,
and at least some applications throw Out of memory errors.
Free Physical Memory The amount of free physical memory that is available on the system. This
is the RAM that is physically built into the computer. If it gets too low, the
system becomes very slow and PRTG no longer works in a useful way.
Some sensors might not be displayed correctly and show the Unknown
status.
827
Channel Description
Free Virtual Memory The address space on the system that PRTG can access. PRTG cannot
use more memory than reported here, which is independent from free
page file and physical memory. On a 32-bit operating system, the
maximum is 2 GB (3 GB with special settings under Windows). On a 64-
bit operating system, it is 4 GB if PRTG runs as a 32-bit version, and
unlimited if it runs as a 64-bit version (PRTG core server only). If the free
virtual memory gets too low, PRTG throws Out of memory errors or the
message not enough storage to process this command. This message is
visible in the Core log.
Health The sum of the PRTG core server state as a value between 100%
(healthy) and 0% (failing). Investigate frequent or repeated health values
below 100%.
Maintenance Days The remaining maintenance days of your PRTG Network Monitor license.
If your maintenance is going to expire soon, act in time to make sure that
you continue to get updates and access to new features for PRTG
Network Monitor.
PRTG Hosted Monitor shows a fixed value here for technical reasons.
Notifications in Send The number of notifications that are in the send queue
Queue
Number of State Objects The number of user-specific state objects that are found in the memory of
the PRTG core server system
Probe Messages per The number of messages sent from all probes to the PRTG core server
Second
Raw Data Buffer The amount of raw data that is temporarily stored on the physical memory
during I/O operations on the disk. Usually, this value should be 0 (or very
low). Investigate increasing values.
828
Channel Description
Threads The number of program parts that are running simultaneously. This
number can increase with heavy load. Usually, this number should not
exceed 100.
More
KNOWLEDGE BASE

829
7.8.23 Dell EMC Unity Enclosure Health v2 Sensor
The Dell EMC Unity Enclosure Health v2 sensor monitors the health of a disk-array enclosure (DAE) or a
physical or virtual disk processor enclosure (DPE) on a Dell EMC storage system via the
Representational State Transfer (REST) application programming interface (API).
Dell EMC Unity Enclosure Health v2 Sensor
List 834 .

§ Dutch: Dell EMC Unity Enclosure Health v2
§ French: Dell EMC Unity état du boîtier v2
§ German: Dell EMC Unity Zustand des Gehäuses v2
§ Japanese: Dell EMC Unity Enclosure Health v2
§ Portuguese: Saúde do sistema Dell EMC Unity v2
§ Russian: Dell EMC Unity v2

§ Simplified Chinese: Dell EMC Unity v2
§ Spanish: Dell EMC Unity salud del gabinete v2
830
Remarks
Remark Description
Credentials § This sensor requires credentials for Dell EMC.
Unity OE 5.x § This sensor only supports systems from the Dell EMC Unity family with
Unity OE 5.x.
REST API § Dell EMC systems that provide a REST API are EMC Unity Family,
EMC Unity All Flash, EMC Unity Hybrid, and EMC UnityVSA.
channels.
you add the sensor:
§ dellemc
§ dellemcenclosure
§ dellemcstorage
831
§ restsensor
Dell EMC Specific
Dell EMC Specific
Setting Description
Enclosure Name The name of the enclosure that this sensor monitors.
Enclosure Type The type of the enclosure that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


832
Setting Description
other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
833
Channel List
Channel Description
Cooling Modules The cooling modules status

§ Up status: OK, OK But Minor Warning
§ Warning status: Degraded, Minor Issue
§ Down status: Major Issue, Critical Issue, Non Recoverable
§ Unknown status: Unknown
Drives The drives status

Health Status The health status

Link Control Cards The link control cards status

Power Consumption The power consumption
834
Channel Description
Power Supplies The power supplies status

Temperature The temperature of the enclosure
More
KNOWLEDGE BASE

835
7.8.24 Dell EMC Unity File System v2 Sensor
The Dell EMC Unity File System v2 sensor monitors a file system on a Dell EMC storage system via the
Dell EMC Unity File System v2 Sensor
List 840 .

§ Dutch: Dell EMC Unity Bestandssysteem v2
§ French: Dell EMC Unity système de fichiers v2
§ German: Dell EMC Unity Dateisystem v2
§ Japanese: Dell EMC Unity File System v2
§ Portuguese: Sistema de arquivos Dell EMC Unity v2

§ Spanish: Dell EMC Unity sistema de archivo v2
Remarks
836
Remark Description
Unity OE 5.x.
you add the sensor:
§ dellemc
§ dellemcfilesystem
§ dellemcstorage
§ emcfilesystemsensor
§ emcsensor
§ restsensor
837
Dell EMC Specific
Dell EMC Specific
Setting Description
File System Name The name of the file system that this sensor monitors.
File System Type The type of the file system that this sensor monitors.
Protocol The protocol under which the monitored file system operates.
Sensor Display
Sensor Display
Setting Description

838
Setting Description

other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
839
Channel List
Channel Description
Allocated Size The allocated size
Free Size The free size
Free Size % The free size (%)

§ Lower error limit: 10%
§ Lower warning limit: 25%
Snapshot Count The snapshot count
Snapshot Used Size The used snapshot size
Total Size The total size
More
KNOWLEDGE BASE

840
7.8.25 Dell EMC Unity Storage Capacity v2 Sensor
The Dell EMC Unity Storage Capacity v2 sensor monitors a Dell EMC storage system via the
Dell EMC Unity Storage Capacity v2 Sensor
List 844 .

§ Dutch: Dell EMC Unity opslagcapaciteit v2
§ French: Dell EMC Unity capacité de stockage v2
§ German: Dell EMC Unity Speicherkapazität v2
§ Japanese: Dell EMC Unity Storage Capacity v2
§ Portuguese: Capacidade de armazenamento Dell EMC Unity v2

§ Spanish: Dell EMC Unity capacidad de almacenamiento v2
841
Remarks
Remark Description
Unity OE 5.x.
you add the sensor:
§ dellemc
§ dellemccapacity
§ dellemcstorage
§ emccapacitysensor
842
§ emcsensor
§ restsensor
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
843
Setting Description
master node.
Inherited Settings
Channel List
Channel Description

844
Channel Description
Preallocated Size The preallocated size
Preallocated Size % The preallocated size (%)
Subscribed Size The subscribed size
Subscribed Size % The subscribed size (%)
Used Size The used size
Used Size % The used size (%)
More
KNOWLEDGE BASE

845
7.8.26 Dell EMC Unity Storage LUN v2 Sensor
The Dell EMC Unity Storage LUN v2 sensor monitors a logical unit number (LUN) on a Dell EMC storage
system via the Representational State Transfer (REST) application programming interface (API).
Dell EMC Unity Storage LUN v2 Sensor
List 850 .

§ Dutch: Dell EMC Unity Opslag LUN v2
§ French: Dell EMC Unity LUN de stockage v2
§ German: Dell EMC Unity LUN-Speicher v2
§ Japanese: Dell EMC Unity Storage LUN v2
§ Portuguese: LUN de armazenamento Dell EMC Unity v2
§ Russian: LUN Dell EMC Unity v2

§ Simplified Chinese: Dell EMC Unity LUN v2
§ Spanish: Dell EMC Unity almacenamiento LUN v2
Remarks
846
Remark Description
Unity OE 5.x.
channels.
you add the sensor:
§ dellemc
§ dellemclun
§ dellemcstorage
§ emclunsensor
§ emcsensor
§ restsensor
847
Dell EMC Specific
Dell EMC Specific
Setting Description
LUN Name The name of the LUN that this sensor monitors.
LUN ID The ID of the LUN that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


848
Setting Description
other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
849
Channel List
Channel Description
Allocated Metadata Size The allocated metadata size
Allocated Size The allocated size
Allocated Snapshot Size The allocated snapshot size

More
KNOWLEDGE BASE

850
7.8.27 Dell EMC Unity Storage Pool v2 Sensor
The Dell EMC Unity Storage Pool v2 sensor monitors a storage pool on a Dell EMC storage system via
the Representational State Transfer (REST) application programming interface (API).
Dell EMC Unity Storage Pool v2 Sensor
List 855 .

§ Dutch: Dell EMC Unity Opslagpool v2
§ French: Dell EMC Unity pool de stockage v2
§ German: Dell EMC Unity Speicherpool v2
§ Japanese: Dell EMC Unity Storage Pool v2
§ Portuguese: Pool de armazenamento Dell EMC Unity v2

851
§ Spanish: Dell EMC Unity grupo de almacenamiento v2
Remarks
Remark Description
Unity OE 5.x.
channels.
you add the sensor:
§ dellemc
852
§ dellemcpool
§ dellemcstorage
§ emcpoolsensor
§ emcsensor
§ restsensor
Dell EMC Specific
Dell EMC Specific
Setting Description
Storage Pool Name The name of the storage pool that this sensor monitors.
Storage Pool ID The ID of the storage pool that this sensor monitors.
Sensor Display
Sensor Display
Setting Description
853
Setting Description

other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
854
Inherited Settings
Channel List
Channel Description


Metadata Subscribed The subscribed metadata size

Size
Metadata Used Size The used metadata size
Preallocated Size The preallocated size
Preallocated Size % The preallocated size (%)
855
Channel Description
Snapshot Subscribed The subscribed snapshot size

Size
Subscribed Size The subscribed size
Subscribed Size % The subscribed size (%)
Used Size The used size
Used Size % The used size (%)
More
KNOWLEDGE BASE

856
7.8.28 Dell EMC Unity VMware Datastore v2 Sensor
The Dell EMC Unity VMware Datastore v2 sensor monitors a VMware datastore on a Dell EMC storage
system via the Representational State Transfer (REST) application programming interface (API).
Dell EMC Unity VMw are Datastore v2 Sensor
List 861 .

§ Dutch: Dell EMC Unity VMware Datastore v2
§ French: Dell EMC Unity VMware datastore v2
§ German: Dell EMC Unity VMware-Datenspeicher v2
§ Japanese: Dell EMC Unity VMware Datastore v2
§ Portuguese: Repositório de dados VMware Dell EMC Unity v2
§ Russian: VMware Dell EMC Unity v2

§ Simplified Chinese: Dell EMC Unity VMware v2
§ Spanish: Dell EMC Unity almacén de datos VMware v2
857
Remarks
Remark Description
Unity OE 5.x.
you add the sensor:
§ dellemc
§ dellemcdatastore
§ dellemcvmware
§ emcsensor
858
§ restsensor
Dell EMC Specific
Dell EMC Specific
Setting Description
VMware Datastore Name The name of the VMware datastore that this sensor monitors.
VMware Datastore Type The type of the VMware datastore that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


859
Setting Description
other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
860
Channel List
Channel Description

Host Count The number of hosts
Virtual Drive Count The number of virtual drives
Virtual Machine Count The number of virtual machines
More
KNOWLEDGE BASE

861
7.8.29 Dell PowerVault MDi Logical Disk Sensor
The Dell PowerVault MDi Logical Disk sensor monitors a virtual disk on a Dell PowerVault system.
This sensor supports Dell PowerVault MD3000i, MD3420, MD3620i, MD3000f, MD3620f, or
MD3820i, and might support other models.
Dell Pow erVault MDi Logical Disk Sensor
List 865 .

§ Dutch: Dell PowerVault MDi Logische Schijf
§ French: Dell PowerVault MDi disque logique
§ German: Dell PowerVault MDi Logischer Datenträger
§ Japanese: Dell PowerVault MDi
§ Portuguese: Disco lógico Dell PowerVault MDi
§ Russian: Dell PowerVault MDi

§ Simplified Chinese: Dell PowerVault MDi
§ Spanish: Disco lógico Dell PowerVault MDi
862
Remarks
Remark Description
Dell Modular Disk § This sensor requires Dell Modular Disk Storage Manager on the probe
Storage Manager system.
§ You must install it on the probe system (on every cluster node, if on a
cluster probe). For details about setup, see section More below.
Create this sensor on a device that has the IP address of the SAN
configured in the IP Address/DNS Name field of the sensor settings.
For more information, see the Knowledge Base: Where do I find the
Dell PowerVault Modular Disk Storage Manager for use with my MDi
SAN?
IP address § This sensor requires the IP address of the storage area network (SAN)
in the settings of the parent device.
Dell PowerVault models § This sensor supports Dell PowerVault MD3000i, MD3420, MD3620i,
MD3000f, MD3620f, or MD3820i, and might support other models.
probe device.
you add the sensor:
863
§ powervault
Sensor Settings
Sensor Settings
Setting Description
Virtual Disk The name of the virtual disk that this sensor monitors.
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
864
Setting Description



other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Cache Hit Percentage The cache hits (%)
Current IOs The number of current I/O operations
Current Speed The current disk speed
865
Channel Description
Maximum IOs The maximum number of I/O operations
Maximum Speed The maximum disk speed
Read Percentage The read operations (%)
Total IOs The total number of I/O operations

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

866
7.8.30 Dell PowerVault MDi Physical Disk Sensor
The Dell PowerVault MDi Physical Disk sensor monitors a physical disk on a Dell PowerVault system.
This sensor supports Dell PowerVault MD3000i, MD3420, MD3620i, MD3000f, MD3620f, or
MD3820i, and might support other models.
Dell Pow erVault MDi Physical Disk Sensor
List 870 .

§ Dutch: Dell PowerVault MDi Fysieke Schijf
§ French: Dell PowerVault MDi disque physique
§ German: Dell PowerVault MDi Physikalischer Datenträger
§ Japanese: Dell PowerVault MDi
§ Portuguese: Disco físico Dell PowerVault MDi
§ Russian: Dell PowerVault MDi

§ Simplified Chinese: Dell PowerVault MDi
§ Spanish: Disco físico Dell PowerVault MDi
Remarks
867
Remark Description
Dell Modular Disk § This sensor requires Dell Modular Disk Storage Manager on the probe
Storage Manager system.
§ You must install it on the probe system (on every cluster node, if on a
cluster probe). For details about setup, see section More below.
Create this sensor on a device that has the IP address of the SAN
configured in the IP Address/DNS Name field of the sensor settings.
IP address § This sensor requires the IP address of the storage area network (SAN)
in the settings of the parent device.
Dell PowerVault models § This sensor supports Dell PowerVault MD3000i, MD3420, MD3620i,
MD3000f, MD3620f, or MD3820i, and might support other models.
Multiple drawers § This sensor only supports devices with one drawer of hard-drives.
Multiple drawers are not supported and prevent sensor creation.
channels.
probe device.
you add the sensor:
§ powervault
868
Sensor Settings
Sensor Settings
Setting Description
Physical Disk The physical disk that this sensor monitors.
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
869
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
This sensor shows the status and mode of the physical disk in the channels as reported in the Modular
Disk Storage Manager. Status and mode combined indicate the particular status of a redundant array of
independent disks (RAID) controller physical disk. The table below provides you with the status
description according to the Dell documentation:
Status Channel Mode Channel Description
Up status: Optimal Unassigned The physical disk in the indicated slot is

unused and available to be configured
Assigned The physical disk in the indicated slot is

configured as part of a disk group
870
Status Channel Mode Channel Description
Hot Spare Standby The physical disk in the indicated slot is

configured as a hot spare
Hot Spare In Use The physical disk in the indicated slot is in use
as a hot spare within a disk group
Down status: Failed § Assigned The physical disk in the indicated slot has
failed because of an unrecoverable error, an
§ Unassigned
incorrect drive type or drive size, or by its
§ Hot Spare In Use operational state being set to failed
§ Hot Spare Standby
Up status: Replaced Assigned The physical disk in the indicated slot has been
replaced and is ready to be, or is actively being,
configured into a disk group
Down status: Pending § Assigned A S.M.A.R.T. error has been detected on the
Failure physical disk in the indicated slot
§ Unassigned
§ Hot Spare In Use
§ Hot Spare Standby
Warning status: None None The indicated slot is empty, or the array cannot
detect the physical disk
Down status: Undefined
More
KNOWLEDGE BASE
Where do I find the Dell PowerVault Modular Disk Storage Manager for use with my MDi SAN?

871
7.8.31 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.
This sensor shows the address of the server and the offered IP address in the sensor message. You
can check the server's response via regular expressions.
DHCP Sensor
List 877 .

§ Dutch: DHCP
§ French: DHCP
§ German: DHCP
§ Japanese: DHCP
§ Portuguese: DHCP
§ Russian: DHCP
§ Simplified Chinese: DHCP
§ Spanish: DHCP
Remarks
872
Remark Description
Sensor creation § You can create this sensor only on a probe device.
Static IP address § The probe device where you create this sensor must have a static IP
address. It cannot get its IP address from DHCP because this can
cause a DHCP failure that results in a severe issue for the probe device
so that you risk losing monitoring data.
Local probe only § This sensor does not work if Probe Connection IP Addresses is set to
Local probe only, 127.0.0.1 (PRTG is not accessible for remote
probes). For more information, see the PRTG Manual: Core & Probes.
DHCP unavailable § This sensor shows a timeout error if no DHCP is available, or if you use
more than two DHCP sensors per device.
Link-local address § Adding this sensor on a link-local address is valid and is not prohibited.
However, as this is a local IP address, the sensor does not receive any
data and shows a timeout error.
Add Sensor dialog § Choose the network card on the probe system that is used to send the
broadcast message in the Add Sensor dialog.
Knowledge Base § Knowledge Base: How can I monitor a DHCP server in a specific
network if there are several DHCP networks?
probe device.
873
you add the sensor:
§ dhcpsensor
DHCP Specific
DHCP Specific
Setting Description
MAC Address The MAC address of the network adapter that sends the broadcast
message to the network.
Client IP Address Specify if you want to check the returned client IP address with a regular
expression (regex):
§ Do not check the IP address using a regular expression: The IP
address only appears in the sensor message without further
processing.
§ Check the IP address using a regular expression: Enter the regex that
you want to use below.
Client IP Address Must This setting is only visible if you select Check the IP address using a
Include (Down Status if regular expression above.
Not Included)
In the response of the DHCP server, search by using a regex. If the
response for the client IP address does not contain this string, the sensor
874
Setting Description
For example, enter 10\.0\.5\..* to make sure that any answering

DHCP server returns any client IP address starting with 10.0.5.. If it
does not, the sensor shows the Down status. Leave this field empty if you
do not want to use it.
PRTG supports Perl Compatible Regular Expression (PCRE) regex.

For more information, see section Regular Expressions.
Client IP Address Must This setting is only visible if you select Check the IP address using a
Not Include (Down Status regular expression above.
if Included)
response for the client IP address contains this string, this sensor shows
the Down status. See the example above. Leave this field empty if you do
not want to use it.

Server IP Address Specify if you want to check the returned server IP address with a regex:
§ Do not check the IP address using a regular expression: The IP
address only appears in the sensor message without further
processing.
§ Check the IP address using a regular expression: Enter the regex that
you want to use below.
Server IP Address Must This setting is only visible if you select Check the IP address using a
Include (Down Status if regular expression above.
Not Included)
response for the server IP address does not contain this string, this
sensor shows the Down status. See the example above. Leave this field
empty if you do not want to use it.

Server IP Address Must This setting is only visible if you select Check the IP address using a
Not Include (Down Status regular expression above.
if Included)
response for the server IP address contains this string, this sensor shows
the Down status. See the example above. Leave this field empty if you do
not want to use it.
875
Setting Description

If the reply takes longer than this value, the sensor cancels the
request and shows a corresponding error message.
If Server Changes If there is more than one DHCP server in the network that can respond to
the broadcast message, the sensor can receive a response 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. Define what PRTG
does if DHCP servers change:
§ Write log entry: Write an entry to the system logs whenever the DHCP
server changes between two sensor scans.
Regardless of this setting, entries are always added to the sensor
log.
If IP Address Changes If the IP address offered by the DHCP server changes between two sensor
scans, PRTG can write an entry to the system logs. Define what PRTG
does if IP addresses change:
§ Write log entry: Write an entry to the system logs whenever the DHCP
server offers a different IP address compared to the last sensor scan.
Regardless of this setting, entries are always added to the sensor

log.
Sensor Display
Sensor Display
876
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
877
Channel Description
Lease Time The lease time reported by the server
Response Time The response time

More
KNOWLEDGE BASE
How can I monitor a DHCP server in a specific network if there are several DHCP networks?

878
7.8.32 DICOM Bandwidth Sensor
The DICOM Bandwidth sensor monitors the bandwidth usage of a C-STORE request to a Digital Imaging
and Communications in Medicine (DICOM) capable device. It sends one or more DICOM images and
files that you have stored in a folder on a local disk or share and checks if the DICOM device can handle
the C-STORE request.
You can use this sensor to test your picture archiving and communication system (PACS), for
example.
DICOM Bandw idth Sensor
List 883 .

§ Dutch: DICOM Bandbreedte
§ French: Bande passante (DICOM)
§ German: DICOM-Bandbreite
§ Japanese: DICOM
§ Portuguese: Largura de banda DICOM
§ Russian: DICOM
§ Simplified Chinese: DICOM
§ Spanish: Ancho de banda DICOM
879
Remarks
Remark Description
does PRTG require?
you add the sensor:
§ bandwidth
§ dicom
880
DICOM Connection
DICOM Connection
Setting Description
Calling Application Entity Enter the Application Entity Title (AET) of PRTG to initialize a DICOM
Title connection.
The AET is case-sensitive and does not support special characters.
Called Application Entity Enter the AET of the target system to initialize a DICOM connection.
Title
Port Enter the port of the DICOM interface to use for the connection. The
default port is 104.
Bandwidth Settings
Bandw idth Settings
881
Setting Description
File Path Enter the full path to the folder where you have stored your DICOM files
and images (ending with .dcm). This sensor sends all files to the DICOM
enabled device via a C-STORE request to measure bandwidth. You can
use any folder on a disk or share that the probe system has access to.
For example, enter C:\DICOM to send files that are stored in a folder
named DICOM on the probe system.
The path must contain *.dcm files. Enter the path without a
backslash (\) at the end.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
882
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
C-STORE Bandwidth The bandwidth usage of the sent files

883
Channel Description
C-STORE Response The response time of the C-STORE request

Time
C-STORE Size The total size of the sent files
More
KNOWLEDGE BASE


884
7.8.33 DICOM C-Echo Sensor
The DICOM C-ECHO sensor monitors the availability of Digital Imaging and Communications in Medicine
(DICOM) capable systems and devices by sending C-ECHO requests to the target system. C-ECHO is
also known as DICOM-Ping.
You can use this sensor to verify that the DICOM handshake is executed and that your target
system is capable of answering DICOM messages.
DICOM C-ECHO Sensor
List 889 .

§ Dutch: DICOM C-ECHO
§ French: C-ECHO (DICOM)
§ German: DICOM-C-ECHO
§ Japanese: DICOM C-ECHO
§ Portuguese: C-ECHO DICOM
§ Russian: DICOM C-ECHO
§ Simplified Chinese: DICOM C-ECHO
§ Spanish: C-ECHO DICOM
Remarks
885
Remark Description

does PRTG require?
you add the sensor:
§ cecho
§ dicom
§ ping
886
DICOM Connection
DICOM Connection
Setting Description
Title connection.
Title
C-ECHO Settings
C-ECHO Settings
887
Setting Description
C-ECHO Count Enter the number of C-ECHO requests that the sensor sends in a row for
one scanning interval. Enter an integer. The default value is 5.
Ping Delay (ms) Enter the time in milliseconds (ms) the sensor waits between two C-
ECHO requests. Enter an integer. The default value is 10.
Make sure that the C-ECHO count multiplied by the delay does not
exceed the scanning interval of the sensor.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
888
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
C-ECHO Response Avg. The average response time of the C-ECHO request
889
Channel Description
C-ECHO Response Max The maximum response time of the C-ECHO request
C-ECHO Response Min The minimum response time of the C-ECHO request
More
KNOWLEDGE BASE


890
7.8.34 DICOM Query/Retrieve Sensor
The DICOM Query/Retrieve sensor monitors the C-FIND capability of Digital Imaging and
Communications in Medicine (DICOM) capable systems and devices. It sends a C-FIND request or
Modality Worklist (MWL) query to the target device and counts all found items.
You can specify search levels to only count specific items.
DICOM Query/Retrieve Sensor
List 896 .

§ Dutch: DICOM Query/Retrieve
§ French: Requête/récupération (DICOM)
§ German: DICOM-Abfrage
§ Japanese: DICOM /
§ Portuguese: Consulta/recuperação DICOM
§ Russian: DICOM
§ Simplified Chinese: DICOM /
§ Spanish: Consulta/Recuperación DICOM
891
Remarks
Remark Description
does PRTG require?
you add the sensor:
§ dicom
§ query
§ retrieve
892
DICOM Connection
DICOM Connection
Setting Description
Title connection.
Title
Query/Retrieve Settings
Query/Retrieve Settings
893
Setting Description
C-FIND Level Define the search level of the C-FIND request:

§ Patient: Retrieve data from the patient column via C-FIND. Enter a
search key below.
§ Study: Retrieve data from the study column via C-FIND. Enter a search
key and a modality below.
§ Series: Retrieve data from the series column via C-FIND. Enter a
search key and a modality below.
§ Worklist: Use an MWL query to retrieve data from the worklist. Enter a
filter field, a filter string, and a channel field below.
Search Key This setting is only visible if you select Patient, Study, or Series above.
Enter a key that you want to search for, for example, an instance Unique
Identifier (UID), series UID, patient UID, or enter an asterisk (*) to search
for all items. Enter a string.
Modality This setting is only visible if select Study or Series above.
Enter a modality in short form that you want to search for, for example,
CT, MRI, US, or enter an asterisk (*) to search for all modalities. Enter a
string.
Filter Field This setting is only visible if you select Worklist above.
Define a field of the worklist that you want to filter for:
§ Station AET
§ Station Name
§ Modality
Filter String This setting is only visible if you select Worklist above.
Enter a string that you want to filter for, for example, a station name,
station AET, modality, or an asterisk (*) to filter for all items.
Channel Naming This setting is only visible if you select Worklist above.
Define which field you want to use to name the channels:

§ Station AET
§ Station Name
§ Modality
894
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

895
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Avg. Query Entry Time The average query entry time
Max Query Entry Time The maximum query entry time
Min Query Entry Time The minimum query entry time
Total The total number of items found

896
Channel Description
Total Time The total time of the C-FIND request or MWL query
This sensor also adds channels for the number of items in each field it finds.
More
KNOWLEDGE BASE


897
7.8.35 DNS v2 Sensor
The DNS v2 sensor monitors a Domain Name System (DNS) server, resolves domain name records, and
compares them to a filter.
This sensor can show the Down status if the DNS server does not correctly resolve a specified
domain name
DNS v2 Sensor
List 903 .

§ Dutch: DNS v2
§ French: DNS v2
§ German: DNS v2
§ Japanese: DNS v2
§ Portuguese: DNS v2
§ Russian: DNS v2
§ Simplified Chinese: DNS v2
§ Spanish: DNS v2
898
Remarks
Remark Description
channels.
you add the sensor:
§ dns
§ dnssensor
899
DNS Sensor Specific
DNS Sensor Specific
Setting Description
Domain Name Enter the DNS name to resolve.
If you use the query type PTR resource record (PTR), enter a proper
reverse DNS representation of the IP address. For example,
1.0.0.127.in-addr.arpa.
Query Type Select the query type that the sensor sends to the DNS server:
§ Host address IPv4 (A) (default)
§ Host address IPv6 (AAAA)
§ Canonical name for an alias (CNAME)
§ Mail exchange (MX)
§ Naming authority pointer (NAPTR)
§ Authoritative name server (NS)
§ PTR resource record (PTR)
§ Start of authority (SOA)
§ Text resource record (TXT)
900
Setting Description
§ Any (depends on the DNS server configuration)
The timeout value must be shorter than the scanning interval of the
sensor.
Filter Usage Define if the sensor checks for a specific filter value in the response:
§ Do not use a filter (default): Do not check the response.
§ Use a filter: Use a filter to check the response. Define the filter value
below.
Filter Value This setting is only visible if you select Use a filter above.
Enter one or more filter values. For an A record, the filter value can be an
IP address like 127.0.0.1, for example. The filter value can also contain a
wildcard (*) to match any content, for example 127.*.1. You can specify
multiple filter values by using a comma as separator, for example
172.217.*.1,172.217.*.2.
Port Enter the number of the port to which this sensor connects. This must be
the port on which the parent device answers queries. The default port is
53.

This sensor connects to the IP address or the DNS name of the
parent device.
Sensor Display
Sensor Display
901
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
902
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Matched Record Count The number of matched records (if you use a filter)
Record Count The number of records
Records Resolved If records were resolved

§ Up status: Yes
§ Down status: No

More
KNOWLEDGE BASE

903
7.8.36 Docker Container Status Sensor
The Docker Container Status sensor monitors the status of a Docker container.
Docker Container Status Sensor
List 908 .

§ Dutch: Docker Container Status
§ French: Statut de conteneur Docker
§ German: Docker-Container-Zustand
§ Japanese: Docker
§ Portuguese: Status do contêiner Docker
§ Russian: Docker
§ Simplified Chinese: Docker
§ Spanish: Estado de contenedor Docker.
904
Remarks
Remark Description
Certificate and private § This sensor requires certificates and private keys to monitor Docker.
key
For more information on how to create a Docker certificate, see the
Knowledge Base: How can I create private key and certificate for the
Docker sensor?
Parent device § This sensor requires that the parent device is the Docker machine on
which the container that you want to monitor runs.
Authentication § This sensor requires an authentication with a certificate and a private

key before you can add it.
§ Provide Port (usually 2376), Private Key, and Certificate and click OK.
channels.
you add the sensor:
§ docker
§ dockercontainer
905
Docker Credentials
Docker Credentials
Setting Description
Port Enter the number of the port to which this sensor connects. The default
port on which Docker over Transport Layer Security (TLS) runs is 2376.
Private Key Provide the private key for the connection to Docker. If you have already
created a key, you can use it here. Otherwise, create a key on Docker
first.
Open the key with a text editor, copy everything that the file includes, and
paste it here. Usually, the key starts with -----BEGIN RSA PRIVATE
KEY----- and ends with -----END RSA PRIVATE KEY-----
Docker sensor?
Certificate Provide the certificate for the connection to Docker. If you have already
created a certificate, you can use it here. Otherwise, create a certificate
on Docker first.
Open the certificate with a text editor, copy everything that the file
includes, and paste it here. Usually, the certificate starts with -----BEGIN
CERTIFICATE----- and ends with -----END CERTIFICATE-----
Docker sensor?
906
Docker Specific
Docker Specific
Setting Description
Container ID The ID of the Docker container that this sensor monitors.
Container Name The name of the Docker container that this sensor monitors.
Image The name of the image that was used to create the Docker container that
this sensor monitors.
Container Identification Define how the sensor identifies the Docker container that it monitors:
§ By container ID (default): Use the ID of the Docker container for
identification.
§ By container name: Use the name of the Docker container for
identification.
Use this option if the IDs of your Docker containers regularly
change, for example, because of nightly deployments of your
Docker containers.
Result of Sensor [ID].Data.txt, Result of Sensor [ID]_1.json, and Result
of Sensor [ID]_2.json. This setting is for debugging purposes. PRTG
master node.
907
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
908
Channel Description

CPU Usage The CPU usage
Eth0 Packets In The number of ingoing packets
Eth0 Packets Out The number of outgoing packets
Eth0 Traffic In The incoming traffic
Eth0 Traffic Out The outgoing traffic
Exit Code The exit code
Status The overall status
§ Up status: Create, Running
§ Warning status: Paused, Restarting
§ Down status: Exited
Uptime The uptime
More
KNOWLEDGE BASE
How can I create private key and certificate for the Docker sensor?

909
7.8.37 Enterprise Virtual Array Sensor
The Enterprise Virtual Array sensor monitors an HPE Storage Enterprise Virtual Array (EVA) via the
sssu.exe from HPE P6000 Command View Software (previously known as HP Command View EVA
Software).
List 913 .

§ Dutch: Enterprise Virtual Array
§ French: Enterprise Virtual Array
§ German: Enterprise Virtual Array
§ Japanese: Enterprise Virtual Array
§ Portuguese: Enterprise Virtual Array
§ Russian: Enterprise Virtual Array
§ Simplified Chinese: Enterprise Virtual Array
§ Spanish: Enterprise Virtual Array
Remarks
Remark Description
HPE P6000 Command § This sensor requires the HPE P6000 Command View Software on the
View Software probe system, or the alternative described in the Knowledge Base: Do I
really have to install the whole Command View on the probe to use the
EVA sensor?
Credentials § This sensor requires that you explicitly specify the credentials for the
EVA in the sensor settings.
channels.
probe device.
910
Add Sensor
Setting Description
Scanning Mode Specify the depth of the meta-scan:

§ Basic mode: We recommend that you use this scanning mode.
Various modules of your EVA are available for monitoring.
§ Detailed mode: PRTG scans for each disk of your EVA. It lists every
disk in the module selection.
you add the sensor:
§ eva
EVA Credentials
Setting Description
User Name Enter the user name for the EVA.
Password Enter the password for the EVA.
911
EVA Settings
Setting Description
Module The module that this sensor monitors.

You can edit this setting if, for example, you rename the module or
move it to a different folder. This way, PRTG can find the module
again and you do not lose the monitoring history.
System The system of the module that this sensor monitors.
Module Type The type of the module that this sensor monitors.
Description The description of the module that this sensor monitors.
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
912
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
This sensor can show the status of several HPE EVA modules:
§ System controllers
§ Enclosures
§ Disks
§ Disk groups
§ Folders
§ Hosts
§ Snapshots
§ Data replication
§ Cabinets
913
§ If the devices have measuring tools for fans and temperature, this sensor displays corresponding data
as well.
For these EVA components, this sensor can show the following:
§ Operational status
§ Predicted failures
§ Accessible media
§ Allocation in percent
§ Availability for VRaids in bytes
§ Exaggerated bytes
§ Group host access
§ Number of grouped and ungrouped disks
§ Age of snapshots
§ License status
More
KNOWLEDGE BASE
Do I really have to install the whole Command View on the probe to use the EVA sensor?

914
7.8.38 Event Log (Windows API) Sensor
Important Notice
This sensor might not work anymore after Windows updates of June 2021. For more information, see
the Knowledge Base: My Event Log (Windows API) sensors fail after installing Windows updates.
What can I do?
The Event Log (Windows API) sensor monitors event log entries via the Windows application
programming interface (API).
Event Log (Window s API) Sensor
List 922 .

§ Dutch: Event Log (Windows API)
§ French: Journal des événements (API Windows)
§ German: Ereignisprotokoll (Windows API)
§ Japanese: ( Windows API)

§ Portuguese: Log de eventos (Windows API)
§ Russian: (API Windows)

§ Simplified Chinese: (Windows API)
§ Spanish: Registro de eventos (Windows API)
915
Remarks
Remark Description
Performance impact § This sensor has a very high performance impact. We recommend that
you use no more than 50 of this sensor on each probe.
Knowledge Base § Knowledge Base: My Event Log (Windows API) sensors fail after
installing Windows updates. What can I do?
§ Knowledge Base: My Event Log sensor ignores changes in the event
log. What can I do?
§ Knowledge Base: How can I configure sensors using speed limits to
keep the status for more than one interval?
probe device.
you add the sensor:
§ wmiapieventlogsensor
916
Windows API Event Log Specific
Window s API Event Log Specific
Setting Description
Log File The Windows event log provides several log files. Specify the log file that
this sensor monitors:
§ Application
§ System
§ Security
§ Directory Service
§ DNS Server
§ File Replication Service
917
Filter Event Log Entries
Setting Description
Event Type Specify the type of event that this sensor processes:
§ Any
§ Error
§ Warning
§ Information
§ Security Audit Success
§ Security Audit Failure
918
Setting Description
The sensor cannot process other event types.
Filter by Source Filter all received events for a certain event source:
§ Off: Do not filter events.
§ On: Filter events.

The sensor only processes messages that match the value that
you define below.
Filter Type This setting is only visible if you select On above.
Select the filter type:

§ Include filter: Include the specified value and disregard all other values.
§ Exclude filter: Exclude the specified value and regard all other values.
Match String (Event This setting is only visible if you select On above.
Source)
Enter an event source that you want to filter for. Depending on the kind of
filter, the sensor either processes the event source (Include filter option)
or it does not process it (Exclude filter option). Enter a string.
Filter by ID Filter all received events for a certain event ID:


you define below.

Match Values (Event ID) This setting is only visible if you select On above.
Enter an event ID that you want to filter for. Depending on the kind of filter,
the sensor either processes the event ID (Include filter option) or it does
not process it (Exclude filter option).
The Event Log (Windows API) supports more than one event ID. You
can enter a comma-separated list of event IDs to filter for more than
one ID. For example, 1100,4627,4747,4884,5050,6422.
919
Setting Description
Filter by Category Filter all received events for a certain event category:

you define below.

Category)
Enter a category that you want to filter for. Depending on the kind of filter,
the sensor either processes the event category (Include filter option) or it
does not process it (Exclude filter option). Enter a string.
Filter by User Filter all received events for a certain event user:

you define below.

User)
Enter a user name that you want to filter for. Depending on the kind of
filter, the sensor either processes the event user (Include filter option) or it
Filter by Computer Filter all received events for a certain event computer:

you define below.
920
Setting Description

Computer)
Enter a computer name that you want to filter for. Depending on the kind
of filter, the sensor either processes the event computer (Include filter
option) or it does not process it (Exclude filter option). Enter a string.
Filter by Message Filter all received events for a certain event message:

you define below.

Message)
Enter a message that you want to filter for. Depending on the kind of filter,
the sensor either processes the event message (Include filter option) or it
This sensor only checks the last line of the event message for the
entered string. This matches the <Data> section of the XML that you
can see on the Details tab in the Event Viewer. If you want to check the
entire event message, use the WMI Event Log sensor.
You must use the percent sign (%) as wildcard for any or no
character if you want to check if the string is part of the last line of
the event message. Otherwise, the whole last line of the event message
must match the string.
921
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
922
Channel Description
New Records The number of new records
More
KNOWLEDGE BASE
My Event Log (Windows API) sensors fail after installing Windows updates. What can I do?
My Event Log sensor ignores changes in the event log. What can I do?
How can I configure sensors using speed limits to keep the status for more than one interval?

923
7.8.39 Exchange Backup (PowerShell) Sensor
The Exchange Backup (PowerShell) sensor monitors backups of an Exchange server via Remote
PowerShell.
Exchange Backup (Pow erShell) Sensor
List 928 .

§ Dutch: Exchange Backup (PowerShell)
§ French: Exchange sauvegarde (PowerShell)
§ German: Exchange-Sicherung (PowerShell)
§ Japanese: Exchange ( PowerShell)

§ Portuguese: Backup Exchange (PowerShell)
§ Russian: Exchange (PowerShell)

§ Simplified Chinese: Exchange (PowerShell)
§ Spanish: Copia de seguridad Exchange (PowerShell)
Remarks
924
Remark Description
Exchange user account § This sensor requires Exchange user account permissions.
permissions
§ This sensor requires a user account that must be either in the
Exchange management role group View-Only Organization
Management or be in a group with the following assigned management
roles:
ú Monitoring
ú View-Only Configuration
ú View-Only Recipients
Remote PowerShell and § This sensor requires Remote PowerShell and Remote Exchange
Remote Exchange Management Shell on the target system and PowerShell on the probe
Management Shell system. Also make sure you have at least PowerShell 2.0 installed on
the probe system.
In larger environments, the default memory limit for the remote shell
might be insufficient. This might result in the error message The
WSMan provider host process did not return a proper response. In this
case, increase the memory limit for Remote PowerShell.
For more information, see the Knowledge Base: How do I enable and
use remote commands in Windows PowerShell? and How can I
increase memory for Remote PowerShell?
does PRTG require?
Parent device § This sensor requires that the parent device is the Exchange server (as
of version 2016) that hosts the database that you want to monitor.
FQDN § In the device settings of the Exchange server, provide the FQDN
instead of the IP address.
For more information, see the Knowledge Base: I have problems with
the PowerShell Exchange sensors, what can I do?
925
Remark Description
channels.
Knowledge Base § Knowledge Base: Where can I find more information about PowerShell
sensors?
probe device.
you add the sensor:
§ backup
§ exchange
§ powershell
Sensor Settings
Sensor Settings
926
Setting Description
Database The name of the database that this sensor monitors.
master node.
Sensor Display
Sensor Display
Setting Description


other above.
927
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Backup In Progress If a backup is running

§ Up status: No, Yes
Last Copy Backup The time since the last copy backup
Last Differential Backup The time since the last differential backup
Last Full Backup The time since the last full backup
Last Incremental Backup The time since the last incremental backup
More
KNOWLEDGE BASE
Where can I find more information about PowerShell sensors?
928
How do I enable and use remote commands in Windows PowerShell?

How can I increase memory for Remote PowerShell?

I have problems with the PowerShell Exchange sensors, what can I do?


My PowerShell sensor returns an error message. What can I do?

I get the error "WinRM cannot process the request" when I try to use a PowerShell sensor
929
7.8.40 Exchange Database (PowerShell) Sensor
The Exchange Database (PowerShell) sensor monitors database information of an Exchange server via
Remote PowerShell.
Exchange Database (Pow erShell) Sensor
List 934 .

§ Dutch: Exchange Database (PowerShell)
§ French: Exchange base de données (PowerShell)
§ German: Exchange-Datenbank (PowerShell)

§ Portuguese: Banco de dados Exchange (PowerShell)

§ Spanish: Base de datos Exchange (PowerShell)
Remarks
930
Remark Description
permissions
roles:
ú Monitoring
the probe system.
does PRTG require?
FQDN § In the device settings of the Exchange server, provide the FQDN
931
Remark Description
sensors?
§ Knowledge Base: How can I monitor additional values of Exchange
databases?
probe device.
you add the sensor:
§ database
§ exchange
§ powershell
Sensor Settings
Sensor Settings
932
Setting Description
AutoRemount Database Define if you want the sensor to try to automatically remount the
database if it is unmounted:
§ Try to remount
§ Do not try to remount, report the current reading
master node.
Sensor Display
Sensor Display
Setting Description

933
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Database Size The size of the database

Is Valid If the database is recognized as valid

§ Up status: Yes
§ Down status: Critical Issue, Major Issue, Non Recoverable
Mounted If the database is mounted
934
Channel Description
§ Up status: Yes
§ Down status: No
More
KNOWLEDGE BASE

How can I monitor additional values of Exchange databases?





935
7.8.41 Exchange Database DAG (PowerShell) Sensor
The Exchange Database DAG (PowerShell) sensor monitors the Database Availability Group (DAG)
status of a database on an Exchange server via Remote PowerShell.
Exchange Database DAG (Pow erShell) Sensor
List 940 .

§ Dutch: Exchange Database DAG (PowerShell)
§ French: Exchange base de données DAG (PowerShell)
§ German: Exchange-Datenbank DAG (PowerShell)
§ Japanese: Exchange DAG( PowerShell)

§ Portuguese: Banco de dados DAG Exchange (PowerShell)
§ Russian: DAG Exchange (PowerShell)

§ Simplified Chinese: Exchange DAG (PowerShell)
§ Spanish: Base de datos DAG Exchange (PowerShell)
936
Remarks
Remark Description
permissions
roles:
ú Monitoring
Valid DAG § This sensor requires that the Exchange server is part of a valid DAG.
For more information, see the Knowledge Base: Why doesn't PRTG
show available databases when adding the Exchange Database DAG
(PowerShell) sensor?
the probe system.
does PRTG require?
937
Remark Description
FQDN § This sensor requires the fully qualified domain name (FQDN) of the
Exchange server in the settings of the parent device.
§ In the device settings of the Exchange server, provide the FQDN
channels.
Target device § Make sure that the Exchange database is mounted on the target
device. Otherwise, you might not be able to properly add this sensor.
sensors?
§ Knowledge Base: How can I monitor additional values of Exchange
databases?
probe device.
you add the sensor:
§ dag
§ database
§ exchange
938
§ powershell
Sensor Settings
Sensor Settings
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description
939
Setting Description



other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Activation Suspended If the activation is suspended

§ Up status: No
§ Warning status: Yes
Active Copy The copy status

§ Up status: Active, Not Active
940
Channel Description
§ Warning status: Active But Not On The Preferred Server, Could Not
Read Activation Preference, Not Active But This Is The Preferred Server
Content Index State The content index status

§ Up status: Healthy, Not Supported In 2019
§ Warning status: Crawling
Copy Queue Length The number of items in the copy queue
Log Copy Queue If the log copy queue is increasing

Increasing
§ Up status: No
Log Replay Queue If the log replay queue is increasing

Increasing
§ Up status: No
Replay Queue Length The number of items in the replay queue
Single Page Restore The number of single page restores
Status The overall DAG status

§ Up status: Healthy, Mounted
§ Warning status: Disconnected and Healthy, Disconnected and

Resynchronizing, Dismounting, Initializing, Mounting, Resynchronizing,
Seeding, SeedingSource, SinglePageRestore, Suspended
§ Down status: Dismounted, Failed, Failed and Suspended, Service
Down
More
KNOWLEDGE BASE
941
Why doesn't PRTG show available databases when adding the Exchange Database DAG (PowerShell)
sensor?

How can I monitor additional values of Exchange databases?






942
7.8.42 Exchange Mail Queue (PowerShell) Sensor
The Exchange Mail Queue (PowerShell) sensor monitors the number of items in the outgoing mail queue
of an Exchange server via Remote PowerShell.
Exchange Mail Queue (Pow erShell) Sensor
List 947 .

§ Dutch: Exchange Mail Wachtrij (PowerShell)
§ French: Exchange file d'attente de messagerie (PowerShell)
§ German: Exchange-Nachrichtenwarteschlange (PowerShell)
§ Japanese: Exchange Mail ( PowerShell)

§ Portuguese: Fila de e-mails Exchange (PowerShell)

§ Spanish: Cola de correo Exchange (PowerShell)
Remarks
943
Remark Description
permissions
roles:
ú Monitoring
the probe system.
does PRTG require?
Authentication § This sensor only supports Kerberos authentication.
944
Remark Description
sensors?
§ Knowledge Base: What types of Exchange transport queues are there?
probe device.
you add the sensor:
§ exchange
§ mailqueue
§ powershell
Sensor Settings
Sensor Settings
945
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
946
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Poisonous Mails The number of poisonous mails
Queued Mails The number of queued mails

Retrying Mails The number of retrying mails
Unreachable Mails The number of unreachable mails
More
KNOWLEDGE BASE

What types of Exchange transport queues are there?
947





948
7.8.43 Exchange Mailbox (PowerShell) Sensor
The Exchange Mailbox (PowerShell) sensor monitors mailboxes of an Exchange server via Remote
PowerShell.
Exchange Mailbox (Pow erShell) Sensor
List 953 .

§ Dutch: Exchange Postbus (PowerShell)
§ French: Exchange boîte aux lettres (PowerShell)
§ German: Exchange-Postfach (PowerShell)
§ Japanese: Exchange Mailbox( PowerShell)
§ Portuguese: Caixa de correio Exchange (PowerShell)

§ Spanish: Buzón Exchange (PowerShell)
Remarks
949
Remark Description
Elevated rights § This sensor requires elevated rights for the user of this sensor on the
Exchange system. It is not sufficient to have administrative rights. For
more information, see the Knowledge Base: I have problems with the
PowerShell Exchange sensors, what can I do? (solution (2) in the
reply).
the probe system.
does PRTG require?
sensors?
950
Remark Description
probe device.
you add the sensor:
§ exchange
§ mailbox
§ powershell
Sensor Settings
Sensor Settings
Setting Description
Mailbox Name The name of the mailbox that this sensor monitors.
951
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description



other above.
procedure to do so.
952
Inherited Settings
Channel List
Channel Description
Item Count The number of items

Last Logon Time The time since the last mailbox login
Total Item Size The total size of items
More
KNOWLEDGE BASE




953

954
7.8.44 Exchange Public Folder (PowerShell) Sensor
The Exchange Public Folder (PowerShell) sensor monitors the public folders and subfolders of an
Exchange server via Remote PowerShell.
Exchange Public Folder (Pow erShell) Sensor
List 959 .

§ Dutch: Exchange Openbare Map (PowerShell)
§ French: Exchange dossier public (PowerShell)
§ German: Exchange Öffentlicher Ordner (PowerShell)

§ Portuguese: Pasta pública Exchange (PowerShell)

§ Spanish: Carpeta pública Exchange (PowerShell)
Remarks
955
Remark Description
permissions
roles:
ú Monitoring
the probe system.
does PRTG require?
956
Remark Description
sensors?
probe device.
you add the sensor:
§ exchange
§ powershell
§ publicfolder
Sensor Settings
Sensor Settings
957
Setting Description
Public Folder The name of the public folder that this sensor monitors.
master node.
Sensor Display
Sensor Display
Setting Description


other above.
958
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Item Count The number of items
Last Modification Time The time since the last access
Total Item Size The total size of items
More
KNOWLEDGE BASE


959


960
7.8.45 EXE/Script Sensor
The EXE/Script sensor runs an executable file (.exe) or a script (batch file, VBScript, PowerShell) on the
probe system. This option is available as part of the PRTG API.
If you want to execute a custom Windows Management Instrumentation Query Language (WQL)
script, use the WMI Custom 2493 sensor.
EXE/Script Sensor
List 969 .

§ Dutch: EXE/Script
§ French: Script/EXE
§ German: Programm/Skript
§ Japanese: EXE/
§ Portuguese: EXE/Script
§ Russian: EXE/
§ Simplified Chinese: EXE/
§ Spanish: EXE/Script
Remarks
961
Remark Description
Remote PowerShell § This sensor requires that Remote PowerShell is enabled on the target
system and PowerShell 3.0 on both the probe system and the target
system.
§ Also make sure that you have at least PowerShell 3.0 installed on both
the probe system and the target system.
If you receive an error message regarding issues with the WinRM

connection, make sure that remote commands have been enabled in
PowerShell. For more information, see the Knowledge Base: How do I
enable and use remote commands in Windows PowerShell?
File storage § The sensor requires the executable or script file to be stored on the
probe system. In a cluster, copy the file to every cluster node.
does PRTG require?
Knowledge Base § Knowledge Base: What is the Mutex Name in the EXE/Script sensor
settings?
§ Knowledge Base: How can I test if parameters are correctly transmitted
to my script when using an EXE/Script sensor?
§ Knowledge Base: How can I show special characters with EXE/Script
sensors?
probe device.
962
Remark Description
Custom scripts on § To run a script in PRTG on this sensor, you have to open Windows
Windows Consumer PowerShell with administrator rights and enter the following command:
Editions powershell.exe Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -
Scope LocalMachine
Add Sensor
Setting Description
Channel Name Enter a name for the channel. Enter a string. This is for display purposes
only.
You can change this value later in the channel settings of this
sensor.
Unit String Enter the unit for the values that this sensor returns. Enter a string.
PRTG uses the unit string for display purposes and shows it in
graphs, data tables, and gauges.
sensor.
you add the sensor:
§ exesensor
963
Click to interrupt the inheritance.
Setting Description
964
Setting Description
Sensor Settings
Sensor Settings
Setting Description
EXE/Script Select an executable file from the list. The sensor executes it with every
scanning interval.
The list contains all files in the corresponding \Custom Sensors\EXE
subfolder of the PRTG program directory on the probe system. For a file
to appear in this list, store the file ending in .bat, .cmd, .exe, .ps1, or .vbs
into this subfolder.
965
Setting Description
To show the expected sensor values and states, your files must use
the correct format for the returned values (in this case,
value:message to standard output). The exit code of the file determines
the sensor status.
If you use a PowerShell script (.ps1) and if the PowerShell Security
Enhancement experimental feature is enabled, scripts that use the
write-host cmdlet to provide their output to PRTG do not work. Use the
write-output cmdlet instead.
If you use custom sensors on the cluster probe, copy your files to
every cluster node.
For more information on how to create custom sensors and for the
return format, see section Custom Sensors.
Parameters If your executable or script file catches command-line parameters, you

can define them here. You can use placeholders as well. Enter a string or
leave the field empty.
For a full list of all placeholders, see section Custom Sensors.
You cannot use environmental variables in this setting. Define

environmental variables directly in your script or update the
environmental variable values on your system.
You need to escape special characters and whitespaces in your

parameters and surround them with double quotation marks ("). See
section Escape Special Characters and Whitespaces in Parameters for
details.
Environment Select whether PRTG command-line parameters are also available as

environment parameters:
§ Default environment: Do not provide values of PRTG placeholders in the
environment. Select this secure option if you are not sure.
§ Set placeholders as environment values: Define if command-line
parameters of PRTG are also available as environment parameters in
your executable or script. For example, you can read and use the
current host value of the parent device from within your script. This
option can pose a security risk because credentials are exposed in
several variables. It is not possible to use the environment variables in
the parameters setting for batch scripts (.bat) for security reasons.
For a full list of all available variables, see section Custom Sensors.
Security Context Define the Windows user account that the sensor uses to run the
executable or script file:
966
Setting Description
§ Use security context of PRTG probe service: Run the file under the
same Windows user account that the probe system runs under. By
default, this is the Windows system user account.
§ Use Windows credentials of parent device: Use the Windows user
account in the parent device settings.
Mutex Name Define a mutual exclusion (mutex) name for the process. Enter a string or
PRTG executes all EXE/Script sensors that have the same mutex
serially, not simultaneously. This is useful if you use a lot of sensors
and you want to avoid high resource usage caused by simultaneously
running processes.
See the Knowledge Base: What is the Mutex Name in the
EXE/Script sensor settings?
Value Type Define the type of the values that your executable or script file returns:
§ Integer: An integer is expected as return value. If the script returns a
float, PRTG displays the value 0.
§ Float: A float is expected as return value, with a dot (.) between the
predecimal position and the decimal places.
The sensor also displays integers unless they produce a buffer
overflow.
§ Counter: Your script returns an integer that increases. PRTG shows the
difference between the values of two sensor scans.
A counter must return an integer. It does not support float values.
The sensor does not support string values.
If Value Changes Define what the sensor does when its value changes:

change.
967
Setting Description
Result Handling Define what the sensor does with the result that the executable file gives
back:
scanning interval.
§ Store result in case of error: Store the last sensor result only if the
sensor shows the Down status.
Select this option if you do not want failures to be overwritten by a
following success of the script.
master node.
Sensor Display
Sensor Display
Setting Description


968
Setting Description
other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Execution Time The execution time

[Value] The value that the executable file or script file returns in one channel
For more information about the return value format, see section
Custom Sensors.
More
KNOWLEDGE BASE
What is the Mutex Name in the EXE/Script sensor settings?

How can I test if parameters are correctly transmitted to my script when using an EXE/Script sensor?
969
How can I show special characters with EXE/Script sensors?



For which sensor types do you recommend at least Windows Server 2016 and why?
970
7.8.46 EXE/Script Advanced Sensor
The EXE/Script Advanced sensor runs an executable file (.exe) or a script (batch file, VBScript,
PowerShell) on the probe system. This option is available as part of the PRTG API.
The return value of this sensor must be valid Extensible Markup Language (XML) or JavaScript
Object Notation (JSON).
If you want to execute a custom Windows Management Instrumentation Query Language (WQL)
script, use the WMI Custom 2493 sensor.
EXE/Script Advanced Sensor
List 978 .

§ Dutch: EXE/Script Geavanceerd
§ French: Script/EXE avancé
§ German: Programm/Skript (Erweitert)
§ Japanese: EXE/ ( )
§ Portuguese: EXE/Script avançado
§ Russian: EXE/
§ Simplified Chinese: EXE/
971
§ Spanish: EXE/Script (avanzado)
Remarks
Remark Description
system.
File storage § The sensor requires the executable or script file to be stored on the
probe system. In a cluster, copy the file to every cluster node.
does PRTG require?
settings?
§ Knowledge Base: How can I test if parameters are correctly transmitted
to my script when using an EXE/Script sensor?
§ Knowledge Base: How can I show special characters with EXE/Script
sensors?
972
Remark Description
§ Knowledge Base: How can I use meta-scans for custom EXE/Script

sensors?
probe device.
Custom scripts on § To run a script in PRTG on this sensor, you have to open Windows
Windows Consumer PowerShell with administrator rights and enter the following command:
Editions powershell.exe Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -
Scope LocalMachine
you add the sensor:
§ xmlexesensor

973
Setting Description
974
Sensor Settings
Sensor Settings
Setting Description
EXE/Script Select an executable file from the list. The sensor executes it with every
scanning interval.
The list contains all files in the corresponding \Custom Sensors\EXE
subfolder of the PRTG program directory on the probe system. For a file
to appear in this list, store the file ending in .bat, .cmd, .exe, .ps1, or .vbs
into this subfolder.
To show the expected values and sensor states, your files must
return the expected XML or JSON format to standard output. Values
and message must be embedded in the XML or JSON.
If you use a PowerShell script (.ps1) and if the PowerShell Security

Enhancement experimental feature is enabled, scripts that use the
write-host cmdlet to provide their output to PRTG do not work. Use the
write-output cmdlet instead.
every cluster node.
Parameters If your executable or script file catches command-line parameters, you

can define them here. You can use placeholders as well. Enter a string or
975
Setting Description
You cannot use environmental variables in this setting. Define

environmental variables directly in your script or update the
environmental variable values on your system.

details.
Environment Select whether PRTG command-line parameters are also available as

environment parameters:
§ Default environment: Do not provide values of PRTG placeholders in the
environment. Select this secure option if you are not sure.
§ Set placeholders as environment values: Define if command-line
parameters of PRTG are also available as environment parameters in
your executable or script. For example, you can read and use the
current host value of the parent device from within your script. This
option can pose a security risk because credentials are exposed in
several variables. It is not possible to use the environment variables in
the parameters setting for batch scripts (.bat) for security reasons.
For a full list of all available variables, see section Custom Sensors.
Security Context Define the Windows user account that the sensor uses to run the
executable or script file:
§ Use security context of PRTG probe service: Run the file under the
same Windows user account that the probe system runs under. By
default, this is the Windows system user account.
account in the parent device settings.
PRTG executes all EXE/Script sensors that have the same mutex
serially, not simultaneously. This is useful if you use a lot of sensors
and you want to avoid high resource usage caused by simultaneously
running processes.
976
Setting Description
Result Handling Define what the sensor does with the result that the executable file gives
back:
scanning interval.
Select this option if you do not want failures to be overwritten by a
following success of the script.
master node.
Sensor Display
Sensor Display
Setting Description


977
Setting Description
other above.
procedure to do so.
The Stack Unit setting for stacking graphs only works if you explicitly
define the same <unit> for at least two channels. For more
information about sensor settings, see section Custom Sensors.
Inherited Settings
Channel List
Channel Description
[Value] The values that the executable file or script file returns in several channels
Custom Sensors.
More
KNOWLEDGE BASE

978

How can I use meta-scans for custom EXE/Script sensors?



979
7.8.47 File Sensor
The File sensor monitors a file located on the local disk on the probe system, parent device, or a file that
is accessible via Server Message Block (SMB). You can monitor changes to the file content and file time
stamp.
In contrast to the Folder 993 sensor, you can also monitor changes to the actual content of a file.
File Sensor
List 984 .

§ Dutch: Bestand
§ French: Fichier
§ German: Datei
§ Japanese:
§ Portuguese: Arquivo
§ Russian:
§ Spanish: Archivo
Remarks
980
Remark Description
LanmanServer service § This sensor requires that the LanmanServer service runs on the target
system.
The display name of the service is Server.

§ To enable the service, log in to the respective system and open the
services manager (for example, via services.msc). In the list, find the
respective service and set its Start Type to Automatic.
FQDN § Try the fully qualified domain name (FQDN) of the target system if the
sensor does not get a connection with the IP address.
Knowledge Base § Knowledge Base: What can I do if PRTG doesn't succeed with
monitoring a share? PE029 PE032
§ Knowledge Base: Can I use placeholders in file names to monitor log
files?
probe device.
you add the sensor:
§ filesensor
981
Sensor Specific
Sensor Specific
Setting Description
File Name Enter the full path to the file that this sensor monitors. For example, enter
C:\Windows\file.txt. to monitor a file on the probe system.
If you use a local path, the sensor only looks for the target file on the
probe system, not on the parent device. To monitor a file on the parent
device, use the dollar sign ($) like C$\User\username\file.txt.
If the file is located on a network device, use the Universal Naming
Convention (UNC) path without the server part (only enter
share\folder\file.txt). The sensor inherits the server part (\\server\) from the
parent device settings. Enter a valid path and file name.
To monitor Windows shares, the LanmanServer service must run on
the target system.
The File sensor supports wildcards (*). For example, you can enter
C:\Windows\*.txt as File Name and select Show down status if file
exists below if you want the sensor to show the Down status if a .txt file
exists in the defined directory.
Sensor Behavior Define when the sensor shows the Down status:
§ Show down status if file does not exist: Show the Down status if the file
does not exist.
§ Show down status if file exists: Show the Down status if the file does
exist.
If Content Changes Define what the sensor does if the content of the file changes (based on a
checksum):
982
Setting Description

change.
If Time Stamp Changes Define what the sensor does if the time stamp of the file changes:

change.
Sensor Display
Sensor Display
Setting Description


other above.
983
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
File Size The file size
Last Modified The time since the last modification of the file
The sensor shows a negative value if the date of a modified file is in
the future.
More
KNOWLEDGE BASE
What can I do if PRTG doesn't succeed with monitoring a share? PE029 PE032
Can I use placeholders in file names to monitor log files?

984
985
7.8.48 File Content Sensor
The File Content sensor checks a text file (for example, a log file) for certain strings.
Additionally, this sensor quotes matching lines in the sensor message.
File Content Sensor
List 991 .

§ Dutch: Bestands inhoud
§ French: Contenu du fichier
§ German: Datei-Inhalt
§ Japanese:
§ Portuguese: Conteúdo de arquivo
§ Russian:
§ Spanish: Contenido de archivo
Remarks
986
Remark Description
system.

UTF-16 encoded files § This sensor does not support UTF-16 encoded files. Try a custom
sensor like the EXE/Script 961 sensor or the EXE/Script Advanced 971
sensor.
Binary files § This sensor does not officially support binary files. If you want to
monitor them anyway, select Always transmit the entire file in the
sensor settings 989 .
Unix line feeds § This sensor supports Unix line feeds.
Linux system § To monitor files on a Linux system, the folder must be accessible via
Server Message Block (SMB).
FQDN § Try the fully qualified domain name (FQDN) of the target system if the
sensor does not get a connection with the IP address.
probe device.
987
you add the sensor:
§ filesensor
Sensor Specific
Sensor Specific
Setting Description
File Name Enter the full path to the file that this sensor monitors. For example, enter
C:\Windows\file.txt. to monitor a file on the probe system.
If you use a local path, the sensor only looks for the target file on the
probe system, not on the parent device. To monitor a file on the parent
device, use the dollar sign ($) like C$\User\username\file.txt.
If the file is located on a network device, use the Universal Naming
Convention (UNC) path without the server part (only enter
share\folder\file.txt). The sensor inherits the server part (\\server\) from the
parent device settings. Enter a valid path and file name.
the target system.
To monitor Linux files, the folder with these files must be accessible
via SMB.
988
Setting Description
Note that it might produce a high amount of network traffic if you

define that PRTG queries an entire file on your network with every
scanning interval.
Search String Define the string that you want to search the file for. You can enter a
simple string in plain text or a regular expression (regex).
The search string must be case-sensitive.
Search Method Define the method with which you want to provide the search string:
§ Simple string search (default): Search for a simple string in plain text.
The characters * and ? work as placeholders. * stands for no number

or any number of characters and ? stands for exactly one character.
You cannot change this behavior. The literal search for these characters
is only possible with a regex.
§ Regular expression: Search with a regex.
The pattern must be in one line and only the last matching line is
returned.

File Transmission Define in which way the sensor transmits the target file to PRTG:
Handling
§ Only transmit new lines at the end of the file (default): Send the entire
file to PRTG only with the first scanning interval. With the following
scanning intervals, the sensor only transmits new lines at the end of
the file. It does not send old lines but it still counts them. This option
improves the performance of the sensor.
This option is in beta status. Do not expect that it works as
expected in every usage scenario.
§ Always transmit the entire file: Send the entire file to PRTG with every
scanning interval. If this results in too much traffic on the target system,
we recommend that you choose Only transmit new lines at the end of
the file (default) instead.
This sensor can only transmit new lines in the following cases:
§ the file is bigger than in the previous scanning interval, and
§ the last line in the file is still in the same place in the file.
This sensor supports Windows and Linux line endings (CRLF or. LF).
File Encoding Specify the encoding of the file that this sensor monitors:
§ Windows-1252 (default)
989
Setting Description
§ UTF-8
§ UTF-16
Sensor Behavior Define the condition for which the sensor shows the Warning status:
§ Show warning status when the string is not found (default): Show the
Warning status if there is no match. Otherwise it remains in the Up
status.
§ Show warning status when the string is found: Show the Warning
status if there is a match. Otherwise it remains in the Up status.
If Value Changes Define what the sensor does if the value of the Last Occurrence (Line)
channel changes:

change.
This sensor does not trigger the notification when the number of
Matches changes.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
990
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
991
Channel Description
Last Occurrence (Line) The line number of the last match
Matches The number of matches
More
KNOWLEDGE BASE

992
7.8.49 Folder Sensor
The Folder sensor monitors a folder via Server Message Block (SMB). You can monitor file changes and
file ages.
Folder Sensor
List 998 .

§ Dutch: Map
§ French: Dossier
§ German: Ordner
§ Japanese:
§ Portuguese: Pasta
§ Russian:
§ Spanish: Carpeta
Remarks
993
Remark Description
system.

File count § This sensor counts all files in a folder, including hidden files.
probe device.
Add Sensor
Setting Description
File Age Check Specify if the sensor monitors the folder for certain file ages and shows a
corresponding status:
§ Do not check: Do not check the age of the files in the folder:
§ Show warning status if older: Set the sensor to the Warning status if
one of the files in the folder is older than a specific limit unit.
§ Show down status if older: Set the sensor to the Down status if one of
the files in the folder is older than a specific limit unit.
§ Show warning status if younger: Set the sensor to the Warning status if
one of the files in the folder is younger than a specific limit unit.
§ Show down status if younger: Set the sensor to the Down status if one
of the files in the folder is younger than a specific limit unit.
You can change this setting later via the Limits section in the
channel settings of Newest File and Oldest File.
994
Setting Description
File Age Limit This setting is only visible if you select a file age check above.
Enter the age of a file in the folder that triggers the sensor status change
if the age falls below a specific value or if it is exceeded. Enter an integer.
Define the limit unit below.
File Age Limit Unit This setting is only visible if you select a file age check above.
Specify the unit for the file age value:

§ Days: Select this option if the File Age Limit is a number of days.
§ Hours: Select this option if the File Age Limit is a number of hours.
§ Minutes: Select this option if the File Age Limit is a number of minutes.
you add the sensor:
§ foldersensor
995
Folder Monitor
Folder Monitor
Setting Description
Folder Name Enter the full path to the folder that this sensor monitors. For example,
enter C:\Windows to monitor a folder on the probe system.
If you use a local path, the sensor only looks for the target folder on the
probe system and not on the parent device. To monitor a folder on the
parent device, use a dollar sign ($) in the path. For example, enter C$:
\Windows.
If the folder is located on a network device, use the Universal Naming
Convention (UNC) path without the server part (only enter share\folder).
The sensor inherits the server part (\\server\) from the parent device
settings. Enter a valid path name.
the target system.
Recurse Subfolders Specify if the sensor includes subfolders in the folder monitoring:
§ Do not recurse subfolders (default): Only monitor the folder. Do not
monitor its subfolders.
§ Monitor the folder and its subfolders (recursive): Monitor the folder and
all of its subfolders.
If you recurse subfolders in large directories that have a high
number of branches, this might cause timeout errors or
performance issues.
If Content Changes Define what the sensor does if the content or file name of the folder
changes, or if there are new or deleted files:

change.
996
Setting Description
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
997
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
998
Channel Description
File Count The number of files in the folder

The sensor counts all files in a folder, including hidden files.
Folder Size The folder size

Newest File The time since the newest modification of a file in the folder (newest file)
the future.
Oldest File The time since the oldest modification of a file in the folder (oldest file)
More
KNOWLEDGE BASE

999
7.8.50 FortiGate System Statistics Sensor
The FortiGate System Statistics sensor monitors the system health of a Fortinet FortiGate firewall via
the Representational State Transfer (REST) application programming interface (API).
FortiGate System Statistics Sensor
List 1003 .

§ Dutch: FortiGate Systeem Statistieken
§ French: Statistiques du système FortiGate
§ German: FortiGate-Systemstatistiken
§ Japanese: FortiGate
§ Portuguese: Estatísticas do sistema FortiGate
§ Russian: FortiGate
§ Simplified Chinese: FortiGate
§ Spanish: Estadísticas del sistema FortiGate
1000
Remarks
Remark Description
Credentials § This sensor requires credentials for FortiGate.
channels.
you add the sensor:
§ firewall
§ fortigate
§ fortinet
§ fortios
§ systemstatistics
1001
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
1002
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Conserve Mode The conserve mode status

§ Up status: Inactive
§ Down status: Active

§ Upper error limit: 90%
1003
Channel Description
Memory Usage The memory usage (%)

§ Upper warning limit: 82%
Session Rate The number of sessions
Sessions The total number of sessions
Uptime The uptime
More
KNOWLEDGE BASE

1004
7.8.51 FortiGate VPN Overview Sensor
The FortiGate VPN Overview sensor monitors the virtual private network (VPN) connections of a Fortinet
FortiGate system via the Representational State Transfer (REST) application programming interface
(API).
FortiGate VPN Overview Sensor
List 1008 .

§ Dutch: FortiGate VPN Overzicht
§ French: FortiGate VPN vue d'ensemble
§ German: FortiGate VPN-Übersicht
§ Japanese: FortiGate VPN
§ Portuguese: Visão geral da VPN FortiGate
§ Russian: VPN FortiGate

§ Simplified Chinese: FortiGate VPN
§ Spanish: Resumen de la VPN FortiGate
Remarks
1005
Remark Description
Credentials § This sensor requires credentials for FortiGate.
you add the sensor:
§ fortigate
§ fortinet
§ fortios
§ vpn
FortiGate Specific
FortiGate Specific
1006
Setting Description
Ignored VPNs Enter the name of any VPN that this sensor should ignore. Ignored VPNs
do not affect the status of the sensor. Enter one VPN per line.
The name that you enter must be case-sensitive.
Sensor Display
Sensor Display
Setting Description

other above.
procedure to do so.
1007
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Connected SSL Clients The number of SSL clients that are connected
1008
Channel Description
IPsec Tunnels "Down" The number of IPsec tunnels that are down
IPsec Tunnels "Up" The number of IPsec tunnels that are up
More
KNOWLEDGE BASE

1009
7.8.52 FTP Sensor
The FTP sensor monitors file servers via the File Transfer Protocol (FTP) and FTP over SSL (FTPS).
This sensor also shows the response message of the server in the sensor message.
FTP Sensor
List 1014 .

§ Dutch: FTP
§ French: FTP
§ German: FTP
§ Japanese: FTP
§ Portuguese: FTP
§ Russian: FTP
§ Simplified Chinese: FTP
§ Spanish: FTP
Remarks
1010
Remark Description
you add the sensor:
§ ftpsensor
Sensor Specific
Sensor Specific
Setting Description
1011
Setting Description
Port Enter the number of the FTP port that the sensor tries to connect to.
Enter an integer. The default port number is 21.
If the connection is unsuccessful, try a different port number.
FTP Mode Define the FTP connection mode that the sensor uses for the connection
to the FTP server:
§ Active mode: Try to establish a command channel by connecting to
FTP port 21 and a data channel by connecting to FTP port 20. If you
cannot establish a connection, use the passive mode.
§ Passive mode (default): Try to establish a command channel by
connecting to FTP port 21 and send a command to the FTP server in
order to receive an FTP port for the data channel.
Connection Security
Connection Security
Setting Description
Transport-Level Security Specify if the sensor uses connection security:

§ Use transport-level security if available: This sensor tries to connect via
Secure Sockets Layer (SSL)/Transport Layer Security (TLS). It
automatically determines whether to connect via the explicit mode or
the implicit mode. If the server does not support SSL/TLS, the sensor
tries to connect without connection security and shows the Up status if
this works.
§ Enforce transport-level security: The connection must be established
via SSL/TLS (in the explicit mode or the implicit mode). Otherwise, this
§ Do not use transport-level security (default): The sensor connects to the
FTP server without connection security.
See the sensor logs to see which method the sensor previously used
to connect to the FTP server.
1012
Authentication
Authentication
Setting Description
User Name Enter a user name for the FTP login. Enter a string or leave the field
empty.
The default user name is anonymous. If the sensor cannot log on to
the FTP server with this user name (or a different user name that you
define), the sensor message shows that the credentials are incorrect but
the sensor remains in the Up status.
Password Enter a password for the FTP login. Enter a string or leave the field
empty.
If the sensor cannot log on to the FTP server with this password, the
sensor message shows that the credentials are incorrect but the
sensor remains in the Up status.
scanning interval.
master node.
1013
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
1014
Channel Description
More
KNOWLEDGE BASE

1015
7.8.53 FTP Server File Count Sensor
The FTP Server File Count sensor logs in to a File Transfer Protocol (FTP) server and can monitor
changes to files.
FTP Server File Count Sensor
List 1021 .

§ Dutch: FTP Server File Aantal
§ French: Serveur FTP compteur de fichiers
§ German: FTP-Server Dateienanzahl
§ Japanese: FTP
§ Portuguese: Contagem de arquivos servidor FTP
§ Russian: FTP-
§ Simplified Chinese: FTP
§ Spanish: Número de archivos en servidor FTP
Remarks
1016
Remark Description
system.
does PRTG require?
you add the sensor:
§ ptfsensor
1017
Sensor Settings
Sensor Settings
Setting Description
FTP Mode Define the FTP connection mode that the sensor uses for the connection
to the FTP server:
§ Active mode: If you cannot establish a connection, use the passive
mode.
§ Passive mode
Check Method Define how to access the FTP server directory that this sensor monitors:
§ URL: This sensor uses a URL of an FTP server to access the target
directory. Define the URL below.
§ Folder on parent device: This sensor uses the IP address or Domain
Name System (DNS) name of the parent device and monitors a folder
on this device. Define the folder below.
1018
Setting Description
FTP URL This setting is only visible if you select URL above.
Enter the URL that this sensor checks. The URL can look like this:
ftp://10.0.0.1/upload
If you use this method, this sensor does not use the IP Address/DNS
Name of the parent device.
You can add a port number to the URL by using a colon, for example
ftp://10.0.0.1/upload:21.
FTP Port This setting is only visible if you select Folder on parent device above.
Enter the number of the port to which this sensor connects. The default
port is 21.
FTP Folder This setting is only visible if you select Folder on parent device above.
Enter the name of the folder on the parent device that this sensor
monitors, for example upload.
Recurse Subfolders This setting is only visible if you select Folder on parent device above.
Define if the sensor additionally monitors the subfolders of the FTP folder:
performance issues.
User Name Enter the user name for the FTP server login. Enter a string.
Password Define the password for the FTP server login. Enter a string.
File Count Define which files the sensor counts:

§ Total number of files: Always show the total number of all files in the
folder.
§ Only new files: Only show the number of new files since the last
scanning interval. You can define the frequency of sensor scans in
section Scanning Interval 1021 .
With every scanning interval, the sensor considers any new files
from the previous scanning interval to be old.
1019
Setting Description
Connection Security Define the security of the connection:

§ Do not use transport-level security (default): The sensor connects
§ Enforce transport-level security: The sensor establishes the connection
to the FTP server via Secure Sockets Layer (SSL)/Transport Layer
Security (TLS) in explicit mode.
This sensor only supports SSL/TLS in explicit mode.

change.
Debug Options
Debug Options
Setting Description
Store the last sensor result in the \Logs\sensors subfolder of the PRTG
data directory on the probe system. The file names are Result of Sensor
[ID].txt and Result of Sensor [ID].Data.txt. This setting is for debugging
purposes. PRTG overwrites these files with each scanning interval.
master node.
1020
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
1021
Channel Description
Files The number of files that are available in the directory listing
More
KNOWLEDGE BASE


1022
7.8.54 HL7 Sensor
The HL7 sensor monitors the availability of Health Level 7 (HL7) interfaces. It sends an HL7 message to
the target device and checks for a valid response.
You can define your own messages in HL7 format as .hl7 files in the PRTG program directory. This
sensor sends them to the HL7-capable system with each scanning interval.
HL7 Sensor
List 1028 .

§ Dutch: HL7
§ French: HL7
§ German: HL7
§ Japanese: HL7
§ Portuguese: HL7
§ Russian: HL7
§ Simplified Chinese: HL7
§ Spanish: HL7
Remarks
1023
Remark Description
does PRTG require?
channels.
you add the sensor:
§ dicom
§ hl7
HL7 Connection
HL7 Connection
1024
Setting Description
Port Enter the port of the HL7 interface that the sensor uses for the
connection. The default port is 1204.
HL7 Message Specific
HL7 Message Specific
Setting Description
Message Header Define if you want to use the default message header (MSH) as defined in
the selected .hl7 message file or if you want to override certain headers:
§ Default message header: Send the MSH as defined in the .hl7
message file.
§ Override message header: Define a custom MSH below that overrides

the MSH in the .hl7 message file.
Sending Application This setting is only visible if you select Override message header above.
Enter the name of the sending application, for example, PRTG. It

overrides the default value in the message. Enter a string.
Sending Facility This setting is only visible if you select Override message header above.
Enter the name of the sending facility. It overrides the default value in the
message. Enter a string.
Receiving Application This setting is only visible if you select Override message header above.
Enter the name of the receiving application. It overrides the default value in
the message. Enter a string.
1025
Setting Description
Receiving Facility This setting is only visible if you select Override message header above.
Enter the name of the receiving facility. It overrides the default value in the
HL7 Message Select an .hl7 file from the list. This sensor sends it to the target device
with every scanning interval.
The list shows all files that are available in the \Custom Sensors\hl7
subfolder of the PRTG program directory on the probe system. For files to
appear in this list, store them in this subfolder with the extension .hl7.
To be accepted by the HL7 interface, your files must have the
expected HL7 message format. PRTG comes with two sample .hl7
message files that you can use to test your HL7 monitoring and to have a
look at the expected format. These files are in the \Custom Sensors\hl7
subfolder.
You can override certain headers using the Message Header sensor
setting.
Debug Options
Debug Options
Setting Description
1026
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
1027
Channel List
Channel Description
ACK Status The acknowledgment (ACK) status

§ Up status: Accept
§ Down status: Error, Reject
Message Control ID OK The message control ID status

§ Up status: Yes
§ Down status: No

More
KNOWLEDGE BASE


1028
7.8.55 HPE 3PAR Common Provisioning Group Sensor
The HPE 3PAR Common Provisioning Group sensor monitors the capacity of a Common Provisioning
Group (CPG) on an HPE 3PAR storage system.
HPE 3PAR Common Provisioning Group Sensor
List 1033 .

§ Dutch: HPE 3PAR Common Provisioning Group
§ French: HPE 3PAR groupe de provisionnement commun
§ German: HPE 3PAR Common Provisioning-Gruppe
§ Japanese: HPE 3PAR
§ Portuguese: Grupo de provisionamento comum do HPE 3PAR
§ Russian: HPE 3PAR

§ Simplified Chinese: HPE 3PAR
1029
§ Spanish: Grupo de suministro común HPE 3PAR
Remarks
Remark Description
Credentials § This sensor requires credentials for HPE 3PAR.
channels.
Knowledge Base § Knowledge Base: Where can I find the Web Services API (WSAPI) port
for the connection to the HPE 3PAR system?
you add the sensor:
§ cpg
§ hpe
§ hpe3par
§ rest
1030
HPE 3PAR Specific
HPE 3PAR Specific
Setting Description
Name The name of the CPG that this sensor monitors.
ID The ID of the CPG that this sensor monitors.
Virtual Domain The virtual domain to which the CPG that this sensor monitors belongs.
Sensor Display
Sensor Display
Setting Description

1031
Setting Description

other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
1032
Channel List
Channel Description
Logical Space Free The free logical space
Logical Space Free % The free logical space (%)
Logical Space Total The allocated logical space
Logical Space Used The space that is already in use
Snapshot Space Free The free snapshot space
Snapshot Space Free % The free snapshot space (%)
Snapshot Space Total The allocated snapshot space
Snapshot Space Used The snapshot space that is already in use
State The CPG status

§ Up status: Normal
§ Warning status: Degraded
User Space Free The free user space
User Space Free % The free user space (%)
User Space Total The allocated user space
1033
Channel Description
User Space Used The user space that is already in use
More
KNOWLEDGE BASE

1034
7.8.56 HPE 3PAR Drive Enclosure Sensor
The HPE 3PAR Drive Enclosure sensor monitors a drive enclosure of an HPE 3PAR storage system.
HPE 3PAR Drive Enclosure Sensor
List 1039 .

§ Dutch: HPE 3PAR Schijfbehuizing
§ French: HPE 3PAR boîtier de lecteurs
§ German: HPE 3PAR Laufwerksgehäuse
§ Portuguese: Gabinete de unidades do HPE 3PAR

§ Spanish: Gabinete de una unidad de disco HPE 3PAR
1035
Remarks
Remark Description
you add the sensor:
§ enclosure
§ hpe
§ hpe3par
§ ssh
1036
HPE 3PAR Specific
HPE 3PAR Specific
Setting Description
ID The ID of the drive enclosure that this sensor monitors.
Enclosure Name The name of the drive enclosure that this sensor monitors.
Drive Count The number of drives in the enclosure that this sensor monitors.
Model The model of the drive enclosure that this sensor monitors.
Form Factor The form factor of the drive bays of the enclosure that this sensor
monitors.
Sensor Display
Sensor Display
Setting Description
1037
Setting Description



other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
1038
Inherited Settings
Channel List
Channel Description
Average Drive The average temperature of all drives in the drive bay
Temperature
§ Upper error limit: 60°C
§ Upper warning limit: 50°C
Drives The drives status

Highest Drive The highest temperature of all drives in the drive bay
Temperature
Interface Cards The interface cards status

1039
Channel Description
Lowest Drive The lowest temperature of all drives in the drive bay
Temperature
Power Supplies The power supplies status

State The drive enclosure status

More
KNOWLEDGE BASE

1040
7.8.57 HPE 3PAR Virtual Volume Sensor
The HPE 3PAR Virtual Volume sensor monitors the capacity of a virtual volume on an HPE 3PAR
storage system.
HPE 3PAR Virtual Volume Sensor
List 1045 .

§ Dutch: HPE 3PAR Virtueel Volume
§ French: HPE 3PAR volume virtuel
§ German: HPE 3PAR Virtual Volume
§ Portuguese: Volume virtual HPE 3PAR
1041
§ Spanish: Volumen virtual HPE 3PAR
Remarks
Remark Description
you add the sensor:
§ hpe
§ hpe3par
§ rest
§ virtualvolume
1042
HPE 3PAR Specific
HPE 3PAR Specific
Setting Description
Name The name of the virtual volume that this sensor monitors.
Provisioning Type The provisioning type of the virtual volume that this sensor monitors.
Volume Type The volume type of the virtual volume that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


1043
Setting Description
other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
1044
Channel List
Channel Description
Snapshot Space Free The free snapshot space
Snapshot Space Free % The free snapshot space (%)
Snapshot Space The reserved snapshot space

Reserved
Snapshot Space Used The snapshot space that is already in use
State The overall virtual volume status

Total Space The total space
Total Space Free The total free space
Total Space Free % The total free space (%)
Total Space Reserved The total reserved space
Total Space Used The total space that is in use
User Space Free The free user space
User Space Free % The free user space (%)
1045
Channel Description
User Space Reserved The reserved user space
User Space Used The user space that is already in use
More
KNOWLEDGE BASE

1046
7.8.58 HTTP Sensor
The HTTP sensor monitors a web server using HTTP.
You can use this sensor to monitor if a website or a specific website element is reachable.
HTTP Sensor
List 1052 .

§ Dutch: HTTP
§ French: HTTP
§ German: HTTP
§ Japanese: HTTP
§ Portuguese: HTTP
§ Russian: HTTP
§ Simplified Chinese: HTTP
§ Spanish: HTTP
Remarks
1047
Remark Description
SRP ciphers § This sensor does not support Secure Remote Password (SRP) ciphers.
Knowledge Base § Knowledge Base: My HTTP sensors fail to monitor websites which use
SNI. What can I do?
§ Knowledge Base: Which HTTP status code leads to which HTTP
sensor status?
you add the sensor:
§ httpsensor
1048
HTTP Specific
HTTP Specific
Setting Description
URL Enter the URL that the sensor connects to.

If you enter an absolute URL, the sensor uses this address independently
of the IP Address/DNS Name setting of the parent device. You can enter
the URL of a web page (to measure the loading time of the page's source
code), or enter the URL of an image or of a page asset to measure this
element's availability and loading time.
The URL must be URL encoded.
If you monitor an image or a page asset, this can create a high
amount of memory load. We recommend that the size of the
elements that you want to monitor does not exceed 200 MB.
Replacement 1052 .
Request Method Select an HTTP request method to determine how the sensor requests the
URL:
§ GET (default): Directly request the website.
We recommend that you use this setting for a simple check of the
web page.
1049
Setting Description

If you select this setting, you must enter the data in the Postdata
field below.
If a POST request is redirected, all further requests are GET
(default) requests.
§ HEAD: Only request the HTTP header from the server without the actual
web page.
Although this saves bandwidth because it transfers less data, we
do not recommended that you use this. This is because the
measured request time is not the one that your users experience and
you might not be notified of slow results or timeouts.

No Extensible Markup Language (XML) is allowed here.
Content Type This setting is only visible if you select POST above.
Define the content type of the POST request:

§ Default (application/x-www-form-urlencoded): Use the default content
type to encode the form data set for submission to the server.
§ Custom: Use a custom content type. Enter the content type below.
Custom Content Type This setting is only visible if you select Custom above.
Define the custom content type, for example, XML, JavaScript Object
Notation (JSON), or HTTP.
Server Name Indication The Server Name Indication (SNI) that the sensor automatically
determines from the host address of the parent device or from the target
URL of the sensor.
The SNI must be a fully qualified domain name (FQDN). Make sure
that it matches the configuration of the target server.
For more information, see the Knowledge Base: My HTTP sensors fail
to monitor websites which use SNI. What can I do?
This sensor implicitly supports SNI, an extension to the Transport

Layer Security (TLS) protocol.
SNI Inheritance Define if you want to inherit the SNI from the parent device:
§ Inherit SNI from parent device: Determine the SNI from the host address
of the parent device.
§ Do not inherit SNI from parent device: Determine the SNI from the target
URL as defined in the settings of this sensor.
1050
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
1051
Channel List
Channel Description
Loading Time The web page or element loading time

More
KNOWLEDGE BASE
My HTTP sensors fail to monitor websites which use SNI. What can I do?

1052

1053
7.8.59 HTTP v2 Sensor
The HTTP v2 sensor monitors a web server using the Hypertext Transfer Protocol (HTTP).
You can use this sensor to monitor if a website or a specific website element is reachable.
HTTP v2 Sensor
List 1060 .

§ Dutch: HTTP v2
§ French: HTTP v2
§ German: HTTP v2
§ Japanese: HTTP v2
§ Portuguese: HTTP v2
§ Russian: HTTP v2
§ Simplified Chinese: HTTP v2
§ Spanish: HTTP v2
Remarks
1054
Remark Description
channels.
Credentials § You can define credentials for HTTP in the settings of an object that is
higher in the object hierarchy.
§ The recommended scanning interval of this sensor is 1 minute.
Knowledge Base § Knowledge Base: Which HTTP status code leads to which HTTP
sensor status?
you add the sensor:
§ http
§ httpsensor
1055
HTTP Specific
HTTP Specific
Setting Description
Timeout per Request Enter a timeout in seconds for the request. Enter an integer. The
(Sec.) maximum timeout value is 900 seconds (15 minutes).
The timeout is per request, not per sensor scan. If a request is
redirected, the timeout begins again.
Maximum Number of Enter the maximum number of times the sensor scan will follow an HTTP
Redirects redirect request. The sensor will display the status of the last page before
the number of redirects is exhausted. The default number of redirects the
sensor will follow is 16. The maximum number of redirects the sensor will
follow is 100. Enter 0 if you do not want the sensor to follow any redirects.
1056
Setting Description

The default URL is https://%host/. PRTG replaces %host with the IP
address or DNS name of the parent device. PRTG does not display
the value in the sensor log or the sensor's settings.
the URL:
web page.
If you select this setting, you must enter the data in the POST
Body field below.
(default) requests.
actual web page.
Define the content type of the POST request. The default content type is
application/x-www-form-urlencoded.
POST Body This setting is only visible if you select POST above.

Custom Headers Enter a list of custom headers with their respective values that the HTTP
request of the sensor contains. The syntax of a header-value pair is
header1:value1.
1057
Setting Description
If you enter more than one header-value pair, enter each pair in one
line:
header1:value1
header2:value2
header3:value3
Make sure that the HTTP header statement is valid. Otherwise, the
sensor request cannot be successful.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1058
Debug Options
Debug Options
Setting Description
Inherited Settings

1059
Channel List
Channel Description
Bytes Received The number of bytes received
Loading Time The web page or element loading time

Response Code The response code of the target server
More
KNOWLEDGE BASE

1060
7.8.60 HTTP Advanced Sensor
The HTTP Advanced sensor monitors the source code of a web page using HTTP. It supports
authentication, content checks, and other advanced parameters.
The monitored content size is uncompressed.
HTTP Advanced Sensor
List 1072 .

§ Dutch: HTTP Geavanceerd
§ French: HTTP avancé
§ German: HTTP (Erweitert)
§ Japanese: HTTP
§ Portuguese: HTTP (avançado)
§ Russian: HTTP ( )
§ Spanish: HTTP (avanzado)
Remarks
1061
Remark Description
If you need to use SRP ciphers, use the Compatibility engine.
HTTP compression § This sensor does not support HTTP compression. If you need to use it
anyway, select Compatibility engine in the sensor settings.
Fast internet connections § Bandwidth monitoring of fast internet connections might be inaccurate.
Knowledge Base § Knowledge Base: Which user agent should I use in the HTTP Advanced
sensor's settings?
§ Knowledge Base: My HTTP sensors fail to monitor websites which use
SNI. What can I do?
sensor status?
you add the sensor:
§ httpsensor
1062
HTTP Specific
HTTP Specific
Setting Description

Replacement 1072 .
the URL:
web page.
1063
Setting Description

field below.
(default) requests.
actual web page.


URL of the sensor.
For more information, see the Knowledge Base: My HTTP sensors
fail to monitor websites which use SNI. What can I do?
This sensor implicitly supports SNI, an extension to the Transport

Layer Security (TLS) protocol.
1064
Setting Description
Monitoring Engine
Monitoring Engine
Setting Description
Monitoring Engine Choose the monitoring engine that the sensor uses:
§ Default: Use the default monitoring engine.
§ Compatibility engine: Execute an external executable program. Use

this method as an alternative for websites that do not work with the
default monitoring engine.
This method needs more resources but it can be helpful in some
cases.
If you select the compatibility mode, the options for the SSL
method are different. You can also check for trusted certificates.
See below.
Smart URL Replacement does not work with the compatibility
mode, so this sensor does not automatically use the IP
Address/DNS Name of the parent device.
SSL/TLS Method This setting is only visible if you select Compatibility engine above.
Select the SSL/TLS method:

§ SSLv3
§ TLS 1.0, TLS 1.1, TLS 1.2
§ SSLv3, TLS 1.0, TLS 1.1, TLS 1.2 (default)
Check SSL Certificates This setting is only visible if you select Compatibility engine above.
Specify if the sensor checks the certificate of the URL:

§ Do not check certificates (default): Do not check the certificates of the
web pages.
1065
Setting Description
§ Check if certificates are trusted: Check the certificates of the web

pages. If the certificate of the server is not trusted, the sensor shows
the Down status and displays a corresponding message.
Advanced Sensor Data
Setting Description
HTTP Version Define the HTTP version that the sensor uses when it connects to the
target URL:
§ HTTP 1.0: Use HTTP version 1.0.
1066
Setting Description
User Agent Choose which user agent string the sensor sends when it connects to the
target URL:
§ Use the default string: Do not enter a specific user agent and use the
default string. Usually, this is Mozilla/5.0 (compatible; PRTG Network
Monitor (www.paessler.com); Windows).
§ Use a custom string: Use a custom user agent. Define the custom user
agent below.
Custom User Agent This setting is only visible if you select Use a custom string above.
Enter the string that the sensor uses as the user agent when it connects
to the target URL.
HTTP Headers Define if you want to send custom HTTP headers to the target URL:
§ Do not use custom HTTP headers: Do not use custom HTTP headers.
§ Use custom HTTP headers: Use custom headers. Define below.
Custom HTTP Headers This setting is only visible if you select Use custom HTTP headers above.
Enter a list of custom HTTP headers and values that you want to transmit
to the URL, each pair in one line. The syntax of a header-value pair is
header1:value1
The sensor does not support the header field names user-agent,
content-length, and host.
If Content Changes Define what the sensor does if the content of the web page changes:

change.
Require Keyword Define if the sensor checks the result at the URL for keywords:
§ Do not check for keyword (default): Do not search for keywords in the
result.
§ Set sensor to warning status if keyword is missing: Check if a keyword
exists in the result. If it exists, set the sensor to the Warning status.
§ Set sensor to down status if keyword is missing: Check if a keyword
exists in the result. If it exists, set the sensor to the Down status.
1067
Setting Description
The content check is only intended for HTML websites and might not
work with other target URLs. For example, binary files are not
supported.
This sensor loads the source code at the 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 code used to display the page
when opening the same URL in a web browser. This is because a reload
might be configured or certain information might be inserted after loading,
for example, via JavaScript.
PRTG does not follow links to embedded objects nor does it execute
scripts. Only the first page at the URL is loaded and checked against
the expressions configured.
Response Must Include This setting is only visible if you select Set sensor to warning status if
keyword is missing or Set sensor to down status if keyword is missing
above.
Define the search string that must be part of the source code at the URL.
You can enter a simple string in plain text or a regular expression (regex).
If the source code does not include the search pattern, the sensor
shows the status defined above.

You can also search for HTML tags.

Exclude Keyword Define if the sensor checks the result at the URL for keywords:
result.
§ Set sensor to warning status if keyword is found: Check if a keyword
§ Set sensor to down status if keyword is found: Check if a keyword
1068
Setting Description
work with other target URLs. For example, binary files are not
supported.
Response Must Not This setting is only visible if you select Set sensor to warning status if
Include keyword is found or Set sensor to down status if keyword is found above.
Define the search string that must not be part of the source code at the
specified URL. You can enter a simple string in plain text or a regular
expression.
If the data does include this string, the sensor shows the status
defined above.

You can also search for HTML tags.

Download Limit (KB) Enter the maximum amount of data (in kilobytes) that the sensor
transfers per request.
If you set content checks, be aware that they might be incomplete

because only the content downloaded up to this limit is checked for
search expressions.
Result Handling Define what the sensor does with the data loaded at the URL:
§ Store result: Store the last result of the requested data in the
\Logs\sensors subfolder of the PRTG data directory on the probe
system. The file names are Result of Sensor [ID].txt, Result of Sensor
[ID]-A.txt, and Result of Sensor [ID].Data.txt. This setting is for
debugging purposes, especially in combination with content checks.
PRTG overwrites these files with each scanning interval.
1069
Setting Description
For debugging, select Store result to write the source code file to
disk and to look up what exactly PRTG gets when it calls the URL. If
the URL does not point to a web page but to a binary file, for example, to
an image, you usually do not check for content.
master node.
Authentication
Authentication
Setting Description
Authentication Define if authentication is necessary on the web page:

§ Web page does not need authentication (default)
§ Web page needs authentication
User Name This setting is only visible if you select Web page needs authentication
above.
If the proxy requires authentication, enter the user name for the proxy
login. Enter a string.
Password This setting is only visible if you select Web page needs authentication
above.
Enter a password.
Authentication Method This setting is only visible if you select Web page needs authentication
above.
Select the authentication method that the URL uses:

§ HTTP authentication (default): Use simple HTTP authentication.
This authentication method transmits credentials as plain text.
1070
Setting Description
§ NT LAN Manager authentication: Use the Microsoft NT LAN Manager

(NTLM) protocol for authentication.
§ Digest access authentication: Use digest access authentication. This
applies a hash function to the password, which is safer than HTTP
authentication (default).
Sensor Display
Sensor Display
Setting Description

other above.
procedure to do so.
1071
Inherited Settings

Channel List
Channel Description
Download Bandwidth The download speed
Loading Time The loading time
1072
Channel Description
Time To First Byte The time to the first byte
More
KNOWLEDGE BASE
Which user agent should I use in the HTTP Advanced sensor's settings?


Why do my HTTP Advanced sensors differ in the bytes received value?


1073
7.8.61 HTTP Apache ModStatus PerfStats Sensor
The HTTP Apache ModStatus PerfStats sensor monitors performance statistics of an Apache web server
via mod_status over HTTP.
This sensor implicitly supports SNI, an extension to the Transport Layer Security (TLS) protocol.
HTTP Apache ModStatus PerfStats Sensor
List 1078 .

§ Dutch: HTTP Apache ModStatus PerfStats
§ French: Apache ModStatus PerfStats (HTTP)
§ German: HTTP Apache ModStatus PerfStats
§ Japanese: HTTP Apache ModStatus
§ Portuguese: PerfStats Apache ModStatus (HTTP)
§ Russian: HTTP Apache ModStatus — -

§ Simplified Chinese: HTTP Apache ModStatus PerfStats
§ Spanish: PerfStats Apache ModStatus (HTTP)
Remarks
1074
Remark Description
sensor status?
you add the sensor:
§ apache
§ httpsensor
§ httpapachemodstatusperfstatssensor
HTTP Specific
HTTP Specific
1075
Setting Description
URL Enter the URL to the mod_status module on your Apache server. PRTG
automatically appends /server-status?auto to it. If you enter an absolute
URL, the sensor uses this address independently of the IP Address/DNS
Name setting of the parent device.
Replacement 1078 .
Authentication
Authentication
Setting Description
above.
above.
Enter a password.
above.
1076
Setting Description

Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1077
Inherited Settings

Channel List
Channel Description
BusyWorkers The number of busy worker threads
BytesPerReq The number of bytes per request
CPULoad The CPU load

1078
Channel Description
IdleWorkers The number of idle worker threads
ReqPerSec The number of requests
Uptime The uptime
More
KNOWLEDGE BASE



1079
7.8.62 HTTP Apache ModStatus Totals Sensor
The HTTP Apache ModStatus Totals sensor monitors the activity of an Apache web server using
mod_status over HTTP.
HTTP Apache ModStatus Totals Sensor
List 1084 .

§ Dutch: HTTP Apache ModStatus Totalen
§ French: Apache ModStatus totaux (HTTP)
§ German: HTTP Apache ModStatus Gesamt
§ Japanese: HTTP Apache ModStatus
§ Portuguese: Totais Apache ModStatus (HTTP)
§ Russian: HTTP Apache ModStatus —
§ Simplified Chinese: HTTP Apache ModStatus
§ Spanish: Totales Apache ModStatus (HTTP)
Remarks
1080
Remark Description
sensor status?
you add the sensor:
§ apache
§ httpsensor
§ httpapachemodstatustotalssensor
HTTP Specific
HTTP Specific
1081
Setting Description
URL Enter the URL to the mod_status module on your Apache server. PRTG
automatically appends /server-status?auto to it. If you enter an absolute
URL, the sensor uses this address independently of the IP Address/DNS
Name setting of the parent device.
Replacement 1084 .
Authentication
Authentication
Setting Description
above.
above.
Enter a password.
above.
1082
Setting Description

Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1083
Inherited Settings

Channel List
Channel Description
Accesses The number of accesses
KBytes The data transferred

1084
More
KNOWLEDGE BASE


1085
7.8.63 HTTP Content Sensor
The HTTP Content sensor monitors numeric values returned by an HTTP request.
In the returned HTML page, each value must be placed between brackets [ ]. See section
Example 1091 .
HTTP Content Sensor
List 1092 .

§ Dutch: HTTP (Inhoud)
§ French: Contenu (HTTP)
§ German: HTTP (Inhalt)
§ Japanese: HTTP
§ Portuguese: Conteúdo HTTP
§ Russian: HTTP:
§ Spanish: Contenido HTTP
Remarks
1086
Remark Description
Knowledge Base § Knowledge Base: How can I monitor internal values of a web application
with PRTG?
sensor status?
Add Sensor
Setting Description
Number of Channels Define how many values the .html file returns. The sensor handles each
value in its own channel. Each value must be placed between brackets
[ ]. Enter the number of bracket-value pairs that the URL returns. Enter an
integer.
Do not enter a number that is greater than the number of values that
the HTTP request returns. Otherwise, you get an error message.
you add the sensor:
§ httpsensor
1087
HTTP Specific
HTTP Specific
Setting Description
Script URL Enter the URL that the sensor connects to. If you enter an absolute URL,
the sensor uses this address independently of the IP Address/DNS Name
setting of the parent device.
Replacement 1092 .
Value Type Define what kind of values the .html file returns:
§ Integer: Returns integers.
§ Float: Returns floats with a dot . between the predecimal position and
the decimal places. The sensor also displays integers unless they do
not produce a buffer overflow.
The sensor cannot handle string values.
1088
Setting Description
If Content Changes Define what the sensor does if the content of the web page changes:

change.
scanning interval.
master node.
Authentication
Authentication
1089
Setting Description

above.
above.
Enter a password.
above.

Sensor Display
Sensor Display
Setting Description
1090
Setting Description



other above.
procedure to do so.
Inherited Settings
Example
For example, consider the URL http://www.example.com/status.html that returns a PHP script with
the current system status in a simple HTML page as follows:
<html>
<body>
Description: Script gives back current status of disk free (%) and CPU usage (%).
[85.5][12.0]
</body>
</html>
You would configure the HTTP Content sensor using
§ the Script URL from above,
§ the value type Float,
1091
§ and the number of channels 2.
The sensor calls the URL with every scanning interval and only regards the two values in brackets [ ] and
handles each of them in one channel. The additional description text and HTML tags are not necessary.
In this example, they are added in case a human calls the URL.
If you define the number of channels as 1, the sensor only reads the first value. The second value is
ignored. Using 3 as the number of channels results in a sensor error message.

Channel List
Channel Description
[Value] The numeric values that an HTTP request returns in several channels
More
KNOWLEDGE BASE
How can I monitor internal values of a web application with PRTG?
1092


1093
7.8.64 HTTP Data Advanced Sensor
The HTTP Data Advanced sensor accesses a web server and retrieves Extensible Markup Language
(XML) encoded or JavaScript Object Notation (JSON) encoded data.
HTTP Data Advanced Sensor
List 1101 .

§ Dutch: HTTP Data Geavanceerd
§ French: Données avancé (HTTP)
§ German: HTTP Daten (Erweitert)
§ Japanese: HTTP
§ Portuguese: Dados HTTP (avançado)
§ Russian: HTTP: ( )
§ Spanish: Datos HTTP (avanzado)
Remarks
1094
Remark Description
Return data § The requested web server must return XML-encoded or JSON-encoded
data that matches the format as defined in the PRTG Manual: Custom
Sensors.
Performance § For best sensor performance, we recommend that you specify the
content type on the target system, which is application/xml or
application/json.
sensor status?
you add the sensor:
§ httpsensor
1095
HTTP Specific
HTTP Specific
Setting Description

Replacement 1101 .
the URL:
web page.
1096
Setting Description

field below.
(default) requests.
actual web page.


URL of the sensor.
For more information, see the Knowledge Base: My HTTP sensors
fail to monitor websites which use SNI. What can I do?
1097
Setting Description
Result Handling Define what the sensor does with the data loaded at the URL:
master node.
Setting Description
HTTP Version Define the HTTP version that the sensor uses when it connects to the
target URL:
target URL:
1098
Setting Description
agent below.
to the target URL.
§ Do not use custom HTTP headers: Do not use custom HTTP headers.
§ Use custom HTTP headers: Use custom headers. Define below.
Custom HTTP Headers This setting is only visible if you select Use custom HTTP headers above.
Enter a list of custom HTTP headers and values that you want to transmit
to the URL, each pair in one line. The syntax of a header-value pair is
header1:value1
content-length, and host.
Authentication
Authentication
Setting Description

above.
1099
Setting Description
above.
Enter a password.
above.

Sensor Display
Sensor Display
Setting Description


1100
Setting Description
other above.
procedure to do so.
Inherited Settings

Channel List
1101
Channel Description
[Value] The values that the web server returns in several channels

Custom Sensors.
More
KNOWLEDGE BASE



1102
7.8.65 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. In the background, it opens the web page in a browser instance to perform the measurement. It
does not follow links.
Be careful with this sensor because it can generate a considerable amount of internet traffic if you
use it with a short scanning interval.
HTTP Full Web Page Sensor
List 1109 .

§ Dutch: HTTP Volledige Webpagina
§ French: Page web complète (HTTP)
§ German: HTTP (Komplette Webseite)
§ Japanese: HTTP
§ Portuguese: Página completa HTTP
§ Russian: HTTP: -
§ Spanish: Página web completa HTTP
Remarks
1103
Remark Description
Knowledge Base § Knowledge Base: What to do when I see a CreateUniqueTempDir()

error message for my HTTP Full Web Page sensor?
§ Knowledge Base: HTTP Full Web Page sensor is unable to navigate.
What can I do?
§ Knowledge Base: How can I change the size of PhantomJS full web
page screenshots?
§ Knowledge Base: Why is my HTTP Full Web Page sensor generating
so many temporary files?
sensor status?
probe device.
you add the sensor:
§ httpfullsensor
1104
Full Web Page Download Settings
Full Web Page Dow nload Settings
Setting Description
URL Enter the address of the web page that the sensor loads. If you enter an
absolute URL, the sensor uses this address independently of the IP
Address/DNS Name setting of the parent device.
Replacement 1109 .
Browser Engine Define which browser engine this sensor uses to load the web page:
§ Chromium (default): Use the WebKit engine that is delivered with PRTG
to measure the loading time. With each scanning interval, PRTG loads
the URL in an instance of Chromium and measures the time it takes to
fully load the page. This is the recommended setting.
Chromium does not support TLS 1.2-only connections. In this
case, we recommend that you use the PhantomJS engine or
Internet Explorer instead.
§ PhantomJS (Headless Webkit): Use the PhantomJS engine. This
engine can have a high impact on the probe system's CPU and
memory load but additional options for result handling 1106 are available.
1105
Setting Description
§ Internet Explorer: With each scanning interval, the URL is loaded in the
background in an instance of Internet Explorer. PRTG uses the Internet
Explorer of the probe system.
For full functionality, we strongly recommend that you install at
least Internet Explorer 11 on the probe system.
If you select Internet Explorer as browser engine, you might face
issues with the creation of temporary files. In this case, we
recommend that you use the Chromium or the PhantomJS browser
engines. For more information, see the Knowledge Base: Why is my
HTTP Full Web Page sensor generating so many temporary files?
All browser engines use the proxy settings from the Windows user
account that the probe runs under (this is usually the local Windows
"system" user account). To use a proxy, adjust the settings accordingly
on the probe system (on all cluster nodes, if in a cluster). For more
information, see the Knowledge Base: How can I access proxy settings
for the HTTP Full Web Page sensor?
Security Context Define the Windows user account that this sensor uses to run the
browser engine:
§ Use security context of PRTG probe service (default): Run the browser
engine under the same Windows user account that the probe system
runs under. By default, this is the local Windows "system" user
account.
account from the parent device settings.
We recommend that you use this setting if you use Chromium
(default) as your browser engine.
Result Handling This setting is only visible if you select PhantomJS (Headless Webkit)
above.
Specify how the browser engine handles the web page result:
§ Render and store a screenshot of most recent result as JPG: Render

and store the web page result in the \Logs\sensors subfolder of the
PRTG data directory on the probe system. The file name is Fullpage of
Sensor (ID).jpg. This setting is for debugging purposes. PRTG
overwrites the file with each scanning interval.
1106
Setting Description
§ Render and store screenshots of all results as JPGs (requires lots of

disk space): Render and store one new screenshot of the web page
with each sensor scan, and store the screenshots in the \Screenshots
(Fullpage Sensor) subfolder of the PRTG data directory on the probe
system. You can use this option to create a visual history of the web
page.
Depending on the monitored website and the scanning interval of
the sensor, this option can create a very high amount of data. Use
this option with care and make sure you set appropriate data purging
limits in the Core & Probes settings.
If necessary, you can change the window size of the rendered
screenshots. For more information, see the Knowledge Base: How
can I change the size of PhantomJS full web page screenshots?
master node.
Authentication This setting is only visible if you select PhantomJS (Headless Webkit)
above.
Define if the monitored web page needs authentication for access:

§ Web page does not need authentication: Access to the web page is
granted without authentication.
§ Web page needs authentication: PRTG automatically tries to use HTTP
basic authentication (BA) or Windows NT LAN Manager (NTLM) to
access the web page with authentication. Enter the credentials below.
Basic access authentication forwards the credentials in plain text.
User Name This setting is only visible if you select PhantomJS (Headless Webkit)
above.
Enter the user name for the web page.
Password This setting is only visible if you select PhantomJS (Headless Webkit)
above.
Enter the password for the web page.
1107
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
1108
Channel List
Channel Description
Loading Time The loading time of the full web page

More
KNOWLEDGE BASE
What to do when I see a CreateUniqueTempDir() error message for my HTTP Full Web Page sensor?
HTTP Full Web Page sensor is unable to navigate. What can I do?
How can I change the size of PhantomJS full web page screenshots?
1109
Why is my HTTP Full Web Page sensor generating so many temporary files?

What is the difference between "HTTP" and "HTTP Full Web Page" web server sensors?
How can I access proxy settings for the HTTP Full Web Page sensor?

1110
7.8.66 HTTP IoT Push Data Advanced Sensor
The HTTP IoT Push Data Advanced sensor displays data from messages that are received from Internet
of Things (IoT) capable devices (for example, Sigfox devices) and that are pushed via an HTTPS request
to PRTG. It provides a URL that you can use to push messages to the probe system via HTTPS
(secured with TLS 1.3 and weak ciphers).
This sensor is especially useful when you want to push data to a PRTG Hosted Monitor instance.
For more information about the sensor usage, see section How to Use 1115 .
HTTP IoT Push Data Advanced Sensor
List 1116 .

§ Dutch: HTTP IoT Push Data Geavanceerd
§ French: Données IoT avancé (HTTP Push)
§ German: HTTP IoT Push-Daten (Erweitert)
§ Japanese: HTTP IoT ( )

§ Portuguese: Dados de push IoT (avançado) (HTTP)
§ Russian: HTTP IoT

§ Simplified Chinese: HTTP IoT
§ Spanish: Datos push IoT (avanzado) (HTTP)
Remarks
1111
Remark Description
Fixed port § This sensor has a fixed port (5051). You cannot change it.
Fixed SSL/TLS version § This sensor has a fixed SSL/TLS version (HTTPS (secured with TLS 1.3
and weak ciphers)). You cannot change it.
Remote probe § If you want to add this sensor to a remote probe and use an HTTPS
connection to send push notifications, you must import a Secure
Sockets Layer (SSL) certificate into the \cert subfolder of the PRTG
program directory on the remote probe. However, this certificate does
not have to match the certificate that you use on the PRTG core server.
For more information about SSL certificates, see the Paessler website:
How to use your own SSL certificate with the PRTG web server
Cluster probe § This sensor does not support cluster probes. You can only set it up on
local probes or remote probes.
Multiple channels § If you use this sensor with multiple channels, we recommend that you
simultaneously push the data for all your channels to PRTG. You can
push data to only one of your channels. However, all other channels
record the value of 0 for this push message.
False alerts § This sensor might result in false alerts if the parent probe disconnects
from the PRTG core server. In this case, the sensor shows the error
message: The latest push message that the sensor received is older
than the specified time threshold allows. (code: PE222).
you add the sensor:
1112
§ HttpPushSensor
§ IoT
§ PushData
§ PushSensor
§ Sigfox
TLS Settings
TLS Settings
Setting Description
TLS Port The number of the port on which this sensor listens for incoming HTTPS
requests. This is always 5051.
HTTP Push Authentication
HTTP Push Authentication
Setting Description
Identification Token This is the token that PRTG uses to find the matching sensor for the
incoming message. When you create the sensor, this token is
{__guid__}.
PRTG replaces this token with an automatically generated token after
sensor creation. If you want to use a different identification token, you can
edit it during or after sensor creation.
PRTG does not automatically replace the token if you change it
already during sensor creation.
1113
HTTP Push Data
HTTP Push Data
Setting Description
No Incoming Data Define which status the sensor shows if it does not receive a push
message for at least two scanning intervals:
§ Ignore and keep last status (default): Keep the status as defined by the
last message that the sensor received.
The parent probe must be connected to keep the last status. If the
parent probe disconnects, the sensor shows the Unknown status.
If the parent probe connects again, the sensor does not automatically
switch from the Unknown status to the last status before the parent
probe disconnected.
§ Switch to unknown status: Show the Unknown status if the sensor
does not receive a message for at least two scanning intervals.
§ Switch to down status after x minutes: Show the Down status if the
sensor does not receive a message within a specific time span. Define
the time threshold below.
Time Threshold (Minutes) This setting is only visible if you select Switch to down status after x
minutes above.
Enter a time threshold in minutes. If this time elapses, the sensor shows
the Down status if it does not receive a push message within this time
span. Enter an integer. The maximum threshold is 1440 minutes.
Sensor Display
Sensor Display
1114
Setting Description


other above.
procedure to do so.
Inherited Settings
How to Use
This function is known as a webhook. Basically, a webhook works like a push notification. Webhooks
are usually triggered by an event (for example, a new comment on a blog post) and send according
information to a specified URL. The HTTP IoT Push Data Advanced sensor then displays the data of
pushed and received messages.
The data that is pushed to this sensor must be valid XML or JSON.
For more information about the return value format, see section Custom Sensors.
The HTTP IoT Push Data Advanced sensor uses the following URLs depending on the type of HTTPS
request:
1115
§ GET (default) requests: https://<probe_ip>:5051/<token>?content=<valid XML_or_JSON>
The XML-encoded value of the content parameter has to match the format defined in section Custom
Sensors.
§ POST requests: https://<probe_ip>:5051/<token>
This HTTPS request method sends the XML-encoded or JSON-encoded HTTPS body as POST data.
The body has to match the format defined in section Custom Sensors. We strongly recommend the
HTTPS content type application/xml or application/json.
Replace the parameters <probe_ip>, <token>, and <valid XML_or_JSON> (for GET requests) with the
corresponding values:
§ For PRTG Network Monitor, the probe IP is the IP address of the probe system.
For PRTG Hosted Monitor instances, the probe IP is the Domain Name System (DNS) name of the
instance.
§ The port number is always 5051. You cannot change this.
§ You can define identification token in the sensor settings.
§ The content of GET requests has to be valid XML or JSON in the PRTG API format.
The content has to be URL encoded (for example, the whitespaces in the sample URL below).
Most browsers do the URL-encoding automatically.
Minimum example for the GET method that returns one static channel value:
https://127.0.0.1:5051/XYZ123?
content=<prtg><result><channel>MyChannel</channel><value>10</value></result><text>this
%20is%20a%20message</text></prtg>
By default, values within the <value> tags in the returned XML or JSON must be integers for them to
be processed. If float values are returned, you must explicitly define this value type as defined in
section Custom Sensors with <float> tags, otherwise the sensor shows 0 values in affected channels.
Example:
https://127.0.0.1:5051/XYZ123?
content=<prtg><result><channel>MyChannel</channel><value>10.45</value><float>1</float>
</result><text>this%20is%20a%20message</text></prtg>
You can use several sensors with the same port and identification token. In this case, push
message data is shown in each of these sensors.
Channel List
1116
Channel Description
[Value] The data received from the message encoded in valid XML or JSON in
several channels
Custom Sensors.
More
KNOWLEDGE BASE

How can I monitor Sigfox geolocation with PRTG?

How can I monitor the Sigfox API with PRTG?

How can I monitor Sigfox callbacks with PRTG?


1117
7.8.67 HTTP Push Count Sensor
The HTTP Push Count sensor counts received messages that are pushed via an HTTP request to PRTG.
It provides a URL that you can use to push messages to the probe system via HTTP (secured with TLS
1.2 or not secure).
HTTP Push Count Sensor
List 1123 .

§ Dutch: HTTP Push Aantal
§ French: Compteur (HTTP Push)
§ German: HTTP Push-Anzahl
§ Japanese: HTTP
§ Portuguese: Contagem de push (HTTP)
§ Russian: HTTP: push-

§ Spanish: Recuento Push (HTTP)
Remarks
1118
Remark Description
probe device.
you add the sensor:
§ HttpPushSensor
§ PushCount
§ PushSensor
1119
HTTP Push
HTTP Push
Setting Description
TLS Settings Define the security of the incoming HTTP push requests:
§ HTTP (unsecure): Send push messages to the probe system via HTTP
(not secure).
§ HTTPS low security (TLS 1.0 to 1.3 and weak ciphers): Send push
messages to the probe system via HTTPS. The sensor supports
connections secured with TLS 1.0 to TLS 1.3 and weak ciphers. It uses
the SSL certificate that is delivered with PRTG or your own trusted SSL
certificate that you imported for the PRTG web server.
If you install the sensor on a remote probe, make sure that you
import the same SSL certificates to the remote probe that you use
on the PRTG core server.
§ HTTPS high security (TLS 1.2 to 1.3 and strong ciphers): Send push
connections secured with TLS 1.2 to TLS 1.3 and strong ciphers. It
uses the SSL certificate that is delivered with PRTG or your own
trusted SSL certificate that you imported for the PRTG web server.
Port This setting is only visible if you select HTTP (unsecure) above.
Enter the number of the port on which this sensor listens for incoming
HTTP requests. The default port is 5050.
1120
Setting Description
TLS Port This setting is only visible if you select HTTPS low security (TLS 1.0 to
1.3 and weak ciphers) or HTTPS high security (TLS 1.2 to 1.3 and strong
ciphers) above.
HTTPS requests. The default port is 5051.
Request Method Select the request method of the webhook:

§ any: Do not use any filter for the request method.
§ GET (default): Select this method if the webhook uses GET.
§ POST: Select this method if the webhook sends POST data.

POST data must be form-encoded request bodies with the same
parameters as for GET requests.
{__guid__}.
Request Handling Define what PRTG does with the incoming messages:
§ Discard request: Do not store the pushed messages.
§ Store result: Store the last message received from the sensor in the
system. The file name is Request for Sensor [ID].txt. This setting is for
debugging purposes. PRTG overwrites this file with each scanning
interval.
Sensor Display
Sensor Display
1121
Setting Description


other above.
procedure to do so.
Inherited Settings
How to Use
This function is known as webhook. Basically, a webhook works like a push notification. Webhooks are
usually triggered by an event (for example, a new comment on a blog post) and send according
information to a specified URL. The HTTP Push Count sensor then displays the number of pushed and
received messages.
The HTTP Push Count sensor uses the following URL:
http://<probe_ip>:<port_number>/<token>
Replace the parameters <probe_ip>, <port_number>, and <token> with the corresponding values.
§ The <probe_ip> is the IP address of the probe system with the sensor.
1122
§ The <port_number> is where the sensor listens for incoming HTTP calls.
§ The <token> is used to define the matching sensor.
Example:
http://192.0.2.0:5050/XYZ123
You can use several sensors with the same port and identification token. In this case, the number of
push messages is shown in each of these sensors.
Channel List
Channel Description
Messages Received The number of messages received

More
KNOWLEDGE BASE

1123
7.8.68 HTTP Push Data Sensor
The HTTP Push Data sensor displays numeric values from received messages that are pushed via an
HTTP request to PRTG. It provides a URL that you can use to push messages to the probe system via
HTTP (secured with TLS 1.2 or not secure).
HTTP Push Data Sensor
List 1130 .

§ Dutch: HTTP Push Data
§ French: Données (HTTP Push)
§ German: HTTP Push-Daten
§ Japanese: HTTP
§ Portuguese: Dados de push HTTP
§ Russian: HTTP
§ Spanish: Datos push (HTTP)
1124
Remarks
Remark Description
probe device.
you add the sensor:
§ HttpPushSensor
§ PushData
§ PushSensor
1125
HTTP Push
HTTP Push
Setting Description
(not secure).
1126
Setting Description
ciphers) above.


{__guid__}.
interval.
1127
HTTP Push Data
HTTP Push Data
Setting Description
probe disconnected.
minutes above.
Value Type Define the type of the value of the received data:
§ Integer
§ Float (with a dot . between the predecimal position and the decimal
places)
If this setting does not match, the sensor shows the Down status.
1128
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
1129
How to Use
usually triggered by an event (for example, a new comment on a blog post) and send according
information to a specified URL. The HTTP Push Data sensor then displays the data of pushed and
received messages.
The HTTP Push Data sensor uses the following URL:
http://<probe_ip>:<port_number>/<token>?value=<integer_or_float>&text=<text message>
Replace the parameters <probe_ip>, <port_number>, <token>, and <integer_or_float> with the
corresponding values. The &text parameter is optional: You can omit it.
§ You can define the port number and identification token in the sensor settings.
§ The probe IP is the IP address of the probe system with this sensor.
§ The value can be an integer or a float value depending on the data of your application. You must set
the value type accordingly in the sensor settings. This parameter is the sensor value.
If this parameter is missing, the sensor shows a Down status.
§ You can optionally add a custom text message by replacing the parameter <text message> with your
custom text. The text is shown as the sensor message. If there is no value but only a text, the text is
shown as an error message.
This text message has to be URL encoded (for example, the whitespaces in the sample URL
below). Most browsers do URL-encoding automatically.
Example:
http://192.0.2.0:5050/XYZ123?value=0&text=this%20is%20a%20message
You can use several sensors with the same port and identification token. In this case, the data of
Channel List
Channel Description
[Value] The received value and an optional message in one channel

1130
More
KNOWLEDGE BASE

1131
7.8.69 HTTP Push Data Advanced Sensor
The HTTP Push Data Advanced sensor displays data from received messages that are pushed via an
HTTP request to PRTG. It provides a URL that you can use to push messages to the probe system via
HTTP (secured with TLS 1.2 or not secure).
HTTP Push Data Advanced Sensor
List 1138 .

§ Dutch: HTTP Push Data geavanceerd
§ French: Données avancé (HTTP Push)
§ German: HTTP Push-Daten (Erweitert)
§ Japanese: HTTP ( )
§ Portuguese: Dados de push HTTP avançado
§ Russian: HTTP: ( )
§ Spanish: Datos push (avanzado) (HTTP)
Remarks
1132
Remark Description
Multiple channels § If you use this sensor with multiple channels, we recommend that you
simultaneously push the data for all your channels to PRTG. You can
push data to only one of your channels. However, all other channels
record the value of 0 for this push message.
probe device.
you add the sensor:
§ HttpPushSensor
1133
§ PushData
§ PushSensor
HTTP Push
HTTP Push
Setting Description
(not secure).
1134
Setting Description
ciphers) above.


{__guid__}.

interval.
1135
HTTP Push Data
HTTP Push Data
Setting Description
probe disconnected.
minutes above.
Sensor Display
Sensor Display
1136
Setting Description


other above.
procedure to do so.
Inherited Settings
How to Use
usually triggered by some event (for example, a new comment on a blog post) and send according
information to a specified URL. The HTTP Push Data Advanced sensor then displays the data of pushed
and received messages.
The data that is pushed to this sensor must be valid XML or JSON.
For more information about the return value format, see section Custom Sensors.
The HTTP Push Data Advanced sensor uses the following URLs depending on the type of HTTP request:
1137
§ GET (default) requests: http://<probe_ip>:<port_number>/<token>?content=<valid XML_or_JSON>
The XML encoded value of the content parameter has to match the format as defined in section
Custom Sensors.
§ POST requests: http://<probe_ip>:<port_number>/<token>
This HTTP request method sends the XML or JSON encoded HTTP body as POST data. The body has
to match the format as defined in section Custom Sensors. For POST requests, use an HTTP content
type other than application/x-www-form-urlencoded. We strongly recommend the HTTP content type
application/xml or application/json.
Replace the parameters <probe_ip>, <port_number>, <token>, and <valid XML_or_JSON> (for GET
requests) with the corresponding values:
§ You can define port number and identification token in the sensor settings.
§ The probe IP is the IP address of the probe system with this sensor.
§ The content of GET requests has to be valid XML or JSON in the PRTG API format.
The content has to be URL encoded (for example, the whitespaces in the sample URL below).
Most browsers do URL-encoding automatically.
Minimum example for the GET method that returns one static channel value:
http://127.0.0.1:5050/XYZ123?
content=<prtg><result><channel>MyChannel</channel><value>10</value></result><text>this
%20is%20a%20message</text></prtg>
By default, values within the <value> tags in the returned XML or JSON must be integers to be
processed. If float values are returned, you must explicitly define this value type as defined in
section Custom Sensors with <float> tags, otherwise the sensor shows 0 values in affected channels.
Example:
http://127.0.0.1:5050/XYZ123?
content=<prtg><result><channel>MyChannel</channel><value>10.45</value><float>1</float>
</result><text>this%20is%20a%20message</text></prtg>
You can use several sensors with the same port and identification token. In this case, the data of
Channel List
Channel Description
1138
Channel Description
[Value] The data received from the message encoded in valid XML or JSON in
several channels
Custom Sensors.
More
KNOWLEDGE BASE


1139
7.8.70 HTTP Transaction Sensor
The HTTP Transaction sensor monitors an interactive website, such as a web shop, by performing a
transaction using a set of HTTP URLs. The sensor monitors whether logins or shopping carts work
properly.
HTTP Transaction Sensor
List 1150 .

§ Dutch: HTTP (Transactie)
§ French: Transaction (HTTP)
§ German: HTTP (Transaktion)
§ Japanese: HTTP
§ Portuguese: Transação HTTP
§ Russian: HTTP
§ Spanish: Transacción HTTP
Remarks
1140
Remark Description
If you need to use SRP ciphers, use the Compatibility engine.
Knowledge Base § Knowledge Base: Configuration tips for HTTP Transaction sensors
needed
§ Knowledge Base: Which user agent should I use in the HTTP Advanced
sensor's settings?
you add the sensor:
§ httptransactionsensor
HTTP Specific
HTTP Specific
1141
Setting Description
Timeout (Sec.) Enter a timeout in seconds for all HTTP requests. Enter an integer. The
maximum value is 900 seconds (15 minutes).
If the complete transaction takes longer than this value, the sensor
cancels the request and shows an according error message. If two
consecutive requests are unsuccessful (for whatever reason), the sensor
Single URL Timeout Enter a timeout in seconds for one single HTTP request. Enter an integer.
(Sec.) The maximum value is 900 seconds (15 minutes).
If the reply of any single request takes longer than this value, the
sensor cancels the transaction and shows an according error
message.
Monitoring Engine
Monitoring Engine
Setting Description
Monitoring Engine Choose the monitoring engine that the sensor uses:
§ Default: Use the default monitoring engine.
§ Compatibility engine: Execute an external executable program. Use

this method as an alternative for websites that do not work with the
default monitoring engine.
This method needs more resources but it can be helpful in some
cases.
If you select the compatibility mode, the options for the SSL
method are different. You can also check for trusted certificates.
See below.
Smart URL Replacement does not work with the compatibility
mode, so this sensor does not automatically use the IP
SSL/TLS Method This setting is only visible if you select Compatibility engine above.
Select the SSL/TLS method:

§ SSLv3
1142
Setting Description
§ TLS 1.0, TLS 1.1, TLS 1.2
§ SSLv3, TLS 1.0, TLS 1.1, TLS 1.2 (default)
Check SSL Certificates This setting is only visible if you select Compatibility engine above.
Specify if the sensor checks the certificate of the URL:

§ Do not check certificates (default): Do not check the certificates of the
web pages.
§ Check if certificates are trusted: Check the certificates of the web
pages. If the certificate of the server is not trusted, the sensor shows
the Down status and displays a corresponding message.
Setting Description
Download Limit (KB) Enter a number that defines the maximum amount of data (in kilobytes)
that the sensor transfers per request.
If you set content checks, be aware that they might be incomplete.
This is because the sensor only checks the content that is
downloaded up to this limit for search expressions.
Cookie Management Select if you want to allow cookies for the transaction:
§ Use cookies (default): Allow cookies to be set and read during the
transaction cycle. We recommend that you use this option.
§ Ignore: Do not allow cookies. Use this option if you want to test the
transaction without the use of cookies.
1143
Setting Description
target URL:
agent below.
to the target URL.
Result Handling Define what PRTG does with the web page that is loaded at the URL:
§ Store result: Store the last result of the web page in the \Logs\sensors
subfolder of the PRTG data directory on the probe system. The file
names are Result of Sensor [ID]-1.txt and Result of Sensor
[ID].Data.txt. This setting is for debugging purposes, especially in
combination with content checks. PRTG overwrites the files with each
scanning interval.
master node.
Authentication
Authentication
Setting Description

1144
Setting Description
above.
above.
Enter a password.
above.

Transaction URL
You can define up to 10 different transaction URLs, which are all called in a row. If the transaction can be
completed, the sensor shows the Up status. Using this mechanism, you can set up extended monitoring
with multiple URLs.
Enter settings for at least one transaction URL. You can use as many steps as necessary and disable
the other steps.
1145
Transaction URL #x
Setting Description
Transaction Step #x This setting is available for URL #2 through #10. Define if you want to use
this step for the transaction check:
§ Disable step #x (default): Do not use this step. Choose this option if
you do not need all 10 steps for the transaction check.
§ Enable step #x: Enable this step. Further options are available.
URL Enter the URL that the sensor connects to. If you enter an absolute URL,
the sensor uses this address independently of the IP Address/DNS Name
The URL must not be URL encoded.
Replacement 1149 .
the URL:
web page.
1146
Setting Description

field below.
(default) requests.
actual web page.

Require Keyword Define if the sensor checks the result at the URL for keywords:
result.
§ Set sensor to warning status if keyword is missing: Check if a keyword
§ Set sensor to down status if keyword is missing: Check if a keyword
exists in the result. If it exists, set the sensor to the Down status.
work with other target URLs.
Response Must Include This setting is only visible if you select Set sensor to warning status if
keyword is missing or Set sensor to down status if keyword is missing
above.
Define the search string that must be part of the result at the URL.
If the result at the URL does not include the search pattern, the
sensor shows the status defined above and displays this string along
with the affected URL in the sensor message.
Only simple text search is available here.
is not possible.
Exclude Keyword Define if the sensor checks the result at the URL for keywords:
1147
Setting Description
result.
§ Set sensor to warning status if keyword is found: Check if a keyword
§ Set sensor to down status if keyword is found: Check if a keyword

work with other target URLs.
Response Must Not Define a string that must not be part of the result at the URL. If the data
Include includes this string, the sensor shows the Down status and displays this
string along with the affected URL in the sensor message. Enter a string.
Only simple text search is available here.
is not possible.
Sensor Display
Sensor Display
Setting Description

1148
Setting Description

other above.
procedure to do so.
Inherited Settings

1149
Channel List
Channel Description
Sum The loading time of the complete transaction

Time of URL [#] The loading time of single URLs
More
KNOWLEDGE BASE
Configuration tips for HTTP Transaction sensors needed


1150
7.8.71 HTTP XML/REST Value Sensor
The HTTP XML/REST Value sensor retrieves an .xml file from a URL and parses it.
HTTP XML/REST Value Sensor
List 1160 .

§ Dutch: HTTP XML/REST Waarde
§ French: Valeur XML/REST (HTTP)
§ German: HTTP XML-/REST-Wert
§ Japanese: HTTP XML/REST
§ Portuguese: Valor HTTP XML/REST
§ Russian: HTTP XML/REST

§ Simplified Chinese: HTTP XML/REST
§ Spanish: Valor HTTP XML/REST
Remarks
1151
Remark Description
system.
does PRTG require?
Single node § This sensor can monitor only one single node in an .xml file and shows
the value in one channel. To monitor more than one node of an .xml
document, add one sensor for each target node.
Knowledge Base § Knowledge Base: Where can I find more information about the HTTP
XML/REST Value sensor?

sensor status?
Add Sensor
Setting Description
Channel Name Enter a name for the channel that displays the value at the URL.
sensor.
1152
you add the sensor:
§ ptfsensor
Sensor Settings
Sensor Settings
1153
Setting Description
URL Enter the URL that returns the .xml file. If you enter an absolute URL, the
sensor uses this address independently of the IP Address/DNS Name
Replacement 1160 .
XML Node (and optional Enter the name of the node that this sensor checks, or enter a node
property) name and a property name to check a property value. To obtain a value
from nested tags, enter the tag names and separate them with a forward
slash (/). For example, use myTag/myTagInside as XML node value.
You can also check values in JavaScript Object Notation (JSON).
See section Checking JSON 1158 .
You can try to use XPath syntax here but it does not work in all
cases and we do not provide any technical support for XPath issues.
For more information about XPath, see the Knowledge Base: How can I
use XPath with the HTTP XML/REST Value sensor?
HTTP User Name If the URL requires authentication, enter the user name. Enter a string or
HTTP Password If the URL requires authentication, enter the password. Enter a string or
Sensor Value Define what value the sensor shows:

§ Use the value of the selected XML node: Return the value that the
sensor finds at the XML node. If this is a non-numeric value, the sensor
shows 0.
§ Use the number of occurrences of the selected XML node or its
children/siblings: Return the number of occurrences found. Define
further settings below.
Count XML Nodes This setting is only visible if you select Use the number of occurrences of
the selected XML node or its children/siblings above.
Define which count the sensor shows:

§ Occurrences of the selected XML node: Return how often the defined
XML node occurs at the URL.
§ Child nodes of the selected XML node: Return the number of child
nodes that exist below the node at the URL.
1154
Setting Description
§ Sibling nodes of the selected XML node: Return the number of sibling
nodes that exist next to the node at the URL.
Name Space Handling Define whether to use namespaces in the .xml document or not:
§ Use name spaces: Process the value you enter in the XML Node (and
optional property) field, possibly including namespace information.
§ Remove name spaces: Ignore namespace information in the .xml
document and process the value you enter in the XML Node (and
optional property) field as node names only.
For more information see section About Namespaces 1159 .
Content Type Define what to include in the header of the request that the sensor sends
to the URL:
§ Enable (default): This works for most web servers and is the
recommended setting.
§ Disable: Only very few web servers cannot handle this content type and
need this setting. Try this if you get an error message with the enabled
option.
§ Custom: You can use a custom content type.
Enter a custom content type like text/xml or text/html.
HTTP Headers Optionally enter a list of custom HTTP headers with their respective
values that you want to transmit to the URL. The syntax of a list with
header-value pairs is header1:value1|header2:value2|...|headerx:valuex
The sensor does not accept header field names that include a dash
(–) character. If you want to use such an HTTP header, leave out the
dash in the name. For example, enter ContentType:value instead of
Content-Type:value. Example: From:johnqpublic@example.com|
AcceptLanguage:en-us
Remove Characters This setting is only visible if you select Use the value of the selected XML
node above.
Optionally enter a string that the sensor removes from the returned XML
value.
1155
Setting Description
Use this to remove any unwanted characters from the result, for example
to remove a thousands separator from numeric values. Enter a string or
Decimal Delimiter This setting is only visible if you select Use the value of the selected XML
node above.
If the sensor value of the returned XML node is of the type float, you can
define any character as the decimal delimiter. Enter one character or
Custom Message Optionally enter a custom sensor message. Use %1 as a placeholder to

automatically fill in the returned XML value. Enter a string or leave the field
empty.
If Channel Value Define what the sensor does if the channel value changes:
Changes

change.
The notification for this sensor can only be triggered if the returned
value is a numeric value. This option does not support strings.
sensor.
Debug Options
Debug Options
Setting Description
1156
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description


other above.
1157
Setting Description
procedure to do so.
Inherited Settings
Checking JSON
With the XML Node (and optional property) field, you can also check values that are returned in JSON
notation under the defined URL.
1158
Example
A JSON notated section might look like the following:

{
"test": "Hello World",
"object": {
"value": "content",
"AnotherValue": "AnotherContent"
},
"arraytest": [
"one",
"two"
]
}
Depending on your entries in the XML Node (and optional property) field, the sensor processes the
respective values:
Entry in Sensor's "XML Node (and optional Processed Value (from Example Above)
property)" Field (from Example Above)
test Hello World
object/value content
object/AnotherValue AnotherContent
object contentAnotherContent
arraytest[1] one
arraytest[2] two
The sensor converts whitespaces in JSON keys into underscores (_). So, for example, if you look for
the node some node in the JSON, you need to enter some_node into the node field. If you count the
number of nodes (for example, some_node), both some node and some_node would be counted if they
appear in the JSON.
If a key exists more than once in the JSON, the value of the first appearance is returned (no
difference between whitespace and underscore).
About Namespaces
In an .xml document, tags might use namespaces.
1159
Example
A namespace notated section might look like the following:

<myNamespace:myNode>
some information
</myNamespace:myNode>
If you set this sensor to Use name spaces (this is the default setting), it expects the full node name,
including the namespace information, in the XML Node (and optional property) field. In the example
above, this is myNamespace:myNode.
If your node names are unique even without the namespace information, you can simplify the settings by
setting this sensor to Remove name spaces. The sensor then expects the node name only in the XML
Node (and optional property) field. In the example above, this is myNode.

Channel List
1160
Channel Description
[Value] The value of one defined XML node

More
KNOWLEDGE BASE
Where can I find more information about the HTTP XML/REST Value sensor?



How can I use XPath with the HTTP XML/REST Value sensor?
How do I extract values from XML nodes (with nested tags) using the HTTP XML/REST Value sensor?
Why does my HTTP XML/REST Value sensor return a 404 error?


1161
7.8.72 Hyper-V Cluster Shared Volume Disk Free Sensor
The Hyper-V Cluster Shared Volume Disk Free sensor monitors free space on the disks of a Microsoft
Hyper-V cluster shared volume via PowerShell.
Hyper-V Cluster Shared Volume Disk Free Sensor
List 1166 .

§ Dutch: Hyper-V Cluster Shared Volume Disk Free
§ French: Hyper-V cluster espace disponible du volume partagé
§ German: Hyper-V Freigegebenes Clustervolume Freier Speicher
§ Japanese: Hyper-V
§ Portuguese: Disco de volume compartilhado do cluster Hyper-V livre
§ Russian: Hyper-V
§ Simplified Chinese: Hyper-V
§ Spanish: Espacio libre en disco de volumen compartido en clúster Hyper-V
Remarks
1162
Remark Description
does PRTG require?
Remote PowerShell § This sensor requires Remote PowerShell on the target system.
WSFC PowerShell § This sensor requires WSFC PowerShell Interface on the target system.
Interface
§ You can list all modules in the PowerShell console with the command
Get-Module -ListAvailable. Here, FailoverClusters must appear. Under
Windows Server 2008 (not officially supported) and Windows Server
2012 (not officially supported), the interface is part of the VMM
Administrator Console, or the VMM 2012 Management Console.
§ The interface is available everywhere the WSFC feature is installed:
Windows Server 2008 R2 (SP1) Full and Core (not installed by default),
Microsoft Hyper-V Server 2008 R2 (SP1), and Remote Server
Administration Tools (RSAT) for Windows 10, Windows 8.1, Windows
8, and Windows 7 (SP1).
Parent device § This sensor requires that the parent device is a Windows server that
runs Hyper-V.
Unsupported characters § Make sure that the resource names of your disks do not contain
unsupported characters, especially avoid the number sign (#). In
general, the sensor supports UTF-8 characters. We recommend that
you do not rename resource disk names once you have set up
monitoring. For more information, see the Knowledge Base: Why don't
my Hyper-V sensors work after changing names?
1163
Remark Description
Knowledge Base § Knowledge Base: Why don't my Hyper-V sensors work after changing
names?
§ Knowledge Base: Where can I find more information about PowerShell
sensors?
probe device.
you add the sensor:
§ diskfree
§ hyperv
§ powershell
Disk Free Settings
Disk Free Settings
1164
Setting Description
Disks The name of the disk that this sensor monitors.
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description


other above.
1165
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Free Bytes The free space
Free Space The free space (%)

Total The total space
More
KNOWLEDGE BASE
Why don't my Hyper-V sensors work after changing names?


1166



1167
7.8.73 Hyper-V Host Server Sensor
The Hyper-V Host Server sensor monitors a Microsoft Hyper-V host server via Windows Management
Instrumentation (WMI) or Windows performance counters, as configured in the Windows Compatibility
Options of the parent device.
Hyper-V Host Server Sensor
List 1172 .

§ Dutch: Hyper-V Host Server
§ French: Hyper-V serveur hôte
§ German: Hyper-V Host Server
§ Portuguese: Servidor host Hyper-V
§ Russian: Hyper-V
§ Spanish: Servidor host Hyper-V
1168
Remarks
Remark Description
Windows version § This sensor requires at least Windows Server 2008 R2 on the probe
system (on every cluster node, if on a cluster probe).
WoW64 must be installed on target systems that run Windows
Server 2016. This allows 32-bit applications to be run on 64-bit
systems. This is necessary because the PRTG probe service only runs
with 32-bit support. Without it, WMI sensors do not work.
Remote Registry § This sensor requires that the Remote Registry Windows service runs
Windows service on the target system.
§ If this service does not run, a connection via performance counters is
not possible. However, WMI connections might still work.
runs Hyper-V.
§ Otherwise, a connection via performance counters is not possible.
However, WMI connections might still work.
probe device.
1169
Hybrid Approach: Performance Counters and WMI
By default, this sensor uses WMI to request monitoring data. You can change the default behavior
to a hybrid approach in the Windows Compatibility Options of the parent device's settings on which
you create this sensor: if you choose this option, the sensor first tries to query data via Windows
performance counters and uses WMI as a fallback if performance counters are not available. When
running in fallback mode, the sensor tries to connect via performance counters again after 24 hours.
Sensors that use the WMI protocol have a high impact on the system performance. Try to stay
below 200 WMI sensors per probe. Above this number, consider using multiple remote probes for
load balancing.
For a general introduction to the technology behind WMI, see section Monitoring via WMI.
you add the sensor:
§ hypervserversensor
Debug Options
Debug Options
Setting Description
1170
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1171
Inherited Settings
Channel List
Channel Description
CPU Usage Guests The CPU usage of the guests (%)
CPU Usage Hypervisor The CPU usage of the hypervisor (%)
CPU Usage Total The total CPU usage

Deposited Pages The number of deposited pages
Host Health Critical The number of host health-critical values
Network Traffic The sum of the total bytes (received and sent) on all ports of the virtual
switch
More
KNOWLEDGE BASE

1172
7.8.74 Hyper-V Virtual Machine Sensor
The Hyper-V Virtual Machine sensor monitors a virtual machine (VM) that runs on a Microsoft Hyper-V
host server via Windows Management Instrumentation (WMI) or Windows performance counters, as
configured in the Windows Compatibility Options of the parent device.
Hyper-V Virtual Machine Sensor
List 1177 .

§ Dutch: Virtuele Hyper-V-Machine
§ French: Hyper-V machine virtuelle
§ German: Hyper-V Virtuelle Maschine
§ Portuguese: Máquina virtual Hyper-V
§ Russian: Hyper-V
§ Spanish: Máquina virtual Hyper-V
Remarks
1173
Remark Description

runs Hyper-V.
Live migration § This sensor does not support Live Migration.
VM monitoring § To monitor a VM with this sensor, disable User Account Control (UAC)
in the control panel of the Windows operating system that runs on this
VM. Otherwise, the sensor might change to the Down status and show
the error message The virtual machine is not running or is powered off.
Unsupported characters § Make sure that the names of your VMs do not contain unsupported
characters, especially avoid the number sign (#). We recommend that
you not rename VMs once you have set up monitoring. For more
information, see the Knowledge Base: Why don't my Hyper-V sensors
work after changing names?
1174
Remark Description
probe device.

load balancing.
you add the sensor:
§ wmihypervsensor
1175
Setting Description
GUID The globally unique identifier (GUID) of the VM that this sensor monitors.
Virtual Machine Name The name of the VM that this sensor monitors.
Description The description of the VM that this sensor monitors.
Powered-Off VM Define how the sensor reacts to VMs that are powered off:
Handling
§ Alarm when VM is powered off (default): Change to the Down status if
the VM is powered off.
If the sensor is in the Down status, it does not record any data in any
of its channels.
§ Ignore powered off state: Do not change to the Down status if the VM is
powered off. The sensor reports zero values instead.
scanning interval.
master node.
1176
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
1177
Channel Description
CPU Usage Guest The CPU usage of the guests (%)
CPU Usage Hypervisor The CPU usage of the hypervisor (%)
CPU Usage Total The total CPU usage
IDE: Read Bytes/Sec The disk read speed of the IDE
IDE: Write Bytes/Sec The disk write speed of the IDE
More
KNOWLEDGE BASE


1178
7.8.75 Hyper-V Virtual Network Adapter Sensor
The Hyper-V Virtual Network Adapter sensor monitors virtual network adapters that run on a Microsoft
Hyper-V host server via Windows Management Instrumentation (WMI) or Windows performance
counters, as configured in the Windows Compatibility Options of the parent device.
Hyper-V Virtual Netw ork Adapter Sensor
List 1183 .

§ Dutch: Hyper-V Virtuele Netwerk Adapter
§ French: Hyper-V carte réseau virtuelle
§ German: Hyper-V Virtueller Netzwerkadapter
§ Portuguese: Adaptador de rede virtual Hyper-V
1179
§ Russian: Hyper-V
§ Spanish: Adaptador de red virtual Hyper-V
Remarks
Remark Description
runs Hyper-V.
1180
Remark Description
Renaming VMs § We recommend that you do not rename virtual machines (VM) once
you have set up monitoring. Renaming VMs also changes the internal
virtual network adapter names, so monitoring might be interrupted. For
more information about VM naming, see the Knowledge Base: Why
don't my Hyper-V sensors work after changing names?
probe device.

load balancing.
you add the sensor:
§ wmihypervvirtualnetworkadapter
1181
Hyper-V Virtual Network Adapter Settings
Hyper-V Virtual Netw ork Adapter Settings
Setting Description
Virtual Network Adapter The name of the virtual network adapter that this sensor monitors.
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
1182
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Broadcast Packets The number of broadcast packets received

Received
Broadcast Packets Sent The number of broadcast packets sent
Bytes The number of bytes transferred in total

Bytes Received The number of received bytes
Bytes Sent The number of sent bytes
1183
Channel Description
Directed Packets The number of directed packets received

Received
Directed Packets Sent The number of directed packets sent
Multicast Packets The number of multicast packets received

Received
Multicast Packets Sent The number of multicast packets sent
Packets The number of packets transferred in total
Packets Received The number of packets received
Packets Sent The number of packets sent
More
KNOWLEDGE BASE

1184
7.8.76 Hyper-V Virtual Storage Device Sensor
The Hyper-V Virtual Storage Device sensor monitors a virtual storage device that runs on a Microsoft
Hyper-V host server via Windows Management Instrumentation (WMI) or Windows performance
counters, as configured in the Windows Compatibility Options of the parent device.
Hyper-V Virtual Storage Device Sensor
List 1189 .

§ Dutch: Hyper-V Virtueel Opslag Apparaat
§ French: Hyper-V équipement de stockage virtuel
§ German: Hyper-V Virtuelles Speichergerät
§ Portuguese: Dispositivo de armazenamento virtual Hyper-V
§ Russian: Hyper-V
§ Spanish: Dispositivo de almacenamiento virtual Hyper-V
Remarks
1185
Remark Description

runs Hyper-V.
Live migration § This sensor does not support Live Migration.
Knowledge Base § Knowledge Base: Why don't my Hyper-V sensors work after changing
names?
probe device.
1186
load balancing.
you add the sensor:
§ wmihypervvirtualstoragesensor
Hyper-V Virtual Storage Device Settings
Hyper-V Virtual Storage Device Settings
1187
Setting Description
Virtual Storage Device The unique identifier of the virtual storage device that this sensor
monitors.
Host Operating System The host operating system of the virtual storage device that this sensor
monitors.
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description


1188
Setting Description
other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Errors The number of errors
Read Bytes/Sec The read speed

Write Bytes/Sec The write speed
More
KNOWLEDGE BASE

1189
1190
7.8.77 IMAP Sensor
The IMAP sensor monitors an email server via the Internet Message Access Protocol (IMAP).
The sensor can check the content of emails for certain keywords. This way, you can use the sensor
to monitor backup solutions via emails that are sent by these solutions. For more information, see
the Knowledge Base: How can I monitor my backup software to be sure backup succeeded last night?
IMAP Sensor
List 1202 .

§ Dutch: IMAP
§ French: IMAP
§ German: IMAP
§ Japanese: IMAP
§ Portuguese: IMAP
§ Russian: IMAP
§ Simplified Chinese: IMAP
§ Spanish: IMAP
Remarks
1191
Remark Description
Microsoft 365 mailboxes § This sensor does not support Microsoft 365 mailboxes. If you want to
monitor a Microsoft 365 mailbox, use the Microsoft 365 Mailbox 1262
sensor.
Content checks § If you use content checks, we recommend that you use a dedicated
IMAP account that is only checked by PRTG. Editing mails in the
mailbox of the monitored IMAP account can lead to false alarms or
malfunctions of this sensor.
Subfolder monitoring § This sensor might not work properly when monitoring subfolders of
mailboxes. If it has to check subsequent emails with identical subjects,
it might not recognize emails that come in later.
Daylight Saving Time § Emails that arrive during the Daylight Saving Time (winter time to
summer time) change might not be processed properly. If you
experience this issue, delete the respective emails.
Knowledge Base § Knowledge Base: My IMAP sensor does not process HTML emails
correctly using regex. What can I do?
§ Knowledge Base: How can I monitor my backup software to be sure
backup succeeded last night?
§ Knowledge Base: Can I analyze multipart emails using the IMAP
sensor?
§ Knowledge Base: My IMAP sensor does not find emails when I check
for message date. What can I do?
1192
you add the sensor:
§ imapsensor
§ mailsensor
Connectivity
Connectivity
Setting Description
Port Specify the port that the sensor uses for the IMAP connection. The
default port for unsecure connections is 143 and the default port for
secure connections is 993. The actual setting depends on the server you
connect to. Enter an integer.
Transport-Level Security Define how the sensor handles the security of the connection:
§ Use transport-level security if available using StartTLS: Try to connect
to the server via a Secure Sockets Layer (SSL)/Transport Layer
Security (TLS) secured connection and StartTLS. If the server does not
support this, the sensor tries to connect without connection security.
§ Use transport-level security if available: Try to connect to the server via
an SSL/TLS-secured connection. If the server does not support this, the
sensor tries to connect without connection security.
1193
Setting Description
§ Enforce transport-level security using StartTLS: Try to connect to the

server via an SSL/TLS-secured connection and StartTLS. If the server
does not support this, the sensor shows the Down status.
§ Enforce transport-level security (default): Try to connect to the server via
If the sensor connects to a server via StartTLS, the connection is first
established without connection security. After the connection has
been established, the sensor sends a certain command (StartTLS) over
the unsecured connection to negotiate a secure connection via SSL/TLS.
If the sensor does not use StartTLS, the negotiation of a secure
connection happens immediately (implicitly) so that no commands
are sent in unencrypted plain text. If no secure connection is possible, no
communication takes place.
Sensor Behavior
Sensor Behavior
Setting Description
Email Processing Define if the sensor additionally checks the content of all incoming
emails:
§ Do not process emails (default): Only check the availability of the IMAP
server and check if a login is successful. Do not process any emails in
the IMAP email account.
§ Count emails in the mailbox: Count the emails in the mailbox.
§ Process emails in the mailbox: Log in to the IMAP email account and
check the emails that it contains. Define further options below.
1194
Setting Description
scanning interval.
master node.
Authentication
Authentication
Setting Description
User Name Enter a user name for IMAP authentication. Enter a string.
Password Enter a password for IMAP authentication. Enter a string.

The password must not contain spaces, percent signs (%), or the
character combination !*.
Folder Name Enter the name of a folder in the mailbox (for example, the IMAP folder)
that the sensor checks. The default value is Inbox. Unless you set a last
message date check below, the sensor always looks at all emails
contained in the mailbox.
Make sure that you do not manually edit emails in this mailbox with
a different email client because this can result in malfunctions of this
sensor's email identification.
Filter Emails in Inbox

This settings section is only visible if you select Process emails in the mailbox.
1195
Filter Emails in Inbox
Setting Description
Only Include Emails with Define if you want to check the "From" field of the emails:
Matching "From"
§ Do not check (default): Do not process this field in emails.
§ Check using simple string search: Process this field in emails using a
simple string in plain text.
§ Check using regular expression: Process this field in emails using a

regular expression (regex).
In the search, the sensor scans all emails from the newest to the
oldest.

The sensor finishes the scan with the first match. This means that
after it finds a match in one email, the sensor does not perform any
further checks in older emails.
Search for This setting is only visible if you select Check using simple string search
or Check using regular expression above.
Enter the email address or the regular expression that the "From" field of
the email must contain or match.
1196
Setting Description
Only Include Emails with Define if you want to check the "Subject" field of the emails:
Matching "Subject"
§ Do not check (default): Do not process this field in emails.
§ Check using simple string search: Process this field in emails using a
§ Check using regular expression: Process this field in emails using a

regular expression (regex).
oldest.

Enter the simple string in plain text or the regex that the "Subject" field of
the email must contain or match.
Only Include Emails with Define if you want to check the body of the emails:
Matching Email Body
§ Do not check (default): Do not process the email body.
§ Check using simple string search: Process the email body using a
§ Check using regular expression: Process the email body using a regex.
oldest.

Enter the simple string in plain text or the regex that the body of the email
must contain or match.
1197
Setting Description
Only Include Recent Define if you want to check all emails in the mailbox or only mails that
Emails were received during the last few hours:
§ Do not check message age (default): Check all emails that the mailbox
contains.
§ Emails must be younger than: Only check emails that were received
during the last few hours. Define below.
Maximum Age (Hours) This setting is only visible if you select Emails must be younger than
above.
Enter the maximum age in hours. The sensor only processes emails that
are younger. Enter an integer.
If No Email Matches the Define which status the sensor shows if it does not find any email in the
Above Filters mailbox that matches the above filters:
§ Set sensor to up status (default): Show the Up status if the sensor
does not find any email in the mailbox that matches the filters.
§ Set sensor to warning status: Show the Warning status if the sensor
does not find any email in the mailbox that matches the filters.
§ Set sensor to down status: Show the Down status if the sensor does
not find any email in the mailbox that matches the filters.
Message This setting is only visible if you select Set sensor to warning status or
Set sensor to down status above.
Define the message that the sensor shows if it does not find any
matching emails.
Validate Latest Email

This settings section is only visible if you select Process emails in the mailbox.
The sensor only validates the latest email that matches the above filters. If the sensor does not find
a matching email, it does not perform any email validation.
1198
Validate Latest Email
Setting Description
Set Sensor to Warning Define in which cases the sensor shows the Warning status:
Status
§ Never (default): Never show the Warning status because of email
content.
§ Always: Always show the Warning status if it could identify any emails.
§ If subject contains: Show the Warning status if the subject of the email
contains the Search String you define below.
§ If subject does not contain: Show the Warning status if the subject of
the email does not contain the Search String you define below.
§ If email body contains: Show the Warning status if the body of the
email contains the Search String you define below.
§ If email body does not contain: Show the Warning status if the body of
the email does not contain the Search String you define below.
Search Method This setting is only visible if you select If subject contains, If subject does
not contain, If email body contains, or If email body does not contain
above.
Define the method with which you want to search for the respective
condition:
§ Simple string search (default): Search the email subject or body with a
1199
Setting Description

§ Regular expression: Search the email subject or body with a regex.

Search String This setting is only visible if you select If subject contains, If subject does
above.
Define the string that you want to search the email subject or body for.
You can enter a simple string in plain text or a regex.
Warning Message This setting is only visible if you select a "warning" condition above.
Define the message that the sensor shows for the Warning status.
Set Sensor to Down Define in which cases the sensor shows the Down status:
Status
§ Never (default): Never show the Down status based on email content.
§ Always: Always show the Down status if any emails could be identified.
§ If subject contains: Show the Down status if the subject of the found
§ If subject does not contain: Show the Down status if the subject of the
found email does not contain the Search String you define below.
§ If email body contains: Show the Down status if the body of the found
§ If email body does not contain: Show the Down status if the body of the
found email does not contain the Search String you define below.
Search Method This setting is only visible if you select If subject contains, If subject does
above.
Define the method with which you want to search for the respective
condition:
§ Simple string search (default): Search the email subject or body with a
1200
Setting Description

§ Regular expression: Search the email subject or body with a regex.

Search String This setting is only visible if you select If subject contains, If subject does
above.
Define the string that you want to search the email subject or body for.
You can enter a simple string in plain text or a regex.
Error Message This setting is only visible if you select Always, If subject contains, If
subject does not contain, If email body contains, or If email body does not
contain above.
Define the message that the sensor shows for the Down status.
Based on Message Age, Define if you want to check the age of the latest matching email in the
Set Sensor to Warning mailbox:
Status
§ Never (default): Do not check the age of the email.
§ If email is older than: Set the sensor to the Warning status if the found
email is older than you define below.
Message Age (Hours) This setting is only visible if you select the message age check above.
Enter the maximum age in hours. If the processed email is older, the
sensor shows the Warning status. Enter an integer.
Make sure you do not manually edit emails in this mailbox with a
different email client because this can result in malfunctions of the
message age check.
Sensor Display
Sensor Display
1201
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Available The response time

1202
Channel Description
Email Count The number of emails in the defined mailbox
More
KNOWLEDGE BASE
How can I monitor my backup software to be sure backup succeeded last night?
My IMAP sensor does not process HTML emails correctly using regex. What can I do?
Can I analyze multipart emails using the IMAP sensor?

My IMAP sensor does not find emails when I check for message date. What can I do?

1203
7.8.78 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.
IP on DNS Blacklist Sensor
List 1207 .

§ Dutch: IP op DNS Blacklist
§ French: IP sur liste noire du DNS
§ German: IP auf Schwarzer Liste des DNS
§ Japanese: DNS IP
§ Portuguese: IP em Blacklist DNS
§ Russian: DNS
§ Simplified Chinese: DNS IP
§ Spanish: IP en lista negra de DNS
Remarks
1204
Remark Description
system.
does PRTG require?
Parent device § If a Domain Name System (DNS) name is used as the host name of
the parent device, PRTG resolves it to an IP address before querying
blacklist servers.
Additional thresholds § During normal operation, there should be 0 hits and the sensor should
show the Up status. If the sensor can find the IP address on at least
one of the blacklist servers, it shows the Warning status by default.
You can set additional thresholds in the channel settings.
Knowledge Base § Knowledge Base: Is there a list of anti spam black list servers?
you add the sensor:
§ ptfsensor
1205
Sensor Settings
Sensor Settings
Setting Description
Blacklist Servers Define the blacklist servers that the sensor uses for the check. You can
enter a comma-separated list. The default is bl.spamcop.net.
For a list of servers, see the Knowledge Base: Is there a list of anti
spam black list servers?
With each scanning interval, PRTG queries all servers in the list. We
recommend that you do not enter more than 10 servers to make sure
that the check can be completed within the scanning interval of this
sensor. If you use too many blacklist servers, the sensor shows the error
message Timeout (code: PE018).
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
1206
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
1207
Channel Description
Sum The number of blacklist hits found

More
KNOWLEDGE BASE
Is there a list of anti spam black list servers?



1208
7.8.79 IPFIX Sensor
The IPFIX sensor receives traffic data from an Internet Protocol Flow Information Export (IPFIX)
compatible device and shows traffic by type. This sensor has several filter options to divide traffic into
different channels.
Make sure that the target device supports IPFIX if you want to use this sensor.
IPFIX Sensor
List 1216 .

§ Dutch: IPFIX
§ French: IPFIX
§ German: IPFIX
1209
§ Japanese: IPFIX
§ Portuguese: IPFIX
§ Russian: IPFIX
§ Simplified Chinese: IPFIX
§ Spanish: IPFIX
Remarks
Remark Description
IPFIX § This sensor requires that the IPFIX export is enabled on the target
system. The target system must send the flow data stream to the IP
address of the probe system.
Knowledge Base § Knowledge Base: What is the Active Flow Timeout in flow sensors?
probe device.
1210
you add the sensor:
§ bandwidthsensor
§ netflowsensor
IPFIX Specific Settings
Setting Description
Receive Packets on UDP Enter the UDP port number on which PRTG receives the flow packets. It
Port must match the UDP port number in the IPFIX export options of the
hardware router device. Enter an integer.
Sender IP Address Enter the IP address of the sending device that you want to receive the
IPFIX data from. Enter an IP address to only receive data from a specific
device or leave the field empty to receive data from any device on the
specified port.
Receive Packets on IP Select the IP addresses on which PRTG listens to IPFIX packets. The list
Address of IP addresses is specific to your setup. To select an IP address, enable
a check box in front of the respective line. The IP address that you select
must match the IP address in the IPFIX export options of the hardware
router device.
1211
Setting Description
Active Flow Timeout Enter a time span in minutes after which the sensor must receive new
(Minutes) flow data. If the timeout elapses and the sensor receives no new data
during this time, it shows the Unknown status. Enter an integer. The
maximum timeout is 60 minutes.
We recommend that you set the timeout one minute longer than the
timeout in the hardware router device.
If you set this value too low, flow information might be lost.
For more information, see the Knowledge Base: What is the Active
Flow Timeout in flow sensors?
Sampling Mode Define if you want to use the sampling mode:

§ Off: Use the standard flow.
§ On: Use the sampling mode and specify the Sampling Rate below.
This setting must match the setting in the xFlow exporter.
Sampling Rate This setting is only visible if you select On above.
Enter a number that matches the sampling rate in the exporting device. If
the number is different, monitoring results will be incorrect. Enter an
integer.
Stream Data Handling Define what PRTG does with the stream and packet data:
§ Discard stream data (recommended): Do not store the stream and
packet data.
§ Store stream data only for the 'Other' channel: Only store stream and
packet data that is not otherwise filtered and is therefore accounted to
the default Other channel. PRTG stores this data in the \StreamLog
name is Streams Sensor [ID] (1).csv. This setting is for debugging
purposes. PRTG overwrites this file with each scanning interval.
§ Store all stream data: Store all stream and packet data. This setting is
for debugging purposes. PRTG overwrites this file with each scanning
interval.
Use with caution. It can create huge data files. We recommend that
you only use this setting for a short time.
1212
Channel Configuration
Setting Description
Channel Selection Define the categories that the sensor accounts the traffic to:
§ Web: Internet web traffic.
§ File Transfer: Traffic from FTP.
§ Mail: Internet mail traffic.
§ Chat: Traffic from chat and instant messaging.
§ Remote Control: Traffic from remote control applications such as RDP,

SSH, Telnet, and Virtual Network Computing (VNC).
§ Infrastructure: Traffic from network services such as DHCP, DNS, Ident,

ICMP, and SNMP.
§ NetBIOS: Traffic from NetBIOS communication.
§ Citrix: Traffic from Citrix applications.
§ Other Protocols: Traffic from various other protocols via UDP and TCP.
For each group, you can select how many channels the sensor uses, that
is, how detailed the sensor divides the traffic:
§ No ( ): Do not account traffic of this group in its own channel. The
sensor accounts all traffic of this group to the default channel named
Other.
§ Yes ( ): Count all traffic of this group and summarize it in one
channel.
1213
Setting Description
§ Detail ( ): Count all traffic of this group and further divide it into
different channels. The traffic appears in several channels that you can
see in the Content column.
Extensive use of this option can cause load problems on the probe
system. We recommend that you set specific, well-chosen filters
for the data that you really want to analyze.
You can change the default configuration for groups and channels.
For more information, see the Knowledge Base: How can I change
the default groups and channels for flow and Packet Sniffer sensors?
Filtering
For more information, see section Filter Rules 1216 .
Filtering
Setting Description
Include Filter Define if you want to filter any traffic. If you leave this field empty, the
sensor includes all traffic. To include specific traffic only, define filters
using a special syntax.
Exclude Filter First, the sensor considers the filters in Include Filter. From this subset,
you can explicitly exclude traffic, using the same syntax.
1214
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Primary Toplist
Primary Toplist
Setting Description
Primary Toplist Define which Toplist is the primary Toplist of the sensor:
1215
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
§ [Any custom Toplists you add]
PRTG shows the primary Toplist in maps when you add a Toplist
object.
Inherited Settings
Toplists
For all Flow (NetFlow, jFlow, sFlow, IPFIX) and Packet Sniffer sensors, Toplists are available on the
sensor's Overview tab. Using Toplists, you can review traffic data for small time periods in great detail.
For more information, see section Toplists.
Filter Rules
For more information, see section Filter Rules for Flow, IPFIX, and Packet Sniffer Sensors.
Channel List
Channel Description
Chat The traffic from chat and instant messaging (IRC, AIM)
Citrix The traffic from Citrix applications
1216
Channel Description
FTP/P2P The traffic from file transfer (FTP/P2P)
Infrastructure The traffic from network services (DHCP, DNS, Ident, ICMP, SNMP)
Mail The internet mail traffic (IMAP, POP3, SMTP)
NetBIOS The traffic from NetBIOS communication
Other The traffic from various other protocols (UDP, TCP)
Remote Control The traffic from remote control applications (RDP, SSH, Telnet, Virtual
Network Computing (VNC))
Total The total traffic

Various The traffic from various other sources
WWW The traffic from the web (HTTP, HTTPS)
More
KNOWLEDGE BASE
What is the Active Flow Timeout in flow sensors?


How can I change the default groups and channels for flow and Packet Sniffer sensors?
PAESSLER TOOLS
NetFlow Tester
§ https://www.paessler.com/tools/netflowtester
1217
7.8.80 IPFIX (Custom) Sensor
The IPFIX (Custom) sensor receives traffic data from an Internet Protocol Flow Information Export (IPFIX)
compatible device and shows the traffic by type. With this sensor, you can define your own channel
definitions to divide traffic into different channels.
Make sure that the target device supports IPFIX if you want to use this sensor.
IPFIX (Custom) Sensor
List 1224 .

§ Dutch: IPFIX (aangepast)
§ French: IPFIX personnalisé
§ German: IPFIX (Benutzerdef.)
1218
§ Japanese: IPFIX( )
§ Portuguese: IPFIX (customizado)
§ Russian: IPFIX ( )
§ Simplified Chinese: IPFIX ( )
§ Spanish: IPFIX (personalizado)
Remarks
Remark Description
IPFIX § This sensor requires that the IPFIX export is enabled on the target
probe device.
1219
you add the sensor:
§ bandwidthsensor
§ netflowsensor
Setting Description
Port must match the UDP port number in the IPFIX export options of the
IPFIX data from. Enter an IP address to only receive data from a specific
specified port.
1220
Setting Description
Receive Packets on IP Select the IP addresses on which PRTG listens to IPFIX packets. The list
must match the IP address in the IPFIX export options of the hardware
router device.

Enter a number that matches the sampling rate in your device that
exports the flows. If the number is different, monitoring results will be
incorrect. Enter an integer.
Channel Definition Enter a channel definition to divide the traffic into different channels. Enter
each definition in one line. The sensor accounts all traffic that you do not
define a channel for to the default channel Other.
For more information, see section Channel Definitions for Flow, IPFIX,
and Packet Sniffer Sensors.
Extensive use of many filters can cause load problems on the probe
system. We recommend that you define specific, well-chosen filters
for the data that you really want to analyze. We recommend that you do
not use more than 20 channels in graphs and tables, and not more than
100 channels in total. For performance reasons, we recommend that you
add several sensors with fewer channels each.
packet data.
1221
Setting Description
interval.
Sensor Display
Sensor Display
Setting Description


other above.
1222
Setting Description
procedure to do so.
Filtering
Filtering
Setting Description
Primary Toplist
Primary Toplist
1223
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
Inherited Settings
Toplists
Filter Rules
Channel List
Channel Description
[Custom] The traffic by type according to the channel definition
1224
Channel Description
Other All traffic for which no channel is defined

More
KNOWLEDGE BASE


PAESSLER TOOLS
NetFlow Tester
1225
7.8.81 IPMI System Health Sensor
The IPMI System Health sensor monitors the status of a system via the Intelligent Platform Management
Interface (IPMI).
IPMI System Health Sensor
List 1230 .

§ Dutch: IPMI Systeemstatus
§ French: IPMI état du système
§ German: IPMI Systemzustand
§ Japanese: IPMI
§ Portuguese: Saúde do sistema IPMI
§ Russian: IPMI
§ Simplified Chinese: IPMI
1226
§ Spanish: Salud de sistema IPMI
Remarks
Remark Description
does PRTG require?
Credentials § This sensor requires that you explicitly specify the credentials of the
IPMI in the sensor settings.
IPMI v1.0 § This sensor only supports IPMI v1.0. If the target system uses IPMI
v2.0, try the Redfish System Health 1706 sensor.
channels.
probe device.
1227
you add the sensor:
§ ipmi
IPMI Credentials
IPMI Credentials
Setting Description
User Name Enter the user name for the IPMI.
Password Enter the password for the IPMI.

This sensor only supports passwords with a maximum of 16
characters.
IPMI Specific
IPMI Specific
Setting Description
Group The metric that this sensor monitors.
Result Handling Define what PRTG does with the log file results:
1228
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1229
Inherited Settings
Channel List
Channel Description
[Value] The value status, for example

§ Fan RPM
§ Status of a power supply
§ Temperatures, for example, the system temperature or the peripheral

temperature
§ Voltages
More
KNOWLEDGE BASE


1230
7.8.82 jFlow v5 Sensor
The jFlow v5 sensor receives traffic data from a jFlow v5-compatible device and shows the traffic by type.
This sensor has several filter options to divide traffic into different channels.
Make sure that the sensor matches the jFlow version that your device exports.
jFlow v5 Sensor
List 1239 .

§ Dutch: jFlow v5
§ French: jFlow v5
§ German: jFlow v5
§ Japanese: jFlow v5
§ Portuguese: jFlow v5
1231
§ Russian: jFlow v5
§ Simplified Chinese: jFlow v5
§ Spanish: jFlow v5
Remarks
Remark Description
jFlow § This sensor requires that the jFlow export of the respective version is
enabled on the target system. The target system must send the flow
data stream to the IP address of the probe system.
Clone sensor § If you clone this sensor to the same probe, PRTG keeps the selected
IP addresses 1234 on which it listens for Flow (NetFlow, jFlow, sFlow,
IPFIX) packets. If you clone this sensor to a different probe, PRTG
selects all available IP addresses by default.
§ Knowledge Base: How can I change the default groups and channels
for flow and Packet Sniffer sensors?
probe device.
1232
you add the sensor:
§ bandwidthsensor
§ jflowsensor
jFlow v5 Specific Settings
Setting Description
Port must match the UDP port number that in the jFlow export options of the
When you configure the export, make sure that you select the
appropriate jFlow version for this sensor.
jFlow data from. Enter an IP address to only receive data from a specific
specified port.
1233
Setting Description
Receive Packets on IP Select the IP addresses on which PRTG listens to jFlow packets. The list
must match the IP address in the jFlow export options of the hardware
router device.

integer.
packet data.
interval.
1234
Setting Description
Setting Description

ICMP, and SNMP.
Other.
1235
Setting Description

channel.
Filtering
Filtering
Setting Description
1236
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Primary Toplist
Primary Toplist
Setting Description
1237
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
Inherited Settings
Toplists
Filter Rules
The following filter rules apply to all Flow (NetFlow, jFlow, sFlow, IPFIX) and Packet Sniffer sensors.
Field Possible Filter Values
IP IP address or DNS name
Port Any number
SourceIP IP address or DNS name
SourcePort Any number
DestinationIP IP address or DNS name
1238
DestinationPort Any number
Protocol Transmission Control Protocol (TCP), User Datagram Protocol (UDP),

Internet Control Message Protocol (ICMP), Open Shortest Path First
(OSPF), any number
ToS Type of Service (ToS): any number
DSCP Differentiated Services Code Point (DSCP): any number
The following filter rules apply to jFlow v5 sensors only.
Interface Any number
ASI Any number
InboundInterface Any number
OutboundInterface Any number
SenderIP IP address of the sending device. Use this if you have several devices that
send flow data on the same port, and you want to divide the traffic of each
device into a different channel.
Possible values: IP address or DNS name
SourceASI Any number
DestinationASI Any number
Channel List
Channel Description
1239
Channel Description

More
KNOWLEDGE BASE


Where is the volume line in graphs?

1240
7.8.83 jFlow v5 (Custom) Sensor
The jFlow v5 (Custom) sensor receives traffic data from a jFlow v5-compatible device and shows the
traffic by type. With this sensor, you can define your own channel definitions to divide traffic into different
channels.
Make sure that the sensor matches the jFlow version that your device exports.
jFlow v5 (Custom) Sensor
List 1248 .

§ Dutch: jFlow v5 (Klant specifiek)
§ French: jFlow v5 personnalisé
§ German: jFlow v5 (Benutzerdefiniert)
§ Japanese: jFlow v5( )

§ Portuguese: jFlow v5 (customizado)
1241
§ Russian: jFlow v5 ( )
§ Simplified Chinese: jFlow v5 ( )

§ Spanish: jFlow v5 (personalizado)
Remarks
Remark Description
jFlow § This sensor requires that the jFlow export of the respective version is
probe device.
you add the sensor:
§ bandwidthsensor
1242
§ jflowsensor
Setting Description
Port must match the UDP port number that in the jFlow export options of the
jFlow data from. Enter an IP address to only receive data from a specific
specified port.
1243
Setting Description
Receive Packets on IP Select the IP addresses on which PRTG listens to jFlow packets. The list
must match the IP address in the jFlow export options of the hardware
router device.

1244
Setting Description

packet data.
interval.
Filtering
Filtering
Setting Description
1245
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Primary Toplist
Primary Toplist
Setting Description
1246
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
Inherited Settings
Toplists
Filter Rules
Port Any number
1247

(OSPF), any number
The following filter rules apply to jFlow v5 sensors only.
Interface Any number
ASI Any number
InboundInterface Any number
OutboundInterface Any number
SenderIP IP address of the sending device. Use this if you have several devices that
send flow data on the same port, and you want to divide the traffic of each
device into a different channel.
Possible values: IP address or DNS name
SourceASI Any number
DestinationASI Any number
Channel List
Channel Description
1248
Channel Description

More
KNOWLEDGE BASE



1249
7.8.84 LDAP Sensor
The LDAP sensor monitors directory services via the Lightweight Directory Access Protocol (LDAP). It
connects to the server by trying a "bind".
If the server does not respond or authentication fails, the sensor shows the Down status.
LDAP Sensor
List 1253 .

§ Dutch: LDAP
§ French: LDAP
§ German: LDAP
§ Japanese: LDAP
§ Portuguese: LDAP
§ Russian: LDAP
§ Simplified Chinese: LDAP
§ Spanish: LDAP
Remarks
1250
Remark Description
LDAP § This sensor officially supports Microsoft implementations of LDAP.

Other third-party LDAP implementations might work but are not
officially supported.
DNS name § This sensor requires a DNS name in the settings of the parent device if
you use a Secure Sockets Layer (SSL)/Transport Layer Security (TLS)
secured connection to the LDAP server.
you add the sensor:
§ ldapsensor
LDAP Specific
LDAP Specific
1251
Setting Description
Connection Security Define if the sensor uses an SSL/TLS-secured connection to the LDAP
server:
§ Use LDAP without connection security (default)
§ Use LDAP over SSL
If you select Use LDAP over SSL, you need to enter a DNS name in
the settings of the parent device. The sensor does not work with an
IP address.
Port Selection Define if you want to use a default port or a custom port for the
connection to the LDAP server:
§ Use default port (default): Use the default port. This is port 389 for
unsecure connections and port 636 for secure connections.
§ Use custom port: Use a custom port. Specify the Port below.
Port This setting is only visible if you select Use custom port above.
Enter a custom port for the connection to the LDAP server. Enter an
integer.
Distinguished Name Enter the distinguished name (DN) that you want to authenticate against
the LDAP server. Usually, this is the information for the user that you
want to authenticate with. For example, use the format
cn=Manager,dc=my-domain,dc=com for a DN on an OpenLDAP server.
Password Enter the password for the Distinguished Name.
Sensor Display
Sensor Display
Setting Description
1252
Setting Description



other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description

1253
More
KNOWLEDGE BASE

1254
7.8.85 Local Folder Sensor
The Local Folder sensor monitors a local folder on a probe system.
Local Folder Sensor
List 1260 .

§ Dutch: Lokale Map
§ French: Dossier local
§ German: Lokaler Ordner
§ Japanese:
§ Portuguese: Pasta local
§ Russian:
§ Spanish: Carpeta local
Remarks
1255
Remark Description
you add the sensor:
§ filesystem
§ folder
1256
Local Folder Specific
Local Folder Specific
Setting Setting
Path Enter the path of the folder that you want to monitor. For example, enter
C:\Windows. The folder must exist on the probe system.
The sensor only supports local paths.
Timeout (Sec.) Enter a timeout in seconds. If the scan of the folder takes longer, the
sensor cancels the request and shows an error message. If two
consecutive scans fail, the sensor shows the Down status. The default
value is 300 seconds (5 minutes). The maximum value is 1079 seconds
(17 minutes and 59 seconds).
performance issues.
Filter by File Name Select if you want to filter by file name:

§ Disable (default): Do not filter by file name.
§ Include filter: The sensor counts files that match the File Filter.
§ Exclude filter: The sensor counts files that do not match the File Filter.
1257
Setting Setting
File Filter This setting is only visible if you select Include filter or Exclude filter
above.
Enter a comma-separated list of file names, file formats, or patterns you

want to filter for. For example, '*.pdf, *.docx' includes or excludes files
with the file formats .pdf or .docx.
The file filter is not case-sensitive and supports wildcards (*).
Filter by File Age Select if you want to filter by file age:

§ Disable (default): Do not filter by file age.
§ Enable: Filter by file age.
Newer Than This setting is only visible if you select Enable above.
Enter a file age. The sensor only counts files that are younger than this
age.
Leave this field empty if you only want to filter for files with the Older
Than setting.
Older Than This setting is only visible if you select Enable above.
Enter a file age. The sensor only counts files that are older than this age.
Leave this field empty if you only want to filter for files with the Newer
Than setting.
File Age Filter Unit This setting is only visible if you select Enable above.
Select the time unit that you want to use for Filter by File Age:
§ Days (default)
§ Hours
§ Minutes
Sensor Display
Sensor Display
1258
Setting Setting


other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
1259
Setting Description
master node.
Inherited Settings
Channel List
Channel Description

Folder Count The number of folders
the future.
More
KNOWLEDGE BASE
1260
1261
7.8.86 Microsoft 365 Mailbox Sensor
The Microsoft 365 Mailbox sensor monitors a folder of a Microsoft 365 mailbox via Microsoft Graph.
Microsoft 365 Mailbox Sensor
List 1271 .

§ Dutch: Microsoft 365 Mailbox
§ French: Microsoft 365 boîte aux lettres
§ German: Microsoft 365 Postfach
§ Japanese: Microsoft 365
§ Portuguese: Caixa de correio do Microsoft 365
§ Russian: Microsoft 365

§ Simplified Chinese: Microsoft 365
§ Spanish: Buzón de Microsoft 365
Remarks
1262
Remark Description
Permission for the APIs § This sensor requires permissions for Microsoft Graph.
§ This sensor requires the following delegated permissions to query data

from Microsoft Graph:
ú Microsoft Graph / User.Read
ú Microsoft Graph / Mail.Read
ú Microsoft Graph / Mail.Read.Shared (optional)
ú Microsoft Graph / offline_access
For more information, see the Knowledge Base: How do I obtain

credentials and set permissions for the Microsoft 365 Mailbox
sensor?
Redirect URIs § This sensor requires that you provide a redirect URI in the Microsoft
Azure Portal.
§ This sensor requires that you provide the DNS name or an IP address
of your PRTG web server as redirect URI in the Microsoft Azure Portal
according the following pattern: https://<yourprtgserver>/ms365.htm
Microsoft Azure only accepts redirect URIs that start with HTTPS.
credentials and set permissions for the Microsoft 365 Mailbox
sensor?
Secure HTTPS server § This sensor requires that the PRTG web server accepts incoming
HTTPS requests.
For more information, see section PRTG Web Server in chapter User
Interface.
Credentials § This sensor requires credentials for Microsoft 365.
Knowledge Base § Knowledge Base: How do I obtain credentials and set permissions for
the Microsoft 365 Mailbox sensor?
1263
you add the sensor:
§ mailsensor
§ microsoft365
§ microsoft365sensor
Microsoft 365 Specific
Setting Description
Folder Name The name of the target folder that this sensor monitors.
Folder Path The path of the target folder that this sensor monitors.
Microsoft OAuth 2.0 Specific
Microsoft OAuth 2.0 Specific
1264
Setting Description
Authorization Click Renew to start the Microsoft Azure authorization process.
Microsoft 365 Mailbox
Microsoft 365 Mailbox
Setting Description
Shared Mailbox User The user principal name of a shared mailbox to which the authenticated
Principal Name (optional) user account has access.
In most cases, the user principal name is the email address of the
shared mailbox.
1265
Microsoft 365 Settings
Setting Description
Filter by 'Subject' Select if you want to filter the emails by the 'Subject' field:
§ Disable (default): Do not use Filter by 'Subject'.
§ 'Subject' matches exact string: Filter emails whose 'Subject' field

matches the defined string exactly.
§ 'Subject' contains all strings: Filter emails whose 'Subject' field contains
all defined strings.
§ 'Subject' contains one or more strings: Filter emails whose 'Subject'
field contains at least one of the defined strings.
§ 'Subject' matches regular expression: Filter emails whose 'Subject' field
matches the defined regular expression.
1266
Setting Description
The regular expressions filter will result in the Down status if there
are more than 10,000 emails in the mailbox folder you want to
monitor. This is because the regular expression filter is applied after the
emails are retrieved from the API. The larger the volume of emails, the
greater the impact on performance. Enable the Filter by 'Age' setting or
use a non-regular expression filter in addition to the regular expression
filter to reduce the number of emails.
If you enable Filter by 'Subject', Filter by 'From', or Filter by 'Body',

the sensor creates up to three additional channels that monitor the
emails that match your filters.
If you disable the filters, the additional channels remain, but do not
receive data anymore.
Search for This setting is only visible if you choose to filter by the 'Subject' field
above.
Enter a string or regular expression that you want to use for Filter by
'Subject'.
If you select 'Subject' contains all strings or 'Subject' contains one or
more strings above, you can also enter a comma-separated list of
strings to search for more than one string. For example, if you select
'Subject' contains all strings and enter backup and failed, the sensor
counts all items that contain both strings. If you select 'Subject' contains
one or more strings and enter backup and failed, the sensor counts all
items that contain at least one of the strings.
Filter by 'From' Select if you want to filter the emails by the 'From' field:
§ Disable (default): Do not use Filter by 'From'.
§ 'From' matches exact string: Filter emails whose 'From' field matches
the defined string exactly.
§ 'From' contains all strings: Filter emails whose 'From' field contains all
defined strings.
§ 'From' contains one or more strings: Filter emails whose 'From' field
contains at least one of the defined strings.
§ 'From' matches regular expression: Filter emails whose 'From' field
matches the defined regular expression.
1267
Setting Description

Search for This setting is only visible if you choose to filter by the 'From' field above.
'From'.
If you select 'From' contains all strings or 'From' contains one or more
strings above, you can also enter a comma-separated list of strings
to search for more than one string. For example, if you select 'From'
contains all strings and enter backup and failed, the sensor counts all
items that contain both strings. If you select 'From' contains one or more
strings and enter backup and failed, the sensor counts all items that
contain at least one of the strings.
Filter by 'Body' Select if you want to filter the emails by the text in the 'Body' field:
§ Disable (default): Do not use Filter by 'Body'.
§ 'Body' matches exact string: Filter emails whose body matches the
defined string exactly.
§ 'Body' contains all strings: Filter emails whose body contains all
defined strings.
§ 'Body' contains one or more strings: Filter emails whose body contains
at least one of the defined strings.
§ 'Body' matches regular expression: Filter emails whose body matches

the defined regular expression.

Search for This setting is only visible if you choose to filter by the 'Body' field above.
1268
Setting Description
'Body'.
If you select 'Body' contains all strings or 'Body' contains one or more
strings above, you can also enter a comma-separated list of strings
to search for more than one string. For example, if you select 'Body'
contains all strings and enter backup and failed, the sensor counts all
items that contain both strings. If you select 'Body' contains one or more
strings and enter backup and failed, the sensor counts all items that
contain at least one of the strings.
Filter by 'Age' Select if you want to filter the emails by their age. The filter will be applied
to all channels of the sensor.
Maximum Age (Minutes) This setting is only visible if you enable Filter by 'Age' above.
Enter the maximum age in minutes. The sensor only processes emails
that are younger. Enter an integer.
Sensor Display
Sensor Display
Setting Description


1269
Setting Description
other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
1270
Channel List
Channel Description
Matching Emails The number of emails that match the defined filters
This channel is only created if you enable Filter by 'Subject', Filter by
'From', or Filter by 'Body'.
Newest Email The age of the newest email
Newest Matching Email The age of the newest email that matches the defined filters
Number of Emails The number of emails

Oldest Email The age of the oldest email
Oldest Matching Email The age of the oldest email that matches the defined filters

More
KNOWLEDGE BASE
How can I provide feedback about PRTG and contribute to the PRTG development?
How do I obtain credentials and set permissions for the Microsoft 365 Mailbox sensor?

1271
7.8.87 Microsoft 365 Service Status Sensor
The Microsoft 365 Service Status sensor monitors the overall status of all services of a Microsoft 365
subscription.
Microsoft 365 Service Status Sensor
List 1276 .

§ Dutch: Microsoft 365 Service Status
§ French: Microsoft 365 statut de service
§ German: Microsoft 365 Dienststatus
§ Portuguese: Status do serviço do Microsoft 365

§ Spanish: Estado del servicio Microsoft 365
Remarks
1272
Remark Description
ú API / Permissions name: Microsoft Graph / ServiceHealth.Read.All

credentials and set permissions for the Microsoft 365 Service Status
sensors?
the Microsoft 365 Service Status sensors?
you add the sensor:
§ microsoft365
1273
Setting Description
API Request Retry Enter a number how often the sensor queries the Microsoft Graph if an
API query returns no result before the sensor shows the Down status.
Enter an integer. The default value is 3. The maximum value is 10. If you
enter 0, the sensor does not retry to query the APIs.
Sensor Display
Sensor Display
Setting Description


1274
Setting Description
other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
1275
Channel List
Channel Description
Degraded Services The number of degraded services
Interrupted Services The number of interrupted services
Operational Services The number of operation services

Warning State Services The number of services in the warning status
More
KNOWLEDGE BASE

1276
7.8.88 Microsoft 365 Service Status Advanced Sensor
The Microsoft 365 Service Status Advanced sensor monitors the detailed status of a service of a
Microsoft 365 subscription.
Microsoft 365 Service Status Advanced Sensor
List 1281 .

§ Dutch: Microsoft 365 Servicestatus Geavanceerd
§ French: Microsoft 365 statut de service avancé
§ German: Microsoft 365 Dienststatus (Erweitert)
§ Portuguese: Status do serviço do Microsoft 365 (Avançado)

§ Spanish: Estado del servicio de Microsoft 365 (avanzado)
Remarks
1277
Remark Description
ú API / Permissions name: Microsoft Graph / ServiceHealth.Read.All

credentials and set permissions for the Microsoft 365 Service Status
sensors?
channels.
the Microsoft 365 Service Status sensors?
you add the sensor:
§ microsoft365
1278
Setting Description
Service The name of the Microsoft 365 service that this sensor monitors.
Workload ID The Microsoft 365 Workload ID of the service that this sensor monitors.
Setting Description
API Request Retry Enter a number how often the sensor queries the Microsoft Graph if an
API query returns no result before the sensor shows the Down status.
Enter an integer. The default value is 3. The maximum value is 10. If you
enter 0, the sensor does not retry to query the APIs.
Sensor Display
Sensor Display
1279
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
1280
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Overall Status The overall services status
§ Up status: Operational
§ Warning status: Degraded, Warning
§ Down status: Interrupted
[Service] Due to changes in the Microsoft 365 Management APIs, this sensor
cannot create service channels anymore.
More
KNOWLEDGE BASE

1281
7.8.89 Microsoft Azure SQL Database Sensor
The Microsoft Azure SQL Database sensor monitors the metrics of an Azure SQL Database (single
database or elastic pool) in a Microsoft Azure subscription.
Microsoft Azure SQL Database Sensor
List 1287 .

§ Dutch: Microsoft Azure SQL database
§ French: Microsoft Azure base de données SQL
§ German: Microsoft Azure SQL-Datenbank
§ Japanese: Microsoft Azure SQL Database
§ Portuguese: Banco de dados SQL do Microsoft Azure
1282
§ Russian: Microsoft Azure SQL
§ Simplified Chinese: Microsoft Azure SQL
§ Spanish: Base de datos SQL de Microsoft Azure
Remarks
Remark Description
Permissions for the § This sensor requires an Azure custom role with permissions for specific
Azure custom role actions.
§ Create an Azure custom role and add permissions for the following
actions:
ú "Microsoft.Sql/servers/*/read",
ú "Microsoft.Insights/Metrics/providers/Metrics/Read",
ú "Microsoft.Insights/Metrics/Microsoft.Insights/Read",
ú "Microsoft.Insights/Metrics/Read",
ú "Microsoft.Insights/Metricnamespaces/Read",
ú "Microsoft.Insights/MetricDefinitions/providers/Microsoft.Insights/Rea
d",
ú "Microsoft.Insights/Components/providers/Microsoft.Insights/MetricD
efinitions/Read"

credentials and create custom roles for the Microsoft Azure sensors?
Credentials § This sensor requires credentials for Microsoft Azure.
Knowledge Base § Knowledge Base: How do I obtain credentials and create custom roles
for the Microsoft Azure sensors?
1283
you add the sensor:
§ azure
§ microsoftazure
§ microsoftazuresqldatabase
Microsoft Azure Specific
Setting Description
Azure SQL Database The name of the Azure SQL Database that this sensor monitors.
Name
If you change the database name in your Microsoft Azure
subscription, you must add the sensor anew.
Azure SQL Database ID The ID of the Azure SQL Database that this sensor monitors.
Azure SQL Server Name The name of the Azure SQL server that hosts the Azure SQL Database.
1284
Setting Description
Resource Type The resource type of the Azure SQL Database that this sensor monitors.
This can be a single database or an elastic pool in a virtual core (vCore)
based purchasing model or a DTU-based purchasing model.
If you change the resource type in your Microsoft Azure subscription,
you must add the sensor anew.
Region The Azure region of the Azure SQL Database that this sensor monitors.
Purchasing Model The purchasing model of the Azure SQL Database. This can be vCore
based or DTU based.
Elastic Pool The name of the elastic pool if the resource type of the Azure SQL
Database is an elastic pool. If the resource type is not an elastic pool, the
field shows n/a.
Sensor Display
Sensor Display
Setting Description


1285
Setting Description
other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
1286
Channel List
Channel Description
Connections Failed The number of failed connections
CPU Used % The CPU usage (%)

Data I/O % The data I/O operations (%)
Data Space Used The data space usage
Data Space Used % The data space usage (%)
Deadlocks The number of deadlocks
DTU % The DTUs (%)
DTU Limit The DTU limit
DTU Used The used DTU
eDTU Limit The eDTU limit
eDTU Used The used eDTU
Log I/O The log I/O operations
Sessions % The sessions (%)
More
KNOWLEDGE BASE
1287
1288
7.8.90 Microsoft Azure Storage Account Sensor
The Microsoft Azure Storage Account sensor monitors the storage account in a Microsoft Azure
subscription.
Microsoft Azure Storage Account Sensor
List 1293 .

§ Dutch: Microsoft Azure Storage Account
§ French: Microsoft Azure compte de stockage
§ German: Microsoft Azure Speicherkonto
§ Japanese: Microsoft Azure
§ Portuguese: Conta de armazenamento do Microsoft Azure
§ Russian: Microsoft Azure

§ Simplified Chinese: Microsoft Azure
§ Spanish: Cuenta de almacenamiento de Microsoft Azure
1289
Remarks
Remark Description
actions:
ú "Microsoft.Storage/storageAccounts/read",
ú "Microsoft.Insights/Metrics/Read"

channels.
1290
you add the sensor:
§ azure
§ microsoftazure
§ microsoftazurestorageaccount
Setting Description
Storage Account Name The name of the storage account that this sensor monitors.
Storage Account ID The ID of the storage account that this sensor monitors.
Account Kind The kind of the storage account that this sensor monitors.
Region The Azure region of the storage account that this sensor monitors.
Resource Group The Microsoft Azure resource group of the storage account that this
sensor monitors.
Sensor Display
Sensor Display
1291
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
1292
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Average E2E Latency The average E2E latency

Request Breakdown The number of request breakdowns
Storage Latency The latency of the storage
Total Egress The total egress
Total Ingress The total ingress
Used Capacity The used capacity
More
KNOWLEDGE BASE
1293

1294
7.8.91 Microsoft Azure Subscription Cost Sensor
The Microsoft Azure Subscription Cost sensor monitors the cost in a Microsoft Azure subscription.
Microsoft Azure Subscription Cost Sensor
List 1299 .

§ Dutch: Microsoft Azure Abonnementskosten
§ French: Microsoft Azure coût de l’abonnement
§ German: Microsoft Azure Abonnementkosten
§ Portuguese: Custo da assinatura do Microsoft Azure

1295
§ Spanish: Coste de la suscripción a Microsoft Azure
Remarks
Remark Description
actions:
ú "Microsoft.Consumption/*/read",
ú "Microsoft.Consumption/*/action",
ú "Microsoft.CostManagement/query/read",
ú "Microsoft.Billing/*/read"

CSP subscriptions § This sensor does not support cloud solution provider (CSP)
subscriptions.
1296
you add the sensor:
§ azure
§ microsoftazure
§ microsoftazuresubscriptioncost
Setting Description
Budgets If additional channels for the budget usage in your Microsoft Azure
subscription are enabled or disabled.
Cost Forecast If the additional channel with a cost forecast for your Microsoft Azure
subscription is enabled or disabled.
Most Expensive Service Select if you want to show the most expensive service of your Microsoft
Azure subscription in the sensor message:
§ Disable (default)
1297
Setting Description
§ Enable
Most Expensive Service This setting is only visible if you select Enable above.
Category
Select the category for which you want to show the most expensive
service in the sensor message:
§ Resource group
§ Resource type
§ Resource ID
§ Location
§ Service name
Sensor Display
Sensor Display
Setting Description


other above.
1298
Setting Description
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Channel List
1299
Channel Description
Current Period Cost The current period cost
Forecast The cost forecast
[Budget] Used The used budget

[Budget] Used % The used budget (%)
Previous Period Cost The previous period cost
More
KNOWLEDGE BASE

1300
7.8.92 Microsoft Azure Virtual Machine Sensor
The Microsoft Azure Virtual Machine sensor monitors the status of a virtual machine (VM) in a Microsoft
Azure subscription.
Microsoft Azure Virtual Machine Sensor
List 1305 .

§ Dutch: Microsoft Azure Virtuele Machine
§ French: Microsoft Azure machine virtuelle
§ German: Microsoft Azure Virtueller Computer
§ Portuguese: Máquina virtual do Microsoft Azure

§ Spanish: Máquina virtual Microsoft Azure
Remarks
1301
Remark Description
actions:
ú "Microsoft.Network/publicIPAddresses/read"
ú "Microsoft.Network/virtualNetworks/read"
ú "Microsoft.Network/loadBalancers/read"
ú "Microsoft.Network/networkInterfaces/read"
ú "Microsoft.Compute/virtualMachines/*/read"
ú "Microsoft.Insights/Metrics/providers/Metrics/Read"
ú "Microsoft.Insights/Metrics/Microsoft.Insights/Read"
ú "Microsoft.Insights/Metrics/Read"
ú "Microsoft.Insights/Metricnamespaces/Read"
ú "Microsoft.Insights/MetricDefinitions/providers/Microsoft.Insights/Rea
d"
ú "Microsoft.Insights/Components/providers/Microsoft.Insights/MetricD
efinitions/Read"

channels.
1302
you add the sensor:
§ azure
§ microsoftazure
§ microsoftazurevirtualmachine
Setting Description
Virtual Machine Name The name of the VM that this sensor monitors.
Virtual Machine ID The ID of the VM that this sensor monitors.
Operating System The operating system of the server on which the VM runs.
1303
Setting Description
Resource Group The Microsoft Azure resource group of the VM that this sensor monitors.
Region The Azure region of the VM that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1304
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Average CPU Usage The average CPU load

CPU Credits Consumed The number of consumed CPU credits
1305
Channel Description
CPU Credits Remaining The number of remaining CPU credits
Status The VM status

§ Up status: Running (Billed), Starting (Not Billed)
§ Warning status: Stopped (Billed), Stopping (Billed)
§ Down status: Deallocated (Not Billed), Deallocating (Not Billed)
More
KNOWLEDGE BASE

1306
7.8.93 Microsoft SQL v2 Sensor
The Microsoft SQL v2 sensor monitors a database on a Microsoft SQL server and executes a query.
The sensor can also process the data table and show the values that you define in individual
channels.
Microsoft SQL v2 Sensor
List 1318 .

§ Dutch: Microsoft SQL v2
§ French: Microsoft SQL v2
§ German: Microsoft SQL v2
§ Japanese: Microsoft SQL v2
§ Portuguese: Microsoft SQL v2
§ Russian: Microsoft SQL v2
§ Simplified Chinese: Microsoft SQL v2
§ Spanish: Microsoft SQL v2
Remarks
1307
Remark Description

computer?
does PRTG require?
Microsoft SQL server § This sensor supports Microsoft SQL server as of version 2005.
Lookups § This sensor can use lookups 1314 . Select Lookup as Channel #x Unit

a guide?

probe device.
1308
you add the sensor:
§ sqlsensor
Database Specific
Database Specific
Setting Description
Database Enter the name of the SQL database to which the sensor connects, for
example, MyDatabase. This is a logical entity on the database server
where database objects exist.
SQL Server Instance Define if you want to use an instance name for the database connection:
§ No instance name required (default): Use the default instance for the
connection.
§ Use instance name: Use a named instance. Specify the Instance
Name below.
1309
Setting Description
Instance Name This setting is only visible if you select Use instance name above.
Enter the name of the instance that you want to monitor.
Encryption Define the encryption usage for the database connection:
§ Use server defaults (default): Only encrypt the database connection if

the database server enforces encryption.
§ Enforce encryption but do not validate server certificate: Make sure that
the database connection is encrypted.
§ Enforce encryption and validate server certificate: Force encryption and
validate the database server certificate. This approach provides the
highest level of security and can help prevent man-in-the-middle
attacks, for example.
The sensor only validates the certificate if the database server
enforces encryption.
Data
Data
Setting Description
cluster nodes.
1310
Setting Description


into the query.
content:
1311
Setting Description

edited).


as the number 0.

Number.
Databases.
1312
Setting Description
Channel #x Name This setting is only visible if you select Process data table for the setting
1313
Setting Description

data table.
Channel #x Unit
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
1314
Setting Description
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
Sensors.
Channel #x Custom Unit This setting is only visible if you select Custom above.
Channel #x Lookup This setting is only visible if you select Lookup above.

1315
Setting Description

point.


change.
1316
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1317
Inherited Settings
Channel List
Channel Description
SQL Variables
1318
More
KNOWLEDGE BASE




How do I monitor the size of a Microsoft SQL Server database?

1319
7.8.94 Modbus RTU Custom Sensor
The Modbus RTU Custom sensor connects to a Modbus Remote Terminal Unit (RTU) server and
monitors up to ten returned numeric values.
Modbus RTU Custom Sensor
List 1327 .

§ Dutch: Modbus RTU Aangepast
§ French: Modbus RTU personnalisé
§ German: Modbus RTU (Benutzerdefiniert)
§ Japanese: Modbus RTU
§ Portuguese: Modbus RTU customizado
§ Russian: Modbus RTU

§ Simplified Chinese: Modbus RTU
§ Spanish: Modbus RTU (personalizado)
Remarks
1320
Remark Description
channels.
Serial port § This sensor always uses the serial port of the probe device.
Knowledge Base § Knowledge Base: How can I apply Zoom Service Status sensors and
Modbus sensors via device templates?
probe device.
Add Sensor
Setting Description
Channel #1 - #10 Name Enter a name for the channel.

sensor.
Channel #1 - #10 Unit Enter a unit for the channel.

sensor.
Channel #2 - #10 You can define up to 10 channels. You must define at least one channel,
§ Disable (default): Do not create this channel.
§ Enable: Create this channel. Specify at least the name, type, and
register number for this channel below.
1321
you add the sensor:
§ modbus
Modbus RTU Specific
Modbus RTU Specific
1322
Setting Description
Device COM Port Enter the component object model (COM) port of the serial port device.
On Windows systems, the COM port of the device looks like this, for
example: COM3.
Baud Rate Enter the speed of the serial connection in baud. The default baud rate is
9600.
Parity Select the parity of the serial connection:

§ None (default)
§ Even
§ Odd
Data Bits Select the number of the data bits of the serial connection:
§ 8 (default)
§ 7
§ 6
§ 5
Stop Bits Select the number of stop bits of the serial connection:
§ 1 (default)
§ 2
Retry Attempts Enter the number of retries until a timeout occurs. If you enter 0, the
sensor does not retry the communication attempt. The default value is 3.
Enter an integer.
Receive Timeout (msec) Enter a receive timeout in milliseconds (msec). If the reply from the device
takes longer than this value, the request is aborted and triggers an error
message. The default value is 500 msec (0.5 seconds).
Unit ID Enter the Modbus unit ID that you want to monitor.

In a standard Modbus network, there are up to 247 unit IDs, each
with a unique assigned identifier from 1 to 247.
Byte Order Select the sequence of the transmitted information:

§ Big-endian (AB CD)
§ Little-endian (DC BA)
§ Big-endian byte swap (BA DC)
1323
Setting Description
§ Little-endian byte swap (CD AB)
Modbus Channel Specific
Setting Description
Channel #1 - #10 Select the type of the register:

Register Type
§ Coil (default): Coil numbers start with 0 and range from 00001 to 09999.
§ Discrete input: Discrete input numbers start with 1 and range from
10001 to 19999.
§ Input register: Input register numbers start with 3 and range from 30001
to 39999.
§ Holding register: Holding register numbers start with 4 and range from
40001 to 49999.
§ Input register bit: Select Input register bit to monitor a specific bit of the
received value. Input register numbers start with 3 and range from
30001 to 39999.
§ Holding register bit: Select Holding register bit to monitor a specific bit
of the received value. Holding register numbers start with 4 and range
from 40001 to 49999.
After sensor creation, this setting shows the register type of the
channel value.
Channel #1 - #10 Enter the register number from which you want to retrieve information.
Register Number
1324
Setting Description
The register number must be a number that contains one to five

digits. The sensor supports numbers between 0 and 65534.
Depending on your Modbus device, you might need to remove the
register type prefix. For example, you need to enter 60 for the input
register 30060 or 316 for the holding register 40316.
Channel #1 - #10 Value This setting is only visible if you select Input register or Holding register
Type above.
Select the value type that the channel displays:

§ Absolute (default): Integer64 values with or without an operational sign,
such as 10 or 120 or -12 or 120.
§ Delta (counter): The sensor calculates the difference between the last
value and the current value. The sensor additionally divides the delta
value by a time period to indicate a speed value. The sensor ignores
this setting if you select Double or Float as Channel #x Data Type.
This mode does not support negative values and decreasing values.
Channel #1 - #10 Data This setting is only visible if you select Input register or Holding register
Type above.
Select the data type of the register:

§ 16-bit integer (default)
§ Unsigned 16-bit integer
§ 32-bit integer
§ 64-bit integer
§ Float
§ Double
Channel #1 - #10 This setting is only visible if you select Input register or Holding register
Register Width above.
Select the width of the value in the register:

§ 16 bits wide (default)
§ 32 bits wide
1325
Setting Description
§ 64 bits wide
Channel #1 - #10 Bit This setting is only visible if you select Input register or Holding register
Index above.
Enter the index of the bit that you want to monitor.

Enter a value between 0 and 15, 31, or 63, depending on the Channel
#1 - #10 Register Width. 0 monitors the least significant bit. To
monitor the most significant bit, enter 15 for a 16-bit register, 31 for a 32-
bit register, or 63 for a 64-bit register.
Sensor Display
Sensor Display
Setting Description


other above.
1326
Setting Description
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Channel List
1327
Channel Description
[Value] The returned numeric values in up to ten channels
More
KNOWLEDGE BASE
How can I apply Zoom Service Status sensors and Modbus sensors via device templates?

1328
7.8.95 Modbus TCP Custom Sensor
The Modbus TCP Custom sensor connects to a Modbus Transmission Control Protocol (TCP) server and
monitors up to ten returned numeric values.
Modbus TCP Custom Sensor
List 1336 .

§ Dutch: Modbus TCP Aangepast
§ French: Modbus TCP personnalisé
§ German: Modbus TCP (Benutzerdefiniert)
§ Japanese: Modbus TCP
§ Portuguese: Modbus TCP customizado
§ Russian: Modbus TCP

§ Simplified Chinese: Modbus TCP
§ Spanish: Modbus TCP (personalizado)
Remarks
1329
Remark Description
channels.
Add Sensor
Setting Description
Channel #1 - #10 Name Enter a name for the channel.
sensor.
Channel #1 - #10 Unit Enter a unit for the channel.
sensor.
§ Enable: Create this channel. Specify at least the name, type, and
register number for this channel below.
1330
you add the sensor:
§ modbus
Modbus TCP Specific
Modbus TCP Specific
Setting Description
Port Enter the port for the connection to the Modbus TCP server. The default
port is 502.
Receive Timeout (msec) Enter a receive timeout in milliseconds (msec). If the reply from the device
takes longer than this value, the request is aborted and triggers an error
message. The default value is 500 msec (0.5 seconds).
Unit ID Enter the Modbus unit ID that you want to monitor.
1331
Setting Description
In a standard Modbus network, there are up to 255 unit IDs, each

with a unique assigned identifier from 1 to 255.
Byte Order Select the sequence of the transmitted information:

§ Big-endian (AB CD)
§ Little-endian (DC BA)
§ Big-endian byte swap (BA DC)
§ Little-endian byte swap (CD AB)
Setting Description
Channel #1 - #10 Select the type of the register:

Register Type
§ Coil (default): Coil numbers start with 0 and range from 00001 to 09999.
§ Discrete input: Discrete input numbers start with 1 and range from
10001 to 19999.
§ Input register: Input register numbers start with 3 and range from 30001
to 39999.
§ Holding register: Holding register numbers start with 4 and range from
40001 to 49999.
§ Input register bit: Select Input register bit to monitor a specific bit of the
received value. Input register numbers start with 3 and range from
30001 to 39999.
1332
Setting Description
§ Holding register bit: Select Holding register bit to monitor a specific bit
of the received value. Holding register numbers start with 4 and range
from 40001 to 49999.
Channel #1 - #10 Enter the register number from which you want to retrieve information.
Register Number
The register number must be a number that contains one to five
digits. The sensor supports numbers between 0 and 65534.
Depending on your Modbus device, you might need to remove the
register type prefix. For example, you need to enter 60 for the input
register 30060 or 316 for the holding register 40316.
Channel #1 - #10 Value This setting is only visible if you select Input register or Holding register
Type above.
Select the value type that the channel displays:

§ Absolute (default): Integer64 values with or without an operational sign,
such as 10 or 120 or -12 or 120.
§ Delta (counter): The sensor calculates the difference between the last
value and the current value. The sensor additionally divides the delta
value by a time period to indicate a speed value. The sensor ignores
this setting if you select Double or Float as Channel #x Data Type.
Channel #1 - #10 Data This setting is only visible if you select Input register or Holding register
Type above.
Select the data type of the register:

§ 16-bit integer (default)
§ 32-bit integer
§ 64-bit integer
§ Float
§ Double
1333
Setting Description
Channel #1 - #10 This setting is only visible if you select Input register or Holding register
Register Width above.
Select the width of the value in the register:

§ 16 bits wide (default)
§ 32 bits wide
§ 64 bits wide
Channel #1 - #10 Bit This setting is only visible if you select Input register or Holding register
Index above.
Enter the index of the bit that you want to monitor.

Enter a value between 0 and 15, 31, or 63, depending on the Channel
#1 - #10 Register Width. 0 monitors the least significant bit. To
monitor the most significant bit, enter 15 for a 16-bit register, 31 for a 32-
bit register, or 63 for a 64-bit register.
Sensor Display
Sensor Display
Setting Description

1334
Setting Description

other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
1335
Channel List
Channel Description
More
KNOWLEDGE BASE

1336
7.8.96 MQTT Round Trip Sensor
The MQTT Round Trip sensor monitors the availability of a Message Queue Telemetry Transport (MQTT)
broker (server), connects to the broker as a publishing and subscribing client, and sends the data
packets using a predefined topic.
MQTT Round Trip Sensor
List 1341 .

§ Dutch: MQTT Heen en Terug
§ French: MQTT aller-retour
§ German: MQTT Round Trip
§ Japanese: MQTT
§ Portuguese: Ida e volta MQTT
§ Russian: MQTT
§ Simplified Chinese: MQTT
§ Spanish: Ida y vuelta MQTT
Remarks
1337
Remark Description
Credentials § This sensor requires credentials for MQTT.
New framework § This sensor was converted to a new framework. MQTT Round Trip
sensors that were added before PRTG 20.2.59 do not work anymore.
We recommend that you pause existing sensors to keep their historic
data. To continue monitoring, please add a new MQTT Round Trip
sensor.
channels.
you add the sensor:
§ mqtt
§ mqttroundtrip
§ roundtrip
1338
MQTT Specific
MQTT Specific
Setting Description
Topic Enter the topic for the round trip. The default is PRTG/roundtrip/%
sensorid.
PRTG replaces %sensorid with the sensor's ID.
Connection Settings Define the connection settings for the connection to the MQTT broker:
§ Use default settings: Use the default connection settings.
§ Use custom settings: Use a ClientID that you can specify below.
ClientID This setting is only visible if you select Use custom settings above.
Enter the ClientID for the connection to the MQTT broker. The default is
PRTG_%sensorid.
PRTG replaces %sensorid with the sensor's ID. For the subscribing
client, PRTG automatically adds _subscriber to the ClientID. For the
publishing client, PRTG automatically adds _publisher to the ClientID.
Sensor Display
Sensor Display
Setting Description
1339
Setting Description



other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
§ Discard result: Do not store the sensor result.
master node.
1340
Inherited Settings
Channel List
Channel Description
Publisher Connection The time it takes the publisher to connect

Time
Round Trip Time The RTT of the message (after both publisher and subscriber connect)
Status The round trip status

§ Up status: Roundtrip Complete
§ Down status: Message Not Received, Message Not Sent, Publisher

Could Not Connect, Subscriber Could Not Connect
Subscriber Connection The time it takes the subscriber to connect

Time
More
KNOWLEDGE BASE

1341
7.8.97 MQTT Statistics Sensor
The MQTT Statistics sensor monitors a Message Queue Telemetry Transport (MQTT) topic.
MQTT Statistics Sensor
List 1345 .

§ Dutch: MQTT Statistieken
§ French: MQTT statistiques
§ German: MQTT Statistik
§ Japanese: MQTT
§ Portuguese: Estatísticas MQTT
§ Russian: MQTT
§ Spanish: Estadísticas MQTT
Remarks
1342
Remark Description
you add the sensor:
§ mqtt
§ mqttstatistics
MQTT Specific
MQTT Specific
Setting Description
Topic Enter the topic that you want to monitor.

The sensor supports single-level (+) and multi-level (#) wildcards.
1343
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
1344
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Active Topics The number of active MQTT topics
Messages Received The number of messages received since the last scan
Payload Received The payload received
1345
More
KNOWLEDGE BASE

1346
7.8.98 MQTT Subscribe Custom Sensor
The MQTT Subscribe Custom sensor subscribes to a Message Queue Telemetry Transport (MQTT) topic
and monitors up to ten numeric values from the received JavaScript Object Notation (JSON) data.
MQTT Subscribe Custom Sensor
List 1352 .

§ Dutch: MQTT Abonneren Aangepast
§ French: MQTT abonnement personnalisé
§ German: MQTT Subscribe (Benutzerdefiniert)
§ Japanese: MQTT
§ Portuguese: Assinatura customizada MQTT
§ Russian: MQTT
§ Spanish: Suscriptor MQTT personalizado
Remarks
1347
Remark Description
Add Sensor
Setting Description
Channel #1 Name Enter a name for the channel.

sensor.
Channel #1 Unit Enter the unit for the numeric value that this sensor monitors.
sensor.
you add the sensor:
§ mqtt
§ mqttsubscribecustom
1348
MQTT Specific
MQTT Specific
Setting Description
Topic Enter the topic that you want to monitor.

The sensor supports single-level (+) and multi-level (#) wildcards.
Time Since Last Select if you want to add a channel that shows the time since the last
Message message was received:
§ Enable: Create this channel. The sensor remains in the Up status even
if it received no messages during the last scan interval.
You can define a threshold notification trigger to receive notifications
if no data is received for a certain amount of time.
Last Message Handling Define what PRTG does with the last message received if there are no
new messages in the following scanning interval:
§ Dismiss (default): The sensor dismisses the last message received
after a new scan.
§ Retain: The sensor saves the last message received until a new
message is received.
Sensor Message Optionally enter the path to the value in the JSON data. The sensor
JSONPath shows the received value as the sensor message.
1349
Setting Description
The data must be in valid JSON format. For details about the format,
see Channel #x JSONPath below.
The sensor only shows the received value if the sensor is in the Up
status. If the sensor changes to the Down status, the sensor
message shows the error message instead.
Channel #x JSONPath Enter the path to the numeric value in the received JSON structure that
you want to monitor.
The data must be in valid JSON format, for example like this:
{
"Sensor1": {"Temp":25,"Unit":"°C"},
"Sensor2": {"Humidity":36,"Unit":"%"}
}
To query temperature, enter the following JSONPath:

$.Sensor1.Temp
To query humidity, enter the following JSONPath:

$.Sensor2.Humidity
Channel #x Value Type Select the value type that the channel displays:
§ Absolute (integer): Integer64 values with or without an operational sign,
such as 10 or 120 or -12 or 120.
§ Absolute (float): Double values, such as -5.80 or 8.23.
If you select Absolute (float), the sensor automatically shows all
decimal places of the received value in the channel. You can define
how many decimal places of the channel's data that you want to
display in graphs and tables in the channel settings.
§ Delta (counter): Counter values. The sensor calculates the difference
between the last and the current value. Enter an integer. The sensor
additionally divides the delta value by a time period to indicate a speed
value.
Absolute (integer) and Absolute (float) support the extraction of
numerical values from a received string. The sensor parses the
numerical value from the beginning of the string until it encounters the first
element that is not part of a numerical value, for example a letter. The
sensor ignores whitespace characters.
1350
Setting Description
If you select Disable (default), you can still see the channels, but
they do not receive data anymore.
Sensor Display
Sensor Display
Setting Description



other above.
procedure to do so.
1351
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
1352
More
KNOWLEDGE BASE

1353
7.8.99 Multi-Platform Probe Connection Health (Autonomous) Sensor
(BETA)
The Multi-Platform Probe Connection Health (Autonomous) sensor monitors the state of the connection
between the PRTG core and multi-platform probes.
This sensor is in beta status. The operating methods and the available settings are still subject to
change. Do not expect that all functions work properly, or that this sensor works as expected at
all.
Multi-Platform Probe Connection Health (Autonomous) Sensor
List 1357 .

§ Dutch: Multi-Platform Probe Verbinding Status (Autonoom)
§ French: État de la connexion de la sonde multi plate-forme (autonome)
§ German: Zustand der Verbindungen mit Multi-Plattform Probes (Autonom)
§ Japanese: ( )
§ Portuguese: Saúde da conexão da sonda multiplataforma (autônoma)
§ Russian: ( )
§ Spanish: Salud de conexión de sonda multiplataforma (autónomo)
Remarks
1354
Remark Description
Sensor creation § PRTG automatically creates this sensor on the PRTG core server when
you enable multi-platform probe connections under Setup | System
Administration | Core & Probes.
channels.
Knowledge Base § Knowledge Base: What is the multi-platform probe and how can I use
it?
you add the sensor:
§ multiplatformprobeconnectionhealthsensor
Sensor Display
Sensor Display
1355
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
1356
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
NATS Connection State The state of the connection to the NATS server
· Up: Connected, Disabled
· Down: Disconnected
· Unknown: Unknown
If this sensor remains in the Down or Unknown state, check your

configuration in Setup | System Administration | Core & Probes.
More
KNOWLEDGE BASE

1357
7.8.100 Multi-Platform Probe Health Sensor
The Multi-Platform Probe Health Sensor monitors the status of a multi-platform probe device.
Multi-Platform Probe Health Sensor
List 1361 .

§ Dutch: Multi-Platform Probe Status
§ French: État de la sonde multiplateforme
§ German: Zustand der Multi-Plattform Probe
§ Japanese:
§ Portuguese: Saúde da sonda multiplataforma
§ Russian:
§ Spanish: Salud de la sonda multiplataforma
Remarks
1358
Remark Description
Sensor creation § PRTG automatically creates this sensor. You cannot delete it. If you
manually create the sensor, you can delete it.
Windows § This sensor does not support Windows operating systems.
Probe device § You can create this sensor only on a probe device.
Scanning interval § The recommended scanning interval of this sensor is 1 minute.
Knowledge Base § Knowledge Base: What is the multi-platform probe and how can I use
it?
you add the sensor:
§ multiplatformprobehealthsensor
1359
Multi-Platform Probe Health Specific
Multi-Platform Probe Health Specific
Setting Description
Port Enter the port number (between 1 and 65535) that this sensor uses to
connect to the multi-platform probe. The default port is 23562.
Sensor Display
Sensor Display
Setting Description
Primary Channel Select a channel from the list to define it as the primary channel.
In the device tree, PRTG displays the last value of the primary
channel below the sensor's name. The available options depend on
what channels are available for this sensor.
You can set a different primary channel later by clicking
below a channel gauge on the sensor's Overview tab.

§ Show channels independently (default): Show a graph for each
channel.
§ Stack channels on top of each other: Stack channels on top of
each other to create a multi-channel graph. This generates a
graph that visualizes the different components of your total
traffic.
You cannot use this option in combination with manual
Vertical Axis Scaling (available in the channel settings).
Stack Unit This setting is only visible if you select Stack channels on top of
each other above.
1360
Setting Description
Select a unit from the list. PRTG stacks all channels with this unit
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.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Channel List
1361
Channel Description
CPU Load The CPU load (%) of the multi-platform probe. Extensive CPU load can
lead to false, incomplete, and incorrect monitoring results. This value
should usually stay below 50%.

Memory Usage The memory usage
Scans per Second The number of scans per second
Uptime The uptime
More
KNOWLEDGE BASE


1362
7.8.101 MySQL v2 Sensor
The MySQL v2 sensor monitors a database on a MySQL server and executes a query.
channels.
MySQL v2 Sensor
List 1373 .

§ Dutch: MySQL v2
§ French: MySQL v2
§ German: MySQL v2
§ Japanese: MySQL v2
§ Portuguese: MySQL v2
§ Russian: MySQL v2
§ Simplified Chinese: MySQL v2
§ Spanish: MySQL v2
Remarks
1363
Remark Description

computer?
does PRTG require?
MySQL server § This sensor supports MySQL server versions as of 5.7.

a guide?

probe device.
1364
you add the sensor:
§ sqlsensor
Database Specific
Database Specific
Setting Description
Database Enter the name of the MySQL database to which the sensor connects, for
example, MyDatabase. This is a logical entity on the database server
where database objects exist.
The database name of a MySQL server also reflects a physical directory
structure where your database objects are stored. Enter the appropriate
string, which is the same as you would supply when you invoke the
mysql.exe admin tool (with the command-line switch -p) or after you log in
with mysql.exe with the command use.
SSL Mode Select the MySQL Secure Sockets Layer (SSL) mode for the connection:
§ None: Do not use SSL.
§ Preferred (default): Use SSL if the server supports it.
1365
Setting Description
§ Required: Always use SSL and deny the connection if the server does
not support it. Do not perform a server certificate validation.
The SSL mode options that you can choose are the same as the values of
the MySQL sslmode parameter. PRTG sends it with the sensor requests.
For more information about the MySQL SSL modes, refer to the
MySQL documentation.
Data
Data
Setting Description
cluster nodes.
1366
Setting Description
into the query.
content:
edited).
1367
Setting Description


as the number 0.

Number.
Databases.
1368
Setting Description

data table.
1369
Setting Description
Channel #x Unit
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
Sensors.
1370
Setting Description

1371
Setting Description
point.

change.
master node.
1372
Sensor Display
Sensor Display
Setting Description
device tree, PRTG displays the last value of the primary channel below the
sensor's name. The available options depend on what channels are


other above.
procedure to do so.
Inherited Settings
Channel List
1373
Channel Description
SQL Variables

More
KNOWLEDGE BASE


1374

1375
7.8.102 NetApp Aggregate Sensor
IMPORTANT INFORMATION
This sensor supports NetApp cDOT as of version 8.3 or ONTAP from versions 9.0 to 9.12. If you use
ONTAP as of version 9.6, we recommend that you use the NetApp Aggregate v2 1383 sensor.
The NetApp Aggregate sensor monitors the status of a NetApp cDOT or ONTAP storage aggregate
accessing the application programming interface (API) via the Simple Object Access Protocol (SOAP).
NetApp Aggregate Sensor
List 1381 .

§ Dutch: NetApp Aggregate
§ French: NetApp agrégat de stockage
§ German: NetApp Aggregat
§ Japanese: NetApp
1376
§ Portuguese: Agregado NetApp
§ Russian: NetApp
§ Simplified Chinese: NetApp
§ Spanish: Agregado NetApp
Remarks
Remark Description
Enabled ONTAPI access § The ONTAPI user account that you use with this sensor requires
access to the DATA ONTAP API (ONTAPI) so that the sensor can
request data from it. The access is enabled by default.
§ If access is disabled, locally use the following command on the cluster
console to enable ONTAPI access for the user:
services web> modify -vserver clusterd -name ontapi -enabled
true
§ For this sensor, read-only user rights are sufficient for the ONTAPI user
account that you use to access ONTAPI. Modify or add this user with a
suitable role in the console under Cluster | ClusterX | Configuration |
Security | Users
does PRTG require?
NetApp versions § This sensor supports NetApp cDOT as of version 8.3 and NetApp
ONTAP as of version 9.0.
Credentials § You can define NetApp API credentials (User Name and Password) in
the credentials for Windows systems settings of the parent device. This
way, you do not need to individually enter credentials for each NetApp
sensor that you add to the same device.
channels.
1377
you add the sensor:
§ cdot
§ netapp
§ ontap
§ soap
NetApp Connection
NetApp Connection
Setting Description
NetApp Credentials Specify which credentials you want to use to connect to the NetApp API:
§ Use explicit credentials: Use individual NetApp API credentials.
1378
Setting Description
§ Use Windows credentials from parent device: Use the credentials (User
Name and Password) in the parent device settings in section
Credentials for Windows Systems.
Defining credentials in the parent device is useful if you add several
NetApp sensors to this device because you do not need to
individually enter credentials for each NetApp sensor.
User Name This setting is only visible if you select Use explicit credentials above.
Enter a user name for access to the NetApp API. Enter a string.
Read-only rights for this ONTAP user account are sufficient.
Password This setting is only visible if you select Use explicit credentials above.
Enter the password of the user for access to the NetApp API. Enter a
string.
Port Enter a port number on which you can access the NetApp API. Enter an
Connection Security Define if the connection to the NetApp API is Secure Sockets Layer
(SSL)/Transport Layer Security (TLS) secured:
§ HTTP: Use an unsecured HTTP connection.
§ HTTPS: Use a secure connection to the defined port to send the query.
NetApp Specific
NetApp Specific
Setting Description
Aggregates The identifier of the aggregate that this sensor monitors.
1379
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

1380
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Aggregate State The aggregate status

§ Up status: Online
§ Warning status: Restrict
§ Down status: Offline, Other Error
Blocks Read The number of blocks read
Blocks Written The number of blocks written
Bytes Free The free bytes in total
Bytes Free % The free bytes (%)
1381
Channel Description
Data Read The data read speed
Data Written The data write speed
Disks # The number of disks on the aggregate
Files The number of files on the aggregate
Latency The latency
User Reads The number of user reads
User Writes The number of user writes
More
KNOWLEDGE BASE


1382
7.8.103 NetApp Aggregate v2 Sensor
The NetApp Aggregate v2 sensor monitors the status of a NetApp storage aggregate via the
Representational State Transfer (REST) application programming interface (API) using ONTAP as of
version 9.6.
This sensor was converted to a new framework so that it will continue to function after the changes
of the ONTAP REST API.
NetApp Aggregate v2 Sensor
List 1387 .

§ Dutch: NetApp Aggregaat v2
§ French: NetApp agrégat de stockage v2
§ German: NetApp Aggregat v2
§ Japanese: NetApp v2
§ Portuguese: Agregado NetApp v2
§ Russian: NetApp v2
§ Simplified Chinese: NetApp v2
§ Spanish: Agregado NetApp v2
1383
Remarks
Remark Description
Credentials for NetApp § This sensor requires an ONTAP System Manager user account with
the role readonly and with access to the HTTP application with
Password authentication.
Permissions for the § This sensor requires permissions for the ONTAP REST API.
ONTAP REST API
§ This sensor requires the role readonly with the following permissions for
the ONTAP REST API:
Access level Read-Only:
ú /api
ú /api/security/audit/destinations
Access level Read/Write:

ú /api/security/authentication/password
Access level None:

ú /api/security
Credentials § This sensor requires credentials for NetApp.
Output § This sensor does not include system-owned root aggregates in the
output.
NetApp versions § This sensor supports ONTAP as of version 9.6. If you want to use
NetApp cDOT as of version 8.3 or ONTAP from version 9.0 to version
9.5, use the NetApp Aggregate 1376 sensor. 1483
channels.
1384
you add the sensor:
§ aggregate
§ netapp
§ ontap
§ rest
NetApp Specific
NetApp Specific
Setting Description
Aggregate Name The name of the aggregate that this sensor monitors.
Node Name The name of the node that contains the aggregate that this sensor
monitors.
1385
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
1386
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Disks The number of disks on the aggregate

Size Free The free size
Size Free % The free size (%)

1387
Channel Description
State The aggregate status
§ Up status: Online, Onlining
§ Warning status: Offline, Offlining, Relocating, Unmounted, Restricted,

Inconsistent
§ Unknown status: Channel Value Not Set, Unknown
More
KNOWLEDGE BASE

1388
7.8.104 NetApp I/O Sensor
ONTAP as of version 9.11, we recommend that you use the NetApp I/O v2 1397 sensor. 1383
The NetApp I/O sensor monitors input and output operations of a NetApp cDOT or ONTAP storage
system accessing the application programming interface (API) via the Simple Object Access Protocol
(SOAP).
NetApp I/O Sensor
List 1394 .
1389
§ Dutch: NetApp I/O
§ French: NetApp E/S
§ German: NetApp I/O
§ Japanese: NetApp I/O
§ Portuguese: NetApp E/S
§ Russian: NetApp
§ Simplified Chinese: NetApp I/O
§ Spanish: E/S de NetApp
Remarks
Remark Description
true
Security | Users
does PRTG require?
1390
Remark Description
you add the sensor:
§ cdot
§ netapp
§ ontap
§ soap
NetApp Connection
NetApp Connection
1391
Setting Description
string.
NetApp Specific
NetApp Specific
1392
Setting Description
System Nodes The ID of the system node that this sensor monitors.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description
1393
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
CIFS Ops The number of CIFS operations

1394
Channel Description
FCP Ops The number of FCP operations
FCP Read The FCP read speed
FCP Write The FCP write speed
HDD Read The HDD read speed
HDD Write The HDD write speed
HTTP Ops The number of HTTP operations
ISCSI Ops The number of iSCSI operations
ISCSI Partner Ops The number of iSCSI partner operations
ISCSI Partner Read The iSCSI partner read speed
ISCSI Partner Write The iSCSI partner write speed
ISCSI Read The iSCSI read speed
ISCSI Write The iSCSI write speed
Network Read The network read speed
Network Write The network write speed
NFS Ops The number of NFS operations
SSD Read The SSD read speed
SSD Write The SSD write speed
Tape Read The tape read speed
1395
Channel Description
Tape Write The tape write speed
More
KNOWLEDGE BASE


1396
7.8.105 NetApp I/O v2 Sensor
The NetApp I/O v2 sensor monitors input and output operations of a NetApp storage system via the
version 9.11.
NetApp I/O v2 Sensor
List 1401 .

§ Dutch: NetApp I/O v2
§ French: NetApp E/S v2
§ German: NetApp I/O v2
1397
§ Japanese: NetApp I/O v2
§ Portuguese: E/S NetApp v2
§ Simplified Chinese: NetApp / v2
§ Spanish: E/S NetApp v2
Remarks
Remark Description
ONTAP REST API
the ONTAP REST API:
ú /api

Access level None:
ú /api/security
NetApp versions § This sensor requires ONTAP as of version 9.11. If you want to use
9.10, use the NetApp I/O 1389 sensor.
1398
you add the sensor:
§ netapp
§ ontap
§ rest
NetApp Specific
NetApp Specific
Setting Description
Node Name The name of the node that this sensor monitors.
Sensor Display
Sensor Display
1399
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
1400
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Bytes Read The number of bytes read
Bytes Written The number of bytes written
CIFS Read The CIFS read speed
CIFS Total Ops The number of CIFS operations

CIFS Write The CIFS write speed
FCP Total Ops The number of FCP operations
1401
Channel Description
iSCSI Read The iSCSI read speed
iSCSI Total Ops The number of iSCSI operations
iSCSI Write The iSCSI read speed
NFS Read The NFS read speed
NFS Total Ops The number of NFS operations
NFS Write The NFS write speed
Total Ops The number of operations
More
KNOWLEDGE BASE

1402
7.8.106 NetApp LIF Sensor
ONTAP as of version 9.10, we recommend that you use the NetApp LIF v2 1383 sensor.
The NetApp LIF sensor monitors logical interfaces of a NetApp cDOT or ONTAP cluster accessing the
application programming interface (API) via the Simple Object Access Protocol (SOAP).
NetApp LIF Sensor
List 1408 .

§ Dutch: NetApp LIF
§ French: NetApp LIF
§ German: NetApp LIF
§ Japanese: NetApp LIF
§ Portuguese: LIF NetApp
1403
§ Russian: LIF NetApp
§ Simplified Chinese: NetApp LIF
§ Spanish: LIF NetApp
Remarks
Remark Description
true
Security | Users
does PRTG require?
channels.
1404
you add the sensor:
§ cdot
§ netapp
§ ontap
§ soap
NetApp Connection
NetApp Connection
Setting Description
1405
Setting Description
string.
NetApp Specific
NetApp Specific
Setting Description
LIFs The ID of the LIF that this sensor monitors.
1406
Debug Options
Debug Options
Setting Description
Result of Sensor [ID].Data.txt and Result of Sensor [ID].log. This
setting is for debugging purposes. PRTG overwrites these files with
each scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

1407
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Data Received The data received

Data Sent The data sent
Errors Received The number of errors received
Errors Sent The number of errors sent
1408
Channel Description
Is Home If the LIF is on the home port

§ Up status: Yes
§ Down status: No
More
KNOWLEDGE BASE


1409
7.8.107 NetApp LIF v2 Sensor
The NetApp LIF v2 sensor monitors a logical interface (LIF) of a NetApp storage system via the
version 9.10.
NetApp LIF v2 Sensor
List 1414 .

§ Dutch: NetApp LIF v2
§ French: NetApp LIF v2
§ German: NetApp LIF v2
§ Japanese: NetApp LIF v2
§ Portuguese: LIF NetApp v2
§ Russian: LIF NetApp v2
§ Simplified Chinese: NetApp LIF v2
§ Spanish: LIF NetApp v2
1410
Remarks
Remark Description
ONTAP REST API
the ONTAP REST API:
ú /api

Access level None:

ú /api/security
9.9, use the NetApp LIF 1403 sensor.
channels.
1411
you add the sensor:
§ lif
§ netapp
§ ontap
§ rest
NetApp Specific
NetApp Specific
Setting Description
Name The name of the LIF that this sensor monitors.
1412
Setting Description
Home Node Name The home node name of the LIF that this sensor monitors.
Scope The scope of the LIF that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1413
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Is Home If the LIF is on the home port
1414
Channel Description
§ Up status: At Home
§ Down status: Not At Home
§ Unknown status: Channel Value Not Set
State The LIF status

§ Up status: Up
Throughput Read The number of bytes read
Throughput Total The total number of bytes read and written
Throughput Write The number of bytes written
More
KNOWLEDGE BASE

1415
7.8.108 NetApp LUN Sensor
ONTAP as of version 9.6, we recommend that you use the NetApp LUN v2 1423 sensor. 1383
The NetApp LUN sensor monitors the logical unit number (LUN) of a NetApp cDOT or ONTAP storage
(SOAP).
NetApp LUN Sensor
List 1421 .

§ Dutch: NetApp LUN
§ French: NetApp LUN
1416
§ German: NetApp LUN
§ Japanese: NetApp LUN
§ Portuguese: LUN NetApp
§ Russian: LUN NetApp
§ Simplified Chinese: NetApp LUN
§ Spanish: LUN NetApp
Remarks
Remark Description
true
Security | Users

does PRTG require?
1417
Remark Description
channels.
you add the sensor:
§ cdot
§ netapp
§ ontap
§ soap
NetApp Connection
NetApp Connection
1418
Setting Description
string.
NetApp Specific
NetApp Specific
1419
Setting Description
LUNs The ID of the LUN that this sensor monitors.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description
1420
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Bytes Free The free space
Bytes Free % The free bytes (%)
1421
Channel Description
LUN State The LUN status
§ Down status: LUN has been automatically taken offline due to a media
error on the associated foreign LUN, LUN has been automatically taken
offline due to an NVRAM failure, LUN has been automatically taken
offline due to insufficient space
§ Unknown status: LUN is administratively offline or a more detailed
offline reason is not available
Mapped If the LUN is mapped

§ Up status: Yes
§ Down status: No
Other Ops The other operations
Read Blocks The number of read blocks
Read Ops The number of disk read operations
SCSI Errors The number of SCSI errors
Write Blocks The number of write blocks
Write Ops The number of disk write operations
More
KNOWLEDGE BASE


1422
7.8.109 NetApp LUN v2 Sensor
The NetApp LUN v2 sensor monitors the logical unit number (LUN) of a NetApp storage system via the
version 9.6.
NetApp LUN v2 Sensor
List 1427 .

§ Dutch: NetApp LUN v2
§ French: NetApp LUN v2
§ German: NetApp LUN v2
§ Japanese: NetApp LUN v2
§ Portuguese: LUN NetApp v2
§ Russian: LUN NetApp v2
§ Simplified Chinese: NetApp LUN v2
1423
§ Spanish: LUN NetApp v2
Remarks
Remark Description
ONTAP REST API
the ONTAP REST API:
ú /api

Access level None:

ú /api/security
9.5, use the NetApp LUN 1416 sensor.
channels.
1424
you add the sensor:
§ lun
§ netapp
§ ontap
§ rest
NetApp Specific
NetApp Specific
Setting Description
LUN Path Name The path name of the LUN that this sensor monitors.
Operating System Type The operating system type of the LUN that this sensor monitors.
Description The description of the LUN that this sensor monitors.
1425
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
1426
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Bytes Free The free space

Bytes Free % The free space (%)
Container State The container status

§ Down status: Aggregate Offline, Volume Offline, Error
1427
Channel Description
IOPS Read The number of IOPS read
IOPS Total The total number of IOPS
IOPS Write The number of IOPS written
Latency Read The read latency
Latency Total The total latency
Latency Write The write latency
State The LUN status

§ Down status: Offline, NVRAM Failure, Space Error, Foreign LUN Error
More
KNOWLEDGE BASE

1428
7.8.110 NetApp NIC Sensor
ONTAP as of version 9.10, we recommend that you use the NetApp NIC v2 1436 sensor.
The NetApp NIC sensor monitors the network interface card (NIC) of a NetApp cDOT or ONTAP cluster
NetApp NIC Sensor
List 1434 .

§ Dutch: NetApp NIC
§ French: NetApp NIC
§ German: NetApp NIC
§ Japanese: NetApp NIC
§ Portuguese: NIC NetApp
§ Russian: NIC NetApp
1429
§ Simplified Chinese: NetApp NIC
§ Spanish: NIC NetApp
Remarks
Remark Description
true
Security | Users
does PRTG require?
1430
you add the sensor:
§ cdot
§ netapp
§ ontap
§ soap
NetApp Connection
NetApp Connection
Setting Description
1431
Setting Description
string.
NetApp Specific
NetApp Specific
Setting Description
NICs The ID of the NIC that this sensor monitors.
1432
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

1433
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description

Bytes Sent The number of bytes sent
Errors Received The number of errors received
Errors Sent The number of errors sent
1434
Channel Description
Healthy If the system is healthy

§ Up status: Healthy
§ Down status: Unhealthy
§ Unknown status: Not Available
Link Up to Down The number of up to down links
More
KNOWLEDGE BASE
What are beta sensors and how can I use them?



1435
7.8.111 NetApp NIC v2 Sensor
The NetApp NIC v2 sensor monitors a network interface card (NIC) of a NetApp storage system via the
version 9.10.
NetApp NIC v2 Sensor
List 1440 .

§ Dutch: NetApp NIC v2
§ French: NetApp NIC v2
§ German: NetApp NIC v2
§ Japanese: NetApp NIC v2
§ Portuguese: NIC NetApp v2
§ Russian: NIC NetApp v2
§ Simplified Chinese: NetApp NIC v2
§ Spanish: NIC NetApp v2
1436
Remarks
Remark Description
ONTAP REST API
the ONTAP REST API:
ú /api

Access level None:

ú /api/security
9.9, use the NetApp NIC 1429 sensor.
channels.
1437
you add the sensor:
§ netapp
§ nic
§ ontap
§ rest
NetApp Specific
NetApp Specific
Setting Description
Name The name of the NIC that this sensor monitors.
Home Node Name The home node name of the NIC that this sensor monitors.
1438
Setting Description
Type The type of the NIC that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1439
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Link Down Count The number of link status changes from up to down
1440
Channel Description

Receive Errors The number of errors received

State The NIC status

§ Up status: Up
§ Unknown status: Channel Value not Set
Transmit Errors The number of errors sent

More
KNOWLEDGE BASE

1441
7.8.112 NetApp Physical Disk Sensor
ONTAP as of version 9.9, we recommend that you use the NetApp Physical Disk v2 1449 sensor.
The NetApp Physical Disk sensor monitors disks of a NetApp cDOT or ONTAP storage system
NetApp Physical Disk Sensor
List 1447 .

§ Dutch: NetApp Fysieke Schijf
§ French: NetApp disque physique
§ German: NetApp Physikal. Laufwerk
§ Japanese: NetApp
§ Portuguese: Disco físico NetApp
1442
§ Russian: NetApp
§ Spanish: Disco físico NetApp
Remarks
Remark Description
true
Security | Users
does PRTG require?
1443
you add the sensor:
§ cdot
§ netapp
§ ontap
§ soap
NetApp Connection
NetApp Connection
Setting Description
1444
Setting Description
string.
NetApp Specific
NetApp Specific
Setting Description
Disk The physical disk that this sensor monitors.
1445
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

1446
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description

Data Write The data write speed
Ops Latency The latency of operations
1447
Channel Description
More
KNOWLEDGE BASE


1448
7.8.113 NetApp Physical Disk v2 Sensor
The NetApp Physical Disk v2 sensor monitors physical disks of a NetApp storage system via the
version 9.9.
NetApp Physical Disk v2 Sensor
List 1453 .

§ Dutch: NetApp Fysieke Schijf v2
§ French: NetApp disque physique v2
§ German: NetApp Physikalischer Datenträger v2
§ Portuguese: Disco físico NetApp v2
§ Spanish: Disco físico NetApp v2
1449
Remarks
Remark Description
ONTAP REST API
the ONTAP REST API:
ú /api

Access level None:

ú /api/security
Channels § This sensor requires ONTAP 9.10 for some channels.
9.8, use the NetApp Physical Disk 1442 sensor.
channels.
1450
you add the sensor:
§ netapp
§ ontap
§ physicaldisk
§ rest
NetApp Specific
NetApp Specific
Setting Description
Disk Name The name of the physical disk that this sensor monitors.
Home Node Name The home node name of the physical disk that this sensor monitors.
1451
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
1452
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Container Type The container type

§ Up status: Aggregate, Foreign, Labelmaint, Maintenance, Shared,
Spare, Unsupported, Remote, Mediator
§ Warning status: Unassigned, Unknown
§ Down status: Broken
IOPS Total The number of IOPS
1453
Channel Description
Latency The latency
Path Error Count The number of path errors

Power On Hours The total time that the disk has been spinning
Throughput The throughput

More
KNOWLEDGE BASE

1454
7.8.114 NetApp SnapMirror Sensor
ONTAP as of version 9.6, we recommend that you use the NetApp SnapMirror v2 1462 sensor.
The NetApp SnapMirror sensor monitors SnapMirror relationships of a NetApp cDOT or ONTAP storage
(SOAP).
NetApp SnapMirror Sensor
List 1460 .

§ Dutch: NetApp SnapMirror
1455
§ French: NetApp SnapMirror
§ German: NetApp SnapMirror
§ Japanese: NetApp SnapMirror
§ Portuguese: NetApp SnapMirror
§ Russian: NetApp SnapMirror
§ Simplified Chinese: NetApp SnapMirror
§ Spanish: NetApp SnapMirror
Remarks
Remark Description
true
Security | Users
does PRTG require?
1456
Remark Description
channels.
you add the sensor:
§ cdot
§ netapp
§ ontap
§ soap
NetApp Connection
NetApp Connection
1457
Setting Description
string.
NetApp Specific
NetApp Specific
1458
Setting Description
SnapMirrors The SnapMirror that this sensor monitors.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description
1459
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Healthy If the system is healthy

§ Up status: Yes
1460
Channel Description
§ Down status: No
Lag The lag transfer duration
Last Transfer Duration The last transfer duration
Last Transfer Size The last transfer size
Last Transfer Timestamp The time stamp of the last transfer
Mirror State The mirror status

§ Up status: Snapmirrored
§ Warning status: Uninitialized
§ Down status: Broken-Off, Unknown
Relationship Type The relationship type

§ Up status: Mirror, Mirror and Vault, Vault
§ Down status: Unknown
Resync Fails The number of resynchronization fails
Transfer Status The transfer status (relationship status returned from the API)
§ Up status: Aborting, Checking, Finalizing, Idle, Preparing, Queued,
Quiesced, Quiescing, Transferring
§ Warning status: Breaking, Unknown
Update Fails The number of update fails
More
KNOWLEDGE BASE


1461
7.8.115 NetApp SnapMirror v2 Sensor
The NetApp SnapMirror v2 sensor monitors SnapMirror relationships of an ONTAP storage system the
version 9.6.
NetApp SnapMirror v2 Sensor
List 1466 .

§ Dutch: NetApp SnapMirror v2
§ French: NetApp SnapMirror v2
§ German: NetApp SnapMirror v2
§ Japanese: NetApp SnapMirror v2
§ Portuguese: NetApp SnapMirror v2
§ Russian: NetApp SnapMirror v2
§ Simplified Chinese: NetApp SnapMirror v2
1462
§ Spanish: NetApp SnapMirror v2
Remarks
Remark Description
ONTAP REST API
the ONTAP REST API:
ú /api

Access level None:

ú /api/security
NetApp cDOT as of version 8.3 or ONTAP from version 9.0 to 9.5, use
the NetApp SnapMirror 1455 sensor.
channels.
1463
you add the sensor:
§ netapp
§ ontap
§ rest
§ snapmirror
NetApp Specific
NetApp Specific
Setting Description
Source Path The source path of the SnapMirror relationship that this sensor monitors.
Sensor Display
Sensor Display
1464
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
1465
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
State The system status
Lag The lag transfer duration
Last Transfer Duration The last transfer duration
Last Transfer Size The last transfer size
Last Transfer Age The age of the last transfer
Mirror State The mirror status
1466
Channel Description
§ Up status: Aborting, Checking, In Sync, Quiesced, Quiescing,

Snapmirrored
§ Warning status: Paused, Synchronizing, Uninitialized
§ Down status: Broken Off, Out of Sync
Policy Type The policy type of the relationship

§ Up status: Async, Async Mirror, Automated Failover, Mirror and Vault,
Strict Sync Mirror, Sync Mirror, Vault
Resync Fails The number of resynchronization fails

Transfer Status The transfer status (relationship status returned from the API)
§ Up status: Finalizing, Idle, In Sync, Preparing, Queued, Success,
Transferring
§ Warning status: Aborted, Hard Aborted
Update Fails The number of update fails

More
KNOWLEDGE BASE

1467
7.8.116 NetApp System Health Sensor
ONTAP as of version 9.6, we recommend that you use the NetApp System Health v2 1476 sensor.
The NetApp System Health sensor monitors the health of a NetApp cDOT or ONTAP storage system
NetApp System Health Sensor
List 1473 .

§ Dutch: NetApp Systeem Gesteldheid
§ French: NetApp état du système
§ German: NetApp Systemzustand
§ Japanese: NetApp
1468
§ Portuguese: NetApp Funcionamento do sistema
§ Russian: NetApp
§ Spanish: Estado del sistema de NetApp
Remarks
Remark Description
true
§ This sensor requires administrator rights for the ONTAPI user account
that you use to access ONTAPI. Modify or add this user with a suitable
role in the console under Cluster | ClusterX | Configuration | Security |
Users
does PRTG require?
Read-only § As an alternative to administrator rights 1473 , you can add a specific

Role Attribute and use read-only rights.
1469
Remark Description
channels.
you add the sensor:
§ cdot
§ netapp
§ ontap
§ soap
NetApp Connection
NetApp Connection
1470
Setting Description
string.
NetApp Specific
NetApp Specific
1471
Setting Description
System Nodes The ID of the system node that this sensor monitors.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description
1472
Setting Description


other above.
procedure to do so.
Inherited Settings
Permissions: Alternative to Administrator Rights

If you do not want to provide administrator rights for the ONTAPI user account that you use with the
NetApp System Health sensor, you can add a new command to the selected role of the user that makes
read-only rights sufficient.
§ Edit the Role of this user in the console under Cluster | ClusterX | Configuration | Security | Users.
§ Add the command storage aggregate check_spare_low with access control list (ACL) all to the Role
Attributes.
With this role attribute, read-only rights are sufficient for the NetApp System Health sensor.
Channel List
1473
Channel Description
CPU The CPU load (%)

Failed Fans The number of failed fans

Failed PSU The number of failed power supplies

Memory The memory usage
Node Health The node health

§ Up status: OK
NVRAM Battery The NVRAM battery status

§ Up status: OK
Spare Disks # The number of spare disks
Spare Disks Low If spare disks are low as reported by the NetApp
§ Up status: No
§ Down status: Yes
1474
Channel Description
Spare Size Usable The usable spare size
Storage Configuration The storage configuration path that describes the connection of a node
Path
§ Up status: multi_path, multi_path_ha, quad_path, quad_path_ha, N/A
§ Warning status: single_path, single_path_ha, mixed_path,

mixed_path_ha
§ Down status: unknown
If no storage configuration path is returned, the sensor shows the Up

status (N/A) because the availability of the configuration path
depends on the NetApp version.
Temperature The temperature status

§ Up status: OK
Uptime The uptime
More
KNOWLEDGE BASE


1475
7.8.117 NetApp System Health v2 Sensor
The NetApp System Health v2 sensor monitors the health of a node of a NetApp storage cluster via the
version 9.6.
NetApp System Health v2 Sensor
List 1480 .

§ Dutch: NetApp Systeemstatus v2
§ French: NetApp état du système v2
§ German: NetApp Systemzustand v2
§ Portuguese: Saúde do sistema NetApp v2
1476
§ Spanish: Salud del sistema NetApp v2
Remarks
Remark Description
ONTAP REST API
the ONTAP REST API:
ú /api

Access level None:

ú /api/security
Channels § This sensor requires ONTAP 9.11 for some channels 1480 .
9.5, use the NetApp System Health 1468 sensor.
channels.
1477
Remark Description
you add the sensor:
§ netapp
§ ontap
§ rest
NetApp Specific
NetApp Specific
Setting Description
Node Name The name of the node that this sensor monitors.
1478
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
1479
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Failed PSUs The number of failed power supplies

Node Health The node health

§ Up status: Up
§ Warning status: Booting, Taken Over, Waiting for Giveback
§ Down status: Down, Degraded, Unknown
1480
Channel Description
NVRAM Battery The NVRAM battery status
§ Up status: OK, Fully Charged
§ Warning status: Near End-of-life, Over-charged, Partially Discharged
§ Down status: Fully Discharged, Not Present, At End-of-life
§ Unknown status: Channel Value Not Set, Unknown
This channel requires ONTAP 9.11.
Storage Configuration The storage configuration path that describes the connection of a node
Path
§ Up status: Multi Path, Multi Path HA, Mixed Path, Single Path HA,
Mixed Path HA, Quad Path, Quad Path HA
§ Warning status: Unknown, Single Path
This channel requires ONTAP 9.11.
Spare Disks Available The number of spare disks

Spare Size Usable The usable spare size
Temperature State The temperature status

§ Down status: Over
Uptime The uptime
More
KNOWLEDGE BASE
1481
1482
7.8.118 NetApp Volume Sensor
ONTAP as of version 9.6, we recommend that you use the NetApp Volume v2 1490 sensor.
The NetApp Volume sensor monitors volumes on a NetApp cDOT or ONTAP storage system accessing
the application programming interface (API) via the Simple Object Access Protocol (SOAP).
NetApp Volume Sensor
List 1488 .

§ Dutch: NetApp Volume
§ French: NetApp volume de stockage
1483
§ German: NetApp Volume
§ Japanese: NetApp
§ Portuguese: NetApp Volume
§ Russian: NetApp
§ Spanish: Volumen de NetApp
Remarks
Remark Description
true
Security | Users

does PRTG require?
Add Sensor dialog § Volumes that are offline do not appear in the Add Sensor dialog.
1484
you add the sensor:
§ cdot
§ netapp
§ ontap
§ soap
NetApp Connection
NetApp Connection
Setting Description
1485
Setting Description
string.
NetApp Specific
NetApp Specific
Setting Description
Volumes The volume that this sensor monitors.
1486
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

1487
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Busy Snapshots % The number of busy snapshots (%)
Compression Savings % The compression savings (%)
Compression Savings The compression savings

Bytes
Deduplication Savings % The deduplication savings (%)
Deduplication Savings The deduplication savings

Bytes
1488
Channel Description
Files Free The free files in total
Files Free % The free files (%)
Latest Snapshot The age of the last snapshot
Oldest Snapshot The oldest snapshot age
Physical Bytes Free The free physical bytes in total
Physical Bytes Free % The free physical bytes (%)
Size Free The free size in total

Size Free For Snapshots The free size for snapshots
Snapshot Reserve Free The free snapshot reserve (%)

%
Snapshots # The number of snapshots
Total Savings % The total savings (%)
Total Savings Bytes The total savings
More
KNOWLEDGE BASE


1489
7.8.119 NetApp Volume v2 Sensor
The NetApp Volume v2 sensor monitors a volume of a NetApp storage system via the Representational
State Transfer (REST) application programming interface (API) using ONTAP as of version 9.6.
NetApp Volume Sensor
List 1494 .

§ Dutch: NetApp Volume v2
§ French: NetApp volume de stockage v2
§ German: NetApp Volume v2
§ Portuguese: Volume NetApp v2
1490
§ Spanish: Volumen NetApp v2
Remarks
Remark Description
ONTAP REST API
the ONTAP REST API:
ú /api

Access level None:

ú /api/security
9.5, use the NetApp Volume 1483 sensor.
channels.
1491
Remark Description
you add the sensor:
§ netapp
§ ontap
§ rest
NetApp Specific
NetApp Specific
Setting Description
Volume Name The name of the volume that this sensor monitors.
Aggregate Names The names of the aggregates that contain the volume that this sensor
monitors.
1492
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
1493
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Autogrow The autogrow status

§ Up status: Off, Can Grow
§ Warning status: Grow Limit Reached
Files Free The number of files that can be created on the volume
Files Free % The number of files that can be created on the volume
1494
Channel Description

Latest Snapshot The time since the latest snapshot
Oldest Snapshot The oldest snapshot age
Physical Bytes Free % The free physical bytes

Size Free The free size

This channel also takes the snapshot reserve space (if set in the
ONTAP System Manager) on the volume into account.

This channel also takes the snapshot reserve space (if set in the
ONTAP System Manager) on the volume into account.
Snapshot The number of snapshots

Volumes can contain up to 1023 snapshot copies. The limit of this

channel is set to define a fixed size of the gauge that reflects the
maximum number of snapshot copies that the volume can contain.
More
KNOWLEDGE BASE
1495
1496
7.8.120 NetFlow v5 Sensor
The NetFlow v5 sensor receives traffic data from a NetFlow v5-compatible device and shows the traffic by
type. This sensor has several filter options to divide traffic into different channels.
Make sure that the sensor matches the NetFlow version that your device exports.
NetFlow v5 Sensor
List 1505 .

§ Dutch: NetFlow v5
§ French: NetFlow v5
1497
§ German: NetFlow v5
§ Japanese: NetFlow v5
§ Portuguese: NetFlow v5
§ Russian: NetFlow v5
§ Simplified Chinese: NetFlow v5
§ Spanish: NetFlow v5
Remarks
Remark Description
NetFlow § This sensor requires that the NetFlow export of the respective version is
probe device.
1498
you add the sensor:
§ bandwidthsensor
§ netflowsensor
NetFlow v5 Specific Settings
1499
Setting Description
Receive Packets on UDP Enter the User Datagram Protocol (UDP) port number on which PRTG
Port receives the flow packets. It must match the UDP port number in the
NetFlow export options of the hardware router device. Enter an integer.
appropriate NetFlow version for this sensor.
NetFlow from. Enter an IP address to only receive data from a specific
specified port.
Receive Packets on IP Select the IP addresses on which PRTG listens to NetFlow packets. The
Address list of IP addresses is specific to your setup. To select an IP address,
enable a check box in front of the respective line. The IP address that you
select must match the IP address in the NetFlow export options of the
hardware router device.
You can also select all items or cancel the selection by using the
check box in the table header.
If the target device sends incorrect time information that results in
wrong monitoring data, try to use 0 as the active flow timeout. This
ignores the start and stop information of a flow as provided by the device
and accounts all data to the current point in time. It might result in spikes
but the sensor captures all data.

1500
Setting Description
integer.
packet data.
interval.
Setting Description
1501
Setting Description

ICMP, and SNMP.
Other.
channel.
Filtering
1502
Filtering
Setting Description
Sensor Display
Sensor Display
Setting Description
1503
Setting Description

other above.
procedure to do so.
Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
Inherited Settings
1504
Toplists
Filter Rules
Channel List
Channel Description

1505
Channel Description
More
KNOWLEDGE BASE



PAESSLER TOOLS
NetFlow Tester
1506
7.8.121 NetFlow v5 (Custom) Sensor
The NetFlow v5 (Custom) sensor receives traffic data from a NetFlow v5-compatible device and shows the
channels.
NetFlow v5 (Custom) Sensor
List 1514 .

§ Dutch: NetFlow v5 (aangepast)
1507
§ French: NetFlow v5 personnalisé
§ German: NetFlow v5 (Benutzerdefiniert)
§ Japanese: NetFlow v5( )

§ Portuguese: NetFlow v5 (customizado)
§ Russian: NetFlow v5 ( )
§ Simplified Chinese: NetFlow v5 ( )
§ Spanish: NetFlow v5 (personalizado)
Remarks
Remark Description
probe device.
1508
you add the sensor:
§ bandwidthsensor
§ netflowsensor
1509
Setting Description
specified port.

1510
Setting Description
packet data.
interval.
Filtering
1511
Filtering
Setting Description
Sensor Display
Sensor Display
Setting Description
1512
Setting Description

other above.
procedure to do so.
Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
Inherited Settings
1513
Toplists
Filter Rules
Channel List
Channel Description

More
KNOWLEDGE BASE



PAESSLER TOOLS
NetFlow Tester
1514
1515
7.8.122 NetFlow v9 Sensor
The NetFlow v9 sensor receives traffic data from a NetFlow v9-compatible device and shows the traffic by
type. This sensor has several filter options to divide traffic into different channels.
NetFlow v9 Sensor
List 1524 .

§ Dutch: NetFlow v9
§ French: NetFlow v9
1516
§ German: NetFlow v9
§ Japanese: NetFlow v9
§ Portuguese: NetFlow v9
§ Russian: NetFlow v9
§ Simplified Chinese: NetFlow v9
§ Spanish: NetFlow v9
Remarks
Remark Description
probe device.
1517
you add the sensor:
§ bandwidthsensor
§ netflowsensor
1518
Setting Description
specified port.

1519
Setting Description
integer.
packet data.
interval.
Setting Description
1520
Setting Description

ICMP, and SNMP.
Other.
channel.
Filtering
1521
Filtering
Setting Description
Sensor Display
Sensor Display
Setting Description
1522
Setting Description

other above.
procedure to do so.
Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
Inherited Settings
1523
Toplists
Filter Rules
Channel List
Channel Description

1524
Channel Description
More
KNOWLEDGE BASE



PAESSLER TOOLS
NetFlow Tester
1525
7.8.123 NetFlow v9 (Custom) Sensor
The NetFlow v9 (Custom) sensor receives traffic data from a NetFlow v9-compatible device and shows the
channels.
NetFlow v9 (Custom) Sensor
List 1533 .

§ Dutch: NetFlow v9 (aangepast)
1526
§ French: NetFlow v9 personnalisé
§ German: NetFlow v9 (Benutzerdefiniert)
§ Japanese: NetFlow v9( )

§ Portuguese: NetFlow v9 (customizado)
§ Russian: NetFlow v9 ( )
§ Simplified Chinese: NetFlow v9 ( )
§ Spanish: NetFlow v9 (personalizado)
Remarks
Remark Description
probe device.
1527
you add the sensor:
§ bandwidthsensor
§ netflowsensor
1528
Setting Description
specified port.

1529
Setting Description
packet data.
interval.
Filtering
1530
Filtering
Setting Description
Sensor Display
Sensor Display
Setting Description
1531
Setting Description

other above.
procedure to do so.
Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
Inherited Settings
1532
Toplists
Filter Rules
Channel List
Channel Description

More
KNOWLEDGE BASE



PAESSLER TOOLS
NetFlow Tester
1533
1534
7.8.124 Network Share Sensor
The Network Share sensor monitors a Server Message Block (SMB) or Common Internet File System
(CIFS) network share.
Netw ork Share Sensor
List 1540 .

§ Dutch: Netwerkshare
§ French: Partage réseau
§ German: Netzwerkfreigabe
§ Japanese:
§ Portuguese: Compartilhamento de rede
§ Russian:
§ Spanish: Recurso compartido de red
1535
Remarks
Remark Description
you add the sensor:
§ cifs
§ folder
§ networkshare
§ smb
1536
Network Share Specific
Netw ork Share Specific
Setting Setting
Path Enter the path of the network share that you want to monitor. For
example, folder\subfolder.
Timeout (Sec.) Enter a timeout in seconds. If the scan of the folder takes longer, the
sensor cancels the request and shows an error message. If two
consecutive scans fail, the sensor shows the Down status. The default
value is 300 seconds (5 minutes).

performance issues.
Filter by File Name Select if you want to filter by file name:

§ Disable (default): Do not filter by file name.
§ Include filter: The sensor counts files that match the File Filter.
§ Exclude filter: The sensor counts files that do not match the File Filter.
File Filter This setting is only visible if you select Include filter or Exclude filter
above.
1537
Setting Setting
Enter a comma-separated list of file names, file formats, or patterns you

want to filter for. For example, '*.pdf, *.docx' includes or excludes files
with the file formats .pdf or .docx.
The file filter is not case-sensitive and supports wildcards (*).
Filter by File Age Select if you want to filter by file age:

§ Disable (default): Do not filter by file age.
§ Enable: Filter by file age.
Newer Than This setting is only visible if you select Enable above.
Enter a file age. The sensor only counts files that are younger than this
age.
Leave this field empty if you only want to filter for files with the Older
Than setting.
Older Than This setting is only visible if you select Enable above.
Enter a file age. The sensor only counts files that are older than this age.
Leave this field empty if you only want to filter for files with the Newer
Than setting.
File Age Filter Unit This setting is only visible if you select Enable above.
Select the time unit that you want to use for Filter by File Age:
§ Days (default)
§ Hours
§ Minutes
Sensor Display
Sensor Display
1538
Setting Setting


other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
1539
Setting Description
master node.
Inherited Settings
Channel List
Channel Description

Folder Count The number of folders
the future.
More
KNOWLEDGE BASE
1540
1541
7.8.125 OPC UA Certificate Sensor
The OPC UA Certificate sensor monitors the certificate of an OPC Unified Architecture (OPC UA) server.
OPC UA Certificate Sensor
List 1545 .

§ Dutch: OPC UA Certificaat
§ French: Certificat OPC UA
§ German: OPC UA Zertifikat
§ Japanese: OPC UA
§ Portuguese: Certificado OPC UA
§ Russian: OPC UA
§ Simplified Chinese: OPC UA
§ Spanish: Certificado OPC UA
Remarks
1542
Remark Description
§ Enter a valid port for the connection to the OPC UA server.
parent device.
channels.
you add the sensor:
§ certificate
§ opcua
§ opcuacertificate
1543
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
1544
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Days to Expiration The number of days to expiration

§ Lower error limit: 7 days
§ Lower warning limit: 28 days
Public Key Length The public key length
1545
Channel Description

§ Lower error limit: 1024 bits
§ Lower warning limit: 1025 bits
Self Signed If a self-signed certificate is used
More
KNOWLEDGE BASE

1546
7.8.126 OPC UA Custom Sensor
The OPC UA Custom sensor monitors up to ten numeric values returned by specific OPC Unified
Architecture (OPC UA) NodeIDs.
OPC UA Custom Sensor
List 1552 .

§ Dutch: OPC UA Aangepast
§ French: OPC UA personnalisé
§ German: OPC UA (Benutzerdefiniert)
§ Japanese: OPC UA
§ Portuguese: OPC UA customizado
§ Russian: OPC UA
§ Spanish: OPC UA (personalizado)
1547
Remarks
Remark Description
parent device.
channels.
Knowledge Base § Knowledge Base: Which OPC UA data types does the OPC UA
Custom sensor support?
Add Sensor
Setting Description
Channel #1 – #10 Select the naming method for the channels of the sensor:
Naming Method
§ Use automatic naming (default): The sensor uses the name provided by
the OPC UA node.
You cannot use automatic naming after sensor creation.
§ Enter custom name: Enter a custom name in field Channel #1 - #10
Name.
sensor.
Channel #1 - #10 Unit Enter the unit for the numeric value that this sensor monitors.
sensor.
1548
Setting Description
Channel #1 – #10 NodeID Enter the NodeID from which you want to receive numeric data.
A NodeID looks like this, for example: ns=1;i=1234,
ns=2;s=test_one, or 'ns=1;s=test_one'[4]. The sensor supports string
identifiers, numeric identifiers, and array syntaxes.
you add the sensor:
§ opcua
§ opcuacustom
OPC UA Specific
OPC UA Specific
1549
Setting Description
Sensor Message NodeID Optionally enter the NodeID from which you want to receive a string that
the sensor shows as sensor message.
The sensor only shows the received string if the sensor is in the Up
status. If the sensor enters the Down status, the sensor message
shows the error message instead.
Channel #x NodeID The NodeID from which the sensor receives numeric data.
Sensor Display
Sensor Display
Setting Description


1550
Setting Description
other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
1551
Channel List
Channel Description
More
KNOWLEDGE BASE
Which OPC UA data types does the OPC UA Custom sensor support?

1552
7.8.127 OPC UA Server Status Sensor
The OPC UA Server Status sensor monitors the server status, uptime, and diagnostic information of an
OPC Unified Architecture (OPC UA) server.
OPC UA Server Status Sensor
List 1556 .

§ Dutch: OPC UA Serverstatus
§ French: OPC UA statut du serveur
§ German: OPC UA Serverzustand
§ Japanese: OPC UA
§ Portuguese: Status de servidor OPC UA
1553
§ Russian: OPC UA
§ Spanish: Estado del servidor OPC UA
Remarks
Remark Description
Activated server § This sensor requires activated diagnostic summary information settings
diagnostics on your OPC on your OPC UA server to create all diagnostic channels. Without
UA server activated diagnostic summary information settings, the sensor can only
show the server status and the uptime.
Note that not all vendors support diagnostic summary information.
parent device.
channels.
1554
you add the sensor:
§ opcua
§ opcuaserverstatus
§ serverstatus
Sensor Display
Sensor Display
Setting Description

other above.
procedure to do so.
1555
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
1556
Channel Description
Rejected Requests The number of rejected requests

Count
Rejected Session Count The number of rejected sessions
Security Rejected The number of security rejected requests

Requests Count
Security Rejected The number of security rejected sessions

Session Count
Server Status The server status

§ Up status: Running, Test
§ Warning status: No Configuration, Shut Down, Suspended
§ Down status: Communication Fault, Failed, Unknown
Session Abort Count The number of session aborts
Session Count The number of sessions
Session Timeout Count The number of session timeouts
Subscription Count The number of subscriptions
Uptime The uptime
More
KNOWLEDGE BASE

1557
7.8.128 Oracle SQL v2 Sensor
The Oracle SQL v2 sensor monitors a database on an Oracle server and executes a query.
channels.
Oracle SQL v2 Sensor
List 1568 .

§ Dutch: Oracle SQL v2
§ French: Oracle SQL v2
§ German: Oracle SQL v2
§ Japanese: Oracle SQL v2
§ Portuguese: Oracle SQL v2
§ Russian: Oracle SQL v2
§ Simplified Chinese: Oracle SQL v2
§ Spanish: Oracle SQL v2
Remarks
1558
Remark Description

computer?
does PRTG require?
Oracle version § This sensor supports Oracle database servers as of version 10.2

a guide?

probe device.
1559
you add the sensor:
§ sqlsensor
Database Specific
Database Specific
Setting Description
Identifier Enter the Oracle System ID (SID) or the SERVICE_NAME of the

database that the sensor connects to. Specify the Identification
Parameter below. By default, the sensor uses the SID as the connection
string.
You can find the SID or SERVICE_NAME in the CONNECT_DATA
part of the TNSNames.ora file on the Oracle server. For example, a
SID can look like this: orcl
Identification Parameter Define the type of identifier that you want to use to connect to the
database:
§ SID (default): Connect to the database instance using the SID as the
connection string.
§ SERVICE NAME: Connect to the database instance using the
SERVICE_NAME as the connection string.
1560
Setting Description
The type of identifier that you need to use depends on the

configuration of the Oracle server.
Data
Data
Setting Description
cluster nodes.
1561
Setting Description
into the query.
content:
edited).
1562
Setting Description


as the number 0.

Number.

Databases.
1563
Setting Description

data table.
1564
Setting Description

Channel #x Unit
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
Sensors.
1565
Setting Description

1566
Setting Description
point.


change.
master node.
1567
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
1568
Channel Description
SQL Variables

More
KNOWLEDGE BASE


1569

1570
7.8.129 Oracle Tablespace Sensor
The Oracle Tablespace sensor monitors a tablespace on an Oracle server.
Oracle Tablespace Sensor
List 1575 .

§ Dutch: Oracle Tablespace
§ French: Tablespace Oracle
§ German: Oracle Tablespace
§ Japanese: Oracle
§ Portuguese: Oracle Tablespace
§ Russian: Tablespace Oracle
§ Simplified Chinese: Oracle
§ Spanish: Oracle Tablespace
1571
Remarks
Remark Description
Sufficient account § This sensor requires sufficient privileges for the account that you use for
privileges the connection.
§ Use an account for the connection that has the privileges to see all (or
specific) views. We recommend that you use the SYSTEM account if
possible, otherwise grant your database administrator the
SELECT_CATALOG_ROLE to the account that you use. Without
sufficient privileges, you might see the error message ORA-00942:
table or view does not exist.
does PRTG require?
Overprovisioning § This sensor does not support overprovisioning.
Oracle version § This sensor supports Oracle database servers as of version 10.2
channels.

Knowledge Base § Knowledge Base: Why is my Oracle Tablespace sensor showing

negative values?
probe device.
1572
you add the sensor:
§ sqlsensor
Oracle Specific
Oracle Specific
Setting Description
Identifier Enter the Oracle System ID (SID) or the SERVICE_NAME of the

database that the sensor connects to. Specify the Identification
Parameter below. By default, the sensor uses the SID as the connection
string.
You can find the SID or SERVICE_NAME in the CONNECT_DATA
part of the TNSNames.ora file on the Oracle server. For example, a
SID can look like this: orcl
Identification Parameter Define the type of identifier that you want to use to connect to the
database:
§ SID (default): Connect to the database instance using the SID as the
connection string.
1573
Setting Description
§ SERVICE NAME: Connect to the database instance using the

SERVICE_NAME as the connection string.
The type of identifier that you need to use depends on the
configuration of the Oracle server.
Sensor Name Prefix Define if you want to use the SERVICE_NAME as the prefix for the
sensor name:
§ Do not use a prefix for the sensor name: Only show the name of the
tablespace that this sensor monitors.
§ Use SERVICE_NAME as prefix for the sensor name: Add the
SERVICE_NAME to the beginning of the sensor name.
If you have multiple databases on your Oracle server, use the
SERVICE_NAME as the prefix to distinguish the tablespaces that
you monitor.
Tablespace Specific
Tablespace Specific
Setting Description
Tablespaces The tablespace that this sensor monitors.
Sensor Display
Sensor Display
1574
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
1575
Channel Description
Free Blocks The number of free blocks
Free Blocks % The number of free blocks (%)

Free Space The free space
Free Space % The free space (%)

Online Status The online status

§ Up status: Online, System
§ Warning status: Recover
§ Down status: Offline, Sysoff, Unknown
Status The status
§ Up status: Available
§ Down status: Invalid, Unknown
Tablespace Size The size of the tablespace
Tablespace Size on Disk The size of the tablespace on disk
More
KNOWLEDGE BASE
Why is my Oracle Tablespace sensor showing negative values?


1576
1577
7.8.130 Packet Sniffer Sensor
The Packet Sniffer sensor monitors the headers of data packets that pass a local network card using a
built-in packet sniffer. You can choose from predefined channels.
This sensor analyzes only header traffic.
Packet Sniffer Sensor
List 1584 .

§ Dutch: Packet Sniffer
§ French: Reniflage de paquets
§ German: Packet Sniffer
1578
§ Japanese:
§ Portuguese: Sniffer de pacotes
§ Russian:
§ Spanish: Analizador de paquetes
Remarks
Remark Description
Probe device § By default, this sensor works only on a probe device.
Network Mapper § Using Network Mapper (Nmap) on the parent probe system might
cause high CPU load. If you have this issue, restarting the PRTG probe
service might help.
Knowledge Base § Knowledge Base: How can I change the default groups and channels
Traffic By default, you can only monitor traffic passing the probe system
where the probe device with the sensor is set up. To monitor other
traffic in your network, you can configure a monitoring port (if available)
that the switch sends a copy of all traffic to. You can then physically
connect this port to a network card of the probe system (either local
probe or remote probe system). This way, PRTG can analyze the
complete traffic that passes through the switch. This feature of your
hardware might be called Switched Port Analyzer (SPAN), port mirroring,
or port monitoring.
probe device.
Known Issues
§ The sensor does not support the Simulate Error Status option in the Sensor Context Menu. If you
trigger this action, the sensor does not show a simulated Down status.
1579
you add the sensor:
§ bandwidthsensor
§ sniffersensor
Sniffer Specific
For more information on filters, see section Filter Rules 1584 .
Sniffer Specific
1580
Setting Description
Network Adapters Select the network adapters that this sensor monitors. You see a list of
all adapters that are available on the probe system. To select an adapter,
enable the check box in front of the respective name.
You cannot change this setting if the probe is not connected.
packet data.
interval.
master node.
1581
Setting Description


ICMP, and SNMP.
Other.
channel.
1582
Setting Description
Sensor Display
Sensor Display
Setting Description



other above.
procedure to do so.
1583
Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
Inherited Settings
Toplists
Filter Rules
Channel List
1584
Channel Description

More
KNOWLEDGE BASE


1585
7.8.131 Packet Sniffer (Custom) Sensor
The Packet Sniffer (Custom) sensor monitors the headers of data packets that pass a local network card
using a built-in packet sniffer. With this sensor, you can define your own channel definitions to divide
traffic into different channels.
This sensor does not have any predefined channels.
Packet Sniffer (Custom) Sensor
List 1593 .

§ Dutch: Packet Sniffer (Aangepast)
1586
§ French: Reniflage de paquets personnalisé
§ German: Packet Sniffer (Benutzerdef.)
§ Japanese: ( )
§ Portuguese: Sniffer de pacotes (customizado)
§ Russian: ( )
§ Spanish: Analizador de paquetes (personalizado)
Remarks
Remark Description
Probe device § By default, this sensor works only on a probe device.
Traffic By default, you can only monitor traffic passing the probe system
where the probe device with the sensor is set up. To monitor other
traffic in your network, you can configure a monitoring port (if available)
that the switch sends a copy of all traffic to. You can then physically
connect this port to a network card of the probe system (either local
probe or remote probe system). This way, PRTG can analyze the
complete traffic that passes through the switch. This feature of your
hardware might be called Switched Port Analyzer (SPAN), port mirroring,
or port monitoring.
probe device.
Known Issues
§ The sensor does not support the Simulate Error Status option in the Sensor Context Menu. If you
trigger this action, the sensor does not show a simulated Down status.
1587
you add the sensor:
§ bandwidthsensor
§ sniffersensor
Sniffer Specific
For more information on filters, see section Filter Rules 1592 .
1588
Sniffer Specific
Setting Description
1589
Setting Description
Network Adapters Select the network adapters that this sensor monitors. You see a list of
all adapters that are available on the probe system. To select an adapter,
enable the check box in front of the respective name.
You cannot change this setting if the probe is not connected.
packet data.
interval.
master node.
Sensor Display
Sensor Display
Setting Description
1590
Setting Description



other above.
procedure to do so.
Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
1591
Inherited Settings
Toplists
Filter Rules
Port Any number

(OSPF), any number
The following filter rules apply to Packet Sniffer sensors only.
1592
MAC Physical address
SourceMAC Physical address
DestinationMAC Physical address
EtherType IPV4, ARP, RARP, APPLE, AARP, IPV6, IPXold, IPX, any number
VlanPCP IEEE 802.1Q VLAN Priority Code Point
VlanID IEEE 802.1Q VLAN Identifier
TrafficClass IPv6 Traffic Class: corresponds to TOS used with IPv4
FlowLabel IPv6 Flow Label
Channel List
Channel Description

More
KNOWLEDGE BASE

1593
1594
7.8.132 PerfCounter Custom Sensor
The PerfCounter Custom sensor monitors a configured set of Windows performance counters. You can
define your own channels.
This sensor does not have any predefined channels.
PerfCounter Custom Sensor
List 1599 .

§ Dutch: Prestatie Meters Klantspecifiek
§ French: Windows PerfCounter personnalisé
§ German: Leistungsindikator (benutzerdef.)
§ Japanese:
§ Portuguese: PerfCounter (customizado)
§ Russian: PerfCounter
§ Spanish: PerfCounter (personalizado)
Remarks
1595
Remark Description

not possible.
The user account must be a member of the Performance Monitor
Users user group on the target system.
Same name § You cannot add different performance counters with the same name to
one sensor.
Angle brackets § If a performance counter contains angle brackets (< or >), do not edit
the channel settings because this might cause an error.
Knowledge Base § Knowledge Base: How can I find out the names of available
performance counters?
§ Knowledge Base: My performance counter sensor does not work. What
can I do?
probe device.
1596
you add the sensor:
§ performancecounter
§ performancecountercustom
Performance Counter Settings
Performance Counter Settings
Setting Description
Performance Counters Enter the performance counters that you want to query. Enter each
counter in one line. PRTG creates one channel for each performance
counter that you select. Use the following syntax: the name of the
counter, followed by two colons (::), and the unit.
Example: \Processor(_Total)\% Processor Time::%
You cannot monitor different performance counters with the same
name in one sensor. The sensor uses the performance counter as
the channel name, so this would create duplicate channels, which PRTG
does not support. If you want to monitor different performance counters
with the same name, add one sensor for each counter. You can also
create a custom sensor. For example, you can write a PowerShell query
that connects to the target device, retrieves the desired counters with the
Get-Counter cmdlet, and reports them to PRTG as individual channels.
1597
Setting Description
If a custom performance counter includes angle brackets (< or >), do

not edit the channel settings (for example, limits) after sensor
creation. This might lead to a malfunctioning sensor.
Value Display Mode Determine if the sensor displays the returned value as an absolute value
or if it displays the difference between the last and the current value:
§ Absolute (default): Display the returned value as an absolute value.
§ Difference: Display the difference between last and current value.

Make sure that all performance counters that you monitor are
capable of this mode.
Sensor Display
Sensor Display
Setting Description


1598
Setting Description
other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
[Custom] The Windows performance counters in different channels
To find available performance counters and their names on the target

system, see the Knowledge Base: How can I find out the names of
available performance counters?
More
KNOWLEDGE BASE
How can I find out the names of available performance counters?

My performance counter sensor does not work. What can I do?

1599
1600
7.8.133 PerfCounter IIS Application Pool Sensor
The PerfCounter IIS Application Pool sensor monitors a Microsoft Internet Information Services (IIS)
application pool via Windows performance counters.
PerfCounter IIS Application Pool Sensor
List 1604 .

§ Dutch: PerfCounter IIS Application Pool
§ French: Windows IIS Pool d'applications (PerfCounter)
§ German: Leistungsindikator IIS-Anwendungspool
§ Japanese: IIS
§ Portuguese: Pool de aplicativos IIS (PerfCounter)
§ Russian: IIS (PerfCounter)

§ Simplified Chinese: IIS
§ Spanish: Grupo de aplicaciones IIS (PerfCounter)
1601
Remarks
Remark Description
IIS version 7.5 § This sensor requires as of Microsoft IIS 7.5 on the target system.
not possible.
The user account must be a member of the Performance Monitor
Users user group on the target system.
channels.
probe device.
1602
you add the sensor:
§ pciisapppool
§ performancecounter
IIS Application Pool Specific
IIS Application Pool Specific
Setting Description
Application Pools The name of the application pool that this sensor monitors.
Sensor Display
Sensor Display
1603
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Application Pool State The overall application pool status

§ Up status: Running, Unavailable for Total
§ Warning status: Initialized, Shutdown Pending
1604
Channel Description
§ Down status: Delete Pending, Stopped, Stopping, Unavailable,

Uninitialized
Worker Process Failures The number of failures in worker processes
Worker Process Ping The number of failures in worker process pings

Failures
Worker Process The number of failures in worker process shutdowns

Shutdown Failures
Worker Process Startup The number of failures in worker process startups

Failures
Worker Processes The number of worker processes
More
KNOWLEDGE BASE

1605
7.8.134 Ping Sensor
The Ping sensor sends an Internet Control Message Protocol (ICMP) echo request ("ping") from the
probe system to the parent device to monitor its availability.
The default number of pings per scanning interval is 5.
Ping Sensor
List 1610 .

§ Dutch: Ping
§ French: Ping
§ German: Ping
§ Japanese: Ping
§ Portuguese: Ping
§ Russian:
§ Simplified Chinese: Ping
§ Spanish: Ping
Remarks
1606
Remark Description
Knowledge Base § Knowledge Base: How to create/customize statistical Ping sensor?
§ Knowledge Base: Can I create an inverse Ping sensor?
you add the sensor:
§ pingsensor
1607
Ping Settings
Ping Settings
Setting Description
integer. The maximum timeout value is 300 seconds (5 minutes).
Packet Size (Bytes) Enter the packet size for the ping in bytes. You can enter any value
between 1 and 10000. Enter an integer.
Ping Method Define the kind of ping check that the sensor performs with each
scanning interval:
§ Send one single ping: Send a single ping only. The sensor then shows
the ping time only.
This setting is useful for monitoring availability.
§ Send multiple ping requests (default): Send multiple pings in a row. The
sensor then also shows the minimum and the maximum ping time as
well as the packet loss (in percent).
This setting is useful if you want to create reports about average
ping times out of a series of ping requests.
If you select this setting, all of the ping requests must be lost for
the sensor to show the Down status. For example, if only one ping
request is answered in a series of five, the sensor still shows the Up
status.
1608
Setting Description
Ping Count This setting is only visible if you select Send multiple ping requests
above.
Enter the number of pings that the sensor sends in a row in one scanning
interval. Enter an integer. The default value is 5.
Ping Delay (ms) This setting is only visible if you select Send multiple ping requests
above.
Enter the time in milliseconds (ms) that the sensor waits between two
ping requests. Enter an integer. The default value is 5.
Increase the value if the target device drops ping packets because of
denial of service (DoS) suspicion.
Acknowledge Define if you want to automatically acknowledge the Down status of the
Automatically sensor:
§ Show down status on error (default): Do not automatically acknowledge
an alarm if this sensor changes to the Down status.
§ Show down (acknowledged) status on error: Automatically
acknowledge an alarm. If this sensor changes to the Down status, it
automatically shows the Down (Acknowledged) status instead.
Sensor Display
Sensor Display
Setting Description
1609
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Maximum The maximum ping time when using more than one ping per interval
Minimum The maximum ping time when using more than one ping per interval
Packet Loss The packet loss when using more than one ping per interval (%)
Ping Time The ping time
1610
Channel Description
More
KNOWLEDGE BASE
How to create/customize statistical Ping sensor?

Can I create an inverse Ping sensor?


1611
7.8.135 Ping v2 Sensor
The Ping v2 sensor sends an Internet Control Message Protocol (ICMP) echo request ("ping") from the
probe system to the parent device to monitor its availability.
Ping v2 Sensor
List 1617 .

§ Dutch: Ping v2
§ French: Ping v2
§ German: Ping v2
§ Japanese: Ping v2
§ Portuguese: Ping v2
§ Russian: v2
§ Simplified Chinese: Ping v2
§ Spanish: Ping v2
Remarks
1612
Remark Description
Knowledge Base § Knowledge Base: How to create/customize statistical Ping sensor?
Add Sensor
Setting Description
Inverted Error Status Select if you want the sensor to show the Down status if the target is
reachable:
§ Disable (default): Show the Down status if the target is not reachable.
§ Enable: Show the Down status if the target is reachable.
To change this behavior after sensor creation, open the channel

settings of channel Status and change the Lookup. Select
prtg.standardlookups.paessler.icmp.reachability_state if you want the
sensor to show the Down status if the target is not reachable. Select
prtg.standardlookups.paessler.icmp.reachability_state_reversed if you
want the sensor to show the Down status if the target is reachable.
If you select Enable, Status is the primary channel.
you add the sensor:
1613
§ icmp
§ ping
§ pingsensor
Ping Settings
Ping Settings
Setting Description
Ping Method Define the kind of ping check that the sensor performs with each
scanning interval:
§ Send one single ping: Send a single ping only. The sensor then shows
the ping time only.
This setting is useful for monitoring availability.
1614
Setting Description
§ Send multiple ping requests (default): Send multiple pings in a row. The
sensor then also shows the minimum and the maximum ping time as
well as the packet loss (in percent).
This setting is useful if you want to create reports about average
ping times out of a series of ping requests.
If you select this setting, all of the ping requests must be lost for
the sensor to show the Down status. For example, if only one ping
request is answered in a series of five, the sensor still shows the Up
status.
Ping Count This setting is only visible if you select Send multiple ping requests
above.
Enter the number of pings that the sensor sends in a row in one scanning
interval. Enter an integer. The default value is 5.
Ping Delay (ms) This setting is only visible if you select Send multiple ping requests
above.
Enter the time in milliseconds (ms) that the sensor waits between two
ping requests. Enter an integer. The default value is 5.
Increase the value if the target device drops ping packets because of
denial of service (DoS) suspicion.
Time to Live (hops) Define the time to live (TTL) for the request. You can limit the number of
network hops that the request can traverse before it is dropped. The
default value is 64.
Sensor Display
Sensor Display
Setting Description
1615
Setting Description



other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
1616
Inherited Settings
Channel List
Channel Description
Maximum Response The maximum ping time when using more than one ping per interval
Time
Minimum Response Time The maximum ping time when using more than one ping per interval
Packet Loss The packet loss when using more than one ping per interval (%)
Response Time The ping time
Status The target status

§ Up status: Reachable
§ Down status: Unreachable
This is the primary channel if you enable Inverted Error Status.
More
KNOWLEDGE BASE
How to create/customize statistical Ping sensor?


1617
7.8.136 Ping Jitter Sensor
The Ping Jitter sensor sends a series of Internet Control Message Protocol (ICMP) echo requests
("pings") to a URI to determine the statistical jitter.
Ping Jitter Sensor
List 1621 .

§ Dutch: Ping Jitter
§ French: Gigue du Ping
§ German: Ping Jitter
§ Japanese: Ping
§ Portuguese: Jitter Ping
§ Russian:
§ Simplified Chinese: Ping
§ Spanish: Jitter de Ping
Remarks
1618
Remark Description
system.
does PRTG require?
you add the sensor:
§ ptfsensor
Sensor Settings
Sensor Settings
1619
Setting Description
Ping Count Define the number of ICMP pings that the sensor sends. Enter an integer.
The default value is 50.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
1620
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
1621
Channel Description
Jitter The statistical jitter value

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 according to the first x packets

received using the statistical variance formula:
Jitter Statistical = SquareRootOf( SumOf( ( ElapsedTime[i] –
Average) ^ 2 ) / ( ReceivedPacketCount – 1 ) )
More
KNOWLEDGE BASE


1622
7.8.137 POP3 Sensor
The POP3 sensor monitors an email server via the Post Office Protocol version 3 (POP3).
POP3 Sensor
List 1628 .

§ Dutch: POP3
§ French: POP3
§ German: POP3
§ Japanese: POP3
§ Portuguese: POP3
§ Russian: POP3
§ Simplified Chinese: POP3
§ Spanish: POP3
Remarks
Remark Description
1623
Remark Description
sensor.
you add the sensor:
§ mailsensor
§ pop3sensor
POP3 Specific
POP3 Specific
Setting Description
1624
Setting Description
Port Specify the port that the sensor uses for the POP3 connection. The
Connection Security
Connection Security
Setting Description
1625
Setting Description

Authentication
Authentication
1626
Setting Description
POP3 Authentication Select the authentication method for the POP3 connection:
Method
§ <%C_Without_login%> (default): Only monitor the connection to the
POP3 server.
§ User name and password: Log in to the POP3 server with user name
and password.
This is a simple login. It is not secure.
§ 128-bit MD5 hash value (APOP): Send the password in an encrypted
form using APOP.
The POP3 server that you connect to must support this option.
User Name This setting is only visible if you select User name and password or 128-
bit MD5 hash value (APOP) above.
Enter a user name for POP3 authentication. Enter a string.
Password This setting is only visible if you select User name and password or 128-
scanning interval.
master node.
Sensor Display
Sensor Display
1627
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
1628
Channel Description

More
KNOWLEDGE BASE

1629
7.8.138 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, the sensor can alert you either when the monitored port is open or
when it is closed.
Port Sensor
List 1636 .

§ Dutch: Poort
§ French: Port
§ German: Port
§ Japanese:
§ Portuguese: Porta
§ Russian:
§ Spanish: Puerto
Remarks
1630
Remark Description
probe device.
you add the sensor:
§ portsensor
Port Specific
Port Specific
Setting Description
1631
Setting Description

Port Enter the number of the port to which this sensor connects. Enter an
integer.
Connection Security
Connection Security
Setting Description
Transport-Level Security Define the security of the connection:

strongest Secure Sockets Layer (SSL)/Transport Layer Security (TLS)
method that the target device provides.
Advanced Sensor Settings
Advanced Sensor Settings
1632
Setting Description
Goal Define how the sensor reports on the port:

§ Open: Show the Up status if the port is open, and the Down status if
the port is closed.
§ Closed: Show the Up status if the port is closed, and the Down status if
the port is open.
Command Handling This setting is only visible if you select Open above.
Define whether the sensor sends a command after it opens the port:
§ Do not send a command (default): Only check if a connection to the
port is possible.
§ Send a command: Open a Telnet session to the respective port and
send a command.
You cannot use this option if the target device is a web server.
Command This setting is only visible if you select Send a command above.
Enter the command that the sensor sends to the respective port in a
Telnet session. Enter a string.
You cannot use line breaks. You can only use a simple Telnet
command in a single line.
Response Define if the sensor further processes the response:

§ Ignore (default): Do not check the response.
§ Check response code (integer): Check if the response matches a

defined response code. Define the response code below.
§ Check response text: Check if the response matches a defined
response text. Define the response text below.
Allowed Response Code This setting is only visible if you select Check response code (integer)
above.
Enter the code that the target device must return. If the target device does
not return this code, the sensor shows the Down status. Enter an integer.
Check for Keywords This setting is only visible if you select Check response text above.
(positive)
Check if the response contains a specific keyword:
§ Disable: Do not check for positive keywords.
1633
Setting Description
§ Enable keyword check (positive): Check if a specific keyword exists in

the received value. Define the keyword below. If the response does not
contain the keyword, the sensor shows the Down status.
Response Must Include This setting is only visible if you select Enable keyword check (positive)
(Down Status if Not above.
Included)
Define the search string that the response must contain. You can enter a
simple string in plain text or a regular expression (regex).
If the data does not include the search pattern, the sensor shows the
Down status.


Check for Keywords This setting is only visible if you select Simple string search (default)
(negative) above.
Check if the response does not contain a specific keyword:

§ Disable: Do not check for negative keywords.
§ Enable keyword check (negative): Check if a specific keyword does not

exist in the received value. Define the keyword below. If the response
does contain the keyword, the sensor shows the Down status.
Response Must Not This setting is only visible if you select Enable keyword check (negative)
Include (Down Status if above.
Included)
Define the search string that the response must not contain. You can
enter a simple string in plain text or a regex.
If the data does include the search pattern, the sensor shows the
Down status.
1634
Setting Description


scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
1635
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Available The time until a request to a port is accepted

More
KNOWLEDGE BASE
1636
1637
7.8.139 Port v2 Sensor (BETA)
The Port v2 sensor monitors a network service by connecting to one or more of its TCP/IP ports.
Depending on your settings, the sensor can alert you either when the monitored port is open or
when it is closed.
all.
Port v2 Sensor
List 1642 .

§ Dutch: Poort v2
§ French: Port v2
§ German: Port v2
§ Japanese: v2
§ Portuguese: Porta v2
§ Russian: v2
§ Simplified Chinese: Port v2
§ Spanish: Puerto v2
1638
Remarks
Remark Description
Enabled Beta Sensors § This sensor requires that the Beta Sensors experimental feature is
experimental feature enabled.
For more information, see the Knowledge Base: What are beta
sensors and how can I use them?
this sensor.
Known Issues
§ The sensor shows the Unknown state if a sensor scan was executed during the scan of the port list. If
this issue occurs, reduce the list of monitored ports or increase the Scanning Interval 1642 of the sensor.
The scan of each port takes about two seconds. For example, if you monitor the ports 1-900, the
sensor needs around 1,800 seconds (30 minutes) to complete the port list.
Add Sensor
Setting Description
Goal Define how the sensor reports on the ports:

§ Open: Shows the Up status if the port is open, and the Down status if
the port is closed.
§ Closed: Shows the Up status if the port is closed, and the Down status
if the port is open.
You can modify the limits in the channel settings to change the
sensor behavior. For more information, see section Channel Settings.
1639
you add the sensor:
§ portrangesensor
§ portsensor
§ tcp
Port Specific
Port Specific
Setting Description
Port-by-Port Delay (ms) Define how long the sensor waits before it tries to connect to the next
port. The maximum delay value is 100 ms.
1640
Setting Description
Port List Enter the port numbers that the sensor tries to connect to. Enter one port
number per line. PRTG supports the port numbers 1 - 65535. You can
also specify port ranges by using A-B, for example 8080-8090. Enter an
integer.
Sensor Display
Sensor Display
Setting Description

other above.
procedure to do so.
1641
Debug Options
Debug Options
Setting Description
Inherited Settings
Channel List
Channel Description
Closed Ports The number of closed ports
1642
Channel Description

Maximum Connect Time The maximum time until a request to connect to a port was accepted
Open Ports The number of open ports
More
KNOWLEDGE BASE


1643
7.8.140 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 the device to
accept each request.
Optionally, you can set limits in the channel settings. This way, you can get alerts about open and
closed ports.
Port Range Sensor
List 1648 .

§ Dutch: Poortbereik
§ French: Plage de port
§ German: Portbereich
§ Japanese:
§ Portuguese: Intervalo de portas
§ Russian:
§ Spanish: Rango de puerto
1644
Remarks
Remark Description
probe device.
you add the sensor:
§ portrangesensor
1645
Port Range Specific
Port Range Specific
Setting Description
Port-by-Port Delay (ms) Define how long the sensor waits in milliseconds (ms) to go to the next
port while it runs through all specified ports.
Port Range Selection Define whether you want to monitor all ports within a range or if you want
Method to monitor several individual ports:
§ Port range: Monitor ports within a range.
§ List of ports: Monitor several individual ports.
Range Start This setting is only visible if you select Port range above.
Enter the port number where the scan starts. Enter an integer.
Range End This setting is only visible if you select Port range above.
Enter the port number where the scan ends. Enter an integer.
Port List This setting is only visible if you select List of ports above.
1646
Setting Description
Enter the numbers of the ports that the sensor tries to connect to. Enter
one or more individual integers. Enter each port in one line.
If Value Changes Define what the sensor does if the number of closed ports or open ports
changes:

change.
Sensor Display
Sensor Display
Setting Description


other above.
1647
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Available The time until requests to ports are accepted

Closed Ports The number of closed ports
Open Ports The number of open ports
More
KNOWLEDGE BASE

1648
7.8.141 PostgreSQL Sensor
The PostgreSQL sensor monitors a database on a PostgreSQL server and executes a query.
channels.
PostgreSQL Sensor
List 1659 .

§ Dutch: PostgreSQL
§ French: PostgreSQL
§ German: PostgreSQL
§ Japanese: PostgreSQL
§ Portuguese: PostgreSQL
§ Russian: PostgreSQL
§ Simplified Chinese: PostgreSQL
§ Spanish: PostgreSQL
Remarks
1649
Remark Description
system. In a cluster, copy the file to every cluster node. Save the SQL
script with the query in the \Custom Sensors\sql\postgresql subfolder of
the PRTG program directory.
computer?
does PRTG require?
PostgreSQL version § This sensor supports as of PostgreSQL 7.x.

Knowledge Base § Knowledge Base: How can I monitor strings from an SQL database and
probe device.
1650
you add the sensor:
§ sqlsensor
Database Specific
Database Specific
Setting Description
Database Enter the name of the PostgreSQL database to which the sensor
connects, for example MyDatabase. This is a logical entity on the
database server where database objects exist.
SSL Mode Select the PostgreSQL Secure Sockets Layer (SSL) mode for the
connection:
§ Disable: Do not use SSL.
§ Allow: Use SSL if the server demands it.
§ Prefer: Use SSL if the server supports it.
§ Require: Always use SSL and deny the connection if the server does
not support it.
1651
Setting Description
The SSL mode options that you can choose are the same as the values
of the PostgreSQL sslmode parameter. PRTG sends it with the sensor
requests.
PostgreSQL SSL connections require OpenSSL to be installed on
both the target server and on the probe system.
For more information about the PostgreSQL SSL modes, refer to the
PostgreSQL documentation.
Data
Data
Setting Description
cluster nodes.
1652
Setting Description
into the query.
content:
edited).
1653
Setting Description


as the number 0.

Number.

Databases.
1654
Setting Description

data table.
1655
Setting Description
Channel #x Unit
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
Sensors.
1656
Setting Description

1657
Setting Description
Message This setting is only visible if you enable Use Data Table Value in Message
above.
point.


change.
master node.
Sensor Display
Sensor Display
1658
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
1659
Channel Description
SQL Variables
More
KNOWLEDGE BASE


1660
7.8.142 Probe Health Sensor
The Probe Health sensor monitors internal PRTG parameters. It shows the status of the probe system
and checks various parameters of the probe system that can affect the quality of the monitoring results.
This sensor does not support multi-platform probes. Use the Multi-Platform Probe Health 1358 sensor
instead.
Probe Health Sensor
List 1663 .

§ Dutch: Probe Status
§ French: État de la sonde
§ German: Zustand der Probe
1661
§ Japanese:
§ Portuguese: Funcionamento da sonda
§ Russian:
§ Spanish: Salud de sonda
Remarks
Remark Description
§ PRTG dynamically creates limits for the Data Storage Free channel 1664
of this sensor.
Knowledge Base § Knowledge Base: My probe system is running out of disk space. What
can I do?
you add the sensor:
§ probehealthsensor
1662
Sensor Display
Sensor Display
Setting Description
device tree, PRTG displays the last value of the primary channel below the
sensor's name. The available options depend on what channels are


other above.
procedure to do so.
Inherited Settings
Channel List
1663
Channel Description
Data Storage Free The free disk space on the probe system
PRTG dynamically creates limits for this channel. This means that
Enable alerting based on limits is enabled in the channel settings but
the limits are empty. Because of this, you cannot save any changes to
the channel settings. Enter limits or select Disable limits to save changes
to the channel settings.
Health The sum of the probe state as a value between 100% (healthy) and 0%
(failing). Investigate frequent or repeated health values below 100%.
Interval Delay non- The interval delay in percent for all sensors that are not of the type SNMP
WMI&SNMP or WMI. If this value is above 0%, try to increase the scanning intervals or
distribute your sensors among probes.
Interval Delay SNMP The interval delay in percent for SNMP sensors. If this value is above 0%,
there are probably too many SNMP v3 sensors that are very slow. In this
case, try to increase the scanning intervals or distribute the sensors
among probes.
Interval Delay WMI The interval delay in percent for WMI sensors. If this value is above 0%,
WMI sensors were not able to check the target device according to their
interval. 100% means that WMI sensors are checked with twice their
interval on average. For values above 0%, try to increase the scanning
intervals or distribute the sensors among probes to keep the number of
WMI sensors per probe below 120 (with a 60-second scanning interval) or
600 (with a 300-second scanning interval).
1664
Channel Description

Lost Flow Packets The number of lost Flow packets. The higher this value, the less flow
packages PRTG can handle. Usually, this value should be 0%.
Investigate increasing values.
Memory Usage The amount of memory that is used by the PRTG probe service as
reported by the memory manager. Investigate obviously increasing values
that occur repeatedly. If the value is constantly above 2 GB, this indicates
that PRTG runs at its limits. In this case, you should distribute some
sensors among remote probes.
§ Upper error limit: 3221225472 bytes
§ Upper warning limit: 1610612736 bytes
Message Queue The number of monitoring results that have not been processed by the
PRTG core server yet. This value should usually stay below 1/10 of the
sensor count.
Open Requests The number of active monitoring requests. This value should stay below
the maximum of 500 open requests.
Probe Process CPU The CPU load (%) that the probe process causes. Extensive CPU load
Load can lead to false, incomplete, and incorrect monitoring results. This value
should usually stay below 50%.
Syslog Buffer The number of buffered syslog packages. Usually, this value should be 0
(or very low). Investigate increasing values.
Syslog Drop The number of dropped syslog packages
1665
Channel Description
Threads The number of program parts that are running simultaneously. This value
can increase with heavy load. Usually, the number should not exceed
100.
Toplist Memory The amount of RAM that the Toplists on this probe are using. Stay below
1 GB memory usage (depending on the available memory on the probe
system). If necessary, reduce the number of Toplists or distribute them
among probes.
§ Upper error limit: 2147483648 bytes
§ Upper warning limit: 1073741824 bytes
Trap Buffer The number of buffered SNMP traps. Usually, this value should be 0 (or
very low). Investigate increasing values.
More
KNOWLEDGE BASE
My probe system is running out of disk space. What can I do?


1666
7.8.143 Python Script Advanced Sensor
The Python Script Advanced sensor executes a Python script on the probe system. This option is
available as part of the PRTG API.
The return value of this sensor must be valid JavaScript Object Notation (JSON) or Extensible
Markup Language (XML).
Python Script Advanced Sensor
List 1674 .

§ Dutch: Python Script Geavanceerd
§ French: Script Python avancé
§ German: Python-Skript (Erweitert)
§ Japanese: Python ( )
§ Portuguese: Script Python (avançado)
§ Russian: Python ( )
§ Simplified Chinese: Python
§ Spanish: Script Python (avanzado)
Remarks
1667
Remark Description
File storage § This sensor requires that you store the script file on the probe system.
In a cluster, copy the file to every cluster node.
§ This sensor does not support channel values greater than 2^62.
Print commands § This sensor does not support print commands in the Python script.
They lead to an invalid JSON result.
Exceptions § This sensor does not support exceptions in the Python script.
Python environment § PRTG uses its own Python environment. This is located in the \python
subfolder of the PRTG program directory. To avoid issues, we
recommend that you do not have other Python environments running on
a probe system. We also recommend that you do not uninstall the
paesslerag_prtg_sensor_api package.
Timeout § The timeout of the sensor is its scanning interval 1674 minus 1 second.
Make sure that your Python script does not run longer than this.
Sensor usage § For best sensor usage, we recommend that the return value is JSON
encoded.
settings?
§ Knowledge Base: After updating to PRTG 20.1.55, my Python Script
Advanced sensors are down
probe device.
1668
you add the sensor:
§ json
§ python
§ pythonxml
§ script
§ xml

Setting Description
1669
Setting Description
Sensor Settings
Sensor Settings
1670
Setting Description
Script Select a Python script from the list. The sensor executes it with every
scanning interval 1674 .
This list shows all Python script files that are available in the \Custom
Sensors\python subfolder of the PRTG program directory on the probe
system. For the files to appear in this list, store the files in this subfolder
with the extension .py.
To show the expected values and sensor status, your files must
return the expected XML or JSON format to standard output. The
values and message must be embedded in the XML or JSON. We
recommend JSON-encoded return values.
every cluster node.
Security Context Define the Windows user account that the sensor uses to run the Python
interpreter:
§ Use security context of PRTG probe service (default): Run the Python
script file under the same Windows user account that the probe system
runs under. By default, this is the Windows system user account.
account from the settings of the parent device.
Device Credentials PRTG adds the device credentials to the JSON object that is passed to
the script as a command-line parameter. Define if you want to transmit
device credentials to the Python script:
§ Do not transmit device credentials: Transmit no device credentials to
the script.
§ Transmit Windows credentials: Transmit Windows credentials to the
script.
§ Transmit Linux credentials: Transmit Linux credentials to the script.
§ Transmit SNMP credentials: Transmit SNMP credentials to the script.
§ Transmit all device credentials: Transmit Windows, Linux, and Simple

Network Management Protocol (SNMP) credentials to the script.
The sensor transmits all parameters in plain text.
Additional Parameters Define additional parameters to add to the JSON object that is passed to
the script as a command-line parameter. Enter a string or leave the field
empty.
1671
Setting Description
The sensor passes a custom JSON object within a dictionary to the

script. The dictionary contains the key params that contains all
additional parameters in one string.
Use the following command to load the dictionary that the sensor sends
to the script:
data = json.loads(sys.argv[1])
Use the following command to load the additional parameters:

params = json.loads(data["params"])
If the string contains more than one parameter, you can use the
Split() function in Python to split the string.
The sensor transmits all parameters in plain text.
PRTG executes all Python Script Advanced sensors that have the
same mutex serially, not simultaneously. This is useful if you use a
lot of sensors and want to avoid high resource usage because of
simultaneously running processes.
Debug Options
Debug Options
Setting Description
1672
Setting Description
You can use Store result to inspect the passed JSON object that
contains all parameters. This way, you can find out which key you
can access when you script.
PRTG masks transmitted passwords in the log file.

master node.
Sensor Display
Sensor Display
Setting Description



other above.
procedure to do so.
1673
Inherited Settings
Channel List
Channel Description
[Value] The values that the Python script returns in several channels
Custom Sensors.
More
KNOWLEDGE BASE

After updating to PRTG 20.1.55, my Python Script Advanced sensors are down

1674
7.8.144 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.
The sensor sends a series of User Datagram Protocol (UDP) packets from the source probe to a
target probe and measures several parameters.
QoS (Quality of Service) One Way Sensor
List 1679 .

§ Dutch: QoS (Quality of Service) Eén Richting
§ French: QoS (qualité de service) unidirectionnel
§ German: QoS (Quality of Service) Unidirektional
§ Japanese: QoS( Quality of Service)
1675
§ Portuguese: Unidirecional QoS (qualidade de serviço)
§ Russian:
§ Simplified Chinese: QoS ( )

§ Spanish: Unidireccional QoS (calidad de servicio)
Remarks
Remark Description
Remote probe § This sensor requires that you configure at least one classic remote
probe in your PRTG Network Monitor setup, and at least two classic
remote probes in PRTG Hosted Monitor.
Sensor creation § You can create this sensor on the probe device of a local probe or a
classic remote probe.
probe device.
you add the sensor:
§ qossensor
1676
Quality of Service Measurement
Setting Description
Target Probe Define the target probe that receives the UDP packets. The dropdown list
shows all local probes and remote probes in your setup.
If you want to run the sensor on the local probe, select a remote probe as
the Target Probe. If no remote probe is available, install and connect a
remote probe first.
If you want to run the sensor on a remote probe, select either a different
remote probe or the local probe as the target. The sensor measures
values for the network track between the parent probe and the target
probe.
You must make sure that firewalls or network address translation
(NAT) rules allow UDP packets to reach the target probe. The probe
automatically opens the Windows firewall on the target system.
In PRTG Hosted Monitor, you can only select a different remote
probe as the target probe. QoS measurements for connections to the
hosted probe are not possible.
Target Host/IP Address Define the IP address of the target probe.
Port Define the source and target port for the UDP packets. Both the source
probe and the target probe use this port. Enter an integer. The default port
is 50000. PRTG supports the port numbers 1024-65536 for UDP packets.
1677
Setting Description
Use a different port for each QoS (Quality of Service) One Way
sensor to make sure that PRTG can assign packets correctly.
The port must be available on both the source system and the target
system.
Number of Packets Define the number of packets that the sensor sends with each scanning
interval. Enter an integer. The default value is 1000. The minimum value is
10. The maximum value is 1000.
Packet Size (Bytes) Define the size of the packets in bytes that the sensor sends. Enter an
integer. The default value is 172. The minimum value is 172. The
Packet Delay (ms) Define the time in milliseconds (ms) that the sensor waits between two
packets. Enter an integer. The default value is 20. The minimum value is
Sensor Display
Sensor Display
Setting Description
1678
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Jitter Average The average jitter
Jitter Max The maximum jitter

Jitter Min The minimum jitter
1679
Channel Description
Packet Delay Variation The average packet delay variation

Average
Packet Delay Variation The maximum packet delay variation

Max
Packet Delay Variation The minimum packet delay variation

Min
Packets Corrupted The corrupted packets (%)

Packets Duplicated The duplicated packets (%)

Packets Lost The lost packets (%)

Packets Out Of Order The out of order packets (%)

Time to Last Packet The time to the last packet

More
KNOWLEDGE BASE

1680
PAESSLER WEBSITE

1681
7.8.145 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.
The sensor sends a series of User Datagram Protocol (UDP) packets from the source probe to a
target probe at the end of the connection line. Then, the target probe sends the packets back to the
source probe.
QoS (Quality of Service) Round Trip Sensor
List 1687 .

§ Dutch: QoS (Quality of Service) Heen en weer
§ French: QoS (qualité de service) aller-retour
§ German: QoS (Quality of Service) Round Trip
§ Japanese: QoS( Quality of Service)
1682
§ Portuguese: Ida e volta QoS (qualidade de serviço)
§ Russian:
§ Simplified Chinese: QoS ( )

§ Spanish: Ida y vuelta QoS (calidad de servicio)
Remarks
Remark Description
Remote probe § This sensor requires that you configure at least one classic remote
probe in your PRTG Network Monitor setup and at least two classic
remote probes in PRTG Hosted Monitor, or you must set up the PRTG
QoS Reflector tool on the target system at the endpoint of the
connection that you want to monitor.
Knowledge Base § Knowledge Base: How can I monitor QoS round trips without using
remote probes?
§ Knowledge Base: How does PRTG calculate the MOS score for QoS
sensors?
§ Knowledge Base: What connection settings are necessary for the QoS
(Quality of Service) Round Trip sensor?
probe device.
1683
you add the sensor:
§ qossensor
Setting Description
1684
Setting Description
QoS Target Define the type of target that receives the UDP packets:
§ Probe (default): Use a probe as the connection endpoint.
§ Custom target: Use the PRTG QoS Reflector as the connection

endpoint.
For more information about the QoS Reflector, see the Knowledge
Base: How can I monitor QoS round trips without using remote
probes?
Target Probe This setting is only visible if you select Probe (default) above.
Define the target probe that receives the UDP packets. The dropdown list
shows all local probes and remote probes in your setup.
If you want to run the sensor on the local probe, select a remote probe as
the Target Probe. If no remote probe is available, install and connect a
remote probe first. Alternatively, you can use the PRTG QoS Reflector.
If you want to run the sensor on a remote probe, select either a different
remote probe or the local probe as the target. The sensor measures
values for the network track between the parent probe and the target
probe.
You must make sure that firewalls or network address translation
(NAT) rules allow UDP packets to reach the target probe. The probe
automatically opens the Windows firewall on the target system. For more
information, see the Knowledge Base: What connection settings are
necessary for the QoS (Quality of Service) Round Trip sensor?
In PRTG Hosted Monitor, you can only select a different remote
probe as the target probe. QoS measurements for connections to the
hosted probe are not possible.
Target Host/IP Address Define the IP address of the QoS target:

§ If you use the QoS Reflector, enter the address of the system on which
the reflector script runs.
§ If you use a probe, enter the address of the probe to which the source
probe connects.
Port Define the source and target port for the UDP packets. Both the source
probe and the target probe use this port. Enter an integer. The default port
is 50000. PRTG supports the port numbers 1024-65536 for UDP packets.
Use a different port for each QoS (Quality of Service) Round Trip
sensor to make sure that PRTG can assign packets correctly.
The port must be available on both the source system and the target
system.
1685
Setting Description
Number of Packets Define the number of packets that the sensor sends with each scanning
interval. Enter an integer. The default value is 1000. The minimum value is
Packet Size (Bytes) Define the size of the packets in bytes that the sensor sends. Enter an
integer. The default value is 172. The minimum value is 172. The
Packet Delay (ms) Define the time in milliseconds (ms) that the sensor waits between two
packets. Enter an integer. The default value is 20. The minimum value is
Sensor Display
Sensor Display
Setting Description

1686
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Jitter Average The average jitter
Jitter Max The maximum jitter

Jitter Min The minimum jitter
MOS The MOS
1687
Channel Description
Packet Delay Variation The average packet delay variation

Average
Packet Delay Variation The maximum packet delay variation

Max
Packet Delay Variation The minimum packet delay variation

Min
Packets Corrupted The corrupted packets (%)

Packets Duplicated The duplicated packets (%)

Packets Lost The lost packets (%)

Packets Out Of Order The out of order packets (%)

RTT (Average) The average RTT
RTT (Maximum) The maximum RTT
RTT (Minimum) The minimum RTT
More
KNOWLEDGE BASE
How can I monitor QoS round trips without using remote probes?
How does PRTG calculate the MOS score for QoS sensors?
1688
What connection settings are necessary for the QoS (Quality of Service) Round Trip sensor?

PAESSLER WEBSITE

1689
7.8.146 RADIUS v2 Sensor
The RADIUS v2 sensor monitors a Remote Authentication Dial-In User Service (RADIUS) server
according to RFC 2865.
The sensor tries to authenticate itself against the server. If authentication fails, the sensor shows the
Down status.
RADIUS v2 Sensor
List 1694 .

§ Dutch: RADIUS v2
§ French: RADIUS v2
§ German: RADIUS v2
§ Japanese: RADIUS V2
§ Portuguese: RADIUS v2
§ Russian: RADIUS v2
§ Simplified Chinese: RADIUS v2
§ Spanish: RADIUS v2
Remarks
1690
Remark Description

does PRTG require?
Plain text authentication § This sensor only supports plain text authentication (Password
Authentication Protocol (PAP)).
channels.
you add the sensor:
§ radiussensor
1691
RADIUS Specific
RADIUS Specific
1692
Setting Description
User Name Enter the user name for the authentication against the RADIUS server.
Enter a string.
Password Enter the password for the authentication between the client (the probe
system) and the RADIUS server. Enter a string.
Shared Secret Enter the shared secret for the authentication between the authenticator
(the probe system) and the RADIUS server. Enter a string.
Port Enter the number of the port for the connection to the RADIUS server. The
default value is 1812. Enter an integer.
NAS Identification Define how to identify the network access server (NAS):
§ Use NAS IP address (default): Enter the NAS IP Address for
identification below.
§ Use NAS identifier: Enter the NAS Identifier below.
NAS IP Address This setting is only visible if you select Use NAS IP address (default)
above.
Enter a valid IP address for the NAS that originates the access request.
NAS Identifier This setting is only visible if you select Use NAS identifier above.
Enter an identifier for the NAS that originates the access request.
scanning interval.
master node.
1693
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
1694
Channel Description
RADIUS Code The RADIUS code
§ Up status: Accept-Accept
§ Warning status: Access-Challenge
§ Down status: Access-Reject
More
KNOWLEDGE BASE


1695
7.8.147 RDP (Remote Desktop) Sensor
The RDP (Remote Desktop) sensor monitors remote desktop services such as Remote Desktop
Protocol (RDP) or Terminal Services Client.
RDP (Remote Desktop) Sensor
List 1699 .

§ Dutch: RDP (Remote Desktop)
§ French: RDP (Bureau à distance)
§ German: RDP (Remotedesktop)
§ Japanese: RDP( )
§ Portuguese: RDP (desktop remoto)
§ Russian: RDP )
§ Simplified Chinese: RDP ( )
§ Spanish: RDP (escritorio remoto)
Remarks
1696
Remark Description
you add the sensor:
§ rdpsensor
Sensor Specific
Sensor Specific
Setting Description
integer. The default value is 3389.
1697
Setting Description
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
1698
Channel List
Channel Description

More
KNOWLEDGE BASE


1699
7.8.148 Redfish Power Supply Sensor
The Redfish Power Supply sensor monitors the power supply of a Redfish Scalable Platforms
Management API (Redfish)-capable server.
Redfish Pow er Supply Sensor
List 1704 .

§ Dutch: Redfish Voeding
§ French: Redfish alimentation
§ German: Redfish Stromversorgung
§ Japanese: Redfish
§ Portuguese: Fonte de alimentação Redfish
§ Russian: Redfish
§ Simplified Chinese: Redfish
§ Spanish: Suministro de alimentación Redfish
1700
Remarks
Remark Description
Credentials § This sensor requires credentials for Redfish in settings that are higher
in the object hierarchy.
channels.
Redfish support § Supporters of the Redfish standard include Dell, Eaton, Emerson,
Fujitsu, HPE, Intel, Lenovo, NetApp, Supermicro, and VMware.
you add the sensor:
§ powersupply
§ redfish
1701
Redfish Specific
Redfish Specific
The information in the Redfish Specific settings reflects the status of the system at the time of
sensor creation. If any setting changes after creation, the Redfish Specific settings do not reflect the
change. Add the sensor anew to update the displayed settings.
Setting Description
Name The name of the power supply that this sensor monitors.
Model The model of the power supply that this sensor monitors.
Manufacturer The manufacturer of the power supply that this sensor monitors.
Serial Number The serial number of the power supply that this sensor monitors.
Sensor Display
Sensor Display
Setting Description
1702
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
1703
Inherited Settings
Channel List
Channel Description
Input Voltage The input voltage
Input Watts The input watts
Output Load The output load

Output Watts The output watts
Power Efficiency The power efficiency
Power Supply Status The power supply status

§ Up status: OK
§ Down status: Critical
§ Unknown status: Offline / Absent
1704
More
KNOWLEDGE BASE
I want to know which of my systems support the PRTG Redfish sensors. Can you help me?
1705
7.8.149 Redfish System Health Sensor
The Redfish System Health sensor monitors the system health of a Redfish Scalable Platforms
Management API (Redfish)-capable server.
Redfish System Health Sensor
List 1710 .

§ Dutch: Redfish Systeemstatus
§ French: Redfish état du système
§ German: Redfish Systemzustand
§ Portuguese: Saúde do sistema Redfish
§ Russian: Redfish
1706
§ Spanish: Salud del sistema Redfish
Remarks
Remark Description
Read permissions § This sensor requires at least read permissions for the target system.
Without sufficient permissions to a subsystem, the sensor will show
the Down status.
Supermicro § If you want to monitor Supermicro, then this sensor requires full
administrator access.
channels.
you add the sensor:
§ redfish
1707
§ restsensor
Redfish Specific
Redfish Specific
Setting Description
Name The name of the system that this sensor monitors.
Model The model of the system that this sensor monitors.
Manufacturer The manufacturer of the system that this sensor monitors.
Serial Number The serial number of the system that this sensor monitors.
Asset Tag The asset tag of the system that this sensor monitors.
Sensor Display
Sensor Display
1708
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
1709
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Chassis Status The chassis status

§ Up status: OK
Drives Status The drives status

§ Up status: OK
Fans Status The fans status

§ Up status: OK
1710
Channel Description
Memory Status The memory status
§ Up status: OK
PCIe Devices Status The PCIe drives status

§ Up status: OK
Power Supplies Status The power supplies status

§ Up status: Off, On, Powering Off, Powering On
Processor Status The processor status

§ Up status: OK
System Power Status The system power status

§ Up status: OK
System Status The system status

§ Up status: OK
1711
Channel Description
Thermal Status The thermal status

§ Up status: OK
More
KNOWLEDGE BASE

1712
7.8.150 Redfish Virtual Disk Sensor
The Redfish Virtual Disk sensor monitors the virtual disk of a Redfish Scalable Platforms Management
API (Redfish)-capable server.
Redfish Virtual Disk Sensor
List 1717 .

§ Dutch: Redfish Virtuele Schijf
§ French: Redfish disque virtuel
§ German: Redfish Virtueller Datenträger
§ Portuguese: Disco físico Redfish
§ Russian: Redfish
§ Spanish: Disco virtual Redfish
1713
Remarks
Remark Description
channels.
Knowledge Base § Knowledge Base: I want to know which of my systems support the
PRTG Redfish sensors. Can you help me?
you add the sensor:
§ logicaldisk
§ redfish
§ virtualdisk
§ virtualvolume
1714
Redfish Specific
Redfish Specific
Setting Description
Virtual Disk Name The name of the virtual disk that this sensor monitors.
Capacity The capacity of the virtual disk that this sensor monitors.
RAID Level The RAID level of the virtual disk that this sensor monitors.
Physical Disks Count The number of physical disks connected to the virtual disk that this
sensor monitors.
System Name The name of the system that the virtual disk belongs to.
Sensor Display
Sensor Display
1715
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
1716
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Capacity The capacity of the virtual disk
Physical Disks "Critical" The number of physical disks in the critical status
Physical Disks "Offline" The number of physical disks in the offline status
Physical Disks "OK" The number of physical disks in the OK status
Physical Disks The number of physical disks in the warning status

"Warning"
1717
Channel Description
Virtual Disk Status The virtual disk status

§ Up status: OK
More
KNOWLEDGE BASE

1718
7.8.151 REST Custom Sensor
The REST Custom sensor queries a Representational State Transfer (REST) application programming
interface (API) endpoint and maps the JavaScript Object Notation (JSON) or Extensible Markup
Language (XML) result to sensor values.
The mapping rule must be available as a REST configuration file in JSON template (*.template)
format according to the PRTG API definition for custom sensors.
REST Custom Sensor
List 1737 .

§ Dutch: REST Aangepast
§ French: REST personnalisé
§ German: REST (Benutzerdef.)
§ Japanese: REST
§ Portuguese: REST (customizado)
1719
§ Russian: REST
§ Simplified Chinese: REST
§ Spanish: REST (personalizado)
Remarks
Remark Description
File storage § The sensor requires that you store the REST configuration file that
contains the mapping rules on the probe system. In a cluster, copy the
file to every cluster node.
Channels § This sensor does not officially support more than 50 channels. If there
are more than 50 channel mappings in the REST configuration file, the
sensor shows an error.
Cluster § In a cluster, status changes triggered by limits only work on the master
node.
probe device.
you add the sensor:
§ restcustomsensor
§ restsensor
1720
REST Specific
REST Specific
Setting Description
the REST API:
§ GET (default): Use the GET method to request the REST API.
§ POST: Use the POST method to request the REST API.
If you use the POST method, use the content type, for example
application/x-www-form-urlencoded, as HTTP header. In section
HTTP Headers, select Send custom HTTP headers and enter the content
type in the Custom HTTP Headers field.

If you use the POST method, use the content type, for example
application/x-www-form-urlencoded, as HTTP header. In section
HTTP Headers, select Send custom HTTP headers and enter the content
type in the Custom HTTP Headers field.
Request Protocol Define the security protocol of the HTTP request:

§ HTTP (default): Send the REST query via HTTP (not secure).
1721
Setting Description
§ HTTPS: Send the REST query via secure HTTPS.
Certificate Acceptance This setting is only visible if you select HTTPS above.
Select the kind of certificates that you want the sensor to accept for the
connection:
§ Accept trusted certificates only (default): Accept only trusted
certificates issued by a certificate authority (CA).
§ Accept all certificates: Accept all certificates, including self-signed
certificates.
Authentication Method Select the authentication method for access to the REST API:
§ No authentication (default): Do not use any authentication for the
request.
§ Basic authentication: Use a user name and password for
authentication.
§ Basic authentication with Windows credentials from parent device: Use
the Windows credentials from the parent device.
§ Token: Use a JSON Web Token (JWT) or OAuth2 Bearer Token for
authentication.
Enter a user name for the REST API. Enter a string.
Enter a password for the REST API. Enter a string.
Token This setting is only visible if you select Token above.
Enter a JWT or OAuth2 Bearer Token that the REST API requires for
authentication.
§ Do not send custom HTTP headers
§ Send custom HTTP headers
Custom HTTP Headers This setting is only visible if you select Send custom HTTP headers
above.
1722
Setting Description
Enter a list of custom HTTP headers with their respective values that you
want to transmit to the target URL, each pair in one line. The syntax of a
header-value pair is header1:value1.
If you enter more than one header-value pair, you must separate
them with delimiters. The syntax is header1:value1|header2:value2|
header3:value3
content-length, host.
If you select the POST as Request Method setting above, enter the
content type, for example application/x-www-form-urlencoded, as the
custom HTTP header.
REST Query The REST query that this sensor executes. To change it, enter a valid
query for the target REST API. The syntax is: [:port]/path[?var1=val1&...]
The sensor always inherits the first part of the address from the
address of the parent device. Only enter the path to the REST
endpoint of the parent device. You can override the port if necessary.
For example, if you add the sensor to a probe device, a query to the
REST API of your PRTG installation that returns the number of sensors
on the probe could look like this:
/api/table.json?
id=1&passhash=<passhash>&username=<username>&content=sensorx
ref&noraw=1&filter_basetype=probe&columns=totalsens=textraw
REST Configuration Select a REST configuration file from the list. The sensor uses it to map
the JSON or XML result from the REST query to sensor values.
The default REST configuration file is channelDiscovery. If you select this
file, the sensor parses the returned JSON or XML and automatically
creates channels based on available values: one channel for each number
and boolean for strings if they are convertible into numbers.
This list shows all REST configuration files that are available in the
\Custom Sensors\rest subfolder of the PRTG program directory on the
probe system. For the files to appear in this list, store the files as JSON
template (*.template) in this subfolder.
1723
Setting Description
To use custom REST configurations in PRTG Hosted Monitor,

contact the Paessler support team, or add this sensor to a remote
probe instead and save the file on the remote probe system.
To show the expected values and sensor status, your files must
return the expected JSON format. Channels, values, and messages
must be embedded in valid JSON using JSONPath. For more information,
see section Define Channels and Select Channel Values 1725 .
every cluster node.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
1724
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Define Channels and Select Channel Values

In your REST configuration file, you must define which values of the returned JSON or XML are mapped
to which channels.
1725
§ A channel is defined by the channel key in your REST configuration. See the JSON Return Format:
Minimum Example in section Custom Sensors.
§ A channel value is defined by an expression that retrieves and processes the value from the JSON
source. The expression can contain JSONPath 1727 , gval operators 1731 , and functions 1733 .
Example
For this example, we take PRTG as REST endpoint and query the sensor status statistics for the
local probe. The REST query that we enter in the sensor settings looks like this:
/api/table.json?id=1&passhash=<passhash>&username=<username>&content=sensorxref&
noraw=1&filter_basetype=probe&columns=totalsens=textraw,upsens=textraw,
downsens=textraw,partialdownsens=textraw,warnsens=textraw,pausedsens=textraw,
unusualsens=textraw,undefinedsens=textraw,downacksens=textraw
This REST query returns some JSON, for example:

{
"prtg-version": "17.3.33.2517",
"treesize": 1,
"state": "ok",
"sensorxref": [
{
"totalsens": 28,
"upsens": 18,
"downsens": 0,
"partialdownsens": 0,
"warnsens": 0,
"pausedsens": 9,
"unusualsens": 1,
"undefinedsens": 0,
"downacksens": 0
}
]
}
Your REST configuration has to translate this JSON for the sensor. It has to be available as JSON
template (*template) in the \Custom Sensors\rest subfolder of the PRTG program directory on the
probe system. See section Custom Sensors for details about the JSON return format.
The following example returns two channels from the JSON resource that are added to the sensor in
PRTG, Total (total sensor count) and Alarms (sensors in the Down status), each selected by their
keys in the returned JSON.
1726
{
"prtg": {
"result": [
{
"channel": "Total" ,
"value": $.sensorxref[0].totalsens
},
{
"channel": "Alarms" ,
"value": $.sensorxref[0].downsens
}
]
}
}
The channel values are the values of the corresponding properties of the REST result defined in
JSONPath notation, $.sensorxref[0].totalsens (28) and $.sensorxref[0].downsens (0).
Each value's property (destination) and the text property is set to the appropriate transformation rules
from source to destination. This is the JSON path of the source. The sensor replaces each path with
the value from the source.
Several REST configuration files are available in the \Custom Sensors\rest subfolder by default. They
are ready for use. You can also analyze them to see how to write your own REST configuration.
JSONPath
The REST Custom sensor uses JSONPath to assign values from the returned JSON to channels. With
JSONPath, you provide the path to the value in the JSON source that you want to monitor in a channel.
The JSONPath implementation that PRTG uses for the REST Custom sensor might differ from other
JSONPath implementations. You can test and debug your definitions 1735 using the command line.
To test simple JSONPath expressions and calculations, you can also use JSONPath Online
Evaluator 1737 , for example. Note that this tool might not work properly with complex JSONPath
expressions that PRTG supports.
Example
To demonstrate the practical usage of JSONPath, we use this JSON example that a REST query
might have returned as reference in this section.
1727
{
"devices":[
{
"firmware":{
"id":"0.7",
"date":"2017-05-18T17:11:43.7049944Z",
"channel": "beta"
},
"networks": {
"a": {
"rx_bytes": 35985021,
"rx_packets": 176791,
"rx_errors": 0,
"rx_dropped": 476,
"tx_bytes": 7229493,
"tx_packets": 35518,
"tx_errors": 0,
"tx_dropped": 1
},
"b": {
"rx_bytes": 40085321,
"tx_bytes": 55294975
}
}
},
{
"networks": {
"a": {
"rx_bytes": 63685865,
"tx_bytes": 7229472
}
}
}
]
}
REST Custom Sensor: JSONPath
Root The dollar sign ($) matches the root element of the JSON data.
1728
Child You can match a child with .<key> or [<key>].

§ .<key> must only contain letters, numbers, and underscore (_).
Hyphens (-) are not supported.
§ [<key>] must only contain a number or a quoted string.
Example
This expression matches 35985021 in the example above:

$.devices.0.networks.a.rx_bytes
You get the same result with this expression:

$["devices"][0]["networks"]["a"]["rx_bytes"]
If an element contains a hyphen (-), the .<key> notation does not work.
Use the [<key>] notation in this case:
$["data"][0]["system-stats"]["temps"]["Board (CPU)"]
Wildcard To match multiple values, you can use the asterisk symbol (*).
§ .*
§ [*]
Example
This expression matches 35985021 and 40085321 in the example above:

$.devices[0].networks.*.rx_bytes
Recursive Descent You can match all subitems of a node with two dots (..).
Example
This expression matches 7229493 and 55294975 and 7229472 in the

example above:
$..tx_bytes
Union You can match multiple children with [<key1>,<key2>,<...>].
Example

$.devices.0.networks.a["rx_bytes","tx_bytes"]
Slice You can match multiple children of an array with [<begin>:<end>] or

[<begin>:<end>:<step>].
§ By default, begin, end, and step are either integers or empty.
1729
§ The default approach is to go step by step from the first array element
to the last element.
§ Step can also be a negative integer to go through the array in reversed
order.
Example

$.devices[-1:].networks.a.rx_bytes
Current The @ symbol matches the current element.
Example
This expression matches 40.085321 and 55.294975 in the example above

and can be used to receive a percentage value:
$.devices[1].networks.a.["rx_bytes","tx_bytes"]
(@/100000000*100)
Filter You can filter matches with [?<expression>].
Example
This expression matches 35985021 in the example above because the

first device is the only one with a beta channel:
$.devices[?@.firmware.channel=="beta"].networks.a.rx_bytes
Script You can modify matches with (<expression>) and keys with
[<expression>].
Example
This expression matches true and false in the example above because
only the first device has a beta channel:
$.devices[*](@.firmware.channel=="beta")
Placeholder Placeholders give access to values of wildcards in a match. A placeholder

#n (where n is a natural number) represents the value of the nth wildcard.
You can use this in the keys of JSON arrays.
Example
This expression creates a JSON map from ids to the corresponding

firmware channel and matches {"0.7":"beta"} in the example above:
{$.devices[#0].id:$.devices[*].channel}
This is an extension of the official JSONPath.
1730
Constant § Numeric constants as 64-bit floating point: 12345.678
§ String constants with double quotation marks ("): "switch"
§ Boolean constants: true and false
Operator § Parentheses control the order of evaluation: (<expression>)
§ Arrays with brackets: [<expression>, <expression>, ...]
§ Objects: {<expression>:<expression>, <expression>:<expression>, ...}
§ Conditionals: <condition> ? <expression> : <expression>
Calculating Channel Values and Functions

You can perform calculations with the values of the source JSON or XML. The sensor uses the Paessler
gval package for the calculations. For more information, refer to the gval documentation 1737 .
The following operators and functions are available to calculate channel values.
REST Custom Sensor: Operators
Operator Description Operand Type Output Type
Infix + plus number number

Modifiers
- minus number number
* times number number
** power of number number
% modulo number number
/ divide number number
& bitwise and number number
| bitwise or number number
^ bitwise xor number number
1731
<< shift left number number
>> shift right number number
Logical Infix > greater than number/string bool

Operators
>= equal or number/string bool

greater than
< less than number/string bool
<= equal or less number/string bool

than
== equal any bool
!= not equal any bool
=~ match regular string bool

expression
!~ mismatch string bool

regular
expression
in contains any, array bool

element
&& and and bool
|| or or bool
?? coalescence any any
Prefix - negative number number

Operators
~ bitwise not number number
1732
! not bool bool
REST Custom Sensor: Functions
duration(start,end) § Calculates the nanoseconds between start and end.
§ Both parameters must be RFC3339 date time strings.
Example
duration($.devices[0].firmware.date, "017-05-
18T17:11:43.7049944Z")
now() § Returns the current date time in RFC3339.
Example
duration($.devices[0].firmware.date, now())
number(string, [base]) § Converts a string to a floating point number.
§ If the base is not set, it is detected via the prefix of the string.
ú "0": base = 8
ú "0X": base = 16
ú otherwise: base = 10
ú Decimals are only supported at base 10.
Examples
number("10.5")
number("a", 16)
len(object/array/string) § Returns the length of an array or string and counts the number of
properties in a JSON object.
Example
len($..(number(@)))
This expression counts every number or string that can be converted into
a number. It returns 13 in the example above.
sum(array-/object-of- § Returns the sum of an array of numbers.

numbers)
Example
1733
REST Custom Sensor: Functions
sum([1,2,3])
This expression returns 6.
mean(array-/object-of- § Returns the average value of an array of numbers.

numbers)
Example
mean([1,2,3])
This expression returns 2.
lookup(string, string, § Returns the index of the specified string in a string list, or -1 if the string
string, ...) is not found.
Example
lookup($.device[0].firmware.channel, "stable", "beta",
"alpha")
This expression returns 1 because $.device[0].firmware.channel resolves

to beta.
implode(array-/object-of- § Returns the concatenation of each string in the array, separated by the
string, string) specified string.
Example
implode($..tx_bytes, ",")
This expression returns 7229493,7229472.
Generic Channels
You can create a template in your REST configuration that defines generic channels. Generic channels
are created based on the data that the REST endpoint returns. When the returned value is an array or
object, the sensor creates a channel for each element and concatenates the corresponding key to the
channel name.
Example
Imagine that you want to have a total byte channel for each network card that is defined in the JSON
example above. You can do this by creating a dynamic channel like in the following example.
1734
{
"prtg": {
"result":[
{
"value": {
"Total bytes on device" + #0 + " in network " + #1: $.devices.*.networks[*]
(@.rx_bytes + @.tx_bytes)
},
"CustomUnit": "Bytes"
}
]
}
}
Every channel must have a unique name. You cannot remove channels once they have been added
and they keep their last received value. You can add new channels.
XML Sources
If the REST source returns XML instead of JSON, the sensor transforms the XML result to JSON before
replacing the value paths with source values. Because of this, you do not know the structure of the
source JSON to correctly provide the paths.
In this case, manually execute the sensor executable rest.exe from the \Sensor System subfolder of the
PRTG program directory on the probe system. Execute rest.exe with the address of the XML endpoint
and the parameter passthrough. The rest executable returns the converted XML to a JSON result that
you can use to define the desired paths.
rest.exe <xml-endpoint-url> passthrough
Usage and Debugging

To create a suitable REST configuration for the sensor, you might want to check the returned JSON or
XML and see what happens when your mapping rules apply.
The REST Custom sensor is an EXE sensor, so you can test and debug your configuration by executing
rest.exe with several parameters. The rest.exe file is located in the \Sensor System subfolder of the
PRTG program directory.
The command syntax is as follows:

rest.exe url template|passthrough|channelDiscovery [flags]
rest.exe: Parameters
url § Address of the REST API endpoint that returns JSON or XML
1735
rest.exe: Parameters
template § Fully qualified path and file name of your REST configuration file used
to map the JSON result to the sensor
passthrough § No mapping, only returning the queried JSON or XML
§ Useful to analyze XML that has been converted to JSON
channelDiscovery § Creates a channel for every number or boolean in the returned JSON or
XML
§ If possible, it converts string values to number or boolean values.
rest.exe: Flags
-authtoken <string> § JWT or OAuth2 Bearer Token to send with the request in authorization
header as Bearer
-authusername <string> § User name for basic authentication
-authuserpwd <string> § User password for basic authentication
-customheaders <string> § key1:val1|key2:val2|...
-post=<int> § {1|0}
§ Default: 0
§ 0 results in a GET request.
§ 1 results in a POST request.
Example
-customheaders 'Content-Type: application/x-www-form-
urlencoded' -post=1 -requestbody 'myvar=value'
-proxy <string> § Proxy server connection
-proxyusername <string> § Proxy user name with basic authentication
-proxyuserpwd <string> § Proxy user password with basic authentication
-requestbody <string> § Body of the request
1736
rest.exe: Flags
You can only use this flag a POST request (-post=1).
Example
-customheaders 'Content-Type: application/x-www-form-
urlencoded' -post=1 -requestbody 'myvar=value'
-timeout <integer> § Sensor timeout in seconds
§ Default: 10
-tlsignore=<int> § {1|0}
§ Default: 0
§ 1 accepts self-signed certificates on HTTPS connections
-template § Returns the discovered template if you use channelDiscovery.
Channel List
Channel Description

[Value] The values that a REST API returns in several channels

Custom Sensors.
More
PRTG MANUAL
§ Data Storage
1737
KNOWLEDGE BASE

Can I create a sensor to monitor the number of paused or unknown sensors?

MISCELLANEOUS
Paessler JSONPath
§ https://github.com/PaesslerAG/jsonpath
Paessler Gval
§ https://github.com/PaesslerAG/gval
JSONPath Online Evaluator

§ https://jsonpath.com/
1738
7.8.152 REST Custom v2 Sensor (BETA)
The REST Custom v2 sensor queries a JavaScript Object Notation (JSON) or Extensible Markup
Language (XML) Representational State Transfer (REST) application programming interface (API)
endpoint and maps the JSON or XML result to sensor values.
all.
REST Custom v2 Sensor
List 1758 .

§ Dutch: REST Aangepast v2
§ French: REST personnalisé v2
§ German: REST (Benutzerdefiniert) v2
§ Japanese: REST v2
§ Portuguese: REST (customizado) v2
§ Russian: REST v2
§ Simplified Chinese: REST v2
§ Spanish: REST (personalizado) v2
Remarks
1739
Remark Description
JSONPath and XPath § This sensor supports JSONPath and XPath 1.0.
version
channels.
Credentials § You can define credentials for REST API in settings that are higher in
the object hierarchy.
Known Issues
§ When you add more channels to the sensor, the fields Channel #x Unit and Channel #x Custom Unit
remain visible regardless of what you select as Channel #x Value Type. You can ignore these fields if
you select Status (string) or Lookup as Channel #x Value Type.
Limitations
§ Strings that contain angled brackets (< and >) cannot be mapped manually. This affects the following
settings: Channel #x Strings mapped to the 'Up' status, Channel #x Strings mapped to the 'Warning'
status, and Channel #x Strings mapped to the 'Down' status. We are already working on a solution.
Add Sensor
Setting Description
1740
Setting Description
Channel #x Enter the JSONPath or XPath of the JSON or XML result that you want to
JSONPath/XPath monitor.
JSONPath example:
$.store.book[0].year
XPath example:
/store/book[1]/year
Channel #x Name Enter a name for the channel. Enter a string. For example, Total.
Channel #x Unit Enter the unit for the value that this sensor monitors. For example, #.
sensor.
you add the sensor:
§ rest
1741
REST Specific
REST Specific
Setting Description
Request URL Enter the URL of the JSON or XML REST API endpoint that you want to
request.
Example URL:
https://:1616/api/health?token=%restbearertoken&name=%
restusername&refresh=true
You can use the following placeholders in this field: %restusername,

%restpassword, %restbearertoken, %restplaceholder1, %
restplaceholder2, %restplaceholder3, %restplaceholder4, and %
restplaceholder5. You can define these placeholders in the
credentials for REST API in settings that are higher in the object
hierarchy.
Replacement 1758 .
If you enter 127.0.0.1 as IP address of the parent device, PRTG
requests the following URL:
https://127.0.0.1:1616/api/health?token=%
restbearertoken&name=%restusername&refresh=true
Request Method Select the HTTP request method that the sensor uses to request the
REST API:
§ GET (default): Use the GET method to request the REST API.
§ POST: Use the POST method to request the REST API.
1742
Setting Description
POST Body This setting is only visible if you select POST above.

hierarchy.
Custom Headers Enter a list of custom HTTP headers with their respective values that you
want to transmit to the target URL. The syntax of a header-value pair is
header1:value1.
Custom header example:
host:host1.example.com
User-Agent:PRTG sensor 0.1
X-API-Key: %restplaceholder1
If you enter more than one header-value pair, enter each pair in one
line:
header1:value1
header2:value2
header3:value3
hierarchy.
Content Type Select the type of the content that the sensor queries:
§ JSON (default)
§ XML
Custom Sensor Message Enter the JSONPath or XPath from which you want to receive a string that
the sensor shows as the permanent sensor message.
1743
Setting Description
JSONPath example:
$.store.book[0].title
XPath example:
/store/book[1]/title
Channel Settings
Channel Settings
Setting Description
Channel #x Enter the JSONPath or XPath of the JSON or XML result that you want to
JSONPath/XPath monitor.
JSONPath example:
$.store.book[0].year
XPath example:
/store/book[1]/year
Channel #x Name Enter a name for the channel. Enter a string. For example, Total. PRTG
dynamically generates channels with this name as the identifier.
Channel #x Value Type Select the value type that the channel displays:
§ Absolute (integer): Integer64 values with or without an operational sign,
such as 10 or 120 or -12 or 120.
§ Absolute (float): Double values, such as -5.80 or 8.23.
If you select Absolute (float), the sensor automatically shows all
decimal places of the received value in the channel. You can define
how many decimal places of the channel's data that you want to
display in graphs and tables in the channel settings.
1744
Setting Description
§ Delta (counter): Counter values. The sensor calculates the difference

between the last and the current value. Enter an integer. The sensor
additionally divides the delta value by a time period to indicate a speed
value.
§ Status (string): The sensor shows a status depending on how you map
the returned strings and shows the returned strings as sensor
message.
§ Lookup: The sensors shows a status depending on how you define
values in a custom lookup file.
Absolute (integer) and Absolute (float) support the extraction of
numerical values from a received string. The sensor parses the
numerical value from the beginning of the string until it encounters the first
element that is not part of a numerical value, for example a letter. The
sensor ignores whitespace characters.
Channel #x Unit This setting is only visible if you select Absolute (integer), Absolute
(float), or Delta (counter) as Channel #x Value Type.
Select the unit that the channel displays:

§ Custom (default)
§ Percent
§ Percent (CPU)
§ Temperature (celsius)
§ Time (milliseconds)
§ Time (hours)
§ Time (seconds)
§ Bytes (memory)
§ Bytes (disk)
§ Bytes (file)
§ Bytes (bandwidth)
§ Bytes per second (disk)
§ Bytes per second (network)
1745
Setting Description
Channel #x Custom Unit This setting is only visible if you select Custom (default) as Channel #x
Unit.
Enter the custom unit of the value of this channel. Enter a string.
Channel #x Strings This setting is only visible if you select Status (string) as Channel #x
mapped to the 'Up' status Value Type.
Enter the strings that the sensor maps to the Up status in a comma-
separated list.
If a string contains a comma, you must put the string in quotation

marks. For example, to map the string Friday,2nd enter "Friday,2nd".
If a string contains quotation marks, you must escape the quotation
marks using a backslash (\) and put the string in quotation marks. For
example, to map the string Friday "2nd" enter "Friday \"2nd\"".
mapped to the 'Warning' Value Type.
status
Enter the strings that the sensor maps to the Warning status in a
comma-separated list.
mapped to the 'Down' Value Type.
status
Enter the strings that the sensor maps to the Down status in a comma-
separated list.
Channel #x Handling of This setting is only visible if you select Status (string) as Channel #x
Unknown Strings Value Type.
Select the status to which the sensor maps all unknown strings in the
returned result that are not manually mapped to the Up, the Warning, or
the Down status:
§ 'Up' status: Map all unknown strings to the Up status.
1746
Setting Description
§ 'Warning' status: Map all unknown strings to the Warning status.
§ 'Down' status (default): Map all unknown strings to the Down status.
Channel #x Lookup ID This setting is only visible if you select Lookup as Channel #x Value
Type.
Enter the ID of the lookup you wish to use. You can find the ID in the
ValueLookup parameter in the lookup file.
For more information, see section Define Lookups.
Sensor Display
Sensor Display
Setting Description

1747
Setting Description

other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
1748
JSONPath
The REST Custom v2 sensor uses JSONPath to assign values from the returned JSON to channels.
With JSONPath, you provide the path to the value in the JSON source that you want to monitor in a
channel.
The JSONPath implementation that PRTG uses for the REST Custom v2 sensor might differ from
other JSONPath implementations. To test simple JSONPath expressions and calculations, you can
use JSONPath Online Evaluator - jsonpath.com, for example. Note that this tool might not work
properly with complex JSONPath expressions that PRTG supports.
1749
Example
To demonstrate the practical usage of JSONPath, we use this JSON example that a REST query
might have returned as reference in this section.
{
"devices":[
{
"firmware":{
"id":"0.7",
"date":"2017-05-18T17:11:43.7049944Z",
"channel": "beta"
},
"networks": {
"a": {
"rx_bytes": 35985021,
"rx_packets": 176791,
"rx_errors": 0,
"rx_dropped": 476,
"tx_bytes": 7229493,
"tx_packets": 35518,
"tx_errors": 0,
"tx_dropped": 1
},
"b": {
"rx_bytes": 40085321,
"tx_bytes": 55294975
}
}
},
{
"networks": {
"a": {
"rx_bytes": 63685865,
"tx_bytes": 7229472
}
}
}
]
}
1750
REST Custom v2 Sensor: JSONPath
Root The dollar sign ($) matches the root element of the JSON data.
Child You can match a child with .<key> or [<key>].

§ .<key> must only contain letters, numbers, and underscore (_).
Hyphens (-) must be escaped with quotation marks.
Example

$.devices.0.networks.a.rx_bytes
You get the same result with this expression:

$["devices"][0]["networks"]["a"]["rx_bytes"]
If an element contains a hyphen (-), the .<key> notation does not work.
Use the [<key>] notation in this case:
$["data"][0]["system-stats"]["temps"]["Board (CPU)"]
§ .*
§ [*]
Example

$.devices[0].networks.*.rx_bytes
Recursive Descent You can match all subitems of a node with two dots (..).
Example

example above:
$..tx_bytes
Union You can match multiple children with [<key1>,<key2>,<...>].
Example

$.devices.0.networks.a["rx_bytes","tx_bytes"]
Slice You can match multiple children of an array with [<begin>:<end>] or

[<begin>:<end>:<step>].
1751
REST Custom v2 Sensor: JSONPath
§ By default, begin, end, and step are either integers or empty.
§ The default approach is to go step by step from the first array element
to the last element.
§ Step can also be a negative integer to go through the array in reversed
order.
Example

$.devices[-1:].networks.a[rx_bytes,tx_bytes]
Current The @ symbol matches the current element.
Example

$.devices[(@.length-1)].networks.a.rx_bytes
Filter You can filter matches with [?<expression>].
Example

$.devices[?(@.firmware.channel=="beta")].networks.a.rx_bytes

If the JSONPath points to a boolean, the sensor translates true as
1 and false as 0.
Functions You can use functions on top level or in filters.

This expression returns the number items in the element devices in the
example above:
length($.devices)
For more information about functions, see JsonCons JSONPath |

Functions.
§ Arrays with brackets: [<expression>, <expression>, ...]
§ Objects: {<expression>:<expression>, <expression>:<expression>, ...}
1752
For more information about JSONPath, see JsonCons JSONPath.
1753
REST Custom v2 Sensor: XPath
Example
To demonstrate the practical usage of XPath, we use this XML example that a REST query might
have returned as reference in this section.
<?xml version="1.0" encoding="UTF-8" ?>
<root>
<devices>
<firmware>
<id type="major">0</id>
<id type="minor">7</id>
<date>2017-05-18T17:11:43.7049944Z</date>
<channel>beta</channel>
</firmware>
<networks>
<a>
<rx_bytes>35985021</rx_bytes>
<rx_packets>176791</rx_packets>
<rx_errors>0</rx_errors>
<rx_dropped>476</rx_dropped>
<tx_bytes>7229493</tx_bytes>
<tx_packets>35518</tx_packets>
<tx_errors>0</tx_errors>
<tx_dropped>1</tx_dropped>
</a>


</networks>
</devices>
<devices>
<networks>
<a>
</a>
</networks>
</devices>
</root>
1754
Root The slash symbol (/) matches the root element of the XML data.
Child You can match a child by its name with /<key> or [<key>] or by its index
with [<index>].
§ /<key> must only contain letters, numbers, and underscore (_).
Hyphens (-) must be escaped with quotation marks.
§ [<index>] must only contain a number.
Example

/root/devices[1]/networks/a/rx_bytes
This expression matches major in the example above:

/root/devices[1]/firmware/id[1]/@type
§ /*
§ /@*
§ [*]
§ [@*]
Example

/root/devices[1]/networks/*/rx_bytes
Recursive Descent You can match all subitems of a node with two slashes (//).
Example

example above:
//tx_bytes
Union You can match multiple queries by combining them with the vertical bar
symbol (|).
Example

/root/devices[1]/networks/a/rx_bytes
| /root/devices[1]/networks/a/tx_bytes
1755
Filter You can filter matches with [<expression>].
Example

/root/devices[firmware/channel='beta']/networks/a/rx_bytes

/root/devices[1]/firmware[1]/id[@type='major']

If the XPath points to a boolean, the sensor translates true as 1
and false as 0.
Functions You can use functions on top level or in filters.

This expression returns the number of items in the devices element in the
example above:
count(/root/devices[position() < 3])
For more information about functions, see XML Path Language (Core
Function Library).
For more information about XPath, see XML Path Language (XPath).
Calculating Channel Values

The REST Custom v2 sensor supports the following arithmetic:
§ Addition (+)
§ Subtraction (-)
§ Multiplication (*)
§ Division (div, /)
§ Equal (=)
§ Not equal (!=)
1756
Examples
XML JSON
<root> {
<one>1</one> "root": {
<two value_int="2">2</two> "one": 1,
<two_point5>2.5</two_point5> "two": 2,
<four>4</four> "two_string": "2",
</root> "two_point5": 2.5,
"four": 4
}
}
XML JSON Description Resul Result (JSON)

t
(XML)
/root/one + /root/two eval($.root.one + Addition of the 3 3

$.root.two) numbers
n/a eval($.root.one + Addition of a n/a 3

to_number($.root.two_ number and a
string)) string
/root/one n/a Addition of a 3 n/a

+ /root/two/@value_int number and an
attribute value
/root/four div /root/two eval($.root.four / Division of two 2 2

$.root.two) integers. The
expected result is
an integer
/root/one div /root/two eval($.root.one / Division of two 0.5 0

$.root.two) integers, the
expected result is
a floating-point
number
1757
XML JSON Description Resul Result (JSON)
t
(XML)
n/a eval($.root.one / Division of two n/a 0.5

$.root.two * 1.0) integers with a
floating point
number as result
/root/one eval($.root.one / Division of a float 0.4 0.4

div /root/two_point5 $root.two_point5) and an integer
/root/one = /root/two eval($.root.one == If entries are equal 0 0 (false)

$.root.two) (false)

Instead of entering a complete address in the Request URL field of the REST Custom v2 sensor, you can
only enter the protocol followed by a colon and three forward slashes (this means that you can enter
either http:/// or https:///, or even a simple forward slash / as the equivalent for http:///). PRTG
automatically fills in the parent device's IP Address/DNS Name in front of the third forward slash.
For example, if you create a device with the DNS name www.example.com and you add a REST Custom
v2 sensor to it, you can provide values in the following ways:
§ If you enter https:/// in the Request URL field, PRTG automatically creates the URL
https://www.example.com/
§ If you enter /help in the Request URL field, PRTG automatically creates the URL
§ It is also possible to provide a port number in the Request URL field. It is taken over by the device's
DNS name and is internally added, for example, https://:1616/
Channel List
1758
Channel Description
HTTP Status The HTTP status that the requested URL returns
§ Up status: Continue, Switching Protocols, Processing, OK, Created,

Accepted, Non-Authoritative Information, No Content, Reset Content,
Partial Content, Multi-Status, Already Reported, IM Used
§ Warning status: Multiple Choices, Moved Permanently, Found, See
Other, Not Modified, Use Proxy, Switch Proxy (deprecated), Temporary
Redirect, Permanent Redirect,
§ Down status: Bad Request, Unauthorized, Payment Required,
Forbidden, Not Found, Method Not Allowed, Not Acceptable, Proxy
Authentication Required, Request Time-out, Conflict, Gone, Length
Required, Precondition Failed, Request Entity Too Large, Request URL
Too Long, Unsupported Media Type, Requested Range Not Satisfiable,
Expectation Failed, I'm a teapot, Policy Not Fulfilled, There are too
many connections from your internet address, Unprocessable Entity,
Locked, Failed Dependency, Unordered Collection, Upgrade Required,
Precondition Required, Too Many Requests, Request Header Fields
Too Large, No Response, The request should be retried after doing the
appropriate action, Unavailable For Legal Reasons, Internal Server
Error, Not Implemented, Bad Gateway, Service Unavailable, Gateway
Time-out, HTTP Version not supported, Variant Also Negotiates[13],
Insufficient Storage, Loop Detected, Bandwidth Limit Exceeded, Not
Extended
[Value] The values that a REST API returns in several channels
More
KNOWLEDGE BASE


Can I create a sensor to monitor the number of paused or unknown sensors?

1759
MISCELLANEOUS
JSONPath Online Evaluator

§ https://jsonpath.com/
JsonCons JSONPath
§ https://danielaparker.github.io/JsonCons.Net/articles/JsonPath/JsonConsJsonPath.html
Stefan Gössner JSONPath
§ https://goessner.net/articles/JsonPath/
1760
7.8.153 Script v2 Sensor (BETA)
The Script v2 sensor runs a Python script (.py) on the probe system.
The return result of this sensor must comply with the provided JavaScript Object Notation (JSON)
schema. For more information, see the Remarks 1762 below.
all.
Script v2 Sensor
List 1766 .

§ Dutch: Script v2
§ French: Script v2
§ German: Skript v2
§ Japanese: v2
§ Portuguese: Script v2
§ Russian: v2
§ Simplified Chinese: Script v2
1761
§ Spanish: Script v2
Remarks
Remark Description
Python § This sensor requires that Python is installed for the Windows user
account that the probe runs under.
File storage § This sensor requires that you store the script file on the probe system.
In a cluster, copy the file to every cluster node.
§ This sensor requires that the script file is stored in the \Custom
Sensors\scripts subfolder of the PRTG program directory of the probe
system on Windows systems or in the /opt/paessler/share/scripts
directory of the probe system on Linux systems.
Channel IDs § This sensor supports the channel IDs 10 to 2,147,483,647.
Channels § This sensor supports up to 50 channels.
Placeholders § You can define placeholders in credentials for script sensors settings
channels.
Parameters § This sensor invokes all scripts with the -E parameter as a security
measure. This parameter ignores all python* environmental variables
when starting the script.
Example scripts § This sensor comes with example scripts. For more information, see the
Knowledge Base: I want to use the Script v2 sensor example scripts.
What do I need to know?
1762
Remark Description
JSON schema § For more information about the JSON schema that this sensor uses,
see the Knowledge Base: Where can I find the JSON schema against
which the Script v2 sensor validates my script output?
probe device.
you add the sensor:
§ exesensor
Script Specific
Script Specific
1763
Setting Description
Name Select one or more Python scripts from the list. PRTG creates one
sensor for each script that you select. The sensor executes it with every
scanning interval 1766 .
This list shows all Python script files that are available in the \Custom
Sensors\scripts subfolder of the PRTG program directory of the probe
system on Windows systems or in the /opt/paessler/share/scripts
directory of the probe system on Linux systems. For the files to appear in
this list, store the files in this subfolder with the extension .py.
To show the expected values and sensor status, your scripts must
return the expected JSON format to standard output (stdout). The
Script v2 sensor validates the results that the script returns against
the provided JSON schema. For more information, see the
Knowledge Base: Where can I find the JSON schema against which the
Script v2 sensor validates my script output?.
every cluster node.
Type The type of the script file.
Script Settings
Script Settings
Setting Description
Parameters If your script file uses parameters, you can enter them here. You can use
placeholders as well. Enter a string or leave the field empty.
1764
Setting Description
You can define placeholders in the credentials for script sensors in

the settings of a parent object and use the %host and %sensorid
placeholders. The sensor replaces the parameters with their values and
passes them to the script as strings via stdin.
Sensor Display
Sensor Display
Setting Description

other above.
procedure to do so.
1765
Debug Options
Debug Options
Setting Description
If you select Store result, the sensor writes the standard error (stderr)
streams in clear text to the last sensor result file. Do not return
sensitive information via the scripts that you run with this sensor.
master node.
Inherited Settings
Channel List
Channel Description
Execution Time The execution time of the script
1766
Channel Description
Status The status that the script returns

§ Up status: OK
[Value] The values that the script file returns in several channels
More
KNOWLEDGE BASE

I want to use the Script v2 sensor example scripts. What do I need to know?
Where can I find the JSON schema against which the Script v2 sensor validates my script output?
1767
7.8.154 Sensor Factory Sensor
The Sensor Factory sensor monitors entire business processes that involve several components. You
can create a customized sensor with channels based on data from other sensors ("source sensors").
If you want to create only a cumulated sensor status based on specific source sensors, we
recommend that you use the Business Process 755 sensor.
Sensor Factory Sensor
List 1779 .

§ Dutch: Sensor Fabriek
§ French: Capteur combiné
§ German: Formelsensor
§ Japanese:
§ Portuguese: Sensor de fórmula
§ Russian:
§ Spanish: Sensor combinado
Remarks
1768
Remark Description
Performance impact § This sensor can have a very high impact on the performance of the
PRTG core server system. We recommend that you use no more than
50 of this sensor per PRTG core server.
Channel definitions § This sensor does not support channel definitions 1772 that refer to
channels of Sensor Factory sensors.
Reports § Uptime or downtime data for this sensor is not available in reports.
Scanning interval § Make sure that the scanning interval 1772 of this sensor is equal to or
greater than the scanning interval of the source sensors to avoid
incorrect sensor behavior. For example, "no data" messages or erratic
changes of the sensor state can be a result of an invalid scanning
interval.
Flow sensors § This sensor might not work with flow sensors. Sensors that use active
flow timeout, for example NetFlow and jFlow sensors, are not supported
by this sensor.
Knowledge Base § Knowledge Base: How can I monitor the overall status of the business
process "email"?
you add the sensor:
§ factorysensor
1769
Sensor Factory Specific Settings
Sensor Factory Specific Settings
Setting Description
Channel Definition Enter a channel definition for the Sensor Factory sensor. Using a specific
syntax, you can refer to data from channels of other sensors. You can
also calculate values. Enter one channel definition for each new channel
that you want to add to the Sensor Factory sensor.
For more information, see section Define Channels 1772 .
Status Handling Define if the Sensor Factory sensor enters the Down status or to the
Warning status if one of the source sensors is in the Down status:
§ Show down status when one or more source sensors are in the down
status (default): If at least one source sensor that you use in a channel
definition is in the Down status, the Sensor Factory sensor shows the
Down status as well until all referred sensors leave this status. While
the Sensor Factory sensor is in the Down status, it still shows data of
all available channels.
If a lookup definition or an error limit triggers the Down status of the
source sensor, the Sensor Factory does not show the Down
status. This is because the Sensor Factory should only show this
status if it cannot calculate values.
§ Show warning status when one or more source sensors are in the down
status: If at least one source sensor that you use in a channel definition
is in the Down status, the Sensor Factory sensor shows the Warning
status until all referred sensors leave the Down status.
If a lookup definition or an error limit triggers the Down status of the
source sensor, the Sensor Factory does not show the Warning
status. This is because the Sensor Factory sensor should only show
this status if it cannot calculate values.
§ Use custom formula: Define the status of the Sensor Factory sensor by
adding a Status Definition below.
Status Definition This setting is only visible if you select Use custom formula above.
1770
Setting Description
Define when the sensor switches to the 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.
For more information, see section Define Sensor Status: status()
Function 1778 .
If a Source Sensor Has Choose how this Sensor Factory sensor reacts if a source sensor referred
No Data to in the channel definition does not provide any data (for example,
because it is set to the Paused status or does not exist):
§ Do not calculate the channels that use the sensor (default): For defined
channels that use one or more sensors that deliver no data, no data is
shown.
§ Calculate the channels and use zero as source value: If a source
sensor that you use in a channel definition does not deliver any data,
zero values are filled in instead. The Sensor Factory sensor calculates
the channel value and shows it using these zero values.
If a sensor in the channel of a Sensor Factory sensor has no data,
the Sensor Factory sensor always shows the Warning status, no
matter which of the above options you select.
Sensor Display
Sensor Display
Setting Description

1771
Setting Description

other above.
procedure to do so.
Inherited Settings
Define Channels
The channels of a Sensor Factory sensor are controlled by the Channel Definition text field. Using a
special syntax, you can refer to other sensors' channels, calculate values, and add horizontal lines. You
can define Sensor Factory channels using data from any other sensor's channels on your PRTG core
server.
Make sure that no channel definitions refer to channels of Sensor Factory sensors.
Example
You see a definition of two Sensor Factory sensor channels. Both use the channel() function that
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 Sensor Factory sensor (#1) collects data from the Health channel (ID 0) of the
Probe Health sensor (ID 1001) running on the 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 are shown together in the Sensor Factory sensor's data tables and graphs.
1772
The basic syntax for a Sensor Factory sensor channel definition looks like this:
#<id>:<name>[<unit>]
<formula>
For each channel, one section is used. A section begins with the number sign (#). Function names in
formulas are not case-sensitive.
The parameters include the following:
§ <id> is the ID of the Sensor Factory sensor's channel. It must be a unique number that is greater than
0.
§ <name> is the name of the Sensor Factory sensor's channel (displayed in graphs and tables).
§ [<unit>] is an optional unit description for the Sensor Factory sensor's channel (for example, bytes). If
you do not provide a unit, the Sensor Factory sensor automatically selects a suitable unit string
(recommended).
§ <formula> contains the formula to calculate the Sensor Factory sensor's channel. For the formula, you
can use the following functions: channel() 1773 , min() 1774 , max() 1774 , avg() 1775 , or percent() 1775 .
Define Channels: channel() Function

The channel() function allows the Sensor Factory sensor to read the data from a channel of a source
sensor. The syntax is:
channel(<sensorId>,<channelId>)
§ <sensorId> is the ID of the source sensor. It is displayed on the sensor's Overview tab.
§ <channelId> is the ID of the channel of the source sensor. It is displayed in the respective field of the
channel settings.
Example
channel(2001,2)
This function reads the data from channel ID 2 of the source sensor with the ID 2001.
#1:Sample
channel(2001,2)
This full channel definition reads the data from channel ID 2 of the source sensor with the ID 2001 and
displays it in the first Sensor Factory sensor channel (#1), without any additional calculations.
Define Channels: Formula Calculations

Within a formula, the following elements are allowed to perform calculations with the values that are
returned by one or more functions.
1773
§ Basic operations: + (add), - (subtract), * (multiply), / (divide)
Example: 3 + 5 * 2
§ Parentheses: ( )
Example: 3 * (2 + 6)
§ Compare: = (equal), <> (not equal), > (greater), < (less), >= (greater or equal), <= (less or equal)
If the comparison resolves to true, the value is 10,000. If false, the value is 0. For delta sensors, the
speed is compared.
Example
You see a Sensor Factory sensor channel definition with calculation.

#1:Traffic Total x Minus Traffic Out y
( channel(2001,-1) - channel(1004,1) ) * 2
This full channel definition results in a Sensor Factory sensor that shows a calculation with values
from two channels (channel IDs -1 and 1) of two traffic sensors (sensor IDs 2001 and 1004). The
returned values are subtracted and then multiplied by two.
Channels can be gauge values (for example, ping ms) or delta values (for example, traffic kbit/s). Not all
combinations are allowed in a formula.
When performing percentage calculation, use the percent() Function 1775 to make sure you obtain the
expected values.
There are calculations you cannot do:
§ You cannot add or 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 Channels: min() and max() Functions

The min() and max() functions return the minimum or maximum of two values. The syntax is:
min(<a>,)
max(<a>,)
Values for <a> and are either numbers or channel() 1773 functions.
1774
Examples
min(10,5)
This function returns 5, because this is the smaller value out of 10 and 5.
min( channel(2001,1),channel(2002,1) )
This function returns the minimum of the values of channel 1 of the source sensor with ID 2001 and
channel 1 of the source sensor with ID 2002.
Define Channels: avg() 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() 1773 functions.
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 source sensor with ID 2001 and channel 1 of the
source sensor with ID 2002.
Define Channels: percent() Function

The percent() function calculates the percent value of two specified values, for example, a channel and a
fixed value. The syntax is:
percent(<source>,<maximum>,<unit>)
§ <source> is the value the percent is calculated for. This is usually a channel() 1773 function.
§ <maximum> is the limit value used for the percent calculation.
§ <unit> is an optional unit the maximum is provided in. You can use constants with this function (see
Define Channels: Constants 1777 below for a list). This can be used for absolute values (for example,
Ping sensors 1606 ) or calculated delta values (for example, traffic sensors). If no unit is provided, 1 is
used.
The sensor adds the unit string % automatically.
PRTG calculates: <source> / <maximum> * <unit> * 100
1775
Examples
#1:Usage Traffic In
percent(channel(2001,0),100,kilobit)
#2:Usage Traffic Out
percent(channel(2001,1),100,kilobit)
This full channel definition results in a Sensor Factory sensor that shows two channels of a traffic
sensor (sensor ID 2001): Traffic in (channel ID 0) and traffic out (channel ID 1). The Sensor Factory
sensor displays the values % of maximum bandwidth (100 kilobit/second).
#1:Ping %
percent(channel(2002,0),200)
This full channel definition results in a Sensor Factory sensor that shows the Ping Time channel
(channel ID 0) of a Ping sensor (sensor ID 2002). The sensor displays the values as a percentage of
200 ms.
Define Channels: Horizontal Lines

You can add lines to the graph using a formula without the channel() function. Use a fixed value instead.
The syntax is:
#<id>:<name>[<unit>]
<value>
§ <id> is the ID of the Sensor Factory sensor's channel and must be a unique number greater than 1.
Although the Sensor Factory sensor does not show a horizontal line as a channel, the ID has to be
unique.
§ <name> is the name of the Sensor Factory sensor's channel. PRTG does not display this name in
graphs and tables, but you can use it as a comment to describe the nature of the line.
§ [<unit>] is an optional unit description (for example, kbit/s). If you do not provide a unit, PRTG
automatically applies the line to the scale of the first Sensor Factory sensor's channel. If your Sensor
Factory sensor uses different units, provide a unit to make sure the line is added for the right scale.
Enter the unit exactly as shown in your graph's legend. If you enter a unit that does not yet exist in
your graph, a new scale is added automatically.
§ <value> contains a number defining where the line is shown in the graph.
1776
Examples
#5:Line at 100ms [ms]

100
This channel definition results in a graph that shows a horizontal line at the value of 100 on the ms
scale.
#6:Line at 2 Mbit/s [kbit/s]

2000
This channel definition results in a graph that shows a horizontal line at the value of 2000 on the kbit/s
scale.
#1:Ping Time
channel(2002,0)
#2:Line at 120ms [ms]
120
This full channel definition results in a Sensor Factory sensor that shows the Ping Time channel
(channel ID 0) of a Ping sensor (sensor ID 2002). Additionally, the sensor graphs show a horizontal
line at 120 ms.
Define Channels: Constants

The following constants are defined and can be used in calculations:
§ one = 1
§ kilo = 1000
§ mega = 1000 * kilo
§ giga = 1000 * mega
§ tera = 1000 * giga
§ byte = 1
§ kilobyte = 1024
§ megabyte = 1024 * kilobyte
§ gigabyte = 1024 * megabyte
§ terabyte = 1024 * gigabyte
§ bit = 1/8
§ kilobit = kilo / 8
§ megabit = mega / 8
§ gigabit = giga / 8
§ terabit = tera / 8
1777
Define Sensor Status: status() Function
You can control the status of a Sensor Factory sensor via the Status Definition text field if you enable
the custom formula option in the sensor settings 1769 . Using a special syntax, you can define when the
Sensor Factory sensor changes to the Down status. In all other cases, the sensor is in the Up status.
The syntax is:
status(sensorID) <boolean> status(sensorID)
§ <sensorId> is the ID of the source sensor that you want to check the status of. It is displayed on the
sensor's Overview tab.
§ <boolean> is one of the Boolean operators AND, OR, or NOT. If the resulting expression is true, the
Sensor Factory sensor changes to the Down status.
Examples
status(2031) AND status(2044)
This changes the Sensor Factory sensor to the Down status if both source sensors, with IDs 2031
and 2044, are in the Down status. Otherwise the Sensor Factory sensor shows the Up status.
status(2031) OR status(2044)
This changes the Sensor Factory sensor to the Down status if at least one of the source sensors with
ID 2031 or ID 2044 is in the Down status. Otherwise the Sensor Factory sensor shows the Up status.
status(2031) AND NOT status(2044)
This changes the Sensor Factory sensor to the Down status if the source sensor with ID 2031 is in
the Down status, but the source sensor with ID 2044 is not in the Down status. Otherwise the Sensor
Factory sensor shows the Up status.
A status() function with NOT has to be connected with AND or OR if it is combined with other
status() functions:
status(sensorID) AND NOT status(sensorID)

status(sensorID) OR NOT status(sensorID)
( status(2031) AND status(2044) ) OR status(2051)
This changes the Sensor Factory sensor to the Down status if both the source sensor with ID 2031
and the source sensor with ID 2044 are in the Down status, or if the source sensor with ID 2051 is in
the Down status. Otherwise the Sensor Factory sensor shows the Up status.
Additionally, the following elements are allowed to perform calculations and comparisons with the values
that are returned by the status functions:
§ Basic operations: + (add), - (subtract), * (multiply), / (divide)

Example: 3 + 5 * 2
1778
§ Parentheses: ( )
Example: 3 * (2 + 6)
§ Compare: = (equal), <> (not equal), > (greater), < (less), >= (greater or equal), <= (less or equal)
If the comparison resolves to true, the value is 10,000. If false, the value is 0. For delta sensors, the
speed is compared.
Internally, the status() function returns the Downtime channel of the source sensor in hundreds of percent
(10,000 = 100%).
§ true corresponds to a value of 10,000, which is the Down status.
§ false corresponds to a value of 0, which is the Up status.
If you understand this, you can use more complex formulas.
Example
( status(1031) + status(1032) + status(1033) + status(1034) ) >= 20000
This changes the Sensor Factory sensor to the Down status if at least any two of the source sensors
with IDs 1031, 1032, 1033, or 1034 are in the Down status. Otherwise the Sensor Factory sensor
shows the Up status.
You can also use the status() function in channel definitions 1772 . Using this functionality, it is
possible, for example, to display the numeric status value of source sensors in a Sensor Factory
sensor channel.
Using Sensor Factory Sensors in a Cluster

If you run PRTG in a failover cluster, note the following:
§ If you add a Sensor Factory sensor underneath the cluster probe, and in the Sensor Factory formula
you refer to a channel of a source sensor running on the cluster probe as well, the Sensor Factory
sensor shows the data of all cluster nodes for this 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 cluster probe, the Sensor Factory sensor only shows
data of the primary master node for this channel.
Channel List
Channel Description
[Custom] The monitoring results from other sensors or devices. Samples for usage
are:
§ Show single channels of one or more sensors in one graph.
1779
Channel Description
§ 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 sensors' channels and add
horizontal lines at specific vertical positions.
The Sensor Factory sensor does not show values in the Downtime
channel because they cannot be calculated for this sensor.
More
KNOWLEDGE BASE
How can I monitor the overall status of the business process "email"?

Can you help me understand when the Sensor Factory sensor changes to the down status and why?
What can I do with the Sensor Factory sensors of PRTG?

VIDEO TUTORIAL
Sensor Factory sensor

§ https://www.paessler.com/support/videos-and-webinars/videos/factory-sensor
1780
7.8.155 sFlow Sensor
The sFlow sensor receives traffic data from an sFlow v5-compatible device and shows the traffic by type.
This sensor has several filter options to divide traffic into different channels.
Make sure that the target device supports sFlow v5.
sFlow Sensor
List 1788 .
1781
§ Dutch: sFlow
§ French: sFlow
§ German: sFlow
§ Japanese: sFlow
§ Portuguese: sFlow
§ Russian: sFlow
§ Simplified Chinese: sFlow
§ Spanish: sFlow
Remarks
Remark Description
sFlow § This sensor requires that the sFlow v5 export is enabled on the target
RAW data § This sensor accepts RAW data only. The stream must be sent via IPv4.
Limitations § This sensor has several limitations 1783 .
Knowledge Base § Knowledge Base: How can I change the default groups and channels
§ Knowledge Base: Where is the volume line in graphs?
1782
Remark Description
probe device.
Limitations
There are some limitations that you should consider before you use this sensor:
§ This sensor only supports sFlow v5 datagrams.
§ This sensor only supports IPv4 flows.
§ This sensor only supports the "raw packet header" format.
§ This sensor only supports the "Flow sample" and "Extended flow" formats. It cannot process "Counter"
formats.
§ This sensor only processes samples where the source ID matches the ifIndex of the input interface
(avoiding double-counted traffic) and ascending sequence numbers.
§ This sensor only supports sample packets of the Ethernet type "IP" (with optional VLAN tag)
§ This sensor only supports sampled packets of the types TCP and UDP.
We recommend that you use sFlow Tester for debugging.
you add the sensor:
§ bandwidthsensor
§ sflowsensor
1783
sFlow v5 Specific Settings
Setting Description
Receive Packets on UDP Enter the UDP port number on which the flow packets are received. It
Port must match the UDP port number in the sFlow export options of the
hardware router device. The default port is 6343. Enter an integer.
sFlow from. Enter an IP address to only receive data from a specific
specified port.
Receive Packets on IP Select the IP addresses on which PRTG listens to sFlow packets. The
select must match the IP address in the sFlow export options of the
appropriate sFlow v5 for this sensor
packet data.
1784
Setting Description
interval.
Setting Description

ICMP, and SNMP.
1785
Setting Description
Other.
channel.
Filtering
Filtering
1786
Setting Description
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1787
Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
Inherited Settings
Toplists
Filter Rules
Channel List
1788
Channel Description

More
KNOWLEDGE BASE


1789
PAESSLER TOOLS
sFlow Tester
§ https://www.paessler.com/tools/sflowtester
1790
7.8.156 sFlow (Custom) Sensor
The sFlow (Custom) sensor receives traffic data from an sFlow v5-compatible device and shows the traffic
by type. With this sensor, you can define your own channel definitions to divide traffic into different
channels.
Make sure that the target device supports sFlow v5.
sFlow (Custom) Sensor
List 1798 .
1791
§ Dutch: sFlow (Custom)
§ French: sFlow personnalisé
§ German: sFlow (Benutzerdef.)
§ Japanese: sFlow( )
§ Portuguese: sFlow (customizado)
§ Russian: sFlow ( )
§ Simplified Chinese: sFlow ( )
§ Spanish: sFlow (personalizado)
Remarks
Remark Description
sFlow § This sensor requires that the sFlow v5 export is enabled on the target
RAW data § This sensor accepts RAW data.
Limitations § This sensor has several limitations 1792 .
Knowledge Base § Knowledge Base: Where is the volume line in graphs?
probe device.
Limitations
There are some limitations that you should consider before you use this sensor:
1792
§ This sensor only supports sFlow v5 datagrams.
§ This sensor only supports IPv4 flows.
§ This sensor only supports the "raw packet header" format.
§ This sensor only supports the "Flow sample" and "Extended flow" formats. It cannot process "Counter"
formats.
§ This sensor only processes samples where the source ID matches the ifIndex of the input interface
(avoiding double-counted traffic) and ascending sequence numbers.
§ This sensor only supports sample packets of the Ethernet type "IP" (with optional VLAN tag)
§ This sensor only supports sampled packets of the types TCP and UDP.
We recommend that you use sFlow Tester for debugging.
you add the sensor:
§ bandwidthsensor
§ sflowsensor
1793
Setting Description
Receive Packets on UDP Enter the UDP port number on which the flow packets are received. It
Port must match the UDP port number in the sFlow export options of the
hardware router device. The default port is 6343. Enter an integer.
sFlow from. Enter an IP address to only receive data from a specific
specified port.
Receive Packets on IP Select the IP addresses on which PRTG listens to sFlow packets. The
select must match the IP address in the sFlow export options of the
1794
Setting Description
packet data.
interval.
Filtering
1795
Filtering
Setting Description
Sensor Display
Sensor Display
Setting Description
1796
Setting Description

other above.
procedure to do so.
Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
Inherited Settings
1797
Toplists
Filter Rules
Channel List
Channel Description

More
KNOWLEDGE BASE


PAESSLER TOOLS
sFlow Tester
§ https://www.paessler.com/tools/sflowtester
1798
7.8.157 SFTP Secure File Transfer Protocol Sensor
The SFTP Secure File Transfer Protocol sensor monitors File Transfer Protocol (FTP) servers of a
Linux/Unix system via the Secure Shell (SSH) File Transfer Protocol (FTP over SSH).
SFTP Secure File Transfer Protocol Sensor
List 1803 .

§ Dutch: SFTP Secure File Transfer Protocol
§ French: Protocole sécurisé de transfert de fichiers (SFTP)
§ German: SFTP Secure File Transfer Protocol
§ Japanese: SFTP( Secure File Transfer Protocol)
§ Portuguese: SFTP Secure File Transfer Protocol
§ Russian: SFTP
§ Simplified Chinese: SFTP
§ Spanish: SFTP Secure File Transfer Protocol
Remarks
1799
Remark Description
Credentials § This sensor requires credentials for Linux/Solaris/macOS

(SSH/WBEM) systems in the settings of the parent device.
Distributions § This sensor does not support all Linux/Unix and macOS distributions.
Knowledge Base § Knowledge Base: Which encryption algorithms do PRTG SSH sensors
support?
§ Knowledge Base: SSH and SFTP sensors in Unknown status
you add the sensor:
§ sftpsensor
1800
SSH Specific
SSH Specific
Setting Description
Connection Timeout Define a timeout in seconds for the connection. This is the time that the
(Sec.) sensor waits to establish a connection to the host. Keep this value as low
as possible. Enter an integer. The maximum timeout value is 900
seconds (15 minutes).
Make sure that the connection timeout is a value that is higher than
the shell timeout to avoid potential errors.
Shell Timeout (Sec.) Define a timeout in seconds for the shell response. This is the time in
seconds the sensor waits for the shell to return a response after it has
sent its specific command (for example, cat /proc/loadavg). The
maximum value is 300 seconds (5 minutes). Enter an integer.
Make sure that the shell timeout is a value that is lower than the
connection timeout to avoid potential errors.
SSH Port Define which port this sensor uses for the SSH connection:
§ Inherit port number from parent device (default): Use the port number as
defined in the Credentials for Linux/Solaris/macOS (SSH/WBEM)
Systems section of the parent device settings.
§ Enter custom port number: Define a custom port number below and do
not use the port number from the parent device settings.
Use Port Number This setting is only visible if you select Enter custom port number above.
1801
Setting Description
Enter the port number (between 1 and 65535) that this sensor uses for
the SSH connection. Enter an integer.
SSH Engine Select the SSH engine that you want to use to access data with this
SSH sensor:
§ Inherit from parent device (default): Use the SSH engine that you
defined in the parent device settings or higher up in the object
hierarchy. If you have not changed the SSH engine, this is the
recommended option.
§ Default: This is the default SSH engine. It provides the best
performance and security. It is set by default in objects that are higher
up in the hierarchy, so usually you can keep the Inherit from parent
device (default) option.
§ Compatibility mode (deprecated): Use this only if the default SSH
engine does not work on a target device. The compatibility mode is the
SSH engine that PRTG used in previous versions. It is deprecated. We
will remove this legacy mode soon, so try to get your SSH sensors to
run with the default SSH engine.
We strongly recommend that you use the default SSH engine.
The option you select here overrides the selection of the SSH engine
in a higher object: a parent device, group, probe, or root.
Result of Sensor [ID].Data.txt. This setting is for debugging purposes.
PRTG overwrites this file with each scanning interval.
master node.
1802
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
1803
Channel Description
More
KNOWLEDGE BASE
Which encryption algorithms do PRTG SSH sensors support?

SSH and SFTP sensors in Unknown status


1804
7.8.158 Share Disk Free Sensor
The Share Disk Free sensor monitors free disk space of a share (Windows/Samba) using Server
Message Block (SMB).
Share Disk Free Sensor
List 1808 .

§ Dutch: Share Disk Ruimte
§ French: Espace disponible du disque partagé
§ German: Freigaben-Speicherplatz
§ Japanese:
§ Portuguese: Disco livre para compartilhamento
§ Russian:
§ Spanish: Espacio libre en disco compartido
Remarks
1805
Remark Description
system.
Quotas § This sensor only works if no quotas are enabled on the target share. If
there are quotas enabled for the user account that this sensor uses to
connect to the share, the absolute value is okay, but the percentage
variable shows incorrect values.
Share name § You can only enter a share name, for example, C$. Do not enter a
complete Universal Naming Convention (UNC) name. The sensor takes
the server name \\server\ from the parent device.
probe device.
you add the sensor:
§ diskspacesensor
1806
§ smbdiskspacesensor
Share Configuration
Share Configuration
Setting Description
Share The name of the share that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


other above.
1807
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description

More
KNOWLEDGE BASE

1808
7.8.159 SIP Options Ping Sensor
The SIP Options Ping sensor monitors the connectivity to a Session Initiation Protocol (SIP) server using
SIP options "ping". The sensor sends auth and options requests to the SIP server.
You can use this sensor to monitor Voice over IP (VoIP) services.
SIP Options Ping Sensor
List 1813 .

§ Dutch: SIP Opties Ping
§ French: SIP Options Ping
§ German: SIP Options Ping
§ Japanese: SIP Ping

§ Portuguese: Options SIP Ping
§ Russian: SIP
§ Simplified Chinese: SIP Ping
§ Spanish: Opciones SIP Ping
Remarks
1809
Remark Description
does PRTG require?
channels.
Error message § An SIP server might return the error '480 Service temporarily
unavailable' until at least one reachable SIP client is connected to the
server.
you add the sensor:
§ pingsensor
§ sipsensor
1810
SIP Specific
SIP Specific
Setting Description
integer. The default User Datagram Protocol (UDP) port is 5060.
User Name Enter the user name of the SIP user account that this sensor logs in to
after a successful connection to the SIP server. Enter a string.
Password Enter the password of the SIP user account that this sensor logs in to
after a successful connection to the SIP server. Enter a string.
Timeout (Sec.) Enter the timeout for the connection to the SIP server. Enter an integer.
The maximum timeout value is 300 seconds (5 minutes).
Retry Count If the connection to the SIP server fails, the sensor tries to connect again.
Enter the maximum number of retries. After the sensor reaches the
maximum count, it shows the Down status. Enter an integer.
Debug Options
Debug Options
1811
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description


other above.
1812
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Response Code The response code
You can individually define the status for each individual response
code by editing the lookup file prtg.standardlookups.sip.statuscode.
More
KNOWLEDGE BASE


1813
7.8.160 SMTP Sensor
The SMTP sensor monitors a mail server using the Simple Mail Transfer Protocol (SMTP).
The sensor can optionally send a test email with every check.
SMTP Sensor
List 1820 .

§ Dutch: SMTP
§ French: SMTP
§ German: SMTP
§ Japanese: SMTP
§ Portuguese: SMTP
§ Russian: SMTP
§ Simplified Chinese: SMTP
§ Spanish: SMTP
Remarks
1814
Remark Description
probe device.
you add the sensor:
§ mailsensor
§ smtpsensor
SMTP Specific
SMTP Specific
1815
Setting Description
Port Enter the number of the port that the sensor uses to send an email via
SMTP. The default port for unsecure connections is 25 and the default
ports for secure connections are 465 or 587. The actual setting depends
on the server that you connect to. Enter an integer.
Authentication
Authentication
Setting Description
SMTP Authentication Define if you want to use authentication for the SMTP connection:
Method
§ None (default): Do not use any authentication method.
§ User name and password: Authenticate against the SMTP server via
user name and password.
Enter a user name for SMTP authentication. Enter a string.
Enter a password for SMTP authentication. Enter a string.
HELO Ident Enter a server name for the HELO part of the mail protocol.
1816
Setting Description
For some mail servers, the HELO identifier must be the valid principal
host domain name for the client host. For more information, see
SMTP RFC 2821.
If you leave this field empty, the value defaults to the computer name.
Only ASCII characters are allowed.
Connection Security
Connection Security
Setting Description

1817
Monitoring
Monitoring
Setting Description
Email Handling Define the monitoring approach when connecting to the SMTP server:
§ Do not send an email (default): Do not send an email, only connect to
the SMTP server.
§ Send an email: Send an email through the SMTP server. If there is an
error when sending the email, this triggers an error message and the
sensor changes to the Down status.
From This setting is only visible if you select Send an email above.
Specify the address of the sender of the email. Enter a valid email
address.
To This setting is only visible if you select Send an email above.
Specify the address that PRTG sends the email to. Enter a valid email
address.
If you define more than one recipient, separate the individual email
addresses with commas.
Subject This setting is only visible if you select Send an email above.
Specify the subject that the email contains. Enter a string or leave the
field empty.
Content This setting is only visible if you select Send an email above.
Specify the body that the email contains. Enter a string or leave the field
empty.
1818
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1819
Inherited Settings
Channel List
Channel Description

More
KNOWLEDGE BASE
1820
7.8.161 SMTP&IMAP Round Trip Sensor
The SMTP&IMAP Round Trip sensor monitors the time it takes for an email to reach an Internet
Message Access Protocol (IMAP) mailbox using the Simple Mail Transfer Protocol (SMTP). It sends an
email via the parent device (an SMTP server) and then scans a dedicated IMAP mailbox until the email
arrives.
The SMTP&IMAP Round Trip sensor automatically deletes these emails from the mailbox as soon
as PRTG retrieves them. The emails only remain in the mailbox if a timeout or a restart of the PRTG
core server occurs during sensor runtime.
SMTP&IMAP Round Trip Sensor
List 1829 .

§ Dutch: SMTP & IMAP Round Trip
§ French: SMTP & IMAP aller-retour
§ German: SMTP&IMAP-Übermittlung
§ Japanese: SMTP & IMAP
§ Portuguese: Ida e volta SMTP&IMAP
§ Russian: SMTP&IMAP
§ Simplified Chinese: SMTP IMAP
§ Spanish: Ida y vuelta SMTP&IMAP
1821
Remarks
Remark Description
Parent device § This sensor requires that the parent device is an SMTP server.
sensor.
Dedicated email § Use dedicated email accounts with this sensor. Make sure that each
accounts sensor uses its own email accounts.
you add the sensor:
§ imapsensor
§ mailsensor
§ roundtrip
1822
Email Settings
Email Settings
Setting Description
From Specify the email address of the email's sender. Enter a valid email
address.
To Specify the address that PRTG sends the emails to. Enter a valid email
address.
You can only enter one email address.
SMTP RFC 2821.
Step 1: Send Email Using Parent Device (SMTP Server)

In this step, you configure how the sensor sends the emails. The sensor uses the IP Address/DNS
Name of the parent device (an SMTP server).
1823
Setting Description
Timeout for SMTP Enter a timeout in seconds for the request. Enter an integer. The
Connection (Sec.) maximum timeout value is 900 seconds (15 minutes).
Method
Additional Text for Email PRTG automatically creates the subject part of the round trip email. The
Subject subject consists of the string PRTG Roundtrip Mail:, followed by a unique
globally unique identifier (GUID) to correctly identify the email in the IMAP
mailbox, for example, PRTG Roundtrip Mail: {5E858D9C-AC70-466A-
9B2A-55630165D276}.
Use this field to place your custom text before the automatically created
text.
Connection Security
Connection Security
1824
Setting Description

Step 2: Check an IMAP Mailbox until Email Arrives

In this step, you configure how to receive the emails that the sensor sends.
1825
Step 2: Check an IMAP Mailbox until Email Arrives
Setting Description
IP Address/DNS Name Specify the IMAP server. Enter a valid IP address or Domain Name
System (DNS) name.
Mailbox Specify the IMAP mailbox that you want to check. Enter the IMAP
mailbox or folder name, for example INBOX.
The IMAP mailbox or folder name must not match the sender of the
email in the From field. Otherwise, the sensor might incorrectly
interpret unsuccessful round trips as successful.
Port Specify the port that the sensor uses for the IMAP connection. The
connect to.. Enter an integer.
Connection Interval Enter the number of seconds the sensor waits between two connections
(Sec.) to the IMAP server. PRTG repeatedly checks the mailbox in this scanning
interval until the email arrives. Enter an integer.
1826
Setting Description
Maximum Trip Time Enter the maximum number of seconds an email can take to arrive in the
(Sec.) IMAP mailbox. PRTG continuously checks the mailbox in this scanning
interval until the email arrives. If it does not arrive within the maximum trip
time, the sensor shows an error message. Enter an integer.
User Name Enter a user name for IMAP authentication. Enter a string.
Password Enter a password for IMAP authentication. Enter a string.

The password must not contain spaces, percent signs (%), or the
character combination !*.
Search Method Define how to search for the round trip email in the mailbox:
§ Search for the email directly (default): Send a SEARCH command to
directly find the round trip email on the IMAP server.
§ Search through all available emails: Search through all available emails
in the mailbox locally to find the round trip email. This might take some
time if you have many emails in your mailbox.
Connection Security
Connection Security
Setting Description
1827
Setting Description

Debug Options
Debug Options
Setting Description
scanning interval.
master node.
1828
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
1829
Channel Description
Response Time (IMAP) The response time of the IMAP server
Response Time (SMTP) The response time of the SMTP server
Total The sum of the response time of the IMAP server and the SMTP server
More
KNOWLEDGE BASE

1830
7.8.162 SMTP&POP3 Round Trip Sensor
The SMTP&POP3 Round Trip sensor monitors the time it takes for an email to reach a Post Office
Protocol version 3 (POP3) mailbox using the Simple Mail Transfer Protocol (SMTP). It sends an email
using the parent device (an SMTP server) and then scans a dedicated POP3 mailbox until the email
comes in.
The SMTP&POP3 Round Trip sensor automatically deletes these emails from the mailbox as soon
as PRTG has retrieves them. Emails only remain in the mailbox if a timeout or a restart of the PRTG
core server occurs during sensor runtime.
SMTP&POP3 Round Trip Sensor
List 1839 .

§ Dutch: SMTP & POP3 Round Trip
§ French: SMTP & POP3 aller-retour
§ German: SMTP&POP3-Übermittlung
§ Japanese: SMTP&POP3
§ Portuguese: Ida e volta SMTP&POP3
§ Russian: SMTP POP3

§ Simplified Chinese: SMTP POP3
§ Spanish: Ida y vuelta SMTP&POP3
1831
Remarks
Remark Description
Parent device § This sensor requires that the parent device is an SMTP server.
sensor.
Dedicated email § Use dedicated email accounts with this sensor. Make sure that each
accounts sensor uses its own email accounts.
you add the sensor:
§ mailsensor
§ pop3sensor
§ roundtrip
1832
Email Settings
Email Settings
Setting Description
From Specify the email address of the email's sender. Enter a valid email
address.
To Specify the address that PRTG sends the emails to. Enter a valid email
address.
You can only enter one email address.
SMTP RFC 2821.

In this step, you configure how the sensor sends the emails. The sensor uses the IP Address/DNS
Name of the parent device (an SMTP server).
1833
Setting Description
Timeout for SMTP Enter a timeout in seconds for the request. Enter an integer. The
Connection (Sec.) maximum timeout value is 900 seconds (15 minutes).
Method
Additional Text for Email PRTG automatically creates the subject part of the round trip email. The
Subject subject consists of the string PRTG Roundtrip Mail:, followed by a unique
globally unique identifier (GUID) to correctly identify the email in the IMAP
mailbox, for example, PRTG Roundtrip Mail: {5E858D9C-AC70-466A-
9B2A-55630165D276}.
Use this field to place your custom text before the automatically created
text.
Connection Security
Connection Security
1834
Setting Description

Step 2: Check a POP3 Mailbox until Email Arrives

In this step, you configure how to receive the sent emails.
Step 2: Check a POP3 Mailbox until Email Arrives
1835
Setting Description
IP Address/DNS Name Specify the POP3 server. Enter a valid IP address or Domain Name
System (DNS) name.
Port Specify the port that the sensor uses for the POP3 connection. The
Connection Interval Enter the number of seconds the sensor waits between two connections
(Sec.) to the POP3 server. PRTG continuously checks the mailbox in this
scanning interval until the email arrives. Enter an integer.
Maximum Trip Time Enter the maximmum number of seconds an email can take to arrive in
(Sec.) the POP3 mailbox. PRTG continuously checks the mailbox in the interval
that you specify above until the email arrives. If it does not arrive within
the maximum trip time, the sensor triggers an error message. Enter an
integer.
POP3 Authentication Select the authentication method for the POP3 connection:
Method
§ <%C_Without_login%>: Only monitor the connection to the POP3
server.
§ User name and password: Log in to the POP3 server with user name
and password.
This is a simple login. It is not secure.
§ 128-bit MD5 hash value (APOP): Send the password in an encrypted

form using APOP.
The POP3 server that you connect to must support this option.
User Name This setting is only visible if you select User name and password or 128-
Password This setting is only visible if you select User name and password or 128-
1836
Connection Security
Connection Security
Setting Description
Debug Options
Debug Options
1837
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description


other above.
1838
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Response Time (POP3) The response time of the POP3 server
Response Time (SMTP) The response time of the SMTP server
Total The sum of the response time of the SMTP server and the POP3 server
More
KNOWLEDGE BASE

1839
7.8.163 SNMP APC Hardware Sensor
The SNMP APC Hardware sensor monitors performance counters on an APC UPS device via the Simple
Network Management Protocol (SNMP).
The SNMP APC Hardware sensor does not appear as a running sensor, instead it is created as an
SNMP Custom Advanced 1907 sensor.
SNMP APC Hardw are Sensor
List 1843 .

§ Dutch: SNMP APC Hardware
§ French: APC matériel (SNMP)
§ German: SNMP APC Hardware
§ Japanese: SNMP APC
§ Portuguese: Hardware APC (SNMP)
§ Russian: SNMP APC

§ Simplified Chinese: SNMP APC
§ Spanish: Hardware APC (SNMP)
Remarks
1840
Remark Description
Knowledge Base § Knowledge Base: How can I monitor additional counters with the SNMP
APC Hardware sensor?
§ Knowledge Base: How can I monitor an APC UPS that does not
support SNMP?
Add Sensor
APC UPS Specific
Setting Description
Category Select the performance counters that you want to monitor. PRTG creates
one SNMP Custom Advanced sensor with all performance counters of
each category that you select.
you add the sensor:
§ apcups
1841
APC UPS Specific
APC UPS Specific
Setting Description
Interface TheSe name of the interface (performance counter) that this sensor
monitors.
Unit String Define the unit of the numeric data that this sensor monitors at the OID.
Enter a string.
Multiplication If you want to multiply the received data with a certain value, enter the
quotient. Enter an integer.
Division If you want to divide the received data by a certain value, enter the divisor.
Enter an integer.

change.
Sensor Display
Sensor Display
1842
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
1843
Channel Description
[Performance Counter] The performance counters on an APC UPS device

§ Actual voltage of battery
§ Capacity of battery
§ Input and output frequency
§ Input and output voltage
§ Output load
§ Remaining runtime of battery
§ Temperature of battery
More
KNOWLEDGE BASE
How can I monitor additional counters with the SNMP APC Hardware sensor?
How can I monitor an APC UPS that does not support SNMP?

1844
7.8.164 SNMP Buffalo TS System Health Sensor
The SNMP Buffalo TS System Health sensor monitors the system health of a Buffalo TeraStation
network-attached storage (NAS) via the Simple Network Management Protocol (SNMP).
This sensor supports the following TeraStation systems: 3000, 3010, 3020, 5000, 5010, 6000, and
7000 series.
Run an auto-discovery with the device template Buffalo TeraStation NAS to automatically create
SNMP Custom Table sensors 1928 with additional useful information about the TeraStation, for
example, array status, disk smart status, disk status, and Internet Small Computer System Interface
(iSCSI) status. This device template also creates SNMP sensors for traffic, memory, and load average on
the TeraStation.
SNMP Buffalo TS System Health Sensor
List 1848 .

§ Dutch: SNMP Buffalo TS Systeemstatus
§ French: Buffalo TS état du système (SNMP)
§ German: SNMP Buffalo TS System Health
§ Japanese: SNMP Buffalo TS
§ Portuguese: Saúde do sistema Buffalo TS (SNMP)
1845
§ Russian: Buffalo TS SNMP
§ Simplified Chinese: SNMP Buffalo TS
§ Spanish: Salud de sistema Buffalo TS (SNMP)
Remarks
Remark Description
TeraStation series § This sensor supports the TeraStation 3000, 3010, 3020, 5000, 5010,
6000, and 7000 series.
channels.
Error message § In certain cases, this sensor might show an error message. If this
occurs, open the settings of the parent device, section SNMP
Compatibility Options, and set the Walk Mode to Use GETNEXT
requests.
you add the sensor:
§ buffalots
§ snmpbuffalots
§ systemhealth
1846
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
1847
Channel List
Channel Description
1 Min CPU Load Average The average CPU load (%)

Failover Status The failover status

§ Up status: Busy, Idle
§ Warning status: Initializing, Starting Backup, Starting Main, Stopping
Firmware Update If a firmware update is available

Available
§ Up status: No, Unknown, Latest
Percent Available The available memory (%)

Memory
Uptime The uptime
Warnings The number of warnings

More
KNOWLEDGE BASE
1848

1849
7.8.165 SNMP Cisco ADSL Sensor
The SNMP Cisco ADSL sensor monitors asymmetric digital subscriber line (ADSL) statistics of a Cisco
router via the Simple Network Management Protocol (SNMP).
SNMP Cisco ADSL Sensor
List 1852 .

§ Dutch: SNMP Cisco ADSL
§ French: Cisco ADSL (SNMP)
§ German: SNMP Cisco ADSL
§ Japanese: SNMP Cisco ADSL
§ Portuguese: Cisco ADSL (SNMP)
§ Russian: SNMP Cisco ADSL
§ Simplified Chinese: SNMP Cisco ADSL
§ Spanish: Cisco ADSL (SNMP)
Remarks
1850
Remark Description
you add the sensor:
§ snmpciscoadsl
Cisco ADSL Settings
Cisco ADSL Settings
Setting Description
Line Index The line index (performance counter) that this sensor monitors.
Sensor Display
Sensor Display
1851
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
1852
Channel Description
Local Attenuation The local attenuation
Local Power Output The local power outpu
Local SNR The local SNR
Remote Attenuation The remote attenuation
Remote Power Output The remote power output
Remote SNR The remote SNR
Speed Downlink The downlink speed

Speed Uplink The uplink speed
More
KNOWLEDGE BASE


1853
7.8.166 SNMP Cisco ASA VPN Connections Sensor
The SNMP Cisco ASA VPN Connections sensor monitors the VPN connections on a Cisco Adaptive
Security Appliance via the Simple Network Management Protocol (SNMP).
SNMP Cisco ASA VPN Connections Sensor
List 1856 .

§ Dutch: SNMP Cisco ASA VPN Verbindingen
§ French: Cisco ASA connexions VPN (SNMP)
§ German: SNMP Cisco ASA VPN-Verbindungen
§ Japanese: SNMP Cisco ASA VPN
§ Portuguese: Conexões VPN Cisco ASA (SNMP)
§ Russian: SNMP Cisco ASA VPN

§ Simplified Chinese: SNMP Cisco ASA VPN
§ Spanish: Conexiones VPN Cisco ASA (SNMP)
1854
Remarks
Remark Description
you add the sensor:
§ snmpciscoasavpnconnectionssensor
§ snmpciscoasavpnsensor
Sensor Display
Sensor Display
Setting Description
1855
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Active Email Sessions The number of active email sessions
Active IPSec Sessions The number of active IPsec sessions
Active L2L Sessions The number of active L2L sessions
1856
Channel Description
Active LB Sessions The number of active LB sessions
Active Sessions The total number of active sessions

Active SVC Sessions The number of active SVC sessions
Active Users The number of active users
Active WebVPN The number of active WebVPN users

Sessions
Groups With Active The number of groups with active users

Users
More
KNOWLEDGE BASE

1857
7.8.167 SNMP Cisco ASA VPN Traffic Sensor
The SNMP Cisco ASA VPN Traffic sensor monitors the traffic of an Internet Protocol Security (IPsec)
VPN connection on a Cisco Adaptive Security Appliance via the Simple Network Management Protocol
(SNMP).
SNMP Cisco ASA VPN Traffic Sensor
List 1861 .

§ Dutch: SNMP Cisco ASA VPN Verkeer
§ French: Cisco ASA trafic VPN (SNMP)
§ German: SNMP Cisco ASA VPN-Datenverkehr
§ Portuguese: Tráfego VPN Cisco ASA (SNMP)

§ Spanish: Tráfico VPN Cisco ASA (SNMP)
Remarks
1858
Remark Description
IPsec connections § This sensor can monitor IPsec connections only.
Permanent connections § This sensor is intended to monitor permanent connections. It shows an

error if a connection is interrupted.
Knowledge Base § Knowledge Base: I get the error PE123 when using the SNMP Cisco
ASA VPN Traffic sensor. What can I do?
you add the sensor:
§ snmpciscoasavpntrafficsensor
ASA VPN Specific
ASA VPN Specific
1859
Setting Description
Remote IP Address The IP address of the connection that this sensor monitors.

monitoring data.
Sensor Behavior Define the sensor status if no active connection is available:

§ Show down status if no connection is active (default): Set the sensor to
the Down status if no connection is active.
§ Show warning status if no connection is active: Set the sensor to the
Warning status if no connection is active.
§ Stay in up status if no connection is active: Stay in the Up status if no
connection is active.
IKE Version Handling Select the engine for the Internet Key Exchange (IKE) version handling:
§ IKEv1 (default): Select this option if the tunnel on the device uses
IKEv1.
§ IKEv1 and IKEv2: Select this option if the tunnel on the device uses
IKEv1 or IKEv2.
The IKEv1 and IKEv2 option is in beta status and might not work
properly.
Sensor Display
Sensor Display
Setting Description
1860
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Traffic In The incoming traffic

Traffic Out The outgoing traffic
1861
More
KNOWLEDGE BASE
I get the error PE123 when using the SNMP Cisco ASA VPN Traffic sensor. What can I do?

1862
7.8.168 SNMP Cisco ASA VPN Users Sensor
The SNMP Cisco ASA VPN Users sensor monitors account connections to a VPN on a Cisco Adaptive
Security Appliance via the Simple Network Management Protocol (SNMP).
SNMP Cisco ASA VPN Users Sensor
List 1865 .

§ Dutch: SNMP Cisco ASA VPN Gebruikers
§ French: Cisco ASA utilisateurs VPN (SNMP)
§ German: SNMP Cisco ASA VPN-Benutzer
§ Portuguese: Usuários VPN Cisco ASA (SNMP)

§ Spanish: Usuarios VPN Cisco ASA (SNMP)
Remarks
1863
Remark Description
VPN users § Do not use this sensor to monitor more than 50 VPN users, especially
if they are all connected simultaneously. For more information, see the
Knowledge Base: My SNMP Cisco ASA VPN Users sensor shows a
user limit error. Why? What can I do?
you add the sensor:
§ snmpciscoasavpntrafficsensor
Sensor Display
Sensor Display
1864
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
[Account] The account status

§ Up status: Offline, Online
1865
Channel Description
Connected Accounts The number of connected accounts

More
KNOWLEDGE BASE
My SNMP Cisco ASA VPN Users sensor shows a user limit error. Why? What can I do?


1866
7.8.169 SNMP Cisco CBQoS Sensor
The SNMP Cisco CBQoS sensor monitors network parameters using Cisco's Class Based Quality of
Service (CBQoS) via the Simple Network Management Protocol (SNMP).
The sensor supports the classes Class Map, Match Statement, and Queueing.
SNMP Cisco CBQoS Sensor
List 1870 .

§ Dutch: SNMP Cisco CBQoS
§ French: Cisco CBQoS (SNMP)
§ German: SNMP Cisco CBQoS
§ Japanese: SNMP Cisco CBQoS
§ Portuguese: CBQoS Cisco (SNMP)
§ Russian: SNMP Cisco CBQoS
§ Simplified Chinese: SNMP Cisco CBQoS
§ Spanish: CBQoS Cisco (SNMP)
Remarks
1867
Remark Description
you add the sensor:
§ cbqossensor
Class Based QoS Specific
Class Based QoS Specific
1868
Setting Description
Object Type The object type of the parameter that this sensor monitors.
Interface The interface of the parameter that this sensor monitors.
Description The description of the parameter that this sensor monitors.
BitMask The number of available channels for the parameter that this sensor
monitors.
ObjectID The ObjectID of the parameter that this sensor monitors.
ConfigID The ConfigID of the parameter that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


1869
Setting Description
other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Current Queue Depth The current queue depth
Drop Packets The number of drop packets
Drop Size The drop size
Maximum Queue Depth The maximum queue depth
No Buffer Drop Packets The number of drop packets without buffer
Post Policy Size The post policy size
Pre Policy Packets The number of pre-policy packets
1870
Channel Description
Pre Policy Size The pre-policy size
More
KNOWLEDGE BASE


1871
7.8.170 SNMP Cisco System Health Sensor
The SNMP Cisco System Health sensor monitors the system health of a Cisco device via the Simple
SNMP Cisco System Health Sensor
List 1875 .

§ Dutch: SNMP Cisco Systeemstatus
§ French: Cisco état du système (SNMP)
§ German: SNMP Cisco Systemzustand
§ Japanese: SNMP Cisco
§ Portuguese: Saúde do sistema Cisco (SNMP)
§ Russian: SNMP Cisco

§ Simplified Chinese: SNMP Cisco
§ Spanish: Salud de sistema Cisco (SNMP)
Remarks
1872
Remark Description
channels.
Additional tags § SNMP Cisco System Health sensors that are created with the Cisco
Device (Generic) device template for auto-discovery can have additional
tags.
you add the sensor:
§ snmpciscosystemhealthsensor
§ systemhealth
Cisco System Health Specific
Cisco System Health Specific
1873
Setting Description
Measurements The ID of the measurement that this sensor monitors.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
1874
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
PRTG creates one sensor per component.
Channel Description
Available Memory [#] The available memory
CPU [#] The CPU load (%)
1875
Channel Description
Fan [#] State The fan status
§ Down status: Critical, Not Functioning, Shutdown
§ Unknown status: Not Present

Memory [#]
Power Supply [#] The power supply status

§ Down status: Critical, Not Functioning, Shutdown
§ Unknown status: Not Present
More
KNOWLEDGE BASE


1876
7.8.171 SNMP Cisco UCS Blade Sensor
The SNMP Cisco UCS Blade sensor monitors the health status of a Cisco Unified Computing System
(UCS) blade server via the Simple Network Management Protocol (SNMP).
SNMP Cisco UCS Blade Sensor
List 1880 .

§ Dutch: SNMP Cisco UCS Blade
§ French: Cisco UCS serveur Blade (SNMP)
§ German: SNMP Cisco UCS Blade
§ Japanese: SNMP Cisco UCS
§ Portuguese: Blade Cisco UCS (SNMP)
§ Russian: SNMP Cisco UCS

§ Simplified Chinese: SNMP Cisco UCS
§ Spanish: Blade Cisco UCS (SNMP)
Remarks
1877
Remark Description
channels.
you add the sensor:
§ blade
§ systemhealth
§ ucs
§ ucssystemhealth
Sensor Settings
Sensor Settings
1878
Setting Description
Blade Servers The blade server that this sensor monitors.
Channel Mask The available channels for the blade server that this sensor monitors.
Model The model of the blade server that this sensor monitors.
Serial Number The serial number blade server that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1879
Inherited Settings
Channel List
Channel Description
Oper State The oper status

§ Up status: Config, Diagnostics, Disabled, Discovery, Ok, Pending
Reassociation, Pending Reboot, Test, Unconfig
§ Warning status: Bios Restore, CMOS Reset, Decomissioning,
Degraded, Maintenance, Power Problem, Restart, Thermal Problem,
Voltage Problem
§ Down status: Compute Failed, Compute Mismatch, Config Failure,
Diagnostics Failed, Discovery Failed, Inaccessible, Indeterminate,
Inoperable, Maintenance Failed, Power Off, Removed, Test Failed,
Unassociated, Unconfig Failed
Operability The operability status

§ Up status: Auto Upgrade, Operable
§ Warning status: Degraded, Unknown
§ Down status: Accessibility Problem, Bios Post Timeout, Chassis Limit

Exceeded, Config, Decomissioning, Disabled, Equipment Problem,
Discovery, Discovery Failed, Fabric Connection Problem, Fabric
Unsupported Connection, Identify, Identity Unestablishable, Inoperable,
Link Activate Blocked, Malformed Fru, Not Supported, Peer Comm
Problem, Performance Problem, Post Failure, Power Problem, Powered
Off, Removed, Thermal Problem, Upgrade Problem, Voltage Problem
Power State The power status
1880
Channel Description
§ Up status: Off Duty, Ok, On, Online, Power Save, Test
§ Warning status: Degraded, Not Supported, Unknown
§ Down status:Error, Failed, Off, Offline
More
KNOWLEDGE BASE


1881
7.8.172 SNMP Cisco UCS Chassis Sensor
The SNMP Cisco UCS Chassis sensor monitors the health status of the chassis of a Cisco Unified
Computing System (UCS) device via the Simple Network Management Protocol (SNMP).
SNMP Cisco UCS Chassis Sensor
List 1884 .

§ Dutch: SNMP Cisco UCS Chassis
§ French: Cisco UCS châssis (SNMP)
§ German: SNMP Cisco UCS Chassis
§ Portuguese: Chassi Cisco UCS (SNMP)

§ Spanish: Chasis Cisco UCS (SNMP)
Remarks
1882
Remark Description
channels.
you add the sensor:
§ chassis
§ systemhealth
§ ucs
§ ucssystemhealth
Sensor Settings
Sensor Settings
Setting Description
Chassis The chassis that this sensor monitors.
1883
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
1884
Channel Description
Config State The configuration status

§ Up status: Acknowledged, Auto Acknowledge, OK
§ Warning status: Ack in Progress, Evaluation
§ Down status: Removing, UnAcknowledged, UnInitalized, Unsupported

Connectivity
License State The license status

§ Up status: License Ok
§ Warning status: License Grace Period, Unknown
§ Down status: License Expired, License Insufficient
§ Unknown status: Not Applicable
Oper State The oper status




1885
Channel Description
Power State The power status

§ Up status: Ok
§ Warning status: Input Degraded, Output Degraded, Redundancy

Degraded, Unknown
§ Down status: Failed, Input Failed, Output Failed, Redundancy Failed
Seeprom State The serial electrically erasable programmable read-only memory

(SEEPROM) state

Thermal State The thermal status

§ Up status: Ok
§ Warning status: Lower Non Critical, Upper Non Critical
§ Down status: Lower Critical, Lower Non Recoverable, Upper Critical,

Upper Non Recoverable
§ Unknown status: Not Supported, Unknown
More
KNOWLEDGE BASE


1886
7.8.173 SNMP Cisco UCS Physical Disk Sensor
The SNMP Cisco UCS Physical Disk sensor monitors a physical disk of a Cisco Unified Computing
System (UCS) device via the Simple Network Management Protocol (SNMP).
SNMP Cisco UCS Physical Disk Sensor
List 1890 .

§ Dutch: SNMP-Cisco UCS fysieke schijf
§ French: Cisco UCS disque physique (SNMP)
§ German: SNMP Cisco UCS Physikalisches Laufwerk
§ Portuguese: Disco físico Cisco UCS (SNMP)

§ Spanish: Disco físico Cisco UCS (SNMP)
Remarks
Remark Description
1887
Remark Description
channels.
Add Sensor dialog § The Add Sensor dialog only shows working disks that have the status
Up or Warning.
you add the sensor:
§ snmp
§ snmpciscophysicaldisksensor
§ ucs
UCS Physical Disk
UCS Physical Disk
Setting Description
1888
Setting Description
Display Name The display name of the physical disk that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
1889
Channel List
Channel Description


Problem, Performance Problem, Post Failure, Powered Off, Power
Problem, Removed, Thermal Problem, Upgrade Problem, Voltage
Problem
Presence The connection status
§ Up status: Equipped, Equipped Not Primary
§ Warning status: Equipped Identity Unestablishable, Mismatch,

Mismatch Identity Unestablishable, Missing,
§ Down status: Equipped With Malformed Fru, Inaccessible, Not
Supported, Unauthorized
§ Unknown status: Empty, Unknown
More
KNOWLEDGE BASE


1890
7.8.174 SNMP Cisco UCS System Health Sensor
The SNMP Cisco UCS System Health sensor monitors the system health of a Cisco Unified Computing
System (UCS) device via the Simple Network Management Protocol (SNMP).
SNMP Cisco UCS System Health Sensor
List 1893 .

§ Dutch: SNMP Cisco UCS Systeemstatus
§ French: Cisco UCS état du système (SNMP)
§ German: SNMP Cisco UCS Systemzustand
§ Portuguese: Saúde do sistema Cisco UCS (SNMP)

§ Spanish: Salud de sistema Cisco UCS (SNMP)
1891
Remarks
Remark Description
channels.
you add the sensor:
§ systemhealth
§ ucs
§ ucssystemhealth
Sensor Display
Sensor Display
1892
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Critical Faults Count The number of critical faults (that are not yet acknowledged in the UCS
logs)
1893
Channel Description
§ Upper error limit: 0.5
Fan Failure Predicted The predicted fan failure status

§ Up status: No, Not Available
§ Down status: Yes
Fan Module Failure The predicted fan module failure status

Predicted
§ Down status: Yes
Fan Module Performance The fan module performance status

§ Up status: Ok

Fan Module Thermal The fan module thermal status
§ Up status: Ok

Fan Modules Inoperable The number of operable fan modules

§ Upper warning limit: 0.5
Fan Modules Operable The number of inoperable fan modules
Fan Performance The fan performance

§ Up status: Ok
1894
Channel Description

Fan Thermal The fan thermal status
§ Up status: Ok

Fans Inoperable The number of inoperable fan modules

Fans Operable The number of operable fan modules

Major Faults Count The number of major faults (that are not yet acknowledged in the UCS
logs)
Minor Faults Count The number of minor faults (that are not yet acknowledged in the UCS
logs)
Power Supplies The number of inoperable power supplies

Inoperable
Power Supplies Operable The number of operable power supplies
Power Supply Failure The predicted power supply failure status

Predicted
1895
Channel Description
§ Down status: Yes
Power Supply The power supply performance status

Performance
§ Up status: Ok

Power Supply Thermal The power supply thermal status

§ Up status: Ok

Power Supply Voltage The power supply voltage status

§ Up status: Ok

Warning Count The number of warnings (that are not yet acknowledged in the UCS logs)
More
KNOWLEDGE BASE


1896
7.8.175 SNMP CPU Load Sensor
The SNMP CPU Load sensor monitors the system load via the Simple Network Management Protocol
(SNMP).
SNMP CPU Load Sensor
List 1900 .

§ Dutch: SNMP CPU Load
§ French: Charge CPU (SNMP)
§ German: SNMP CPU-Last
§ Japanese: SNMP CPU
§ Portuguese: Carga CPU (SNMP)
§ Russian: SNMP
§ Simplified Chinese: SNMP CPU
§ Spanish: Carga CPU (SNMP)
Remarks
1897
Remark Description
Localhost § It might not work to query data from a probe device via SNMP (querying
localhost, 127.0.0.1, or ::1). Add this device with the IP address that it
has in your network and create the sensor on this device instead.
you add the sensor:
§ cpu
§ cpuloadsensor
§ snmp
Debug Options
Debug Options
Setting Description
1898
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
1899
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Processor [#] The CPU load (%)
Total The total CPU load (%)

More
KNOWLEDGE BASE


1900
7.8.176 SNMP Custom Sensor
The SNMP Custom sensor monitors a single parameter that is returned by a specific object identifier
(OID) via the Simple Network Management Protocol (SNMP).
SNMP Custom Sensor
List 1905 .

§ Dutch: SNMP (Klant specifiek)
§ French: SNMP personnalisé
§ German: SNMP (Benutzerdef.)
§ Japanese: SNMP
§ Portuguese: SNMP (customizado)
§ Russian: SNMP
§ Simplified Chinese: SNMP
§ Spanish: SNMP (personalizado)
Remarks
Remark Description
1901
Remark Description
Knowledge Base § Knowledge Base: How do I find out which OID I need for an SNMP
Custom sensor?
Add Sensor
Setting Description
Channel Name Enter a name for the channel in which the sensor shows the results for
the OID. Enter a string.
sensor.
sensor.
you add the sensor:
§ snmpcustomsensor
1902
OID Settings
OID Settings
Setting Description
OID Enter the OID of the SNMP object that you want to receive numeric data
from.
Most OIDs begin with 1.3.6.1. However, OIDs that start with 1.0, or
1.1, or 1.2 are also allowed. If you want to entirely disable the
validation of your entry, add the string norfccheck: to the beginning of the
OID, for example, norfccheck:2.0.0.0.1.
Value Type Select the expected numeric type of the results at the OID:
§ Absolute (unsigned integer): Integers without an operational sign, such
as 10 or 120.
§ Absolute (signed integer): Integers with an operational sign, such as -
12 or 120.
§ Absolute (float): Float values, such as -5.80 or 8.23.
§ Delta (counter): Counter values. PRTG calculates the difference

between the last and the current value. PRTG additionally divides the
delta value by a time period to indicate a speed value.
1903
Setting Description
multiplier. Use the default value 1 to not change the received value. Enter
an integer.
Use the default value 1 to not change the received value. Enter an integer.

change.
Sensor Display
Sensor Display
Setting Description


1904
Setting Description
other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
[Value] The single numeric value (int64) for a specified OID

More
KNOWLEDGE BASE
How do I find out which OID I need for an SNMP Custom sensor?


1905
VIDEO TUTORIAL
SNMP Custom sensor and SNMP Custom Library sensor

§ https://www.paessler.com/support/videos-and-webinars/videos/snmp-custom-and-library-sensor
1906
7.8.177 SNMP Custom Advanced Sensor
The SNMP Custom Advanced sensor monitors numeric values returned for object identifiers (OID) via the
Simple Network Management Protocol (SNMP).
The SNMP Library 2069 sensor automatically creates SNMP Custom Advanced sensors when the
Management Information Base (MIB) file that you import contains single values.
SNMP Custom Advanced Sensor
List 1912 .

§ Dutch: SNMP Aanpasbaar Geavanceerd
§ French: SNMP personnalisé avancé
§ German: SNMP (Benutzerdef. erweitert)
§ Japanese: SNMP
§ Portuguese: SNMP (customizado / avançado)
§ Russian: SNMP
1907
§ Spanish: SNMP (personalizado / avanzado)
Remarks
Remark Description
Custom sensor?
you add the sensor:
§ snmpcustomadvanced
§ snmpcustomsensor
1908
OID Settings
OID Settings
Setting Description
Channel #x Name Enter a name for the channel in which the sensor shows the results at the
OID. Enter a string.
Channel #x OID Enter the OID of the SNMP object from which you want to receive
numeric data.
Channel #x Value Type Select the expected numeric type of the results at the OID:
as 10 or 120.
12 or 120.

Absolute (float) and Delta (counter) are not compatible with the unit
Lookup.
Channel #x Unit Define the unit of the numeric data that this sensor receives from the OID:
1909
Setting Description
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
Sensors.
You cannot use the unit Lookup if you select the value type Delta
(counter) or Absolute (float). You are not able to create the sensor in
this case.
1910
Setting Description
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1911
Inherited Settings
Channel List
Channel Description
[Value] The numeric value for a specified OID (up to 10 OIDs are possible) that
refers to a specific SNMP device
More
KNOWLEDGE BASE


1912
7.8.178 SNMP Custom String Sensor
The SNMP Custom String sensor monitors a string returned by a specific object identifier (OID) via the
Simple Network Management Protocol (SNMP). It can check for keywords. If you want to set limits to
the channel value, you can also extract a numeric value contained in the string.
In the sensor message, the sensor shows the string that you search 1916 for and the reason for the
Warning or Down status.
The SNMP Library 2069 sensor automatically creates SNMP Custom String sensors when the
Management Information Base (MIB) file that you import contains string values.
SNMP Custom String Sensor
List 1921 .

§ Dutch: SNMP Aangepaste Tekenreeks
§ French: Chaîne personnalisée (SNMP)
§ German: SNMP-Zeichenfolge
§ Japanese: SNMP
§ Portuguese: Sequência de caracteres (customizado) (SNMP)
§ Russian: SNMP:
§ Spanish: Cadena (personalizado) (SNMP)
1913
Remarks
Remark Description
Custom sensor?
you add the sensor:
§ snmpcustomstringsensor
1914
OID Settings
OID Settings
Setting Description
OID Enter the OID of the SNMP object that you want to receive a string from.
Maximum String Length Define the maximum length of the string that PRTG receives from the
SNMP object at the OID. If the string is longer than this value, the sensor
shows the Down status. Enter an integer or leave the field empty.

change.
1915
Keyword Search
Keyw ord Search
Setting Description
Response Must Include Define the search string that must be part of the data that PRTG receives
(Down Status if Not from the SNMP object at the OID. You can enter a simple string in plain
Included) text or a regular expression (regex).

Down status.


1916
Setting Description
Response Must Not Define the search string that must not be part of the data that PRTG
Include (Down Status if receives form the SNMP object at the OID. You can enter a simple string
Included) in plain text or a regex.
Down status.


Response Must Include Define the search string that must be part of the data that PRTG receives
(Warning Status If Not from the SNMP object at the OID. You can enter a simple string in plain
Included) text or a regex.
Warning status.


Response Must Not Define the search string that must not be part of the data that PRTG
Include (Warning Status receives form the SNMP object at the OID. You can enter a simple string
If Included) in plain text or a regex.
1917
Setting Description
Warning status.


Extended Processing
Extended Processing
Setting Description
Interpret Result As Define the type of the received string:

§ String (default): Handle the result as a common string.
§ Bytes in hexadecimal notation: Handle the result as bytes in

hexadecimal notation. For example, select this option if you monitor
MAC addresses.
§ Bytes in decimal notation: Handle the result as bytes in decimal
notation. For example, select this option if you monitor IP addresses.
Numeric Value Extraction Define if you want to filter out a numeric value from the received string:
§ Do not use extraction (default): Do not extract a float value. Use the
result as a string value.
1918
Setting Description
§ Use a regular expression for extraction: Use a regular expression

(regex) to identify a numeric value in the string and to convert it to a
float value to use it, for example, with channel limits. Define below. See
also the example 1920 .
For more information, see section Channel Settings.
Regular Expression This setting is only visible if you select Use a regular expression for
extraction above.
Enter a regular expression to identify the numeric value that you want to
extract from the string returned by the SNMP object at the specified OID.
You can use capturing groups.
Make sure that the expression only returns numbers, including the
decimal and thousands separators.

Index of Capturing Group This setting is only visible if you select Use a regular expression for
extraction above.
If your regex uses capturing groups, specify which one captures the
number. Enter an integer or leave the field empty.
Decimal Separator This setting is only visible if you select Use a regular expression for
extraction above.
Define the character for the decimal separator of the number. Enter a
Thousands Separator This setting is only visible if you select Use a regular expression for
extraction above.
Define the character for the thousands separator of the number. Enter a
Sensor Display
Sensor Display
1919
Setting Description


other above.
procedure to do so.
Inherited Settings
Number Extraction with Regular Expression

If you want to extract a number in the response string via a regex, note that the index for captures in
this sensor is based on 1 (not on 0). Furthermore, capturing groups are not automatically created.
The example below illustrates 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, this is the percentage in the second parentheses.
Enter the following regex in the Regular Expression field:
(\d+\.\d+).*?(\d+\.\d+).*?(\d+\.\d+)
1920
As Index of Capturing Group, enter 3. This extracts the desired number 3.555.
The index must 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
Keep this note about index and capturing groups in mind when using number extraction.
It is not possible to match an empty string with the PRTG regex sensor search.
PRTG supports Perl Compatible Regular Expression (PCRE) regex. For more information, see
section Regular Expressions.
Channel List
Channel Description
Extracted Value The value extracted from the string (optional)

More
KNOWLEDGE BASE


1921
7.8.179 SNMP Custom String Lookup Sensor
The SNMP Custom String Lookup sensor monitors a string that a specific object identifier (OID) returns
via the Simple Network Management Protocol (SNMP). It can map the string directly to a sensor status
by using a defined lookup file.
Basically, this sensor does a "reverse lookup". You need to define all potential return strings in the
lookup file as text values, each in one lookup entry. Graphs and data tables show the value to which
the string is mapped, usually an integer (lookup type SingleInt). For more information, see section
Example 1925 .
SNMP Custom String Lookup Sensor
List 1926 .

§ Dutch: SNMP Aangepaste Tekst Lookup
§ French: Recherche chaînes personnalisée (SNMP)
§ German: SNMP-Zeichenfolge mit Lookup
§ Japanese: SNMP
§ Portuguese: Pesquisa da sequência de caracteres (customizado) (SNMP)
§ Russian: SNMP
§ Spanish: Búsqueda de cadena (personalizado) (SNMP)
Remarks
1922
Remark Description
channels.
Custom sensor?
Add Sensor
Setting Description
Channel Name Enter a name for the channel in which the sensor shows the results for
the OID. Enter a string.
sensor.
you add the sensor:
§ snmpcustomsensor
1923
OID Settings
OID Settings
Setting Description
OID Enter the OID of the SNMP object that you want to receive a string from.
Lookup Select a lookup file that is available in the \lookups\custom subfolder of

the PRTG program directory on the probe system.
The lookup file must contain all potential strings that the OID can
return.

change.
Sensor Display
Sensor Display
1924
Setting Description


other above.
procedure to do so.
Inherited Settings
Example
You must provide all possible return strings for this sensor in one lookup file. For example, consider
an OID that can return one of the three strings Good, Deficient, or Bad. Then you must define a
lookup file for this sensor that contains all these possible string values as text, each text value in one
lookup entry:
1925
<?xml version="1.0" encoding="UTF-8"?>
<ValueLookup id="mylookupfile" desiredValue="0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="PaeValueLookup.xsd">
<Lookups>
<SingleInt state="OK" value="0">
Good
</SingleInt>
<SingleInt state="Warning" value="1">
Deficient
</SingleInt>
<SingleInt state="Error" value="2">
Bad
</SingleInt>
</Lookups>
</ValueLookup>
If a retrieved string matches one of the text values, the sensor maps it into the defined integer ("reverse
lookup") that is shown, for example, in data graphs. Depending on the integer, the sensor shows the
respective status and converts the integer back to the original string to show it as a channel value. If the
OID returns a string that the lookup definition does not contain, the sensor shows the Down status with a
corresponding error message.
For example, you create an SNMP Custom String Lookup sensor, apply the example lookup definition
from above (store it into the \lookups\custom subfolder of the PRTG program directory), and the specified
OID returns the string Good. Then the sensor maps the string Good to the integer 0 that is shown in the
live graph of the sensor, for example. According to the status definition state="OK", the sensor status is
Up in this case. The integer 0 is converted back to the string Good, which is shown as the channel value.
The string match is not case-sensitive.
Use the lookup type SingleInt for this sensor. BitFields and ranges are not supported.
If you imported an SNMP library 2075 (this is an .oidlib file) that contains lookups (you can see this in
section Lookup in the MIB Importer), you can define your own sensor states for returning values.
Use the lookupname of the imported SNMP library as id parameter in a custom lookup definition. This
overrides the lookups that an .oidlib file might contain with your own status definitions. See section
Define Lookups for details about this mechanism.
Channel List
1926
Channel Description
[Value] The retrieved string value and its status, as defined in the corresponding
lookup file
More
KNOWLEDGE BASE


PAESSLER TOOLS
MIB Importer
§ https://www.paessler.com/tools/mibimporter
1927
7.8.180 SNMP Custom Table Sensor
The SNMP Custom Table sensor monitors entries from a table that is provided via the Simple Network
Management Protocol (SNMP). You can create one new sensor per table row. For each sensor, you can
define up to ten channels. Each channel shows the value of one defined table column.
The SNMP Library 2069 sensor automatically creates SNMP Custom Table sensors when the
Management Information Base (MIB) file that you import contains tables.
SNMP Custom Table Sensor
List 1934 .

§ Dutch: SNMP Aangepaste Tabel
§ French: Table personnalisée (SNMP)
§ German: SNMP (Benutzerdef. Tabelle)
§ Japanese: SNMP
§ Portuguese: Tabela (customizada) (SNMP)
§ Russian: SNMP
§ Spanish: Tabla (personalizado) (SNMP)
Remarks
1928
Remark Description
Custom sensor?
§ Knowledge Base: What can I monitor with the SNMP Custom Table
sensor?
Add Sensor
Setting Description
Table The sensor shows you the table that the OID returns. Select the table
rows that contain the data that you want to monitor. PRTG creates one
sensor for each table row that you select.
you add the sensor:
§ snmpcustomsensor
§ snmpcustomtable
1929
SNMP Table
SNMP Table
Setting Description
Table OID Enter the object identifier (OID) of the SNMP table that you want to
monitor. The OID must directly point to an object that represents an
SNMP table. PRTG creates one SNMP Custom Table sensor for each
table row that you select.
If you do not enter an OID, you cannot proceed with channel creation.
Table Specific
Table Specific
Setting Description
Identifier This is the value of the column that you selected as the Identification
Column during sensor creation. PRTG also displays it in the sensor name
to distinguish it from other sensors you created for the same table with
other table rows.
Identification Column Define the identification column for the sensors that you want to create.
The sensors use this column to uniquely identify each table row.
1930
Setting Description
We recommend that you use a unique identification column because

it allows the sensors to keep track of changing indexes.
The value of the column that you select as identification column
replaces the [rowidentifier] in the sensor name. This lets you
distinguish sensors that you create for the same SNMP table.
After sensor creation, this setting shows the table column that you
chose as identification column.
Channel #x Name Enter a name for the channel in which the sensor shows the desired
result. Enter a string.
Channel #x Column Select the table column that, together with the table row, points to the
value that you want to monitor in this channel. You can choose between
the available columns of the table that you monitor.
Channel #x Value Type Select the expected numeric type of the results at the OID:
as 10 or 120.
12 or 120.

Absolute (float) and Delta (counter) are not compatible with the unit
Lookup.
See below 1930 for other channel settings that you can also change
after sensor creation.
This sensor monitors numeric values only. Make sure that you do not
select columns that return strings because they lead to the Down
status. For example, if you monitor an ifTable, we recommend that you do
not select an ifDescr column because this results in an error.
Channel #x Unit Define the unit of the data that this sensor receives in this channel:
§ BytesBandwidth
§ BytesMemory
1931
Setting Description
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
Sensors.
You cannot use the unit Lookup if you select the value type Delta
(counter) or Absolute (float). You are not able to create the sensor in
this case.
1932
Setting Description

All channels that you define during the creation of an SNMP
Custom Table sensor are the same for all sensors for each table
row.
Sensor Display
Sensor Display
Setting Description

other above.
procedure to do so.
1933
Inherited Settings
Channel List
Channel Description
[Value] The returned numeric values in up to ten channels per table row
More
KNOWLEDGE BASE
What can I monitor with the SNMP Custom Table sensor?



Can I monitor UPS systems complying with the UPS MIB (RFC-1628) with PRTG?
1934
7.8.181 SNMP Custom v2 Sensor (BETA)
The SNMP Custom v2 sensor monitors a single parameter that is returned by a specific object identifier
(OID) or Abstract Syntax Notation One (ASN.1) Management Information Base (MIB) via the Simple
all.
SNMP Custom v2 Sensor
List 1940 .

§ Dutch: SNMP Aangepast v2
§ French: SNMP personnalisé v2
§ German: SNMP (Benutzerdef.) v2
§ Japanese: SNMP v2
§ Portuguese: SNMP (customizado) v2
§ Russian: SNMP Custom v2
§ Simplified Chinese: SNMP v2

§ Spanish: SNMP (personalizado) v2
Remarks
1935
Remark Description
Custom sensor?
you add the sensor:
§ snmp
§ snmpcustomsensor
1936
SNMP Custom Specific
SNMP Custom Specific
Setting Description
OID or ASN.1 MIB Name Enter the OID or ASN.1 MIB name of the SNMP object that you want to
receive numeric data from.
Value Type Select the expected numeric type of the result:

§ Absolute (unsigned integer) (default): Integers without an operational
sign, such as 10 or 120.
12 or 120.
§ Absolute (floating point): Float values, such as -5.80 or 8.23.
§ Delta (unsigned integer): Integers without an operational sign, such as

10 or 120. The sensor calculates the difference between the last value
and the current value.
§ Time (unsigned integer): Integers without an operational sign, such as
10 or 120. The sensor measures the response time.
Channel Unit Define the unit of the numeric data that this sensor receives. The following
options are only visible if you select Absolute (unsigned integer), Absolute
(signed integer), Absolute (floating point), or Delta (unsigned integer) as
Value Type:
1937
Setting Description
§ Custom
§ Count (default)
§ Percent (CPU)
§ Temperature (°C)
§ Bytes (memory)
§ Bytes (disk)
§ Bytes (bandwidth)
§ Bytes per second (disk)
§ Bytes per second (network)
The following options are only visible if you select Time (unsigned integer)
as Value Type:
§ Time (milliseconds)
§ Time (seconds, default)
§ Time (hours)
Sensors.
multiplier. Use the default value 1 to not change the received value. Enter
an integer.
Use the default value 1 to not change the received value. Enter an integer.
Sensor Display
Sensor Display
1938
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
Do not store the sensor result.
master node.
1939
Inherited Settings
Channel List
Channel Description
Result The single numeric value for a specified OID

More
KNOWLEDGE BASE


How do I use Management Information Base (MIB) folders with the SNMP Custom v2 sensor?
VIDEO TUTORIAL
SNMP Custom sensor and SNMP Custom Library sensor

§ https://www.paessler.com/support/videos-and-webinars/videos/snmp-custom-and-library-sensor
1940
7.8.182 SNMP Dell EqualLogic Logical Disk Sensor
The SNMP Dell EqualLogic Logical Disk sensor monitors a volume of a Dell EqualLogic storage system
via the Simple Network Management Protocol (SNMP).
SNMP Dell EqualLogic Logical Disk Sensor
List 1944 .

§ Dutch: SNMP Dell EqualLogic Logische Schijf
§ French: Dell EqualLogic disque logique (SNMP)
§ German: SNMP Dell EqualLogic Logischer Datenträger
§ Japanese: SNMP Dell EqualLogic
§ Portuguese: Disco lógico Dell EqualLogic (SNMP)
§ Russian: SNMP Dell EqualLogic

§ Simplified Chinese: SNMP Dell EqualLogic
§ Spanish: Disco lógico Dell EqualLogic (SNMP)
Remarks
1941
Remark Description
channels.
you add the sensor:
§ dell
§ dellequallogic
§ snmpdell
Dell EqualLogic Specific
1942
Setting Description
Volumes The volume that this sensor monitors.
Member ID The member ID of the volume that this sensor monitors.
Volume ID The ID of the volume that this sensor monitors.
Volume Description The description of the volume that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1943
Inherited Settings
Channel List
Channel Description
Availability The availability status

§ Down status: Missing Members
Average Write Latency The average write latency
Connections The number of connections
Operations Status The operations status

§ Warning status: Available But No New Connections
§ Down status: Not Available, Not Available Due To, Not Available Due To
Internal Error, Not Available Due To Lost Cached Blocks, Not Available
Due To Members Offline, Not Available Due To Missing Pages, Not
Available Due To No Space For Auto Grow, Not Available Due To Snap
Reserve Met, Not Available Due To Thin Max Growth Met,
1944
Channel Description
More
KNOWLEDGE BASE


1945
7.8.183 SNMP Dell EqualLogic Member Health Sensor
The SNMP Dell EqualLogic Member Health sensor monitors the health of an array member of an
EqualLogic storage system via the Simple Network Management Protocol (SNMP).
SNMP Dell EqualLogic Member Health Sensor
List 1949 .

§ Dutch: SNMP Dell EqualLogic Lid Gezondheid
§ French: Dell EqualLogic état du composant (SNMP)
§ German: SNMP Dell EqualLogic Member-Zustand
§ Portuguese: Funcionamento do membro Dell EqualLogic (SNMP)
1946
§ Russian: Dell EqualLogic SNMP
§ Spanish: Salud de miembro Dell EqualLogic (SNMP)
Remarks
Remark Description
SNMP v1 § This sensor works with SNMP v2c and SNMP v3. It does not support
SNMP v1. Make sure that you set the correct SNMP Version in the
settings of an object that is higher in the object hierarchy.
channels.
you add the sensor:
§ dell
§ dellequallogic
§ snmpdell
1947
Setting Description
Array Member The name of the member that this sensor monitors.
Group ID The group ID of the member that this sensor monitors.
Member ID The ID of the group member that this sensor monitors.
Sensor Display
Sensor Display
Setting Description

1948
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Average Read Latency The average write latency
1949
Channel Description
Fan Power Cooling The power of the cooling module fan

Module [#] Fan [#]
Member Health Status The member health status

§ Down status: Critical, Unknown
Member Status The member status

§ Warning status: Vacated, Vacating
§ Down status: Offline
Number of Spares The number of spare drives

Power Supply Power The power supply cooling module status

Cooling Module [#]
§ Up status: On and Operating
§ Down status: Failed or No Data, No AC Power
RAID Status The RAID status

§ Up status: Expanding, Mirroring, Ok, Verifying
§ Warning status: Degraded, Reconstructing
§ Down status: Catastrophic Loss, Failed
Storage Free % The free storage (%)
Temperature Control The control module temperature

Module [#] [Module]
More
KNOWLEDGE BASE
1950

1951
7.8.184 SNMP Dell EqualLogic Physical Disk Sensor
The SNMP Dell EqualLogic Physical Disk sensor monitors a disk in a Dell EqualLogic storage system
SNMP Dell EqualLogic Physical Disk Sensor
List 1955 .

§ Dutch: SNMP Dell EqualLogic Fysieke Schijf
§ French: Dell EqualLogic disque physique (SNMP)
§ German: SNMP Dell EqualLogic Physikalischer Datenträger
§ Portuguese: Disco físico Dell EqualLogic (SNMP)
§ Russian: Dell EqualLogic SNMP

§ Spanish: Disco físico Dell EqualLogic (SNMP)
Remarks
1952
Remark Description
channels.
you add the sensor:
§ dell
§ dellequallogic
§ snmpdell
1953
Setting Description
Group ID The group ID of the physical disk that this sensor monitors.
Member ID The group member ID of the physical disk that this sensor monitors.
Disk Slot The slot number of the physical disk that this sensor monitors.
Serial Number The serial number of the physical disk that this sensor monitors.
Manufactured The production date of the physical disk that this sensor monitors. If this
field is empty, the physical disk does not provide information about the
date (this depends on the manufacturer).
Sensor Display
Sensor Display
1954
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
1955
Channel Description
Disk Status The disk heath status

§ Up status: Online, Spare
§ Warning status: Alt-Sig, History Of Failures, Replacement
§ Down status: Encrypted, Failed, Not Approved, Offline, Preempt Failed,

Too Small, Unhealthy, Unsupported Version
Failed Transfers The number of failed transfers
More
KNOWLEDGE BASE


1956
7.8.185 SNMP Dell Hardware Sensor
The SNMP Dell Hardware sensor monitors performance counters on a Dell hardware device via the
The data that you can monitor with this sensor depends on the available performance counters on
the target system.
The SNMP Dell Hardware sensor does not appear as a running sensor, instead it is created as an
SNMP Custom Advanced 1907 sensor or an SNMP Custom Table 1928 sensor with up to 10 channels
per category.
SNMP Dell Hardw are Sensor
List 1960 .

§ Dutch: SNMP Dell Hardware
§ French: Dell matériel (SNMP)
§ German: SNMP Dell Hardware
§ Japanese: SNMP Dell
§ Portuguese: Hardware Dell (SNMP)
§ Russian: Dell SNMP

§ Simplified Chinese: SNMP Dell
§ Spanish: Hardware Dell (SNMP)
Remarks
1957
Remark Description
Dell OpenManage Server § This sensor requires the Dell OpenManage Server Administrator on the
Administrator target system.
§ Make sure that you enable SNMP in the OMSA.
For more information, see the Knowledge Base: What do I need to

monitor Dell servers?
Counters § Select the counters that you want to monitor with caution. We
recommend that you select only a few counters in the Add Sensor
dialog. Use the search in the table header to filter for specific counters.
Selecting too many counters might result in thousands of sensors or
the sensor creation is canceled.
Knowledge Base § Knowledge Base: What do I need to monitor Dell servers?
you add the sensor:
§ dell
1958
Dell Hardware Specific
Dell Hardw are Specific
Setting Description
Interface The name of the interface (performance counter) that this sensor
monitors.
Unit String Define the unit of the numeric data that the sensor receives at the
specified OID. Enter a string.
multiplier. Enter an integer.
Enter an integer.

change.
Sensor Display
Sensor Display
1959
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
1960
Channel Description
[Performance Counter] The value returned by a specific Dell hardware OID, for example
§ Data about the system management software
§ Data about system status
§ Information about chassis and BIOS
§ Various hardware parameters
§ Other valuable data
More
KNOWLEDGE BASE
What do I need to monitor Dell servers?



1961
7.8.186 SNMP Dell PowerEdge Physical Disk Sensor
The SNMP Dell PowerEdge Physical Disk sensor monitors a physical disk in a Dell PowerEdge server
SNMP Dell Pow erEdge Physical Disk Sensor
List 1965 .

§ Dutch: SNMP-Dell PowerEdge Fysieke Schijf
§ French: Dell PowerEdge disque physique (SNMP)
§ German: SNMP Dell PowerEdge Physikalischer Datenträger
§ Japanese: SNMP Dell PowerEdge
§ Portuguese: Disco físico Dell PowerEdge (SNMP)
§ Russian: Dell PowerEdge SNMP

§ Simplified Chinese: SNMP Dell PowerEdge
§ Spanish: Disco físico Dell PowerEdge (SNMP)
Remarks
1962
Remark Description
Dell OpenManage Server § This sensor requires Integrated Dell Remote Access Controller (iDRAC)
Administrator or iDRAC 7 7 or the Dell OpenManage Server Administrator (OMSA) on the target
system.

You can also monitor Dell PowerEdge servers with this sensor via
iDRAC 7.
channels.
Knowledge Base § Knowledge Base: What do I need to monitor Dell servers?
§ Knowledge Base: I can't add Dell PowerEdge sensors to PRTG. What

can I do?
§ Knowledge Base: My Dell PowerEdge sensor fails to validate disks and
I can't add it. What can I do?
you add the sensor:
§ dell
§ physicaldisk
§ snmpdell
§ snmpdellphysicaldisksensor
1963
Dell PowerEdge Physical Disk Settings
Dell Pow erEdge Physical Disk Settings
Setting Description
Data Source The interface that PRTG uses to get monitoring data. This is either Dell
OMSA or iDRAC.
Sensor Display
Sensor Display
Setting Description


1964
Setting Description
other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Component Status The component status
§ Up status: OK
§ Warning status: Non Critical
§ Down status: Critical, Non Recoverable, Other, Unknown
Disk State The disk status

§ Up status: Non-Raid, Online, Ready
§ Warning status: Foreign
§ Down status: Blocked, Critical, Failed, Non Recoverable, Other,

Removed, Unknown
1965
Channel Description
Roll Up Status The roll up status

§ Up status: OK
This channel requires that Dell OMSA is installed on the target

system.
S.M.A.R.T. Warning The S.M.A.R.T. warning status

§ Up status: No
§ Down status: Yes
More
KNOWLEDGE BASE

I can't add Dell PowerEdge sensors to PRTG. What can I do?

My Dell PowerEdge sensor fails to validate disks and I can't add it. What can I do?


1966
7.8.187 SNMP Dell PowerEdge System Health Sensor
The SNMP Dell PowerEdge System Health sensor monitors the system health of a Dell PowerEdge
server via the Simple Network Management Protocol (SNMP).
SNMP Dell Pow erEdge System Health Sensor
List 1970 .

§ Dutch: SNMP Dell PowerEdge Systeemstatus
§ French: Dell PowerEdge état du système (SNMP)
§ German: SNMP Dell PowerEdge Systemzustand
§ Japanese: SNMP Dell PowerEdge
§ Portuguese: Saúde do sistema Dell PowerEdge (SNMP)
§ Russian: Dell PowerEdge SNMP

§ Simplified Chinese: SNMP Dell PowerEdge
§ Spanish: Salud de sistema Dell PowerEdge (SNMP)
1967
Remarks
Remark Description
Dell OpenManage Server § This sensor requires Integrated Dell Remote Access Controller (iDRAC)
Administrator or iDRAC 7 7 or the Dell OpenManage Server Administrator (OMSA) on the target
system.

You can also monitor Dell PowerEdge servers with this sensor via
iDRAC 7.
channels.
Knowledge Base § Knowledge Base: Why does my Dell PowerEdge System Health
sensor show a power unit status error after iDRAC update?
§ Knowledge Base: What do I need to monitor Dell servers?
§ Knowledge Base: I can't add Dell PowerEdge sensors to PRTG. What

can I do?
you add the sensor:
§ dell
1968
§ snmpdell
§ snmpdellsystemhealthsensor
§ systemhealth
Dell PowerEdge System Health Specific
Dell Pow erEdge System Health Specific
Setting Description
Chassis The chassis that this sensor monitors.
Channel Mask The channel mask that describes which channels are available.
Data Source The interface that PRTG uses to get monitoring data. This is either Dell
OMSA or iDRAC.
Sensor Display
Sensor Display
Setting Description
1969
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Ampere Status The ampere status

§ Up status: OK
Battery Status The battery status

§ Up status: OK
1970
Channel Description
Chassis Status The chassis status

§ Up status: OK
Cooling Device Status The cooling device status

§ Up status: OK
Cooling Unit Status The cooling unit status

§ Up status: OK
Global System Status The global system status
§ Up status: OK
Intrusion Status The intrusion status

§ Up status: OK
Memory Device Status The memory device status

§ Up status: OK
1971
Channel Description

§ Up status: OK
Power Unit Status The power unit status

§ Up status: OK
Processor Status The processor status

§ Up status: OK
Temperature Status The temperature status

§ Up status: OK
Voltage Status The voltage status

§ Up status: OK
More
KNOWLEDGE BASE
Why does my Dell PowerEdge System Health sensor show a power unit status error after iDRAC
update?

1972
I can't add Dell PowerEdge sensors to PRTG. What can I do?


1973
7.8.188 SNMP Disk Free Sensor
The SNMP Disk Free sensor monitors the free disk space on a logical disk via the Simple Network
SNMP Disk Free Sensor
List 1977 .

§ Dutch: SNMP vrije schijf ruimte
§ French: Espace disponible disque (SNMP)
§ German: SNMP Datenträgerspeicher
§ Japanese: SNMP
§ Portuguese: Disco livre (SNMP)
§ Russian: SNMP
§ Spanish: Espacio libre en disco (SNMP)
Remarks
1974
Remark Description
OID values § This sensor uses more generic object identifier (OID) values than the
SNMP Linux Disk Free 2078 sensor.
you add the sensor:
§ diskfree
§ diskspacesensor
§ snmpdiskfreesensor
§ snmp
Disk Free Settings
Disk Free Settings
1975
Setting Description
Disk The name of the disk that this sensor monitors.

monitoring data.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1976
Inherited Settings
Channel List
Channel Description

More
KNOWLEDGE BASE


1977
7.8.189 SNMP Disk Free v2 Sensor (BETA)
The SNMP Disk Free v2 sensor monitors the free disk space on a logical disk via the Simple Network
Management Protocol (SNMP). The sensor uses HOST-RESOURCES-V2-MIB::hrStorageTable.
SNMP Disk Free v2 Sensor
List 1982 .

§ Dutch: SNMP Vrije Schijf Ruimte v2
§ French: Espace disque disponible v2 (SNMP)
§ German: SNMP Datenträgerspeicher v2
§ Portuguese: Disco livre (SNMP) v2
§ Russian: SNMP Disk Free v2
§ Simplified Chinese: SNMP 2

§ Spanish: Espacio libre en disco (SNMP) v2
Remarks
1978
Remark Description
you add the sensor:
§ diskfree
§ diskspacesensor
§ snmp
1979
SNMP Disk Free Specific
SNMP Disk Free Specific
Setting Description

monitoring data.
Type The type of the disk that this sensor monitors.
Size The size of the disk that this sensor monitors.
Sensor Display
Sensor Display
Setting Description
1980
Setting Description



other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
Do not store the sensor result.
master node.
1981
Inherited Settings
Channel List
Channel Description

Total Space The total space
More
KNOWLEDGE BASE


1982
7.8.190 SNMP Fujitsu System Health v2 Sensor
The SNMP Fujitsu System Health v2 sensor monitors the status of a Fujitsu PRIMERGY server via the
integrated Remote Management Controller (iRMC) and Simple Network Management Protocol (SNMP).
The sensor might also work on other Fujitsu devices that have an iRMC available like PRIMEQUEST
servers, some storage systems of the ETERNUS product line, and CELSIUS workstations in racks.
SNMP Fujitsu System Health v2 Sensor
List 1987 .

§ Dutch: SNMP Fujitsu Systeemstatus v2
§ French: Fujitsu état du système v2 (SNMP)
§ German: SNMP Fujitsu Systemzustand v2
§ Japanese: SNMP Fujitsu v2

§ Portuguese: Saúde do sistema Fujitsu (SNMP) v2
§ Russian: Fujitsu SNMP, 2

§ Simplified Chinese: SNMP Fujitsu 2
§ Spanish: Salud de sistema Fujitsu (SNMP) v2
1983
Remarks
Remark Description
SNMP § This sensor requires SNMP to be enabled in the iRMC via ServerView.
Parent device § Use an iRMC interface as the parent device for this sensor.
SNMP v1 § This sensor does not support SNMP v1.
iRMC S5 § As of iRMC S5, additional counters for physical disks and logical disks
are supported.
channels.
you add the sensor:
§ fujitsu
§ irmc
§ snmp
§ snmpfujitsusystemhealthsensor
§ systemhealth
1984
System Specific
System Specific
Setting Description
Measurement The type of measurement that this sensor monitors.
Sensor Version The version of the sensor definition that was used to create this sensor.
Identifier The value that the sensor uses to find the component in the OID table.
The identifier has the following format: RowIndex | Unique |
Measurement. For example, 1.1|BATT 3.0V|Voltage.
OID Index The OID table index that this sensor uses.
Debug Options
Debug Options
Setting Description
1985
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1986
Inherited Settings
Channel List
Channel Description
CPU Status The CPU status

§ Up status: OK
Fan Status The fan status
§ Up status: OK
Memory Module Status The memory module status

§ Up status: OK
Overall Status The overall status

§ Up status: OK
1987
Channel Description

§ Up status: OK
Temperature Status The temperature status

§ Up status: OK
Voltage Status The voltage status

§ Up status: OK
The sensor can also show CPU speed and core count, fan speed, number of correctable and
uncorrectable errors of the memory module, service processor battery status, condition of the power
supply, power limit status, and power consumption.
More
KNOWLEDGE BASE


1988
7.8.191 SNMP Hardware Status Sensor
The SNMP Hardware Status sensor monitors the status of a server's hardware component via the Simple
SNMP Hardw are Status Sensor
List 1992 .

§ Dutch: SNMP Hardware Status
§ French: Statut matériel (SNMP)
§ German: SNMP Hardwarezustand
§ Japanese: SNMP
§ Portuguese: Status do hardware (SNMP)
§ Russian: SNMP
§ Spanish: Estado de hardware (SNMP)
Remarks
Remark Description
1989
Remark Description
channels.
you add the sensor:
§ hardwarestatus
Hardware Specific
Hardw are Specific
1990
Setting Description
Hardware Components The hardware component that this sensor monitors.
Product ID The product ID of the hardware component that this sensor monitors.
Description The description of the hardware component that this sensor monitors.
Type The type of the hardware component that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
1991
Inherited Settings
Channel List
Channel Description
Status The hardware component status

§ Up status: Running
§ Warning status: Warning, Testing
§ Down status: Down, Unknown
More
KNOWLEDGE BASE


1992
7.8.192 SNMP HP LaserJet Hardware Sensor
The SNMP HP LaserJet Hardware sensor monitors performance counters on an HP LaserJet hardware
device via the Simple Network Management Protocol (SNMP).
The SNMP HP LaserJet Hardware sensor does not appear as a running sensor, instead it is created
as an SNMP Custom Advanced 1907 sensor.
The following performance counters are available:
§ Toner/Status
§ Paper/Status
§ Jam/Status
SNMP HP LaserJet Hardw are Sensor
List 1996 .

§ Dutch: SNMP HP LaserJet Hardware
§ French: HP LaserJet matériel (SNMP)
§ German: SNMP HP LaserJet Hardware
§ Japanese: SNMP HP LaserJet
§ Portuguese: Hardware HP LaserJet (SNMP)
§ Russian: HP LaserJet SNMP

§ Simplified Chinese: SNMP HP LaserJet
§ Spanish: Hardware HP LaserJet (SNMP)
1993
Remarks
Remark Description
channels.
you add the sensor:
§ hplaserjet
HP LaserJet Specific
HP LaserJet Specific
1994
Setting Description
Interface The name of the interface (performance counter) that this sensor
monitors.

change.
Sensor Display
Sensor Display
Setting Description


other above.
1995
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Jam The paper jam status
§ Up status: No Jam Detected
§ Down status: Paper Jam Detected
Paper The paper status

§ Up status: Paper Okay
§ Down status: Manual Paper Feed Required, Out Of Paper Or No

Cassette Loaded
Toner The toner status

§ Up status: Toner Okay
§ Warning status: Toner Low
§ Down status: No Toner Cartridge Loaded
1996
More
KNOWLEDGE BASE

1997
7.8.193 SNMP HPE BladeSystem Blade Sensor
The SNMP HPE BladeSystem Blade sensor monitors the status of an HPE BladeSystem via the Simple
SNMP HPE BladeSystem Blade Sensor
List 2001 .

§ Dutch: SNMP HPE BladeSystem Blade
§ French: HPE BladeSystem serveur blade (SNMP)
§ German: SNMP HPE BladeSystem Blade
§ Japanese: SNMP HPE BladeSystem
§ Portuguese: Blade HPE BladeSystem (SNMP)
§ Russian: HPE BladeSystem SNMP

§ Simplified Chinese: SNMP HPE BladeSystem
§ Spanish: Blade HPE BladeSystem (SNMP)
Remarks
1998
Remark Description
Parent device § This sensor requires that the IP address or Domain Name System
(DNS) name in the settings of the parent device points to the HPE
BladeSystem Enclosure hosting the Onboard Administrator.
channels.
you add the sensor:
§ blade
§ bladesystem
§ hpe
§ snmp
HPE BladeSystem Specific
HPE BladeSystem Specific
1999
Setting Description
Server Blades The server blade that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
2000
Channel List
Channel Description
Blade Status The blade status

§ Up status: OK
§ Unknown status: Other
Power Status The power status

§ Up status: On, Rebooting
§ Warning status: Off, Power Stagged Off, Unknown
More
KNOWLEDGE BASE


2001
7.8.194 SNMP HPE BladeSystem Enclosure System Health Sensor
The SNMP HPE BladeSystem Enclosure Health sensor monitors the health of an HPE BladeSystem
device via the Simple Network Management Protocol (SNMP).
SNMP HPE BladeSystem Enclosure HealthSensor
List 2004 .

§ Dutch: SNMP HPE BladeSystem Behuizing Status
§ French: HPE BladeSystem état du boîtier (SNMP)
§ German: SNMP HPE BladeSystem Gehäuse-Zustand
§ Japanese: SNMP HPE BladeSystem
§ Portuguese: Saúde do gabinete HPE BladeSystem (SNMP)
§ Russian: HPE BladeSystem SNMP

§ Simplified Chinese: SNMP HPE BladeSystem
§ Spanish: Salud de gabinete HPE BladeSystem (SNMP)
Remarks
2002
Remark Description
Parent device § This sensor requires that the IP address or Domain Name System
(DNS) name in the settings of the parent device points to the HPE
BladeSystem Enclosure hosting the Onboard Administrator.
channels.
you add the sensor:
§ blade
§ bladesystem
§ health
§ hpe
§ snmp
§ systemhealth
2003
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2004
Channel Description
Enclosure Condition The enclosure condition
§ Up status: OK
Enclosure Manager The enclosure manager condition

Condition
§ Up status: OK
More
KNOWLEDGE BASE

2005
7.8.195 SNMP HPE ProLiant Logical Disk Sensor
The SNMP HPE ProLiant Logical Disk sensor monitors a logical disk in an HPE server via the Simple
SNMP HPE ProLiant Logical Disk Sensor
List 2009 .

§ Dutch: SNMP HPE ProLiant Logische Schijf
§ French: HPE ProLiant disque logique (SNMP)
§ German: SNMP HPE ProLiant Logischer Datenträger
§ Japanese: SNMP HPE ProLiant
§ Portuguese: Disco lógico HPE ProLiant (SNMP)
§ Russian: HPE ProLiant SNMP

§ Simplified Chinese: SNMP HPE ProLiant
§ Spanish: Disco lógico HPE ProLiant (SNMP)
Remarks
2006
Remark Description
HPE system § For Gen10 servers: This sensor requires HPE Agentless Management
management tools and the HPE Agentless Management Service on the target system.
§ For Gen10 servers: Use the HPE Integrated Lights Out (iLO) interface
as the parent device.
§ For Gen9 servers or earlier: This sensor requires HPE Insight

Management Agents and HPE Insight Management WBEM Providers
on the target system.
§ For Gen9 servers or earlier, this sensor requires a specific HPE system
management tool to be installed on the target system to report data via
SNMP: HPE Insight Management Agents. To receive SNMP data from
redundant array of independent disks (RAID) controllers, the sensor
also requires HPE Insight Management Agents. For Gen10 servers,
this sensor no longer requires HPE system management tools.
§ Instead, the sensor requires the HPE Agentless Management Service
to be installed on the target system.
For more information and download links, see the Knowledge Base:
Monitor HP ProLiant via SNMP?
For Gen9 servers or earlier, some of the HPE object identifiers (OID) that
this sensor uses are only accessible via the iLO interface. If this
sensor throws an error that it cannot find "such device types", create
a device that points to the address of the HPE iLO interface (if available)
and add the sensor to this device. We recommend that you use the
Agentless Management feature with configured SNMP. You can set this
up in the iLO configuration interface under Administration | Management |
SNMP Settings. For Gen10 servers, use the HPE iLO interface as parent
device for this sensor.
iLO versions § This sensor supports iLO as of iLO 3. We recommend that you use at
least iLO 4.
channels.
2007
you add the sensor:
§ hpe
§ logicaldisk
§ snmphpe
§ snmphpelogicaldisksensor
HPE ProLiant Logical Disk Settings
HPE ProLiant Logical Disk Settings
Setting Description
Sensor Display
Sensor Display
2008
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Completion The completion (%)

This is only important when the disk status is "Reconstructing" or
"Expanding" and illustrates the progress of this task.
2009
Channel Description
Disk Status The disk status

§ Up status: Expanding, Ok, Rebuilding
§ Warning status: Ready For Rebuild, Recovering, Unconfigurated
§ Down status: Bad Connect, Erasing, Failed, Multipath Access

Degraded, Not Available, Overheating, Queued For Expansion,
Shutdown, Wrong Drive,
More
KNOWLEDGE BASE


2010
7.8.196 SNMP HPE ProLiant Memory Controller Sensor
The SNMP HPE ProLiant Memory Controller sensor monitors a memory controller in an HPE server via
the Simple Network Management Protocol (SNMP).
SNMP HPE ProLiant Memory Controller Sensor
List 2014 .

§ Dutch: SNMP HPE ProLiant Geheugencontroller
§ French: HPE ProLiant contrôleur de mémoire (SNMP)
§ German: SNMP HPE ProLiant Speichercontroller
§ Portuguese: Controlador de memória HPE ProLiant (SNMP)

§ Spanish: Controlador de memoria HPE ProLiant (SNMP)
2011
Remarks
Remark Description
least iLO 4.
channels.
Modules § If modules are inserted at a later point, you must add this sensor anew.
2012
Remark Description
Knowledge Base § Knowledge Base: Which lookup values are supported by the SNMP
HPE ProLiant Memory Controller sensor?
you add the sensor:
§ hpe
§ memorycontroller
§ snmphpe
§ snmphpememorycontrollersensor
HPE ProLiant Memory Controller Settings
HPE ProLiant Memory Controller Settings
Setting Description
Controller The name of the controller that this sensor monitors.
2013
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2014
Channel Description
Controller Condition The controller condition

§ Up status: OK
Controller Error Status The controller error status

§ Up status: Advanced Ecc, Lock Step, Memory Raid, Mirrored, No
Error, OnlineSpare
§ Down status: Bus Error, Config Error, Dimm Ecc Error, Lock Step
Error, Mirrored Dimm Error, Power Error, Raid Dimm Error, Unlock Error
Module [#] Condition The module condition

§ Up status: OK
§ Down status: Degraded, Failed
Module [#] Status The module status

§ Up status: Add, Good, Present
§ Warning status: Not Present, Upgrade
§ Down status: Bad Config, Degraded, Does Not Match, Missing, Not
Supported
More
KNOWLEDGE BASE
Which lookup values are supported by the SNMP HPE ProLiant Memory Controller sensor?
2015


2016
7.8.197 SNMP HPE ProLiant Network Interface Sensor
The SNMP HPE ProLiant Network Interface sensor monitors a network interface in an HPE server via the
SNMP HPE ProLiant Netw ork Interface Sensor
List 2020 .

§ Dutch: SNMP HPE ProLiant Netwerkinterface
§ French: HPE ProLiant interface réseau (SNMP)
§ German: SNMP HPE ProLiant Netzwerkschnittstelle
§ Portuguese: Interface de rede HPE ProLiant (SNMP)

§ Spanish: Interfaz de red HPE ProLiant (SNMP)
2017
Remarks
Remark Description
least iLO 4.
Sensor creation § During sensor creation, the status of each available network interface is
shown. If this status is Link Failure, it is still possible to add a sensor
for the respective interface. Though, most likely the sensor for this
interface does not work correctly. The error message in this case is No
Such Name (SNMP error # 2).
2018
you add the sensor:
§ hpe
§ snmphpe
§ snmphpenetworkinterfacesensor
HPE ProLiant Network Interface Settings
HPE ProLiant Netw ork Interface Settings
Setting Description
Network Interfaces The name of the network interface that this sensor monitors.
Sensor Display
Sensor Display
2019
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Alignment Errors The number of alignment errors
Bad Frames Received The number of bad frames received
2020
Channel Description
Bad Frames Transmitted The number of bad frames transmitted
Carrier Sense Errors The number of carrier sense errors
Excessive Collisions The number of excessive collisions
FCS Errors The number of FCS errors
Frames Too Long The number of frames that are too long
Good Frames Received The number of good frames received
Good Frames The number of good frames transmitted

Transmitted
Late Collisions The number of late collisions

More
KNOWLEDGE BASE



2021
7.8.198 SNMP HPE ProLiant Physical Disk Sensor
The SNMP HPE ProLiant Physical Disk sensor monitors a physical disk in an HPE server via the Simple
SNMP HPE ProLiant Physical Disk Sensor
List 2025 .

§ Dutch: SNMP HPE ProLiant Fysieke Schijf
§ French: HPE ProLiant disque physique (SNMP)
§ German: SNMP HPE ProLiant Physikalischer Datenträger
§ Portuguese: Disco físico HPE ProLiant (SNMP)

§ Spanish: Disco físico HPE ProLiant (SNMP)
2022
Remarks
Remark Description
least iLO 4.
channels.
2023
Remark Description
"Limited Monitoring" § The sensor only shows Disk Status and no other channels if it runs in
mode "Limited Monitoring" mode. For more information, see the Knowledge
Base: SNMP HPE ProLiant Physical Disk sensor not showing all
information.
you add the sensor:
§ hpe
§ physicaldisk
§ snmphpe
§ snmphpephysicaldisksensor
HPE ProLiant Physical Disk Settings
HPE ProLiant Physical Disk Settings
Setting Description
Disk The ID of the physical disk that this sensor monitors.
2024
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2025
Channel Description
Corrected Read Errors The corrected read errors
Corrected Write Errors The corrected write errors
§ Up status: OK
§ Warning status: Erase Done, Erase Queued, Erasing, Not

Authenticated, Predictive Failure
§ Down status: Failed, SSD Wear Out
Drive Condition The drive condition

§ Up status: OK
Hard Read Errors The number of hard read errors
Hard Write Errors The number of hard write errors
S.M.A.R.T. Status The S.M.A.R.T. status

§ Up status: OK
§ Warning status: Replace Drive
Sectors Read The number of sectors read
Sectors Written The number of sectors written
Threshold Passed If the threshold is passed

§ Up status: No
2026
Channel Description
§ Down status: Yes
More
KNOWLEDGE BASE
SNMP HPE ProLiant Physical Disk sensor not showing all information



2027
7.8.199 SNMP HPE ProLiant System Health Sensor
The SNMP HPE ProLiant System Health sensor monitors the system health of an HPE ProLiant server
SNMP HPE ProLiant System Health Sensor
List 2031 .

§ Dutch: SNMP HPE ProLiant Systeemstatus
§ French: HPE ProLiant état du système (SNMP)
§ German: SNMP HPE ProLiant Systemzustand
§ Portuguese: Saúde do sistema HPE ProLiant (SNMP)
2028
§ Spanish: Salud de sistema HPE ProLiant (SNMP)
Remarks
Remark Description
HPE system § For Gen10 servers: Use the HPE Integrated Lights Out (iLO) interface
management tools as the parent device.
least iLO 4.
channels.
Limits § This sensor has predefined limits for temperatures and broken frames.
2029
Remark Description
RAID controllers § Redundant array of independent disks (RAID) controllers that have no
hard disks assigned might cause the Down status. In this case,
deactivate the respective controllers in the HPE ProLiant BIOS to avoid
sensor errors.
you add the sensor:
§ hpe
§ snmphpe
§ snmphpesystemhealthsensor
§ systemhealth
Sensor Display
Sensor Display
Setting Description
2030
Setting Description



other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
CPU Fan Status The CPU fan status

§ Up status: OK
2031
Channel Description
Disk Controller Status The disk controller status

§ Up status: OK
Fans Broken The number of broken fans

Fans Running The number of running fans
Fault Tolerant Fans The number of fault-tolerant broken fans

Broken
Fault Tolerant Fans The number of fault-tolerant running fans

Running

§ Up status: OK
Power Consumption [#] The power consumption
Power Consumption [#] The power consumption (%)

(%)
Power Supply [#] The power supply condition

Condition
§ Up status: OK
2032
Channel Description
§ Down status: Degraded, Failed
Power Supply [#] Status The power supply status
§ Up status: No Error
§ Down status: Bist Failure, Brownout, Calibration Table Invalid, Dac

Failure, Eprom Failure, Fan Failure, General Failure, Give Up On
Startup, Interlock Open, No Power Input, Nvram Invalid, Orring Diode
Failed, Ram Test Failed, Temp Failure, Voltage Channel Failed, Vref
Failure
System Fan Status The system fan status

§ Up status: OK
Temperature [#] The temperature of the component

([Component])
Thermal Status The thermal status

§ Up status: OK
More
KNOWLEDGE BASE


Why is my SNMP HPE ProLiant System Health sensor in the error status after updating PRTG?
2033
2034
7.8.200 SNMP IBM System X Logical Disk Sensor
The SNMP IBM System X Logical Disk sensor monitors a logical disk in an IBM server via the Simple
SNMP IBM System X Logical Disk Sensor
List 2038 .

§ Dutch: SNMP IBM System X Logical Disk
§ French: IBM System X disque logique (SNMP)
§ German: SNMP IBM System X Logischer Datenträger
§ Japanese: SNMP IBM System X
§ Portuguese: Disco lógico IBM System X (SNMP)
§ Russian: IBM System X SNMP

§ Simplified Chinese: SNMP IBM System X
§ Spanish: Disco lógico IBM System X (SNMP)
Remarks
Remark Description
IBM Systems Director § This sensor requires the IBM Systems Director Platform Agent on the
Platform Agent target system.
2035
Remark Description
For more information, see the Knowledge Base: What are the
requirements to monitor IBM System x?
channels.
Knowledge Base § Knowledge Base: What are the requirements to monitor IBM System
x?
§ Knowledge Base: IBM System X sensors could not find any disk/data
on this device (PE187/PE188/PE194)
you add the sensor:
§ ibm
§ logicaldisk
§ snmpibm
§ snmpibmlogicaldisksensor
2036
IBM System X Logical Disk Settings
IBM System X Logical Disk Settings
Setting Description
Disk The ID of the logical disk that this sensor monitors.
Sensor Display
Sensor Display
Setting Description



other above.
procedure to do so.
2037
Inherited Settings
Channel List
Channel Description

§ Up status: Completed, In Service, Ok, Power Mode
§ Warning status: Dormant, Predictive Failure, Starting, Stressed
§ Down status: Aborted, Degraded, Error, Lost Communication, No

Contact, Non-Recoverable Error, Other, Stopped, Stopping, Supporting
Entity In Error, Unknown
More
KNOWLEDGE BASE
What are the requirements to monitor IBM System x?

IBM System X sensors could not find any disk/data on this device (PE187/PE188/PE194)


2038
7.8.201 SNMP IBM System X Physical Disk Sensor
The SNMP IBM System X Physical Disk sensor monitors a physical disk in an IBM server via the Simple
SNMP IBM System X Physical Disk Sensor
List 2042 .

§ Dutch: SNMP IBM System X Physical Disk
§ French: IBM System X disque physique (SNMP)
§ German: SNMP IBM System X Physikalischer Datenträger
§ Portuguese: Disco físico IBM System X (SNMP)

§ Spanish: Disco físico IBM System X (SNMP)
Remarks
Remark Description
2039
Remark Description
channels.
x?
you add the sensor:
§ ibm
§ physicaldisk
§ snmpibm
§ snmpibmphysicaldisksensor
2040
IBM System X Physical Disk Settings
IBM System X Physical Disk Settings
Setting Description
Sensor Display
Sensor Display
Setting Description



other above.
procedure to do so.
2041
Inherited Settings
Channel List
Channel Description


More
KNOWLEDGE BASE



2042
7.8.202 SNMP IBM System X Physical Memory Sensor
The SNMP IBM System X Physical Memory sensor monitors the memory modules in an IBM server via
SNMP IBM System X Physical Memory Sensor
List 2046 .

§ Dutch: SNMP IBM System X Physical Memory
§ French: IBM System X mémoire physique (SNMP)
§ German: SNMP IBM System X Physikalischer Speicher
§ Portuguese: Memória física IBM System X (SNMP)

§ Spanish: Memoria física IBM System X (SNMP)
Remarks
2043
Remark Description
channels.
x?
you add the sensor:
§ ibm
§ memorycontroller
§ snmpibm
§ snmpibmphysicalmemorysensor
2044
IBM System X Physical Memory Settings
IBM System X Physical Memory Settings
Setting Description
Name The name of the memory module that this sensor monitors.
Caption The caption of the memory module that this sensor monitors.
Serial Number The serial number of the memory module that this sensor monitors.
Size The size of the memory module that this sensor monitors.
Sensor Display
Sensor Display
Setting Description

2045
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Controller Condition The memory controller condition


2046
Channel Description
Power The power status

§ Up status: On
§ Down status: Off
More
KNOWLEDGE BASE



2047
7.8.203 SNMP IBM System X System Health Sensor
The SNMP IBM System X System Health sensor monitors the system health of an IBM device via the
SNMP IBM System X System Health Sensor
List 2051 .

§ Dutch: SNMP IBM System X Systeemstatus
§ French: IBM System X état du système (SNMP)
§ German: SNMP IBM System X Systemzustand
§ Portuguese: Saúde do sistema IBM System X (SNMP)

§ Spanish: Salud de sistema IBM System X (SNMP)
Remarks
2048
Remark Description
channels.
IMM § This sensor can also run directly on an Integrated Management Module
(IMM) network port and can show the overall health of IMMs.
Unexpected format § If the IBM device returns a string in an unexpected format for the
percentage of fan revolutions (for example, "offline"), this sensor shows
-1% in the corresponding channel. You can define the Down status for
this via channel limits.
x?
The SNMP IBM System X System Health sensor can also run directly on an IMM network port and
can show the overall health of IMMs.
2049
you add the sensor:
§ snmpibmsystemhealthsensor
§ systemhealth
IBM System X System Health Specific
IBM System X System Health Specific
Setting Description
Source The source of the measurement that this sensor monitors.
Sensor Display
Sensor Display
Setting Description

2050
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Ambient Temp The ambient temperature
CMOS Battery The CMOS battery voltage
CPU [#] Temp The CPU temperature
Fan [#] Tach The fan RPM or the percentage of the possible maximum
2051
Channel Description
§ Up status: Normal, System Level
SysBrd 3.3V The 3.3V-system board voltage
SysBrd 5V The 5V-system board voltage
SysBrd 12V The 12V-system board voltage
More
KNOWLEDGE BASE



2052
7.8.204 SNMP interSeptor Pro Environment Sensor
The SNMP interSeptor Pro Environment sensor queries data from a Jacarta interSeptor Pro
environmental monitoring system via the Simple Network Management Protocol (SNMP).
SNMP interSeptor Pro Environment Sensor
List 2056 .

§ Dutch: SNMP interSeptor Pro Omgeving
§ French: interSeptor Pro environnement (SNMP)
§ German: SNMP interSeptor Pro Umgebung
§ Japanese: SNMP interSeptor Pro
§ Portuguese: Ambiente interSeptor Pro (SNMP)
§ Russian: interSeptor Pro SNMP

§ Simplified Chinese: SNMP interSeptor Pro
§ Spanish: Entorno interSeptor Pro (SNMP)
Remarks
Remark Description
2053
Remark Description
IP address § To monitor data of an interSeptor Pro device with this sensor, you must
add the IP address of your PRTG core server system to Access Control
in the interSeptor Pro control panel. Open the interSeptor Pro web
interface, select InterSeptor Pro Menu | System Configuration | Access
Control, and allow access for the IP address of PRTG.
you add the sensor:
§ environment
§ interseptor
InterSeptor Environment Specific
InterSeptor Environment Specific
Setting Description
Name The name of the measuring point that this sensor monitors.
2054
Setting Description
Measuring Point The measuring point that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
2055
Channel List
Channel Description
Humidity The humidity (%)
Temperature The temperature
More
KNOWLEDGE BASE


2056
7.8.205 SNMP Juniper NS System Health Sensor
The SNMP Juniper NS System Health sensor monitors the system health of a Juniper NetScreen device
SNMP Juniper NS System Health Sensor
List 2059 .

§ Dutch: SNMP Juniper NS systeemstatus
§ French: Juniper NS état du système (SNMP)
§ German: SNMP Juniper NS Systemzustand
§ Japanese: SNMP Juniper NS
§ Portuguese: Saúde do sistema Juniper NS (SNMP)
§ Russian: Juniper NS SNMP

§ Simplified Chinese: SNMP Juniper NS
§ Spanish: Salud de sistema Juniper NS (SNMP)
Remarks
2057
Remark Description
channels.
you add the sensor:
§ snmpjuniper
§ systemhealth
Sensor Display
Sensor Display
Setting Description
2058
Setting Description



other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description

2059
Channel Description
Power Supply (Power) The power supply status

§ Up status: Good
§ Down status: Fail
Session Usage The session usage (%)
Temperature (System The system temperature

Temperature)
More
KNOWLEDGE BASE


2060
7.8.206 SNMP LenovoEMC Physical Disk Sensor
The SNMP LenovoEMC Physical Disk sensor monitors a physical disk in a LenovoEMC network-
attached storage (NAS) via the Simple Network Management Protocol (SNMP).
SNMP LenovoEMC Physical Disk Sensor
List 2064 .

§ Dutch: SNMP LenovoEMC fysieke schijf
§ French: LenovoEMC disque physique (SNMP)
§ German: SNMP LenovoEMC Physikalischer Datenträger
§ Japanese: SNMP LenovoEMC
§ Portuguese: Disco físico LenovoEMC (SNMP)
§ Russian: LenovoEMC SNMP

§ Simplified Chinese: SNMP LenovoEMC
§ Spanish: Disco físico LenovoEMC (SNMP)
Remarks
Remark Description
2061
Remark Description
channels.
you add the sensor:
§ lenovoemc
§ physicaldisk
§ snmplenovoemc
LenovoEMC NAS Settings
LenovoEMC NAS Settings
Setting Description
2062
Setting Description
Name The name of the physical disk that this sensor monitors.
Size The size of the physical disk that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
2063
Inherited Settings
Channel List
Channel Description

§ Warning status: Foreign, Unknown
§ Down status: Faulted, Missing
More
KNOWLEDGE BASE


2064
7.8.207 SNMP LenovoEMC System Health Sensor
The SNMP LenovoEMC System Health sensor monitors the system health of a LenovoEMC network-
attached storage (NAS) via the Simple Network Management Protocol (SNMP).
SNMP LenovoEMC System Health Sensor
List 2067 .

§ Dutch: SNMP LenovoEMC Systeemstatus
§ French: LenovoEMC état du système (SNMP)
§ German: SNMP LenovoEMC Systemzustand
§ Japanese: SNMP LenovoEMC
§ Portuguese: Saúde do sistema LenovoEMC (SNMP)
§ Russian: LenovoEMC SNMP

§ Simplified Chinese: SNMP LenovoEMC
§ Spanish: Salud sistema LenovoEMC (SNMP)
2065
Remarks
Remark Description
channels.
you add the sensor:
§ lenovoemc
§ snmplenovoemc
§ systemhealth
Sensor Display
Sensor Display
2066
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
2067
Channel Description
Fan "Internal Fan" The fan RPM
RAID Status The RAID status

§ Warning status: Degraded, RebuildFS, Rebuilding, Unknown
§ Down status: Faulted
Temperature "CPU" The CPU temperature
Temperature "Drives" The temperature of the drives
Temperature "System" The temperature of the system
Voltage "System Voltage The system voltage (12V)

(12V)"
Voltage "V1.1" The voltage of the 1.1V-battery
Voltage "V3.3" The voltage of the 3.3V-battery
More
KNOWLEDGE BASE


2068
7.8.208 SNMP Library Sensor
The SNMP Library sensor uses a Management Information Base (MIB) file to create sensors that monitor
a device via the Simple Network Management Protocol (SNMP).
The content of the MIB file determines which data types are available for monitoring. When you
create the sensor, it provides a list of counters that the target device returns based on every object
identifier (OID) in the MIB file.
The SNMP Library sensor does not appear as a running sensor. It uses the meta-scan facility of the
probe to find or to match OIDs from the MIB file. It is useful because you do not need to manually
enter OIDs.
To monitor SNMP-capable devices and to add sensors via the SNMP Library sensor, download the
manufacturer's MIB files for the target device, convert the MIB files to the OID library format, and
import 2075 them into PRTG. PRTG also provides precompiled .oidlib files 2075 that contain the OIDs of
SNMP counters for the most common network devices.
For more information, see the Knowledge Base: How do SNMP, MIBs and OIDs work?
SNMP Custom Advanced Sensor Created by SNMP Library Sensor
2069
§ Dutch: SNMP Bibliotheek
§ French: Bibliothèque (SNMP)
§ German: SNMP-Bibliothek
§ Japanese: SNMP
§ Portuguese: Biblioteca (SNMP)
§ Russian: SNMP
§ Spanish: Biblioteca (SNMP)
Remarks
Remark Description
Knowledge Base § Knowledge Base: How do SNMP, MIBs and OIDs work?
§ Knowledge Base: How can I import my MIB files into PRTG?
§ Knowledge Base: Can't find a sensor for my device in PRTG but I

believe it supports SNMP. How to proceed?
PRTG Hosted Monitor To import MIB files into PRTG Hosted Monitor, see section Manage a
PRTG Hosted Monitor Subscription.
Add Sensor
PRTG shows a list of .oidlib files that are available on the system. This list contains all library files in the
\snmplibs subfolder of the PRTG program directory. It contains both the default PRTG library files and
your own library files.
2070
List of SNMP Library Files
The library file names in the list indicate their purpose. Select a library file that is suitable for the target
device (for example, choose an MIB file that you imported) and confirm via Ok.
If the library file not suitable for the target device, this results in the error message The scan for
available monitoring items has failed on this device: No such object (SNMP error # 222). If you see
this message, click Cancel and try to add the sensor with a different library file.
The SNMP Library sensor takes a list of OIDs that you import from an MIB file into an .oidlib file and
tests the OIDs against the target device to find the OIDs that the target device supports. This discovery
process is the meta-scan. If the sensor finds counters for the target device, the sensor settings open
with a list of all available monitoring items.
List of SNMP Single Values: Sorted by MIB, Category, Name
2071
List of SNMP Table Values: Sorted by MIB, Category (Table Name/OID), Row , Name
The list of SNMP table values sequentially presents row values to help you find the values you are
interested in.
You can also use the search to find the desired group or category. The search matches individual
strings, so if your string has a space in it, put the search string in double quotation marks (").
Select the counters that you want to monitor and click Save. PRTG creates sensors based on the OID
types of the selected counters.
Add Sensor Settings
Setting Description
Library The path to the .oidlib file that this sensor uses.
Category Select the parameters that you want to monitor. The list is specific to
your setup. The list contains all counters that are available in the .oidlib
file that match the target device.
Depending on the type of the selected entries, PRTG creates the
following sensors:
§ SNMP Custom Advanced 1907 : For up to 10 channels for 10 OIDs each.
For example, 22 selected single values result in 3 sensors: 2 sensors
with 10 channels and 1 sensor with 2 channels.
2072
Setting Description
§ SNMP Custom String 1913 : For each selected entry that returns a string
value.
§ SNMP Custom Table 1928 : For up to 10 channels for 10 columns per
row. The channels represent the values in the columns of the same
row.
Once you create a custom SNMP sensor, you can create a device
template from it and prepare it for distribution. For example, you can
refine the template with better name templates.
you add the sensor:
§ snmplibrarysensor
Sensor Specific
The available sensor settings depend on the sensor that the SNMP Library sensor creates. For more
information about settings, see the sections of these sensors:
§ SNMP Custom Advanced 1909
§ SNMP Custom String 1915
§ SNMP Custom Table 1930
2073
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
2074
Import MIB Files
Additionally, you can create your own .oidlib files by importing the device manufacturers' MIB files
with the free MIB Importer tool. You can convert your MIB files and save the .oidlib file results to the
\snmplibs subfolder of the PRTG program directory.
For more information about the MIB Importer, see the Knowledge Base: How can I import my MIB
files into PRTG?
If the.oidlib files that you import contain lookups (you can see this in section Lookup in the MIB
Importer), you can define your own sensor states for the values that the lookups return. Add an SNMP
Library sensor with this .oidlib file. PRTG then creates a lookup definition file using the lookupname of
the chosen library as id parameter.
PRTG adds the lookups without status definitions, so the sensor shows the Warning status by
default. You must edit the corresponding lookup files to get reliable alarms. Override the lookup
definition with your own custom lookup. For more information, see section Define Lookups.
To import MIB files into PRTG Hosted Monitor, see section Manage a PRTG Hosted Monitor
Subscription.
Default .oidlib Files Overview

PRTG comes with the following .oidlib files.
The .oidlib files might not support all devices or parameters.
.oidlib File Description
APC UPS.oidlib Monitors uninterruptible power supplies (UPSs) from APC

American Power Conversion Corp.
APCSensorstationlib.oidlib Monitors alarm status, communication status, humidity, and

temperature as shown by an APC sensor station.
Basic Linux Library (UCD-SNMP- Monitors basic system parameters on Linux systems, such
MIB).oidlib as memory, disk and swap, CPU, and more.
cisco-interfaces.oidlib Monitors Cisco-specific parameters, for example, the number

of present network interfaces on a system, several states of
an interface (admin, oper, speed, type, errors, discards, etc.),
and more.
cisco-queue.oidlib Monitors queues on a Cisco interface, for example, queue

depth and its maximum, discarded messages from the
queue, the number of the queue within the queue set, and
more.
2075
.oidlib File Description
Dell Storage Management.oidlib Monitors Dell storage devices. Possible parameters include
disk arrays, battery and power supply, fan and temperature,
virtual disk, and more.
Dell Systems Management Monitors the hardware of Dell systems. Possible parameters
Instrumentation.oidlib include ACPower and battery, alerts, base board, BIOS,
Baseboard Management Controller (BMC), chassis, COO,
cooling, event log, firmware, integrated development
environment (IDE), keyboard, memory, port, network,
processor, Small Computer System Interface (SCSI),
system, temperature, USB, universally unique identifier
(UUID), and more.
HP LaserJet Status.oidlib Monitors toner, paper, and jam status of an HP LaserJet

printer.
Linux SNMP (AX BGP DisMan Monitors different aspects of Linux systems.
EtherLike Host).oidlib
This file might detect a very large number of interfaces. It
might take a few seconds until the selection table
appears.
Linux SNMP (Framework Proxy Noti Monitors different aspects of Linux systems.
v2).oidlib
appears.
Linux SNMP (IP Net SNMP Noti Monitors different aspects of Linux systems.
OSPF RMON SMUX).oidlib
appears.
Linux SNMP (Source TCP UCD Monitors different aspects of Linux systems.
UDP).oidlib
appears.
Paessler Common OID Library.oidlib Monitors many common hardware devices. It is used for
several sensors and is encrypted.
SNMP Informant std.oidlib Monitors logical disks, processor, memory, and network
interface on Windows systems.
2076
More
KNOWLEDGE BASE
How do SNMP, MIBs and OIDs work?

How can I import my MIB files into PRTG?
Can't find a sensor for my device in PRTG but I believe it supports SNMP. How to proceed?


How can I monitor EMC Isilon storage systems with PRTG?

PAESSLER TOOLS
MIB Importer
§ https://www.paessler.com/tools/mibimporter
2077
7.8.209 SNMP Linux Disk Free Sensor
The SNMP Linux Disk Free sensor monitors the free space on disks of a Linux/Unix system via the
SNMP Linux Disk Free Sensor
The free space that this sensor returns shows the disk space that is not yet used. Not all of this
space might be available for use because a part of this space might be reserved by the system, for
example, for redundancy purposes. For more information, see the Knowledge Base: Why do SSH Disk
Free and SNMP Linux Disk Free show different values for my target Linux system?
List 2084 .

§ Dutch: SNMP Linux vrije schijf ruimte
§ French: Linux espace disponible du disque (SNMP)
§ German: SNMP Linux-Datenträgerspeicher
§ Japanese: SNMP Linux
§ Portuguese: Disco livre Linux (SNMP)
2078
§ Russian: Linux SNMP
§ Simplified Chinese: SNMP Linux
§ Spanish: Espacio libre en disco Linux (SNMP)
Remarks
Remark Description
Knowledge Base § Knowledge Base: Why do SSH Disk Free and SNMP Linux Disk Free
show different values for my target Linux system?
§ Knowledge Base: Monitoring Linux problem - SNMP port not reachable
you add the sensor:
§ diskspacesensor
Set Limits Checked for ALL Disks

In this section, you can set limits that are valid for all channels and all drives. With limits, you can define
when the sensor shows the Warning or Down status, depending on the data provided by all drives that
this sensor monitors. If you want to individually define limits for separate channels, use the limit settings
in the channel settings.
2079
All limits that you define here are valid in addition to the limits in the particular channel settings. The
limits are valid simultaneously, so the first limit that is breached applies.
Setting Description
Percentage Limit Check By default, the sensor enables percentage limits with a lower warning
limit and a lower error limit. Enable or disable a limit check for the free
space in percentage channels of all drives:
§ Only use the limits in the settings of the percentage channels: Do not
define sensor limits that are valid for all percentage channels. The
sensor only uses the limits that you define in the settings of the
particular "free space in percent" channels to determine the status.
§ Use the limits of both the sensor and the channel settings: Define
sensor limits that are valid for all percentage channels. Additional fields
appear below. The sensor shows the Warning or the Down status when
free space limits are above or below the limits.
Upper Error Limit This setting is only visible if you select Use the limits of both the sensor
and the channel settings above.
Specify an upper limit in percent for the Down status. If the free disk
space of one of your drives exceeds this value, the sensor changes to the
Down status. Enter an integer or leave the field empty.
The limits that you set here are valid for all channels of this sensor.
You can additionally set individual limits for each channel in the
channel settings. Both the limits that you set here and in the channel
settings are valid simultaneously.
2080
Setting Description
Upper Warning Limit This setting is only visible if you select Use the limits of both the sensor
Specify an upper limit in percent for the Warning status. If the free disk
Warning status. Enter an integer or leave the field empty.
Lower Warning Limit This setting is only visible if you select Use the limits of both the sensor
Specify a lower limit in percent for the Warning status. If the free disk
space of one of your drives falls below this value, the sensor changes to
the Warning status. Enter an integer or leave the field empty.
Lower Error Limit This setting is only visible if you select Use the limits of both the sensor
Specify a lower limit in percent for the Down status. If the free disk space
of one of your drives falls below this value, the sensor changes to the
Size Limit Check Enable or disable a limit check for the free bytes channels of all drives:
§ Only use the limits in the settings of the byte size channels: Do not
define sensor limits that are valid for all byte size channels. The sensor
only uses limits that you define in the settings of the particular free
space in bytes channels to determine the status.
§ Use the limits of both the sensor and the channel settings: Define limits
for the sensor that are valid for all byte size channels. Additional fields
appear below. The sensor shows the Warning or Down status when free
space limits are above or below the value.
By default, byte size limits are not enabled for drives.
2081
Setting Description
Specify an upper limit. Use the same unit as shown by the free bytes
channels of this sensor (the default unit is MB). If the free disk space of
one of your drives exceeds this value, the sensor changes to the Down
status. Enter an integer or leave the field empty.
one of your drives exceeds this value, the sensor changes to the Warning
Specify a lower limit. Use the same unit as shown by the free bytes
one of your drives falls below this value, the sensor changes to the
one of your drives falls below this value, the sensor changes to the Down
2082
Setting Description
Alarm on If a monitored disk is removed or not found, the sensor sets the values to
Missing/Removed Disk zero. Select the alarm approach in this case:
§ Deactivate alarm (default): Do not send an alert for a removed disk.
§ Activate alarm: Send an alert if a monitored disk is removed or not

found.
Sensor Display
Sensor Display
Setting Description


other above.
2083
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Free Bytes [Partition] The free space
Free INodes [Partition] The free index nodes (%)
Free Space [Partition] The free space (%)
Total The free total disk space
More
KNOWLEDGE BASE
Why do SSH Disk Free and SNMP Linux Disk Free show different values for my target Linux system?
Monitoring Linux problem - SNMP port not reachable

2084

2085
7.8.210 SNMP Linux Load Average Sensor
The SNMP Linux Load Average sensor monitors the system load average of a Linux/Unix system via the
SNMP Linux Load Average Sensor
List 2088 .

§ Dutch: SNMP Linux Gemiddelde belasting
§ French: Linux charge moyenne (SNMP)
§ German: SNMP Linux Durchschnittliche Last
§ Portuguese: Carga média Linux (SNMP)

§ Spanish: Promedio de carga Linux (SNMP)
Remarks
2086
Remark Description
Knowledge Base § Knowledge Base: Monitoring Linux problem - SNMP port not reachable
you add the sensor:
§ snmploadsensor
Sensor Display
Sensor Display
Setting Description
2087
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
1 Minute The average system load within a 1-minute interval

5 Minutes The average system load within a 5-minute scanning interval
15 Minutes The average system load within a 15-minute interval
2088
More
KNOWLEDGE BASE


2089
7.8.211 SNMP Linux Meminfo Sensor
The SNMP Linux Meminfo sensor monitors the memory usage of a Linux/Unix system via the Simple
SNMP Linux Meminfo Sensor
List 2092 .

§ Dutch: SNMP Linux meminfo
§ French: Linux information mémoire (SNMP)
§ German: SNMP Linux Speicherinfo
§ Portuguese: Meminfo Linux (SNMP)
§ Russian: Linux Meminfo SNMP

§ Spanish: Meminfo Linux (SNMP)
2090
Remarks
Remark Description
you add the sensor:
§ memorysensor
§ snmpmeminfosensor
Sensor Display
Sensor Display
2091
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
2092
Channel Description

Free Physical Memory The free physical memory
Free Physical Memory % The free physical memory (%)

Free Swap Space The free swap memory
Free Swap Space % The free swap memory (%)

Total Free Memory The total free memory (physical memory plus swap)
Total Free Memory % The total free memory (%) (physical memory plus swap)
More
KNOWLEDGE BASE


2093
2094
7.8.212 SNMP Linux Physical Disk Sensor
The SNMP Linux Physical Disk sensor monitors the input/output (I/O) on disks of a Linux/Unix system
SNMP Linux Physical Disk Sensor
List 2097 .

§ Dutch: SNMP Linux Fysieke Schijf
§ French: Linux disque physique (SNMP)
§ German: SNMP Linux Physikalischer Datenträger
§ Portuguese: Disco físico Linux (SNMP)

§ Spanish: Disco físico Linux (SNMP)
Remarks
2095
Remark Description
you add the sensor:
§ physicaldisk
§ snmpphysicaldisksensor
Physical Disk Settings
Physical Disk Settings
Setting Description
BitMask The bitmask that might be necessary for bug tracking purposes.
2096
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2097
Channel Description

Load Average (1 Minute) The load average (1 minute) (%)
Load Average (5 Minutes) The load average (5 minutes) (%)
Load Average (15 The load average (15 minutes) (%)

Minutes)
Read Accesses The number of read accesses
Write Accesses The number of write accesses
More
KNOWLEDGE BASE



2098
7.8.213 SNMP Memory Sensor
The SNMP Memory sensor monitors the memory usage of a system via the Simple Network
This sensor uses more generic object identifier (OID) values in comparison to the SNMP Linux
Meminfo 2090 sensor.
SNMP Memory Sensor
List 2101 .

§ Dutch: SNMP Geheugen
§ French: Mémoire (SNMP)
§ German: SNMP Speicher
§ Japanese: SNMP
§ Portuguese: Memória (SNMP)
§ Russian: SNMP
§ Spanish: Memoria (SNMP)
Remarks
2099
Remark Description
you add the sensor:
§ memory
§ memorysensor
§ snmp
§ snmpmemorysensor
Memory Settings
Memory Settings
Setting Description
Memory Type The type of memory that this sensor monitors.
2100
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2101
Channel Description

Memory
Total Memory The total memory
More
KNOWLEDGE BASE


2102
7.8.214 SNMP NetApp Disk Free Sensor
The SNMP NetApp Disk Free sensor monitors the free space on disks of a NetApp storage system via
SNMP NetApp Disk Free Sensor
List 2106 .

§ Dutch: SNMP NetApp Schijf Vrije Ruimte
§ French: NetApp espace disponible du disque (SNMP)
§ German: SNMP NetApp-Datenträgerspeicher
§ Japanese: SNMP NetApp
§ Portuguese: Disco livre NetApp (SNMP)
§ Russian: NetApp SNMP

§ Simplified Chinese: SNMP NetApp
§ Spanish: Espacio libre en disco NetApp (SNMP)
2103
Remarks
Remark Description
channels.
Knowledge Base § Knowledge Base: How can I monitor capacity and used disk space on
a NetApp?
you add the sensor:
§ netapp
§ snmpnetapp
§ snmpnetappdiskfreesensor
2104
NetApp Disk Free Settings
NetApp Disk Free Settings
Setting Description
File System The name of the disk that this sensor monitors.
Virtual Disk The name of the virtual disk that this sensor monitors (if applicable).
Sensor Display
Sensor Display
Setting Description


other above.
2105
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Deduplication Saved The deduplication saved space

Space
Deduplication Saved The deduplication saved space (%)

Space %
Deduplication Shared The deduplication shared space

Space
Deduplication Shared The deduplication shared space (%)

Space %

§ Up status: Creating, Mounted, Mounting, Nofsinfo, Replayed,
Replaying, Unmounting
§ Down status: Destroying, Frozen, Unmounted
2106
Channel Description
Files Free The free files (%)

INodes Free The free index nodes (%)
More
KNOWLEDGE BASE
How can I monitor capacity and used disk space on a NetApp?



2107
7.8.215 SNMP 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 the Simple Network Management Protocol (SNMP).
SNMP NetApp Enclosure Sensor
List 2111 .

§ Dutch: SNMP NetApp Behuizing
§ French: NetApp boîtier (SNMP)
§ German: SNMP NetApp Enclosure
§ Portuguese: Gabinete NetApp (SNMP)

§ Spanish: Gabinete NetApp (SNMP)
2108
Remarks
Remark Description
NetApp versions § This sensor only supports NetApp versions up to 8.2.
you add the sensor:
§ netapp
§ snmpnetapp
§ snmpnetappenclosuresensor
NetApp Enclosure Settings
NetApp Enclosure Settings
2109
Setting Description
Enclosure The identifier of the enclosure that this sensor monitors.
NetApp Specific
NetApp Specific
Setting Description
N/A Measurement Define the sensor behavior if the requested NetApp value is not available
Handling (N/A values):
§ Set sensor to down status (default): Set the sensor to the Down status
if a measurement is not available.
We recommend that you use this setting to not miss any hardware
errors.
§ Interpret as valid: Handle unavailable measurements as valid sensor
results to keep the sensor in the Up status.
This might be useful, for example, if a hardware sensor on the
NetApp is disabled for some reason but actually there is no
hardware error. If the NetApp returns an N/A measurement, the sensor
interprets this as 0.
We recommend that you use the lookup file
prtg.standardlookups.netapp.notavailable.ovl for channels with
unavailable measurements if you select this option. This replaces 0
with the message Not Available. Open the settings of the affected
channels and select this file in section Lookup. For more information,
see section Define Lookups.
Sensor Display
Sensor Display
2110
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Broken Electronic Parts The number of broken electronic parts
Broken Power Supplies The number of broken power supplies
2111
Channel Description
Current [#] The current
Fan [#] The fan RPM
Fans Failed The number of failed fans
Voltage [#] The voltage
More
KNOWLEDGE BASE


2112
7.8.216 SNMP NetApp I/O Sensor
The SNMP NetApp I/O sensor monitors the input/output operations per second (IOPS) on a NetApp
storage system via the Simple Network Management Protocol (SNMP).
SNMP NetApp I/O Sensor
List 2115 .

§ Dutch: SNMP NetApp I/O
§ French: NetApp E/S (SNMP)
§ German: SNMP NetApp E/A
§ Japanese: SNMP NetApp I/O
§ Portuguese: E/S NetApp (SNMP)

§ Simplified Chinese: SNMP NetApp I/O
2113
§ Spanish: E/S NetApp (SNMP)
Remarks
Remark Description
NetApp I/O § If you use NetApp cDOT 8.3 or NetApp ONTAP as of version 9.0, we
recommend that you use the NetApp I/O 1389 sensor.
you add the sensor:
§ netapp
§ snmpnetapp
§ snmpnetappiosensor
Sensor Display
Sensor Display
2114
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
CIFS Ops The number of CIFS operations
2115
Channel Description
FCP Ops The number of FCP operations

HTTP Ops The number of HTTP operations
ISCSI Ops The number of iSCSI operations
ISCSI Read The iSCSI read speed
ISCSI Write The iSCSI read speed
Network Received The number of bytes received
Network Sent The number of bytes sent
NFS Ops The number of NFS operations
Tape Read The tape read speed
Tape Write The tape write speed
More
KNOWLEDGE BASE


2116
7.8.217 SNMP NetApp License Sensor
The SNMP NetApp License sensor monitors the licenses for the services of a NetApp storage system
SNMP NetApp License Sensor
List 2119 .

§ Dutch: SNMP NetApp licentie
§ French: NetApp Licence (SNMP)
§ German: SNMP NetApp Lizenz
§ Portuguese: Licença NetApp (SNMP)

§ Spanish: Licencia NetApp (SNMP)
Remarks
Remark Description
2117
Remark Description
you add the sensor:
§ netapp
§ snmpnetapp
§ snmpnetapplicensesensor
NetApp License Settings
NetApp License Settings
Setting Description
License for Service The name of the license whose service this sensor monitors.
2118
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2119
Channel Description
Time Left The time until the license for a service expires
More
KNOWLEDGE BASE


2120
7.8.218 SNMP NetApp Logical Unit Sensor
The SNMP NetApp Logical Unit sensor monitors the input/output operations per second (IOPS) on a
logical unit of a NetApp storage system via the Simple Network Management Protocol (SNMP).
SNMP NetApp Logical Unit Sensor
List 2124 .

§ Dutch: SNMP NetApp Logical Unit
§ French: NetApp unité logique (SNMP)
§ German: SNMP NetApp Logische Einheit
§ Portuguese: Unidade lógica NetApp (SNMP)

§ Spanish: Unidad lógica NetApp (SNMP)
2121
Remarks
Remark Description
channels.
NetApp LUN § If you use NetApp cDOT 8.3 or NetApp ONTAP as of version 9.0, we
recommend that you use the NetApp LUN 1416 sensor.
you add the sensor:
§ netapp
§ snmpnetapp
§ snmpnetappdiskfreesensor
2122
NetApp Logical Unit Settings
NetApp Logical Unit Settings
Setting Description
Logical Unit The name of the logical unit that this sensor monitors.
Alignment Monitoring Select if the sensor checks the alignment of the logical unit:
§ Do not check alignment
§ Check alignment (if available)
Volume The volume that this sensor monitors.
Comment Comments for the logical unit that this sensor monitors.
Sensor Display
Sensor Display
Setting Description
2123
Setting Description



other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
2124
Channel Description
Ops The total number of operations

Other Ops The number of other operations
Status The logical unit status

§ Down status: Offline
More
KNOWLEDGE BASE

2125
7.8.219 SNMP NetApp Network Interface Sensor
The SNMP NetApp Network Interface sensor monitors a network card of a NetApp storage system via
SNMP NetApp Netw ork Interface Sensor
List 2128 .

§ Dutch: SNMP NetApp Network Interface
§ French: NetApp interface réseau (SNMP)
§ German: SNMP NetApp Netzwerkschnittstelle
§ Portuguese: Interface de rede NetApp (SNMP)

§ Spanish: Interfaz de red NetApp (SNMP)
Remarks
2126
Remark Description
NetApp NIC § If you use NetApp cDOT 8.3 or NetApp ONTAP as of version 9.0, we
recommend that you use the NetApp NIC 1429 sensor.
you add the sensor:
§ netapp
§ snmpnetapp
§ snmpnetappnetworkinterfacesensor
NetApp Network Interface Settings
NetApp Netw ork Interface Settings
Setting Description
Network Interface The name of the network interface that this sensor monitors.
2127
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2128
Channel Description
Errors In The number of incoming errors
Errors Out The number of outgoing errors

More
KNOWLEDGE BASE


2129
7.8.220 SNMP NetApp System Health Sensor
The SNMP NetApp System Health sensor monitors the status of a NetApp storage system via the
SNMP NetApp System Health Sensor
List 2132 .

§ Dutch: SNMP NetApp Systeemstatus
§ French: NetApp état du système (SNMP)
§ German: SNMP NetApp Systemzustand
§ Portuguese: Saúde do sistema NetApp (SNMP)
2130
§ Spanish: Salud de sistema NetApp (SNMP)
Remarks
Remark Description
NetApp System Health § If you use NetApp cDOT 8.3 or NetApp ONTAP as of version 9.0 or
later, we recommend that you use the NetApp System Health 1468
sensor.
you add the sensor:
§ netapp
§ snmpnetapp
§ snmpnetappsystemhealthsensor
2131
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2132
Channel Description
CPU Load The CPU load (%)
Disks Active The number of active disks
Disks Being Added The number of disks being added
Disks Being Scrubbed The number of disks being scrubbed
Disks Failed The number of failed disks

Disks Failing Soon The number of disks that will fail soon
Disks Out Of Date The number of disks that are out of date
Disks Reconstructing The number of disks that are reconstructing
Disks Reconstructing The number of disks that are reconstructing parity

Parity
Disks Spare The number of spare disks

§ Lower error limit 1
Disks Total The total number of disks

Disks Verifying Parity The number of disks that are verifying parity
2133
More
KNOWLEDGE BASE

2134
7.8.221 SNMP Nutanix Cluster Health Sensor
The SNMP Nutanix Cluster Health sensor monitors the status and the performance of a Nutanix cluster
SNMP Nutanix Cluster Health Sensor
List 2139 .

§ Dutch: SNMP Nutanix Cluster Health
§ French: Nutanix état de cluster (SNMP)
§ German: SNMP Nutanix Clusterzustand
§ Japanese: SNMP Nutanix
§ Portuguese: Funcionamento do cluster Nutanix (SNMP)
§ Russian: SNMP Nutanix

§ Simplified Chinese: SNMP Nutanix
§ Spanish: Salud de clúster Nutanix (SNMP)
Remarks
2135
Remark Description
SNMP v3 § Nutanix devices only support SNMP v3. Make sure that you select
SNMP v3 in the credentials for SNMP devices settings of the parent
device.
channels.
you add the sensor:
§ nutanix
§ snmp
§ snmpnutanixclusterhealthsensor
2136
System Specific
System Specific
Setting Description
Debug Options
Debug Options
Setting Description
2137
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
2138
Inherited Settings
Channel List
Channel Description
I/O Bandwidth The bandwidth of I/O operations
I/O Latency The latency of I/O operations
I/O Operations The number of I/O operations
Status The Nutanix cluster status

§ Up status: Started
§ Warning status: Starting, Stopping
§ Down status: Stopped, Unknown
More
KNOWLEDGE BASE


2139
7.8.222 SNMP Nutanix Hypervisor Sensor
The SNMP Nutanix Hypervisor sensor monitors a Nutanix hypervisor via the Simple Network
SNMP Nutanix Hypervisor Sensor
List 2144 .

§ Dutch: SNMP Nutanix Hypervisor
§ French: Nutanix hyperviseur (SNMP)
§ German: SNMP Nutanix Hypervisor
§ Japanese: SNMP Nutanix
§ Portuguese: Hipervisor Nutanix (SNMP)
§ Russian: SNMP Nutanix

§ Simplified Chinese: SNMP Nutanix
§ Spanish: Hipervisor Nutanix (SNMP)
2140
Remarks
Remark Description
SNMP v3 § Nutanix devices only support SNMP v3. Make sure that you select
SNMP v3 in the credentials for SNMP devices settings of the parent
device.
channels.
you add the sensor:
§ nutanix
§ snmp
§ snmpnutanixhypervisorsensor
2141
System Specific
System Specific
Setting Description
Debug Options
Debug Options
Setting Description
2142
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
2143
Inherited Settings
Channel List
Channel Description

I/O Bandwidth The bandwidth of I/O operations
I/O Latency The latency of I/O operations
I/O Read The read speed of I/O operations
I/O Write The write speed of I/O operations
Package Drop In The number of dropped incoming packages
Package Drop Out The number of dropped outgoing packages
VM Count The number of VMs
More
KNOWLEDGE BASE
2144

2145
7.8.223 SNMP Poseidon Environment Sensor
The SNMP Poseidon Environment sensor monitors performance counters for environmental
measurements on Poseidon hardware via the Simple Network Management Protocol (SNMP).
SNMP Poseidon Environment Sensor
List 2148 .

§ Dutch: SNMP Poseidon Omgeving
§ French: Poseidon environnement (SNMP)
§ German: SNMP Poseidon-Umgebung
§ Japanese: SNMP Poseidon
§ Portuguese: Ambiente Poseidon (SNMP)
§ Russian: Poseidon SNMP

§ Simplified Chinese: SNMP Poseidon
§ Spanish: Entorno Poseidon (SNMP)
Remarks
Remark Description
2146
Remark Description
you add the sensor:
§ apcups
Poseidon Environment Specific
Poseidon Environment Specific
Setting Description
Name The name of the measurement that this sensor monitors.
Unit The unit of the value measurement that this sensor monitors.
Measuring Point The measuring points that this sensor monitors.
2147
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2148
Channel Description
[Value] The humidity (%) or the temperature
More
KNOWLEDGE BASE


2149
7.8.224 SNMP Printer Sensor
The SNMP Printer sensor monitors various types of printers via the Simple Network Management
Protocol (SNMP).
The sensor supports the following printers, among others: HP OfficeJet printers, HP LaserJet
printers, RICOH SP 5200, SP 3410, SP C242DN, MP C3003, and MP C2503.
The sensor also shows the printer status as the sensor message.
SNMP Printer Sensor
List 2152 .

§ Dutch: SNMP Printer
§ French: Imprimante (SNMP)
§ German: SNMP Drucker
§ Japanese: SNMP
§ Portuguese: Impressora (SNMP)
§ Russian: SNMP
§ Spanish: Impresora (SNMP)
2150
Remarks
Remark Description
Printers § This sensor supports the following printers, among others: HP OfficeJet
printers, HP LaserJet printers, RICOH SP 5200, SP 3410, SP C242DN,
MP C3003, and MP C2503.
channels.
Channels § We recommend that you do not rename channels of the sensor.

Renaming a channel creates a new empty channel.
you add the sensor:
§ printer
§ snmp
2151
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2152
Channel Description
Black Cartridge [Printer] The cartridge fill level

§ Up status: No Restriction, Not Empty, Ok
§ Warning status: Low
Cyan Cartridge [Printer] The cartridge fill level

Magenta Cartridge The cartridge fill level

[Printer]
Printer Cover The printer cover status

§ Up status: Cover Closed, Interlock Closed
§ Warning status: Other
§ Down status: Cover Open, Interlock Open
Total Page Count The total number of printed pages

Yellow Cartridge [Printer] The cartridge fill level

2153
Channel Description
More
KNOWLEDGE BASE


2154
7.8.225 SNMP QNAP Logical Disk Sensor
The SNMP QNAP Logical Disk sensor monitors a logical disk in a Quality Network Appliance Provider
(QNAP) network-attached storage (NAS) via the Simple Network Management Protocol (SNMP).
SNMP QNAP Logical Disk Sensor
List 2158 .

§ Dutch: SNMP QNAP Logische Schijf
§ French: QNAP disque logique (SNMP)
§ German: SNMP QNAP Logischer Datenträger
§ Japanese: SNMP QNAP
§ Portuguese: Disco lógico QNAP (SNMP)
§ Russian: QNAP SNMP

§ Simplified Chinese: SNMP QNAP
§ Spanish: Disco lógico QNAP (SNMP)
Remarks
2155
Remark Description
channels.
you add the sensor:
§ logicaldisk
§ qnap
§ snmpqnap
QNAP NAS Settings
QNAP NAS Settings
2156
Setting Description
Disk The logical disk that this sensor monitors.
Description The name of the disk that this sensor monitors.
File System The file system of the disk that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
2157
Inherited Settings
Channel List
Channel Description

Volume Status The volume status

§ Up status: Ready
§ Warning status: In Degraded Mode, Rebuilding, Synchronizing
§ Down status: Failure
More
KNOWLEDGE BASE

Why do I get DoS alarms on my QNAP?


2158
7.8.226 SNMP QNAP Physical Disk Sensor
The SNMP QNAP Physical Disk sensor monitors a physical disk in a Quality Network Appliance
Provider (QNAP) network-attached storage (NAS) via the Simple Network Management Protocol (SNMP).
SNMP QNAP Physical Disk Sensor
List 2162 .

§ Dutch: SNMP QNAP Fysieke Schijf
§ French: QNAP disque physique (SNMP)
§ German: SNMP QNAP Physikalischer Datenträger
§ Portuguese: Disco físico QNAP (SNMP)

§ Spanish: Disco físico QNAP (SNMP)
Remarks
2159
Remark Description
channels.
you add the sensor:
§ physicaldisk
§ qnap
§ snmpqnap
QNAP NAS Settings
QNAP NAS Settings
2160
Setting Description
Description Information about the physical disk that this sensor monitors.
Model The model of the physical disk that this sensor monitors.
Capacity The capacity of the physical disk that this sensor monitors.
Unit The unit of temperature measurement.
Sensor Display
Sensor Display
Setting Description


other above.
2161
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
HD Status The disk status
§ Up status: Ready
§ Down status: Invalid, No Disk, RwError, Unknown
S.M.A.R.T. Status The S.M.A.R.T. status

§ Up status: Good, Normal
§ Down status: Bad

More
KNOWLEDGE BASE
2162


2163
7.8.227 SNMP QNAP System Health Sensor
The SNMP QNAP System Health sensor monitors the system health of a Quality Network Appliance
Provider (QNAP) network-attached storage (NAS) via the Simple Network Management Protocol (SNMP).
SNMP QNAP System Health Sensor
List 2166 .

§ Dutch: SNMP QNAP Systeemstatus
§ French: QNAP état du système (SNMP)
§ German: SNMP QNAP Systemzustand
§ Portuguese: Saúde do sistema QNAP (SNMP)

§ Spanish: Salud de sistema QNAP (SNMP)
Remarks
2164
Remark Description
you add the sensor:
§ qnap
§ snmpqnap
§ systemhealth
QNAP NAS Settings
QNAP NAS Settings
Setting Description
Unit The unit of temperature measurement.
2165
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2166
Channel Description
CPU Temperature The CPU temperature
Fan [#] (System FAN [#]) The fan RPM
System Temperature The system temperature
More
KNOWLEDGE BASE



2167
7.8.228 SNMP Rittal CMC III Hardware Status Sensor
The SNMP Rittal CMC III Hardware Status sensor monitors the overall status of Rittal data center
hardware, for example Rittal Computer Multi Control version 3 (CMC III) processing units, Rittal power
distribution units (PDU), or Rittal IoT Interfaces and the hardware status of every attached external
sensor via the Simple Network Management Protocol (SNMP).
SNMP Rittal CMC III Hardw are Status Sensor
List 2170 .

§ Dutch: SNMP Rittal CMC III hardwarestatus
§ French: Rittal CMC III statut matériel (SNMP)
§ German: SNMP Rittal CMC III Hardware Status
§ Japanese: SNMP Rittal CMC III
§ Portuguese: Status hardware Rittal CMC III (SNMP)
§ Russian: Rittal CMC III, SNMP

§ Simplified Chinese: SNMP Rittal CMC III
§ Spanish: Estado hardware Rittal CMC III (SNMP)
2168
Remarks
Remark Description
channels.
you add the sensor:
§ cmc3
§ snmprittal
Sensor Display
Sensor Display
2169
Setting Setting


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
2170
Channel Description
Overall Device Status The overall device status

§ Up status: OK, Update
§ Warning status: Warning, Detected, Changed
§ Down status: Alarm, Lost
[Status of attached An attached external sensor status

external sensor]
§ Up status: OK; Firmware Update Pending; Firmware Update Running
§ Warning status: Device Detected, Confirmation Required; Device

Changed
§ Down status: Device Not Available; Device Lost (Disconnected),
Confirmation Required; Error
More
KNOWLEDGE BASE

2171
7.8.229 SNMP RMON Sensor
The SNMP RMON sensor monitors traffic on a device using the Remote Monitoring (RMON) standard via
You can create it on an SNMP-compatible device that provides traffic data via RMON. Depending on
the data that the device returns, PRTG displays traffic data for each port in different channels, which
allows a detailed analysis. If available, the sensor queries 64-bit counters.
SNMP RMON Sensor
List 2175 .

§ Dutch: SNMP RMON
§ French: RMON (SNMP)
§ German: SNMP RMON
§ Japanese: SNMP RMON
§ Portuguese: RMON (SNMP)
§ Russian: RMON SNMP

§ Simplified Chinese: SNMP RMON
2172
§ Spanish: RMON (SNMP)
Remarks
Remark Description
Port name templates § You can define the displayed sensor name with port name templates in
the SNMP compatibility options of the parent device.
Knowledge Base § Knowledge Base: What value does the Transmitted channel of an
RMON sensor show?
§ Knowledge Base: Automatically update port name and number for
SNMP Traffic sensors when the device changes them
you add the sensor:
§ snmprmon
2173
RMON Specific
RMON Specific
Setting Description
Port The number of the interface port that this sensor monitors.
Channel Mask Describes which channels are available. This information might be useful
for the Paessler support team.
Sensor Display
Sensor Display
Setting Description


2174
Setting Description
other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Broadcast Packets The number of broadcast packets
Collisions The number of collisions
CRC Errors The number of CRC errors
Drop Events The number of drop events
Fragments The number of fragments
Jabbers The number of jabbers
Multicast Packets The number of multicast packets
2175
Channel Description
Oversize Packets The number of oversize packets
Packets The number of packets
Packets <= 64 Byte The number of packets with less than or equal to 64 bytes
Packets 65 - 127 Bytes The number of packets with 65 - 127 bytes
Packets 512 - 1023 The number of packets with 512 - 1023 bytes
Bytes
Packets 1024 - 1518 The number of packets with 1024 - 1518 bytes
Bytes
Transmitted The transmitted bytes

Undersize Packets The number of undersize packets
More
KNOWLEDGE BASE
What value does the Transmitted channel of an RMON sensor show?




2176
7.8.230 SNMP SonicWall System Health Sensor
The SNMP SonicWall System Health sensor monitors health values of a SonicWall Network Security
Appliance (NSA) via the Simple Network Management Protocol (SNMP).
SNMP SonicWall System Health Sensor
List 2179 .

§ Dutch: SNMP SonicWall Systeemstatus
§ French: SonicWall état du système (SNMP)
§ German: SNMP SonicWall Systemzustand
§ Japanese: SNMP SonicWall
§ Portuguese: Saúde do sistema SonicWall (SNMP)
§ Russian: SonicWall SNMP

§ Simplified Chinese: SNMP SonicWall
§ Spanish: Salud de sistema SonicWall (SNMP)
Remarks
2177
Remark Description
Knowledge Base § Knowledge Base: Why does PRTG write error messages into my
SonicWall log?
you add the sensor:
§ snmpsonicwallsystemhealthsensor
§ systemhealth
Sensor Display
Sensor Display
Setting Description
2178
Setting Description



other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Connection Cache Used The connection cache usage (%)

2179
Channel Description
More
KNOWLEDGE BASE
Why does PRTG write error messages into my SonicWall log?



2180
7.8.231 SNMP SonicWall VPN Traffic Sensor
The SNMP SonicWall VPN Traffic sensor monitors the traffic of an Internet Protocol Security (IPsec)
VPN on a SonicWall Network Security Appliance (NSA) via the Simple Network Management Protocol
(SNMP).
SNMP SonicWall VPN Traffic Sensor
List 2185 .

§ Dutch: SNMP SonicWall VPN Verkeer
§ French: SonicWall trafic VPN (SNMP)
§ German: SNMP SonicWall VPN-Datenverkehr
§ Japanese: SNMP SonicWall VPN
§ Portuguese: Tráfego de VPN SonicWall (SNMP)
§ Russian: VPN SonicWall SNMP

§ Simplified Chinese: SNMP SonicWall VPN
§ Spanish: Tráfico VPN SonicWall (SNMP)
Remarks
2181
Remark Description
Knowledge Base § Knowledge Base: Why does PRTG write error messages into my
SonicWall log?
Add Sensor
Setting Description
Connection Select the connections that you want to monitor. PRTG creates one
sensor for each connection that you select.
you add the sensor:
§ snmpsonicwallvpntrafficsensor
§ traffic
2182
SonicWall VPN Specific
SonicWall VPN Specific
Setting Description
Security Policy The security policy of the connection that this sensor monitors.
Remote IP Address The remote IP address of the connection that this sensor monitors.
Source IP Addresses The source IP addresses of the connection that this sensor monitors.
Destination IP Addresses The destination IP addresses of the connection that this sensor monitors.
Index The index of the connection that this sensor monitors.
Identification Method Define how you want to identify the connection that you want to monitor:
§ Index: Every connection has a unique index. This is the safest method
to identify your connection. If the connection is lost and reconnected, it
receives a new index.
§ Remote IP address: If the target of the VPN always has the same IP
address, you can use this IP address to identify the connection.
§ Security policy name: If you use a different security policy for every
VPN, you can use its name to identify the connection.
§ Remote IP address and security policy name: You can also combine
both identification methods.
§ Remote IP address, security policy name, and IP address ranges: If
you use separate connections for specific IP address ranges, identify
the connection by remote IP address, security policy name, and IP
address ranges.
2183
Setting Description
§ IP address ranges: Use IP address ranges only to identify the

connection.
The sensor always uses the first connection that it finds that
matches all criteria.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
2184
Inherited Settings
Channel List
Channel Description
Decrypted Packets The number of decrypted packets
Decrypted Transmissions The decrypted transmissions
Encrypted Packets The number of encrypted packets

Encrypted Transmissions The encrypted transmissions
Fragmented Packets In The number of incoming fragmented packets
Fragmented Packets Out The number of outgoing fragmented packets
More
KNOWLEDGE BASE
Why does PRTG write error messages into my SonicWall log?



2185
7.8.232 SNMP Synology Logical Disk Sensor
The SNMP Synology Logical Disk sensor monitors a logical disk in a Synology network-attached
storage (NAS) via the Simple Network Management Protocol (SNMP).
SNMP Synology Logical Disk Sensor
List 2189 .

§ Dutch: SNMP Synology Logische Schijf
§ French: Synology disque logique (SNMP)
§ German: SNMP Synology Logischer Datenträger
§ Japanese: SNMP Synology
§ Portuguese: Disco lógico Synology (SNMP)
§ Russian: Synology SNMP

§ Simplified Chinese: SNMP Synology
§ Spanish: Disco lógico Synology (SNMP)
Remarks
2186
Remark Description
channels.
you add the sensor:
§ logicaldisk
§ snmpsynology
§ synology
Synology NAS Settings
Setting Description
2187
Setting Description

monitoring data.
Sensor Display
Sensor Display
Setting Description

other above.
procedure to do so.
2188
Inherited Settings
Channel List
Channel Description
Volume Status The volume status

§ Up status: Converting SHR to Pool, Data Scrubbing, Deploying,
Expanding Unfinished SHR, Migrating SHR to Pool, Migrating SHR1 to
SHR2, Mounting Cache, Normal, Parity Checking, Undeploying,
Unmounting Cache
§ Warning status: Assembling, Creating, Expanding, Migrating,
Repairing, Syncing
§ Down status: Canceling, Crashed, Degrade, Deleting, Unknown
More
KNOWLEDGE BASE


2189
7.8.233 SNMP Synology Physical Disk Sensor
The SNMP Synology Physical Disk sensor monitors a physical disk in a Synology network-attached
SNMP Synology Physical Disk Sensor
List 2193 .

§ Dutch: SNMP-Synology Fysieke Schijf
§ French: Synology disque physique (SNMP)
§ German: SNMP Synology Physikalischer Datenträger
§ Portuguese: Disco físico Synology (SNMP)

§ Spanish: Disco físico Synology (SNMP)
Remarks
2190
Remark Description
channels.
you add the sensor:
§ physicaldisk
§ snmpsynology
§ synology
2191
Setting Description
Disk Name The name of the disk that this sensor monitors.
Model The model of the physical disk that this sensor monitors.
Type The type of the physical disk that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
2192
Inherited Settings
Channel List
Channel Description

§ Up status: Initialized, Normal
§ Warning status: NotInitialized
§ Down status: Crashed, SystemPartitionFailed

More
KNOWLEDGE BASE


2193
7.8.234 SNMP Synology System Health Sensor
The SNMP Synology System Health sensor monitors the system health of a Synology network-attached
SNMP Synology System Health Sensor
List 2196 .

§ Dutch: SNMP-Synology Systeemstatus
§ French: Synology état du système (SNMP)
§ German: SNMP Synology Systemzustand
§ Portuguese: Saúde do sistema Synology (SNMP)

§ Spanish: Salud de sistema Synology (SNMP)
Remarks
2194
Remark Description
channels.
Knowledge Base § Knowledge Base: Why does my Synology System Health sensor show
incorrect CPU and memory values?
you add the sensor:
§ snmpsynology
§ synology
§ systemhealth
Sensor Display
Sensor Display
2195
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
CPU Fan Status The CPU fan status

2196
Channel Description
CPU Load The CPU load (%)

For more information about the shown memory and CPU load values,
see the Knowledge Base: Why does my Synology System Health
sensor show incorrect CPU and memory values?
Memory Free The free memory (%)

For more information about the shown memory and CPU load values,
see the Knowledge Base: Why does my Synology System Health
sensor show incorrect CPU and memory values?
Power Status The power status

System Fan Status The system fan status

System Status The system status

More
KNOWLEDGE BASE
Why does my Synology System Health sensor show incorrect CPU and memory values?

2197
2198
7.8.235 SNMP System Uptime Sensor
The SNMP System Uptime sensor monitors the uptime of a device via the Simple Network Management
Protocol (SNMP).
SNMP System Uptime Sensor
List 2201 .

§ Dutch: SNMP Systeem Uptime
§ French: Disponibilité du système (SNMP)
§ German: SNMP Laufzeit
§ Japanese: SNMP
§ Portuguese: Tempo de atividade do sistema (SNMP)
§ Russian: SNMP
§ Spanish: Tiempo activo del sistema (SNMP)
Remarks
2199
Remark Description
Knowledge Base § Knowledge Base: Why does the SNMP System Uptime sensor report
wrong values?
you add the sensor:
§ snmpuptimesensor
Sensor Display
Sensor Display
2200
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
2201
Channel Description
System Uptime The uptime

More
KNOWLEDGE BASE
Why does the SNMP System Uptime sensor report wrong values?


2202
7.8.236 SNMP Traffic Sensor
The SNMP Traffic sensor monitors traffic on a device via the Simple Network Management Protocol
(SNMP).
You can create the sensor on a device that provides traffic data.
SNMP TrafficSensor
List 2208 .

§ Dutch: SNMP Verkeer
§ French: Trafic (SNMP)
§ German: SNMP Datenverkehr
§ Japanese: SNMP
§ Portuguese: Tráfego (SNMP)
§ Russian: SNMP
§ Spanish: Tráfico (SNMP)
Remarks
2203
Remark Description
SNMP v2c or SNMP v3 § We recommend that you select SNMP v2c (most common) or SNMP
v3 in the credentials for SNMP devices of the parent device (if supported
by the target device). SNMP v1 does not support 64-bit counters, which
might result in invalid data. For more information, see the Knowledge
Base: SNMP Traffic sensor suddenly drops at 610Mbps
Port name templates § You can define the displayed sensor name with port name templates in
the SNMP compatibility options of the parent device.
Auto-discovery § The auto-discovery always creates SNMP Traffic sensors for all
interfaces whose SNMP traffic counters are above 0. As a result, every
interface that has had traffic since the last restart of the target system
is added, even if it is currently disconnected or disabled. For more
information, see the Knowledge Base: How does auto-discovery with
SNMP Traffic sensors work?
Knowledge Base § Knowledge Base: Automatically update port name and number for
SNMP Traffic sensors when the device changes them
Add Sensor
Setting Description
Name for Traffic In For the standard channel Traffic In, enter the channel name. The sensor
Channel shows it in graphs and tables.
You can change this description in the channel settings later.
Name for Traffic Out For the standard channel Traffic Out, enter the channel name. The sensor
Channel shows it in graphs and tables.
2204
Setting Description
Name for Traffic Total For the standard channel Traffic Total, enter the channel name. The
Channel sensor shows it in graphs and tables.
you add the sensor:
§ bandwidthsensor
§ snmptrafficsensor
Traffic Specific
Traffic Specific
2205
Setting Description
Interface Number The number and name of the interface in the physical device that this
sensor monitors.

monitoring data.
Additional Channels By default, each SNMP Traffic sensor creates the channels Traffic In,
Traffic Out, and Traffic Total. Select additional channels for all interfaces.
Click the respective channel names to mark the channels and to monitor
their data:
§ Errors in and errors out: The number of incoming and outgoing packets
that could not be delivered because of errors.
§ Discards in and discards out: The number of discarded incoming and
outgoing packets even though no errors have been detected.
§ Unicast packets in unicast packets out: The number of unicast packets
that have been delivered.
§ Non unicast packets in and non unicast packets out (32-bit only): The
number of non-unicast packets that have been delivered.
§ Multicast packets in and multicast packets out (64-bit only): The
number of delivered packets that were addressed to a multicast
address.
§ Broadcast packets in and broadcast packets out (64-bit only): The
number of delivered packets that were addressed to a broadcast
address
§ Unknown protocols: The number of received packets that were

discarded because of an unknown or unsupported protocol.
You cannot delete additional channels later. You can only disable
them.
If the sensor shows the Warning status with the message Channels
not available, you can disable the affected channels to remove the
warning.
Connection Status An interface is not operational if, for example, an Ethernet port on a
Handling switch with no cable plugged in. This setting is valid for all selected
interfaces.
Define how PRTG reacts when an interface is operational:
§ Show down status for all disconnected states: Show the Down status
for a disconnected interface. This applies if the ifOperStatus of the
interface is not "up".
§ Show down status when disconnected, ignore when deactivated: Show
the Down status for a disconnected interface only if it is not deliberately
deactivated in the configuration. This applies if the ifOperStatus of the
interface is not "up" and the ifAdminStatus is "up". So the sensor stays
2206
in the Up status when the interface has been deactivated.
§ Ignore all disconnected states (default): Show the Up status.
Monitoring is discontinued without notice.
Sensor Display
Sensor Display
Setting Description


§ Show in and out traffic as positive and negative area graph: Show
channels for incoming and outgoing traffic as positive and negative area
graph. This visualizes your traffic in a clear way.
Axis Scaling (available in the channel settings). Manual scaling is
not possible if you choose this option.
You cannot show a positive/negative graph for a channel if you
choose to display its data in percent of maximum (available in the
channel settings).
other above.
procedure to do so.
2207
Inherited Settings
Channel List
Channel Description
Discards In The number of incoming discards
Discards Out The number of outgoing discards
Non-Unicast In The number of incoming non-unicast packets
Non-Unicast Out The number of outgoing non-unicast packets
Traffic Total The total traffic

Unicast In The number of incoming unicast packets
Unicast Out The number of outgoing unicast packets
Unknown Protocols In The number of incoming, unknown protocols
2208
More
KNOWLEDGE BASE
How does auto-discovery with SNMP Traffic sensors work?



SNMP Traffic sensor suddenly drops at 610Mbps


2209
7.8.237 SNMP Traffic v2 Sensor (BETA)
The SNMP Traffic v2 sensor monitors bandwidth and traffic on a device via the Simple Network
all.
SNMP Traffic v2 Sensor
List 2216 .

§ Dutch: SNMP Traffic v2
§ French: Trafic v2 (SNMP)
§ German: SNMP-Datenverkehr v2
2210
§ Portuguese: Tráfego (SNMP) v2
§ Russian: SNMP Traffic v2

§ Spanish: Tráfico (SNMP) v2
Remarks
Remark Description
SNMP v2c or SNMP v3 § We recommend that you select SNMP v2c (most common) or SNMP
v3 in the credentials for SNMP devices of the parent device (if supported
by the target device). SNMP v1 does not support 64-bit counters, which
might result in invalid data. For more information, see the Knowledge
Base: SNMP Traffic sensor suddenly drops at 610Mbps
SNMP compatibility § This sensor is not affected by the following SNMP compatibility options
options set in the parent device: Port Name Template, Port Name Update, Port
Identification, Start Interface Index, and End Interface Index.
Knowledge Base § Knowledge Base: Where is the volume line in graphs?
2211
you add the sensor:
§ bandwidthsensor
§ snmp
§ snmptrafficsensor
SNMP Interface
SNMP Interface
Setting Description
Description The description of the interface in the physical device that this sensor
monitors. The internal name is found in the ifTable under ifDescr.

monitoring data.
64-Bit If the interface that this sensor monitors uses 64-bit counters.

monitoring data.
2212
SNMP Traffic Specific
SNMP Traffic Specific
2213
Setting Description
Additional Channels By default, each SNMP Traffic v2 sensor creates the channels Traffic In,
Traffic Out, and Traffic Total. Select additional channels for all interfaces.
Click the respective channel names to mark the channels and to monitor
their data.
You can choose between the following additional channels:
§ Errors in and errors out: The number of incoming and outgoing packets
that could not be delivered because of errors.
§ Discards in and discards out: The number of discarded incoming and
outgoing packets even though no errors have been detected.
§ Unicasts in and unicasts out: The number of unicast packets that have
been delivered.
§ Non-unicasts in and non-unicasts out: The number of non-unicast
packets that have been delivered.
These channels might not function properly with 64-bit interfaces.
§ Multicasts in and multicasts out (64-bit only): The number of delivered
packets that were addressed to a multicast address.
§ Broadcasts in and broadcasts out (64-bit only): The number of delivered
packets that were addressed to a broadcast address.
§ Unknown protocols in: The number of received packets that were
discarded because of an unknown or unsupported protocol.
You cannot delete additional channels later. You can only disable
them.
If the sensor shows the Warning status with the message Channels
not available, you can disable the affected channels to remove the
warning.
Connection Status An interface that is not operational if, for example, an Ethernet port on a
Handling switch with no cable plugged in. This setting is valid for all selected
interfaces.
Define how PRTG reacts when an interface is operational:
§ Show the 'Down' status anytime ifOperStatus is not 'Up': Show the
Down status for a disconnected interface. This applies if the
ifOperStatus of the interface is not 'up'.
§ Show the 'Down' status when ifAdminStatus is 'Up' but ifOperStatus is
not: Show the Down status for a disconnected interface only if it is not
deliberately deactivated in the configuration. This applies if the
ifAdminStatus is 'up' and the ifOperStatus of the interface is not 'up'.
The sensor stays in the Up status when the interface has been
deactivated.
§ Ignore all disconnected states (default): Show the Up status.
Monitoring is discontinued without notice.
2214
Sensor Display
Sensor Display
Setting Description


channel settings).
other above.
procedure to do so.
2215
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Broadcasts In The number of incoming broadcast packets
Broadcasts Out The number of outgoing broadcast packets
2216
Channel Description
Multicasts In The number of incoming multicast packets
Multicasts Out The number of outgoing multicast packets
Non-Unicasts In The number of incoming non-unicast packets
Non-Unicasts Out The number of outgoing non-unicast packets
Traffic Total The total traffic

Unicasts In The number of incoming unicast packets
Unicasts Out The number of outgoing unicast packets
Unknown Protocols In The number of incoming, unknown protocols
More
KNOWLEDGE BASE


SNMP Traffic sensor suddenly drops at 610Mbps
2217

2218
7.8.238 SNMP Trap Receiver Sensor
The SNMP Trap Receiver sensor receives and analyzes Simple Network Management Protocol (SNMP)
traps.
The sensor can also show the actual trap messages.
SNMP Trap Receiver Sensor
List 2227 .

§ Dutch: SNMP Trap-ontvanger
§ French: Récepteur de Trap (SNMP)
§ German: SNMP-Trap-Empfänger
§ Japanese: SNMP
§ Portuguese: Receptor de trap SNMP
§ Russian: SNMP
§ Spanish: Receptor de trap SNMP
Remarks
2219
Remark Description
SNMP v3 traps § This sensor does not support SNMP v3 traps. Use SNMP v1 or v2c.
UDP § This sensor only supports the User Datagram Protocol (UDP).
Probe device § Add this sensor to the probe device to receive all messages of the
remote probe system.
§ If you add the sensor to a device other than a probe device, the IP
address or Domain Name System (DNS) name of the parent device
must match the proper sender. For example, if you want to receive
messages from a storage area network (SAN), you might need to add a
device with the IP address of a specific array member that sends the
messages. Providing a DNS name that points to the IP address of a
whole group might not work for SANs.
Specific device § Add this sensor to a specific device to directly receive all messages
from this device. This is faster than using source filters.
Placeholders § You can use placeholders in email notification templates to see

messages when you receive email notifications.
Sensor states § The sensor states of this sensor persist for one scanning interval only.
After showing the Warning or the Down status, and if there is no
warning or error message in the next scanning interval, the sensor
shows the Up status again. For more information on a workaround, see
the Knowledge Base: How can I configure sensors using speed limits
to keep the status for more than one interval?
Filter options § You can use the filter options to define which types of messages the
sensor considers for monitoring, and which messages it categorizes as
warnings or errors.
MIB file § In PRTG Network Monitor, you can copy the Management Information
Base (MIB) file for your traps to the \MIB subfolder of the PRTG
program directory to translate the object identifiers (OID) for the traps
into readable messages. For more information, see the Knowledge
Base: How can I show the name of a received OID in PRTG?
To import MIB files into PRTG Hosted Monitor, see section Manage a
PRTG Hosted Monitor Subscription.
2220
Remark Description
Knowledge Base § Knowledge Base: How do I test an SNMP Trap Receiver sensor?
probe device.
you add the sensor:
§ snmptrapsensor
SNMP Trap Specific
SNMP Trap Specific
Setting Description
Port Enter the number of the port on which the sensor listens for SNMP traps.
The default port is 162. Enter an integer.
2221
Setting Description
Purge Messages After Define for how long PRTG stores received trap messages for analysis.
Choose a period of time from the dropdown list.
Filter
Filter
2222
Setting Description
Include Filter Define if you want to filter traps. If you leave this field empty or use the
keyword any, the sensor processes all data. To include only specific
types of traps, define filters using a special syntax.
Exclude Filter Define which types of traps the sensor discards and does not process. To
exclude specific types of traps, define filters using a special syntax.
Warning Filter Define which types of traps count for the Warnings channel. To categorize
received traps as warning messages, define filters using a special syntax.
The sensor collects messages until a scanning interval ends. As long
as the scanning interval is running, no status change happens. By
default, the sensor changes to the Warning status after a scanning
interval finishes and there was at least one warning message (and no
error message) during this scanning interval. The sensor shows the
Warning status at least until the succeeding scanning interval finishes. If
the sensor does not receive any warning or error message in this
scanning interval, its status changes to the Up status again with the start
of the next scanning interval.
Error Filter Define which types of traps count for the Errors channel. To categorize
received traps as error messages, define filters using a special syntax.
as the scanning interval is running, no status change happens. By
default, the sensor changes to the Down status after a scanning interval
finishes and there was at least one error message during this scanning
interval. The sensor shows the Down status at least until the succeeding
scanning interval finishes. If the sensor does not receive any warning or
error message in this scanning interval, its status changes to the Up
status again with the start of the next scanning interval.
Sensor Display
Sensor Display
2223
Setting Description


other above.
procedure to do so.
Inherited Settings
Debug Options
Debug Options
Setting Description
2224
Setting Description
§ Store result: Store the last sensor result in the \Logs\debug subfolder of
the PRTG data directory on the probe system. The file name is Sensor
[ID]_[Date].log. This setting is for debugging purposes.
Use with caution. We recommend that you only use this setting for
a short time because it can create huge data files.
Filter Rules
Filter rules are used for the include, exclude, warning, and error definition fields of the SNMP Trap
Receiver sensor. They are based on the following format:
field[filter]
You can use include and exclude filters to define which traps to monitor or use warning and error filters to
define how to categorize received traps. Provide these filters in the sensor settings as formulas.
Formulas are fields that you can combine with boolean operators (AND, OR, NOT) and brackets.
Field Parameter Examples
source[ip] Enter an IP address where the UDPs come from. IP source[10.0.23.50],

masks and ranges are also possible. source[10.0.23.10-50],
source[10.0.23.10/24]
agent[ip] Enter an IP address that specifies the object that agent[10.0.0.1]

creates the SNMP trap.
agent[ip] only supports v1.
enterprise[oid] Enter an OID that specifies the object that originates the enterprise[1.3.6.1.4.1.2.6.182.
trap. 1.2.31.1.0]
enterprise[oid] only supports v1.
bindings[text] Enter a substring to match all OIDs and values in the bindings[ERROR],
bindings. bindings[1.3.6.1.4.1.2.6.182.1
.2.31.1.0],
bindings["port blocked"]
It is not necessary to use
quotation marks (") to find
strings. If the string contains
quotation marks that you want
to include in the filter, you
need to escape them with
quotation marks.
bindings Enter an OID and a substring to match a value in the bindings[1.3.6.1.4.1.2.6.182.1

[oid,value] specified OID. Separate the OID and the value with a .2.31.1.0,error]
comma.
2225
Field Parameter Examples
bindings Enter an OID, a substring, and a mode to match a value bindings[1.3.6.1.4.1.2.6.182.1

[oid in the specified OID. Separate the OID, the value, and .2.31.1.0,error,exact]
,value,mode] the mode with a comma. The mode can be: bindings[1.3.6.1.4.1.2.6.182.1
.2.31.1.0,10,equal]
§ substring (default): This mode works like
bindings[oid,value].
§ exact: This mode enforces an exact match of a value.
§ equal, greater, greaterorequal, less, or lessorequal:

This interprets and compares values as numbers.
This mode only supports integers without extra
characters and without thousands separators.
It also supports hex format.
gentrap Enter a number that specifies the generic trap type. gentrap[3], gentrap[2-6]
[number]
You can also enter ranges.
spectrap Enter a number that defines the specific trap code. spectrap[4], spectrap[0-3]
[number]
You can also enter ranges.
version[number] Enter a number (1 or 2) that specifies the SNMP version. version[1], version[2]
community Enter a community string for an exact, case-sensitive community[public],

[text] match. community[private]
Messages Tab: Review and Analyze Traps

PRTG stores received traps as common files in the \Trap Database subfolder of the PRTG data directory.
To review and analyze all received messages, you can directly access the most recent data in a table
list in the PRTG web interface. You can access this list via the sensor's Overview tab.
PRTG only shows received traps in the table on the Overview tab after an (automatic) page refresh
following a sensor scan. The default value for auto refresh is 30 seconds.
For more details and further filter options, click the Messages tab of the SNMP Trap Receiver sensor.
You see all received messages in a table list. At the top, you have display filter options to drill down into
the data for specific events of your interest. The filters are the same as those that are available in the
sensor settings, but you can define them without using formulas. Provide the desired parameters and
PRTG automatically loads the filtered list.
PRTG automatically applies boolean operators to the filters in the following manner: parameters
across all columns are combined with AND, and parameters within a single column are combined
with OR.
The parameters that you enter in the filters must exactly match the parameters in the message.
They are case-sensitive.
You can automatically add a filter by clicking the content of a column.
Advanced Filter Settings
2226
You can open advanced filter settings by clicking in the Filter row. The Advanced Filter appears in a
popup window. In the text field, you can define a filter using the syntax as described in section Filter
Rules 2225.
If you provided filter parameters on the Messages tab, the advanced filter already includes them as a
corresponding formula with the correct syntax. You can adjust this filter to your needs. You can also
copy the automatically created and manually adjusted formula for usage in the filter fields of the sensor
settings.
Channel List
Channel Description
Drops The number of dropped packets on the SNMP trap collector port
Errors The number of messages categorized as "error"

Messages The overall number of received traps

Warnings The number of messages categorized as "warning"

More
KNOWLEDGE BASE
How can I show the name of a received OID in PRTG?

2227
How do I test an SNMP Trap Receiver sensor?


2228
7.8.239 SNMP Uptime v2 Sensor
The SNMP Uptime v2 sensor monitors the uptime of a device via the Simple Network Management
Protocol (SNMP).
SNMP Uptime v2 Sensor
List 2233 .

§ Dutch: SNMP Uptime v2
§ French: Disponibilité v2 (SNMP)
§ German: SNMP Laufzeit v2
§ Portuguese: Tempo de atividade (SNMP) v2
§ Russian: SNMP Uptime v2

§ Spanish: Tiempo de actividad (SNMP) v2
Remarks
2229
Remark Description
Credentials § This sensor requires credentials for SNMP in settings that are higher in
the object hierarchy.
you add the sensor:
§ snmp
§ snmpuptimesensor
§ uptime
§ uptimesensor
2230
SNMP Uptime Specific
SNMP Uptime Specific
Setting Description
Data Source Select the object identifier (OID) the sensor gets its uptime from:
§ Automatic (default): Use HOST-RESOURCES-V2-
MIB::hrSystemUptime and fall back to SNMPv2-MIB::sysUpTime.
§ Use HOST-RESOURCES-V2-MIB::hrSystemUptime: Use HOST-
RESCOURCES-V2-MIB::hrSystemUptime.
§ Use SNMPv2-MIB::sysUpTime: Use SNMPv2-MIB::sysUpTime.
§ Use SNMP-FRAMEWORK-MIB::snmpEngineTime: Use SNMP-

FRAMEWORK-MIB::snmpEngineTime.
Sensor Display
Sensor Display
Setting Description

2231
Setting Description

other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
2232
Channel List
Channel Description

More
KNOWLEDGE BASE
Why does the SNMP System Uptime sensor report wrong values?

2233
7.8.240 SNMP Windows Service Sensor
The SNMP Windows Service sensor monitors a Windows service via the Simple Network Management
Protocol (SNMP).
SNMP Window s Service Sensor
List 2236 .

§ Dutch: SNMP Windows Service
§ French: Windows service (SNMP)
§ German: SNMP Windows-Dienst
§ Japanese: SNMP Windows
§ Portuguese: Serviço Windows (SNMP)
§ Russian: Windows SNMP

§ Simplified Chinese: SNMP Windows
§ Spanish: Servicio Windows (SNMP)
Remarks
Remark Description
"not installed" status § This sensor cannot distinguish the status "not installed" from "not
running".
2234
Remark Description
channels.
you add the sensor:
§ servicesensor
§ snmpservicesensor
SNMP Windows Service Monitor
SNMP Window s Service Monitor
Setting Description
Service The Windows service that this sensor monitors.
2235
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2236
Channel Description
Operating State The target device operating status
§ Up status: Active
§ Down status: Continue-Pending, Pause-Pending, Paused
More
KNOWLEDGE BASE


2237
7.8.241 SNTP Sensor
The SNTP sensor monitors a Simple Network Time Protocol (SNTP) server.
The sensor tries to get a valid time stamp from the server up to three times per scan until it reports
an error.
SNTP Sensor
List 2240 .

§ Dutch: SNTP
§ French: SNTP
§ German: SNTP
§ Japanese: SNTP
§ Portuguese: SNTP
§ Russian: SNTP
§ Simplified Chinese: SNTP
§ Spanish: SNTP
Remarks
2238
Remark Description
you add the sensor:
§ sntpsensor
Sensor Specific
Sensor Specific
Setting Description
2239
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2240
Channel Description
Difference The time difference in comparison to the local system time

More
KNOWLEDGE BASE

2241
7.8.242 Soffico Orchestra Channel Health Sensor
The Soffico Orchestra Channel Health sensor monitors the state and the overall number of successful or
unsuccessful channel calls.
The sensor supports inbound and outbound channels.
Soffico Orchestra Channel Health Sensor
List 2246 .

§ Dutch: Soffico Orchestra Kanaal Gezondheid
§ French: Soffico Orchestra état de canal
§ German: Soffico Orchestra Channel-Zustand
§ Japanese: Soffico Orchestra
§ Portuguese: Funcionamento do canal do Soffico Orchestra
§ Russian: Soffico Orchestra

§ Simplified Chinese: Soffico Orchestra
§ Spanish: Salud del canal Orchestra Soffico
Remarks
2242
Remark Description
Soffico license and § This sensor requires a Soffico license and as of Orchestra 4.8.2.5.
Orchestra version
Credentials § This sensor requires credentials for Soffico Orchestra in the settings of
the parent device.
channels.
Scanning interval § The recommended scanning interval of this sensor is 5 minutes.
you add the sensor:
§ orchestra
§ orchestrachannelhealth
§ soffico
2243
Orchestra Channel Specific
Orchestra Channel Specific
Setting Description
Channel Name The name of the Orchestra channel that this sensor monitors.
The channel name consists of the Orchestra scenario, a slash, and
the Orchestra channel name.
Channel Type The type of the Orchestra channel that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


2244
Setting Description
other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
2245
Channel List
Channel Description
Adapter State The adapter status

§ Up status: Offline, Online
§ Warning status: Not Installed, Unknown
§ Down status: Online With Error
Error Count The number of errors
OK Count The number of OKs
More
KNOWLEDGE BASE
2246
7.8.243 Soffico Orchestra Scenario Sensor
The Soffico Orchestra Scenario sensor monitors the status of processes within an Orchestra scenario.
Soffico Orchestra Scenario Sensor
List 2250 .

§ Dutch: Soffico Orchestra Scenario
§ French: Scénario Soffico Orchestra
§ German: Soffico Orchestra-Szenario
§ Japanese: Soffico Orchestra
§ Portuguese: Cenário do Soffico Orchestra
§ Russian: Soffico Orchestra

§ Simplified Chinese: Soffico Orchestra
§ Spanish: Escenario Soffico Orchestra
Remarks
2247
Remark Description
Soffico license and § This sensor requires a Soffico license and as of Orchestra 4.8.2.5.
Orchestra version
Credentials § This sensor requires credentials for Soffico Orchestra in the settings of
the parent device.
you add the sensor:
§ orchestra
§ orchestrascenario
§ soffico
2248
Orchestra Scenario Specific
Orchestra Scenario Specific
Setting Description
Base Path The base path of the Orchestra scenario that this sensor monitors.
Scenario Name The name of the Orchestra scenario that this sensor monitors.
Sensor Display
Sensor Display
Setting Description


other above.
2249
Setting Description
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Channel List
2250
Channel Description
Aborted Count The number of aborted processes
Finished Count The number of finished processes
Paused Count The number of paused processes
Running Count The number of running processes

Warning Count The number of processes with a warning status
More
KNOWLEDGE BASE

2251
7.8.244 SSH Disk Free Sensor
The SSH Disk Free sensor monitors the free space on disks of a Linux/Unix system using Secure Shell
(SSH).
The free space that this sensor returns shows the available disk space of the volume, minus a
reserve defined for this volume (for example, for redundancy purposes). So, this sensor shows the
disk space that is actually available for use. You can define the size of the reserved disk space with
tune2fs. For more information, see the Knowledge Base: Why do SSH Disk Free and SNMP Linux Disk
Free show different values for my target Linux system?
SSH Disk Free Sensor
List 2260 .

§ Dutch: SSH Disk vrij
§ French: Espace disponible disque (SSH)
§ German: SSH Laufwerkskapazität
§ Japanese: SSH
§ Portuguese: Disco livre (SSH)
§ Russian: SSH
§ Simplified Chinese: SSH
§ Spanish: Espacio libre en disco (SSH)
2252
Remarks
Remark Description

Add Sensor dialog § You can select up to 100 disks in the Add Sensor dialog. If you select
more disks, you cannot create the sensor. Add the sensor multiple
times to monitor more than 100 disks with several sensors.
support?
you add the sensor:
§ diskfreesensor
§ sshdiskfreesensor
2253
SSH Specific
SSH Specific
Setting Description
2254
Setting Description
SSH sensor:
recommended option.
Sensor [ID] (SSHv2).txt. This setting is for debugging purposes. PRTG
master node.

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 shows the Warning or the Down status, depending on the data provided by all
drives that this sensor monitors. If you want to individually define limits for separate channels, use the
limit settings in the channel settings.
2255
All limits that you define here are valid in addition to the limits defined in the particular Channel
settings. The limits are valid simultaneously, so the first limit that is breached applies.
Setting Description
2256
Setting Description
Specify a lower limit in percent for the Down status. If the free disk space
§ Use the limits of both the sensor and the channel settings: Define limits
for the sensor that are valid for all byte size channels. Additional fields
appear below. The sensor shows the Warning or Down status when free
space limits are above or below the value.
2257
Setting Description
2258
Setting Description

found.
Sensor Display
Sensor Display
Setting Description


other above.
2259
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Free Bytes [Mounted The free space

Partition]
Free Space [Mounted The free space (%)

Partition]
More
KNOWLEDGE BASE
Why do SSH Disk Free and SNMP Linux Disk Free show different values for my target Linux system?

2260

How do I set up SSH sensors with my AWS Linux instances?

2261
7.8.245 SSH INodes Free Sensor
The SSH INodes Free sensor monitors the free index nodes on disks of Linux/Unix and macOS systems
via Secure Shell (SSH).
SSH INodes Free Sensor
List 2266 .

§ Dutch: SSH INodes Vrij
§ French: INodes disponibles (SSH)
§ German: SSH Freie INodes
§ Japanese: SSH inode
§ Portuguese: INodes livre (SSH)
§ Russian: INodes SSH

§ Simplified Chinese: SSH INode
§ Spanish: INodes libres (SSH)
2262
Remarks
Remark Description

ESX(i) hosts § This sensor does not support ESX(i) hosts.
support?
you add the sensor:
§ sshinodesfreesensor
2263
SSH Specific
SSH Specific
Setting Description
2264
Setting Description
SSH sensor:
recommended option.
master node.
2265
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2266
Channel Description
Free INodes [Mount] The free index nodes for the mount (%)
UNIX file systems only allow a limited number of index nodes. If the
limit is exceeded, no more data can be stored, although free space
might still be available. This sensor informs you before one of your drives
runs out of INodes.
More
KNOWLEDGE BASE




2267
7.8.246 SSH Load Average Sensor
The SSH Load Average sensor monitors the load average of a Linux/Unix system using Secure Shell
(SSH).
SSH Load Average Sensor
List 2272 .

§ Dutch: SSH Gemiddelde belasting
§ French: Charge moyenne (SSH)
§ German: SSH Durchschnittliche Last
§ Japanese: SSH
§ Portuguese: Carga média (SSH)
§ Russian: SSH
§ Spanish: Promedio de carga (SSH)
Remarks
2268
Remark Description

support?
you add the sensor:
§ sshloadavgsensor
2269
SSH Specific
SSH Specific
Setting Description
2270
Setting Description
SSH sensor:
recommended option.
master node.
2271
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2272
Channel Description
1 Minute The average system load within a 1-minute interval

5 Minutes The average system load within a 5-minute scanning interval
15 Minutes The average system load within a 15-minute interval
More
KNOWLEDGE BASE



2273
7.8.247 SSH Meminfo Sensor
The SSH Meminfo sensor monitors the memory usage of a Linux/Unix system using Secure Shell
(SSH).
SSH Meminfo Sensor
List 2278 .

§ Dutch: SSH Meminfo
§ French: Information mémoire (SSH)
§ German: SSH Speicherinfo
§ Japanese: SSH
§ Portuguese: Meminfo (SSH)
§ Russian: Meminfo SSH

§ Spanish: Meminfo (SSH)
Remarks
2274
Remark Description

Distributions § This sensor does not support all Linux/Unix distributions.
§ This sensor does not support any macOS distributions.
support?
you add the sensor:
§ memorysensor
§ sshmeminfosensor
2275
SSH Specific
SSH Specific
Setting Description
2276
Setting Description
SSH sensor:
recommended option.
master node.
2277
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2278
Channel Description

Memory
More
KNOWLEDGE BASE




2279
7.8.248 SSH Remote Ping Sensor
The SSH Remote Ping sensor remotely monitors the connectivity between a system running
Linux/macOS X and another device, using Internet Control Message Protocol (ICMP) echo requests
("ping") and Secure Shell (SSH).
SSH Remote Ping Sensor
List 2285 .

§ Dutch: SSH Remote Ping
§ French: Ping distant (SSH)
§ German: SSH Remote Ping
§ Japanese: SSH Ping

§ Portuguese: Ping remoto (SSH)
§ Russian: SSH
§ Simplified Chinese: SSH Ping
§ Spanish: Ping remoto (SSH)
Remarks
2280
Remark Description

support?
you add the sensor:
§ pingsensor
§ remotepingsensor
§ sshremotepingsensor
2281
SSH Remote Ping Configuration
SSH Remote Ping Configuration
Setting Description
Target Enter the Domain Name System (DNS) name or IP address of the target
device the ping is sent to. The sensor remotely connects to the parent
device it is created on via SSH, then performs a ping request from this
remote device to the target device or server. Enter a string.
Packet Count Enter the number of packets that the sensor sends with each scanning
interval.
Custom Parameter Optionally, enter additional parameters that the sensor adds at the end of
the ping command. Enter a string or leave the field empty.
Do not use parameters that change the output format of the result to
make sure that it can still be parsed. You cannot enter an additional
command.
2282
SSH Specific
SSH Specific
Setting Description
2283
Setting Description
SSH sensor:
recommended option.
master node.
2284
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2285
Channel Description
Avg. Response The average response time measured from the remote device
Max Response The maximum response time measured from the remote device
Min Response The minimum response time measured from the remote device
Packet Loss The packet loss (%)

More
KNOWLEDGE BASE




2286
7.8.249 SSH SAN Enclosure Sensor
The SSH SAN Enclosure sensor monitors a storage area network (SAN) enclosure via Secure Shell
(SSH).
The SAN must provide a command-line interface (CLI) for this purpose.
SSH SAN Enclosure Sensor
List 2292 .

§ Dutch: SSH SAN behuizing
§ French: SAN boîtier (SSH)
§ German: SSH SAN Enclosure
§ Japanese: SSH SAN
§ Portuguese: Gabinete SAN (SSH)
§ Russian: SAN SSH

§ Simplified Chinese: SSH SAN
§ Spanish: Gabinete SAN (SSH)
Remarks
2287
Remark Description

SAN support § This sensor does not support every SAN, even if it provides a CLI. This
sensor only works with specific devices, for example, the HPE P2000.
Scanning interval § If the controller of the target system breaks down, increase the
scanning interval to discharge the controller and try again.
Firmware update § After a firmware update of the target system, this sensor might show
incorrect channel values. Add this sensor anew in this case.
channels.
Device status § Sometimes the devices you monitor with this sensor return status
values that are not officially documented so that the shown sensor
status in PRTG differs from the "real" device status. For more
information, see the Knowledge Base: Why does my SSH SAN sensor
show a wrong status?
support?
you add the sensor:
2288
§ enclosure
§ sshsan
§ sshsanenclosure
SSH SAN Enclosure Settings
SSH SAN Enclosure Settings
Setting Description
Storage Enclosure The identifier of the storage enclosure that this sensor monitors.
Durable ID The durable identifier of the storage enclosure that this sensor monitors.
Name The name of the storage enclosure that this sensor monitors.
WWN The World Wide Name (WWN) of the storage enclosure that this sensor
monitors.
2289
SSH Specific
SSH Specific
Setting Description
as possible. Enter an integer.
This sensor has a fixed timeout of 300 seconds. If you change the
value, it does not have an effect on the timeout.
2290
Setting Description
SSH sensor:
recommended option.
master node.
2291
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2292
Channel Description
Controller[#] The controller status

§ Up status: Ok
§ Down status: Fault, Not Available
Enclosure[#] The overall enclosure status

§ Up status: Ok
PSU[#] The power supplies status

§ Up status: Ok
More
KNOWLEDGE BASE
Why does my SSH SAN sensor show a wrong status?


2293
7.8.250 SSH SAN Logical Disk Sensor
The SSH SAN Logical Disk sensor monitors a logical disk on a storage area network (SAN) via Secure
Shell (SSH).
SSH SAN Logical Disk Sensor
List 2299 .

§ Dutch: SSH SAN Logische Schijf
§ French: SAN disque logique (SSH)
§ German: SSH SAN Logisches Laufwerk
§ Portuguese: Disco lógico SAN (SSH)
§ Russian: SAN SSH

§ Spanish: Disco lógico SAN (SSH)
Remarks
2294
Remark Description

channels.
support?
you add the sensor:
§ logicaldisk
2295
§ sshsan
§ sshsanlogicaldisk
SSH Specific
SSH Specific
Setting Description
2296
Setting Description
SSH sensor:
recommended option.

2297
Setting Description
master node.
SSH SAN Logical Disk Settings
SSH SAN Logical Disk Settings
Setting Description
Volume The volume that this sensor monitors.
Size The size of the volume that this sensor monitors.
Command Mode Define the command set that the sensor uses on the device to get
monitoring data:
§ Basic (default): Use the basic command set. We recommend that you
use the basic command set for best sensor performance. This setting
is appropriate for most scenarios.
§ Advanced: Monitor additional data on the target device like IOs and
bandwidth.
Because this setting results in higher usage of system resources
and so might cause sensor instabilities, we strongly recommend
that you ony select this option if this data is crucial for the volume that
you monitor.
Sensor Display
Sensor Display
2298
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
2299
Channel Description
Health The disk heath status

§ Up status: Ok
Transferred The data transferred
More
KNOWLEDGE BASE



2300
7.8.251 SSH SAN Physical Disk Sensor
The SSH SAN Physical Disk sensor monitors a physical disk on a storage area network (SAN) via
Secure Shell (SSH).
SSH SAN Physical Disk Sensor
List 2307 .

§ Dutch: SSH SAN Fysieke Schijf
§ French: SAN disque physique (SSH)
§ German: SSH SAN Physikalisches Laufwerk
§ Portuguese: Disco físico SAN (SSH)
§ Russian: SAN SSH

§ Spanish: Disco físico SAN (SSH)
Remarks
2301
Remark Description

channels.
support?
you add the sensor:
§ physicaldisk
2302
§ sshsan
§ sshsanphysicaldisk
SSH Specific
SSH Specific
Setting Description
2303
Setting Description
SSH sensor:
recommended option.

2304
Setting Description
master node.
SSH SAN Physical Disk Settings
SSH SAN Physical Disk Settings
Setting Description
Name The name of the physical disk that this sensor monitors.
Size The size of the physical disk that this sensor monitors.
Command Mode Define the command set that the sensor uses on the device to get
monitoring data:
§ Basic (default): Use the basic command set. We recommend that you
use the basic command set for best sensor performance. This setting
is appropriate for most scenarios.
§ Advanced: Monitor additional data on the target device like IOs and
bandwidth.
Because this setting results in higher usage of system resources
and so might cause sensor instabilities, we strongly recommend
that you ony select this option if this data is crucial for the volume that
you monitor.
Request Mode Define the which type of data the sensor requests:
2305
Setting Description
§ Request all historical data (default): Use this mode to possibly deliver
better data.
§ Request actual counters: Use this mode if the device does not support
Request all historical data (default). This mode might result in incorrect
data and spikes in graphs.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
2306
Inherited Settings
Channel List
Channel Description
Health The disk heath status

§ Up status: Ok
Transferred The data transferred
More
KNOWLEDGE BASE



2307
7.8.252 SSH SAN System Health Sensor
The SSH SAN System Health sensor monitors the system health of a storage area network (SAN) via
Secure Shell (SSH).
SSH SAN System Health Sensor
List 2313 .

§ Dutch: SSH SAN Systeemstatus
§ French: SAN état du système (SSH)
§ German: SSH SAN Systemzustand
§ Portuguese: Saúde do sistema SAN (SSH)
§ Russian: SAN SSH

§ Spanish: Salud de sistema SAN (SSH)
Remarks
2308
Remark Description

channels.
support?
you add the sensor:
§ sshsan
2309
§ sshsansystemhealth
§ systemhealth
SSH SAN Specific
SSH SAN Specific
Setting Description
Metric The metric that this sensor monitors.
Monitoring Mode Define how the sensor requests data from the target device:
§ Automatic detection: Automatically detect the firmware version and use
the appropriate mode. We recommend that you use this option and
only explicitly define the firmware date if errors occur.
§ Firmware before June 2015: Use the mode that is appropriate for
firmware versions before June 2015.
§ Firmware as of June 2015: Use the mode that is appropriate for
firmware versions as of June 2015.
The required mode depends on the firmware version of the target
device. The sensor automatically detects the firmware version and
uses the appropriate mode in most cases. If errors occur, explicitly define
the firmware version.
2310
SSH Specific
SSH Specific
Setting Description
2311
Setting Description
SSH sensor:
recommended option.
master node.
2312
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2313
Channel Description
Capacitor Cell [#] The capacitor cell voltage

Voltage [Controller]
Capacitor Cell [#] The capacitor cell voltage status

Voltage [Controller]
§ Up status: Ok
Status
§ Down status: Error, Unavailable, Unknown, Unrecoverable
§ Unknown status: Not Installed, Unsupported
Capacitor Pack Voltage The capacitor pack voltage

[Controller]
Capacitor Pack Voltage The capacitor pack voltage status

[Controller] Status
§ Up status: Ok
Disk Controller Temp The disk controller temperature

[Controller]
Disk Controller Temp The disk controller temperature status

[Controller] Status
§ Up status: Ok
Overall Unit Status The overall unit status

§ Up status: Ok
2314
Channel Description
Memory Controller Temp The memory controller temperature

[Controller]
Memory Controller Temp The memory controller temperature status

[Controller] Status
§ Up status: Ok
On-Board Temperature The on-board temperature

[Controller]
On-Board Temperature The on-board temperature status

[Controller] Status
§ Up status: Ok
More
KNOWLEDGE BASE



2315
7.8.253 SSH Script Sensor
The SSH Script sensor connects to a Linux/Unix system via Secure Shell (SSH) and executes a script
file that is located on the target system. This option is available as part of the PRTG API.
SSH Script Sensor
List 2324 .

§ Dutch: SSH Script
§ French: Script (SSH)
§ German: SSH-Skript
§ Japanese: SSH
§ Portuguese: Script (SSH)
§ Russian: SSH
§ Spanish: Script (SSH)
Remarks
2316
Remark Description
File storage § For security reasons, this sensor requires that you store your script file
in the /var/prtg/scripts directory on the target system. Make sure that
the script has executable rights. If the script is not available or was
deleted from the directory, you get the error message Script not found
(237).

Return format § For more information about the return value format, see the PRTG
Manual: Custom Sensors.
support?
Add Sensor
Setting Description
Channel Name Enter a name for the channel. Enter a string. This is for display purposes
only.
sensor.
2317
you add the sensor:
§ sshscript

Setting Description
2318
Setting Description
Sensor Settings
Sensor Settings
2319
Setting Description
Script Select a script file from the dropdown list. It shows all script files that are
available in the /var/prtg/scripts directory on the target Linux/Unix system.
For a script file to appear in this list, store the target file in this directory.
Make sure that the script has executable rights.
To show the expected sensor value and status, your file must use
the correct format for the returned values. In this case, it is
exitcode:value:message to standard output stdout. The exit code
determines the sensor status.
For more information and an example script, see the Knowledge
Base: Is there a shell script example for the SSH Script sensor?
Character Encoding Define the character encoding that you use in your script to correctly
display the sensor message:
§ UTF-8 (default)
§ ASCII
Parameters If your script file catches command-line parameters, define them here.
You can also use placeholders. Enter a string or leave the field empty.
details.
In SSH scripts, you can use alphanumeric characters and the
special characters ".", "_", "-", "=", and "/" outside of quoted strings.
PRTG runs all custom script sensors that have the same mutex
name serially (not simultaneously). This is useful if you use a lot of
sensors and want to avoid high resource usage caused by processes that
run running at the same time.
Unit String Define a unit for the channel value. Enter a string. This is for display
purposes only and is the default unit for a new channel. You can change
the unit after sensor creation in the sensor's channel settings.
2320
Setting Description
Value Type Define the type of the values that your executable or script file returns:
§ Integer: An integer is expected as return value. If the script returns a
float, PRTG displays the value 0.
§ Float: A float is expected as return value, with a dot (.) between the
predecimal position and the decimal places.
The sensor also displays integers unless they produce a buffer
overflow.
§ Counter: Your script returns an integer that increases. PRTG shows the
difference between the values of two sensor scans.
A counter must return an integer. It does not support float values.
The sensor does not support string values.

change.
SSH Specific
SSH Specific
2321
Setting Description
SSH sensor:
recommended option.
2322
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


2323
Setting Description
other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description

[Value] The value that the script file returns in one channel
Custom Sensors.
More
KNOWLEDGE BASE

2324
Is there a shell script example for the SSH Script sensor?



2325
7.8.254 SSH Script Advanced Sensor
The SSH Script Advanced sensor connects to a Linux/Unix system via Secure Shell (SSH) and
executes a script file that is located on the target system. This option is available as part of the PRTG
API.
SSH Script Advanced Sensor
List 2333 .

§ Dutch: SSH Script Geavanceerd
§ French: Script avancé (SSH)
§ German: SSH-Skript (Erweitert)
§ Japanese: SSH ( )
§ Portuguese: Script (avançado) (SSH)
§ Russian: SSH
§ Spanish: Script (avanzado) (SSH)
Remarks
2326
Remark Description
File storage § For security reasons, this sensor requires that you store the script file
in the /var/prtg/scriptsxml directory on the target system. Make sure
that the script has executable rights.

Return format § For more information about the return value format, see the PRTG
Manual: Custom Sensors.
support?
you add the sensor:
§ sshscript
2327
Setting Description
2328
Setting Description
Sensor Settings
Sensor Settings
Setting Description
Script Select a script file from the dropdown list. It shows all script files that are
available in the /var/prtg/scriptsxml directory on the target Linux/Unix
system. For a script file to appear in this list, store the target file in this
directory.
Make sure that the script has executable rights.
To show the expected sensor value and status, your files must return
the expected XML or JSON format to standard output stdout. The
values and message must be embedded in the XML or JSON.
Parameters If your script file catches command-line parameters, define them here.
You can also use placeholders. Enter a string or leave the field empty.
details.
In SSH scripts, you can use alphanumeric characters and the
special characters ".", "_", "-", "=", and "/" outside of quoted strings.
2329
Setting Description
PRTG runs all custom script sensors that have the same mutex
name serially (not simultaneously). This is useful if you use a lot of
sensors and want to avoid high resource usage caused by processes that
run running at the same time.
SSH Specific
SSH Specific
Setting Description
2330
Setting Description
SSH sensor:
recommended option.
2331
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
2332
Channel List
Channel Description
[Value] The values that the script file returns in several channels
Custom Sensors.
More
KNOWLEDGE BASE




2333
7.8.255 SSL Certificate Sensor
The SSL Certificate sensor monitors the certificate of a Secure Sockets Layer (SSL)/Transport Layer
The sensor also shows the certificate common name and the certificate thumbprint in the sensor
message.
SSL Certificate Sensor
List 2340 .

§ Dutch: SSL Certificaat
§ French: SSL certificat
§ German: SSL-Zertifikat
§ Japanese: SSL
§ Portuguese: Certificado SSL
§ Russian: SSL
§ Simplified Chinese: SSL
§ Spanish: Certificado SSL
2334
Remarks
Remark Description
DNS name § Enter the Domain Name System (DNS) name in the settings of the
parent device exactly as it is written in your certificate. You can also
use wildcards 2339 .
Revocation status § To check the revocation status of a certificate, the sensor uses
WinHTTP to auto-detect the proxy server to use. You can also
manually define a server. If you do not define a proxy server, PRTG
uses the default WinHTTP proxy settings. For more information, see
the Knowledge Base: How can I configure the WinHTTP proxy settings
for the SSL Certificate sensor?
channels.
you add the sensor:
§ certificate
§ ssl
§ sslcertificate
2335
SSL Certificate Specific
SSL Certificate Specific
Setting Description
Virtual Host (SNI Define the host name that the sensor tries to query if your server has
Domain) multiple certificates on the same IP address and port combination. Enter
a string.
In the case of virtual hosting, you must identify the specific certificate
for a specific domain while all domains use the same IP address, you
can use SNI, which is an extension of TLS.
If you select a Certificate Name Validation option below, the sensor
compares the common name and optionally alternative names with
the SNI. Leave this field empty to validate the common name with the
host address of the parent device.
Certificate Name Define if you want the sensor to validate the certificate name:
Validation
§ Do not compare common name (CN) with device address or SNI
(default): Do not check if the certificate name is valid by comparing it
with the address of the parent device or the defined SNI.
§ Compare and show down status if common name (CN) and
address/SNI do not match: Check the common name to validate the
certificate name. If you define an SNI above, the sensor compares the
common name with the SNI. If you do not define an SNI, the sensor
uses the host address of the parent device. If the common name and
the checked address/SNI do not match, the sensor shows the Down
status.
§ Compare and show down status if common name (CN)/alternative
names (SAN) and address/SNI do not match: Check the common
name and the Subject Alternative Names (SAN) to validate the
certificate. If you define an SNI domain above, the sensor compares the
common name and alternative names with the SNI. If you do not define
an SNI, the sensor uses the host address of the parent device. If the
common name or alternative names and the checked address/SNI do
not match, the sensor shows the Down status.
2336
Connection Specific
Connection Specific
Setting Description
Use SOCKS Proxy (v5 Define if the sensor uses a SOCKS proxy server for the sensor
only) connection:
§ Do not use SOCKS proxy(default): Directly connect to the target host
without using a SOCKS proxy.
§ Use SOCKS proxy: Connect using SOCKS5. Provide data for the
SOCKS connection below.
Other SOCKS versions are not supported.
This sensor only supports SOCKS5 proxies. It does not support
HTTP proxies.
Server This setting is only visible if you select Use SOCKS proxy above.
Enter the IP address or host name of the proxy server that the sensor
uses for connection.
Port This setting is only visible if you select Use SOCKS proxy above.
Enter the port number of the proxy server that the sensor uses for
connection.
User Name This setting is only visible if you select Use SOCKS proxy above.
If the proxy server requires authentication, enter a user name.
Password This setting is only visible if you select Use SOCKS proxy above.
If the proxy server requires authentication, enter the password for the user
you specified above.
2337
Debug Options
Debug Options
Setting Description
§ Store result: Store the last sensor result to the \Logs\sensors subfolder
Result of Sensor [ID].Data.txt, Result of Sensor [ID] (Certificate 0 in
Certificate Chain).cer, Result of Sensor [ID] (Certificate 1 in Certificate
Chain).cer, Result of Sensor [ID] (Certificate 2 in Certificate Chain).cer,
Result of Sensor [ID] (Certificate Chain).txt, and Result of Sensor [ID]
(Certificate).cer. This setting is for debugging purposes. PRTG
master node.
You can use the debug option to get a log file with information about the certificate chain.
Additionally, certificates in the certificate chain are stored in the log folder (.cer files). This can help
you, for example, if you have issues with the Root Authority Trusted channel of this sensor.
Sensor Display
Sensor Display
Setting Description
2338
Setting Description


other above.
procedure to do so.
Inherited Settings
Using Wildcards
You can use wildcards in the IP Address/DNS Name in the device settings. Wildcards that apply to only
one level of the domain name are supported.
Example Result
*.wildcard.com for www.wildcard.com Works
api.wildcard.com for api.wildcard.com Works
2339
Example Result
contoso.com for contoso.com Works
*.subapi.subapi2.wildcard.com for Works

de.subapi.subapi2.wildcard.com
*. *.wildcard.com for www.de.wildcard.com Not supported
*.wildcard.com for de.subapi.wildcard.com Doesn't work
www.contoso.com for contoso.com Doesn't work
subapi.*.wildcard.com for Doesn't work

subapi.dns.wildcard.com
Channel List
Channel Description
Common Name Check If the common name or subject-alternative names match the host address
or SNI (if you select a Certificate Name Validation option)
§ Up status: CN/SAN Match, Disabled, Matches Device Address,
Matches SNI
§ Down status: CN/SAN Do Not Match SNI, Does Not Match Device
Address, Does Not Match SNI
Days to Expiration The days to expiration with a predefined lower warning limit (28 days) and
lower error limit (7 days)
2340
Channel Description
Public Key Length The public key length
§ Up status:
ú RSA keys: For 2048-bit keys (good security) and longer (perfect
security)
ú ECC keys: For 128-bit and 192-bit keys (good security) and longer
(perfect security)
§ Warning status: For weak security
§ Down status: For shorter keys (unsecure)
Revoked If the certificate has been revoked

§ Up status: No
§ Warning status: Unable To Check Revocation Status
§ Down status: Yes
Root Authority Trusted If the certificate is trusted as root authority

§ Up status: Yes
§ Warning status: No
Self-Signed If a self-signed certificate is used

§ Up status: Yes, No
More
KNOWLEDGE BASE
How can I configure the WinHTTP proxy settings for the SSL Certificate sensor?

2341
7.8.256 SSL Security Check Sensor
The SSL Security Check sensor monitors Secure Sockets Layer (SSL)/Transport Layer Security (TLS)
connectivity to the port of a device. It tries to connect to the specified TCP/IP port number of a device
with different SSL/TLS versions and shows if the device supports a particular protocol.
SSL Security Check Sensor
List 2346 .

§ Dutch: SSL Security Check
§ French: SSL vérification de sécurité
§ German: SSL-Sicherheitsüberprüfung
§ Japanese: SSL
§ Portuguese: Verificação de segurança SSL
§ Russian: SSL
§ Simplified Chinese: SSL
§ Spanish: Comprobación de seguridad SSL
2342
Remarks
Remark Description
Protocols § This sensor only checks accepted protocols. It does not consider the
used ciphers.
channels.
Knowledge Base § Knowledge Base: How do you determine the protocol security ratings of
the SSL Security Check sensor?
you add the sensor:
§ sslsensor
2343
SSL Security Specific
SSL Security Specific
Setting Description
Virtual Host (SNI Enter the host name that the sensor queries. The sensor uses this host
Domain) for the connection if the target server has multiple certificates on the same
IP address and IP port when using Server Name Indication (SNI).
Connection Specific
Connection Specific
Setting Description
Use SOCKS Proxy (v5 Define if the sensor uses a SOCKS proxy server for the sensor
only) connection:
§ Do not use SOCKS proxy(default): Directly connect to the target host
without using a SOCKS proxy.
§ Use SOCKS proxy: Connect using SOCKS5. Provide data for the
SOCKS connection below.
Other SOCKS versions are not supported.
2344
Setting Description
This sensor only supports SOCKS5 proxies. It does not support

HTTP proxies.
Server This setting is only visible if you select Use SOCKS proxy above.
Enter the IP address or host name of the proxy server that the sensor
uses for connection.
Port This setting is only visible if you select Use SOCKS proxy above.
Enter the port number of the proxy server that the sensor uses for
connection.
User Name This setting is only visible if you select Use SOCKS proxy above.
If the proxy server requires authentication, enter a user name.
Password This setting is only visible if you select Use SOCKS proxy above.
If the proxy server requires authentication, enter the password for the user
you specified above.
Sensor Display
Sensor Display
Setting Description

2345
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Security Rating The security of the connection to the defined port

§ Up status: Only Strong Protocols Available
§ Warning status: Weak Protocols Available
§ Down status: No Secure Protocol Available
SSL 2.0 (Deprecated) No longer available
2346
Channel Description
SSL 3.0 (Weak) The status of connections using SSL v3

§ Up status: Denied
§ Warning status: Accepted
TLS 1.0 (Weak) The status of connections using TLS 1.0

§ Up status: Denied
§ Warning status: Accepted
TLS 1.1 (Weak) The status of connections using TLS 1.1

§ Up status: Accepted
§ Unknown status: Denied
TLS 1.2 (Strong) The status of connections using TLS 1.2

TLS 1.3 (Perfect) The status of connections using TLS 1.3

More
KNOWLEDGE BASE

How do you determine the protocol security ratings of the SSL Security Check sensor?
2347
7.8.257 Syslog Receiver Sensor
The Syslog Receiver sensor receives and analyzes Syslog messages.
Syslog Receiver Sensor
List 2355 .

§ Dutch: Syslog ontvanger
§ French: Récepteur Syslog
§ German: Syslog-Empfänger
§ Japanese: Syslog
§ Portuguese: Receptor de Syslog
§ Russian: Syslog
§ Simplified Chinese: Syslog
§ Spanish: Receptor de Syslog
Remarks
Remark Description
2348
Remark Description
UDP § This sensor only supports the User Datagram Protocol (UDP).
Probe device § Add this sensor to the probe device to receive all messages of the
§ If you add the sensor to a device other than a probe device, the IP
address or Domain Name System (DNS) name of the parent device
must match the proper sender. For example, if you want to receive
messages from a storage area network (SAN), you might need to add a
device with the IP address of a specific array member that sends the
messages. Providing a DNS name that points to the IP address of a
whole group might not work for SANs.
Filter options § You can use the filter options to define which types of messages the
sensor considers for monitoring, and which messages it categorizes as
warnings or errors.
Specific device § Add this sensor to a specific device to directly receive all messages
from this device. This is faster than using source filters.
Placeholders § You can use placeholders in email notification templates to see

messages when you receive email notifications.
Sensor states § The sensor states of this sensor persist for one scanning interval only.
After showing the Warning or the Down status, and if there is no
warning or error message in the next scanning interval, the sensor
shows the Up status again. For more information on a workaround, see
the Knowledge Base: How can I configure sensors using speed limits
to keep the status for more than one interval?
probe device.
2349
you add the sensor:
§ syslogsensor
Syslog Specific
Syslog Specific
Setting Description
Port Enter the number of the port on which the sensor listens for Syslog
messages. The default port is 514. Enter an integer.
Purge Messages After Define how long PRTG stores received Syslog messages for analysis.
Select a period of time from the dropdown list.
Filter
2350
Filter
Setting Description
Include Filter Define if you want to filter Syslog messages. If you leave this field empty
or use the keyword any, the sensor processes all data. To only include
specific types of messages, define filters using a special syntax.
Exclude Filter Define which types of Syslog messages the sensor discards and does
not process. To exclude specific types of messages, define filters using a
special syntax.
Warning Filter Define which types of Syslog messages count for the Warnings channel.
To categorize received messages as warning messages, define filters
2351
Setting Description

as the scanning interval is running, the sensor does not change its
status. By default, the sensor changes to the Warning status after a
scanning interval finishes and there was at least one warning message
(and no error message) during this scanning interval. The sensor shows
the Warning at least until the succeeding scanning interval finishes. If the
sensor does not receive any warning or error message in this scanning
interval, its status changes to the Up status again with the start of the
next scanning interval.
Error Filter Define which types of Syslog messages count for the Errors channel. To
categorize received messages as error messages, define filters using a
special syntax.
as the scanning interval is running, the sensor does not change its
status. By default, the sensor changes to the Down status after a
scanning interval finishes and there was at least one error message
during this scanning interval. The sensor shows the Down status at least
until the succeeding scanning interval finishes. If the sensor does not
receive any warning or error message in this scanning interval, its status
changes to the Up status again with the start of the next scanning
interval.
Sensor Display
Sensor Display
Setting Description

2352
Setting Description

other above.
procedure to do so.
Inherited Settings
Debug Options
Debug Options
Setting Description
§ Store result: Store the last sensor result in the \Logs\debug subfolder of
the PRTG data directory on the probe system. The file name is Sensor
[ID]_[Date].log. This setting is for debugging purposes.
Use with caution. We recommend that you only use this setting for
a short time because it can create huge data files.
2353
Filter Rules
Filter rules are used for the include, exclude, warning, and error definition fields of the Syslog Receiver
sensor. They are based on the following format:
field[filter]
You can use various filters suitable to your needs. Include and exclude filters define which messages to
monitor. Warning and error filters define how to categorize received messages. Provide these filters in the
sensor settings as formulas. Formulas are fields that you can combine with boolean operators (AND,
OR, NOT) and brackets.
Field Parameter Example
source[ip] Enter an IP address where the messages come from. § source[10.0.23.50]

IP masks and ranges are also possible.
§ source[10.0.23.10-50]
§ source[10.0.23.10/24]
facility[number] Enter any number or range from 0 to 23 specifying the § facility[2]

program type that sends the message.
§ facility[5-7]
§ facility[5] OR facility[6]
severity[number] Enter any number or range from 0 (emergency) to 7 § severity[4]

(debug) specifying the message type.
§ severity[1-3]
§ severity[1] AND severity[2]
hostname[text] Enter any string that specifies the hostname of a § hostname[www.example.c

device in the message. om]
tag[text] Enter any string that specifies the tag of a program or § tag[su]
process in the message.
appname[text] Enter any string that specifies the appname part of the § appname[myproc]
message.
§ appname[demo] AND
msgid[m42]
procid[text] Enter any string that specifies the process identifier § procid[1860]
part of the message.
msgid[text] Enter any string that specifies the message identifier § msgid[ID47]
part of the message.
message[parttext] Enter any string that specifies the message part of the § message[Error]
message. (Any substring matches. This value is not
case-sensitive.)
2354
Field Parameter Example
data This checks the SD-ID block of the message's § data[exampleSDID@12345

[id,param,value] structured data for a parameter matching the specified ,eventSource,Application]
value.
data[parttext] This checks if the specified substring matches § data[exampleSDID@1234]

structured data as displayed in the corresponding
table.
data[id,param] This checks if the parameter exists in the specified ID § data[exampleSDID@1234,

element. eventSource]
String parameters (except the substring in message) must exactly match the particular parts of the
message. They are case-sensitive.
Messages Tab: Review and Analyze Syslog Messages

PRTG stores received Syslog messages as common files in the \Syslog Database subfolder of the
PRTG data directory. To review and analyze all received messages, you can directly access the most
recent data in a table list on the PRTG web interface. You can access this list via the sensor's Overview
tab.
Received Syslog messages are only shown in the table on the Overview tab after an (automatic)
page refresh following a sensor scan. The default value for auto refresh is 30 seconds.
For more details and further filter options, click the Messages tab of the Syslog Receiver sensor. You
see all received messages in a table list. On the top, you have display filter options to drill down into the
data for specific events of your interest. The filters are the same as those available in the sensor
settings, but you can define them without using formulas. Provide the desired parameters and PRTG
automatically loads the filtered list.
You can automatically add a filter by clicking the content of a column.
Advanced Filter Settings
You can open advanced filter settings by clicking in the Filter row. The Advanced Filter appears in a
popup window. In the text field, you can define a filter using the syntax as specified in section Filter
Rules 2354.
If you provided filter parameters on the Messages tab, the advanced filter already includes them as a
corresponding formula with the correct syntax. You can adjust this filter to your needs. You can also
copy the automatically created and manually adjusted formula for usage in the filter fields of the sensor
settings.
Channel List
2355
Channel Description
Drops The number of dropped packets on the syslog port

Errors The number of messages categorized as "error"

Messages The number of received Syslog messages

Warnings The number of messages categorized as "warning"

More
KNOWLEDGE BASE

VIDEO TUTORIAL
SNMP Trap receiver and syslog receiver sensors

§ https://www.paessler.com/support/videos-and-webinars/videos/syslog-receiver
2356
7.8.258 System Health Sensor
The System Health sensor monitors the status of the probe system. It checks various system
parameters that can affect the quality of the monitoring results.
PRTG automatically creates this sensor. You cannot delete the sensor if it was created
automatically. If you manually create the sensor, you can delete it.
System Health Sensor
List 2359 .

§ Dutch: Systeemstatus
§ French: État du système
§ German: Systemzustand
§ Japanese:
§ Portuguese: Saúde do sistema
§ Russian:
§ Spanish: Salud de sistema
2357
Remarks
Remark Description
you add the sensor:
§ systemhealthsensor
Sensor Display
Sensor Display
Setting Description
2358
Setting Description



other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Available Memory The amount of free memory available on the system. This value should
not fall below 500 MB. This way, PRTG can still request resources during
report generation or auto-discoveries, for example.
System CPU Load The CPU load (%). Extensive CPU load can lead to false, incomplete, and
2359
Channel Description

Health The sum of the system status as a value between 100% (healthy) and 0%
(failing). Investigate frequent or repeated health values below 100%.
More
KNOWLEDGE BASE

2360
7.8.259 System Health v2 Sensor
The System Health v2 sensor monitors the health of a Linux system that the PRTG core server runs on.
List 2364 .

§ Dutch: Systeemstatus v2
§ French: État du système v2
§ German: Systemzustand v2
§ Japanese: v2
§ Portuguese: Saúde do sistema v2
§ Russian: v2
§ Simplified Chinese: v2
§ Spanish: Salud del sistema v2
Remarks
2361
Remark Description
Sensor creation § PRTG automatically creates this sensor. You cannot delete it. If you
manually create the sensor, you can delete it.
Windows OS § This sensor does not support Windows operating systems.
you add the sensor:
§ systemhealthsensor
2362
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
2363
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Available Memory The amount of free memory available on the system. This value should
not fall below 500 MB. This way, PRTG can still request resources during
report generation or auto-discoveries, for example.

2364
Channel Description
System CPU Load The CPU load (%).

Extensive CPU load can lead to false, incomplete, and incorrect
monitoring results. This value should usually stay below 50%.
More
KNOWLEDGE BASE


2365
7.8.260 TFTP Sensor
The TFTP sensor monitors a Trivial File Transfer Protocol (TFTP) server and checks if a certain file is
available for download.
TFTP Sensor
List 2369 .

§ Dutch: TFTP
§ French: TFTP
§ German: TFTP
§ Japanese: TFTP
§ Portuguese: TFTP
§ Russian: TFTP
§ Simplified Chinese: TFTP
§ Spanish: TFTP
Remarks
Remark Description
2366
Remark Description
you add the sensor:
§ trivialftpsensor
Sensor Specific
Sensor Specific
Setting Description
2367
Setting Description
Port Enter the number of the port that the TFTP service runs on. The sensor
connects to this port. Enter an integer.
File Name Enter the name of the file that this sensor checks. If the file is not
available on the server, the sensor shows the Down status. Enter a string.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
2368
Inherited Settings
Channel List
Channel Description
Available The response time

More
KNOWLEDGE BASE
2369
7.8.261 Traceroute Hop Count Sensor
The Traceroute Hop Count sensor traces the number of hops from the probe system to the IP
If the number of hops (the route) changes, you can additionally define a different sensor status.
Traceroute Hop Count Sensor
List 2373 .

§ Dutch: Traceroute Hop Count
§ French: Compteur de hop Traceroute
§ German: Traceroute Hop-Anzahl
§ Japanese: Traceroute
§ Portuguese: Contagem de hops em traceroute
§ Russian:
§ Simplified Chinese: Traceroute
§ Spanish: Recuento de saltos traceroute
Remarks
2370
Remark Description
system.
does PRTG require?
you add the sensor:
§ ptfsensor
Sensor Settings
Sensor Settings
2371
Setting Description
If Route Changes Define what to do if the route has changed since the last check:
§ Set sensor to warning status: Show the Warning status if the route
changes.
§ Set sensor to down status: Show the Down status if the route changes.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
2372
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
2373
Channel Description
Hops The number of hops

More
KNOWLEDGE BASE


2374
7.8.262 Veeam Backup Job Status Sensor
The Veeam Backup Job Status sensor monitors the status of all backup job runs on the Veeam Backup
Enterprise Manager in the last 24 hours.
Veeam Backup Job Status Sensor
List 2378 .

§ Dutch: Veeam Backup Taak Status
§ French: Veeam statut de tâche de sauvegarde
§ German: Veeam Backupjob-Status
§ Japanese: Veeam
§ Portuguese: Status da tarefa de backup do Veeam
§ Russian: Veeam
§ Simplified Chinese: Veeam
§ Spanish: Estado del trabajo de copia de seguridad Veeam
Remarks
2375
Remark Description
Veeam version § This sensor requires that the Veeam Backup Enterprise Manager 10 or
11 with the Enterprise Plus license are installed.
Credentials § This sensor requires credentials for Veeam.
Backup jobs § This sensor does not support the following backup job types: Tape,
Sure Backup, NAS Backup Copy, and Agent Backup Copy.
Veeam agent § This sensor does not support Veeam Agent Backup Jobs if they are
managed by a Veeam Agent.
REST API § This sensor only supports version 1.5 of the Representational State
Transfer (REST) application programming interface (API).
you add the sensor:
§ veeam
§ veeambackup
§ veeamenterprisemanager
2376
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
2377
Setting Description
master node.
Inherited Settings
Channel List
Channel Description
Job Runs Failed The number of failed job runs (sessions)

The Job Runs Failed channel shows the total number of all failed job
runs.
Job Runs Finished The number of finished job runs
2378
Channel Description
The Job Runs Finished channel shows the total number of all finished
job runs with status Success, Warning, and Failed.
Job Runs Running The number of running job runs
Job Runs Successful The number of successful job runs

The Job Runs Successful channel shows the total number of all
finished job runs with status Success.
Job Runs Warning The number of job runs in the warning status
Jobs Scheduled The number of scheduled backup jobs
More
KNOWLEDGE BASE

2379
7.8.263 Veeam Backup Job Status Advanced Sensor
The Veeam Backup Job Status Advanced sensor monitors the status of a specific backup job that runs
on the Veeam Backup Enterprise Manager.
Veeam Backup Job Status Advanced Sensor
List 2384 .

§ Dutch: Veeam Backup Taakstatus Geavanceerd
§ French: Veeam statut de tâche de sauvegarde avancée
§ German: Veeam Backupjob-Status (Erweitert)
§ Japanese: Veeam
§ Portuguese: Status da tarefa de backup do Veeam (Avançado)
§ Russian: Veeam
§ Simplified Chinese: Veeam
§ Spanish: Estado del trabajo de Veeam Backup (avanzado)
Remarks
2380
Remark Description
Veeam version § This sensor requires that the Veeam Backup Enterprise Manager 10 or
11 with the Enterprise Plus license are installed.
Credentials § This sensor requires credentials for Veeam.
Backup jobs § This sensor does not support the following backup job types: Tape,
Sure Backup, NAS Backup Copy, and Agent Backup Copy.
Veeam agent § This sensor does not support Veeam Agent Backup Jobs if they are
managed by a Veeam Agent.
REST API § This sensor only supports version 1.5 of the Representational State
Transfer (REST) application programming interface (API).
channels.
Knowledge Base § Knowledge Base: How can I change the status of my Veeam sensors
based on whether a job is scheduled or not?
you add the sensor:
§ veeam
2381
§ veeambackup
§ veeamenterprisemanager
Veeam Specific
Veeam Specific
Setting Description
Job Name The name of the backup job that this sensor monitors.
Job Type The type of backup job that this sensor monitors.
Platform The platform on which the backup job runs.
Job Description The description of the backup job that this sensor monitors.
Sensor Display
Sensor Display
Setting Description
2382
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
Setting Description
master node.
2383
Inherited Settings
Channel List
Channel Description
Duration The duration of the backup job run
Job Scheduled If the backup job is scheduled

§ Up status: No, Yes. Which status the sensor actually shows depends
on the lookup file that you choose in the channel settings.
the status of my Veeam sensors based on whether a job is
scheduled or not?
§ Down status: No
Last Job Run The time since the last backup job run
Last Result The last backup job run status

§ Up status: Successful
§ Unknown status: None
Status The backup job run status

§ Up status: Starting, Working, Stopped
2384
Channel Description
§ Warning status: Stopping, Pausing, Resuming, Never Started,

Postprocessing
§ Unknown status: Idle
More
KNOWLEDGE BASE
How can I change the status of my Veeam sensors based on whether a job is scheduled or not?
2385
7.8.264 VMware Datastore (SOAP) Sensor
The VMware Datastore (SOAP) sensor monitors the disk usage of a VMware datastore using the Simple
Object Access Protocol (SOAP).
VMw are Datastore (SOAP) Sensor
List 2390 .

§ Dutch: VMware Datastore (SOAP)
§ French: VMware Datastore (SOAP)
§ German: VMware Datastore (SOAP)
§ Japanese: VMware Datastore( SOAP)
§ Portuguese: Armazenamento de dados VMware (SOAP)
§ Russian: VMware (SOAP)

§ Simplified Chinese: VMware (SOAP)
§ Spanish: Almacén de datos VMware (SOAP)
Remarks
2386
Remark Description
does PRTG require?
Parent device § This sensor requires that the parent device is a VMware ESXi server as
of version 5.2 or vCenter.
Credentials § This sensor requires credentials for VMware/XenServer in the settings

of the parent device. Enter a user with sufficient access rights to obtain
statistics (read-only usually works).
channels.
Knowledge Base § Knowledge Base: I cannot add VMware sensors because of "wrong"
password although it is correct. What can I do?
§ Knowledge Base: Why are my VMware sensors not working after
upgrading to VCSA 6.5 U1?
Settings on VMware Host System

If you set up this sensor on different probes (for example, when using remote probes or when running a
failover cluster), you might need to change the settings of your VMware host so that it accepts more
incoming connections. Otherwise, you might get connection timeouts when running plenty of VMware
sensors with a short scanning interval.
For more information, see the Knowledge Base: How can I increase the connection limit on VMware
systems? PE121.
2387
you add the sensor:
§ vmwaredatastoreexternsensor
Datastore Settings
Datastore Settings
Setting Description
Managed Object Identifier The managed object identifier (MOID) of the datastore that this sensor
(MOID) monitors.
scanning interval.
2388
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
2389
Channel List
Channel Description
Accessible The accessibility of the datastore

§ Up status: Yes
§ Down status: No
Available Capacity The available capacity (the physically or virtually available size of the
datastore)
Free Bytes The free space (the disk space that is not used by VMs. Used disk space
can be either thick-provisioned or used by thin-provisioned virtual disks)
Free Space The free space (%) (the disk space that is not used by VMs. Used disk
space can be either thick-provisioned or used by thin-provisioned virtual
disks)
Total Provisioned The total provisioned disk space (%) (the sum of all potentially used disk
space of thin-provisioned and thick-provisioned VM hard drives, that is,
the uncommitted bytes plus used bytes)
Uncommitted Bytes The uncommitted bytes (the disk space that is provisioned for thin-
provisioned VMs but not used yet)
More
KNOWLEDGE BASE
I cannot add VMware sensors because of "wrong" password although it is correct. What can I do?
Why are my VMware sensors not working after upgrading to VCSA 6.5 U1?
2390


Monitoring VMware ESXi 5.5 does not work. What can I do?
2391
7.8.265 VMware Host Hardware (WBEM) Sensor
The VMware Host Hardware (WBEM) sensor monitors information about the hardware of an ESXi server
using Web-based Enterprise Management (WBEM).
VMw are Host Hardw are (WBEM) Sensor
List 2395 .

§ Dutch: VMware Host Hardware (WBEM)
§ French: VMware matériel du serveur hôte (WBEM)
§ German: VMware Host Hardware (WBEM)
§ Japanese: VMware ( WBEM)

§ Portuguese: Hardware de host VMware (WBEM)
§ Russian: VMware (WBEM)

§ Simplified Chinese: VMware (WBEM)
§ Spanish: Hardware de host VMware (WBEM)
Remarks
2392
Remark Description
Enabled CIM Interface on § This sensor requires that the CIM interface is enabled on the ESXi host.
ESXi Host As of ESXi 6.5, you must manually enable CIM.
For more information, see the Knowledge Base: How do I enable the
CIM interface on VMware ESXi 6.5?

of version 5.2.
channels.
Knowledge Base § Knowledge Base: Why are my VMware sensors not working after
you add the sensor:
§ esxshealthsensor
2393
ESXi Server Elements
ESXi Server Elements
Setting Description
Hardware Element The hardware element that this sensor monitors.
Automatic Sensor Status Define if the sensor changes its status depending on the health status
reading:
§ Set sensor to warning or down status (default): Set the sensor to the
Warning or the Down status when the server returns respective values.
The sensor also changes to the Down status if the connection to the
server fails.
§ Report the current reading: Never change the sensor's status
dependent on the values returned by the server. The sensor only
changes to the Down status if the connection to the server fails.
scanning interval.
master node.
2394
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2395
Channel Description
Current The current
Healthstate The health status

§ Up status: OK Unknown
§ Warning status: Degraded, Minor
§ Down status: Critical, Major, Non Recoverable Error
Power The average host power usage
Rotational Speed The fan RPM
More
KNOWLEDGE BASE
How do I enable the CIM interface on VMware ESXi 6.5?


2396
7.8.266 VMware Host Hardware Status (SOAP) Sensor
The VMware Host Hardware Status (SOAP) sensor monitors the hardware status of a VMware host
server using the Simple Object Access Protocol (SOAP). It gives you a general status overview of the
host.
The sensor also shows any states other than normal in the sensor message.
VMw are Host Hardw are Status (SOAP) Sensor
List 2401 .

§ Dutch: VMware Host Hardware Status (SOAP)
§ French: VMware statut du matériel du serveur hôte (SOAP)
§ German: VMware Hostserver Hardware-Zustand (SOAP)
§ Japanese: VMware ( SOAP)

§ Portuguese: Status do hardware de host VMware (SOAP)

§ Spanish: Estado de hardware host VMware (SOAP)
Remarks
2397
Remark Description
does PRTG require?

of version 5.2. We recommend that you do not use this sensor on your
vCenter. Reliable hardware information can only be provided when this
sensor is created on your physical host server as parent device.
Sensors § This sensor only shows items that report an actual state, so you might
see more "sensors" in your vSphere client than the number of states
available in the channels of this sensor

systems? PE121.
2398
you add the sensor:
§ esxserverhosthealthsensor
VMware Host Settings
VMw are Host Settings
Setting Description
Managed Object Identifier The managed object identifier of the host that this sensor monitors.
(MOID)
Known Warnings Enter one or more warning messages from the VMware host that you
want to ignore. Use semicolons (;) as separators, for example, Power
Supply 7;Power Supply 8. Enter a string or leave the field empty.
Warning messages that you enter do not affect the sensor status.
2399
Setting Description
We strongly recommend that you use this filter for known issues
only. For example, for states that systems return because of errors
in the vendors' CIM extensions. Because of this, the sensor might never
show the Up status although the vSphere client does not show any
warnings.
Known Errors Enter one or more error messages from the VMware host that you want to
ignore. Use semicolons (;) as separators, for example, Power Supply
7;Power Supply 8. Enter a string or leave the field empty.
Error messages that you enter do not affect the sensor status.
We strongly recommend that you use this filter for known issues
only. For example, for states that systems return because of errors
in the vendors' CIM extensions. Because of this, the sensor might never
show the Up status although the vSphere client does not show any errors.
Handling of Unknown Define the sensor behavior when the vSphere client reports unknown
States states:
§ Show unknown states (default): Show unknown states in the status
message and set the sensor to the Warning status.
§ Do not show unknown states: Do not show unknown states in the
status message and do not change the sensor status.
scanning interval.
master node.
Sensor Display
Sensor Display
2400
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Alert States The total number of items in the alert status as the vSphere client reports
2401
Channel Description
Normal States The total number of items in the normal status as the vSphere client
reports
Unknown States The total number of items in the unknown status as the vSphere client
reports
Warning States The total number of items in the warning status as the vSphere client
reports
More
KNOWLEDGE BASE


2402
7.8.267 VMware Host Performance (SOAP) Sensor
The VMware Host Performance (SOAP) sensor monitors a VMware host server using the Simple Object
Access Protocol (SOAP).
VMw are Host Performance (SOAP) Sensor
List 2407 .

§ Dutch: VMware Host Prestaties (SOAP)
§ French: VMware performances du serveur hôte (SOAP)
§ German: VMware Hostserver Leistung (SOAP)

§ Portuguese: Performance do host VMware (SOAP)

§ Spanish: Rendimiento de host VMware (SOAP)
2403
Remarks
Remark Description
does PRTG require?
of version 5.2. We recommend that you do not use this sensor on your
vCenter. Reliable hardware information can only be provided when this
sensor is created on your physical host server as parent device.


systems? PE121.
2404
you add the sensor:
§ esxserverhostsensor
VMware Host Settings
VMw are Host Settings
Setting Description
Managed Object Identifier The managed object identifier of the host that this sensor monitors.
(MOID)
scanning interval.
2405
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
2406
Channel List
Channel Description
CPU Ready (Percent) The CPU readiness (%)

Datastore Total The datastore total read latency

ReadLatency
Datastore Total The datastore total write latency

WriteLatency
Disk Usage The disk usage
Disk.DeviceLatency The disk device latency
Disk.KernelLatency The disk kernel latency
Memory Active The active memory
Memory Consumed The consumed memory
Memory Consumed The memory consumed (%)

(Percent)
Memory Swap Used The used memory swap
Network Received The received bytes
2407
Channel Description
Network Transmitted The transmitted bytes
Network Usage The total network usage
More
KNOWLEDGE BASE



2408
7.8.268 VMware Virtual Machine (SOAP) Sensor
The VMware Virtual Machine (SOAP) sensor monitors a virtual machine (VM) on a VMware host server
using the Simple Object Access Protocol (SOAP).
VMw are Virtual Machine (SOAP) Sensor
List 2413 .

§ Dutch: VMware Virtuele Machine (SOAP)
§ French: VMware machine virtuelle (SOAP)
§ German: VMware Virtual Machine (SOAP)

§ Portuguese: Máquina virtual VMware (SOAP)

§ Spanish: Máquina virtual VMware (SOAP)
2409
Remarks
Remark Description
does PRTG require?

Parent device § We recommend that you use vCenter as parent device. If the monitored
VM changes the host server via vMotion, PRTG can still continue
monitoring. The sensor can monitor VMware ESXi server as of version
5.2.
VMs § For VMware virtual machines, disk usage channels are only available
as of virtual hardware version 8.
§ PRTG requests a full list of all VMs configured on the target device
(also those that do not run). Because of this, it might take a few
seconds before the dialog appears.

2410
systems? PE121.
you add the sensor:
§ esxservervmsensor
VMware Virtual Machine Settings
VMw are Virtual Machine Settings
Setting Description
Managed Object Identifier The managed object identifier (MOID) of the VM that this sensor monitors.
(MOID)
Powered-Off VM Define how the sensor reacts to VMs that are powered off:
Handling
§ Alarm when VM is powered off (default): Change to the Down status if
the VM is powered off.
If the sensor is in the Down status, it does not record any data in any
of its channels.
§ Ignore powered off state: Do not change to the Down status if the VM is
powered off. The sensor reports zero values instead.
2411
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description


other above.
2412
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
CPU Ready (Percent) The CPU readiness (%)

Datastore Total Read The datastore total read latency

Latency
Datastore Total Write The datastore total write latency

Latency
Disk Usage The disk usage
2413
Channel Description
Memory Active The active memory
Memory Consumed The consumed memory
Memory Consumed The memory consumed (%)

(Percent)
Network Received The received bytes
Network Transmitted The transmitted bytes
Network Usage The total network usage
More
KNOWLEDGE BASE



2414
7.8.269 Windows CPU Load Sensor
The Windows CPU Load sensor monitors the CPU load on a system via Windows Management
Window s CPU Load Sensor
List 2419 .

§ Dutch: Windows Processor Belasting
§ French: Windows charge CPU
§ German: Windows CPU-Last
§ Japanese: Windows CPU
§ Portuguese: Carga de CPU Windows
§ Russian: Windows
§ Simplified Chinese: Windows CPU
§ Spanish: Carga de CPU Windows
Remarks
2415
Remark Description

WoW64 § This sensor requires WoW64 (Windows 32-bit on Windows 64-bit) for
target systems that run Windows Server 2016.
probe device.

2416
load balancing.
you add the sensor:
§ cpuloadsensor
§ wmicpuloadsensor
Debug Options
Debug Options
Setting Description
master node.
2417
Alternative WMI Query
Setting Description
Query Method Select the method that the sensor uses to query via WMI:
§ Use the default WMI query method (default): Use the standard method
to query WMI. We recommend that you use this option.
§ Use the alternative WMI query method: Use an alternative method to
query WMI for better compatibility if WMI sensors return errors such as
class not valid or invalid data.
Sensor Display
Sensor Display
Setting Description


2418
Setting Description
other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Processor [#] The CPU load of the processor (%)
Total The total CPU load (%)

More
KNOWLEDGE BASE

My Windows sensors do not work when using direct performance counter access. What can I do?
2419
7.8.270 Windows IIS Application Sensor
The Windows IIS Application sensor monitors a Microsoft Internet Information Services (IIS) server via
Windows Management Instrumentation (WMI). It can also monitor applications that use IIS, such as
Microsoft SharePoint or Microsoft Reporting Services (SSRS).
Window s IIS Application Sensor
List 2423 .

§ Dutch: Windows IIS Toepassing
§ French: Windows IIS application
§ German: Windows IIS-Anwendung
§ Japanese: Windows IIS
§ Portuguese: Aplicativo Windows IIS
§ Russian: Windows IIS

§ Simplified Chinese: Windows IIS
2420
§ Spanish: Aplicación IIS Windows
Remarks
Remark Description
Performance counters § The sensor cannot return data for the channels Status, Uptime, and
Total when using performance counters. We recommend that you use
WMI only (default) as Preferred Data Source in the Windows
Compatibility Options of the parent device.
probe device.
you add the sensor:
§ wmiiis
2421
Windows Internet Information Services
Window s Internet Information Services
Setting Description
Instance The unique instance name of the web service that this sensor monitors.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
2422
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Anonymous Users The number of anonymous users
2423
Channel Description

CGI Requests The number of CGI requests
Files Received The number of files received
Files Sent The number of files sent
Get Requests The number of GET requests
Known Users The number of known users
Not Found Errors The number of not found errors
Post Requests The number of POST requests
Status The web service status

§ Up status: Running
§ Down status: Stopped
Total The total
Uptime The uptime
More
KNOWLEDGE BASE

2424
7.8.271 Windows MSMQ Queue Length Sensor
The Windows MSMQ Queue Length sensor reads the number of messages in a Microsoft message
queue of the parent device.
Window s MSMQ Queue Length Sensor
List 2430 .

§ Dutch: Windows MSMQ wachtrijlengte
§ French: Windows MSMQ longueur de la file d'attente
§ German: Windows MSMQ Queue-Länge
§ Japanese: Windows MSMQ
§ Portuguese: Comprimento da fila MSMQ Windows
§ Russian: Windows MSMQ

§ Simplified Chinese: Windows MSMQ
§ Spanish: Longitud de cola MSMQ Windows
Remarks
2425
Remark Description
MSMQ service § This sensor requires that the Microsoft Message Queuing (MSMQ)
service runs on both the probe system and the target system.
§ Depending on your Windows version, you might first need to install the
MSMQ Server.
When installing MSMQ Server, make sure that you install it including
the Directory Service. Depending on your Windows installation, this
might have a different name, such as:
§ MSMQ Active Directory Domain Service Integration
§ Directory Service Integration
§ Active Directory Integration
For more information, see the Knowledge Base: How do I activate

Message Queuing in my Windows installation?
system.
does PRTG require?
Subqueues § This sensor cannot monitor subqueues.
2426
Remark Description
Add Sensor dialog § If no message queues are available in the Add Sensor dialog, you see a
corresponding message.
Knowledge Base § Knowledge Base: How do I activate Message Queuing in my Windows

installation?
probe device.
you add the sensor:
§ ptfsensor
2427
Sensor Settings
Sensor Settings
Setting Description
Message Queue The name of the message queue that this sensor monitors.
Message Queue Type The type of the message queue that this sensor monitors.
Minimum Message Age Optionally define an age in minutes that the message must be for the
sensor to count it. If you set a minimum message age, the sensor does
not regard messages that are younger than this age. If you leave this field
empty, the sensor does not check for the message age. Enter an integer
or leave the field empty.

change.
Debug Options
Debug Options
2428
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description


other above.
2429
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Messages The total number of messages in the queue

More
KNOWLEDGE BASE
How do I activate Message Queuing in my Windows installation?



2430
7.8.272 Windows Network Card Sensor
The Windows Network Card sensor monitors the bandwidth usage and traffic of a network interface via
Windows Management Instrumentation (WMI) or Windows performance counters, as configured in the
Windows Compatibility Options of the parent device.
Window s Netw ork Card Sensor
List 2435 .

§ Dutch: Windows Netwerkkaart
§ French: Windows carte réseau
§ German: Windows Netzwerkadapter
§ Japanese: Windows
§ Portuguese: Adaptador de rede Windows
§ Russian: Windows
2431
§ Simplified Chinese: Windows
§ Spanish: Tarjeta de red Windows
Remarks
Remark Description
system to work with Windows performance counters.
§ This sensor requires at least Windows Server 2008 R2 or Windows 7 to
monitor 64-bit counters of the class Network Adapter (virtual network
interfaces). On older target systems, the sensor can only monitor 32-bit
counters of the class Network Interface (the physical interface) and
shows fewer channels.
Teamed network § This sensor supports teamed network adapters ("network interface card
adapters (NIC) teaming") on Windows Server 2016.
2432
Remark Description
probe device.

load balancing.
you add the sensor:
§ bandwidthsensor
§ wmibandwidthsensor
2433
Sensor Specific
Sensor Specific
Setting Description
Network Card The name of the network card that this sensor monitors.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
2434
Setting Description


channel settings).
other above.
procedure to do so.
Inherited Settings
Channel List
2435
Channel Description
Non-Unicast In The number of incoming non-unicast packets
Non-Unicast Out The number of outgoing non-unicast packets
Packets The total number of packets

Unicast In The number of incoming unicast packets
Unicast Out The number of outgoing unicast packets
Unknown Protocols In The number of unknown protocols
More
KNOWLEDGE BASE

2436
2437
7.8.273 Windows Pagefile Sensor
The Windows Pagefile sensor monitors the Windows pagefile usage via Windows Management
Window s Pagefile Sensor
List 2442 .

§ Dutch: Windows Wisselbestand
§ French: Windows fichier d'échange
§ German: Windows Auslagerungsdatei
§ Portuguese: Arquivo de Paginação (Pagefile) Windows
§ Russian: Windows
§ Spanish: Archivo de página Windows
Remarks
2438
Remark Description

§ This sensor does not work with Windows 2000 because the respective
WMI class does not exist on this operating system.
probe device.
2439
load balancing.
you add the sensor:
§ pagefilesensor
§ wmipagefilesensor
Debug Options
Debug Options
Setting Description
2440
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
2441
Inherited Settings
Channel List
Channel Description
Total The total pagefile usage (%)

More
KNOWLEDGE BASE

2442
7.8.274 Windows Physical Disk I/O Sensor
The Windows Physical Disk I/O sensor monitors the input/output (I/O) parameters of a hard disk on a
Windows system via Windows Management Instrumentation (WMI) or Windows performance counters,
as configured in the Windows Compatibility Options of the parent device.
Window s Physical Disk I/O Sensor
List 2447 .

§ Dutch: Windows Fysieke Schijf I/O
§ French: Windows disque physique E/S
§ German: Windows Physikalischer Datenträger E/A
§ Japanese: Windows I/O

§ Portuguese: E/S de disco físico Windows
§ Russian: Windows
2443
§ Simplified Chinese: Windows I/O
§ Spanish: E/S de disco físico Windows
Remarks
Remark Description
probe device.
2444
load balancing.
you add the sensor:
§ wmiphysicaldisksensor
Windows Physical Disk Specific
Window s Physical Disk Specific
Setting Description
2445
Debug Options
Debug Options
Setting Description
scanning interval.
PRTG only stores the result of this sensor if you select WMI only
(default) as Preferred Data Source in the Windows Compatibility
master node.
Sensor Display
Sensor Display
Setting Description
2446
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Avg. Bytes Per Read The average number of bytes per read
Avg. Bytes Per Transfer The average number of bytes per transfer
Avg. Bytes Per Write The average number of bytes per write
Avg. Queue The average number of items in the queue
Avg. Read Queue The average number of items in the read queue
Avg. Read Time The average read time
2447
Channel Description
Avg. Transfer Time The average transfer time
Avg. Write Queue The average number of items in the write queue
Avg. Write Time The average write time
Current Queue The current number of items in the queue
Disk IOs The number of disk I/O operations
Disk Read IOs The number of disk read I/O operations
Disk Read Time % The disk read time (%)

Disk Time % The disk time (%)
Disk Transfer The disk transfer speed
Disk Write IOs The number of disk write I/O operations
Disk Write Time % The disk write time (%)
Idle Time % The idle time (%)
Split IOs The number of split I/O operations
More
KNOWLEDGE BASE
2448
2449
7.8.275 Windows Print Queue Sensor
The Windows Print Queue sensor reads the print queue on the parent device and returns the number of
jobs in the print queue. It can monitor queues for all printers that are locally installed.
You can use this sensor to monitor all print queues on your Windows print server and to retrieve
information about all available jobs that are in the queue longer than defined.
Additionally, this sensor can change to a defined status if there is a printer problem. See section
Sensor Settings 2452 for available parameters.
Window s Print Queue Sensor
List 2457 .

§ Dutch: Windows Print Queue
§ French: Windows file d'attente d'impression
§ German: Windows Druckwarteschlange
§ Portuguese: Fila de impressão Windows
§ Russian: Windows
§ Spanish: Cola de impresión Windows
Remarks
2450
Remark Description
Print Spooler Windows § This sensor requires that the Print Spooler Windows service runs on
service the target device and the probe system.
system.
does PRTG require?
probe device.
You can add a change trigger to this sensor to get a notification when the number of jobs in the
queue changes.
2451
you add the sensor:
§ ptfsensor
Sensor Settings
Sensor Settings
Setting Description
Print Queue Select the print queues that you want to monitor. PRTG creates one
sensor for each print queue that you select.
If no print queues are available, you see a corresponding message.
If a printer name changes after sensor creation, you need to add the
sensor anew.
Advanced Status Options Optionally define specific sensor states for several return messages of the
printer that this sensor monitors:
§ Do not define sensor states for specific return messages: Do not define
sensor states for specific return messages.
2452
Setting Description
§ Define sensor states for specific return messages: Define sensor states
for various messages that the printer reports.
Not all printer types properly support Advanced Status Options,
which might lead to false alerts. If the printer does not support a
property, this property is always false. This means that the sensor cannot
display the state or detect if the printer supports the property. Even if the
printer can report a property, it can only do so if a print job is sent to the
printer.
Door Open This setting is only visible if you select Define sensor states for specific
return messages above.
For each problem that the printer reports, define the status that the
sensor shows:
§ Ignore (default): Stay the same if the printer reports this message.
§ Warning: Show the Warning status if the printer reports this message.
§ Down: Show the Down status if the printer reports this message.
Manual Feed Required This setting is only visible if you select Define sensor states for specific
sensor shows:
Needs User Intervention This setting is only visible if you select Define sensor states for specific
sensor shows:
Offline This setting is only visible if you select Define sensor states for specific
sensor shows:
2453
Setting Description
Out of Memory This setting is only visible if you select Define sensor states for specific
sensor shows:
Out of Paper This setting is only visible if you select Define sensor states for specific
sensor shows:
Paper Jammed This setting is only visible if you select Define sensor states for specific
sensor shows:
Paper Problem This setting is only visible if you select Define sensor states for specific
sensor shows:
2454
Setting Description
Paused This setting is only visible if you select Define sensor states for specific
sensor shows:
Printer Error This setting is only visible if you select Define sensor states for specific
sensor shows:
Printer Not Available This setting is only visible if you select Define sensor states for specific
sensor shows:
Toner Low This setting is only visible if you select Define sensor states for specific
sensor shows:
Toner Out This setting is only visible if you select Define sensor states for specific
2455
Setting Description
sensor shows:
Minimum Print Job Age Optionally define the age of the print job in seconds. If you define a
(Sec.) minimum print job age, the sensor does not regard jobs that are younger
than this value. If you leave this field empty, the sensor does not check
for the print job age. Enter an integer or leave the field empty.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
2456
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
2457
Channel Description
Jobs The number of jobs in the queue

More
KNOWLEDGE BASE


2458
7.8.276 Windows Process Sensor
The Windows Process sensor monitors a Windows process via Windows Management Instrumentation
(WMI) or Windows performance counters, as configured in the Windows Compatibility Options of the
parent device.
Window s Process Sensor
List 2463 .

§ Dutch: Windows Proces
§ French: Windows processus
§ German: Windows Prozess
§ Portuguese: Processo Windows
§ Russian: Windows
§ Spanish: Proceso Windows
Remarks
2459
Remark Description

Performance counters § The sensor cannot show values above 4 GB for 64-bit processes if you
use performance counters.
probe device.
2460
load balancing.
you add the sensor:
§ wmiprocesssensor
Windows Process Monitor
Window s Process Monitor
Setting Description
Executable Enter the name of the process that you want to monitor. Provide the
name of an executable file without the .exe extension (for example, enter
firefox to monitor firefox.exe).
The sensor shows the Down status if the process is not active on the
target device.
2461
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

2462
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
CPU Usage (Average per The average CPU usage (%) (if multiple instances are running)
Instance)
For this 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.
CPU Usage (Total) The total CPU usage (%)

For this value of a process, all CPU usage values are summed up.
The total is divided by the number of all CPUs and the maximum
value is 100%. This corresponds to the CPU usage of all instances of this
specific process.
2463
Channel Description
Handles The number of handles
Instances The number of instances
Private Bytes The private bytes
Threads The number of threads
Working Set The working set

More
KNOWLEDGE BASE

2464
7.8.277 Windows SMTP Service Received Sensor
The Windows SMTP Service Received sensor monitors the number of received emails of a Windows
Simple Mail Transfer Protocol (SMTP) service via Windows Management Instrumentation (WMI) or
Windows performance counters, as configured in the Windows Compatibility Options of the parent
device.
List 2468 .

§ Dutch: Windows SMTP Service Ontvangen
§ French: Service Windows SMTP reçu
§ German: Windows SMTP-Dienst Empfangen
§ Japanese: Windows SMTP
§ Portuguese: Serviço Windows SMTP recebido
§ Russian: Windows SMTP

§ Simplified Chinese: Windows SMTP
§ Spanish: Servicio SMTP de Windows recibidos
Remarks
Remark Description
2465
Remark Description
probe device.

load balancing.
2466
you add the sensor:
§ wmiiissmtpreceivedsensor
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
2467
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Message Bytes Received The number of bytes in received messages
Messages Received The number of received messages

2468
More
KNOWLEDGE BASE

2469
7.8.278 Windows SMTP Service Sent Sensor
The Windows SMTP Service Sent sensor monitors the number of sent emails on a Windows Simple Mail
Transfer Protocol (SMTP) service via Windows Management Instrumentation (WMI) or Windows
performance counters, as configured in the Windows Compatibility Options of the parent device.
List 2473 .

§ Dutch: Windows SMTP Service Verzonden
§ French: Service Windows SMTP envoyé
§ German: Windows SMTP-Dienst Versendet
§ Japanese: Windows SMTP
§ Portuguese: Serviço Windows SMTP enviado
§ Russian: Windows SMTP

§ Simplified Chinese: Windows SMTP
§ Spanish: Servicio SMTP de Windows enviados
Remarks
Remark Description
2470
Remark Description
probe device.

load balancing.
2471
you add the sensor:
§ wmiiissmtpsentsensor
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
2472
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Message Bytes Sent The number of bytes in sent messages
Message Send Retries The number of retries per second for sent messages
Messages Sent The number of sent messages

2473
More
KNOWLEDGE BASE

2474
7.8.279 Windows System Uptime Sensor
The Windows System Uptime sensor monitors the uptime of a Windows system via Windows
Management Instrumentation (WMI) or Windows performance counters, as configured in the Windows
Compatibility Options of the parent device.
Window s System Uptime Sensor
List 2478 .

§ Dutch: Windows Systeem Uptime
§ French: Windows disponibilité du système
§ German: Windows-Systemlaufzeit
§ Portuguese: Tempo de atividade do sistema Windows
§ Russian: Windows
§ Spanish: Tiempo activo del sistema Windows
Remarks
Remark Description
Performance impact § This sensor has a high performance impact.
2475
Remark Description
probe device.

load balancing.
2476
you add the sensor:
§ wmiuptimesensor
Debug Options
Debug Options
Setting Description
master node.
2477
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2478
Channel Description
More
KNOWLEDGE BASE

2479
7.8.280 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 updates that are either from Microsoft or from
the local Windows Server Update Services (WSUS) server.
You can find the updates that the sensor considers in the Server Manager (WSUS) under Roles |
Windows Server Update Services | Update Services | Computers | Reports.
Window s Updates Status (Pow erShell) Sensor
List 2485 .

§ Dutch: Windows Updates Status (PowerShell)
2480
§ French: Windows statut des mises à jour (PowerShell)
§ German: Windows Updates Status (PowerShell)
§ Japanese: Windows ( PowerShell)

§ Portuguese: Status de atualizações do Windows (PowerShell)
§ Russian: Windows (PowerShell)

§ Simplified Chinese: Windows (PowerShell)
§ Spanish: Estado de actualizaciones Windows (PowerShell)
Remarks
Remark Description
system.
does PRTG require?
this sensor.
§ The minimum scanning interval of this sensor is 1 hour.
§ The recommended scanning interval of this sensor is 12 hours. We

recommend this scanning interval to limit the load on the server that
2481
Remark Description
Initial data § In certain cases, it might take some time until the sensor receives data
for the first time.
Time Since Last Update § If the sensor cannot determine any values for the Time Since Last
channel Update channel (for example, because the list of updates is empty), it
shows the value -1s and changes to the Warning status.
Roaming Profiles § When monitoring a Remote Desktop Server (RDS) system with the
option Roaming Profiles enabled, this sensor creates a temporary user
profile folder for each scanning interval. To minimize this effect, we
recommend that you set the sensor's scanning interval to at least 7
days.
sensors?
probe device.
you add the sensor:
§ windowsupdatesstatus
2482
Sensor Specific
Sensor Specific
Setting Description
Port in SPN Define whether to include the port number in the Service Principal Name
(SPN) used for Kerberos authentication, for example, on devices where
Microsoft Internet Information Services (IIS) or similar services are
installed:
§ Exclude port in SPN (default): Do not include the port number in the
SPN.
§ Include port in SPN: Include the port number in the SPN.
With this option, a client that uses a non-default SPN can

authenticate against a remote computer that uses Kerberos
authentication.
Authentication Method Select the authentication method for the connection to the host via
PowerShell:
§ Kerberos authentication (default): The sensor uses Kerberos
authentication.
§ Negotiate authentication: The sensor uses Negotiate authentication.
For more information about Negotiate authentication, see the
Knowledge Base: Facing issues with the Windows Updates Status
(PowerShell) sensor - can you help me?
Debug Options
Debug Options
2483
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
2484
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Time Since Last Update The time passed since the last update

The sensor always creates the channel Time Since Last Update.
All other channels are optional and only show up if the sensor
can retrieve respective data.
Updates (Severity The number of hidden updates with critical severity

Critical) Hidden
Updates (Severity The number of installed updates with critical severity

Critical) Installed
2485
Channel Description
Updates (Severity The number of missing updates with critical severity

Critical) Missing
Updates (Severity The number of hidden updates with important severity

Important) Hidden
Updates (Severity The number of installed updates with important severity

Important) Installed
Updates (Severity The number of missing updates with important severity

Important) Missing
Updates (Severity Low) The number of hidden updates with low severity
Hidden
Updates (Severity Low) The number of installed updates with low severity
Installed
Updates (Severity Low) The number of missing updates with low severity
Missing
Updates (Severity The number of hidden updates with moderate severity

Moderate) Hidden
Updates (Severity The number of installed updates with moderate severity

Moderate) Installed
Updates (Severity The number of missing updates with moderate severity

Moderate) Missing
Updates (Unclassified) The number of hidden updates with unclassified severity

Hidden
2486
Channel Description
Updates (Unclassified) The number of installed updates with unclassified severity

Installed
Updates (Unclassified) The number of missing updates with unclassified severity

Missing
More
KNOWLEDGE BASE






Facing issues with the Windows Updates Status (PowerShell) sensor - can you help me?
2487
7.8.281 WMI Battery Sensor
The WMI Battery sensor monitors the available capacity and the state of connected batteries or
uninterruptible power supplies (UPSs) of a Windows-based device via Windows Management
Instrumentation (WMI).
WMI Battery Sensor
List 2491 .

§ Dutch: WMI batterij
§ French: Batterie (WMI)
§ German: WMI Batterie
§ Japanese: WMI
§ Portuguese: Bateria (WMI)
§ Russian: WMI
§ Simplified Chinese: WMI
§ Spanish: Batería (WMI)
Remarks
2488
Remark Description
Performance impact § This sensor has a high performance impact. Stay below 200 WMI
sensors per probe. Above this number, consider using multiple remote
probes for load balancing.
channels.
probe device.
you add the sensor:
§ batterysensor
§ wmibatterysensor
2489
WMI Battery Specific
WMI Battery Specific
Setting Description
Name The name of the battery or the UPS that this sensor monitors.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
2490
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Battery Health The battery health (%)
2491
Channel Description
Estimated Charge The estimated remaining charge (%)

Remaining
Status The battery status

§ Up status: Charging, Discharging, Fully Charged, Unknown
§ Warning status: Critical But Charging
§ Down status: Critical But Discharging
Time Until Empty The time until the battery is empty
Time Until Full The time until the battery is fully charged
Voltage The voltage
More
KNOWLEDGE BASE


2492
7.8.282 WMI Custom Sensor
The WMI Custom sensor performs a custom query via Windows Management Instrumentation (WMI) and
monitors numeric values (integers and floats).
If the WQL query returns strings, use the WMI Custom String 2499 sensor.
WMI Custom Sensor
List 2498 .

§ Dutch: WMI (Klant Specifiek)
§ French: Requête personnalisée (WMI)
§ German: WMI (Benutzerdef.)
§ Japanese: WMI
§ Portuguese: WMI (customizado)
§ Russian: WMI
§ Spanish: WMI (personalizado)
Remarks
2493
Remark Description
Knowledge Base § Knowledge Base: Why do I have to store SQL sensor queries and
§ Knowledge Base: How do I create a WMI Custom sensor?
probe device.
Add Sensor
Setting Description
Channel Name Enter a name for the channel in which PRTG shows the received data.
PRTG shows this name in graphs and tables. Enter a string.
sensor.
2494
you add the sensor:
§ wmicustomsensor
Custom Query Specific
Setting Description
Namespace Enter the WMI namespace for the query.
WQL File Select a .wql file. The sensor executes it with every scanning interval.
The list contains WQL scripts that are available in the \Custom
Sensors\WMI WQL scripts subfolder of the PRTG program directory on
the probe system. Store your script there. If used on a cluster probe, you
must store the file on all cluster nodes.
Your query must return an integer or float value. Strings are not
supported. Use the WMI Custom String 2499 sensor in this case.
Placeholder <#PH1> In your WQL script, you can use up to three placeholders to which you
can assign a value in this field. Enter a string for variable <#PH1> or leave
the field empty.
2495
Setting Description
the field empty.
the field empty.

change.
Unit String Enter a unit for the data that the sensor receives from your script. This is
for display purposes only. The unit is displayed in graphs and tables.
Enter a string.
Multiplication Define a multiplier for the received values. The default value 1 does not
change received values. Enter an integer.
Division Define a divisor for the received values. The default value 1 does not
change received values. Enter an integer.
Debug Options
Debug Options
Setting Description
2496
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
2497
Channel List
Channel Description
[Value] The retrieved numeric value

More
KNOWLEDGE BASE
How do I create a WMI Custom sensor?

How do I properly configure a WMI custom sensor?

Which WQL queries are used by the PRTG WMI sensors?


2498
7.8.283 WMI Custom String Sensor
The WMI Custom String sensor performs a custom string query via Windows Management
The sensor can also show the retrieved string value in the sensor message.
If the WQL query returns numeric values, use the WMI Custom 2493 sensor.
WMI Custom String Sensor
List 2506 .

§ Dutch: WMI Aangepaste Tekenreeks
§ French: Chaîne personnalisée (WMI)
§ German: WMI Text (benutzerdef.)
§ Japanese: WMI
§ Portuguese: Sequência de caracteres (customizado) (WMI)
§ Russian: WMI
§ Spanish: Cadena (personalizado) (WMI)
Remarks
2499
Remark Description
Knowledge Base § Knowledge Base: Why do I have to store SQL sensor queries and
§ Knowledge Base: How do I create a WMI Custom sensor?
probe device.
you add the sensor:
§ wmicustomsensor
2500
Setting Description
Namespace Enter the WMI namespace for the query.

.
WQL File Select a .wql file. The sensor executes it with every scanning interval.
2501
Setting Description
The list contains WQL scripts that are available in the \Custom
Sensors\WMI WQL scripts subfolder of the PRTG program directory on
the probe system. Store your script there. If used on a cluster probe, you
must store the file on all cluster nodes.
If the WQL query returns integers or floats, use the WMI Custom 2493
sensor to not only show the returned value in the sensor message,
but to also monitor the value in a channel.
the field empty.
the field empty.
the field empty.
Unit String Enter a unit for the data that the sensor receives from your script. This is
for display purposes only. The unit is displayed in graphs and tables.
Enter a string.

change.
Response Must Include Define the search string that must be part of the data that is received from
(Down Status if Not the WMI object. You can enter a simple string in plain text or a regular
Included) expression.
Down status.
Response Must Not Define the search string that must not be part of the data that is received
Include (Down Status if from the WMI object. You can enter a simple string in plain text or a
Included) regular expression.
2502
Setting Description

Down status.

§ Regular expression: Search with a regular expression (regex).

Maximum String Length Define the maximum allowed length of the string that is received from the
WMI object. If it is longer than this value, the sensor shows the Down
Numeric Value Define if you want to filter out a numeric value from the string received
Extraction from the WMI object:
§ Do not use extraction (default): Do not extract a float value. Use the
result as a string value.
§ Use a regular expression for extraction: Use a regex to identify a
numeric value in the string and convert it to a float value. Define below.
See also the example 2505 .
You can convert this into a float value to use it with channel
limits.
Regular Expression This setting is only visible if you select Use a regular expression for
extraction above.
Enter a regex 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 that the expression returns numbers only (including
decimal and thousands separators). The result is further refined by
the settings below.

2503
Setting Description
Index of Capturing Group This setting is only visible if you select Use a regular expression for
extraction above.
If your regex uses capturing groups, specify which one captures the
number. Enter an integer or leave the field empty.
Decimal Separator This setting is only visible if you select Use a regular expression for
extraction above.
Define the character for the decimal separator of the number. Enter a
Thousands Separator This setting is only visible if you select Use a regular expression for
extraction above.
Define the character for the thousands separator of the number. Enter a
master node.
Sensor Display
Sensor Display
Setting Description
2504
Setting Description



other above.
procedure to do so.
Inherited Settings
Number Extraction with Regular Expression

If you want to extract a number in the response string via a regex, note that the index for captures in
this sensor is based on 1 (not on 0). Furthermore, capturing groups are not automatically created.
The example below illustrates 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, this is the percentage in the second parentheses.
Enter the following regex in the Regular Expression field:
(\d+\.\d+).*?(\d+\.\d+).*?(\d+\.\d+)
As Index of Capturing Group, enter 3. This extracts the desired number 3.555.
The index must 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
2505
Keep this note about index and capturing groups in mind when using number extraction.
It is not possible to match an empty string with the PRTG regex sensor search.
PRTG supports Perl Compatible Regular Expression (PCRE) regex. For more information, see
section Regular Expressions.
Channel List
Channel Description

More
KNOWLEDGE BASE
How do I create a WMI Custom sensor?



2506
7.8.284 WMI Disk Health Sensor
The WMI Disk Health sensor monitors the health of a physical disk on a Windows system via Windows
Management Instrumentation (WMI).
WMI Disk Health Sensor
List 2510 .

§ Dutch: WMI schijfstatus
§ French: État du disque (WMI)
§ German: WMI Laufwerkszustand
§ Japanese: WMI
§ Portuguese: Funcionamento do disco (WMI)
§ Russian: WMI
§ Spanish: Salud de disco (WMI)
Remarks
2507
Remark Description
Windows version § This sensor supports Windows versions as of Windows 10 or Windows

Server 2016 on the target system.
probe device.
you add the sensor:
§ diskhealthsensor
§ wmidiskhealthsensor
2508
WMI Disk Health Specific
WMI Disk Health Specific
Setting Description
Friendly Name The user-friendly name for the physical disk that this sensor monitors.
Debug Options
Debug Options
Setting Description
master node.
2509
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2510
Channel Description
Flush Latency Max The maximum flush latency

Operational Status The operational status

§ Up status: OK
§ Unknown status: Starting
Read Latency Max The maximum read latency
Write Latency Max The maximum write latency
More
KNOWLEDGE BASE


2511
7.8.285 WMI Event Log Sensor
The WMI Event Log sensor monitors a Windows log file via Windows Management Instrumentation
(WMI).
You can individually set the sensor to a specific status according to a new event log entry.
WMI Event Log Sensor
List 2519 .

§ Dutch: WMI Logboek
§ French: Journal des événements (WMI)
§ German: WMI Ereignisprotokoll
§ Japanese: WMI
§ Portuguese: Log de eventos (WMI)
§ Russian: WMI
§ Spanish: Registro de eventos (WMI)
Remarks
2512
Remark Description
Knowledge Base § Knowledge Base: My Event Log sensor ignores changes in the event
log. What can I do?
§ Knowledge Base: How can I configure sensors using speed limits to
keep the status for more than one interval?
probe device.
you add the sensor:
§ wmieventlogsensor
2513
WMI Event Log Monitor
WMI Event Log Monitor
Setting Description
Log File The Windows log file that this sensor monitors.
scanning interval.
master node.

For more information and how to find out the correct filter, see the Knowledge Base: My Event Log
sensor ignores changes in the event log. What can I do?
2514
Setting Description
Event Type Specify the type of event that this sensor processes:
§ Any
§ Error
§ Warning
§ Information
§ Security Audit Success
§ Security Audit Failure
The sensor cannot process other event types.
2515
Setting Description
Filter by Source Filter all received events for a certain event source:

you define below.

Source)
Enter an event source that you want to filter for. Depending on the kind of
filter, the sensor either processes the event source (Include filter option)
or it does not process it (Exclude filter option). Enter a string.
Filter by ID Filter all received events for a certain event ID:


you define below.

Match Values (Event ID) This setting is only visible if you select On above.
Enter an event ID that you want to filter for. Depending on the kind of filter,
the sensor either processes the event ID (Include filter option) or it does
not process it (Exclude filter option).
The WMI Event Log supports more than one event ID. You can enter
a comma-separated list of event IDs to filter for more than one ID. For
example, 1100,4627,4747,4884,5050,6422.
Filter by Category Filter all received events for a certain event category:
2516
Setting Description

you define below.

Category)
Enter a category that you want to filter for. Depending on the kind of filter,
the sensor either processes the event category (Include filter option) or it
Filter by User Filter all received events for a certain event user:

you define below.
User)
Enter a user name that you want to filter for. Depending on the kind of
filter, the sensor either processes the event user (Include filter option) or it
Filter by Computer Filter all received events for a certain event computer:

you define below.
2517
Setting Description

Computer)
Enter a computer name that you want to filter for. Depending on the kind
of filter, the sensor either processes the event computer (Include filter
option) or it does not process it (Exclude filter option). Enter a string.
Filter by Message Filter all received events for a certain event message:

you define below.

Message)
Enter a message that you want to filter for. Depending on the kind of filter,
the sensor either processes the event message (Include filter option) or it
You must use the percent sign (%) as wildcard for any or no
character if you want to check if the string is part of the message.
Otherwise, the whole event message must match the string. For
example, you can enter %RAS% for any event message that contains the
string RAS.
Sensor Display
Sensor Display
2518
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
2519
Channel Description
New Records The number of new records

More
KNOWLEDGE BASE
My Event Log sensor ignores changes in the event log. What can I do?


2520
7.8.286 WMI Exchange Server Sensor
The WMI Exchange Server sensor monitors a Microsoft Exchange Server as of version 2016 via Windows
You might be able to monitor aspects regarding:
§ SMTP Server: Queue Lengths
§ MSExchangeIS Mailbox: Queue Sizes, Delivery Times, Operations, Messages
§ MSExchangeIS Public: Queue Sizes, Delivery Times, Operations, Messages
§ MSExchangeIS: Packets, Operations, Clients, Latency, Requests, Users
§ MSExchange RPC Client Access: Active User Count, User Count, Connection Count
§ MSExchange OWA: Current Unique Users, Average Response Time
Depending on your Exchange server version, not all counters might be available.
WMI Exchange Server Sensor
List 2525 .

§ Dutch: WMI Exchange Server
§ French: Exchange serveur (WMI)
§ German: WMI Exchange-Server
§ Japanese: WMI Exchange
§ Portuguese: Servidor Exchange (WMI)
§ Russian: WMI Exchange Server
2521
§ Simplified Chinese: WMI Exchange
§ Spanish: Servidor Exchange (WMI)
Remarks
Remark Description
probe device.
you add the sensor:
§ wmiexchangeserversensor
2522
Exchange Server Data Readings Accessible Using WMI
Exchange Server Data Readings Accessible Using WMI
Setting Description
Display Name The display name that the sensor uses to query data from the target
device.
Instance The instance that the sensor uses to query data from the target device.
WMI Class The WMI class that the sensor uses to query data from the target device.
Counter The counter that the sensor uses to query data from the target device.
Time Stamp The time stamp that the sensor uses to query data from the target device.
Time Frequency The time frequency that the sensor uses to query data from the target
device.
Counter Type The counter type that the sensor uses to query data from the target
device.
scanning interval.
2523
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
2524
Channel List
Channel Description
Active User Count The number of active users
Average Response Time The average response time (OWA)
Connection Count The number of connections
Current Unique Users The number of current unique users (OWA)
RPC Requests Failed The number of failed RPC requests
RPC Requests The number of outstanding RPC requests

Outstanding
RPC Requests Sent The number of sent RPC requests
RPC Slow Requests The number of slow RPC requests
User Count The number of users
More
KNOWLEDGE BASE


2525
7.8.287 WMI Exchange Transport Queue Sensor
The WMI Exchange Transport Queue sensor monitors the length of transport queues of a Microsoft
Exchange Server as of version 2016 via Windows Management Instrumentation (WMI). It shows the
same information as in Windows System Monitor perfmon.
WMI Exchange Transport Queue Sensor
For more information and an explanation of transport queue types, see the Knowledge Base: What
types of Exchange transport queues are there?
List 2530 .

§ Dutch: WMI Exchange Transport Wachtrij
§ French: Exchange file d'attente de transport (WMI)
§ German: WMI Exchange Transportwarteschlange
§ Japanese: WMI Exchange
§ Portuguese: Fila de transporte Exchange (WMI)
§ Russian: WMI Exchange

§ Simplified Chinese: WMI Exchange
§ Spanish: Cola de transporte Exchange (WMI)
Remarks
2526
Remark Description
Knowledge Base § Knowledge Base: What types of Exchange transport queues are there?
probe device.
Add Sensor
Setting Description
Transport Queue Select the transport queues that you want to monitor. PRTG creates one
sensor for each transport queue that you select.
The available options depend on your Exchange server configuration.
PRTG shows all possible queues with names and instance
descriptions (if available).
For performance reasons, we recommend that you only select
necessary items.
2527
you add the sensor:
§ wmiexchangeservertransportqueuesensor
WMI Exchange Transport Queue Specific
WMI Exchange Transport Queue Specific
Setting Description
device.
device.
device.
2528
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
2529
Inherited Settings
Channel List
Channel Description
Active Mailbox Delivery The number of items in the active mailbox delivery queue
Queue Length
Active Non-SMTP The number of items in the non-SMTP delivery queue

Delivery Queue Length
Active Remote Delivery The number of items in the active remote delivery queue
Queue Length
Aggregate Delivery The number of items in the aggregate delivery queue (all queues)
Queue Length (All
Queues)
Aggregate Shadow The number of items in the aggregate shadow queue

Queue Length
Categorizer Job The categorizer job availability

Availability
Items Completed Delivery The number of items with completed delivery

Per Second
Items Completed Delivery The number of items with completed delivery in total
Total
Items Deleted By Admin The number of items deleted by the admin in total
Total
2530
Channel Description
Items Queued For The number of items expired queued for delivery in total
Delivery Expired Total
Items Queued for The number of items queued for delivery

Delivery Per Second
Items Queued For The number of items queued for delivery in total
Delivery Total
Items Resubmitted Total The number of items resubmitted in total
Largest Delivery Queue The largest number of items in the delivery queue
Length
Messages Completed The number of messages with completed delivery

Delivery Per Second
Messages Completed The number of messages with completed delivery in total

Delivery Total
Messages Completing The number of messages completing categorization

Categorization
Messages Deferred Due The number of messages deferred due to local loop
To Local Loop
Messages Deferred The number of messages deferred during categorization

During Categorization
Messages Queued For The number of messages queued for delivery

Delivery
Messages Queued for The number of messages queued for delivery per second
Delivery Per Second
Messages Queued For The number of messages queued for delivery in total
Delivery Total
Messages Submitted Per The number of messages submitted

Second
Messages Submitted The number of messages submitted in total

Total
2531
Channel Description
Poison Queue Length The number of items in the poison queue
Retry Mailbox Delivery The number of items in the retry mailbox delivery queue
Queue Length
Retry Non-SMTP Delivery The number of items in the retry non-SMTP delivery queue
Queue Length
Retry Remote Delivery The number of items in the retry remote delivery queue
Queue Length
Shadow Queue Auto The number of auto discards in the shadow queue in total
Discards Total
Submission Queue Items The number of items expired in the submission queue in total
Expired Total
Submission Queue The number of items in the submission queue

Length
Unreachable Queue The number of items in the unreachable queue

Length
More
KNOWLEDGE BASE
What types of Exchange transport queues are there?



2532
7.8.288 WMI File Sensor
The WMI File sensor monitors a file via Windows Management Instrumentation (WMI).
WMI File Sensor
List 2536 .

§ Dutch: WMI Bestand
§ French: Fichier (WMI)
§ German: WMI Datei
§ Japanese: WMI
§ Portuguese: Arquivo (WMI)
§ Russian: WMI
§ Spanish: Archivo (WMI)
Remarks
2533
Remark Description
probe device.
you add the sensor:
§ wmifilesensor
WMI File Monitor
WMI File Monitor
2534
Setting Description
File Name Enter the name of the file that you want to monitor. Enter the full local
path. The file must exist on the probe system.
The sensor does not support Universal Naming Convention (UNC)
paths.
If Time Stamp Changes Define what the sensor does if the time stamp of the file changes:

change.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
2535
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
2536
Channel Description
File Size The file size

Last Modified The time since the last modification of the file
More
KNOWLEDGE BASE


2537
7.8.289 WMI Free Disk Space (Multi Disk) Sensor
The WMI Free Disk Space (Multi Disk) sensor monitors the free disk space of one or more drives via
Windows Management Instrumentation (WMI).
The sensor monitors logical partitions of a hard or fixed disk drive. PRTG identifies logical disks by
their drive letter, such as C.
WMI Free Disk Space (Multi Disk) Sensor
List 2544 .

§ Dutch: WMI Vrije Schijfruimte (Multi Schijf)
§ French: Capacité disponible de multiples disques (WMI)
§ German: WMI Laufwerkskapazität (mehrf.)
§ Japanese: WMI ( )
§ Portuguese: Espaço livre em disco (vários discos) (WMI)
§ Russian: WMI )
§ Simplified Chinese: WMI ( )
§ Spanish: Espacio libre en disco (discos múltiples) (WMI)
Remarks
2538
Remark Description
probe device.
you add the sensor:
§ diskspacesensor
§ wmidiskspacesensor
Drive Selection
Drive Selection
2539
Setting Description
Drives The drives that this sensor monitors. This is either All or a specific drive
letter.

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 shows the Warning or the Down status, depending on the data provided by all
drives that this sensor monitors. If you want to individually define limits for separate channels, use the
limit settings in the channel settings.
All limits that you define here are valid in addition to the limits defined in the particular channel
settings. The limits are valid simultaneously, so the first limit that is breached applies.
Setting Description
2540
Setting Description
Lower Error Limit Specify a lower limit in percent for the Down status. If the free disk space
2541
Setting Description
limits for the sensor that are valid for all byte size channels. Additional
fields appear below. The sensor shows the Warning or Down status
when free space limits are above or below the value.
2542
Setting Description

found.
Debug Options
Debug Options
Setting Description
master node.
2543
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2544
Channel Description
Free Bytes C: The free space
Free Bytes D: The free space
Free Space C: The free space (%)
Free Space D: The free space (%)
Total The total disk space
More
KNOWLEDGE BASE


2545
7.8.290 WMI HDD Health Sensor
The WMI HDD Health sensor connects to the parent device via Windows Management Instrumentation
(WMI) and monitors the health of integrated development environment (IDE) disk drives on the target
system using Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.).
WMI HDD Health Sensor
List 2550 .

§ Dutch: WMI HDD Status
§ French: État du disque dur (WMI)
§ German: WMI Laufwerkszustand
§ Japanese: WMI HDD
§ Portuguese: Funcionamento do HDD (WMI)
§ Russian: WMI
2546
§ Spanish: Salud HDD (WMI)
Remarks
Remark Description
Windows version § This sensor requires at least Windows 7 on the target system that
holds the hard disk drives you want to monitor. The sensor might not
work reliably if the target system runs on Windows 2003, Windows XP,
or Windows Vista. Because of a known bug in those systems, the
sensor might not detect available hard disk drives.
Sensor values § The values that this sensor shows can vary depending on how a vendor
handles S.M.A.R.T. values. See the respective vendor's documentation
Add Sensor dialog § The items in the list in the Add Sensor dialog are specific to the parent
device.
probe device.
2547
you add the sensor:
§ smartsensor
S.M.A.R.T. Specific
S.M.A.R.T. Specific
Setting Description
Serial Number The serial number of the disk that this sensor monitors.
Size (GB) The size of the disk that this sensor monitors.
Name The name of the disk that this sensor monitors.
Debug Options
Debug Options
2548
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description



other above.
2549
Setting Description
procedure to do so.
Inherited Settings
Channel List
The channel names indicate the ID of the S.M.A.R.T. attribute, followed by a colon, and the typical
meaning of the channel. The sensor can also show other attributes that the target device returns, but
some channels have the name Unknown Channel. This happens if PRTG cannot match the ID of a found
attribute with an internally defined channel name.
Some vendors do not agree on attribute definitions and define meanings other than the common
ones.
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 health.
Higher 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 automatically shows
the Warning status. This indicates that the S.M.A.R.T. status of the HDD might break soon.
For some attributes, there are no thresholds defined and because of this, they cannot be
categorized for a status other than the Up status. You can define lookups and use them with
affected channels to get the desired status for a return value.
Channel Description
Average Erase Count The average erase count and the maximum erase count
And Maximum Erase
Count
Command Timeout The command timeout count
2550
Channel Description
Erase Fail Count The erase fail count
G-Sense Error Rate The G-sense error rate count
Hardware ECC The hardware ECC recovered count

Recovered
Power Cycle Count The power cycle count
Power Loss Protection The power loss protection failure count

Failure
Power-On Hours The power-on hours count
Program Fail Count Total The program fail count total
Read Error Rate The read error rate count

Read Error Retry Rate The read error retry rate count
Reallocated Sectors The reallocated sectors count

Count
Reported Uncorrectable The reported uncorrectable errors count

Errors
SATA Downshift Error The SATA downshift error count

Count
Soft ECC Correction The soft ECC correction count
Soft Read Error Rate The soft read error rate count
SSD Erase Fail Count The SSD erase fail count
SSD Life Left The SSD life left count
2551
Channel Description
SSD Program Fail Count The SSD program fail count
Unexpected Power Loss The unexpected power loss count

Count
Unknown Channel PRTG cannot match the ID of a found attribute with an internally defined
channel name
Unused Reserved Block The total unused reserved block count

Count Total
Used Reserved Block The total used reserved block count

Count Total
Temperature Celsius The temperature
Total LBAs Read The total LBAs read
Total LBAs Written The total LBAs written
Wear Range Delta The wear range delta
More
KNOWLEDGE BASE


2552
7.8.291 WMI Logical Disk I/O Sensor
The WMI Logical Disk I/O sensor monitors the disk usage of a logical disk or mount point on a Windows
system via Windows Management Instrumentation (WMI).
The sensor shows performance data of counters that monitor logical partitions of a hard drive. The
system monitor identifies logical disk instances by their identifier, such as C, and the sensor reads
the logical disk object in the system monitor and returns the values.
WMI Logical Disk I/O Sensor
List 2556 .

§ Dutch: WMI Logische Schijf I/O
§ French: Disque logique E/S (WMI)
§ German: WMI Logischer Datenträger E/A
§ Japanese: WMI I/O

§ Portuguese: E/S do disco lógico (WMI)
§ Russian: WMI
2553
§ Simplified Chinese: WMI I/O
§ Spanish: E/S de disco lógico (WMI)
Remarks
Remark Description
Windows version § This sensor requires at least Windows Server 2008 R2. It does not work
on previous Windows versions (Windows Server 2008 or earlier).
probe device.
you add the sensor:
§ wmilogicalsensor
2554
WMI Logical Disk I/O Specific
WMI Logical Disk I/O Specific
Setting Description
Disk The logical disk or mount point that this sensor monitors.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
2555
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Avg. Bytes Per Read The average number of bytes per read
Avg. Bytes Per Transfer The average number of bytes per transfer
2556
Channel Description
Avg. Bytes Per Write The average number of bytes per write
Avg. Queue Length The average number of items in the queue
Avg. Read Queue The average number of items in the read queue
Avg. Read Time The average read time
Avg. Transfer Time The average transfer time
Avg. Write Queue The average number of items in the write queue
Avg. Write Time The average write time
Current Queue The current number of items in the queue
Disk IOs The number of disk I/O operations
Disk Read IOs The number of disk read I/O operations
Disk Read Time % The disk read time (%)
Disk Time % The disk time (%)
Disk Transfer The disk transfer speed
Disk Write IOs The number of disk write I/O operations
Disk Write Time % The disk write time (%)
2557
Channel Description
Idle Time % The idle time (%)
Split IOs The number of split I/O operations
More
KNOWLEDGE BASE


2558
7.8.292 WMI Memory Sensor
The WMI Memory sensor monitors available (free) system memory on Windows systems via Windows
WMI Memory Sensor
List 2562 .

§ Dutch: WMI Geheugen
§ French: Mémoire (WMI)
§ German: WMI Arbeitsspeicher
§ Japanese: WMI
§ Portuguese: Memória (WMI)
§ Russian: WMI
§ Spanish: Memoria (WMI)
Remarks
2559
Remark Description
probe device.
you add the sensor:
§ memorysensor
§ wmimemorysensor
Debug Options
Debug Options
2560
Setting Description
master node.
Setting Description
Query Method Select the method that the sensor uses to query via WMI:
§ Use the default WMI query method (default): Use the standard method
to query WMI. We recommend that you use this option.
§ Use the alternative WMI query method: Use an alternative method to

query WMI for better compatibility if WMI sensors return errors such as
class not valid or invalid data.
Sensor Display
Sensor Display
2561
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
2562
Channel Description

More
KNOWLEDGE BASE


2563
7.8.293 WMI Microsoft SQL Server 2005 Sensor (Deprecated)
Important Notice
This sensor is deprecated.

Monitoring of Microsoft SQL Server 2005 using PRTG is discontinued. Microsoft SQL Server 2005
cannot be monitored with PRTG anymore 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:
§ Security Update for SQL Server 2005 Service Pack 4 (KB2716429)
§ Security Update for SQL Server 2005 Service Pack 4 (KB2716427)
We have made reasonable effort to fix this from our side but we were unable to do so. We do not have
instructions to circumvent this issue at this time. Please ask the vendor to fix this.
More
Knowledge Base: Why does my WMI Microsoft SQL Server 2005 sensor not work anymore?
The WMI Microsoft SQL Server 2005 sensor monitors the performance of a Microsoft SQL Server via
WMI Microsoft SQL Server 2005 Sensor
List 2569 .
2564
§ Dutch: WMI Microsoft SQL Server 2005
§ French: Microsoft SQL serveur 2005 (WMI)
§ German: WMI Microsoft SQL Server 2005
§ Japanese: WMI Microsoft SQL Server 2005
§ Portuguese: Microsoft SQL Server 2005 (WMI)
§ Russian: WMI Microsoft SQL Server 2005
§ Simplified Chinese: WMI Microsoft SQL Server 2005
§ Spanish: Microsoft SQL Server 2005 (WMI)
Remarks
Remark Description
Target system § You can only add this sensor to a target system that runs a Microsoft
SQL database.
probe device.
2565
you add the sensor:
§ wmisqlserversensor
SQL Server Settings
SQL Server Settings
Setting Description
Service The service that this sensor monitors.

The service name is provided as returned by the SQL server.
Name The name of the server instance that this sensor monitors.
The display name is provided as returned by the SQL server.
Naming Method Select whether PRTG automatically selects the name of the WMI class
used for monitoring:
2566
Setting Description
§ Automatically determine the WMI class name (default): Automatically

select WMI class. We recommend this setting.
§ Manually enter the WMI class name: Manually enter a WMI class
name. Select this option if your server instance returns an error code in
automatic mode.
WMI Class This setting is only visible if you select Manually enter the WMI class
name above.
Enter the WMI class name that the sensor uses to monitor the server
instance.
scanning interval.
master node.
SQL Counter Specific
Setting Description
Performance Counters You see a list of different groups of performance counters that the sensor
can monitor for the instances that you selected above. Every sensor that
PRTG creates for the server instances monitors the performance counters
you select here.
§ General Statistics: Read general performance counters. This shows the
number of user connections and the number of logins and logouts per
second.
§ Access Methods: Read access method counters. This shows the
number of full scans, page splits, and table lock escalations (per
second).
2567
Setting Description
§ Buffer Manager: Read buffer manager counters. This shows the buffer
cache hit ratio in percent and the number of database pages and stolen
pages.
§ Memory Manager: Read memory manager counters. This shows the
connection memory, optimizer memory, total server memory, target
server memory, and SQL cache memory (in kb).
§ Locks: Read locks counters. This shows the number of lock requests
and deadlocks (per second), and the average wait time.
§ SQL Statistics: Read SQL statistics. This shows the number of batch
requests, SQL compilations, and SQL re-compilations (per second).
Depending on your selection, PRTG creates a sensor with the specified
channels.
To monitor more than one of the listed groups of performance
counters, add the sensor several times for the respective instances.
After sensor creation, this setting shows the performance counter
that this sensor monitors.
Sensor Display
Sensor Display
Setting Description

2568
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Average Wait Time The average amount of wait time for each lock request that resulted in a
wait
Batch Requests/Sec The number of Transact-SQL command batches received. This statistic is
affected by all constraints (such as input/output, number of users, cache
size, or complexity of requests). High batch requests mean good
throughput.
Buffer Cache Hit Ratio The 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.
2569
Channel Description
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.
Connection Memory (KB) The total amount of dynamic memory the server is using for maintaining
connections
Database Pages The number of pages in the buffer pool with database content
Number of The number of lock requests that resulted in a deadlock

Deadlocks/Sec
Full Scans/Sec The number of unrestricted full scans. These can be either base-table or
full-index scans.
Lock Requests/Sec The number of new locks and lock conversions requested from the lock
manager
Logins/Sec The total number of logins started
Logouts/Sec The total number of logout operations started
Optimizer Memory (KB) The total amount of dynamic memory the server is using for query
optimization
Page Life Expectancy The number of seconds a page stays in the buffer pool without references
Page Splits/Sec The number of page splits that occur as the result of overflowing index
pages
SQL Cache Memory The total amount of dynamic memory the server is using for the dynamic
(KB) SQL cache
SQL Compilations/Sec The number of SQL compilations per second. Indicates the number of
times the compile code path is entered. Includes compiles because of
recompiles. After the SQL Server user activity is stable, this value
reaches a steady state.
SQL Recompilations/Sec The number of SQL recompiles per second. Counts the number of times
recompiles are triggered. In general, you want the recompiles to be low.
Stolen Pages The number of pages used for miscellaneous server purposes (including
procedure cache)
2570
Channel Description
Table Lock The number of times that locks on a table were escalated
Escalations/Sec
Target Server Memory The total amount of dynamic memory the server can consume
(KB)
Total Server Memory The total amount of dynamic memory that the server is using
(KB)
User Connections The 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.
More
KNOWLEDGE BASE
Why does my WMI Microsoft SQL Server 2005 sensor not work anymore?


2571
7.8.294 WMI Microsoft SQL Server 2008 Sensor
List 2576 .

Remarks
2572
Remark Description
SQL database.
probe device.
you add the sensor:
§ wmisqlserversensor2008
2573
SQL Server Settings
SQL Server Settings
Setting Description

automatic mode.
name above.
instance.
scanning interval.
2574
Setting Description
master node.
Setting Description
you select here.
second.
second).
pages.
channels.
2575
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2576
Channel Description
wait
throughput.
SQL Server.
connections

Deadlocks/Sec
full-index scans.
manager
optimization
pages
2577
Channel Description
(KB) SQL cache
procedure cache)
Escalations/Sec
(KB)
(KB)
More
KNOWLEDGE BASE


2578
List 2583 .

Remarks
2579
Remark Description
SQL database.
probe device.
you add the sensor:
2580
SQL Server Settings
SQL Server Settings
Setting Description

automatic mode.
name above.
instance.
scanning interval.
2581
Setting Description
master node.
Setting Description
you select here.
second.
second).
pages.
channels.
2582
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2583
Channel Description
wait
throughput.
SQL Server.
connections

Deadlocks/Sec
full-index scans.
manager
optimization
pages
2584
Channel Description
(KB) SQL cache
procedure cache)
Escalations/Sec
(KB)
(KB)
More
KNOWLEDGE BASE


2585
List 2590 .

Remarks
2586
Remark Description
SQL database.
probe device.
you add the sensor:
2587
SQL Server Settings
SQL Server Settings
Setting Description

automatic mode.
name above.
instance.
scanning interval.
2588
Setting Description
master node.
Setting Description
you select here.
second.
second).
pages.
channels.
2589
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2590
Channel Description
wait
throughput.
SQL Server.
connections

Deadlocks/Sec
full-index scans.
manager
optimization
pages
2591
Channel Description
(KB) SQL cache
procedure cache)
Escalations/Sec
(KB)
(KB)
More
KNOWLEDGE BASE


2592
List 2598 .

Remarks
2593
Remark Description
SQL database.
probe device.
you add the sensor:
2594
SQL Server Settings
SQL Server Settings
Setting Description


automatic mode.
name above.
instance.
2595
Setting Description
scanning interval.
master node.
Setting Description
you select here.
second.

second).
pages.
channels.
2596
Setting Description

Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
2597
Channel List
Channel Description
wait
throughput.
SQL Server.
connections

Deadlocks/Sec
full-index scans.
manager
optimization
2598
Channel Description
pages
(KB) SQL cache
procedure cache)
Escalations/Sec
(KB)
(KB)
More
KNOWLEDGE BASE


2599
List 2604 .

Remarks
2600
Remark Description
SQL database.
probe device.
you add the sensor:
2601
SQL Server Settings
SQL Server Settings
Setting Description

automatic mode.
name above.
instance.
scanning interval.
2602
Setting Description
master node.
Setting Description
you select here.
second.
second).
pages.
channels.
2603
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2604
Channel Description
wait
throughput.
SQL Server.
connections

Deadlocks/Sec
full-index scans.
manager
optimization
pages
2605
Channel Description
(KB) SQL cache
procedure cache)
Escalations/Sec
(KB)
(KB)
More
KNOWLEDGE BASE


2606
List 2611 .

Remarks
2607
Remark Description
SQL database.
probe device.
you add the sensor:
2608
SQL Server Settings
SQL Server Settings
Setting Description

automatic mode.
name above.
instance.
scanning interval.
2609
Setting Description
master node.
Setting Description
you select here.
second.
second).
pages.
channels.
2610
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2611
Channel Description
wait
throughput.
SQL Server.
connections

Deadlocks/Sec
full-index scans.
manager
optimization
pages
2612
Channel Description
(KB) SQL cache
procedure cache)
Escalations/Sec
(KB)
(KB)
More
KNOWLEDGE BASE


2613
7.8.300 WMI Remote Ping Sensor
The WMI Remote Ping sensor remotely connects to a Windows system via Windows Management
Instrumentation (WMI) and performs an Internet Control Message Protocol (ICMP) echo request ("ping")
from this device to a specified target.
WMI Remote Ping Sensor
List 2618 .

§ Dutch: WMI Remote Ping
§ French: Ping distant (WMI)
§ German: WMI Remote Ping
§ Japanese: WMI Ping

§ Portuguese: Ping remoto (WMI)
§ Russian: WMI
§ Simplified Chinese: WMI Ping
§ Spanish: Ping remoto (WMI)
Remarks
2614
Remark Description
probe device.
you add the sensor:
§ pingsensor
§ remotepingsensor
§ wmisensor
§ wmipingsensor
2615
WMI Remote Ping Configuration
WMI Remote Ping Configuration
Setting Description
Target Enter the Domain Name System (DNS) name or IP address of the target
device that you want to ping. The sensor remotely connects to its parent
device via WMI. Then it performs a ping request from this remote device to
the target device or server. Enter a string.
Debug Options
Debug Options
Setting Description
2616
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
2617
Channel List
Channel Description
Ping Time The ping time from the remote device to the target device
More
KNOWLEDGE BASE


2618
7.8.301 WMI Security Center Sensor
The WMI Security Center sensor monitors the security status of a Windows client system via Windows
Management Instrumentation (WMI). It can monitor all security products that are controlled by Windows
Security Center / Windows Action Center.
WMI Security Center Sensor
List 2623 .

§ Dutch: WMI Security Center
§ French: Centre de sécurité (WMI)
§ German: WMI Sicherheits-Center
§ Japanese: WMI
§ Portuguese: Centro de segurança (WMI)
§ Russian: WMI
§ Spanish: Centro de seguridad (WMI)
Remarks
2619
Remark Description
Windows version § This sensor requires at least Windows Vista on the target system.
§ This sensor does not run on Windows Server operating systems

(Windows Server 2003, 2008, 2012, 2016) because the Windows
Security Center / Windows Action Center is only available on client
Windows versions.
channels.
probe device.
Add Sensor
WMI Security Center Specific
Setting Description
Security Center Product Select the security center products that you want to monitor. PRTG
creates one sensor for each product that you select.
You see a list showing the Name and Type of all security products that
the sensor finds in the Windows Security Center on the target device. If
there are no products, you see a corresponding message.
2620
you add the sensor:
§ WMISecurityCenter
Setting Description
Display Name The display name of the security center product that this sensor
monitors.
Type The type of the security center product that this sensor monitors.
Debug Options
Debug Options
2621
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description



other above.
2622
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Status The status code of the security product
§ Up status: Running - Up To Date (status code 4)
§ Warning status: Running - Out Of Date (status code 2)
§ Down status: Not Running - Out Of Date (status code 1), Not Running -
Up To Date (status code 3), Unknown (status code 0)
More
KNOWLEDGE BASE


2623
7.8.302 WMI Service Sensor
The WMI Service sensor monitors a Windows service via Windows Management Instrumentation (WMI).
After creation, the sensor shows the Down status if the service does not run.
WMI Service Sensor
List 2628 .

§ Dutch: WMI Service
§ French: Service (WMI)
§ German: WMI Dienst
§ Japanese: WMI
§ Portuguese: Serviço (WMI)
§ Russian: WMI
§ Spanish: Servicio (WMI)
Remarks
2624
Remark Description
Add Sensor dialog § The name and description of the service in the Add Sensor dialog
appear in the language of the device's Windows installation.
probe device.
you add the sensor:
§ servicesensor
§ wmiservicesensor
2625
WMI Service Monitor
WMI Service Monitor
Setting Description
If Service is Not Running Select whether you want PRTG to start or restart the service if it is
stopped or paused:
§ Start/Restart service (default): PRTG tries to start the service if it is not
running when the device is scanned. In combination with a change
trigger, you can use this mechanism to trigger a notification whenever
PRTG (re)starts the service.
§ Do not start/restart service: PRTG does not automatically start any
service on the device.
If you select the Start/Restart service (default) option and the sensor
detects that the service does not run, PRTG tries to restart the
service during this scan and postpones the next sensor scan for one
interval. With the following scan, the sensor checks if the service runs
now. If starting the service was not successful or if the service fails again,
the sensor shows the Down status and does not try to start the service
again. If the service runs after a (re)start attempt, the sensor continues
monitoring as usual.
If Service is Restarted This setting is only visible if you select Start/Restart service (default)
above.
Define what the sensor does if PRTG restarts the service:


change.
Extended Monitoring Select whether you want to monitor CPU usage and other performance
counters:
2626
Setting Description
§ Only check if the service is running (default): PRTG only monitors the
channel Sensor Execution Time.
§ Monitor other performance counters: PRTG also monitors other
performance counters.
Extended monitoring might cause a class not found error on some

Windows systems.
Service The Windows service that this sensor monitors.
Description The description of the Windows service that this sensor monitors.
master node.
Sensor Display
Sensor Display
Setting Description
2627
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description

Enable Monitor other performance counters in the sensor settings to
show this parameter.
Handles The number of handles

2628
Channel Description
Pagefile Usage The pagefile usage

Sensor Execution Time The execution time of the monitoring request
Threads The number of threads

Working Set The working set

More
KNOWLEDGE BASE

2629
7.8.303 WMI Share Sensor
The WMI Share sensor monitors a shared resource on a Windows system via Windows Management
You can set the sensor to the Down status for different share status messages.
WMI Share Sensor
List 2636 .

§ Dutch: WMI Share
§ French: Partage (WMI)
§ German: WMI Freigabe
§ Japanese: WMI
§ Portuguese: Compartilhamento (WMI)
§ Russian: WMI
§ Spanish: Recurso compartido (WMI)
Remarks
2630
Remark Description
LanmanServer service § To provide any shares, the LanmanServer "Server" Windows service
must run on the target system. If it does not run, there are no shares
and you see a No Share available message.
probe device.
you add the sensor:
§ wmisharesensor
2631
WMI Shared Resource
WMI Shared Resource
Setting Description
Shared Resource Information about the shared resource that this sensor monitors.
Description The description of the shared resource that this sensor monitors.
Type The type of the shared resource that this sensor monitors.
TypeID The typeID of the shared resource that this sensor monitors.
Trigger Down Status on Following Conditions

Select under which conditions the sensor shows the Down status. As long as the share returns OK, the
sensor status shows the Up status. Enable the check box in front of the respective line to select a Down
condition. Select none, one, or several of the following conditions.
If the sensor is in the Down status, it does not record any data in any of its channels.
2632
Trigger Dow n Status on Follow ing Conditions
Condition Description
Error Set the sensor to the Down status if the share returns an error status. A
share in this status is not operational.
This condition is enabled by default.
Degraded Set the sensor to the Down status if the share returns a degraded status.
A share in this status is still operational.
Unknown Set the sensor to the Down status if the share returns an unknown
status.
2633
Condition Description
Pred Fail Set the sensor to the Down status if the share returns a predicted fail
status. This indicates that an element works properly but predicts a
failure (for example, a SMART-enabled hard drive). A share in this status
is still operational.
Starting Set the sensor to the Down status if the share returns a starting status. A
share in this status is not operational.
Stopping Set the sensor to the Down status if the share returns a stopping status.
A share in this status is not operational.
Service Set the sensor to the 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 device that this sensor monitors.
Not all such work is done online, but the managed element is neither OK
nor has one of the other states. A share in this status is not operational.
Stressed Set the sensor to the Down status if the share returns a stressed status.
Nonrecover Set the sensor to the Down status if the share returns a non recover
status.
NoContact Set the sensor to the Down status if the share returns a no contact
status.
LostComm Set the sensor to the Down status if the share returns a lost
communication status.
Debug Options
Debug Options
2634
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description



other above.
2635
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Available The availability of the share

More
KNOWLEDGE BASE


2636
7.8.304 WMI SharePoint Process Sensor
The WMI SharePoint Process sensor monitors a Microsoft SharePoint server via Windows Management
WMI SharePoint Process Sensor
List 2640 .

§ Dutch: WMI SharePoint Proces
§ French: SharePoint processus (WMI)
§ German: WMI SharePoint-Prozess
§ Japanese: WMI SharePoint
§ Portuguese: Processo SharePoint (WMI)
§ Russian: SharePoint WMI

§ Simplified Chinese: WMI SharePoint
§ Spanish: Proceso SharePoint (WMI)
Remarks
2637
Remark Description
probe device.
you add the sensor:
§ wmiprocesssensor
§ wmisharepointprocesssensor
WMI Process Monitor
WMI Process Monitor
2638
Setting Description
SharePoint Process The name of the SharePoint process that this sensor monitors.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description
2639
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Active Threads The number of active threads
Current Page Requests The number of current page requests

2640
Channel Description
Executing SQL Queries The number of SQL queries being executed
Global Heap Size The global heap size
Object Cache Always The object cache always live size

Live Size
Template Cache Size The template cache size
More
KNOWLEDGE BASE


2641
7.8.305 WMI Storage Pool Sensor
The WMI Storage Pool sensor monitors a storage pool via Windows Management Instrumentation (WMI).
WMI Storage Pool Sensor
List 2645 .

§ Dutch: WMI opslagpool
§ French: Pool de stockage (WMI)
§ German: WMI Speicherpool
§ Japanese: WMI
§ Portuguese: Pool de armazenamento (WMI)
§ Russian: WMI
§ Spanish: Grupo de almacenamiento (WMI)
Remarks
2642
Remark Description
Windows version § This sensor supports Windows versions as of Windows 10 or Windows

Server 2016 on the target system.
probe device.
you add the sensor:
§ storagepoolsensor
§ wmistoragepoolsensor
2643
WMI Storage Pool Specific
WMI Storage Pool Specific
Setting Description
Friendly Name The user-friendly name for the storage pool that this sensor monitors.
Debug Options
Debug Options
Setting Description
master node.
2644
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Inherited Settings
Channel List
2645
Channel Description


Operational Status The operational status

§ Up status: OK
§ Unknown status: Starting
More
KNOWLEDGE BASE


2646
7.8.306 WMI Terminal Services (Windows 2008+) Sensor
The WMI Terminal Services (Windows 2008+) sensor monitors the number of sessions on a Windows
Terminal Services (Remote Desktop Services) server via Windows Management Instrumentation (WMI).
The sensor supports Windows 2008 R2 and later.
WMI Terminal Services (Window s 2008+) Sensor
List 2650 .

§ Dutch: WMI Terminal Services (Windows 2008+)
§ French: Windows (2008+) Terminal Services (WMI)
§ German: WMI Terminaldienste (Windows 2008+)
§ Japanese: WMI ( Windows 2008 )

§ Portuguese: Serviços de terminal (Windows 2008+) (WMI)
§ Russian: WMI (Windows 2008 )

§ Simplified Chinese: WMI (Windows 2008+)
§ Spanish: Terminal Services (Windows 2008+) (WMI)
Remarks
2647
Remark Description
probe device.
you add the sensor:
§ wmiterminalservicessensor
Debug Options
Debug Options
2648
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description


other above.
2649
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Active Sessions The number of active sessions: sessions with a logged in user, including
used published applications
Total Sessions The total number of sessions (including inactive sessions): inactive
sessions can be sessions with a disconnected user that has not logged
out or system services using a session
For the Total Sessions channel, the sensor returns the number of
active and inactive sessions, plus two additional sessions: one for
the console, and one for the services. So, the number of total sessions
might actually be higher than expected.
More
KNOWLEDGE BASE

2650
2651
7.8.307 WMI Terminal Services (Windows XP/Vista/2003) Sensor
The WMI Terminal Services (Windows XP/Vista/2003) sensor monitors the number of sessions on a
Windows Terminal Services (Remote Desktop Services) server via Windows Management
The sensor supports Windows XP, Vista, or 2003.
WMI Terminal Services (Window s XP/Vista/2003) Sensor
List 2655 .

§ Dutch: WMI Terminal Services (Windows XP/Vista/2003)
§ French: Windows (XP/Vista/2003) Terminal Services (WMI)
§ German: WMI Terminaldienste (Windows XP/Vista/2003)
§ Japanese: WMI ( Windows XP/Vista/2003)

§ Portuguese: Serviços de terminal (Windows XP/Vista/2003) (WMI)
§ Russian: WMI (Windows XP/Vista/2003)

§ Simplified Chinese: WMI (Windows XP/Vista/2003)
§ Spanish: Terminal Services (Windows XP/Vista/2003) (WMI)
Remarks
2652
Remark Description
probe device.
you add the sensor:
§ wmiterminalservicessensor
Debug Options
Debug Options
2653
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description


other above.
2654
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Active Sessions The number of active sessions: sessions with a logged in user, including
used published applications
Total Sessions The total number of sessions (including inactive sessions): inactive
sessions can be sessions with a disconnected user that has not logged
out or system services using a session
For the Total Sessions channel, the sensor returns the number of
active and inactive sessions, plus two additional sessions: one for
the console, and one for the services. So, the number of total sessions
might actually be higher than expected.
More
KNOWLEDGE BASE

2655
2656
7.8.308 WMI UTC Time Sensor
The WMI UTC Time sensor monitors the Coordinated Universal Time (UTC) time of a target device via
WMI UTC Time Sensor
List 2660 .

§ Dutch: WMI UTC Tijd
§ French: Heure UTC (WMI)
§ German: WMI UTC-Zeit
§ Japanese: WMI UTC
§ Portuguese: Tempo UTC (WMI)
§ Russian: WMI UTC

§ Simplified Chinese: WMI UTC
§ Spanish: Tiempo UTC (WMI)
Remarks
2657
Remark Description
probe device.
you add the sensor:
§ wmiutctimesensor
Debug Options
Debug Options
2658
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description



other above.
2659
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description
Difference The time difference between the PRTG core server system time and the
target device
UTC Time The UTC time of the target device

More
KNOWLEDGE BASE


2660
7.8.309 WMI Vital System Data v2 Sensor
The WMI Vital System Data v2 sensor monitors vital system parameters via Windows Management
The sensor can monitor CPU, thread, memory, network, or pagefile, for example.
WMI Vital System Data v2 Sensor
List 2665 .

§ Dutch: WMI Vitale Systeem Gegevens V2
§ French: Données système vitales v2 (WMI)
§ German: WMI Wichtige Systemdaten v2
§ Japanese: WMI ( V2)

§ Portuguese: Dados vitais do sistema (WMI) v2
§ Russian: WMI v2
§ Simplified Chinese: WMI v2
§ Spanish: Datos vitales de sistema (WMI) v2
Remarks
2661
Remark Description
probe device.
Add Sensor
Setting Description
Performance Counter Select the performance counters that you want to monitor. PRTG creates
one sensor for each counter that you select.
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 the name and
instance description (if available).
Choose from the following counters:
§ CPU
§ Thread
§ Memory
§ Network
§ Pagefile
2662
you add the sensor:
§ wmivitalsystemdatasensor
Vital System Data Readings Accessible Using WMI
Vital System Data Readings Accessible Using WMI
Setting Description
device.
2663
Setting Description
device.
device.
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
2664
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Bytes In All Heaps The CLR memory bytes in all heaps
Bytes Total/Sec The total number of bytes per second
Committed The committed bytes
Excepts The number of thrown CLR exceptions
2665
Channel Description
Free Physical Memory The free physical memory
Packets Outbound Errors The number of outbound packet errors
Queue Length The CPU queue length
Total Visible Memory The total visible memory
User Time The CPU user time (%)
More
KNOWLEDGE BASE


2666
7.8.310 WMI Volume Sensor
The WMI Volume sensor monitors the free disk space on a drive, logical volume, or mount point via
The sensor does not support disk drive management.
The 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 (NTFS), and might have a drive letter
assigned to it. One hard disk can have multiple volumes, and volumes can span multiple physical disks.
WMI Volume Sensor
List 2671 .

§ Dutch: WMI Volume
§ French: Espace disponible du disque (WMI)
§ German: WMI Datenträger
§ Japanese: WMI
§ Portuguese: Volume (WMI)
§ Russian: WMI
§ Spanish: Volumen (WMI)
2667
Remarks
Remark Description
Windows version § This sensor does not support Windows XP and earlier.
probe device.
you add the sensor:
§ diskspacesensor
§ wmivolumesensor
2668
WMI Volume Specific
WMI Volume Specific
Setting Description
DeviceID The unique identifier of the volume (drive, logical volume, mount point) that
Drive Type The type of disk drive that this sensor monitors.
ID Selection Define how the sensor identifies the volume:

§ Use system device ID (default): Use the system device ID. This is
usually the best option for this sensor because the device ID does not
change when the volume is renamed.
§ Use drive letter: Use the drive letter. In a Microsoft cluster environment,
the device ID changes when the cluster is switched to a different node.
We recommend that you select this option in this case.
Drive Letter This setting is only visible if you select Use drive letter above.
Enter the letter of the drive that you want to monitor followed by a colon,
for example, C:
Debug Options
Debug Options
2669
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description



other above.
2670
Setting Description
procedure to do so.
Inherited Settings
Channel List
Channel Description

More
KNOWLEDGE BASE


2671
7.8.311 WSUS Statistics Sensor
The WSUS Statistics sensor monitors various statistics on a Windows Server Update Services (WSUS)
server via Windows Management Instrumentation (WMI).
WSUS Statistics Sensor
List 2676 .

§ Dutch: WSUS Statistieken
§ French: WSUS statistiques
§ German: WSUS-Statistiken
§ Japanese: WSUS
§ Portuguese: Estatísticas WSUS
§ Russian: WSUS
§ Simplified Chinese: WSUS
2672
§ Spanish: Estadísticas WSUS
Remarks
Remark Description
WSUS 3.0 § This sensor requires the Microsoft WSUS 3.0 Administration Console
Administration Console on the probe system. In a cluster, it must be installed on every cluster
node.
system.
does PRTG require?
Knowledge Base § Knowledge Base: Can I encrypt connections to my WSUS server?
probe device.
2673
you add the sensor:
§ ptfsensor
Sensor Settings
Sensor Settings
Setting Description
WSUS Server Port Enter the number of the port the WSUS server service runs on. The
default value is 8530. Enter an integer.
Connection Security Define if you want to use Secure Sockets Layer (SSL)/Transport Layer
Security (TLS) for the connection to the WSUS server or if you prefer
unsecured connections:
§ Use SSL/TLS
§ Do not use connection security (default)
If you want to use SSL/TLS, you must configure the WSUS server
accordingly. For more information, see the Knowledge Base: Can I
encrypt connections to my WSUS server?
2674
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

2675
Setting Description

other above.
procedure to do so.
Inherited Settings
Channel List
Channel Description
Approved Updates The number of approved updates
Computers Having The number of computers that have update errors

Update Errors
Computers Needing The number of computers that need updates

Updates
Computers Not The number of computers that have not synchronized for seven days
Synchronized for 7 Days
Computers Registered The number of computers that are registered
2676
Channel Description
Computers Up To Date The number of computers that are up to date
Declined Updates The number of updates that were declined
Expired Updates The number of updates that are expired
Not Approved Critical Or The number of critical or security updates that were not approved
Security Updates
Not Approved Updates The number of updates that were not approved
Total Updates The total number of updates
Unapproved, Needed The number of updates that are unapproved but needed
Updates
Updates Needed By The number of updates that computers need

Computers
Updates Needing Files The number of updates that need files
Updates Up To Date The number of updates that are up to date
Updates With Client The number of updates that have client errors
Errors
Updates With Server The number of updates that have server errors
Errors
Updates With Stale The number of updates that have stale update approvals
Update Approvals
WSUS Infrastructure The number of WSUS infrastructure updates that were not approved for
Updates Not Approved installation
For Install
More
KNOWLEDGE BASE
2677
Can I encrypt connections to my WSUS server?


2678
7.8.312 Zoom Service Status Sensor
The Zoom Service Status sensor monitors the overall status of Zoom groups based on the status of their
components.
Zoom Service Status Sensor
List 2682 .

§ Dutch: Zoom Service Status
§ French: Zoom statut des services
§ German: Zoom-Dienste-Status
§ Japanese: Zoom
§ Portuguese: Status do serviço do Zoom
§ Russian: Zoom
§ Simplified Chinese: Zoom
§ Spanish: Estado del servicio de Zoom
2679
Remarks
Remark Description
Internet proxies § This sensor is not compatible with internet proxies.
channels.
you add the sensor:
§ zoom
§ zoomsensor
2680
Sensor Display
Sensor Display
Setting Description


other above.
procedure to do so.
Debug Options
Debug Options
2681
Setting Description
Inherited Settings
Channel List
Channel Description
APAC - Zoom Phone The status of the group 'APAC - Zoom Phone' based on its components
§ Warning status: Degraded Performance, Under Maintenance
§ Down status: Major Outage, Partial Outage
AUSTRALIA - Zoom The status of the group 'AUSTRALIA - Zoom Phone' based on its
Phone components
Conference Room The status of the group 'Conference Room Connector' based on its
Connector components
2682
Channel Description
EMEA - Zoom Phone The status of the group 'EMEA - Zoom Phone' based on its components
Global - Zoom Contact The status of the group 'Global - Zoom Contact Center' based on its
Center components
Global - Zoom Phone The status of the group 'Global - Zoom Phone' based on its components
HONG KONG/CHINA - The status of the group 'HONG KONG/CHINA - Zoom Phone' based on its
Zoom Phone components
JAPAN - Zoom Phone The status of the group 'JAPAN - Zoom Phone' based on its components
LATIN AMERICA - Zoom The status of the group 'LATIN AMERICA - Zoom Phone' based on its
Phone components
2683
Channel Description
Live Streaming The status of Live Streaming

NORTH AMERICAS - The status of the group 'NORTH AMERICAS - Zoom Contact Center'
Zoom Contact Center based on its components
NORTH AMERICAS - The status of the group 'NORTH AMERICAS - Zoom Phone' based on its
Zoom Phone components
Zoom Chat The status of the group 'Zoom Chat' based on its components
Zoom Community The status of Zoom Community

Zoom Developer Platform The status of the group 'Zoom Developer Platform' based on its
components
2684
Channel Description
Zoom Events The status of Zoom Events

Zoom IQ for Sales The status of the group 'Zoom IQ for Sales' based on its components
Zoom Meetings The status of the group 'Zoom Meetings' based on its components
Zoom Room The status of the group 'Zoom Room' based on its components
Zoom Subscription The status of Zoom Subscription

Zoom Support The status of the group 'Zoom Support' based on its components
Zoom Video SDK The status of the group 'Zoom Video SDK' based on its components
2685
Channel Description
Zoom Video Webinars The status of the group 'Zoom Video Webinars' based on its components
Zoom Website The status of the group 'Zoom Website' based on its components
Zoom Whiteboard The status of Zoom Whiteboard

Zoom Workspace The status of Zoom Workspace Reservation

Reservation
More
KNOWLEDGE BASE

2686
7.9 Additional Sensor Types (Custom Sensors)
You can create and use your own custom sensors in PRTG to extend the standard sensor set. You can
create your own sensors by using Windows Management Instrumentation Query Language (WQL), visual
basic scripting, PowerShell, batch scripting, Structured Query Language (SQL) queries, by compiling an
.exe file, by running Python scripts, or by translating JavaScript Object Notation (JSON) and Extensible
Markup Language (XML) responses of a Representational State Transfer (REST) application
programming interface (API) into sensor values.
You cannot use custom sensors on hosted probes in PRTG Hosted Monitor (except SSH sensors).
If you want to use custom sensors, add them to a remote probe device.
Basics
For a general introduction, see the sections about EXE/Script sensors and section Custom Sensors 3142 ,
which contain details about the necessary return format for these sensors.
WMI Custom sensors allow you to execute WQL requests. Additionally, some types of SQL
sensors execute script files with SQL queries.
Custom Sensors in PRTG

After you install PRTG, you can find a selection of custom EXE/Script, Python, and WMI WQL script
sensors in the PRTG program directory 3218 , as well as scripts with SQL queries for specific database
sensors, REST configuration files in the JSON template (*.template) format for the REST Custom sensor,
and .hl7 message files for the HL7 sensor. Many of the files are sample projects that you can edit and
improve for your needs.
Subfolder of the PRTG Custom Sensors

Program Directory
\Custom Sensors\EXE The following custom sensors are available by default:

§ Demo Batchfile - Returns 200.bat
§ Demo Batchfile - Set sensorstate to error.bat
§ Demo Batchfile - Set sensorstate to warning.bat
§ Demo Cmd - Returns 200.cmd
§ Demo 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 - Powershell Version.ps1
§ Demo Powershell Script - Returns a fixed integer.ps1
§ Demo Powershell Script - Returns a random integer.ps1
2687
Program Directory
§ Demo Powershell Script - Returns Random Integer and Warnings.ps1
§ Demo VBScript - InterruptsPerSec via WMI.vbs
§ Demo VBScript - Multiplies two integers(2 parameters).vbs
§ Demo VBScript - Returns a fixed float value.vbs
§ Demo VBScript - Returns a fixed integer.vbs
§ Demo VBScript - Returns a random value.vbs
§ Demo VBScript - Returns number of svchost processes.vbs
§ Demo VBScript - Returns user of process.vbs
§ Demo VBScript - Returns warning depending on number of svchost

processes.vbs
§ Demo VBScript - Timezone via WMI.vbs
§ Demo VBScript - UTCTime via WMI.vbs
§ Load_Test_CPU_1_Mio_Primes.exe
§ Load_Test_CPU_10_Mio_Primes.exe
§ Load_Test_Disk_Write_Read_1000_files.exe
§ Load_Test_Disk_Write_Read_10000_files.exe
§ Load_Test_Memory_Allocate_And_Free_400MB.exe
To create a new sensor based on one of these files, create a new

EXE/Script sensor and choose the respective file from the EXE/Script list
in the sensor settings.
We recommend that you not edit the demo files. Create your own
new files and make sure to give them unique names that do not start
with Demo, for example.
\Custom The following custom sensor is available by default:

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

EXE/Script Advanced sensor and choose the respective file from the
EXE/Script list in the sensor settings.
\Custom Sensors\hl7 The following custom sensors are available by default:

§ ADT_A08.hl7
§ ORM_O01.hl7
2688
Program Directory
Each file contains an HL7 message that is conform to the HL7 message
format. To create a new sensor based on one of these files, create a new
HL7 sensor and choose the respective file from the HL7 Messages list in
the sensor settings. You can override certain message headers in the
files via the sensor settings.
\Custom Sensors\python The following custom sensor is available by default:

§ sensor_example.py
This Python example script only returns fixed values in two channels to
demonstrate the usage. To create a new sensor based on this file, create
a new Python Script Advanced sensor and choose the file from the Script
list in the sensor settings.
\Custom Sensors\rest The following custom sensors are available by default:

§ kemp.loadbalancer.template: maps values returned by the RESTful API
of a KEMP load balancer to channels, for example, CPU usage,
memory usage, traffic
§ prtg-sensor-stats.template: maps values returned by the PRTG API to
channels that show the count of each sensor status on the local probe
§ windows.docker.container.stats.template: maps values returned by the
Docker Engine API to channels, for example, CPU usage, memory
usage, traffic, input/output (I/O)
§ wunderground.template: maps values returned by the Weather
Underground API to channels, for example, temperature, dew point,
pressure, wind speed, wind direction
To create a new sensor based on one of these files, create a new REST
Custom sensor on the device that provides the REST API and choose the
file from the REST Configuration list in the sensor settings.
\Custom The following example scripts are available by default:

Sensors\scripts\example
§ dice_roll.py
s\python
§ dropbox_space_free.py
§ hybrid_parameters_ping.py
§ remote_ssh_linux_network.py
§ remote_ssh_linux_system_load.py
To use the example scripts, copy them to the \Custom Sensors\scripts

subfolder of the PRTG program directory. To create a new sensor based
on one of these files, create a new Script v2 sensor and choose one or
more Python scripts from the list in the script specific settings. PRTG
creates one sensor for each script that you select.
2689
Program Directory
\Custom The following custom sensor is available by default:

Sensors\sql\[dbms]
§ Demo Serveruptime.sql
You can find this demo SQL query script in each subfolder for each
supported database management system (DBMS): \adosql, \mssql,
\mysql, \oracle, \postgresql
To create a new sensor that uses one of the scripts in the dbms folders,
create the according sensor (see above for supported sensors 2687 ) and
choose the respective file from the SQL Query File list in the sensor
settings.
\Custom Sensors\WMI The following custom sensors are available by default:

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
Custom sensor and choose the respective file from the WQL File list in
the sensor settings.
Download Custom Sensors

Good resources to find custom sensors that other users and we from Paessler share are the PRTG
Sensor Hub and our Knowledge Base. In the Knowledge Base, search for the tag custom-script-exe to
find a lot of custom sensors.
More
KNOWLEDGE BASE
Guide for PowerShell-based custom sensors

Custom sensors
§ https://kb.paessler.com/en/tags/custom-script-exe
How can I share my self-written PRTG script/program with other PRTG users?
2690
I want to use the Script v2 sensor example scripts. What do I need to know?
PAESSLER WEBSITE
You can find useful scripts for sensors in the PRTG Sensor Hub
2691
7.10 Channel Settings
A sensor has one or more channels in which it handles the actual monitoring data. In the channel
settings, you can define how to display the data from the sensor's different channels displayed in graphs,
gauges, and tables. Additionally, the channel data can determine the sensor status 184 . Use the limit
settings to define desired sensor states for values.
On the sensor's Overview tab, click below a gauge to change the channel's settings. Click below a
gauge to make this channel the primary channel of the selected sensor.
You can also open the settings of a channel by clicking in the channels data table.
For lookup 3186 channels, we recommend that you stay below 120 lookup values to get expressive
gauges. For non-primary lookup channels, the upper limit is around 40 lookup values.
The Gear Icon of an SNMP Traffic Total Channel to Open Channel Settings
The available options are nearly the same for all sensors. An exception applies to the Downtime channel,
which PRTG automatically calculates and which does not offer all settings. Channels with absolute
values additionally have an option to define the Value Mode. Custom channels have a Lookups and
Limits setting to distinguish between alerting by lookups or numeric limits.
You can choose a different channel via the dropdown list at the top of the channel settings list.
2692
Channel Settings for a Disk Sensor
Edit Channel
Setting Description
Name Enter a name for the channel. The name appears in graphs and tables.
You can automatically add the sensor's ID to the name by using the
placeholder [#id].
You cannot edit the name for script sensors after sensor creation.
2693
Setting Description
Unit This setting is only visible for custom sensors.
Enter the unit for the values that this sensor returns. Enter a string.
Scaling Multiplication This setting is only visible for channels with a custom unit.
If you want to multiply the received raw data by a certain value, enter the
multiplier. Otherwise, use the default value 1 to not change the received
value. Enter an integer.
For example, the following sensors provide the scaling factor for received
values with custom units in their settings:
§ Sensor Factory (you can use multiplication and division in the channel
definition)
§ SNMP APC Hardware
§ SNMP Custom
§ WMI Custom
If the channel uses lookups, the scaling factor does not modify the
values that are defined in the lookups. Any applied lookup always
uses the raw value as it is retrieved from the target device. If you use a
scaling factor for such a channel, you notice the scaling in data graphs,
but the channel value appears unmodified in data tables.
Scaling Division This setting is only visible for channels with a custom unit.
If you want to divide the received raw data by a certain value, enter the
divisor here. Otherwise, use the default value 1 to not change the received
value. Enter an integer.
For example, the following sensors provide the scaling factor for received
values with custom units in their settings:
§ Sensor Factory sensor (you can use multiplication and division in the
channel definition)
§ SNMP APC Hardware sensor
§ SNMP Custom sensor
§ SNMP Dell Hardware sensor
2694
Setting Description
§ WMI Custom sensor
If the channel uses lookups, the scaling factor does not modify the
values that are defined in the lookups. Any applied lookup always
uses the raw value as it is retrieved from the target device. If you use a
scaling factor for such a channel, you notice the scaling in data graphs,
but the channel value appears unmodified in data tables.
ID Shows the ID of the channel. PRTG uses it for unique identification. For
example, you need the ID for Sensor Factory sensors.
There are a few special, fixed channel IDs.
§ -1 is for sum channels of traffic sensors (for example, of the SNMP
Traffic sensor).
§ -4 is for the Downtime channel (you can use it, for example, for an
uptime percentage calculation in a Sensor Factory sensor).
§ -2 (coverage) and -3 (error) are internally used.
Limits This setting is not available for custom channels.
Define if you want to set limits for this channel:

§ Disable limits: Do not use the channel data to define the sensor status.
§ Enable alerting based on limits: Define limits for the numeric values that
are returned by the device. The sensor of which this channel is a part of
shows the Warning status or the Down status when limits fall below the
defined value or when limits are exceeded.
The channel can affect the status of the sensor 184 that it is a part of.
By setting limits, you can define when the sensor shows the Warning
status or the Down status, depending on the channel data. For example,
you can use limits to set a traffic sensor (that is usually never in the
Down status) to show the Down status when the monitored values reach
critical limits.
Enable alerting based on limits is not available for the Downtime
channel.
You can show limits in graphs (highlighted in yellow or red) if you
select exactly one channel with a limit in a graph.
Lookups and Limits This setting is only available for custom channels.
Define when the sensor shows the Down status and alerts you, either
based on the lookup definition or based on limits for returned values:
2695
Setting Description
§ Enable alerting based on lookups: Use the lookup definition of the

channel to define the sensor status. Make sure that the channel uses a
proper Lookup if you use this option. Select the lookup file either in the
channel settings or in the sensor settings, depending on the sensor. If
you do not want to use the channel data to define the sensor status,
select None as Lookup.
§ Enable alerting based on limits: Define limits for numeric values

returned by the device. The sensor of which this channel is a part of
shows the Warning status or the Down status when limits fall below the
defined value or when limits are exceeded.
Only the option you choose applies. If you choose limit-based
alerting, errors and warnings that you have defined in the lookup file
do not apply.
Lookup This setting is only visible for custom sensors and if you select lookups-
based alerting.
Select the lookup file that you want to use with this channel.
Do not use this option for sensors that provide the unit Lookup in the
sensor settings. The channel setting is overwritten with the next
sensor scan. Define the lookup file that you want to use with this channel
on the Settings tab of the sensor. Select the option Lookup for the setting
Channel #x Unit (where x is the number of the channel) and define the
desired lookup file under Channel #x Lookup. See section Define
Lookups 3186 for affected sensors.
If you choose None, alerting by lookups and limits is disabled and
channels do not appear as lookups. If you want to keep the lookup
representation without alerting, define the states accordingly in the lookup
file.
Upper Error Limit ([unit]) This setting is only visible if you select Enable alerting based on limits
above.
Specify an upper limit for the Down status. If the channel values exceed
this value, the sensor shows the Down status. Enter a valid number into
at least one of the limit fields.
The value that you enter here must match the type of value that the
device returns, either an integer or a float. See also Absolute Values
and Delta Values for Limits 2701 .
While a sensor shows the Down status because of a limit, it still
receives data in its channels.
Upper Warning Limit This setting is only visible if you select Enable alerting based on limits
([unit]) above.
2696
Setting Description
Specify an upper limit for the Warning status. If the channel values
exceed this value, the sensor shows the Warning status. Enter a valid
number into at least one of the limit fields.
Lower Warning Limit This setting is only visible if you select Enable alerting based on limits
([unit]) above.
Specify a lower limit for the Warning status. If the channel values fall
below this value, the sensor shows the Warning status. Enter a valid
number into at least one of the limit fields.
Lower Error Limit ([unit]) This setting is only visible if you select Enable alerting based on limits
above.
Specify a lower limit for the Down status. If the channel values fall below
this value, the sensor shows the Down status. Enter a valid number into
at least one of the limit fields.
While a sensor shows the Down status because of a limit, it still
receives data in its channels.
Error Limit Message This setting is only visible if you select Enable alerting based on limits
above.
Enter an additional message. PRTG adds it to the sensor message when

the sensor shows the Down status. Enter a string or leave the field
empty.
Warning Limit Message This setting is only visible if you select Enable alerting based on limits
above.
Enter an additional message. PRTG adds it to the sensor message when

the sensor shows the Warning status. Enter a string or leave the field
empty.
Graph Rendering Select if you want to show this channel in data graphs:
2697
Setting Description
§ Show in graphs: Sensor graphs contain the data of this channel.
§ Hide in graphs: Sensor graphs do not contain data of this channel.
If you choose to hide this channel in graphs, it also does not appear
in the graphs of reports 2764 or maps 2786 .
For more information about data graphs, see the Knowledge Base:
Table Rendering Select if you want to show this channel in data tables:
§ Show in tables: Sensor data tables contain the data of this channel.
§ Hide in tables: Sensor data tables do not contain the data of this
channel. This option hides the gauge as well, but the channel is still
available in the data table of the sensor's Overview tab.
If you choose to hide this channel in data tables, PRTG also does
not use it for the calculation of the Total channel of a sensor. It also
does not appear in data tables of a report.
For more information about data tables, see the Knowledge Base:
Line Color Select the color of the channel display in graphs:

§ Automatic: PRTG automatically sets the color of this channel in
graphs.
§ Manual: Individually define the color of this channel. You can enter the
desired color code below.
Color (#rrggbb) This setting is only visible if you select Manual above.
Enter a color in hexadecimal notation as in .html and .css files, or choose

a color from the visual color selector. The field with the hexadecimal color
value automatically changes to the color you select.
Line Width Enter the width of the channel line in graphs. Enter an integer in pixels.
The maximum line width is 25, but we recommend that you only use
values between 1 and 7 to get optimal results.
Data This setting is available for most channels. Define how to display data:
§ Display actual values in [unit]: Display the values in the shown unit.
2698
Setting Description
§ Display in percent of maximum: Calculate and show percent values

based on a maximum value. Enter a maximum below.
If you choose this option, you cannot display the data of traffic
sensors as a positive and negative area graph.
If you choose this option, values in the Limits section are counted
as percent values.
Maximum ([unit]) This setting is only visible if you select Display in percent of maximum
above.
Enter a value to use as the maximum. Consider the unit. PRTG

calculates all percent values based on this value. Enter an integer.
Value Mode This setting is only available for channels that return absolute values.
Define which value type you want to display in historic data graphs and
tables:
§ Average: The channel shows average values.
§ Minimum: The channel shows the minimum values.
§ Maximum: The channel shows the maximum values.
This setting is not available for sensors that show difference values,
such as traffic channels.
For more information about value modes, see the Knowledge Base:
What is the Value Mode in channel settings?
Decimal Places Define how many decimal places of the channel's data that you want to
display in graphs and tables:
§ Automatic: PRTG automatically defines how many decimal places to
use for optimal viewing results.
PRTG rounds values between 10 and –10 to two decimal places. It
rounds values that are very close to an integer to the integer, for
example, it rounds 3.001 to 3.
§ All: Display all available decimal places.
§ Custom: Manually define the number of decimal places. If you choose

this option, an additional field appears. Enter an integer.
Spike Filter You can use a spike filter to correct faulty monitoring data. Sometimes,
sensors report values that are enormously high or far too low. This can be
because of an error in data transmission, or because of incompatibilities
of the physical device you are monitoring. This can make graphs
unreadable. A spike filter can compensate for these flaws.
Define if you want to filter incoming data:
2699
Setting Description
§ Disable filtering: Display all data as it is received. Do not filter out

spikes.
§ Enable filtering: Enable a filter to remove spike values. PRTG
disregards values that are above and below a certain limit in the
monitoring data for graphs and tables. Additional fields appear below.
This does not change monitoring data itself but only the
presentation of the data. This setting is valid for all data of this
channel, including historic data.
Use the spike filter with care. For overflow values in SNMP sensors,
check the SNMP Compatibility Options 459 before.
The spike filter option is not available for the channel Downtime.
Spike Filter Max. Value This setting is only visible if you select Enable filtering above.
([unit])
Enter the maximum value to show in the channel data. PRTG disregards
all data above this value in graphs and tables. Enter an integer or leave
the field empty.
Spike Filter Min. Value This setting is only visible if you select Enable filtering above.
([unit])
Enter the minimum value to show in the channel data. PRTG disregards
all data below this value in graphs and tables. Enter an integer or leave
the field empty.
Vertical Axis Scaling Define how to display the vertical axis for the channel in graphs:
§ Automatic scaling: PRTG automatically uses the optimum scaling.

Usually the scaling ranges from the minimum to the maximum value.
PRTG uses one single scale for each unit label only.
§ Manual scaling: Manually define the scaling. Additional fields appear
below. If you define manual axis scaling, it can make low values better
visible in your graph, but it might result in a graph with multiple vertical
axes for the same unit label.
PRTG ignores settings for this option if you select Stack channels on
top of each other under Graph Type on the sensor's Settings tab.
Vertical Axis Maximum This setting is only visible if you select Manual scaling above.
([unit])
Enter the maximum value to use on the vertical axis for the channel.
Enter an integer.
Vertical Axis Minimum This setting is only visible if you select Manual scaling above.
([unit])
2700
Setting Description
Enter the minimum value to use on the vertical axis for the channel. Enter
an integer.
Click OK to save your settings and to close the settings window. Click Apply to save the changed
settings while the Edit Channel window remains open, for example if you want to change the
settings of other channels of the current sensor as well. You can select a different channel via the
dropdown list above the settings. You can close the settings window without saving by clicking Cancel.
If you change any settings and either click Cancel or select a different channel via the dropdown list,
PRTG asks you to confirm this step. Click Save to apply the changes or click Discard Changes to
ignore the changes. PRTG closes the window or shows the settings of the selected channel respectively.
Absolute Values and Delta Values for Limits
The value type that you need to configure for limits depends on the type of data that the channel delivers:
Value Type Description
Absolute values For channels that measure absolute values, for example, for free disk
space, you must set limits with absolute values like 20.
Delta values For channels that measure delta values, that is, measurements per
second (x.xx/sec), you must set delta values according to the formula
number of errors/scanning interval in seconds.
For example, you have an SNMP Traffic sensor and want to receive an alert when the sensor reports
errors:
§ Set the sensor to the Warning status when 1 error occurs.
§ Set the sensor to the Down status when 30 errors occur.
The following screenshot shows how to configure the limits for delta channels. You could set the
following limits for the channel Errors In with a standard scanning interval of 60 seconds:
2701
Setting Channel Limits w ith Delta Values
Because this channel uses per second (delta) measurements, the sensor reports a single error that
occurs over a standard 60-second scanning interval as 0.016 # per second. So the warning limit for one
single error within a scanning interval is 0.1 (errors/sec). To get an alert when there are 30 errors within a
scanning interval, the limit needs to be 0.5 (errors/sec).
2702
If no new errors occur in the next scanning interval, the sensor shows the Up status again. To make
sure that you do not miss any notifications for this sensor, set a notification trigger with 0 seconds.
Channel List Status
Under the channel gauge view on a sensor overview page, there is a channel list showing the active
channels of a sensor listed alphabetically and data from each channel. The Downtime channel never
shows any values. Sensors in the Paused status display No data in place of all data values or remain
blank, regardless of whether there is historic data available. The data values are displayed again when
the sensor is no longer paused.
Channel List
Table Header Description
Channel The name of the channel.
ID The ID of the channel.
Last Value The most recent value of the channel recorded by the sensor.
Minimum The lowest historic value recorded by the sensor.
Maximum The highest historic value recorded by the sensor.
The Minimum and Maximum values remain the same until one of two events take place:
§ The value is replaced by another value that is less than or greater than the original, respectively.
§ A PRTG cache recalculation is prompted, refreshing all values.
These values are cached and are not affected by historic data purges 2909 , making it possible to have a
minimum or maximum value that is no longer recorded in the historic data.
More
KNOWLEDGE BASE

What is the Value Mode in channel settings?

2703
7.11 Notification Triggers Settings
You can use changes in a sensor's status or in the sensor's data to trigger notifications.
Notification Triggers Tab
Although sensors activate notification triggers, you can set notification triggers in the settings of objects
that are higher in the object hierarchy 136 . This allows you to use the inheritance of settings 140 to define
notification triggers for multiple sensors. Objects that inherit notification triggers show them on the
Notification Triggers tab.
For more information, see section Triggers That Can Be Inherited from Parent Objects 2714 .
You can also define notification triggers in libraries 2748 . If a sensor is in a library that has notification
triggers, the sensor shows them on the Notification Triggers tab.
For more information, see section Triggers That Are Defined in Libraries 2715 .
You can also directly edit notification templates on the Notification Triggers tab. To do so, click
next to name of a notification template.
Note
You must take the following four steps to set up and use notifications:
1. Check and set up the notification delivery 2887 settings if you use PRTG Network Monitor. These
settings define how PRTG sends messages.
2. Check and set up notification contacts 2851 for the user accounts. These contacts define the recipients
to which PRTG sends notifications.
2704
3. Check and set up several notification templates 2818 . These templates define the notification methods
and their content.
You can also check or edit notification templates via the Notification Triggers tab. For more
information, see section Notification Triggers Settings 2704 .
4. Check and set up notification triggers settings 2704 for objects. These triggers define when PRTG
sends notifications.
Usually, there are three successive attempts to deliver a notification. If all of these attempts fail, the
notification is lost. To never miss a notification, we recommend that you always set up at least two
notifications with different notification methods for a notification trigger, for example, one email notification
and one SMS notification. If delivery via email fails, PRTG can still notify you via smartphone as a
fallback. For example, use the latency setting of a state trigger 2705 to choose a notification with a
different notification method than in the first trigger condition, or set up a second trigger with a different
notification method for the corresponding object.
For a detailed step-by-step guide, see the Paessler website: How to set up notifications via the
PRTG web interface.
Custom notification scripts are also available in the PRTG Sensor Hub.
Notification Triggers
Select the Notification Triggers tab of an object to add or edit notification triggers. You can set up one or
more of the following notification triggers:
§ State Trigger 2705
§ Speed Trigger 2707
§ Volume Trigger 2710
§ Threshold Trigger 2711
§ Change Trigger 2713
Different options are available for every notification trigger. You see the Type of notification trigger and the
notification Rule that the sensor executes once it activates a notification trigger.
Which notification triggers are available on the Notification Triggers tab depends on the kind of object
you select.
State Trigger
The state trigger performs a notification when a sensor changes its status. Hover over and select Add
State Trigger from the menu to add a new state trigger or click next to a state trigger to change it.
Add State Trigger
2705
PRTG includes a state trigger for the root group 136 by default. This notification trigger performs the
notification Email and push notification to admin if any sensor is in the Down status 184 for at least
10 minutes.
Setting Description
When sensor status is Select the status that triggers a notification:

[...]
§ Down: Trigger a notification if a sensor changes to the Down status.
§ Warning: Trigger a notification if a sensor changes to the Warning

status.
§ Unusual: Trigger a notification if a sensor changes to the Unusual
status.
§ Down (Partial): Trigger a notification if a sensor changes to the Down
(Partial) status. This status is only possible in a failover cluster 132 .
§ Up: Trigger a notification if a sensor changes to the Up status.
§ Unknown: Trigger a notification if a sensor changes to the Unknown

status.
for at least [...] seconds, Enter the time in seconds that PRTG waits before it sends a notification
(latency). This can avoid false alarms if, for example, a sensor changes to
the Down status for only a few seconds. Enter an integer.
Do not define a latency that is shorter than the scanning interval of a
sensor that uses this trigger. The notification trigger might not work
as expected in this case.
perform [...] Select the notification that PRTG sends if the sensor is in the selected
status and if the defined latency is over. You see all notification templates
that you have defined under Setup | Account Settings | Notification
Templates. Use the search box to filter for notification templates. You can
also select no notification to not send a notification in this case.
You can also directly create and use new notification templates by
clicking in the dropdown list.
When sensor status is Enter the escalation latency in seconds that PRTG waits before it sends
[...] for at least [...] an escalation notification. Use this to automatically escalate a notification
seconds if a problem exists for a longer time. Enter an integer.
PRTG automatically fills in the selected status.
perform [...] Select the notification that PRTG sends if the sensor is still in the
selected status and if the defined escalation latency is over. You see all
notification templates that you have defined under Setup | Account
Settings | Notification Templates. Use the search box to filter for
notification templates. You can also select no notification to not send a
notification in this case.
2706
Setting Description
Select a notification with a different delivery method than in the first

trigger condition to make sure that you receive a notification in case
the first notification could not be sent.
and repeat every [...] Enter the interval in minutes after which PRTG sends the escalation
minutes notification again. Enter an integer.
If you enter 0, PRTG does not send the escalation notification again.
When sensor status is Select the notification that PRTG sends if the sensor is no longer in the
no longer [...] , perform selected status and if the defined latency is over. You see all notification
[...] templates that you have defined under Setup | Account Settings |
Notification Templates. Use the search box to filter for notification
templates. You can also select no notification to not send a notification in
this case.
PRTG automatically fills in the selected status.
Click to save your settings or click to undo your changes.
Speed Trigger
The speed trigger performs a notification if the speed that a sensor monitors changes. Hover over and
select Add Speed Trigger from the menu to add a new speed trigger or click next to a speed trigger to
change it.
Add Speed Trigger
Setting Description
When [...] channel Select the channel 2692 whose data PRTG uses for the speed comparison.
At root, probe, group, or device level or in libraries, the following channels
are available:
§ Primary: Use the data of the primary channel of the sensor for the
comparison.
2707
Setting Description
§ Total: Use the data of the Total channel of the sensor for the
comparison.
§ Traffic In: Use the data of the Traffic In channel of the sensor for the
speed comparison.
§ Traffic Out: Use the data of the Traffic Out channel of the sensor for the
speed comparison.
At sensor level, the available channels depend on the type of sensor you
select.
If you set notification triggers at root, probe, group, or device level and
you want to know which sensors the notification triggers apply to,
is [...] Select the condition that triggers the notification:

§ Above: Trigger the notification if the value of the selected channel
exceeds a defined value.
§ Below: Trigger the notification if the value of the selected channel falls
below a defined value.
§ Equal to: Trigger the notification if the value of the selected channel is
the same as a defined value.
§ Not equal to: Trigger the notification if the value of the selected channel
is different than a defined value.
[value] Enter the value to which PRTG compares the channel data. Enter an
integer.
[scale] Select the unit for the [value]:

§ bit
§ kbit
§ Mbit
§ Gbit
§ Tbit
§ Byte
§ KB
§ MB
§ GB
§ TB
The available units depend on the type of sensor you select.
2708
Setting Description
[scale] and [time] define the unit for [value]. If the channel data has a
different unit, PRTG internally converts the values.
[time] Select the time for the scale to create a scale per time unit:
§ second
§ minute
§ hour
§ day
the Down status for only a few seconds.. Enter an integer.
perform [...] Select the notification that PRTG sends if the defined [value], [scale], and
[time] are true and the defined latency is over. You see all notification
templates that you have defined under Setup | Account Settings |
this case.
When condition clears, Select the notification that PRTG sends if the defined [value], [scale], and
perform [...] [time] are no longer true and the defined latency is over. You see all
notification templates that you have defined under Setup | Account
Settings | Notification Templates. Use the search box to filter for
notification templates. You can also select no notification to not send a
notification in this case.
2709
Volume Trigger
The volume trigger performs a notification if a sensor reaches a certain volume in a specific time. Hover
over and select Add Volume Trigger from the menu to add a new volume trigger or click next to a
volume trigger to change it.
Add Volume Trigger
Setting Description
When [...] channel Select the channel whose data PRTG uses for the volume comparison.
are available:
comparison.
comparison.
§ Traffic In: Use the data of the Traffic In channel of the sensor for the
speed comparison.
§ Traffic Out: Use the data of the Traffic Out channel of the sensor for the
speed comparison.
select.
If you set notification triggers at root, probe, group, or device level
and you want to know which sensors the notification triggers apply
to, see section Available Sensor Types 3237 .
reaches [value] Enter the value to which PRTG compares the channel data. Enter an
integer.
[scale] Select the unit for the [value]:

§ Byte
§ KB
§ MB
§ GB
§ TB
per [time], Select the time for the scale to create a scale per time unit:
2710
Setting Description
§ Hour
§ Day
§ Week
§ Month
perform [...] Select the notification that PRTG sends if the defined [value], [scale], and
[time] are true. You see all notification templates that you have defined
under Setup | Account Settings | Notification Templates. Use the search
box to filter for notification templates. You can also select no notification
to not send a notification in this case.
Threshold Trigger
The threshold trigger performs a notification if a sensor reaches specific values. Hover over and select
Add Threshold Trigger from the menu to add a new threshold trigger, or click next to a threshold
trigger to change it.
Add Threshold Trigger
Setting Description
When [...] channel Select the channel whose data PRTG uses for the threshold comparison.
are available:
comparison.
comparison.
select.
2711
Setting Description
The threshold trigger for a Total channel that you define at group or
device level or in libraries only applies to the Total channel of traffic
sensors. This channel has the ID -1. The threshold trigger works with the
Total channel of the following sensors:
§ IPFIX
§ IPFIX (Custom)
§ jFlow v5
§ jFlow v5 (Custom)
§ NetFlow v5
§ NetFlow v5 (Custom)
§ NetFlow v9
§ Packet Sniffer
§ Packet Sniffer (Custom)
§ sFlow
§ sFlow (Custom)
§ SMTP&IMAP Round Trip
§ SMTP&POP3 Round Trip
§ SNMP Traffic (channel Traffic Total)
§ Windows Network Card
If you set notification triggers at root, probe, group, or device level and
you want to know which sensors the notification triggers apply to,
is [...] Select the condition that triggers the notification:

§ Above: Trigger the notification if the value of the selected channel
exceeds a defined value.
§ Below: Trigger the notification if the value of the selected channel falls
below a defined value.
§ Equal to: Trigger the notification if the value of the selected channel is
the same as a defined value.
§ Not equal to: Trigger the notification if the value of the selected channel
is different than a defined value.
[value] Enter the value to which PRTG compares the channel data. Enter values
in the smallest (base) unit that is possible, for example, in bytes,
milliseconds, or percent. Enter an integer.
2712
Setting Description
the Down status for only a few seconds. Enter an integer.
perform [...] Select the notification that PRTG sends if the defined channel condition is
true and the defined latency is over. You see all notification templates
that you have defined under Setup | Account Settings | Notification
Templates. Use the search box to filter for notification templates. You can
also select no notification to not send a notification in this case.
When condition clears, Select the notification that PRTG sends if the defined channel condition is
perform [...] no longer true and the defined latency is over. You see all notification
templates that you have defined under Setup | Account Settings |
this case.
Change Trigger
Before you set up a change trigger, make sure that you select Trigger 'change' notification in the
sensor's settings, otherwise PRTG never sends the notification.
Trigger 'Change' Notification
The change trigger performs a notification if a compatible sensor's value changes. Hover over and
select Add Change Trigger from the menu to add a new change trigger, or click next to a change
trigger to change it.
Add Change Trigger
2713
Setting Description
When sensor changes, Select the notification that PRTG sends if a compatible sensor triggers a
perform [...] 'change' notification. You can enable this option in the settings of
compatible sensors. You see all notification templates that you have
defined under Setup | Account Settings | Notification Templates. Use the
search box to filter for notification templates. You can also select no
notification to not send a notification in this case.
Triggers That Can Be Inherited from Parent Objects

You see a list of all notification triggers that the selected object inherits from parent objects. The list is
empty and shows the message (no triggers defined) if you have not set any notification triggers for
objects that are higher in the object hierarchy 136 .
Trigger Inheritance
Setting Description
Trigger Inheritance Select the notification triggers that you want to use for the selected
object:
§ Inherit all triggers from parent objects and use the triggers defined
above: Use the inherited notification triggers in section Triggers that can
be inherited from parent objects and use the specific triggers for this
object in section Notification Triggers. To change settings of the
inherited notification triggers, click the name of the monitoring object in
the column Inherited from to open its Overview tab and then open the
Notification Triggers tab.
§ Only use the triggers defined above: Do not use the inherited
notification triggers in section Triggers that can be inherited from parent
objects. Only use the triggers that you define for this object in section
Notification Triggers.
This setting is valid for all notification triggers that you see here. It is
not possible to select only some of the notification triggers.
2714
Setting Description
You can also click a notification template to edit its settings or click
the object under Inherited from to go to the object's Overview tab.
Triggers That Are Defined in Libraries

You see a list of all notification triggers that are set in libraries 2748 that contain the selected sensor. The
list is empty and shows the message (no triggers defined) if you have not set any notification triggers in
libraries that contain the selected sensor.
Triggers in Libraries
Click a notification template to change its settings. Click a library in the column Inherited from to view the
library.
You cannot disable notification trigger usage from a library here. If you do not want to use
notification triggers from a library for the selected sensor, open the library and remove the sensor
from it or edit the notification triggers on the Notification Triggers tab 2759 of the library.
2715
Part 8
Advanced Procedures
2716 1/9/2023
8 Advanced Procedures
The following sections introduce more advanced features and procedures of PRTG.
In this section:
§ Toplists 2718
§ Move Objects 2723
§ Clone Object 2725
§ Multi-Edit 2729
§ Create Device Template 2735
§ Show Dependencies 2738
§ Geo Maps 2741
§ Notifications 2745
§ Libraries 2748
ú Library Management 2751
ú Libraries and Node Settings 2754
ú Library Context Menus 2761
§ Reports 2764
ú Run Reports 2769
ú Report Settings 2774
§ Maps 2786
ú Map Designer 2790
ú Maps Settings 2802
ú Map Rotation 2807
§ Setup 2809
ú Account Settings 2811
ú System Administration 2865
ú PRTG Status 2945
ú License Information 2972
ú Auto-Update 2979
ú Optional Downloads 2984
ú Help and Support Center 2986
ú Contact Support 2987
2717
8.1 Toplists
Packet Sniffer sensors and Flow (NetFlow, jFlow, sFlow, IPFIX) sensors not only measure the total
bandwidth usage, but also break down traffic by IP address, port, protocol, and other parameters. This
way, PRTG can tell which IP address, connection, or protocol uses the most bandwidth. PRTG shows
the results in Toplists.
Toplist Top Protocols for a Packet Sniffer Sensor
Toplist Storage
PRTG looks at all network packets and collects the bandwidth information for all IP addresses, ports,
and protocols. This creates a huge amount of analysis data. To reduce the amount of data that is
actually stored, PRTG only stores the top 100 entries of each Toplist in the database at the end of a
specified Toplist period by default.
Toplist Overview
Toplists are only available for Flow and Packet Sniffer sensors 3237 . PRTG displays Toplist on the
sensor's Overview tab.
2718
Toplist Overview for a Packet Sniffer Sensor
By default, there are three preconfigured Toplists:
Toplist Description
Top Talkers Shows bandwidth usage by IP address.
Top Connections Shows bandwidth usage by connection.
Top Protocols Shows bandwidth usage by protocol.
Working with Toplists

§ Click one of the Toplist names on the sensor's Overview tab or click below a Toplist to view a
distribution chart and a list of source IP addresses and destination IP addresses, source ports and
destination ports, protocols, or kinds of traffic in different channels, for example. What kind of
information is available depends on the selected Toplist.
ú Click an entry in the Toplist periods list on the left side to view data for a specific time period. The
default value is 15 minutes. You can also manually define the start and end time of the Toplist period
that you want to view. Use the date time picker to enter the date and time. Additionally, several table
list options 221 are available.
ú Click Print This Toplist to view a printer-friendly version of your Toplist and use the print dialog of
your browser to print the Toplist.
ú Click Sensor Overview to return to the selected sensor's Overview tab. For a quick selection of other
Toplists of the selected sensor, click one of the Toplist tiles at the top of the page.
Toplist Tiles
§ Click Add Toplist on the sensor's Overview tab to create a new Toplist. The available options are the
same as when you edit 2720 a Toplist.
2719
§ Click below a Toplist on the sensor's Overview tab and confirm with Delete to delete the Toplist.
Edit Toplists
Click below a Toplist on the sensor's Overview tab to modify a Toplist.
Setting Description
Name Enter a name to identify the Toplist.

Toplist Type Select the type of Toplist:

§ Top Talkers (IP address): Shows bandwidth usage by IP address.
§ Top Connections: Shows bandwidth usage by connection.
§ Top Protocols: Shows bandwidth usage by protocol.
§ Custom: Create your own Toplist by selecting one or more Toplist

fields.
Toplist Fields This setting is only visible if you select Custom above.
Select the fields that you want to add to the Toplist by enabling the check
box in front of the respective field name. The available options depend on
the sensor. They are different for Packet Sniffer, NetFlow v5, NetFlow v9,
IPFIX, and sFlow sensors.
For performance reasons, only select the fields that you really need
to monitor.
For more information, see section Performance Considerations 2721 .
Toplist Period (Minutes) Define the time span that a Toplist period covers in minutes. Enter an
integer. When a Toplist period is finished, PRTG stores the top results
and starts a new Toplist period.
To avoid load problems on the probe system, do not set this time
period too long. The default value is 15 minutes.
Top Count Define the length of your Toplist. PRTG stores only this number of entries
for each Toplist period. Enter an integer.
To avoid load problems on the probe system, set this value as low as
possible. The default setting is 100 to store the top 100 entries for
each Toplist period.
2720
Setting Description
Reverse DNS Lookup Define if you want to do a reverse Domain Name System (DNS) lookup for
IP addresses that are stored in the Toplist:
§ Reverse DNS lookup for IP addresses: Determine the domain name

that is associated with an IP address and show it in the Toplist.
§ No reverse DNS lookup: Only show IP addresses. Select this option to
increase performance.
Data Transfer Define how the probe sends the Toplist data set to the PRTG core server:
§ According to scanning interval (default): Send data in the scanning
interval defined in the settings of the sensor for which you create this
Toplist.
This setting can create a lot of bandwidth usage and CPU load if
you have many Packet Sniffer sensors, complex traffic, or long
Toplists.
§ At end of Toplist period: Send data once a Toplist period is finished.
This setting creates less bandwidth usage and CPU load, but you
cannot see the data of the current Toplist in the PRTG web
interface. You can only see Toplists with finished time periods.
Memory Limit (MB) Define the maximum amount of memory (in megabytes) that the probe
uses to collect the different connection information. Every Toplist adds its
amount of used memory to the probe's memory consumption. Increase
this value if the number of captured connections is not sufficient. Enter an
integer.
settings are lost.
Performance Considerations
If you create Toplists for data lines with considerable usage (for example, steady bandwidth over 10
megabits per second) or if the traffic is very diverse (for example, many IP addresses or ports with only
little traffic each), consider the following aspects:
§ The probe gathers all information that is needed for the Toplist in RAM during each Toplist period. By
default, only the top 100 entries are transferred to the PRTG core server. Depending on the Toplist type
and the traffic patterns, the required memory can consume many megabytes.
§ Define Toplist periods that are as short as possible to minimize memory usage. This is especially
important when the traffic is highly diverse.
2721
§ Memory requirements can grow almost exponentially with each Toplist field that you use in the Toplist
definition (depending on the traffic pattern). Avoid complex Toplists for high and diverse traffic. For
example, the Toplist Top Connections with 5 Toplist fields needs a lot more memory than the Toplist
Top Talkers with 1 Toplist field.
§ If you notice a high bandwidth usage between the PRTG core server and the probe, try the At end of
Toplist period option in the Toplist settings 2720 .
§ If you get Data incomplete, memory limit was exceeded messages, try to increase the memory limit in
the Toplist settings but keep an eye on the memory usage of the probe process.
§ To increase the performance of a Toplist, disable the reverse DNS lookup setting.
Notes
§ When you work 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 system to the outside
world and you must make sure that it is legal for you to configure PRTG like this.
§ Keep in mind that Toplists can be viewed in the PRTG web interface. You might not want to show lists
of domains that are used in your network to others, so restrict access rights 149 to sensors that have
Toplists.
§ Toplist charts, for example for top connections, are not meant to be used for detailed analysis.
Instead, they should indicate if there is an uncommon, bigger change in this Toplist.
More
KNOWLEDGE BASE


2722
8.2 Move Objects
There are several options for moving objects in the device tree or for moving objects from one probe or
group to a different probe or group.
Probes or Groups: Management Tab

The Management tab is available when you view probes or groups. After you click this tab, you can
directly move devices and sensors in the device tree via drag-and-drop.
Move Objects on a Probe or Group
If it is not possible to move an object, PRTG automatically starts a clone 2725 process.
For more information, see section Manage Device Tree 434 .
Devices: Overview Tab

When you view the Overview tab of a device, you see a list of all sensors on the device.
2723
Move Sensors on a Device
Click the column headers Pos, Sensor, Status, or Priority to sort the sensor list. To change a sensor's
position, click at the beginning of the row, drag the sensor to the new position, and drop it.
Context Menu: Move Option

Right-click any object in the device tree to show its context menu 232 . Hover over Move to open the Move
menu. The following actions are available:
Move Context Menu
§ Open the Management tab 434 of the object. This setting is only available for probes and groups.
2724
8.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.
Rules
The following rules for cloning apply:
§ The new object takes over all settings of the original object. This means, for example, that an auto-
discovery 270 starts automatically on a cloned device if this setting is enabled on the original device.
§ A cloned device contains all objects of the original device, regardless of whether they produce working
sensors or not. This often depends on the settings of the cloned device.
This behavior is different from creating a device template 2735 .
§ Cloned sensors initially show the Paused status to give you the chance to change any settings
230
before monitoring starts. Check the settings and resume 230 monitoring.
§ You cannot clone fixed objects such as the root group, a probe device, or PRTG system-internal
sensors.
§ The user account 2911 that clones an object must have at least read access 149 to this object and all
objects underneath in the object hierarchy 136 . The user group to which this user account belongs
must have the permission 2924 to create all sensors that run on the device or group that they want to
clone.
Clone an Object
Right-click an object in the device tree and select Clone from the context menu 232 to open an assistant.
If you want to clone a sensor, a faster way is to manage the manage device tree 434 .
2725
Clone Dialog for a Sensor
Clone Object Settings

[Object] To Be Cloned
2726
Several fields show information about the object that you want to clone. The available information varies
depending on whether you clone a group, a device, or a sensor.
Name for New [Object]
Enter information for the new object as described below.
Field Description
New [Object] Name Enter a name for the new object to identify it later, for example, in the
device tree or in table lists. By default, PRTG uses the old name with the
prefix Clone of.
New IP Address/DNS This setting is only available when you clone a device.
Name
Enter the IP address or Domain Name System (DNS) name for the new
device.
Service URL This setting is only available when you clone a device.
Specify a URL that you want to open directly when you select Device
Tools | Go to Service URL from the context menu of the device. For
example, you can configure this option to call the address
http://www.example.com/service.html. Enter a valid URL or leave the field
empty.
Parent [Object] for New [Object]
Use the object selector 225 to select the object to which you want to add the cloned object. If you clone a
group or a device, select a group. If you clone a sensor, select a device.
Click Continue to clone the object.
Results
After you clone an object, you can see the following:
§ If you clone a sensor, the Overview tab of the new sensor opens.
§ If you clone a group or a device, you stay on the same page.
§ Cloned sensors initially show the Paused status to give you the chance to change any settings
230
before monitoring starts. Check the settings and resume 230 monitoring.
2727
More
KNOWLEDGE BASE

2728
8.4 Multi-Edit
Table lists 221 offer the multi-edit feature. With this, you can bulk edit the properties of many objects.
Multi-edit is also available on the Management tab of probes or groups when you hold down the Ctrl key
to select multiple objects. See also section Manage Device Tree 434 .
You cannot change every setting with multi-edit. PRTG only displays settings that all selected
objects have in common.
Multi-Edit in Table Lists

In a table list, you can select several objects by enabling the check boxes on the right. You can also
select all objects on the page at once by enabling the check box in the table header.
Selecting all objects via the check box in the table header does not select all objects across
multiple pages. It only selects all objects on the first page in most cases.
Example of a Table List w ith Some Selected Objects
Use the Items option in the upper-right corner to view more items per page.
2729
When you select one or more objects, the multi-edit menu appears in which different functions are
available. The available menu options depend on the selected objects. For sensor lists, for example,
some frequently used functions are Pause ( ), Resume ( ), Scan Now ( ), Delete ( ), or Settings (
). Click a button to apply the respective function to all selected objects.
Multi-Edit Menu
Multi-Edit on the Management Tab

The Management tab is available for probes and groups.
You can use multi-edit for object settings:
§ Hold down the Ctrl key and select multiple objects of the same type, for example, multiple groups,
devices, or sensors.
§ In the dialog that appears, select the properties that you want to edit, change the respective settings,
and click Save. The changes are applied to all selected objects.
Multi-Edit on the Management Tab
2730
Edit Object Settings
Click in the multi-edit menu to open the Edit Multiple Objects dialog. This dialog shows most of the
settings that the selected objects have in common. For example, you can edit the name, tags, priority,
scanning interval, or access rights. The available options depend on the selected objects.
Example of Device Settings in Multi-Edit Mode
2731
To change a property, enable the check box in front of the respective setting and then change the
setting. New settings are applied to all selected objects. All properties with a disabled check box remain
unchanged.
If you multi-edit tags, PRTG overwrites existing tags.
lost.
Edit Channel Settings

The Channel Settings tab in the Edit Multiple Objects dialog is only available when you edit multiple
sensors. The available settings depend on the selected sensors. You can edit the settings of all
channels that the selected sensors have in common. Select a channel name from the Channel list. You
can then edit display settings, colors, scaling, and limits, for example.
2732
Example of Channel Settings in Multi-Edit Mode
To change a property, enable the check box in front of the respective setting and then change the
setting. New settings are applied to all selected objects. All properties with a disabled check box remain
unchanged.
lost.
2733
More
KNOWLEDGE BASE
Why are my credentials resulting in an error?

2734
8.5 Create Device Template
To add a specific device several times, you can create a device template from this device. When you
create a device template, PRTG saves information for nearly all sensors on this device to a template file
that you can later use in combination with the auto-discovery 270 (restrictions 2736 apply for a few
sensors). Custom device templates are also available in the PRTG Sensor Hub.
In the device template, PRTG saves all relevant sensor settings except for settings that you set on other
objects, such as schedules 145 , notification triggers 2745 , and access rights 149 . PRTG automatically sets
these settings to inherited settings.
To create a device template, right-click a device in your device tree. From the context menu 232 , select
Create Device Template to open the Create Device Template dialog.
Create Device Template Assistant
2735
Template Settings
Setting Description
Template Name Enter a display name to identify the device template.

Exclude Sensors Enable the check box in front of the sensors that you want to exclude
from the device template.
Sensors that you cannot save in device templates do not appear in
this list.
Sensors that dynamically scan for available monitoring items when
you add the sensor to a device do not appear in this list. PRTG
automatically includes these sensors in the device template if they
support the device template functionality. You cannot exclude these
sensors from the device template.
lost.
Device templates only save the sensors on the device and the sensors' settings including the
channel settings 2692 . They do not save the device itself or the device's settings. To successfully
create a device template, you must add sensors to the device (either manually 430 or via the auto-
discovery) and the sensors must be device template capable 2737 .
After you save your device template file, you see a message where you can review the sensors that the
new device template contains. Click OK to finish. PRTG stores the device template in the
\devicetemplates subfolder of the PRTG program directory 3218 . Your device template file contains all
sensors of the original device, including the sensors' settings.
Before the next auto-discovery, choose the Auto-discovery with specific device templates setting and
select the name of your new device template from the list. PRTG then tries to discover the stored
sensors. If the physical device answers to a sensor request, the sensor is added to the respective device
in PRTG.
Restrictions
There are a few settings that you cannot save in a device template so PRTG uses the default settings:
§ The Dependency Type setting Master sensor for parent in the Schedules, Dependencies, and
Maintenance Window section,
§ The Result Handling setting Store result because this setting is only intended for debugging purposes,
§ Settings in the Access Rights section to avoid security flaws, and
2736
§ Notification triggers settings that you set on other objects, for example, a device or group. PRTG
saves, however, notification triggers settings that you set directly on a sensor.
In general, you cannot save all sensor settings and channel settings (for example, channel limits of
dynamically created channels) of sensors that dynamically scan for available monitoring items when
you add the sensor.
Furthermore, because of internal restrictions, PRTG does not save every sensor in a device template.
For an overview list of all sensors, including their device template capability see section Available
Sensor Types 3237 .
Device Template Updates

Once a device template is created, it is not possible to add additional sensors to it via the PRTG web
interface. If you want to create a device template with an extended set of sensors, you need to create a
new template.
When you save a new device template, PRTG updates all internal sensor IDs in this template.
Because of this, PRTG creates all sensors that the new device template contains anew on the
device to which you apply the template, even if the same sensors have already been created on this
device with a different device template.
You cannot delete device templates via the PRTG web interface.
You cannot edit device template files in PRTG Hosted Monitor but you can upload the updated
device template again. For more information, see section Manage a PRTG Hosted Monitor
Subscription.
Device Template Filtering

You can include and exclude sensors from existing device templates. For more information, see the
Knowledge Base: How can I include and exclude sensors from device templates?
More
KNOWLEDGE BASE

How can I include and exclude sensors from device templates?

2737
8.6 Show Dependencies
The Dependencies 144 feature gives an overview of the dependencies that are configured for the objects in
your setup.
To see an object's dependencies, select Devices | Dependencies from the main menu bar 254 .
Dependencies Graph View
Tab Description
Overview Shows the dependencies graph 2738 . This is a visualization of device,

group, and sensor dependencies.
To show the dependencies graph, you need to access the PRTG web
interface as an administrator.
Selected Dependencies Shows a table list of manually set dependencies (see the Dependency
setting in section Schedules, Dependencies, and Maintenance Window in
any object's settings).
Master Dependencies Shows a table list of master dependencies.
Dependencies Graph
The Overview tab 174 shows the device tree in the dependencies graph view. The lines in the
dependencies graph symbolize dependencies between the monitoring objects in the device tree.
Additionally, PRTG uses different line colors 2739 for the dependencies. You can also view the
dependencies in different table lists on the Selected Dependencies tab or the Master Dependencies tab.
To show the dependencies graph, you need to access the PRTG web interface as an administrator.
The following actions are available:
2738
§ Enable the Show or Hide option to show or hide master dependencies. Hide is enabled by default to
only show parent dependencies, selected dependencies, and broken dependencies.
For technical reasons, the Show and Hide radio buttons are not available in Internet Explorer. Use
Google Chrome 75 or Mozilla Firefox 67 instead.
§ Click or in the upper-left corner to zoom in or out of the dependencies graph.

§ Click probe and group nodes to show the respective dependencies.
§ Click device or sensor nodes to open the corresponding Overview tab.
§ Click or to expand or collapse probe and group nodes.

§ The numbers in parentheses indicate how many child nodes of an object are shown.
Legend of Dependencies Graph

The line's colors show the kind and source of a dependency. This represents the Dependency Type as
defined in the Schedules, Dependencies, and Maintenance Window settings of a probe 529 , group 603 ,
device 674 , or sensor.
You can also find the legend for the line colors in the graph header bar.
Col Description
or
Gra Gray lines show a dependency by inheritance (Use parent (default) setting). The source of the
y dependency is the parent object on the left end of the line, for example, Root is the parent of
Local Probe.
Gray Line for Parent Dependency
Gre Green lines show a master dependency for a device (Master sensor for parent setting). The
en sensor that is set as the master points to the dependent device with a green arrow head at the
line's end. The arrow head from the dependent device to its master sensor is pink.
Green Line for Master Dependency
Pink Pink lines show a dependency that you set manually (Select a sensor setting). The source of
the dependency points to the dependant with a pink arrow at the line's end.
Pink Line for Selected Dependency
2739
Col Description
or
Red Red lines indicate broken dependencies, for example, if the master sensor is not available.
Red Line for Broken Dependency
2740
8.7 Geo Maps
With the Geo Maps feature, you can visualize geographical information about monitored objects that are
located at different sites worldwide on one page. You can display the location of probes, groups, and
devices in a geographical map on the Overview tab of an object or in Maps 2786 .
Global Status of a Netw ork in a Geographical Map
Prerequisites
To use geographical maps and view them in the PRTG web interface, make sure that your PRTG core
server has access to the internet to obtain map tiles. If a proxy is mandatory in your network, configure
the according proxy settings.
For more information, see section Core & Probes 2898 .
For more information about map tile server domains, see the Knowledge Base: Which domains and
ports does the Geo Maps feature use?
Geo Maps Concepts

The Geo Maps feature works as follows:
2741
Concept Description
Location information Enter Location (for Geo Maps) information, for example, a city name, an
address, or coordinates, for each probe, group, or device in the object's
settings 204 . The PRTG core server resolves your location specification to
global geographical coordinates with the help of an external map service
provider. PRTG uses this information to query a geographical map that
shows your objects.
You can use the first line of the location information field to label 2742
your locations.
Geo Maps settings Select a map service provider and the type of map that you want to view in
the User Interface 2869 settings in section Geo Maps. You can also disable
the integration of Geo Maps there.
PRTG connects to the specified maps service provider to get map tiles.
These map tiles provide the geographical background map. PRTG then
marks defined locations with a corresponding location marker that consists
of an object icon and the object's status color 2744 .
Object Marker
for a Group
Geographical maps You can display geographical maps in the device tree on an object's
display Overview tab. PRTG automatically adjusts the zoom level of a geographical
map so that it can show all locations of a selected object.
Geographical Map on an Object's Overview Tab
You can also add geographical maps to Maps. To do so, open the Map
Designer 2790 and click Geo Maps in the properties menu on the right.
Location Labels
You can define your own labels for locations of objects. To do so, enter the desired label in the first line
of the Location (for Geo Maps) field in an object's settings and provide the geo coordinates of the location
in the second line. The object appears with the defined label in geographical maps. It is also possible to
define the same label for different locations as long as the coordinates differ from each other.
2742
For example, enter the following information:
Big Apple
40.712778,-74.005833
Location New York w ith Geo Coordinates and Label Big Apple
The location New York appears on the geographical map with the label Big Apple:
Location New York w ith Label Big Apple
2743
Status Color of Location Markers
The location markers use different colors to show the overall monitoring status at this location.
For an overview of the colors and their states, see section Sensor States 184 .
More
KNOWLEDGE BASE
Which domains and ports does the Geo Maps feature use?
Which provider should I use for the Geo Maps feature of PRTG?
Why does my street not appear on the Geo Map shown in PRTG?
How do I get a Google Maps API key for use in PRTG?

Which limitations apply when using the Google Maps API in PRTG?
My geo maps are displayed without background. What can I do?


2744
8.8 Notifications
PRTG uses notifications to send you an alert, for example, whenever PRTG discovers a defined sensor
status 184 or when channels breach specific limits. You can define an unlimited number of notifications
using one or more notification methods 2745 . PRTG sends notifications to a user's notification contacts 2851
that you can define for each user account.
For more information, see the video tutorial: Notifications.
Overview
PRTG sends a notification when a defined event triggers it. The following events can trigger notifications:
Event Examples
Sensor status change § A sensor changes from the Up status to the Down or the Warning status
because responses are slow.
§ A sensor changes to the Unusual status.
Sensor value threshold § A sensor shows a request time that is higher than 1,000 ms for more
breach than 30 minutes.
§ Free disk space is below 10%.
Speed threshold A traffic sensor shows more than 1 Mbit/s for more than 5 minutes.
breach
Volume threshold A traffic sensor shows more than 1 GB transferred in 24 hours.

breach
Sensor value change A specific value changes, for example, when the sensor monitors files on a
hard disk drive.
Notification Methods
A notification can use one or more of the following notification methods:
§ Send Email 2825
§ Add Entry to Event Log 2828
§ Send SMS/Pager Message 2829
§ Execute HTTP Action 2831
§ Execute Program 2833
§ Send Syslog Message 2834
§ Send SNMP Trap 2835
2745
§ Send Amazon Simple Notification Service Message 2837
§ Assign Ticket 2838
§ Send Push Notification 2840
§ Send Microsoft Teams Message 2841
§ Send Slack Message 2843
§ Send MQTT Publish Notification 2845
§ Send OPC UA Notification 2848
For more information, see section Notification Templates 2825 .
Placeholders
Notifications can contain valuable sensor information that you can define via placeholders, for example:
§ Last error message
§ Last successful or failed request
§ Total downtime
§ Total uptime
§ Recent sensor history
§ A direct link to the PRTG web interface
For available placeholders, see section Placeholders for Notifications 3361 .
Notifications Setup
and their content.
2746
PRTG web interface.
More
KNOWLEDGE BASE
Notifications based on priority or favorites

VIDEO TUTORIAL
Notifications
§ https://www.paessler.com/support/videos-and-webinars/videos/notifications
PAESSLER WEBSITE
You can find custom notification scripts in the PRTG Sensor Hub
2747
8.9 Libraries
With the Libraries feature, you can create additional, customized views of your device tree.
For more information, see the video tutorial: Libraries in PRTG
Example of a Library
In this section:
§ Introduction 2748
§ Preconfigured Libraries 2749
§ Libraries Menu 2749
§ Libraries List 2750
§ Working with Libraries 2750
Introduction
With libraries, you can create custom device tree views of your network's status and monitoring data.
PRTG updates these views in the same interval as your device tree. The library views display the same
monitoring data, but arranged the way you want, for example, based on target groups or a specific use
case. For example, you can create a library that contains an overview of all your bandwidth monitoring
sensors, regardless of the device that they run on.
The Libraries feature includes the following options:
§ Create libraries that contain library nodes with objects from your entire configuration.
§ Show data from different 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 the device that they run on.
2748
§ Filter your entire device tree or parts of it by sensor type, status, or tag, and only show matching
sensors.
Preconfigured Libraries
PRTG provides several preconfigured libraries that you can also edit or delete.
Preconfigured libraries are only visible to administrators.
Preconfigured Libraries
The following libraries are automatically created when you install PRTG for the first time. Some of these
libraries are initially empty, but as you add more sensors, PRTG automatically fills them according to the
filter settings defined for the library nodes:
§ All bandwidth sensors
§ All CPU load sensors
§ All diskspace sensors
§ All memory sensors
§ All sensors grouped by state
§ All VMware sensors
§ Sensors grouped by priority
Sensors that you add to libraries do not count against the maximum number of sensors of your
license.
Libraries Menu
Click Libraries in the main menu bar 256 to open an overview list of all libraries. Hover over Libraries to
show other options.
2749
Option Description
All Open the Libraries list where you can view or add custom device tree
views of your network status and monitoring data.
Add Library Open a dialog to create a new library.
Select Library Open a library. Hover over Select Library to show more options. Follow
the alphabetical menu path that is specific to your setup to view your
libraries. Click a library to open it.
Libraries List
In the All view, you see a list of all libraries. Enable the check box next to a library and use the quick
action buttons:
§ Used by ( ): Show which objects use this library.
§ Clone ( ): Create a clone 2725 of this library.
§ Delete ( ): Delete this library.
§ Settings ( ): Open this library and change the settings 2754 of the library and its library nodes.
To add a new library, hover over and select Add Library from the menu.
See also sections Working with Table Lists 221 and Multi-Edit 2729 .
Working with Libraries

For more information on how to work with libraries, see the following sections:
§ Library Management 2751
§ Libraries and Node Settings 2754
§ Library Context Menus 2761
More
PAESSLER WEBSITE
How to use libraries in PRTG in 4 steps

§ https://www.paessler.com/support/how-to/libraries
VIDEO TUTORIAL
Libraries in PRTG
§ https://www.paessler.com/support/videos-and-webinars/videos/libraries
2750
8.9.1 Library Management
You can manage your libraries by adding and editing library nodes and by defining which objects you
want to see on a library node.
Click the Management tab. You see a split screen:
§ On the left side, you can see your library. If you create a new library, it is empty in the beginning.
§ On the right side, you see your device tree.
Bandw idth 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 is immediately added as a new library node. Repeat this procedure as often as you wish
until you have added all desired items to the library.
Library nodes can contain up to 1,000 sensors. However, if you add single sensors to the library via
the Management tab, there can only be one sensor in one library node.
Click Add Library Node or Add Group in the bottom-left corner of the split screen to create nested library
nodes.
Drag and drop library nodes 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 library node's settings.
2751
Set Library Node Display Settings
Right-click the name of a library node and select Edit | Settings from the context menu 2761 to change the
Library Node Display Settings. In the dialog that appears, you can change the name of the library and its
tags, as well as the linked object, the library node view, and filters. These settings are available for each
library node.
Edit Library Node Display Settings
You can either show the Linked Object as a subtree of your device tree including probes, groups, and
devices, or you can view all sensors underneath the Linked Object.
2752
§ When you select Show a subtree of the device tree, the library node called My Sub Tree, for example,
looks like a branch in your device tree.
Library with One Node that Shows a Branch of the Device Tree
§ When you select Show a collection of filtered sensors, PRTG only shows the sensors that are
underneath the Linked Object in the device tree without probes, groups, and devices. You can
additionally filter for certain sensor types, states, and tags. PRTG then only shows matching sensors.
In the example screenshot, you can see the library node My Sub Tree where only bandwidth sensors
are shown.
Library with One Node that Only Shows a Collection of Bandwidth Sensors
For more information, see section Libraries and Node Settings 2754 .
Context Menu
You can right-click any object on a library's Overview tab or Management tab to open its context menu.
For more information, see section Library Context Menus 2761 .
2753
8.9.2 Libraries and Node Settings
Use the library tabs to access all functionalities and settings of a library.
Library Tabs
Overview
Click the Overview tab to show the status of your library.
Management
Click the Management tab to edit the contents of your library, for example, to add items to the library via
drag-and-drop.
For more information, see section Library Management 2751 .
Library Node Settings

To change the settings of a library node, go to a library's Overview tab and click the name of a library
node. You can also open the library node settings on the Management tab via the library node's context
menu 2761 .
You can only change the settings of a library node if it already contains monitoring objects like
groups, devices, or sensors.
Basic Library Node Settings
Setting Description
Library Node Name Enter a name to identify the library node.

Security Context Define the security context for the Overview tab of the library. Select a
user account from the dropdown list to define which objects are visible. All
users with access to the library can only see the objects that the
selected user account has the rights to view.
Only sensors that are visible in the library trigger a notification 2745 .
2754
Setting Description
Basically, the security context defines the minimum access rights to

objects like libraries, reports, or maps, that a user account has. If the
security context of an object is PRTG System Administrator, for example,
every user sees all objects in a library, in a report, or on a map, no matter
what the particular user access rights are.
Library Node Display Settings
Setting Description
Linked Object Click and use the object selector 225 to change the object in the
device tree that the library node references.
Library Node View Select how you want to view the objects that PRTG shows underneath
the library node:
§ Show a subtree of the device tree: View all objects underneath the
linked object as you can see them in the device tree, including probes,
groups, and devices.
§ Show a collection of filtered sensors: Only view the sensors underneath
the linked object without probes, groups, and devices. You can use
filters to show only specific sensors.
The library node can show up to 1,000 sensors. PRTG discards
further sensors.
Filter by Sensor Type This setting is only visible if you select Show a collection of filtered
sensors above.
Select if you want to filter the displayed sensors by specific sensor types:
§ Show all sensor types: Do not filter by sensor types.
§ Show only specific sensor types: Filter the displayed sensors by

specific sensor types.
2755
Setting Description
PRTG applies this filter in real time. If the configuration underneath

the linked object changes, the library node accordingly shows
matching sensors.
Sensor Types This setting is only visible if you select Show only specific sensor types
above.
You can see a list of all sensor types. PRTG displays sensors that are in
use in bold print.
Enable the check box in front of a sensor type that you want to include in
the library node view.

matching sensors.
You cannot filter for sensor types that are defined in mini probes.
Filter by Sensor Status This setting is only visible if you select Show a collection of filtered
sensors above.
Select if you want to filter the displayed sensors by specific sensor

states:
§ Show all sensor states: Do not filter by sensor status.
§ Show only sensors in specific states: Filter the displayed sensors by

specific sensor states.
Sensor States This setting is only visible if you select Show only sensors in specific
states above.
You can see a list of all sensor states. Enable the check box in front of a
sensor status to include all sensors that show this status in the library
node view:
§ Unknown
§ Up
§ Warning
§ Down
§ Paused by user
§ Unusual
§ Down (Acknowledged)
2756
Setting Description
§ Down (Partial)

matching sensors.
Filter by Tag This setting is only visible if you select Show a collection of filtered
sensors above.
Select if you want to filter the displayed sensors by specific tags:

§ Show all tags: Do not filter by tag.
§ Show only sensors with specific tags: Filter the displayed sensors by
specific tags.
Tags This setting is only visible if you select Show only sensors with specific
tags above.
Enter one or more tags for sensors that you want to include in the library
node view. You can also use the plus sign (+) or the minus sign (-) to
categorize tags as must have or must not have, for example, +snmp;–
wmi (must have the tag snmp and must not have the tag wmi).
The tag of a sensor can also be inherited from a parent object.

matching sensors.
Filter by Priority This setting is only visible if you select Show a collection of filtered
sensors above.
Select if you want to filter the displayed sensors by specific priorities 227 :
§ Show all priorities: Do not filter by priority.
§ Show only sensors with specific priorities: Filter the displayed sensors
by specific priorities.
PRTG ignores the priority settings of a parent object. It only regards
the priority setting of the sensor itself.
Priorities This setting is only visible if you select Show only sensors with specific
priorities above.
2757
Setting Description
You can see a list of all available priorities. Enable the check box in front
of a priority to include all sensors that have this priority in the library node
view:
§ ***** (highest priority)
§ ****
§ ***
§ **
§ * (lowest priority)

matching sensors.
lost.
After you apply filters, it might take several seconds for the changes to become visible. This is
because of internal filter processes that run in the background.
Settings
Click the Settings tab to open a library's general settings.
Basic Library Node Settings
Setting Description
Library Node Name Enter a name to identify the library.

Security Context Define the security context for the Overview tab of the library. Select a
user account from the dropdown list to define which objects are visible. All
users with access to the library can only see the objects that the
selected user account has the rights to view.
Only sensors that are visible in the library trigger a notification 2745 .
2758
Setting Description
Access Rights
Setting Description
User Group Access Define the user groups that have access to the object. You see a table
with user groups and group access rights. The table contains all user
groups in your setup. For each user group, you can choose from the
object does not show up in lists.
§ Read access: Users in this user group can see the object and view its
settings.
§ Write access: Users in this user group can see the object and view and
edit its settings. However, they cannot edit the object's access rights
settings.
§ Full access: Users in this user group can see the object, view and edit
its settings, and edit its access rights settings.
You can create new user groups in the User Groups 2922 settings.
When you give access rights to a user group, all user group members can see the objects in the
respective library.
settings are lost.
Notification Triggers
You can define notification triggers for any kind of library, also for dynamic libraries that can change with
every scanning interval, for example, when you filter a library by sensor status or priority.
Comments
2759
History
Delete
You can delete the entire library at any time. Right-click a library's name and select Delete from the
context menu.
More
KNOWLEDGE BASE

2760
8.9.3 Library Context Menus
Right-click a library or a library node on a library's Overview tab or Management tab to show its context
menu.
Library Context Menu

The Library Context Menu contains actions for your libraries.
Library Context Menu
Action Description
available:
Edit Context Menu
§ Settings: Open a dialog to edit the library settings 2758 .
§ Management: Open the Management tab 2751 of the library.
an object.
Add Library Node Add a new library node to the library.
Add Group Add a group to the library to create nested library nodes.
2761
Action Description
Library Node Menu

The Library Node Menu contains actions for your library nodes.
Library Node Menu
Action Description
available:
§ Settings: Open a dialog to edit the library node settings 2754 .
Delete from Library Delete the object. PRTG asks for confirmation before it actually deletes
an object.
available:
Move Context Menu
2762
Action Description
§ Top: Move the library node to the top of the library.
§ Up Move the library node one entry up.
§ Down: Move the library node one entry down.
§ Bottom Move the library node to the bottom of the library.
More
KNOWLEDGE BASE

2763
8.10 Reports
With the Reports feature, you can view and analyze historic monitoring results for a specific period of
time or for your system configuration. You can create reports for all sensors or only for specific sensors.
Example of a Report
The report above shows the report data for devices on a local probe. You can see graphs for the
preceding week and data tables with numeric results.
In this section:
§ Reports Menu 2765
§ Reports List 2766
§ Configuration Reports 2767
2764
§ Automatic Averaging 2767
Introduction
You can generate reports on demand or via schedules in HTML and PDF format, as well as in comma-
separated values (CSV) and Extensible Markup Language (XML) format. Furthermore, you can create
reports for a single sensor or for a whole range of sensors. It is also possible to create HTML reports of
your system configuration 2767 .
Report templates define the overall look of your report and in which detail the report shows monitoring
data.
Preconfigured Reports
PRTG provides several preconfigured reports that you can also edit or delete:
§ Summary report for all sensors
§ Top 100 Busy/Idle Processor Sensors
§ Top 100 Fastest/Slowest HTTP Sensors
§ Top 100 Fastest/Slowest Ping Sensors
§ Top 100 Free/Full Disk Space Sensors
§ Top 100 Most/Least Used Bandwidth Sensors
§ Top 100 Most/Least Used Memory Sensors
§ Top 100 Uptime/Downtime Report
Reports Menu
Click Reports in the main menu bar 261 to open an overview list of all reports about monitoring data. Hover
over Reports to show other options.
Option Description
All Open the Reports list where you can view or add reports about your
monitoring data.
Add Report Open a dialog to create a new report.
Select Report Hover over Select Report to show a list of your reports about monitoring
data. Click a report to open it.
Configuration Reports Hover over Configuration Reports to see the available configuration
reports 2767 . Select an item to create reports for maps, reports, users and
user groups, and system configuration to document changes to the
configuration.
2765
Reports List
In the All view, you see a list of all reports about monitoring data.
List of Reports
Section Description
Object Shows the name of the report.
Template Shows the name of the template that this report uses.
Security Context Shows the user account that PRTG uses to run the report. This user
account defines which objects are visible in the report.
For more information, see section Report Settings 2774 .
Period Shows the time span that the report covers.
Schedule Shows if you set a schedule to automatically run the report in a regular
interval.
For more information, see section Report Settings 2774 .
Email Shows the email address to which PRTG automatically sends the report if
you set a schedule and entered an email address in the report settings.
Status Shows the status of the report.
2766
Section Description
Next Run Shows the date and time at which PRTG runs the report the next time if
you set a schedule in the report settings.
Last Run Shows the date and time at which PRTG ran the report the last time if
you set a schedule in the report settings.
# Sensors in Last Run Shows the number of sensors whose data was included when PRTG last
ran the report.
Click the name of a report about monitoring data to open the Run Now tab.
You can only run configuration reports via the main menu bar.
Enable the check box next to a report and use the quick action buttons:
§ Clone ( ): Create a clone 2725 of this report.
§ Delete ( ): Delete this report.
§ Settings ( ): Open this report and change its settings 2774 .
To add a new report, hover over and select Add Report from the menu.
Configuration Reports
Configuration reports show the PRTG configuration. They are available for Maps, Reports, Users & User
Groups, and System Configuration. PRTG directly displays a configuration report in a new browser
window as an HTML page. You can use configuration reports, for example, to file and document changes
to the PRTG configuration.
Configuration reports contain the same information as you can see on the Maps 2786 overview, the
Reports 2764 overview, and on the User Accounts 2911 and User Groups 2922 tabs of the system
administration settings. The configuration report System Configuration includes the system
administration settings of the User Interface 2865 , Monitoring 2879 , Notification Delivery 2887 , Core &
Probes 2897, and Cluster 2933 tabs.
Configuration reports are interactive. You can click available links to go to the corresponding pages
in the PRTG web interface.
Automatic Averaging
For performance reasons, PRTG automatically averages monitoring data when it calculates data for large
periods of time.
2767
Period of Time in Report Minimum Level of Detail (Averaging Interval)
Up to 40 days Any
40 to 500 days 60 minutes/1 hour or longer
Reports for periods that are longer than 500 days are not possible. If you enter a longer period,
PRTG automatically shortens it to 365 days.
In some cases, the generated report might contain a period of time that differs from the defined start
and end date for the report because of internal averaging processes. When averaging intervals are
longer than 1 hour and do not equal 24 hours, and when they are combined with specific periods of
time, the resulting data points might be asynchronous to the periods of time. Consider this behavior
particularly if you use application programming interface (API) calls 3094 to generate reports.
More
PAESSLER WEBSITE
How to set up reports in PRTG in 5 easy steps

§ https://www.paessler.com/support/how-to/reports
2768
8.10.1 Run Reports
Run Now
On the Run Now tab, you can immediately run a report with the settings that you defined before.
When you set up or run a report, also keep in mind the remarks for reports 2772 .
Run Report on Demand
Report Period
Setting Description
Period Define the time span that the report covers:

§ Current period: This week [date range]: Use monitoring data of the
current period. The actual time span depends on the report period that
you define in the report settings 2774 . It can be today, this week, this
month, or this year.
2769
Setting Description
§ Previous period: Last week [date range]: Use monitoring data of the
previous period. The actual time span depends on the report period that
you define in the report settings. It can be yesterday, last week, last
month, or last year.
§ Select a predefined date range: Use monitoring data of a predefined
period other than the current or the previous period. Select from a list of
date ranges below.
§ Define a custom date range: Use monitoring data of a custom period.
Set the start and end date below or choose from several quick range
buttons.
Date Range This setting is only visible if you select Select a predefined date range
above.
From the list, select a date range for which PRTG generates the report.
The shown time spans depend on the available monitoring data and on
the report period that you define in the report settings. It can be days,
weeks, months, or years.
Start Date This setting is only visible if you select Define a custom date range above.
Set the start date of the time span for which PRTG generates the report.
Use the date time picker to enter the date and time. Make sure that you
define a valid period.
End Date This setting is only visible if you select Define a custom date range above.
Set the end date of the time span for which PRTG generates the report.
Use the date time picker to enter the date and time. Make sure that you
define a valid period.
Quick Range This setting is only visible if you select Define a custom date range above.
Use the buttons to quickly set the start and end dates for the report:
§ Today
§ Yesterday
§ Last Week (Mo-Su)
§ Last Week (Su-Sa)
§ Last Month
§ 2 Months
§ 6 Months
§ 12 Months
2770
Setting Description
PRTG sets the date range 223 to the last matching period. It starts at
00:00 and ends at 00:00 of the following day.
Report Processing
This section is not visible for read-only users.
Setting Description
File Format and Delivery Define how you want to view the report:
§ View report as HTML: Directly view the report in a new browser window
or tab.
§ Create and store .pdf and data files: Create a .pdf file and, depending
on the Data Files 2782 setting, create data files of the report and store it.
You find the stored report files on the Stored Reports tab. You also
receive a ToDo ticket. By default, PRTG sends out a notification email
to administrators in this case.
§ Create and store .pdf and data files and send them by email: Create a
.pdf file and, depending on the Data Files setting, create data files of
the report, store the files, and send them via email to the email address
that you define below. You can find the stored report files on the Stored
Reports tab.
PRTG only generates .csv and .xml data files for report templates
that include data tables.
To create .pdf files, make sure that the print spooler service runs on
the PRTG core server system.
Some special characters, for example, 4-byte unicode characters,
might not be displayed correctly in PDF reports. As a workaround,
we recommend that you generate an HTML report and save it as a .pdf
file.
If you generate reports with Internet Explorer 11, we recommend that
you use one of the PDF options for optimal results.
Target Email Address This setting is only visible if you select Create and store .pdf and data
files and send them by email above.
Enter one or more valid email addresses to which PRTG sends the report.
Use commas to separate email addresses.
PRTG sends an email to all recipients. All recipients appear in the To

field of the email.
2771
Setting Description
You can change the configuration for outgoing emails in the

Notification Delivery 2887 settings.
File Compression This setting is only visible if you select Create and store .pdf and data
files and send them by email above.
Define if PRTG compresses the attached report files before it sends them:
§ Send files without compression: PRTG sends the report files by email
in their original size.
§ Compress files in a .zip file: PRTG compresses the report files to a .zip
file before they are sent by email.
Click Run Report to start the report generation. Depending on the number of selected sensors, this might
take a while. If it takes a long time to generate HTML reports, consider using one of the PDF options.
Remarks for Reports

§ Any sensor graph in your report only shows channels that you select via the Show in graphs option in
the channel settings 2692 .
§ Reports show statistics for the uptime (the Up and Down states184 in percent) and for requests (Good
and Failed in percent). PRTG rounds values between 5% and 95%, as well as 100% and 0%, to whole
numbers without decimal places. Other values are shown with 3 decimal places.
§ Because PRTG rounds values, the statistics in the report section Sensor Status History can differ from
the values in the report section Uptime Stats by a few seconds.
§ PRTG limits data reporting to 5 requests per minute.
§ Reports cannot show uptime or downtime data for the Sensor Factory sensor.
§ Create reports that include an appropriate amount of data. Reports might not work as expected if
PRTG has to process too many sensors with short scanning intervals. Adjust your report size and the
time span that the report covers, if necessary.
Stored Reports
On the Stored Reports tab, you can view all PDF reports and data files that you created and stored.
Click a name to open the report. PRTG stores reports until they are deleted according to the data
purging settings 2909 of your PRTG configuration.
Other Tabs
For all other tabs, see section Report Settings 2774 .
2772
More
KNOWLEDGE BASE
Why is there missing data in historic data reports?

Creating a PDF report does not work. What can I do?
2773
8.10.2 Report Settings
In this section:
§ Settings 2774
§ Basic Report Settings 2774
§ Included Sensors 2776
§ Report Schedule 2778
§ Report Period 2780
§ Percentile Handling 2781
§ Data Files 2782
§ Report Comments 2783
§ Select Sensors Manually 2784
§ Sensors Selected by Tag 2785
§ Comments 2785
Settings
Click the Settings tab to open the settings of a report.
When you set up or run a report, also keep in mind the remarks for reports 2772 .
Basic Report Settings
Setting Description
Report Name Enter a name to identify the report. PRTG uses the name in reports
lists 261 and as the title of generated reports.
2774
Setting Description
Report Template Templates define the overall look of your report and in which detail the
report shows monitoring data. PRTG includes several preconfigured report
templates. Select a template for the report from the dropdown list:
§ Graph with data table (data files available): Create a report with graphs
and data tables. Choose from different intervals. Reports that use one of
these templates also generate .csv and .xml files if you select the
respective setting in the Data Files section.
§ Data table only (data files available): Create a report with data tables.
Choose from different intervals. Reports that use one of these templates
also generate .csv and .xml files if you select the respective setting in
the Data Files section.
§ Graph only (data files not available): Create a report with graphs.
cannot generate .csv or .xml files.
§ List of sensors (data files not available): Create a report in a compact
sensor list style. The list is available with and without graphs. Reports
that use one of these templates cannot generate .csv or .xml files.
§ Top 100 highest and lowest (data files not available): Create a report
with up to 100 objects with the highest and lowest average values.
cannot generate .csv or .xml files.
§ Top 10 uptime and downtime (data files not available): Create a report
with up to 10 objects with the highest uptime and downtime for each
object. You can choose between data in percent and hours. Reports
§ Top 100 uptime and downtime (data files not available): Create a report
with up to 100 objects with the highest uptime and downtime for each
object. You can choose between data in percent and hours. Reports
PRTG automatically averages 2767 monitoring data within an interval.
Security Context Define the security context that the report uses for access to monitoring
data. Select a user account from the dropdown list to define which
objects are visible in the report. The report only contains objects that the
selected user has the access rights 149 to view. By default, the security
context is the user account that creates the report.
2775
Setting Description

Time Zone Select a time zone from the dropdown list. PRTG uses this time zone for
all date-specific settings in the report.
Page Format Define the page size in which PRTG creates .pdf files:
§ None: Do not specify a page format. PRTG automatically sets a size.
§ DIN A4: Use the German DIN A4 format.
§ DIN A3: Use the DIN A3 format.
§ DIN A2: Use the DIN A2 format.
§ Legal: Use the North American legal page format.
§ Letter: Use the North American letter page format.
§ Ledger: Use the North American ledger page format.
Page Orientation Define the page orientation for the data in PDF reports:
§ Portrait: Use the portrait orientation.
§ Landscape: Use the landscape orientation to show data tables of

sensors with many channels. Other parts of the report remain in the
portrait orientation and do not resize to the landscape orientation.
Included Sensors
Setting Description
Cluster Node This setting is only visible if you run PRTG in a failover cluster 132 .
Select the cluster node from which the report takes monitoring data from
the dropdown list. The available options are specific to your configuration.
By default, the master node is set. Select All cluster nodes to create a
report that includes data from all of your cluster nodes.
A report for all cluster nodes only includes data for the primary
channels. Be careful with big reports for all cluster nodes because
the report generation might significantly slow down your monitoring.
2776
Setting Description
If you select a failover node, report and data files do not show data
from the local probe or from a remote probe and might be empty or
show 0 values.
You can generate .csv and .xml data files only for a single failover
node. If you select the option All cluster nodes, the report does not
create data files.
Sensors by Tag Select the sensors that you want to include in the report by tag. Enter
one or more tags. Confirm each tag with the Spacebar key, a comma, or
the Enter key. You can use tags to group objects and use tag-filtered
views later on. Tags are not case-sensitive. Tags are automatically
inherited 142 . The report covers all sensors that have at least one of the
tags. You can also leave the field empty.
You can also use the plus sign (+) or the minus sign (-) to categorize
tags as must have or must not have, for example, +snmp –wmi (must
have the tag snmp and must not have the tag wmi).
The report automatically includes all channels of sensors that you

add by tag, unless you run a cluster and select All cluster nodes in
the Cluster Node setting above.
If you want to manually select the sensors to include in the report,
save your settings and go to the Select Sensors Manually 2784 tab.
Filter Included Sensors Filter the included sensors further. Use this option, for example, if you
by Tag manually add entire probes, groups, or devices to the report and do not
want to include all sensors that have these objects as their parent
objects. PRTG then only includes the sensors in the report that have at
least one of the tags that you enter here.
Enter one or more tags. Confirm each tag with the Spacebar key, a
automatically inherited 142 . You can also leave the field empty.
You can also use the plus sign (+) or the minus sign (-) to categorize
tags as must have or must not have, for example, +snmp –wmi (must
have the tag snmp and must not have the tag wmi).
2777
Report Schedule
Setting Description
Schedule Define the time at which you want to automatically run the report:
§ No schedule (default): Only use the options on the Run Now tab to
manually start the report generation.
§ Every full hour: Run the report every 60 minutes.
§ Every day at a specific hour: Run the report every 24 hours. Specify the
exact time below.
§ Every specific day of the week: Run the report every 7 days. Specify
the exact time below.
§ Every specific day of the month: Run the report on a specific day every
month. Specify the exact time below.
§ First day after the quarter: Run the report on the first day after the end
of the quarter. This means, for example, on April 1st for the first quarter
of the year (January 1st - March 31st).
§ Every specific date: Run the report on a specific date every year.
Specify the exact date below.
Specific Hour This setting is only visible if you select Every day at a specific hour
above.
From the list, select the hour at which you want to run the report.
Specify Day This setting is only visible if you select Every specific day of the week
above.
From the list, select a day of the week or a day of the month for which
you want to run the report.
If you select Last, the report always runs on the last day of the
month, regardless of how many days the month has. If you select a
date that does not exist in every month, for example, 30th, PRTG
automatically runs the report on the last day of the month.
Specific Date This setting is only visible if you select Every specific date above.
Enter a valid date in the format DD.MM., for example, 31.12. The report
runs on this date every year.
Report Handling This setting is only visible if you select one of the schedule options above.
Define what you want to do with a finished report:
2778
Setting Description
§ Store report and send it by email: Create a .pdf file and, depending on
the Data Files setting, create data files of the report, store the files, and
send them via email to the email address that you define below. You
can find the stored report files on the Stored Reports tab.
§ Store report (default): Create a .pdf file and, depending on the Data
Files 2782 setting, create data files of the report and store it. You find the
stored report files on the Stored Reports tab. You also receive a ToDo
ticket. By default, PRTG sends out a notification email to
administrators in this case.
§ Send report by email: Create a .pdf file and, depending on the Data
Files setting, create data files of the report and send them via email to
the email address that you define below. PRTG does not permanently
store the report files.
PRTG only generates .csv and .xml data files for report templates
that include data tables.
To create .pdf files, make sure that the print spooler service runs on
Some special characters, for example, 4-byte unicode characters,
might not be displayed correctly in PDF reports. As a workaround,
we recommend that you generate an HTML report and save it as a .pdf
file.
Target Email Address This setting is only visible if you select one of the email options above.
Enter one or more valid email addresses to which PRTG sends the report.
Use commas to separate email addresses.

field of the email.
You can change the configuration for outgoing emails in the
Notification Delivery 2887 settings.
Email to User Group This setting is only visible if you select one of the email options above.
From the list, select a user group to which you send an email with the
report. All members of this group receive the email. You can edit user
groups in the User Groups 2922 settings.
If you define both individual email addresses and select a user group,
PRTG sends the report to the individual email addresses as well as
to the members of the selected user group.
field of the email.
2779
Setting Description
File Compression This setting is only visible if you select one of the email options above.
Define if PRTG compresses the attached report files before it sends them:
§ Disable (default): PRTG sends the report files by email in their original
size.
§ Enable: PRTG compresses the report files to a .zip file before they are
sent by email.
Report Period
Setting Description
Report Period Type Define the type of period for which you want to create the report:
§ Current period: Use monitoring data of the current period.
§ Previous period: Use monitoring data of the previous period.
This setting works in combination with the Period setting below. For
example, Previous period means yesterday if you select the Day
option.
Period Define the period that the report covers:

§ Day
§ Week
§ Month
§ Quarter of year
§ Year
Day Period This setting is only visible if you select Day above.
From the list, select the hours at which a day starts and ends. The
default setting is 0:00-23:59.
Week Period This setting is only visible if you select Week above.
From the list, select the days of the week when the week starts and
ends:
§ Monday-Sunday: A reported week starts on the Monday and ends on
the Sunday of the week.
2780
Setting Description
§ [Day-Day]: A reported week starts on the [Day] of the week and ends
on the [Day] of the following week.
Month Period This setting is only visible if you select Month above.
From the list, select the days of the month when the month starts and
ends:
§ first-last day: A reported month starts on the first day and ends on the
last day of the month.
§ [15.-14.]: A reported month starts on the 15th of the month and ends on
the 14th of the following month.
Year Period This setting is only visible if you select Year above.
From the list, select when the year starts and ends:
§ 1/1-12/31: A reported year starts on January 1st and ends on
December 31st.
§ 7/1-6/30: A reported year starts on July 1st and ends on June 30th the
following year.
Report Schedule From the list, select a specific time span for which you want to generate
the report. The report only includes monitoring data for specific hours or
weekdays within the defined period.
Select None to include all available monitoring data in the report, or
choose a schedule, for example Weekdays, to exclude all weekends from
the report. The available schedules depend on your configuration.
For more information, see section Schedules 2856 .
Percentile Handling
Setting Description
Percentile Results Define if you want to include an additional percentile calculation 3200 of
your data in the report:
§ Do not show percentiles: PRTG does not use a percentile formula to
calculate your monitoring results. It only shows the standard values.
§ Show percentiles: PRTG displays an overview table with the percentiles
of each channel for the whole report period, and the percentiles of the
primary channel in the table for each scanning interval.
2781
Setting Description
Percentiles are not available for all report templates. If a template

does not support percentiles, they do not show up in the report, even
if you enable this setting.
Percentiles are also not available for a cluster if you select All cluster
nodes in the Cluster Node setting in section Included Sensors.
Select a failover node to include percentiles.
Percentile Type This setting is only visible if you select Show percentiles above.
Enter the percentile type that you want PRTG to use for the calculation. If
you choose, for example, to calculate the 95th percentile, enter 95 here
and 5% of peak values are discarded. Enter an integer.
Percentile Averaging This setting is only visible if you select Show percentiles above.
Interval
Enter a value to define the averaging interval on which PRTG bases the
percentile calculation. The default value is 300 seconds (5 minutes). This
means that PRTG takes 5-minute averages as basic values for the
percentile calculation. Enter an integer.
Percentile Mode This setting is only visible if you select Show percentiles above.
Select the mode for percentile calculation:

§ Discrete: PRTG takes discrete values to calculate percentile results.
§ Continuous: PRTG interpolates between discrete values and bases the

calculation on interpolated values.
Data Files
Setting Description
Files in CSV / XML Define if you want to generate .csv and .xml files for data tables in the
Format report in addition to the .pdf file:
§ Do not include data files: PRTG does not generate .csv or .xml files for
the report. It only creates a .pdf file.
§ Include only .csv files: PRTG generates and stores .csv files in addition
to the .pdf file. The data files are only generated if the report uses a
report template that includes data tables.
§ Include only .xml files: PRTG generates and stores .xml files in addition
to the .pdf file. The data files are only generated if the report uses a
report template that includes data tables.
2782
Setting Description
§ Include all data files: PRTG generates and stores .csv and .xml files in
addition to the .pdf file. The data files are only generated if the report
uses a report template that includes data tables.
If you run PRTG in a cluster, the report does not generate data files if
you select All cluster nodes in the Cluster Node setting. Select a
failover node to get data files.
Report Comments
Setting Description
Introductory Comment Enter a custom text that the report displays at the top of the first page.
Enter a string or leave the field empty.
Final Comment Enter a custom text that the report displays below the last data table or
graph on the last page. Enter a string or leave the field empty.
Access Rights
Setting Description
settings.
settings.
settings are lost.
2783
Select Sensors Manually
Click the Select Sensors Manually tab to manually add sensors that you want to include in the report.
You see a split screen: On the left side, there is a list of objects that the report already contains, and on
the right side, you see your device tree. You can add objects to the report via drag-and-drop.
You can also add a report via the context menu 232 of an object. In this case, the selected object is
automatically included in the report.
Select Sensors Manually Tab
Action Description
Add items From the device tree on the right side, drag objects and drop them onto
the list on the left side. You can add entire probes, groups, devices, or
single sensors. PRTG adds each dropped object as a new list item.
The objects you drop on the left side are always added to the end of
the list, you cannot directly add objects in a different order.
Select channels If you add a sensor to the selection, you can specify the channels that
the report includes. By default, PRTG selects all channels. To exclude a
channel from the report, disable the check box in front of a channel name.
If you run PRTG in a cluster, you can only choose between single
channels if you select a specific Cluster Node in the report settings.
If you select All cluster nodes, the report contains only the primary
channel of each sensor.
2784
Action Description
Change order You can change the order of list items on the left side via drag-and-drop.
Click in the upper-right corner of a selected object, drag it to the
desired position, and drop it there.
Remove To remove any objects from the report, click next to the respective list
item, or select several list items while holding down the Ctrl key, then
click .
PRTG automatically saves your selection. There is no undo function.
The final report includes both manually selected sensors and sensors selected by tag.
Sensors Selected by Tag

Click the Sensors Selected by Tag tab to view all sensors that you added to the report by tag in section
Included Sensors of the report settings. This is for your information only, you cannot change sensors
here.
To edit the sensor selection, go to the Settings tab of the report and change the tags that the report uses
to include sensors. Additionally, you can also exclude sensors with specific tags there.
For sensors that you add by tag, PRTG automatically includes all channels in the report unless you use
a cluster and select All cluster nodes in the Cluster Node setting of the report. In this case, the report
only includes the primary channel of each sensor.
The final report includes both manually selected sensors and sensors selected by tag.
Comments
More
KNOWLEDGE BASE

Creating a PDF report does not work. What can I do?

2785
8.11 Maps
With the Maps feature, you can create dashboards with monitoring information in a customizable layout.
You can also make live data overviews publicly available.
Example of a Map
In this section:
§ Maps Menu 2787
§ Maps List 2787
§ Home Menu 2788
§ Working with Maps 2788
Introduction
There are a lot of different options for the implementation of maps:
§ Create network maps with status icons for each device.
§ Create views of your network that can be shown on network operations center screens.
§ Create network overviews that you can publish on the intranet for colleagues or the management.
§ Create custom views of the most important sensors in your monitoring setup.
§ Create Top 10 lists of the sensors of a specific group or device.
Map Technology
In technical terms, a map is a common HTML web page. A map can consist of the following elements:
2786
§ Map items including device icons, sensor status icons, graphs, data tables, sensor lists, connection
lines, geographical maps, or custom HTML code.
§ An optional background image in JPG, PNG, or GIF format, for example, your company logo or a
graphical view of your network.
Preconfigured Map
PRTG provides the preconfigured map Sample Dashboard that you can also edit or delete. The map is
only visible to administrators. Define a lower priority 227 for the map to not show it under Home in the
main menu bar 253 .
Maps Menu
Click Maps in the main menu bar to open an overview list of all maps. Hover over Maps to show other
options.
Option Description
All Open the Maps list where you can view or add custom views of your
network status and monitoring data.
Add Map Open a dialog to create a new map.
Select Map Hover over Select Map to show a list of your maps. Click a map to open
it.
Maps List
In the All view, you see a list of all maps. Click the name of a map to view it. Enable the check box next
to a map and use the quick action buttons:
§ Map Rotation ( ): Rotate 2807 between maps.
§ Clone ( ): Create a clone 2725 of this map.
§ Delete ( ): Delete this map.
§ Settings ( ): Open the map's settings 2802 .
Hover over and select Add Map from the menu to add a new map.
You can also define the priority of a map. Maps with a 5-star priority ( ) appear in the main menu
bar under Home so that you can directly select them. PRTG can show up to 10 entries in the Home
menu.
For more information, see section Home Menu 2788 .
2787
Home Menu
You can add any map to the Home menu in the main menu bar of the PRTG web interface. This way,
you can gain quick access to your most important maps.
If you open a map via the Home menu, it appears as a dashboard without the tabs that are available
when you open a map via the Maps menu. Furthermore, in contrast to a map that you open via a
URL, the map is embedded in the PRTG web interface with the global header area and page footer.
You can define whether a map appears in the Home menu via the priority setting:
Add Map to Home Menu
1. Open the Maps overview via the main menu bar (1).
2. In the overview list, look for the map that you want to add to the Home menu (2).
3. In the Priority column, select for the desired map (3).
The map appears in the Home menu (4). To immediately see the change, manually refresh the page with
F5.
You can include up to 10 map entries in the Home menu.
Every map with a 5-star priority ( ) appears as a menu item under Home.
PRTG provides a sample dashboard in the Home menu by default. You can remove the sample
dashboard and other dashboards from the menu by changing their priority to or lower.
Working with Maps

For more information on how to work with maps and on how to make the maps available to other people,
see the following sections:
§ Map Designer 2790
§ Maps Settings 2802
§ Map Rotation 2807
2788
More
PAESSLER WEBSITE
How to create dashboards in PRTG with the Maps feature in 5 steps

§ https://www.paessler.com/support/how-to/map-designer
2789
8.11.1 Map Designer
With the Map Designer feature, you can create custom web pages as maps, or dashboards, that
represent your network.
In this section:
§ Browser Compatibility 2790
§ Basic Design Concept 2790
§ Device Tree Section 2791
§ Properties Section 2793
§ Properties Object Types 2794
§ Edit Map Items 2796
§ Draw Connection Lines Between Items 2799
§ Snap To Grid 2801
§ Undo and Redo 2801
Browser Compatibility
Because of the map designer's extensive scripting capability, it is important that you use a compatible
browser when you edit maps. We recommend that you use Google Chrome 75. You can also use
Mozilla Firefox 67 or Microsoft Edge 79. The map designer is not fully compatible with earlier versions of
Internet Explorer or Opera browsers.
Basic Design Concept

Click the Map Designer tab to open the map editor. It might take a few moments to load. Here, you can
add or change map items to create your individual map.
2790
Map Designer General Layout
The map designer consists of three main sections:
§ The Device Tree section on the left side. Here you can select the object whose data you want to show
on the map.
§ The map design area in the middle that has the size in pixels that you specified in the map
settings 2803 .
§ The Properties section on the right side. Here you can define how a map item is displayed, for
example, as an icon or a data table.
Drag and drop any object from either side onto the map, or double-click an object. You always see all
changes immediately.
Device Tree Section

Use the Device Tree section to select the object whose data you want to show on the map. This can be
a probe, a group, a device, or a single sensor.
2791
Device Tree Section in the Map Designer
Action Description
Find an object To find the desired object, you have the following options:
§ Click at the beginning of a line to expand objects in the device tree and show
objects below probes, groups, and devices. Click to collapse the object again.
2792
Action Description
§ Enter a few characters into the Search box to search for names or parts of
names of objects in your configuration. You immediately get the search results.
Click to clear your search.
Drag-and-drop You can always drag any object from the device tree onto a free area of the map to
create a new map item.
If you drag the object onto an existing map item, the displayed device tree object is
replaced while the property and size stay the same.
Double-click Double-click an object in the device tree to add a new map item.
If you select a map item and double-click an object in the device tree, the map
designer replaces the map item.
Change size You can adapt the size of the Device Tree section. Drag the right border to the left
to make the section smaller. To enlarge the section, drag the right border to the
right.
Properties Section
Use the Properties section to define how to display the map item, for example, as an icon, a map, a
table, or a graph. Select the appearance of a map item from different categories.
2793
Properties Section in the Map
Designer
§ Hover over an object to get a live preview of it, if available.
§ Drag an object onto a free area of the map to create a new map item. If you drag the object onto an
existing map item, the property is replaced while the device tree object attributes and size stay the
same.
§ Double-click an object to add it to the map, or select an existing map item and double-click an object
to replace the map item.
If a specific Properties object is not available for a selected Device Tree object, you see a
corresponding note in the live preview of the Properties object.
Properties Object Types

Many different object types are available. Click one of the categories to show all available types.
2794
Object Type Description
Default Icons A, Default Icons B Choose from various icons that represent typical network devices
in the style of the PRTG web interface. Default icons from
category A also display object data. You can see the object name
and a sensor overview for the object. This indicates how many
sensors show a specific status. For some sensors, a mini graph
is shown as well.
Icons A, Icons B, Icons C Choose from various icons that represent typical network devices.
Icons from this category also display object data. You can see the
object name and a sensor overview for the object. This indicates
how many sensors show a specific status. For some sensors, a
mini graph is shown as well.
Icons A (Static), Icons B Choose from the same icons as in the category described above.
(Static), Icons C (Static) Here, only the icon is displayed without additional object data.
Static Images Choose from various free or public domain geographical maps from
different sources.
Use the category Geo Maps if you want to show geographical
maps that include monitoring locations.
The items in this category are independent from the selected
objects in the device tree.
Status Icons Choose from various sensor status icons in different styles. You
can see the object name and a sensor overview for the object.
This indicates how many sensors show a specific status. For
some sensors, a mini graph is shown as well. Additionally, you
can add traffic lights or the QR code of an object to your map. A
map item for an audible alert that plays a sound when the number
of alarms of the monitored object is > 0 is also available.
Your browser must support playing embedded sounds for the
status icon that includes an audible alert.
For more information, see the Knowledge Base: Which
audible notifications are available in the PRTG web interface
and in the PRTG app for desktop?
If you experience issues with audible notifications in Google
Chrome, see the Knowledge Base: Why are audible alerts in
public maps not working in Chrome?
Cluster These map items are only available if you run PRTG in a failover
cluster 132 . Choose between a map and a status table.
The Map item does not scale automatically. You need to
manually enlarge the item in the map design area.
2795
Object Type Description
If you do not have a cluster, you only see white boxes instead
of map previews.
Data Tables Choose from various table lists 221 that show sensors for the
selected object. You can also choose from several lists that only
show sensors in a specific status.
Device Tree Views Choose from various device tree views 178 , including gauges for the
selected object.
Status Donuts Choose from various status donuts that either show all alarms or
all sensor states for the selected object. These are the same
status donuts that you see on the Welcome page 161 .
Geo Maps These map items are only available if you enable the Geo
Maps 2741 feature and enter location information in the selected
device tree object's settings. Choose between a globe and a
geographical map.
If the Geo Maps feature is disabled, you only see white boxes
instead of map previews.
Graphs Choose from various graph styles that differ in font size and detail.
You can also select graphs that include a legend or sensor
states.
Shapes Choose from various geometrical shapes.

Top 10 Lists Choose from various tables that show the top 10 sensors in
specific categories like the highest bandwidth usage or the best
availability.
Custom HTML Use this property, for example, to add custom text 2799 , external
images, or applets to your map.
Drag the item to the map design area and select it to edit 2796 it.
You can then copy your custom code into the HTML Before and
HTML After fields.
Edit Map Items

Properties Section
2796
Click a map item to select it. You can then edit its attributes in the upper part of the Properties section.
Edit Map Items in the Properties Section
Property Description
Top Enter position values to directly position the item on the map. Enter a
positive integer.
Left
You can also use the mouse to move a map item.
Width Enter size values to give the item a predefined size. Enter a positive
integer.
Height
You can also use the mouse to resize a map item.
Layer Enter a layer value that defines if an item appears in front of or behind a
different item if the items overlap. The item with the higher value appears
in front. Enter a positive integer.
You can also use the context buttons 2798 of a map item to bring it an
item to the front ( ) or send it back one layer ( ).
External Link Enter the address of any web page. If you click the map item while you
view the map, PRTG opens the web page in a browser window. Enter the
full URL of an external website, for example, https://www.paessler.com,
or the address of a subpage of your PRTG installation, for example,
devices.htm.
To make a map interactive, you need to define a suitable public
access 2804 setting for the map.
2797
Property Description
HTML Before Enter custom HTML code to embed an object in the map. Any HTML
code you enter in these fields is added before or after the map item and
HTML After your HTML object is inserted into the map. For example, you can enter
<img src="https://media.paessler.com/common/img/logoclaim_r1.gif"> to
insert an image of a Paessler logo.
settings are lost.
Context Buttons
Hover over a map item to show its context buttons.
Edit Map Items via Context Buttons
Context Button Description
Bring to front Move this item one layer to the front. This is useful when you add several
items to a map that overlap each other.
Send to back Move the item one layer to the back. This is useful when you add several
items to a map that overlap each other.
Delete Delete the item.

The item is immediately deleted without notice. You cannot undo this
action.
You can also select the item and press the Delete key on your
keyboard.
Drop Connections Delete all connection lines 2799 to the item.
2798
Cursor Keys
Select a map item and use the cursor keys to move the item one pixel at a time. Hold down the Shift
key in combination with the cursor keys to move the object 10 pixels at a time.
Add Custom Text

You can add custom text with individual styling to your map with the Custom HTML Element.
For more information, see the Knowledge Base: How to add text to a map?
Draw Connection Lines Between Items

You can draw connection lines between any map items via drag-and-drop to indicate, for example,
network connections or a logical coherence between two items.
2799
Map w ith Connection Lines
§ Click the gray handle to the left of an item and drag it onto the item with which you want to create a
connection to create a connection line.
§ Hover over a connection line and click to delete it.
The map designer dynamically colors the lines between items depending on the status 184 of the
linked objects. A line is red, for example, if the linked objects both show the Down status.
Connection lines can also have two colors. For example, if one linked object shows the Down status and
the second linked object shows the Warning status, one half of the line is red and the other half is
yellow.
2800
Snap To Grid
With the Snap To Grid setting, you can define how map items are positioned when you add or remove
them via drag-and-drop.
Click at the bottom of the Device Tree section to enable Snap To Grid so that you can only place
items aligned with the grid. Click to disable Snap To Grid to place map objects freely.
Undo and Redo

You can undo previous changes to the map and its items by clicking (Ctrl+Z) at the bottom of the
Device Tree section. To redo actions, click (Ctrl+Y). You can undo and redo up to 50 changes when
you work on a map. Because PRTG saves changes persistently in your configuration, you can even
revert changes at a later point in time.
Both buttons are only available if they can apply, otherwise they are grayed out.
More
KNOWLEDGE BASE
Why are audible alerts in public maps not working in Chrome?

How to add text to a map?

Why does my browser show an unresponsive script warning while loading the Map Designer?
2801
8.11.2 Maps Settings
Use the maps tabs to access all functionalities and settings of a map.
Map Tabs
Settings
Click the Settings tab to open the general settings of a map.
In the Add Map dialog, not all of these settings are available. You can change the settings later via
the Settings tab.
Basic Map Settings
Setting Description
Map Name Enter a name to identify the map.

Security Context and Define the security context that the map uses for access to monitoring
Color Mode data. Select a user account from the dropdown list to define which
objects are visible on the map. The map only contains objects that the
selected user has the access rights 149 to view. By default, the security
context is the user account that creates the map.
2802
Setting Description
This setting also affects the color mode 2815 of public maps 2804 . PRTG
takes the color mode setting of the security context user account.
Time Zone Define the time zone that the map uses for all date-related settings.
Select a time zone from the dropdown list.
Filter by Tag This setting applies to table map objects. Enter one or more tags
separated by a space or comma to include sensors in map data tables.
Only sensors that have one of the specified tags appear in the tables,
including sensors that inherit 140 tags from parent objects. Enter a string
or leave the field empty.
For some map objects, for example for sunburst and treemap
objects, the tag filter applies only to probes, groups, and devices. If
you only enter tags of sensors, these map objects do not appear on the
map. Filtering sunburst and treemap objects with multiple tags might not
work properly and is not officially supported.
Use this setting with caution because it affects all tables of the map.
Map Layout
Setting Description
Map Width Define the width of the map in pixels. Enter an integer.
Map Height Define the height of the map in pixels. Enter an integer.
Automatic Scaling Define if you want the map to automatically adapt to your screen size:
§ Scale map view to fit browser size: The size of the map automatically
adapts to the size of your screen. We recommend that you use this
option if you display the map on different screens with different
resolutions.
This setting does not apply to the map designer.
§ Do not automatically scale map view: The map always uses the
specified width and height settings.
Background Image Define if you want to use a background image for the map:
§ Use a background image: Use a custom background image, for
example, your company logo.
2803
Setting Description
§ Do not use a background image: Use a background that shows the

color that you define in the Background Color setting.
Custom Image This setting is only visible if you select Use a background image above.
Click Select File and select an image from your system or network.
PRTG only supports images in JPG, PNG, and GIF format. The file
size must be smaller than 20 MB.
Background Color Select a background color for this map. Either enter a hex color code or
choose a color from the color selector. The hex color code field always
displays the defined color.
Map Access
Setting Description
Public Access Define who can view the map:

§ No public access: Do not allow public access to the map. Users who
want to view the map first need to log in to PRTG. They also need
sufficient access rights to the map.
§ Allow public access: Allow access to the map via a unique URL. The
URL contains a secret key that you can change. The map is an
interactive public map.
§ Allow public access but disable all links except for Geo Maps: Allow
access to the map via a unique URL. The URL contains a secret key
that you can change. If you select this option, all links on the map are
disabled so that you get a non-interactive public map.
It is not possible to disable the links in map objects that contain an
embedded geographical map 2741 . As a workaround, place an
empty, transparent square object over the Geo Map object and link
it to an unrelated URL.
PRTG displays maps with public access in the color mode defined
for the security context user account.
Secret Key This setting is only visible if you select Allow public access or Allow
public access but disable all links except for Geo Maps above.
The secret key is automatically generated. It is part of the public URL for
the map. You can also enter a customized string.
2804
Setting Description

For more information on public access, see section Get
HTML 2805 .
The characters comma (,) and colon (:) are not allowed in the secret
key field.
Access Rights
Setting Description
settings.
settings.
settings are lost.
Get HTML
Your map is a standard HTML page. You can make it available to other people via a unique URL.
Depending on the map's Public Access setting 2804 , a visitor needs to provide login credentials for PRTG
to view the map, or they immediately see the map.
You have different options to link to the map:
§ Option 1: Link To The Map With Required Login

A user who wants to view the map via the shown URL first needs to log in to PRTG.
In the URL, PRTG usually specifies the IP address under which the page is reachable. If a
network address translation (NAT) is set in your firewall, or if you want to use a domain name or a
name from a dynamic Domain Name System (DNS) service for public access, customize the URL
according to your needs.
2805
§ Option 2: Link To The Map Without A Login
People who want to view the map via the shown URL do not need login credentials. Allow public
access to the map to make it available to the public.
In the URL, PRTG usually specifies the IP address under which the page is reachable. If a NAT is
set in your firewall, or if you want to use a domain name or a name from a dynamic DNS service for
public access, customize the URL according to your needs.
§ Option 3: Show the Map on Other Webpages via an Iframe
Here you can find the HTML code to embed an iframe in your web page. It includes a URL for direct
access to the map. Allow public access to the map to make it available to the public.
In the URL, PRTG usually specifies the IP address under which the page is reachable. If a NAT is
set in your firewall, or if you want to use a domain name or a name from a dynamic DNS service for
public access, customize the URL according to your needs.
Comments
History
Delete
You can delete a map at any time. To do so, click in the upper-right corner of the screen.
More
KNOWLEDGE BASE

2806
8.11.3 Map Rotation
With the Map Rotation feature, you can rotate between several maps on one page. This is similar to a
slide show.
Map Rotation Setup

To configure your custom map rotation, take the following steps:
Map Rotation Setup
1. Open the Maps overview from the main menu bar.

2. Select the maps that you want to rotate by enabling the check box next to the respective maps. The
multi-edit 2729 menu appears.
3. Click .
4. PRTG now rotates the selected maps on a new page in a specific interval.
5. You can change the interval until a new map appears. Hover over in the lower-right corner and
choose from 10s, 30s, 60s (seconds), 10m (minutes), and Refresh (now).
To view the maps that you specified for the map rotation, you need login credentials for PRTG.
Public Map Rotation

You can also set up a public map rotation that you can use without login credentials. For this purpose,
you need to create a custom URL that includes the map IDs and the maps' secret keys:
1. In the Public Access settings 2804 of all maps that you want to include in the map rotation, select
Allow public access. The Secret Key setting appears.
2. Note the secret keys of all maps that you want to include in the map rotation.
3. Find the map IDs and note them as well. To find the ID of a map, open the map with your browser.
The map ID is included in the URL of the map as the value of the parameter id. In the URL
https://<yourprtgserver>/map.htm?id=2124, for example, the number 2124 is the needed ID.
2807
4. Create the public map rotation URL. The complete URL has the following format:
https://yourprtgserver/public/mapshow.htm?
ids=mapid1:secretkey1,mapid2:secretkey2,mapid3:secretkey3.
Make sure that you connect each map ID and the respective secret key with a colon, and that
you separate each mapid:secretkey token from the next mapid:secretkey token with a comma.
This is an example URL for the public rotation of two maps with the map IDs 9507 and 9358:
https://prtg.example.com/public/mapshow.htm?ids=9507:4049BEA1-B89C-4B5D-ACC4-
3C8E00566EB8,9358:718D3CE1-DF00-4B92-AE8A-E0253B912C37
5. Open the URL in your browser to start the public map rotation.
6. You can change the interval until a new map appears. Hover over in the lower-right corner and
choose from 10s, 30s, 60s (seconds), 10m (minutes), and Refresh (now).
2808
8.12 Setup
In the setup settings of the PRTG web interface, you can define almost all system settings for PRTG.
However, you need to define some of the machine-oriented settings via two Windows administration tools
(see section Others 2810 below).
Click Setup in the main menu bar 265 to show the available options.
Some setup options are only available for PRTG Network Monitor (marked with ), so you cannot
use these with PRTG Hosted Monitor.
Some setup options are only available for PRTG Hosted Monitor (marked with ), so you cannot
use these with PRTG Network Monitor.
In this section:
ú My Account 2811
ú Notification Templates 2818
ú Notification Contacts 2851
ú Schedules 2856
ú API Keys 2861
§ System Administration 2865
ú Manage Subscription
ú User Interface 2865
ú Monitoring 2879
ú Notification Delivery 2887
ú Core & Probes 2897
ú User Accounts 2911
ú User Groups 2922
ú Administrative Tools 2928
ú Cluster 2933
ú Single Sign-On 2935
ú Maintainer Mode 2941
§ PRTG Status 2945
ú System Status 2945
ú Cluster Status 2970
§ License Information 2972
§ Auto-Update 2979
2809
§ Optional Downloads 2984
§ Help and Support Center 2986
§ Contact Support 2987
Others
There are some settings that you need to make in the PRTG Administration Tool 3050 .
For more information, see sections PRTG Administration Tool on PRTG Core Server Systems 3051
and PRTG Administration Tool on Remote Probe Systems 3077 .
2810
8.12.1 Account Settings
To open the account settings of the user, select Setup | Account Settings from the main menu bar 265 .
Select the various tabs to change the different settings.
Account Settings Tabs
In this section:
§ My Account 2811
§ Notification Templates 2818
§ Notification Contacts 2851
§ Schedules 2856
§ API Keys 2861
8.12.1.1 My Account
On the My Account tab, you can define and edit settings for the user account. All settings are specific to
the user account.
If 15 minutes (900) seconds have passed since your last credential-based login and you open a
setup page from a different setup page, PRTG asks you to enter your credentials again for security
reasons. A dialog box appears. Enter your Login Name and Password and click OK to continue.
In this section:
§ PRTG App Login 2811
§ User Account Settings 2812
§ API Access 2813
§ Group Membership 2814
§ PRTG Web Interface 2815
§ Ticket System 2817
PRTG App Login
PRTG App Login
2811
Setting Description
QR Code Click Show QR Code for PRTG App Login to display the QR code and to
copy your account settings to a PRTG app 2998 .
User Account Settings
Setting Description
Login Name Enter a login name for the user account.

The login name must not contain the following invalid characters: " / \
[]:;|=,+*?<>
Display Name Enter a display name that you recognize. PRTG uses it for display
purposes only, for example on the Welcome page.
Primary Email Address Enter the primary email address. This is the email address that PRTG
uses by default for the ticket system, including important system
messages, and password recovery.
Make sure that your email client can show HTML emails, otherwise
you cannot read emails from PRTG.
Password Define whether to change the password for the user account:
§ Do not change the password
§ Specify a new password
For security reasons, PRTG does not display the password.
2812
Setting Description
If you specify a new password, enter the old password, then enter the
new password twice.
The new password must be at least 8 characters long. It must
contain a number and a capital letter.
Do not use leading or trailing whitespaces in the new password.
Passhash Click Show passhash to display the passhash for the user account. This
is necessary for authentication for the PRTG API 3094 .
API Access
These settings are only available in PRTG Hosted Monitor.
API Access
Setting Description
API User Name Shows the API user name of the user account. This is necessary for
authentication for the PRTG API.
API Passhash Click Show passhash to display the API passhash of the user account.
This is recommended for authentication for the PRTG API.
Generate API Passhash Click Generate new passhash to reset the passhash of the user.
2813
Account Settings
Account Settings
Setting Description
Primary Group Select the primary group for the user account from the dropdown list.
Every user account must be a member of a primary group to make
sure there is no user account without group membership.
Membership in other user groups is optional.
You cannot change the primary group of Active Directory users.
Users that you add via Active Directory integration 3091 can only have
the respective Active Directory group as their primary group.
Status This setting is for your information only. You cannot change it.
Last Login Shows the time stamp of the last login of the user account.
Group Membership
Group Membership
2814
Setting Description
Member of Shows the user groups that the user account is a member of. You can
define access rights to device tree objects, libraries, maps, reports and
the ticket system at group level.
PRTG Web Interface
PRTG Web Interface
Setting Description
Automatic Refresh Define if you want PRTG to automatically reload web pages in the PRTG
web interface for the user:
§ Automatically refresh pages (recommended): PRTG automatically
refreshes single page elements on web pages in the PRTG web
interface.
§ Do not automatically refresh pages: PRTG does not automatically
refresh single page elements on web pages in the PRTG web interface.
Refresh Interval (Sec.) This setting is only visible if you select Automatically refresh pages
(recommended) above.
Enter the number of seconds that PRTG waits between two refreshes.
We recommend that you use 30 seconds or more. The minimum value is
20 seconds. The maximum value is 600 seconds.
2815
Setting Description
Shorter refresh intervals create more CPU load on the probe system.
If you experience load issues while using the PRTG web interface (or
maps 2786 ), set a longer refresh interval.
Audible Alarms Define whether PRTG plays an audible alarm on web pages in the PRTG
web interface when there is a new alarm 2811 :
§ Do not play audible alarms: PRTG does not play sound files on any
web pages.
§ Play audible alarms on dashboard pages only: When there is a new
alarm, PRTG plays a predefined sound on dashboard 253 pages only.
The sound is played with every refresh of the dashboard page if there is
at least one new alarm.
§ Play audible alarms on all pages: When there is a new alarm, PRTG
plays a predefined sound on all web pages. PRTG plays the sound with
every page refresh if there is at least one new alarm.
PRTG only plays audible alarms if the New Alarms value in the global
header area 172 of the PRTG web interface is greater than 0 after a
page refresh. PRTG does not consider the number of old alarms.
For more information, see the Knowledge Base: Which audible
notifications are available in the PRTG web interface and in the PRTG
app for desktop? and Why are audible alerts in public maps not working
in Chrome?
Home Page URL Define the user's default home page in the PRTG web interface. This is
the page that the user sees after logging in or when selecting Home 253
from the main menu. Enter a PRTG-internal web page.
Time Zone Define the time zone for the user account. Depending on the time zone
that you select, PRTG shows the local time zone of the user account in
all data tables and graph legends.
PRTG receives the Coordinated Universal Time (UTC) from the
system time of the PRTG core server for this purpose.
If you get a warning message about differing time zones, see the
Knowledge Base: Why do I get a warning message when time zones
differ?
Date Format Select the date format for the user:

§ Use default settings: Use the date format of the PRTG core server
system.
§ DD.MM.YYYY HH:MM:SS (24h)
§ DD.MM.YYYY HH:MM:SS (A.M./P.M.)
§ MM/DD/YYYY HH:MM:SS (24h)
2816
Setting Description
§ MM/DD/YYYY HH:MM:SS (A.M./P.M.)
§ YYYY-MM-DD HH:MM:SS (24h)
§ YYYY-MM-DD HH:MM:SS (A.M./P.M.)
This setting takes effect after the next login.
Color Mode Select a color mode for the PRTG web interface:
§ Light
§ Dark
Ticket System
Ticket System
Setting Description
Email Notifications Define if the user receives emails from the ticket system:
§ Receive an email when a ticket changes:
§ The user receives an email each time a ticket is assigned to the user or
to the user group they are a member of, or if a ticket is changed.
If the user edits tickets that are assigned to them or the user group
they are a member of, or if they assign a ticket to themselves or
their user group, they do not get an email.
§ Do not receive any emails from the ticket system: The user does not
receive any emails from the ticket system.
Save your settings. If you leave the page, all changes to the settings are lost.
More
KNOWLEDGE BASE

2817

Why do I get a warning message when time zones differ?

Others
There are some settings that you must define in the PRTG Administration Tool 3050 . For more information,
see sections:
§ PRTG Administration Tool on PRTG Core Server Systems 3051
§ PRTG Administration Tool on Remote Probe Systems 3077
8.12.1.2 Notification Templates
On the Notification Templates tab, you can define and edit user account-specific notifications. You can
use notification templates to trigger notifications for specific sensor states 184 and values.
Notification Templates Tab
2818
In this section:
§ Note 2819
§ Overview 2819
§ Notification Template Settings 2820
§ Basic Settings 2821
§ Notification Summarization 2822
§ Notification Methods 2825
Note
and their content.
PRTG web interface.
Overview
Click the Notification Templates tab to show a list of all notification templates, what actions they perform,
and their status (active or paused). To edit a notification template, enable the check box next to the
notification template and choose from the following options.
2819
Option Description
Send test notification ( Triggers the notification immediately for testing purposes.
)
When you test notifications, PRTG does not resolve the
placeholders, but rather sends the original variables instead.
Used by ( ) Show all objects that trigger the notification.
Pause ( ) Pauses the notification.

If you manually pause 230 a notification, PRTG does not send
messages when this notification is triggered.
Resume ( ) Resumes the notification.
Clone ( ) Creates a clone of the notification.
Delete ( ) Deletes the notification.

You cannot delete predefined notifications.
Settings ( ) Opens the settings 2820 of a notification template.
You can also use the quick action buttons Send test notification ( ), Used by ( ), Pause ( ) or
Resume ( ) next to the status of a notification template.
Notification Template Settings

Hover over and select Add Notification Template from the menu to add a new notification template.
You can also click the name of a notification template to edit it.
When a user with administrative rights creates a new object, only other users with administrative
rights can view or edit the new object by default. When a read/write user creates a new object, all
members of the read/write user's primary group can view and edit the new object as well. This behavior
applies to libraries 2748 , maps 2786 , reports 2764 , notification templates 2818 , and schedules 2856 . For more
information, see section Access Rights Management 149 .
2820
Basic Settings
Basic Settings
Setting Description
Template Name Enter a name to identify the notification template.

Status Select the status of the notification template:

§ Started (default): PRTG executes the notifications that are defined in
the notification template whenever it is triggered.
§ Paused: PRTG does not execute any notifications that are defined in
the notification template.
Schedule Define if you want to use a schedule to activate a notification template

only during specific time spans:
§ None
§ Saturdays
§ Sundays
§ Weekdays
2821
Setting Description
§ Weekends
Use this setting to pause notifications, for example, during regular

maintenance periods or system restarts.
The overall status of the notification template must be Started
(default) to apply any schedule settings.
For more information, see section Schedules 2856 .
Notification Handling Define how PRTG handles notifications that are triggered during a
during Scheduled Pause scheduled pause:
§ Collect notifications and send them when reactivated: PRTG collects all
notifications that are triggered during a scheduled pause and sends
them all out once the paused status ends.
§ Discard notifications during paused status: PRTG discards all
notifications that are triggered during a scheduled pause.
If you manually pause a notification, PRTG never collects
notifications that are triggered while the notification is paused.
Notification Summarization
Notification Summarization
2822
Setting Description
Method Define if and how PRTG collects and summarizes several notifications
into one or more messages with a maximum of 1,000 characters:
§ Always notify immediately, never summarize: PRTG always sends out
one notification for each notification trigger that it receives as soon as
possible, for example, immediately.
§ Send first down message immediately, then summarize: When PRTG

receives several down triggers, it sends the first notification
immediately, then it continues to summarize notification triggers into
one message, regardless of the sensor status.
§ Send first down and up message immediately, then summarize: When
PRTG receives several down or up triggers, it sends each first
notification immediately, then it continues to summarize notification
triggers into one message, regardless of the sensor status.
§ Send all down messages immediately, summarize the others: When
PRTG receives several down triggers, it sends out one notification for
each trigger that it receives, but it summarizes notifications for all non-
down triggers into one message.
§ Send all down and up messages immediately, summarize the others:
When PRTG receives several down or up triggers, it sends out one
notification for each trigger that it receives, but it summarizes the
notifications for all non-down and non-up triggers into one message.
§ Always summarize notifications, regardless of type: When PRTG
receives several notification triggers, it summarizes the notifications,
regardless of the kind of notification trigger that it receives.
The maximum number of notifications (see below) still applies.
Regardless of the option that you choose, PRTG never summarizes
notifications of the types Send Slack Message, Send Microsoft
Teams Message, Execute HTTP Action, Execute Program, and Assign
Ticket because it always sends them immediately. PRTG can summarize
the messages of all other notification types.
'first down' and 'first up' messages refer to the notification trigger
condition and the clear condition respectively. You can also define
warning or unusual states as notification trigger conditions or even
thresholds or other triggers notification summarizations. The condition
clear triggers, if applicable, are defined in the respective notification trigger
conditions as well. The notification triggers all qualify as 'first down' or 'first
up' messages.
PRTG collects up to 25 single notifications for one summarization
and sends out the message as soon as this number is reached (or
when the gathering time passes). If PRTG receives more than 25
notifications within the defined time span, you receive more than one
message with up to 25 entries each. For example, if PRTG collects 74
notifications, this results in 3 summarized messages with 25, 25, and 24
collected notifications.
2823
Setting Description
Subject for Summarized Define a subject that PRTG includes when it sends summarized
Email or SNS Messages notifications. The default subject is [%sitename%] %summarycount
Summarized Notifications.
PRTG only uses the subject for the notification methods Send Email
and Send Amazon Simple Notification Service Message.
You can use placeholders. For more information, see section

Placeholders for Notifications 3361 .
Time Span for Define a time span in minutes to define how long PRTG collects
Summarizing Messages notifications for summarization. Enter an integer.
(in Minutes)
If you enter a long time span, for example, 60 minutes, PRTG
collects notifications for one hour before it sends them out
summarized unless other features (see above) require an earlier message
dispatch.
Access Rights
Access Rights
Setting Description
User Group Access Define the user groups that have access to the notification template. You
see a table with user groups and group access rights. The table contains
all user groups in your setup. For each user group, you can choose from
the following group access rights:
§ No access: Users in this user group cannot see or edit the notification
template. The object does not show up in lists.
§ Read access: Users in this user group can see the notification
template and view its settings.
§ Write access: Users in this user group can see the notification
template and view and edit its settings. However, they cannot edit its
access rights settings.
§ Full access: Users in this user group can see the notification template,
view and edit its settings, and edit its access rights settings.
2824
Notification Methods
With the following settings, you can add one or more methods for how PRTG sends out a notification
message. You can choose one method or combine several methods. Whenever the notification is
triggered, PRTG sends out messages or performs actions for all configured methods at once.
To select a notification method, click in front of it. You can then see and set the options as
described in this section. The following notification methods are available:
Some notification types are only available for PRTG Network Monitor (marked with ). You cannot
use these with PRTG Hosted Monitor.
§ Send Email 2825
§ Add Entry to Event Log 2828
§ Send SMS/Pager Message 2829
§ Execute HTTP Action 2831
§ Execute Program 2833
§ Send Syslog Message 2834
§ Send SNMP Trap 2835
§ Send Amazon Simple Notification Service Message 2837
§ Assign Ticket 2838
§ Send Push Notification 2840
§ Send Microsoft Teams Message 2841
§ Send Slack Message 2843
§ Send MQTT Publish Notification 2845
§ Send OPC UA Notification 2848
Send Email
This notification method uses notification contacts to deliver the email notifications. Set up
notification contacts in advance in the notification contacts 2853 settings.
2825
Send Email
Setting Description
Sender Define which sender email address and sender name appear in the FROM part of
the email notifications:
§ Default: Use the default sender email address and sender name from the
notification delivery 2888 settings.
§ Custom: Enter a custom sender email address and sender name.
Sender Email This setting is only visible if you select Custom above.
Address
Enter an email address to use as the sender of the email notifications.
If you enter a custom sender email address, it overrides the email address in
the notification delivery 2889 settings.
The outgoing Simple Mail Transfer Protocol (SMTP) server in the notification
delivery settings must allow the email address so that it can deliver email
notifications.
Sender Name This setting is only visible if you select Custom above.
Enter a sender name to use as the sender of the email notifications.

If you enter a custom sender name, it overrides the sender name in the
notification delivery 2889 settings.
2826
Setting Description
Send to User Select a user account to send the email notifications to. PRTG sends the email
notifications to every active email notification contact 2853 for this user account.
Leave None to not use this option.
Read/write users can send notifications to any user that is a member of the
same user group as the read/write user.
Send to User, Send to User Group, and Send to Email Address all work
simultaneously. Because of this, you can define more than one user as a
recipient of this notification. PRTG sends the email notifications to the active
email notification contacts 2853 of the user that you select, to the active email
notification contacts of all members of the user group that you select, and to all
email addresses that you enter under Send to Email Address.
Send to User Select a user group to send the email notifications to all members of this user
Group group. PRTG sends the email notifications to every active email notification
contact 2853 of every user in the user group. Leave None to not use this option.
If you select a user group and a specific member of this user group as
recipients, the user only receives one single email. This also applies if you
enter an individual email address under Send to Email Address that is already
defined as an email notification contact of the selected user.
If you define individual email addresses under Send to Email Address, define
a specific user account under Send to User, and define a user group here,
PRTG sends the message to the individual email addresses, to the individual
user, as well as to the members of the selected user group. In all cases, PRTG
sends one message with all recipients in the To part of the email.
Read/write users can send email notifications to all user groups that they are
members of.
Send to Email Enter one or more email addresses to which PRTG sends the email notifications.
Address If you enter more than one email address, separate them with commas. Leave
this field empty to only send email notifications to the email notification contacts
of the user or to the members of the user group you choose above.
We recommend that you use Send to User and/or Send to User Group
instead because you can then manage the notification contacts of users.
2827
Setting Description
Subject Enter the subject of the email notifications. The default subject is [%sitename] %
device %name %status %down (%message).
You can use placeholders. For more information, see section Placeholders
for Notifications 3361 .
Format Define the kind of email that PRTG sends when the notification is triggered:
§ HTML: PRTG uses the default HTML email template for the message part of the
email.
Make sure that your email client can show HTML emails, otherwise you
cannot read emails from PRTG.
§ Text: PRTG uses the default plain text email template for the message part of
the email.
§ Custom text: PRTG uses custom plain text for the message part of the email.
Define a custom text below.
Custom Text This setting is only visible if you select Custom text above.
Enter the desired message for this email notification in plain text format. You can
use placeholders here.
For more information, see section Placeholders for Notifications 3361 .
Priority Define the priority that PRTG sets for the email:
§ Very high
§ High
§ Normal
§ Low
§ Very low
Most email clients can show this priority flag.
HTTP Version Define the HTTP version that PRTG uses to send the email:
§ HTTP 1.1 (default): Use HTTP version 1.1.
Add Entry to Event Log

2828
Add Entry to Event Log
Setting Description
Log File Define the log file to which PRTG adds an event:
§ Application: PRTG adds an entry to the Application log file under
Windows Logs in the event log
§ PRTG Network Monitor: PRTG adds an entry to the PRTG Network
Monitor log file under Applications and Services Logs in the event log.
Event Source This setting is only visible if you select Application above.
Enter the source for the event. This is usually the name of the application.
Event Type Select the type of the event:

§ Error: An event that indicates a significant problem such as loss of data
or loss of functionality. For example, if a service fails to load during
startup, an Error event is logged.
§ Warning: An event that is not necessarily significant, but might indicate
a possible future problem. For example, when disk space is low, a
Warning event is logged.
§ Information: An event that describes the successful operation of an

application, driver, or service. For example, when a network driver loads
successfully, it might be appropriate to log an Information event.
Message Define the message that PRTG writes in the event log. The default
message is [%sitename] %device %name %status %down (%message).
To reset this field to the default value, enter only an asterisk (*).
Send SMS/Pager Message

You must first set up this notification method in the Notification Delivery 2887 settings.
This notification method uses notification contacts to deliver the SMS/pager messages. Set up
notification contacts in advance in the notification contacts 2853 settings.
2829
This notification method uses the central proxy settings that you define for the PRTG core server.
For more information, see section Core & Probes 2898 (section Proxy Configuration).
Send SMS/Pager Message
Setting Description
Send to User Select a user account from the dropdown list. PRTG sends the
SMS/pager message to every SMS notification contact 2853 for the user
account. Leave None to not use this option.
Send to User Group Select a user group from the dropdown list. PRTG sends the SMS/pager
message to every SMS notification contact for every member of the user
group 2922 .Leave None to not use this option.
If you select a user group and a specific member of this user group
as recipients at the same time, this user receives the SMS/pager
message only once. This also applies if you enter an individual phone
number below that is already defined as an SMS notification contact for
the selected user.
Send to Phone Number Enter a phone number to send the SMS/pager message to. If you enter
more than one phone number, use commas as separators.
The format depends on the SMS provider. Usually, you use a plus
sign (+), followed by the country code and the number. For example,
+1555012345.
Make sure that the number format meets the requirements of the
SMS provider or the hardware that you use in combination with an
application programming interface (API) call. Sometimes, a plus sign is
not required. The wrong format might result in undelivered messages.
We recommend that you use Send to User and/or Send to User
Group instead because you can then manage the notification
contacts of users.
Message Define the SMS/pager message. The default message is [%sitename] %

2830
Setting Description

HTTP Version Define the HTTP version that PRTG uses to send the SMS/pager
message:
Execute HTTP Action

Regardless of the Notification Summarization method that you use, PRTG always sends
notifications of the type Execute HTTP Action immediately. PRTG never summarizes them.
This notification method uses the central proxy settings that you define for the PRTG core server.
For more information, see section Core & Probes 2898 (section Proxy Configuration).
For more information, see section Custom Notifications 3156 . You can find ready-to-use custom
notifications in the PRTG Sensor Hub, see below 2850 .
Execute HTTP Action
Setting Description
URL Enter the URL that PRTG sends the request to.
HTTP notifications work with or without Secure Sockets Layer (SSL).
2831
Setting Description
SNI Handling Define if PRTG sends the Server Name Indication (SNI) extension to the
Transport Layer Security (TLS) protocol along with the HTTP request:
§ Do not send SNI (default): PRTG does not send the SNI when it
executes the HTTP action.
§ Send SNI: PRTG sends the SNI when it calls the target URL. Specify
the SNI below.
SNI Name This setting is only visible if you select Send SNI above.
Enter the SNI name that the endpoint configuration requires. Usually, this
is the fully qualified domain name (FQDN) of the virtual host.
HTTP Method Select the HTTP method that the notification uses:
§ GET (default): Use the GET method.
§ POST: Use the POST method.
§ PUT: Use the PUT method.
§ PATCH: Use the PATCH method.
Payload This setting is only visible if you select POST, PUT, or PATCH above.
Enter a payload. The payload is the data that PRTG transmits to the
URL.
You cannot use Extensible Markup Language (XML) or JavaScript
Object Notation (JSON).
Only the content type application/x-www-form-urlencoded is

supported.
You can use line breaks.
HTTP Version This setting is only visible if you select POST above.
Select the HTTP version that PRTG uses to execute the HTTP action:
Make sure that the target supports the HTTP version that you select.
2832
Execute Program
notifications of the type Execute Program immediately. PRTG never summarizes them.
To remotely run PowerShell scripts, make sure that you set the according Execution Policy. For
more information, see the Knowledge Base: PowerShell 32 bit and 64 bit and Execution Policy
For more information, see section Custom Notifications 3156 . You can find ready-to-use custom
notifications in the PRTG Sensor Hub, see below 2850 .
Execute Program
Setting Description
Executable File Select an executable file from the list. PRTG runs it every time the
notification is triggered.
You see the files that are in the corresponding \Notifications\EXE
subfolder of the PRTG program directory 3218 . For files to appear in
this list, store them as .bat, .cmd, .exe, .com, .ps1, or .vbs.
In a cluster, copy the files to every cluster node. This makes sure
that PRTG can execute the notification even when the master node
fails. If your custom notification executes an external program, install it on
all cluster nodes as well.
Parameters Enter the parameters that the notification passes to the executable. For
example, if you use a batch file that contains a %1 variable, you can
provide a value for this variable. The default parameters are [%sitename]
%device %name %status %down (%message).
2833
Setting Description

section Escape Special Characters and Whitespaces in Parameters 3348
for details.
Domain or Computer Enter a Windows authority if you want to use a different security context
Name for the program than the security context of the PRTG probe service.
User Name Enter the user name for Windows access.
Password Enter the password for Windows access.
Timeout (Sec.) Enter a timeout in seconds. After this time passes, PRTG stops the
process if it is still running. Enter an integer.
Send Syslog Message

Send Syslog Message
Setting Description
Host/IP Address Define the IP address or the Domain Name System (DNS) name of the
system that runs the syslog server.
You can receive and analyze syslog messages with the Syslog
Receiver sensor.
Syslog Port Enter the port that PRTG sends the syslog messages to. The default port
is 514.
You can only use the User Datagram Protocol (UDP).
2834
Setting Description
Facility Define the facility of the syslog messages:

§ User-level messages
§ Local use 0-7
Encoding Define the encoding of the syslog messages that PRTG sends to the
syslog receiver:
§ ANSI
§ UTF-8
Make sure that the syslog receiver supports the encoding that you
select.
Message Define the syslog message. The default message is [%sitename] %

Syslog Message Severity Status
Depending on the status of the sensor that triggers the syslog notification, PRTG automatically sets
the Severity level of the syslog messages.
Status Severity level
Notice (5)
Up
Warning (4)
Warning
Error (3)
Down
Send SNMP Trap

For more information about the object identifiers (OID) that PRTG uses in the content of the Simple
Network Management Protocol (SNMP) traps, see the Knowledge Base: Is it possible to send
SNMP traps using PRTG?
2835
Send SNMP Trap
Setting Description
Host/IP Address Define the IP address or DNS name of the system that runs the trap
receiver.
You can receive and analyze SNMP trap messages with the SNMP
Trap Receiver sensor.
SNMP Port Enter the port on which PRTG sends trap messages. The default port is
162.
Community String Enter the community string of the device. The default community string is
public. Enter a string or leave the field empty.
Custom Trap Code Enter a code to identify the purpose of the trap. The default trap code is 0.
Enter an integer.
Message ID Enter an ID to identify the origin of the trap.Enter an integer. PRTG sends
it on the OID 1.3.6.1.4.1.32446.1.1.1.
Message Define the trap message.

Agent IP Define the IP address of the agent. Leave this field empty to use the IP
address of the PRTG web server.
2836
Setting Description
Include Sensor ID Define if PRTG should include the sensor ID of the sensor that triggers
the notification:
§ Do not include sensor ID (default): Do not include the sensor ID with the
notification message.
§ Include sensor ID: Include the sensor ID with the notification message.
PRTG sends it on the OID 1.3.6.1.4.1.32446.1.1.5.
Send Amazon Simple Notification Service Message
Send Amazon Simple Notification Service Message
Setting Description
AWS Access Key ID Enter your access key ID from aws.amazon.com. Enter a string.
AWS Secret Access Enter your secret access key from aws.amazon.com. Enter a string.
Key
Location Define the location of your Amazon service:

§ Africa (Cape Town)
§ Asia Pacific (Hong Kong)
§ Asia Pacific (Mumbai)
§ Asia Pacific (Osaka)
§ Asia Pacific (Seoul)
2837
Setting Description
§ Asia Pacific (Tokyo)
§ Canada (Central)
§ China (Beijing)
§ China (Ningxia)
§ Europe (Frankfurt)
§ Europe (Stockholm)
§ Europe (Milan)
§ Europe (Ireland)
§ Europe (London)
§ Europe (Paris)
§ Middle East (Bahrain)
§ South America (São Paulo)
§ US East (Ohio)
§ US West (Oregon)
Amazon Resource Name Enter the Amazon resource name. Enter a string.
Subject Enter the subject of the Amazon Simple Notification Service (SNS)
The maximum length for the subject is 202 characters. PRTG ignores
characters that exceed this length.
Message Define the SNS message. The default SNS message is [%sitename] %
PRTG only sends the message if you use email-based notifications
delivered by Amazon SNS. For SMS delivery, PRTG only sends the
subject and ignores the message because of SMS size restrictions.
Assign Ticket
notifications of the type Assign Ticket immediately. PRTG never summarizes them.
2838
For more information about the ticket system, see section Tickets 216 .
Assign Ticket
Setting Description
Assign to User Group or Specify whether to assign the notification ticket 216 to a user group or to
User a single user:
§ To user group: Assign the notification ticket to a user group.
§ To user: Assign the notification ticket to a single user.
User Group Select the user group to which PRTG assigns the notification ticket.
Read/write users can assign tickets to all user groups that they are
a member of as well as to administrators and individual users that
are members of the same user group as the read/write user.
User Select the user to which PRTG assigns the notification ticket.
Read/write users can assign tickets to all user groups that they are
a member of as well as to administrators and individual users that
are members of the same user group as the read/write user.
Subject Enter the subject of the notification ticket. The default subject is %device
%name %status %down (%message).
Content Enter the message of the notification ticket. The default message is
Sensor: %name
Status: %status %down
2839
Setting Description
Date/Time: %datetime (%timezone)

Last Result: %lastvalue
Last Message: %message
Probe: %probe
Group: %group
Device: %device (%host)
Last Scan: %lastcheck

Last Up: %lastup
Last Down: %lastdown
Uptime: %uptime
Downtime: %downtime
Cumulated since: %cumsince
Location: %location
When Condition Clears Define how PRTG handles the notification ticket when the defined trigger
condition clears:
§ Close the notification ticket (recommended): Automatically close the
notification ticket if the trigger condition is not met anymore.
§ Do not close the notification ticket: Do not close the notification ticket
after the condition clears.
Send Push Notification

Push notifications only work with the apps PRTG for Android 2999 and PRTG for iOS 2998 . You must
activate push notifications in the settings of the app first. For more information about the setup, see
the Knowledge Base: How can I use push notifications with PRTG?
This notification method uses notification contacts to deliver push notifications. Set up notification
contacts in advance in the notification contacts 2853 settings.
The PRTG core server needs to communicate with the PRTG Cloud on port 443 to send push
notifications. It uses https://api.prtgcloud.com:443, which is the same as for the Cloud HTTP v2
sensor, the Cloud Ping v2 sensor, and support tickets 2987 .
Send to User and Send to User Group both work simultaneously. Because of this, you can define
more than one user as a recipient of push notifications. PRTG sends push notifications to the active
push notification contacts 2853 of the user that you select, and to the active push notification contacts of
all members of the user group that you select.
2840
Send Push Notification
Setting Description
Send to User Select the user that PRTG sends push notifications to. PRTG sends the
push notifications to each active push notification contact of the user.
Leave None to not use this option.
You can edit push notification contacts of a user in the Notification
Contacts 2853 settings and also activate push notifications in the
Android or iOS app with the user.
Send to User Group Select the user group that PRTG sends push notifications to. PRTG
sends the push notifications to each active push notification contact of
every member of the group. Leave None to not use this option.
If you select a user group and a specific member of the group as
recipients at the same time, the user receives the text message only
one time.
You can edit user groups in the User Groups 2922 settings and push
notification contacts in the Notification Contacts 2853 settings.
Message Define the message of the push notification. The default message is [%
sitename] %device %name %status %down (%message).
HTTP Version Define the HTTP version that PRTG uses to send the push notification:
Send Microsoft Teams Message

Regardless of the Notification Summarization method you use, PRTG always sends notifications of
the type Send Microsoft Teams Message immediately. PRTG never summarizes them.
2841
Send Microsoft Teams Message
Setting Description
Teams Webhook URL Enter the URL of the incoming webhook that you set up in your Microsoft
Teams channel.
For more information, see the Knowledge Base: How do I create a
webhook for the PRTG Notifications to Slack and Microsoft Teams?
Title Enter the title of the Microsoft Teams notification. The default title is Enter
value.
Subtitle Enter the subtitle of the Microsoft Teams notification. The default subtitle
is %message.

Content Define the content of the Microsoft Teams notification:

§ Use default content: Use the default notification message content. This
includes information about the Status, Last Scan, Last Value, Last Up,
Coverage, Downtime, Priority, Probe, and Group.
§ Define custom content: Define custom notification message content.
Choose Custom Content below.
Custom Content This setting is only visible if you select Define custom content above.
Enable the check boxes in front of content that you want PRTG to include
in the Microsoft Teams notifications. Disable the check boxes in front of
the content that you do not want to include.
The following types of monitoring information are available:
§ Name
2842
Setting Description
§ Host
§ Status
§ Last scan
§ Last value
§ Message
§ Last down
§ Last up
§ Coverage
§ Downtime
§ Uptime
§ Priority
§ Probe
§ Group
§ Device
§ Date and time
§ Time zone
§ Comments (probe)
§ Comments (group)
§ Comments (device)
§ Comments (sensor)
§ History
Send Slack Message

Regardless of the Notification Summarization method you use, PRTG always sends notifications of
the type Send Slack Message immediately. PRTG never summarizes them.
2843
Send Slack Message
Setting Description
Slack Webhook URL Enter the URL of the incoming webhook that you set up in your Slack
workspace.
For more information, see the Knowledge Base: How do I create a
webhook for the PRTG Notifications to Slack and Microsoft Teams?
Sender Name Enter a sender name to use as the sender of Slack notifications.
This field overrides the sender that you might have defined in your
Slack workspace.
Title Enter the title of the Slack notifications. The default title is Enter value.

Subtitle Enter the subtitle of the Slack notifications. The default subtitle is %
message.
Content Define the content of the Slack notifications:

§ Use default content: Use the default notification message content. This
includes information about the Status, Last Scan, Last Value, Last Up,
Coverage, Downtime, Priority, Probe, and Group.
§ Define custom content: Define custom notification message content.
Choose Custom Content below.
2844
Setting Description
Custom Content This setting is only visible if you select Define custom content above.
Enable the check boxes in front of the content that you want PRTG to
include in the Slack notifications. Disable the check boxes in front of the
content that you do not want to include.
The following types of monitoring information are available:

§ Name
§ Host
§ Status
§ Last scan
§ Last value
§ Message
§ Last down
§ Last up
§ Coverage
§ Downtime
§ Uptime
§ Priority
§ Probe
§ Group
§ Device
§ Date and time
§ Time zone
§ Comments (probe)
§ Comments (group)
§ Comments (device)
§ Comments (sensor)
§ History
Send MQTT Publish Notification

Regardless of the Notification Summarization method you use, PRTG might not send notifications of
the type Send MQTT Publish Notification immediately.
2845
Send MQTT Publish Notification
Setting Description
MQTT Broker Enter the address for the connection to the MQTT broker (server).
is 1883.
User Authentication Select if you want to connect without credentials or define credentials for
User Name Enter the user name for access to the Message Queue Telemetry
Password Enter the password for access to the MQTT broker.
Server Authentication Select if you want to use a certificate for server authentication:
CA Certificate Paste the certificate authority (CA) certificate for the verification of the
MQTT broker.
2846
Setting Description
Client Authentication Select if you want to use a certificate for client authentication:
Client Certificate Paste the certificate that you created for authenticating the sensor
Client Key Enter the client key for access to the MQTT broker.
Client Key Password Enter the password for the client key certificate.
MQTT Topic Enter the topic for the MQTT publish notifications. The default topic is
PRTG/%sitename/notifications.
MQTT clients that are subscribed to this topic receive the MQTT
publish notifications.
ClientID Enter the ClientID for the connection to the MQTT broker (server). The
default ClientID is PRTG - %sitename.
Message Define the message of the MQTT publish notifications. The default
message is PRTG - [%sitename] %device %name %status %down (%
message).
2847
Send OPC UA Notification
Send OPC UA Notification
Setting Description
OPC UA Server Enter the address for the connection to the OPC Unified Architecture
(OPC UA) server.
Port Enter the port for the connection to the OPC UA server. The default port
for secure connections is 4843. The default port for unsecure connections
is 4840.
NodeID Enter the NodeID for the OPC UA notification. PRTG writes the data that
you define below to the specified NodeID.
Timeout (Sec.) Enter a timeout in seconds for the request.
want to use:
2848
Setting Description
the OPC UA server.


to use.
2849
Setting Description
Data Type Select the type of the data that PRTG sends:
§ Boolean: PRTG sends a Boolean.
§ Int64: PRTG sends a 64-bit integer.
§ Double: PRTG sends a double value.
Boolean This setting is only visible if you select Boolean above.
Select the Boolean value that PRTG sends:

§ True (default)
§ False
If you select Boolean as Data Type, the data type on the OPC UA
server must be Boolean.
Int64 This setting is only visible if you select Int64 above.
Enter the 64-bit integer that PRTG sends.

If you select Int64 as Data Type, the data type on the OPC UA server
must be Int64.
Double This setting is only visible if you select Double above.
Enter the double value that PRTG sends.

If you select Double as Data Type, the data type on the OPC UA
server must be Double.
settings are lost.
PRTG Sensor Hub Notifications

In addition to the standard notifications, you can also create custom notifications. To do so, write a script
or a program and use it with an Execute Program notification or an Execute HTTP Action notification.
There are also many free scripts, plugins, and add-ons for PRTG in the PRTG Sensor Hub.
Others
For information about the Comments and History tabs, see section Object Settings 204 .
More
KNOWLEDGE BASE
2850
PowerShell 32 bit and 64 bit and Execution Policy

Is it possible to send SNMP traps using PRTG?


How do I create a webhook for the PRTG Notifications to Slack and Microsoft Teams?
How do I troubleshoot erratic behavior of push notifications in the PRTG app for desktop or PRTG apps?
PAESSLER WEBSITE
8.12.1.3 Notification Contacts
On the Notification Contacts tab, you can define and change the notification contacts of the user
account.
Notification Contacts Tab
2851
Notification contacts are unique for each user account. This means that every user can individually define
how they want to receive notifications 2745 from PRTG. Recipients of notifications are email addresses,
phone numbers, push devices (with PRTG for Android 2999 or PRTG for iOS 2998 ), and users of certain
instant messaging services.
The notification methods 2825 Send Email, Send SMS/Pager Message, and Send Push Notification let
you define a user who receives notifications for every active notification contact. If you select a user
group, PRTG sends the notifications to all active notification contacts of all users that are in the user
group. To exclude notification contacts from the notification delivery, use the Pause button to deactivate
them.
In this section:
§ Note 2852
§ Notification Contacts Overview 2853
§ Notification Contacts Settings 2853
§ Add Email Contact 2854
§ Add SMS Contact 2855
Note
and their content.
PRTG web interface.
2852
Notification Contacts Overview
Click the Notification Contacts tab to show a list of all notification contacts for the user account. You
have the following options:
Option Description
Pause ( ) Pauses the notification contact. If a notification contact is paused 230 ,

PRTG does not send any messages to the contact when a notification for
this user is triggered.
Resume ( ) Resumes the notification contact. When a notification for this user is
triggered, PRTG sends a message to this user.
Edit ( ) Open the settings of the notification contact 2853 and change its
description and recipient.
This is not possible for predefined notification contacts, for example,
for Primary Email Address. You can change the primary email
address under My Account 2811 .
Delete ( ) Delete the notification contact.

This is not possible for predefined notification contacts, for example,
for Primary Email Address.
Notification Contacts Settings

Hover over and select Add Email Contact or Add SMS Contact from the menu to add a new
notification contact. You can also click the next to a notification contact to edit it.
PRTG automatically adds push contacts for the corresponding user when you install a PRTG app for
iOS or Android on your smartphone or tablet, connect to PRTG, and activate push notifications. You
cannot manually add push contacts. If your mobile device actively rejects push notifications for a push
contact, for example, because you deactivate push on the target device or reset it, PRTG automatically
pauses the push contact. The affected user account receives a ToDo ticket 216 in this case.
2853
Add New Notification Contact
Add Email Contact
Setting Description
Description Enter a description to identify the email contact.

Recipient Enter a valid email address for the email contact.
For the contact type Push, this field shows a unique token that you
cannot change. PRTG uses this token to send push notifications
through the cloud. For more information, see the Knowledge Base: How
can I use push notifications with PRTG?
Type Shows the type of the notification contact.
If you want to use a different contact type, create a new contact with
Add Email Contact or Add SMS Contact, or activate push
notifications in your PRTG for iOS or Android app.
Click OK to save your settings, or click Cancel to close the dialog box without changes to the
notification contact.
2854
Add SMS Contact
Setting Description
Description Enter a description to identify the SMS contact.

Recipient Enter a valid phone number for the SMS contact. The format of the phone
number depends on the SMS provider. You can use a plus sign (+) or 00,
followed by the country code and the number. For example, +1555012345
or 001555012345.
Make sure that the number format meets the requirements of your
SMS provider or the hardware that you use in combination with an
application programming interface (API) call. Sometimes a preceding plus
sign is not required. The wrong format might result in undelivered
messages.
For the contact type Push, this field shows a unique token that you
cannot change. PRTG uses this token to send push notifications
through the cloud. For more information, see the Knowledge Base: How
can I use push notifications with PRTG?
Contact Type Shows the type of the notification contact.
If you want to use a different contact type, create a new contact with
Add Email Contact or Add SMS Contact, or activate push
notifications in your PRTG for iOS or Android app.
Click OK to save your settings, or click Cancel to close the dialog box without changes to the
notification contact.
More
KNOWLEDGE BASE


PAESSLER WEBSITE
2855
8.12.1.4 Schedules
On the Schedules tab, you can define or change schedules for the user account. You can use schedules
to pause 230 monitoring and notifications for certain time periods with the period lists option. Also, you
can activate monitoring and notifications at certain times with the time table option. You can also use
schedules to define the time periods that PRTG covers when you create reports 2764 .
Schedules Settings
In this section:
§ Schedules Settings 2856
§ Basic Settings 2858
§ Schedules and Time Zones 2860
§ Period Definition Syntax 2860
§ Others 2861
Schedules Settings
When a user with administrative rights creates a new object, only other users with administrative
rights can view or edit the new object by default. When a read/write user creates a new object, all
members of the read/write user's primary group can view and edit the new object as well. This behavior
applies to libraries 2748 , maps 2786 , reports 2764 , notification templates 2818 , and schedules 2856 . For more
information, see section Access Rights Management 149 .
2856
Click the Schedules tab to show a list of all schedules. To edit a schedule, enable the check box next to
a schedule and choose from the following options:
Option Description
Used by ( ) Shows a list of objects that use this schedule.
Delete ( ) Deletes the schedule.

This is not possible for predefined schedules.
Settings ( ) Opens the settings of the schedule.
Hover over and select Add Schedule from the menu. You can also click the name of a schedule to
edit it.
2857
Basic Settings
Edit Schedule Time Table
Setting Description
Schedule Name Enter a name to idenitfy the schedule.

For more information, see section Tags 142 .
2858
Setting Description
Selection Method Select the method that you want to use to define a schedule:
§ Use weekday/hour time table: Select specific days of the week or
specific hours in which the schedule is active. This means that
monitoring objects, notifications, and reports are not paused.
§ Use list of period definitions: Enter a list of period definitions in which

the schedule is inactive. This means that monitoring objects,
notifications, and reports are paused.
Time Table (active time This setting is only visible if you select Use weekday/hour time table
slots) above.
Enable or disable check boxes or use buttons to define the schedule:
§ Weekday buttons ( ): Use the weekday buttons Mo, Tu, We,

Th, Fr, Sa, and Su to define the days of the week in which the schedule
is active. For example, click the Mo button to set the schedule to active
for all hours every Monday. This enables all check boxes under the Mo
column.
§ Hour buttons ( ): Use the hour buttons 0:00 - 23:00 to define the
hours of the day in which the schedule is active. For example, if the
0:00 button is blue, click it to set the schedule to active for the hour
0:00 of all days of the week. If the 0:00 button is white, click it to set
the schedule to inactive for the hour 0:00 of all days of the week.
§ All off button ( ): Use the All off button to disable all check
boxes, and to deselect all weekday buttons and hour buttons.
§ All on button ( ): Use the All on button to enable all check

boxes, and to select all weekday buttons and hour buttons.
For more information, see Schedules and Time Zones 2860 below.
Period List (inactive time This setting is only visible if you select Use list of period definitions above.
slots)
Enter the date and time periods in which the schedule is inactive. The
periods must have the following format:
ww:hh:mm-ww:hh:mm
Make sure that you enter each period exactly in this format.
Otherwise you receive an error message. Go back to the schedule
and correct the period in this case. For details and examples, see Period
Definition Syntax 2860 below.
For more information, see Schedules and Time Zones 2860 below.
2859
Access Rights
Setting Description
settings.
settings.
lost.
Schedules and Time Zones

Schedules use the time zone of the PRTG core server system. This might be different from other
time displays in PRTG that are saved in UTC.
§ If you select Use weekday/hour time table, PRTG converts the time in which the schedule is active to
the time zone of the user account 2815 . This means that the schedule applies according to the time that
the user account shows.
§ If you select Use list of period definitions, PRTG does not adjust the time in which the schedule is
inactive to the time zone of the user account. The schedule applies according to the time on the PRTG
core server system in this case. Because of this, you encounter time shifts for schedules if there are
changes to the time zone on the server or because of daylight saving and standard time changes.
Period Definition Syntax

Define one or more periods of time during which the object that uses this schedule is inactive. In each
line, enter one range in the format ww:hh:mm-ww:hh:mm. The following values are possible:
§ ww: mo, tu, we, th, fr, sa, su.
§ hh: Enter the hour in the 24-hour format. For example, a number between 00 and 23.
You must use the 24-hour format. You cannot use A.M./P.M.
§ mm: Enter the minute. For example, a number between 00 and 59.
2860
Example
This example shows 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 that uses this schedule is inactive (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 is active during the other times.
Others
For information about the comments and history tabs, see section Object Settings 204 .
More
KNOWLEDGE BASE

Others
see sections:
8.12.1.5 API Keys
On the API Keys tab, you can add, edit, and delete API keys that are specific to the user account.
API Keys Overview

Click the API Keys tab to show a list of all API keys for the user account. You have the following
options:
2861
Option Description
Edit ( ) Open the settings of the API key 2864 and change its name, description,
and access level.
Delete ( ) Delete the API key.
Add API Key

Hover over and select Add API Key from the menu to add a new API key.
Add new API key
2862
Setting Description
Name Enter a name to identify the API key.

Description Enter a description for the API key.
Access Level Select the access level for the API key:
§ Read access
§ Acknowledge access
§ Write access
§ Full access
For more information about access rights in PRTG, see section

Access Rights Management 149 .
API Key Shows the token.

Copy and store this token. After you click OK, the token will not be
visible again.
This setting is for your information only. You cannot change it. If you
lose it, you should remove the API key and create a new one.
Click OK to save your settings, or click Cancel to close the dialog box without creating an API key.
2863
Edit API Key
Edit API Key
After creation, you can edit the name, the Name, the Description, and the Access Level of your API
keys.
2864
8.12.2 System Administration
To open the system administration, select Setup | System Administration from the main menu bar 265 .
System Administration Bar
In this section:
§ User Interface 2865
§ Monitoring 2879
§ Notification Delivery 2887
§ Core & Probes 2897
§ User Accounts 2911
§ User Groups 2922
§ Administrative Tools 2928
§ Cluster 2933
§ Single Sign-On 2935
§ Maintainer Mode 2941
8.12.2.1 User Interface
On the User Interface tab, you can define global settings regarding the PRTG web interface, PRTG web
server settings and performance, Geo Maps, and graph settings.
In this section:
§ PRTG Web Interface 2866
§ Geo Maps 2869
§ PRTG Web Server 2870
§ Graph Settings 2876
2865
PRTG Web Interface
PRTG Web Interface
Setting Description
Site Name In the PRTG web interface, you can see the site name on the Login 157 screen and in
the title bar of the browser window. PRTG also uses the site name in notification
emails by default. Enter a string.
If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for
security reasons. For more information, see the Knowledge Base: What security
features does PRTG include?
DNS Name Enter a Domain Name System (DNS) name if the PRTG web interface is also
reachable via the DNS name. PRTG also uses the DNS name in notification emails to
generate links by default. Enter a string.
Do not use the special characters " and \ in the DNS name.
In a cluster, only the master node uses the DNS name that you enter. You cannot
enter a DNS name for a failover node.
Language Select the language. The default language is English.

This setting defines the language of the PRTG web interface and the PRTG
Administration Tool 3050 .
List of available languages:
§ Deutsch (German)
§ English
2866
Setting Description
§ Español (Spanish)
§ Français (French)
§ Nederlands (Dutch)
§ Português (Portuguese)
§ (Russian)
§ (Japanese)
§ (Simplified Chinese)
If you change this setting, PRTG needs to restart the PRTG core server to apply
your changes. After you click Save, a dialog box appears that asks you to confirm
the restart. Click OK to trigger the restart. During the restart, all users of the PRTG
web interface, the PRTG app for desktop 2994 , or the PRTG Apps for Mobile Network
Monitoring 2998 are disconnected and reconnected.
Graph Type Select how PRTG displays graphs in the PRTG web interface and in reports 2764 :
§ Display area graphs (recommended): Display series of data points connected by
straight lines. Areas between axis and lines are shaded.
§ Display line graphs: Display series of data points connected by straight lines.
We recommend that you use area charts for better visibility.

PRTG automatically displays graphs that contain data from more than one cluster
node as line graphs.
Automatic Define if PRTG automatically logs inactive users out of the PRTG web interface:
Logout
§ Do not log out users after a period of inactivity: Do not log out users even if they are
inactive for a longer period of time.
§ Log out users after a period of inactivity: Log out users if they are inactive for a
certain period of time for security reasons.
Period of This setting is only visible if you select Log out users after a period of inactivity above.
Inactivity
Specify the period of inactivity in minutes after which PRTG automatically logs out
users. Enter an integer.
PRTG redirects users to the Login 157 screen after this period of inactivity.
If the value you enter is greater than 1 minute, a logout countdown appears 1
minute before PRTG logs out users. If the value is 1 minute, users see the logout
countdown 30 seconds before PRTG logs them out. Click in the browser window to
stop the countdown and to stay logged in to the PRTG web interface.
2867
Setting Description
Logout Countdow n
Google Enter your Google Analytics Tracking ID to track the usage of pages in the PRTG web
Analytics interface with Google Analytics. Enter a string or leave the field empty. The string
Tracking ID looks like this UA-xxxxxx-xx, for example.
You need a Google Analytics account for this feature. Create a tracking ID within
the Google Analytics portal and enter it here. PRTG then dynamically integrates it
into the PRTG web interface.
For more information, see the Knowledge Base: How can I integrate Google
Analytics into PRTG?
2868
Geo Maps
Geo Maps
Setting Description
Service Provider Select if and how you want to enable the Geo Maps feature. If you enable
the feature, PRTG uses the first line of the location setting 438 of an object
to show it on a geographical map. Choose a map provider:
§ Disable Geo Maps integration: Disable the Geo Maps feature and do
not show geographical maps in the PRTG web interface.
§ Default: Use the default option HERE Maps to show geographical
maps.
§ HERE Maps: Use HERE Maps to show geographical maps.
§ Google Maps (API key required): Use Google Maps to show

geographical maps. Sign up for a Google Maps API key to use this
service.
For more information about the different map providers, see the
Knowledge Base: Which provider should I use for the Geo Maps
feature of PRTG?
Map Type The options that are available depend on the map provider that you select
above. Default, HERE Maps, and Google Maps (API key required) all have
the following options:
§ Standard: Show geographical maps in a standard map view.
§ Satellite: Show geographical maps in a satellite view.
In addition to these options, Google Maps (API key required) also has the
following options:
§ Terrain: Show geographical maps in a terrain view.
§ Hybrid (satellite and standard map): Show geographical maps in a

hybrid view.
Google Maps Static API This setting is only visible if you select Google Maps (API key required)
Key above.
2869
Setting Description
Enter your Google Maps Static API key.

For more information on how to get a Google API key, see the
Knowledge Base: How do I get a Google Maps API key for use in
PRTG?
PRTG Web Server
PRTG Web Server
2870
Setting Description
Performance Handling Select if you want to enable performance improvements for the PRTG web
interface:
§ Do not limit features or delay display (recommended): Provide full
functionality and show all menu items and live data.
We recommend that you use this option.
§ Limit features and delay display: Improve the reaction time and speed
of the PRTG web interface by delaying the display of monitoring data
and hiding some features.
For more information on how to speed up the PRTG web interface,
see the Knowledge Base: How can I speed up PRTG—especially for
large installations?
IP Address for PRTG The PRTG web server provides access via the PRTG web interface and
Web Server the PRTG app for desktop 2994 . Once you specify an IP address, you use
it to log in to the PRTG web interface in your browser. Specify on which
IP address the PRTG web server runs:
§ Localhost, 127.0.0.1 (PRTG is not accessible from other
computers):Use 127.0.0.1 only. The PRTG web interface and the PRTG
app for desktop are only accessible from the PRTG core server system.
Either the selected port or at least one port in the range from 8080
to 8089 must be available on 127.0.0.1.
If you run PRTG on localhost, do not use the DNS name

http://localhost to log in to the PRTG web server. This might
considerably slow down the PRTG web interface. Use your local IP
address or http://127.0.0.1 instead.
§ All IP addresses available on the PRTG core server system
(recommended): Use all IP addresses that are available on the PRTG
core server system and enable access to the PRTG web server for all of
these IP addresses.
The selected Transmission Control Protocol (TCP) port for the
PRTG web server must be available on all selected IP addresses.
§ Specify IP addresses: Select specific IP addresses on which the PRTG
web server runs. The list is specific to your setup. Enable check boxes
in front of every IP address that you want the PRTG web server to be
available at. You can also select all IP addresses by clicking the Select
all IP addresses button or deselect all addresses by clicking the
Deselect all IP addresses button.
to 8089 must be available on the specified IP address.
Regardless of the setting that you select, one port in the range from
8080 to 8180 must be available on the specified IP address so that
PRTG can create reports. The report engine tries to connect to the PRTG
core server on one of these ports.
2871
Setting Description
If PRTG does not find a network card on startup, it switches this

setting to Localhost, 127.0.0.1 (PRTG is not accessible from other
computers). This setting remains even if a network card is available later
on. If you disable or remove the network card on the PRTG core server
system, check this setting.
If you change this setting, PRTG needs to restart the PRTG core
server to apply your changes. After you click Save, a dialog box
appears that asks you to confirm the restart. Click OK to trigger the
restart. During the restart, all users of the PRTG web interface, the PRTG
app for desktop 2994 , or the PRTG Apps for Mobile Network Monitoring 2998
are disconnected and reconnected.
TCP Port for PRTG Web Specify how the PRTG web server accepts incoming web page requests:
Server
§ Secure HTTPS server (port 443, recommended, mandatory for internet
access): Use a Secure Sockets Layer (SSL)/Transport Layer Security
(TLS) secured HTTPS connection on port 443.
This setting is required if you want to access the PRTG web
interface via the internet.
Although the connection is secure, you see an SSL certificate

warning in your browser when you log in to the PRTG web interface
because the default certificate is unknown to your browser. For more
information, see the Knowledge Base: Why does my browser show an
SSL certificate warning when I open the PRTG web interface?. You can
install a different SSL certificate for PRTG. For more information, see
the Paessler website: How to use your own SSL certificate with the
PRTG web server.
If port 80 is available, PRTG reserves it as well. If port 80 is not

available, PRTG tries port 8080 as fallback. If this port is also not
available, PRTG searches from port 8081 upwards for a free port. PRTG
sends a ticket 216 that shows you the currently used port number and
switches back to port 80 as soon as it is available again. When users
try to connect on port 80 via HTTP, they are redirected to port 443 via
HTTPS. You can change this behavior via a registry setting. If port 443
is not available, PRTG tries port 8443 as fallback. If this port is also not
sends a ticket that shows you the currently used port number and
switches back to port 443 as soon as it is available again.
2872
Setting Description
§ Unsecure HTTP server (default port 80, not recommended): Use the
PRTG web server without SSL/TLS on port 80.
This setting is not recommended for WAN connections.
If you use the PRTG web server via the internet without connection
security, attackers could potentially spy on credentials that you
enter in PRTG. We strongly recommend that you use this option only
in a LAN.
§ Custom configuration: Specify a custom port for the PRTG web server
and the security of the connection. This option is intended for systems
that already have a web server on the standard port.
If PRTG always uses a fallback port after a server restart, check for
other programs that use the same port as PRTG. For example, the
Microsoft Microsoft Internet Information Services (IIS) web server also
uses port 80 (port 443 for secure connections) by default and blocks it.
We recommend that you disable such programs and services on
startup.
PRTG Web Server Port This setting is only visible if you select Custom configuration above.
Enter the TCP port number (between 1 and 65535) that you want the
PRTG web server to run on. Enter an integer.
If you use a secure connection and port 80 is free, PRTG also
reserves it. When users try to connect on port 80 via HTTP, they are
redirected to the custom port via HTTPS. You can change this behavior
via a registry setting.
If the port that you define for secure connections is not available,
PRTG tries port 8443 as fallback. If this port is also not available,
PRTG searches from port 8444 upwards for a free port. PRTG sends a
ticket 216 that shows you the currently used port and switches back to
the original port as soon as it is available again.
2873
Setting Description
PRTG Web Server This setting is only visible if you select Custom configuration above.
Security
Specify if you want to use connection security:
§ Use HTTPS (secured with SSL/TLS): Use an SSL/TLS secured HTTPS
connection on the port that you define as PRTG Web Server Port.
warning in your browser when you log in to the PRTG web
interface, because the default certificate is unknown to your browser.
You can install a different SSL certificate for PRTG later. For more
information, see the Paessler website: How to use your own SSL
certificate with the PRTG web server.
§ Do not use connection security (not recommended): Use the PRTG
web server without SSL/TLS on the port that you define as PRTG Web
Server Port.
We recommend that you do not use this setting for WAN
connections.
If you use the PRTG web server without connection security on the
internet, attackers could potentially spy on credentials that you
enter in PRTG. We strongly recommend that you use this setting in a
LAN only.
Connection Security Specify the security level to use for connections to and from the PRTG
web server:
§ High security (TLS 1.3, TLS 1.2): Only accept high security
connections from clients like web browsers, apps, the PRTG app for
desktop, or API clients.
These clients must support modern forward secrecy cipher suites.
§ Default security (TLS 1.3, TLS 1.2) (recommended): Only accept high
security connections from clients like web browsers, apps, the PRTG
app for desktop, or API clients.
These clients must support modern forward secrecy cipher suites.
2874
Setting Description
§ Weakened security (TLS 1.3, TLS 1.2, TLS 1.1, TLS 1.0): If you have
clients that do not support High security (TLS 1.3, TLS 1.2) or Default
security (TLS 1.3, TLS 1.2) (recommended), temporarily use this
setting so that they can connect. This setting accepts TLS 1.3, TLS
1.2, TLS 1.1 and TLS 1.0 connections.
This might be necessary, for example, for older browsers, browsers
that run on old network components, or some default browsers on
Android systems.
We strongly recommend that you update your clients and then use
Default security (TLS 1.3, TLS 1.2) (recommended) or High
security (TLS 1.3, TLS 1.2).
If you set a registry key in previous PRTG versions to override the
Secure Sockets Layer (SSL)/Transport Layer Security (TLS) version
and cipher suites of PRTG web server connections or probe connections,
High security (TLS 1.3, TLS 1.2) overrides the registry setting and only
TLS 1.3 and TLS 1.2 are allowed. If you select Default security (TLS 1.3,
TLS 1.2) (recommended), the registry value overrides this setting and the
connection security that you defined in the registry applies.
PRTG displays the SSL/TLS versions and cipher suites that are used
for connections to and from the PRTG web server under Setup |
PRTG Status 2945 .
Active IP Address/Port Shows all active combinations of the IP addresses and ports on which the
Combinations PRTG web server listens for web requests.
PRTG internally uses port 8085 for report generation.
2875
Graph Settings
PRTG shows several graphs on the Overview tabs and x Days tabs of objects in the PRTG web interface.
PRTG keeps these in RAM for fast graph display. The longer the time frames and the shorter the
intervals are, the more memory PRTG uses for this. You can adapt the details for all four graphs. This
setting also changes the caption of the graphs and tabs in the PRTG web interface and thePRTG app for
desktop.
If you change this setting, PRTG needs to restart the PRTG core server to apply your changes. After
you click Save, a dialog box appears that asks you to confirm the restart. Click OK to trigger the
restart. During the restart, all users of the PRTG web interface, the PRTG app for desktop 2994 , or the
PRTG Apps for Mobile Network Monitoring 2998 are disconnected and reconnected.
Graph Settings
Setting Description
Live Graph The live graph is only available for sensors.

The live graph does not have a fixed time span but you can define
how many values to display. The actual time span that the live graph
covers depends on the scanning interval of the sensor that you view.
PRTG automatically calculates the time span. The default is 120 Values.
This results in a graph that covers a time span of two hours if a sensor
has a 1-minute scanning interval. Other scanning intervals result in graphs
that cover different time spans.
Define how many values the graph displays:
§ 60 values: Cover a time span of one hour if a sensor has a scanning
interval of one minute.
This setting uses the least amount of RAM. We recommend this
setting for installations with 10,000 sensors or more.
§ 120 values: Cover a time span of two hours if a sensor has a scanning
2876
Setting Description
§ 240 values: Cover a time span of four hours if a sensor has a scanning
§ 480 values: Cover a time span of eight hours if a sensor has a scanning
§ 960 values: Cover a time span of 16 hours if sensor has a scanning

This setting uses the most amount of RAM.
Graph 1 By default, this is the 2 days graph in the PRTG web interface. You can
change it to have more or less detail. PRTG averages the monitoring
results of the actual scanning intervals of the sensors.
§ 1 day with averages of 1 minute: Cover a time span of one day with
averages of one minute. This results in 1440 values.
§ 1 day with averages of 5 minutes: Cover a time span of one day with
averages of five minutes. This results in 288 values.
§ 1 day with averages of 15 minutes: Cover a time span of one day with
averages of 15 minutes. This results in 96 values.
§ 2 days with averages of 1 minute : Cover a time span of two days with
averages of one minute. This results in 2880 values.
§ 2 days with averages of 5 minutes: Cover a time span of two days with
averages of five minutes. This results in 576 values.
§ 2 days with averages of 15 minutes: Cover a time span of two days with
averages of 15 minutes. This results in 192 values.
§ 4 days with averages of 1 hour: Cover a time span of two days with
averages of one hour. This results in 96 values.
Graph 2 By default, this is the 30 days graph in the PRTG web interface. You can
change it to have more or less detail.
§ 10 days with averages of 1 hour: Cover a time span of 10 days with
2877
Setting Description

§ 30 days with averages of 6 hours: Cover a time span of 30 days with
averages of six hours. This results in 120 values.

§ 40 days with averages of 6 hours: Cover a time span of 40 days with
averages of six hours. This results in 160 values.
§ 60 days with 6 hour averages of 6 hours: Cover a time span of 60 days
with averages of six hours. This results in 240 values.
Graph 3 By default, this is the 365 days graph in the PRTG 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.
§ 100 days with averages of 1 day: Cover a time span of 100 days with
averages of one day. This results in 100 values.
settings are lost.
More
KNOWLEDGE BASE
2878
How can I integrate Google Analytics into PRTG?

Which provider should I use for the Geo Maps feature of PRTG?
How do I get a Google Maps API key for use in PRTG?


Which domains and ports does the Geo Maps feature use?
Which limitations apply when using the Google Maps API in PRTG?
PAESSLER WEBSITE
§ https://www.paessler.com/support/how-to/ssl-certificate
Others
see sections:
8.12.2.2 Monitoring
On the Monitoring tab, you can define global settings for scanning intervals, unusual and similar sensors
detection, auto-discovery, and uptime threshold.
2879
In this section:
§ Scanning Intervals 2880
§ Unusual Detection 2881
§ Similar Sensors Detection 2883
§ Recommended Sensors Detection 2884
§ Auto-Discovery 2885
§ Experimental Features 2886
§ Uptime Threshold 2886
Scanning Intervals
Scanning Intervals
Setting Description
Available Intervals Define the scanning intervals available in the dropdown list of every
object's settings 204 . In the text field, enter one value in each line. Use s,
m, h, and d to define seconds, minutes, hours, and days. By default, the
following scanning intervals are available:
§ 30s: 30 seconds
§ 1m: 60 seconds
§ 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: 24 hours
2880
Setting Description
We recommend that you do not use scanning intervals that are below
10 seconds to prevent system overload. Scanning intervals that are
below 10 seconds are not officially supported. The maximum supported
scanning interval is 10 days.
PRTG might convert values that you enter to a more readable
equivalent of the values. For example, if you enter 24h (24 hours),
PRTG displays this as 1d (one day) in the dropdown list in the object
settings.
Valid values are positive integers followed by s, m, h, and d. You can
also define specific points in time to indicate when PRTG executes
scanning actions. Enter up to 50 concrete Coordinated Universal Time
(UTC) points in time according to the formula @ UTC hh:mm , hh:mm.
You do not need to use a space before and/or after the comma. However,
PRTG always saves the entries with a space both before and after the
comma.
Your local time might be different from the UTC time.
For more information on how to set specific points in time as a
scanning time for sensors, see the Knowledge Base: Can I set a
sensor to run at a specific time?
Unusual Detection
The Unusual Detection feature sets sensors to the Unusual status 184 when there are values that are not
typical for the time span in which they are measured. PRTG compares the current average values to the
historic monitoring results for this purpose. If the current values show a big difference to the values that
are normally retrieved by a sensor, this sensor indicates this with the Unusual status.
You can define the granularity of the unusual detection, that is, how big the difference must be to cause
the Unusual status. If you disable the unusual detection by setting both settings to Never, sensors never
show the Unusual status.
You can enable and disable unusual detection for specific devices, groups, and probes in the
respective object settings 471 .
Unusual detection requires sensor data from at least four weeks (28 to 34 days) to have enough data
available for comparison. If less data is available, PRTG cannot calculate the Unusual status.
Unusual Detection
2881
Setting Description
Show Unusual When Define when a sensor shows the Unusual status by comparing the day of
the week:
§ Never: Disable unusual detection for weekday average.
§ 24h average is <80% or >120% of weekday average: Show the Unusual

status when the average of the values measured on the day before is
either lower than 80% or higher than 120% than usual on the same
weekday.
§ 24h average is <50% or >200% of weekday average: Show the Unusual
status when the average of the values measured on the day before is
either lower than 50% or higher than 200% than usual on the same
weekday.
§ 24h average is <20% or >500% of weekday average (recommended):
Show the Unusual status when the average of the values measured on
the day before is either lower than 20% or higher than 500% than usual
on the same weekday.
§ 24h average is <10% or >1,000% of weekday average: Show the
Unusual status when the average of the values measured on the day
before is either lower than 10% or higher than 1,000% than usual on the
same weekday.
§ 24h average is <1% or >10,000% of weekday average: Show the
Unusual status when the average of the values measured on the day
before is either lower than 1% or higher than 10,000% than usual on the
same weekday.
If you enable this unusual detection, the average of the values that
were measured on the day before is compared to the average of the
same day of the week in previous weeks.
For example, consider a traffic sensor that usually measures 100 MB of

average traffic on a weekday. If you choose the first option, the sensor
shows the Unusual status if the average from the day before is lower than
80 MB or higher than 120 MB.
Show Unusual When Define when a sensor shows the Unusual status by comparing the hour of
the day:
§ Never: Disable unusual detection for hour-of-day average.
§ Hourly average is <80% or >120% of hour-of-day average: Show the

Unusual status when the average of the values measured in the hour
before is either lower than 80% or higher than 120% than usual in this
hour of this weekday.
§ Hourly average is <50% or >200% of hour-of-day average: Show the
before is either lower than 50% or higher than 200% than usual in this
2882
Setting Description
§ Hourly average is <20% or >500% of hour-of-day average

(recommended): Show the Unusual status when the average of the
values measured in the hour before is either lower than 20% or higher
than 500% than usual in this hour of this weekday.
§ Hourly average is <10% or >1,000% of hour-of-day average: Show the
before is either lower than 10% or higher than 1,000% than usual in this
§ Hourly average is <1% or >10,000% of hour-of-day average: Show the
before is either lower than 1% or higher than 10,000% than usual in this
If you enable this unusual detection, the average of the values that
were measured in the hour before is compared to the average of the
same hour on the same day of the week in previous weeks.
Consider a traffic sensor that usually measures 10 MB average traffic
within an hour. If you choose the first option, the sensor would show the
Unusual status if the average from the hour before is below 8 MB or above
12 MB.
Log Unusual Events Define if you also want to record unusual events and display them on the
Log tab of a sensor that shows the Unusual status:
§ Do not log unusual events
§ Log and display unusual events on a sensor's Log tab

The Similar Sensors Detection feature enables PRTG to analyze sensor data for similarities. The
detection runs in the background with low priority. The recommended setting for the analysis depth is to
let PRTG automatically decide how many channels it analyzes. However, you can also override this
setting.
Similar sensors analysis requires sensor data from at least seven days to have enough data for
comparison. If not enough data is available, PRTG does not display data in the Similar Sensors
Overview or in the Similar Sensors section on a sensor's Overview tab. For more information, see section
Similar Sensors 198 .
When similar sensors analysis is turned off or if your PRTG installation exceeds 1,000 sensors and
you select Manage automatically based on sensor count (default), PRTG does not show the Similar
Sensors Overview in the main menu bar 257 .
2883
Setting Description
Analysis Depth Define the number of channels that PRTG analyzes to detect similarities
between sensors, or disable the analysis. The analysis depth depends on
the total number of sensors you have:
§ Manage automatically based on sensor count (default): Analyze all
channels for up to 500 sensors and only the primary channels for up to
1,000 sensors. For more than 1,000 sensors, PRTG disables the
analysis.
This is the default setting in PRTG Network Monitor.
§ Analyze only primary channels: Only analyze the primary channels.

Be aware of potentially high CPU load on the PRTG core server
system if your PRTG installation has more than 1,000 sensors.
§ Analyze all channels (higher CPU load): Analyze all channels.
Be aware of potentially high CPU load on the PRTG core server
system if your PRTG installation has more than 500 sensors.
§ Disable detection of similar sensors: Do not detect similarities. Select
this option if you are not interested in the analysis results or if you want
to keep the CPU load on the PRTG core server system to a minimum.
This is the default setting in PRTG Hosted Monitor.
Recommended Sensors Detection

The Recommended Sensors Detection feature enables PRTG to analyze devices in your network and to
suggest sensors that are missing for a complete monitoring setup. The analysis runs with low priority in
the background when you add a new device, when the last analysis was executed more than 30 days
ago, or when you manually start 201 it.
See section Recommended Sensors 200 for more information, for example, on SNMP settings 201 ,
on the results 201 you get and on how to add the suggested sensors 202 .
Recommended Sensors Detection
2884
Setting Description
Detection Handling Define if you want PRTG to analyze your devices and to recommend
useful sensors:
§ Manage automatically based on sensor count (default): Run the
detection engine for installations with up to 5,000 sensors. If you
exceed this threshold, PRTG disables the detection engine for
performance reasons.
We recommend that you select this option so that you do not miss
any important monitoring data about your network, without risking
running into performance issues.
§ Always show recommended sensors: Always analyze your devices
even if your installation exceeds 5,000 sensors and if you never want to
miss any suggestion to complete your monitoring.
If you select this option, keep it in mind in case you encounter
performance issues.
§ Disable sensor recommendations: Never recommend sensors. Select
this option if you have performance issues with PRTG or if you do not
want to see this information on devices' Overview tabs. Moreover, you
do not see the option Recommend Now in device context menus 240 or
on Overview tabs anymore.
Auto-Discovery
Auto-Discovery
Setting Description
Run Auto-Discovery At Define the time when PRTG automatically runs an auto-discovery 270 in
your network if you configured a daily or weekly schedule in the auto-
discovery group settings 283 . Select a full hour.
§ 00:00 - 23:00
We recommend that you choose a time when there is little user

activity in your network because auto-discoveries can produce a
certain amount of load.
2885
Experimental Features
Experimental Features
The operating methods of the experimental features might change at any time. Do not expect that all
functions work properly, or that the experimental features work as expected at all. Be aware that
Paessler might remove these features at any time.
Setting Description
Beta Sensors Select if you want to enable or disable sensors in beta status:
§ Disable (default): Disable sensors in beta status.
§ Enable: Enable sensors in beta status.

Beta sensors then become available in the Add Sensor 430 dialog.
If you disable beta sensors, existing beta sensors change to
the Unknown status.
PowerShell Security Select if you want to improve PowerShell security by hiding command-line
Enhancement parameters in the process explorer and the event log:
§ Enable (default): Enable PowerShell security enhancement.
If you enable PowerShell Security Enhancement, PowerShell
scripts that use the write-host cmdlet to provide their output to
PRTG do not work anymore. Custom scripts only work if you use the
write-output cmdlet.
Enabling this feature can also improve the performance of
PowerShell sensors.
§ Disable: Disable PowerShell security enhancement.
Uptime Threshold
Uptime Threshold
2886
Setting Description
Minimum Uptime Define which uptime in percent PRTG regards as 100 percent. This
setting affects the colors that you see next to sensor icons in reports.
§ 90 % - 99.999 %
settings are lost.
More
KNOWLEDGE BASE

Can I set a sensor to run at a specific time?

Others
see sections:
8.12.2.3 Notification Delivery
On the Notification Delivery tab, you can define and test global settings for notification delivery. If you do
not want to use a specific notification method, leave the respective fields empty.
In this section:
§ Note 2888
§ SMTP Delivery 2888
§ SMS Delivery 2893
2887
Note
and their content.
PRTG web interface.
SMTP Delivery
SMTP Delivery
Setting Description
Delivery Mechanism Define how PRTG sends emails via the Simple Mail Transfer Protocol
(SMTP):
2888
Setting Description
§ Use direct delivery with the built-in email server (default): Use the built-
in SMTP relay server. This server manages its own email queue. For
each email, it looks up the target SMTP server via the MX record of the
target domain, and sends the email.
§ Use one SMTP relay server (recommended in LANs/NATs): Set up your
own SMTP relay server to send emails. Enter data below.
§ Use two SMTP relay servers (primary and fallback server): Set up two
SMTP relay servers with one as the primary relay server and one as the
fallback relay server. Enter data below.
If you monitor the IT infrastructure in your network address translation
(NAT) or LAN, use your own LAN-based relay server to ensure faster
delivery of notification emails.
This option is not available in PRTG Hosted Monitor. PRTG Hosted

Monitor uses sendgrid for email notifications. For more information,
see the Paessler website: FAQ – PRTG Hosted Monitor.
Sender Email Address Enter an email address to use as the sender of all email notifications.
This setting is global and applies to all email notifications by default.
You can override the sender email in the settings of individual
notification templates 2825 .
Sender Name Enter a name to use as the sender of all email notifications. This setting
is global and applies to all email notifications by default.
You can override the sender name in the settings of individual
notification templates.
SMTP RFC 2821.
The HELO identifier must be a unique name.
We recommend that you use the Domain Name System (DNS) name
of the PRTG core server system.
2889
Setting Description
SMTP Relay Server This setting is only visible if you select Use one SMTP relay server
(recommended in LANs/NATs) or Use two SMTP relay servers (primary
and fallback server) above.
Enter the IP address or DNS name of the SMTP relay server.
SMTP Relay Port This setting is only visible if you select Use one SMTP relay server
Enter the port for the connection to the SMTP server. The default port is
25.
SMTP Relay This setting is only visible if you select Use one SMTP relay server
Authentication (recommended in LANs/NATs) or Use two SMTP relay servers (primary
Select the kind of authentication that the SMTP server requires:

§ Use no authentication: Use SMTP without authentication.
§ Use standard SMTP authentication: Use standard authentication.
§ Use SASL authentication: Use secure authentication via Simple

Authentication and Security Layer (SASL).
SMTP Relay User Name This setting is only visible if you select Use standard SMTP
authentication or Use SASL authentication above.
Enter a valid user name.
SMTP Relay Password This setting is only visible if you select Use standard SMTP
authentication or Use SASL authentication above.
Enter a valid password.
2890
Setting Description
Connection Security This setting is only visible if you select Use one SMTP relay server
Define the connection security for SMTP connections:
§ Use SSL/TLS if the server supports it: Use a Secure Sockets Layer
(SSL)/Transport Layer Security (TLS) secured connection.
§ Do not use connection security: Use an unsecure connection with plain
text transfer.
SSL/TLS Method This setting is only visible if you select Use one SMTP relay server
(recommended in LANs/NATs) and Use SSL/TLS if the server supports it
above.
Select the SSL or TLS version that the SMTP server supports:
§ Auto-Negotiate (TLS 1.0 or higher) (default)
§ SSLv3
§ TLS 1.0
§ TLS 1.1
§ TLS 1.2
§ TLS 1.3
If you select Auto-Negotiate (TLS 1.0 or higher) (default), PRTG uses

the highest available TLS level supported by the SMTP endpoint.
This is only relevant for secure connections. If you do not get a
connection, try a different setting.
SMTP Relay Server

(Fallback) This setting is only visible if you select Use two SMTP relay servers
(primary and fallback server) above.
Enter the IP address or DNS name of the fallback SMTP relay server.
SMTP Relay Port

2891
Setting Description
Enter the port for the connection to the fallback SMTP server. The default
port is 25.
SMTP Relay
Authentication (Fallback) This setting is only visible if you select Use two SMTP relay servers
Select the kind of authentication that the fallback SMTP server requires:
§ Use no authentication: Use SMTP without authentication.
§ Use standard SMTP authentication: Use standard authentication.
§ Use SASL authentication: Use secure authentication via Simple

Authentication and Security Layer (SASL).
SMTP Relay User Name

(primary and fallback server) and Use standard SMTP authentication or
Use SASL authentication above.
Enter a valid user name.
SMTP Relay Password

(primary and fallback server) and Use standard SMTP authentication or
Use SASL authentication above.
Enter a valid password.
Connection Security
Define the connection security for SMTP connections:

§ Use SSL/TLS if the server supports it: Use a Secure Sockets Layer
(SSL)/Transport Layer Security (TLS) secured connection.
§ Do not use connection security: Use an unsecure connection with plain
text transfer.
2892
Setting Description
SSL/TLS Method
(primary and fallback server) and Use SSL/TLS if the server supports it
above.
Select the SSL or TLS version that the SMTP server supports:
§ Auto-Negotiate (TLS 1.0 or higher) (default)
§ SSLv3
§ TLS 1.0
§ TLS 1.1
§ TLS 1.2
§ TLS 1.3
If you select Auto-Negotiate (TLS 1.0 or higher) (default), PRTG uses

the highest available TLS level supported by the SMTP endpoint.
This is only relevant for secure connections. If you do not get a
connection, try a different setting.
Test SMTP Settings Click Test SMTP Settings to test your SMTP notification delivery
configuration.
§ Email Address: Enter an email address to send the test email

notification to.
§ Subject: Enter a subject for the test email notification.
SMS Delivery
Your PRTG Network Monitor license or PRTG Hosted Monitor subscription does not include the cost
for SMS delivery. Refer to the pricing information of the service provider that you plan to use to find
out more about their pricing.
Although PRTG has built-in support for the application programming interface (API) of some SMS
providers, we cannot officially provide support for them. If you have technical questions about SMS
delivery beyond PRTG, contact your SMS provider directly.
Instead of using a preconfigured provider, you can use a custom URL that enables you to use
extended parameters. This is also an alternative to using providers for which we offer preconfigured
options.
2893
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, see the
Knowledge Base: How can I send SMS text message notifications via a modem or a mobile phone
with PRTG?
SMS Delivery
Setting Description
Configuration Mode Define a mode for the SMS delivery configuration:

§ Disable SMS delivery: Do not use SMS delivery.
§ Select an SMS provider from a list of providers: Select a provider from a

list below.
§ Enter a custom URL for a provider not listed: Use a different provider
and manually enter the custom URL below.
Service Provider This setting is only visible if you select Select an SMS provider from a list
of providers above.
Select a service provider from the list:

§ BulkSMS All regions (except South Africa): Enter a User Name and
Password below.
ú URL:
https://www.bulksms.co.uk:443/eapi/submission/send_sms/2/2.0
ú Port: 443
§ BulkSMS South Africa: Enter a User Name and Password below.
ú URL:
https://bulksms.2way.co.za:443/eapi/submission/send_sms/2/2.0
ú Port: 443
§ Agile Telecom: Enter a User Name and Password below.
ú URL: http://agiletelecom.com/smshurricane3.0.asp
ú Port: 80
§ Esendex: Enter a User Name, Password, and Account below.
ú URL:
https://www.esendex.com/secure/messenger/formpost/SendSMS.as
px
2894
Setting Description
ú Port: 443
Some providers might require a port configuration in your firewall. Use

the respective port from the list above.
User Name This setting is only visible if you select Select an SMS provider from a list
of providers above.
Enter a user name for the service provider account.
Password This setting is only visible if you select Select an SMS provider from a list
of providers above.
Enter a password for the service provider account.
Account This setting is only visible if you select Select an SMS provider from a list
of providers and Esendex above.
Enter the account number or the API ID to connect your account if your
provider asks you to register, for example EX0000000. Enter a string or
Custom URL This setting is only visible if you select Enter a custom URL for a provider
not listed above.
From the documentation of your SMS provider, enter the service URL that
it uses to send SMS messages.
Use the following placeholders for the recipient phone number and the
text message:
§ %SMSNUMBER
§ %SMSTEXT
Use the GET method to request the custom URL. POST requests
are not supported.
HTTP Authentication This setting is only visible if you select Enter a custom URL for a provider
not listed above.
Select if PRTG uses HTTP basic authentication when it calls the custom
URL of the SMS provider:
§ Do not use HTTP basic authentication (default)
§ Use HTTP basic authentication
HTTP basic authentication is necessary if the custom URL looks like

this https://[username]:[password]@my.custom.sms.provider/.
2895
Setting Description
Custom SNI This setting is only visible if you select Enter a custom URL for a provider
not listed above.
Define if PRTG sends the Server Name Indication (SNI) extension to the
Transport Layer Security (TLS) protocol along with the HTTP request:
§ Do not send SNI (default): PRTG does not send the SNI when it
executes the HTTP action.
§ Send SNI: PRTG sends the SNI when it calls the target URL. Specify
the SNI below.
Encoding for SMS This setting is only visible if you select Enter a custom URL for a provider
not listed above.
Define the encoding of the URL string that PRTG sends to the SMS
provider:
§ ANSI local system code page (default)
§ UTF-8
§ UTF-16
Virtual Host (SNI) Enter the SNI name that the endpoint configuration requires. Usually, this
is the fully qualified domain name (FQDN) of the virtual host.
Maximum Length of Text Some SMS providers do not allow SMS messages that exceed a certain
amount of characters. PRTG restricts the number of characters according
to the length specified in this field. A value of 0 means that PRTG sends
the entire SMS.
The use of some special characters, especially ones that are not in
the GSM-7 alphabet, might cause the message to be cut off after 70
characters and the special characters might not display properly. The
exact results depend on which SMS provider you use.
Test SMS Settings Click Test SMS Settings to test your SMS notification delivery
configuration.
§ Number: Enter a phone number to send the test SMS notification to.
§ Message: Enter a message for the test SMS notification.
The notification methods Send SMS/Pager Message and Execute HTTP Action use the central
proxy settings of the PRTG core server. For more information, see section Core & Probes 2898
(section Proxy Configuration).
settings are lost.
2896
More
KNOWLEDGE BASE

How can I send SMS text message notifications via a modem or a mobile phone with PRTG?
Which URLs does PRTG use for its preconfigured SMS providers?
Why do I get a connection timeout message when sending SMS via bulksms?
Can Gmail / Google Apps / G-Suite be used for SMTP relay?

How can I enable notification delivery logging?

Can I use Microsoft Office 365 as SMTP relay server for PRTG email delivery?
PAESSLER WEBSITE
FAQ – PRTG Hosted Monitor

§ https://www.paessler.com/prtg/prtg-hosted-monitor/faq
8.12.2.4 Core & Probes
On the Core & Probes tab, you can define settings for the PRTG core server as well as for probe
connections if you use remote probes or mini probes.
If you cannot save changes to Core & Probes settings because you get an Error (Bad Request) with
the message Active Directory Domain not accessible, make sure that you provide the correct
access type for your domain in section Active Directory Integration 2907 . For example, change Use the
PRTG core server service account (usually Local System) to Use explicit credentials and provide correct
credentials for the domain. PRTG automatically sets the access type to Use the PRTG core server
service account (usually Local System) by default, so you might need to change this.
2897
In this section:
§ Proxy Configuration 2898
§ Probe Connection Settings 2900
§ Multi-Platform Probe Connection Settings 2905
§ Active Directory Integration 2907
§ Historic Data Purging 2909
Proxy Configuration
Proxy Configuration
Setting Description
Proxy Server Handling Define if you want to use PRTG with a direct internet connection or if a
proxy is necessary:
§ Do not use a proxy server (default): Do not use a proxy. Use this
setting if a direct internet connection to the PRTG core server system
is available.
§ Use a proxy server: Define proxy settings below. Use this setting if a
proxy is mandatory in your network.
We recommend that you use PRTG with a direct internet connection.
The proxy settings are valid for auto-update 2979 , activating the
product 107 , obtaining Geo Maps 2741 tiles, and for sending HTTP,
push, and SMS text message notifications 2825 .
Server This setting is only visible if you select Use a proxy server above
Enter the address of the proxy server that you use for outbound
connections. Enter a valid address.
Port This setting is only visible if you select Use a proxy server above
Enter the port number of the proxy server that you use for outbound
connections. Enter an integer.
2898
Setting Description
Proxy Authentication This setting is only visible if you select Use a proxy server above
Determine whether the proxy server needs credentials or not:

§ Do not use authentication: Do not use credentials for proxy
connections.
§ User name and password: Define credentials (user name and

password) below. Use this setting if the proxy server requires
credentials.
Enter a user name for proxy authentication. Enter a string.
Enter a password for proxy authentication. Enter a string.
2899
Probe Connection Settings
Probe Connection Settings
Setting Description
Probe Connection IP Define how the PRTG core server handles incoming connections from
Addresses probes:
§ Local probe only, 127.0.0.1 (PRTG is not accessible for remote
probes): Only accept local probe connections. The PRTG core server
does not allow the use of remote probes 3201 .
This is the default setting in PRTG Network Monitor.
2900
Setting Description
§ All IP addresses available on this computer: Accept incoming

connections from remote probes, no matter on which IP address of the
PRTG core server they come in.
§ Specify IP addresses: Accept incoming connections from
remote probes only on the selected IP address(es) of the PRTG core
server. In the list, select the IP addresses by enabling a check box in
front of the desired IP addresses.
You can also change this setting in the PRTG Administration Tool on
PRTG Core Server Systems 3056 .
Access Keys Enter a list of access keys for remote probe connections. Enter one
access key per line.
Every remote probe and multi-platform probe that wants to connect to
this PRTG installation has to use one of these keys.
For more information on how to set an access key for a remote
probe, see section PRTG Administration Tool 3077 .
Allow IP Addresses Enter a list of remote probe IP addresses or Domain Name System (DNS)
names that you want to allow to connect to the PRTG core server. Enter
one IP address or DNS name per line. The following options are also
possible:
§ [Empty]: An empty field does not allow any remote probes (only the
local probe). Enter IP addresses or DNS names to allow remote probe
connections.
We recommend that you use IP addresses instead of DNS names
because DNS name resolution might be cached.
§ any: Enter the word any to automatically allow all remote probe
connections.
We recommend that you only use this option in intranets in
PRTG Network Monitor, not in PRTG Hosted Monitor.
PRTG always automatically allows the local probe (127.0.0.1). PRTG
checks the list of allowed IP addresses before it checks the list of
denied IP addresses.
2901
Setting Description
If the IP address of a remote probe regularly changes (for example,

because of an internet provider that dynamically assigns IP
addresses), enter the potential IP address range for the remote probe or
use any.
You can use the PRTG syntax for IP address ranges. For more
information, see section Define IP Address Ranges 3185 .
Deny IP Addresses Enter a list of remote probe IP addresses or DNS names that you do not
want to allow to connect to the PRTG core server. Enter one IP address
or DNS name per line.
You can use Deny IP Addresses to explicitly deny connections from
remote probes that you do not want to include in your setup either at
all or for a certain time. You can also use it to allow access to an IP
address range under Allow IP Addresses, but to deny access to a single
IP address from the IP address range.
You can use the PRTG syntax for IP address ranges. For more
information, see section Define IP Address Ranges 3185 .
If you deny the IP address or DNS name of a remote probe, you must
restart the PRTG core server to apply your changes.
We recommend that you use IP addresses rather than DNS names
because DNS name resolution might be cached.
Deny GIDs Enter a list of global IDs (GID) Enter one GID per line. PRTG denies
access to matching GIDs.
If you remove a remote probe from the device tree or if you deny a
remote probe after installation, PRTG automatically adds its GID to
this list. The remote probe is no longer able to connect. Denying GIDs is
more precise than denying IP addresses, where other remote probes at
the same location could also be excluded.
A GID is the ID that PRTG attributes to every probe that you include
in your monitoring.
Connection Security Specify the security level that the PRTG web server accepts for
connections to and from the PRTG core server:
§ High security (TLS 1.3, TLS 1.2): Only accept high security
connections from probes.
§ Default security (TLS 1.3, TLS 1.2) (recommended): Only accept high
security connections from probes.
2902
Setting Description
§ Weakened security (TLS 1.3, TLS 1.2, TLS 1.1, TLS 1.0): Additionally
accept TLS 1.1-secured and TLS 1.0-secured connections from probes.
If you have probes that do not support TLS 1.3-secured or TLS 1.2-
secured connections because you updated from an older PRTG
version, you can use this setting to connect to and to update 2979 older
probes. After the update, we recommend that you change this setting
to High security (TLS 1.3, TLS 1.2) or Default security (TLS 1.3, TLS
1.2) (recommended).
If you set a registry key in previous PRTG versions to override the
Secure Sockets Layer (SSL)/Transport Layer Security (TLS) version
and cipher suites of PRTG web server connections or probe connections,
High security (TLS 1.3, TLS 1.2) overrides the registry setting and only
TLS 1.3 and TLS 1.2 are allowed. If you select Default security (TLS 1.3,
TLS 1.2) (recommended), the registry value overrides this setting and the
connection security that you defined in the registry applies.
Mini Probes Define if you want to allow mini probe connections to the PRTG core
server:
§ Do not allow mini probes: Mini probes cannot connect to the PRTG web
server. You are not able to monitor with mini probes if you choose this
option.
§ Allow mini probes to connect to the PRTG web server: Mini probes can
connect to the PRTG web server and use the defined TCP port for the
web server 2870 for this purpose. The default port for secure connections
is 443.
§ Allow mini probes to connect to an extra port: Mini probes can connect
to the PRTG web server via a specific port. Use this if you do not want
the whole PRTG web server to be reachable from other networks all the
time only because of mini probes.
SSL/TLS must be enabled on the mini probe port.
If you want to use mini probes, you need to configure the PRTG web
server to accept connections from mini probes and select Secure
HTTPS server (port 443, recommended, mandatory for internet access) in
the PRTG web server settings 2870 .
For more information, see section Mini Probe API 3158 . See also the
Knowledge Base: Where can I find PRTG mini probes which are
ready to use?
2903
Setting Description
Mini Probe Port This setting is only visible if you select Allow mini probes to connect to an
extra port above.
Enter the number of the port for mini probe connections. Make sure that
SSL is available on this port.
PRTG MultiBoard File Select if you want to allow PRTG MultiBoard to access the PRTG data
Transfer directories and PRTG program directories of the PRTG core servers
connected to PRTG MultiBoard:
§ Disable (default): Do not allow PRTG MultiBoard to access, configure,

and transfer PRTG files. You will not be able to use the Probe Transfer,
Configuration Viewer, and Template Transfer features.
§ Enable: Allow PRTG MultiBoard to access, configure, and transfer
PRTG files.
PRTG MultiBoard requires access to the PRTG Configuration.dat file
for the Probe Transfer and Configuration Viewer features.
2904
Multi-Platform Probe Connection Settings
Multi-Platform Probe Connection Settings
Setting Description
Multi-Platform Probe Define if you want to allow multi-platform probe connections to the PRTG
Connections core server:
§ Do not allow multi-platform probe connections (default): Multi-platform
probes cannot connect to the PRTG core server. You are not able to
monitor with multi-platform probes if you select this option.
§ Allow multi-platform probe connections: Allow multi-platform probes to

connect to the PRTG core server. PRTG automatically creates a Multi-
Platform Probe Connection Health (Autonomous) sensor on your PRTG
core server.
Multi-platform probes connect to the PRTG core server via a NATS
server.
For more information, see the Multi-Platform Probe for PRTG manual.
NATS Connection This setting is only visible if you select Allow multi-platform probe
Security connections above.
2905
Setting Description
Define the connection security level between the PRTG core server and
the NATS server.
§ TLS (default): Select Transport Layer Security (TLS) for an encrypted
communication channel to the NATS server. This configures the NATS
connection to use the tls:// schema.
§ Unsecure (not recommended): All data sent between the PRTG core
server and the NATS server, including passwords and other sensitive
information, will be transmitted in plain text. The NATS connection will
use the unencrypted nats:// schema.
NATS Server Host This setting is only visible if you select Allow multi-platform probe
connections above.
Enter the host name and the port of the NATS server. An encrypted NATS
server connection follows the format host name:port. The default host is
localhost:23561.
Enter the host name as a fully qualified domain address name
(FQDN) of the system that runs the NATS server.
The default port for this connection is 23561. The NATS server
supports port numbers 1 - 65535.
NATS User Name This setting is only visible if you select Allow multi-platform probe
connections above.
Enter the user name for authentication against the NATS server. Enter a
string.
NATS Password This setting is only visible if you select Allow multi-platform probe
connections above.
Enter the password for authentication against the NATS server. Enter a
string.
NATS Server Certificate This setting is only visible if you select TLS (default) above.
Authority Handling
Define the CA certificate the NATS server uses:
§ Use system certificate store (default): Use the CA certificate from your
system's certificate store.
§ Specify a certificate authority certificate file: Define a CA certificate file
below. Use this setting if you created your own TLS certificate.
For more information, see the Knowledge Base: How can I create a
TLS certificate?
2906
Setting Description
Certificate File Name This setting is only visible if you select Specify a certificate authority
certificate file above.
Select the CA certificate to use for TLS validation. This file must match
the CA certificate used to install the NATS server.
Connection Log Level Define the log severity level of the multi-platform probe connection that will
appear in the log file:
§ Error: Log critical events.
§ Warning: Log unexpected events that might result in future errors.
§ Info (default): Log events that are significant to the normal operation of
the the probe adapter.
§ Debug: Log detailed events that occur during the operation of the probe
adapter. Useful for identifying issues.
§ Trace: Log all events of the probe adapter.
The log level decreases in severity, with Error being the highest
severity and Trace being the lowest. The log file will record all logs
pertaining to the selected log severity level and all higher severity levels.
For example, if you select Info (default), the log file will contain logs
identified as Info, Warning, and Error. If you select Debug, the log file will
contain logs identified as Error, Warning, Info, and Debug.
You can find the log files in the PRTG data directory 3219 : C:
\ProgramData\Paessler\PRTG Network Monitor\Logs\probeadapter.
We recommend that you only set your level to Debug or Trace when
you are troubleshooting your setup due to the large amount of logs
the probe adapter generates. Treat log files created at these log levels as
confidential as some logs may contain sensitive information.
Active Directory Integration

Active Directory Integration
2907
Setting Description
Domain Name To use the Microsoft Entra ID integration, enter the name of your local
domain. Enter a string or leave the field empty.
PRTG does not support trusted domains or AD subdomains. For
more important notes about AD integration, see section Active
Directory Integration 3092 , section Notes and Restrictions.
Domain Access Define how PRTG performs Active Directory (AD) queries:
§ Use domain name: Use the entry in the Domain Name field above.
§ Specify domain controllers: Use specific domain controllers. Specify

the domain controllers below.
Primary Domain This setting is only visible if you select Specify domain controllers above.
Controller
Enter the DNS name of the primary domain controller.
Backup Domain This setting is only visible if you select Specify domain controllers above.
Controller (optional)
Optionally enter the DNS name of the backup domain controller or leave
the field empty.
LDAP Connection Define if you want to use a Secure Sockets Layer (SSL)/Transport Layer
Security Security (TLS) secured connection to the LDAP server:
§ Use LDAP without connection security: Do not use an SSL/TLS-
secured connection.
§ Use LDAP over SSL: Use an SSL/TLS-secured connection.
Access Type Define which user account PRTG uses to configure AD access:
§ Use the PRTG core server service account (usually Local System): Use
the same Windows user account configured for the PRTG core server
service. In a default installation, this is the "local system" Windows
user account. If this account does not have the right to query all groups
of your Active Directory, do not use this option.
§ Use explicit credentials: Define a user account that PRTG uses to
authenticate against the Active Directory. This should be a user
account with full access to all of your AD groups.
PRTG uses this account to query the AD for available groups.
Enter the Windows user account name that PRTG uses to authenticate
for AD configuration.
2908
Setting Description
Enter the password for the Windows user account that PRTG uses to
authenticate for AD configuration.
Historic Data Purging

Data purging enables you to automatically delete unnecessary data to free up disk space and to improve
system performance. You can define different time spans for several kinds of data.
For more information on storage locations, see section Data Storage 3218 .
PRTG Hosted Monitor purges historic data using the default purging limits of PRTG Network Monitor
except the configuration backups that are purged after 30 days. You cannot modify historic data
purging limits in PRTG Hosted Monitor.
Historic Data Purging
2909
Setting Description
Log File Records Define how long PRTG keeps records in the system log file Log
Database.db. Enter a value in days. PRTG automatically deletes all
entries that are older than this value. This also affects the content of the
Logs 213 tab of monitoring objects like sensors.
Keep this value as low as possible to enhance system performance.
The default value is 30 days.
PRTG Web Server Log PRTG creates one PRTG web server log file every day. Define how many
Records PRTG web server log files to keep. Enter a value in days. PRTG
automatically deletes all PRTG web server log files that older than this
value.
Historic Sensor Data Define for how long PRTG keeps historic sensor data for all sensors.
Enter a value in days.
Historic sensor data is the basis for reports on monitoring data. If you
decrease this value, less historic monitoring data is available.
Depending on the scanning intervals and the number of sensors in
your setup, the file that contains this data can become large. For
smaller installations up to 500 sensors, 365 is usually appropriate.
The maximum value is 9999 days.
Toplist Records Define for how long PRTG keeps toplist records for Flow (NetFlow, jFlow,
sFlow, IPFIX) 3021 and Packet Sniffer 3019 sensors. Enter a value in days.
We recommend that you use 30 days here.
Old toplist data is deleted automatically as soon as a limit of 2 GB is
reached. The oldest data is deleted from the database first.
Closed Tickets Define for how long PRTG keeps tickets that are in the Closed status.
Enter a value in days.
Reports Define the maximum age for PDF reports. Enter a value in days. PRTG
automatically deletes all reports that are older than this value.
2910
Setting Description
Configuration Auto- Define the maximum age for daily configuration backups. Enter a value in
Backups days. PRTG automatically deletes all configuration backup files that are
older than this value.
PRTG Hosted Monitor purges the configuration backups after 30

days.
Screenshots of HTTP Define for how long PRTG keeps the screenshots of the HTTP Full Web
Full Web Page Sensor Page sensor (PhantomJS browser engine). Enter a value in days. PRTG
automatically deletes screenshots that are older than this value with every
sensor scan.
settings are lost.
More
KNOWLEDGE BASE
Where can I find PRTG mini probes which are ready to use?

How can I create a TLS certificate?

Others
see sections:
8.12.2.5 User Accounts
On the User Accounts tab, administrators can add new user accounts, edit user accounts, and define
which user groups that users are members of.
2911
In this section:
§ User Accounts Overview 2912
§ Add User Accounts 2913
§ User Account Settings Tabs 2913
§ Settings Tab 2914
ú User Account Settings 2914
ú API Access 2915
ú Account Settings 2916
ú Group Membership 2918
ú PRTG Web Interface 2918
ú Ticket System 2920
§ Notification Contacts Tab 2921
§ Comments Tab 2921
§ History Tab 2921
§ API Keys Tab 2922
User Accounts Overview

The User Accounts tab shows a list of all user accounts in this PRTG installation and various types of
information about each user.
Object Shows the name of the user account. Click the user account to open its
settings 2914 .
Type Shows the user type, for example, read-only user.
Email Shows the primary email address of the user account.
Primary Group Shows the primary group of the user account. Click the user group name
to open its settings 2924 .
2912
Group Memberships Shows all user groups that the user account belongs to.
Active/Paused Shows the status of the user account. This can be active or paused.
Add User Accounts

You have several options to add user accounts:
§ To add a new user to PRTG Network Monitor, hover over and select Add User from the menu.
The options are almost the same as for editing users.
§ To add a new user to PRTG Hosted Monitor, click Invite User. The options are almost the same
as for editing users but PRTG Hosted Monitor automatically generates the initial account password.
The new user can change it later. Click Send Invite to save your settings and to send the invitation per
email to the defined primary email address.
§ To batch-add several users at once, hover over and select Add Multiple Users from the menu. In
the dialog box that appears, select a user group 2922 from the dropdown list and enter or paste a list of
email addresses. Separate them by a space, comma, semicolon, or a new line. Click OK to confirm.
For each email address, PRTG creates a new, local user account in the user group, using the email
address as the value for Login Name, Display Name, and Primary Email Address. PRTG automatically
generates a new password and sends it to the email address.
Access rights to device tree objects, libraries, maps, reports, or the ticket system are defined in
user groups. Make sure that the user is a member of the correct user group with the required group
access rights.
You cannot delete predefined objects such as the PRTG System Administrator user account, the
PRTG Users Group, or the PRTG Administrators group.
User Account Settings Tabs

Click on a user account and select the various tabs to change the different settings.
2913
Settings Tab
Setting Description
Login Name Enter a login name for the user account.

The login name must not contain the following invalid characters: " / \
[]:;|=,+*?<>
Display Name Enter a display name that the user recognizes. PRTG uses it for display
purposes only, for example on the Welcome page.
Primary Email Address Enter the primary email address. This is the email address that PRTG
uses by default for the ticket system, including important system
messages, and password recovery.
Make sure that your email client can show HTML emails, otherwise
you cannot read emails from PRTG.
Login Type Only available for PRTG Hosted Monitor instances if a Microsoft
Entra ID connection (formerly Azure Active Directory) has been
successfully configured.
§ Auth0 (default): Send the user a random password to log in to the
PRTG Hosted Monitor instance.
§ Federated Directory: Add a user from your Microsoft Entra tenant.
Use this option when you have configured a Microsoft Entra ID
connection for your PRTG Hosted Monitor instance and want to
add a user from your Microsoft Entra tenant.
2914
Setting Description
For more information, see the Knowledge Base: How to integrate

Microsoft Entra ID into PRTG Hosted Monitor?.
Password Define whether to change the password for the user account:
§ Do not change the password
§ Specify a new password
For security reasons, PRTG does not display the password.

If you specify a new password, enter the old password, then enter the
new password twice.
The new password must be at least 8 characters long. It must
contain a number and a capital letter.
Do not use leading or trailing whitespaces in the new password.
Passhash Click Show passhash to display the passhash for the user account. This
is necessary for authentication for the PRTG API 3094 .
API Access
These settings are only available in PRTG Hosted Monitor.
API Access
Setting Description
API User Name Shows the API user name of the user account. This is necessary for
authentication for the PRTG API.
2915
Setting Description
API Passhash Click Show passhash to display the API passhash of the user account.
This is recommended for authentication for the PRTG API.
Generate API Passhash Click Generate new passhash to reset the passhash of the user.
Account Settings
Account Settings
Setting Description
User Type Define the user type:

§ Read/write user: Can only view monitoring results, libraries, maps,
reports, and also edit the according settings. In addition, they can add
and delete objects, libraries, maps, and reports. The user can
acknowledge alarms, edit notification templates, notification contacts,
and schedules.
§ Read-only user: Can only view monitoring results, libraries, maps,
reports, and the according settings. The user can acknowledge alarms
and change their own password if allowed. This is a good choice for
public or semi-public logins.
Read-only users cannot be members of groups with administrative
rights.
This setting is not available for the PRTG System Administrator user
account.
2916
Setting Description
Acknowledge Alarms This setting is only visible if you select Read-only user above.
Acknowledging an alarm is an action that requires write access. However,

you can explicitly allow a read-only user to acknowledge alarms 206 :
§ Allow user to acknowledge alarms: Allow the read-only user to
acknowledge alarms.
§ Do not allow user to acknowledge alarms (default): Do not allow the
read-only user to acknowledge alarms.
Password Change This setting is only visible if you select Read-only user above.
Define if the user can change their account password:

§ Allow user to change the account password: Allow the read-only user
to change their password. The option to change their password is
available in the My Account 2811 settings of the user.
§ Do not allow user to change the account password (default): Do not
allow the read-only user to change their password.
Primary Group Select the primary group for the user account from the dropdown list.
Every user account must be a member of a primary group to make
sure there is no user account without group membership.
Membership in other user groups is optional.
You cannot change the primary group of Active Directory users.
Users that you add via Active Directory integration 3091 can only have
the respective Active Directory group as their primary group.
Select Create new user group for this user to create a user group for the
new user. This option is only visible when you add a new user account.
The default name of the new user group is the Display Name of the new
user.
Status Define the status of the user:

§ Active: Can log in to the PRTG web interface.
§ Paused: Cannot log in to the PRTG web interface. Use this option to
temporarily deny access for this user.
This setting is not available for the PRTG System Administrator user
account.
Last Login Shows the time stamp of the last login of the user account.
2917
Group Membership
Group Membership
Setting Description
Member of Shows the user groups that the user account is a member of. You can
define access rights to device tree objects, libraries, maps, reports and
the ticket system at group level.
PRTG Web Interface
PRTG Web Interface
2918
Setting Description
Automatic Refresh Define if you want PRTG to automatically reload web pages in the PRTG
web interface for the user:
§ Automatically refresh pages (recommended): PRTG automatically
refreshes single page elements on web pages in the PRTG web
interface.
§ Do not automatically refresh pages: PRTG does not automatically

refresh single page elements on web pages in the PRTG web interface.
Refresh Interval (Sec.) This setting is only visible if you select Automatically refresh pages
(recommended) above.
Enter the number of seconds that PRTG waits between two refreshes.
We recommend that you use 30 seconds or more. The minimum value is
20 seconds. The maximum value is 600 seconds.
Shorter refresh intervals create more CPU load on the probe system.
If you experience load issues while using the PRTG web interface (or
maps 2786 ), set a longer refresh interval.
Audible Alarms Define whether PRTG plays an audible alarm on web pages in the PRTG
web interface when there is a new alarm 2911 :
§ Do not play audible alarms: PRTG does not play sound files on any
web pages.
§ Play audible alarms on dashboard pages only: When there is a new
alarm, PRTG plays a predefined sound on dashboard 253 pages only.
The sound is played with every refresh of the dashboard page if there is
at least one new alarm.
§ Play audible alarms on all pages: When there is a new alarm, PRTG
plays a predefined sound on all web pages. PRTG plays the sound with
every page refresh if there is at least one new alarm.
PRTG only plays audible alarms if the New Alarms value in the global
header area 172 of the PRTG web interface is greater than 0 after a
page refresh. PRTG does not consider the number of old alarms.
For more information, see the Knowledge Base: Which audible
notifications are available in the PRTG web interface and in the PRTG
app for desktop? and Why are audible alerts in public maps not working
in Chrome?
Home Page URL Define the user's default home page in the PRTG web interface. This is
the page that the user sees after logging in or when selecting Home 253
from the main menu. Enter a PRTG-internal web page.
Time Zone Define the time zone for the user account. Depending on the time zone
that you select, PRTG shows the local time zone of the user account in
all data tables and graph legends.
2919
Setting Description
PRTG receives the Coordinated Universal Time (UTC) from the

system time of the PRTG core server for this purpose.
If you get a warning message about differing time zones, see the
Knowledge Base: Why do I get a warning message when time zones
differ?
Date Format Select the date format for the user:

§ Use default settings: Use the date format of the PRTG core server
system.
§ DD.MM.YYYY HH:MM:SS (24h)
§ DD.MM.YYYY HH:MM:SS (A.M./P.M.)
§ MM/DD/YYYY HH:MM:SS (24h)
§ MM/DD/YYYY HH:MM:SS (A.M./P.M.)
§ YYYY-MM-DD HH:MM:SS (24h)
§ YYYY-MM-DD HH:MM:SS (A.M./P.M.)
This setting takes effect after the next login.
Color Mode Select a color mode for the PRTG web interface:
§ Light
§ Dark
Ticket System
Ticket System
Setting Description
Email Notifications Define if the user receives emails from the ticket system:
§ Receive an email when a ticket changes:
2920
Setting Description
§ The user receives an email each time a ticket is assigned to the user or
to the user group they are a member of, or if a ticket is changed.
If the user edits tickets that are assigned to them or the user group
they are a member of, or if they assign a ticket to themselves or
their user group, they do not get an email.
§ Do not receive any emails from the ticket system: The user does not
receive any emails from the ticket system.
Notification Contacts Tab
Notification Contacts
The Notification Contacts tab shows a list of all notification contacts of the selected user account.
Setting Description
Description Shows the description for the email contact.
Recipient Shows the email address for the email contact.
Type Shows the type of the notification contact.
You can add new notification contacts under Setup | Account Settings | Notification Contacts 2851 .
Comments Tab
History Tab
2921
API Keys Tab
On the API Keys tab, you can add, edit, and delete API keys that are specific to the user account. For
more information, see section API Keys 2861 .
More
KNOWLEDGE BASE


Why do I get a warning message when time zones differ?

Others
see sections:
8.12.2.6 User Groups
On the User Groups tab, you can define access rights for monitoring objects, libraries, maps, and
reports at user group level. This means that group membership determines what a user can do and which
monitoring objects, libraries, maps, or reports they can see. This does not apply to read-only users, who
always have only read access, no matter what access rights the user group they belong to has. You can
define group access rights for each object in the object's settings.
User Groups Overview

The User Groups tab shows a list of all user groups in this PRTG installation and various types of
information about each user group.
2922
Object Shows the name of the user group. Click the user group to open its
settings 2924 .
Type Shows the user group type, for example, a PRTG user group, an Active
Directory group, or a single sign-on (SSO) group.
Members Shows all users that are a member of this user group.
Primary Group Shows all users that have this user group as their primary group. Click
the user group name to open its settings 2924 .
Active Directory Group Shows the Active Directory group that the user group is connected to.
SSO Claim Shows the access claim for the SSO group that the user group is
connected to.
Add User Groups

§ To add a new user group to PRTG Network Monitor or to PRTG Hosted Monitor, hover over and
select Add User Group from the menu. The options are almost the same as for editing user groups.
§ For each user group you create, PRTG automatically adds a new group in the device tree 137 with the
name [group_name] home.
§ For each user group you create, PRTG automatically adds a new email notification 2825 to the
notification templates 2818 . It has the name Email to all members of group [group_name]. The new user
group automatically has read access 149 to the new notification template.
§ By default, there are no access rights 149 defined on objects for a newly created user group. Initially,
users in this user group do not see any objects in the device tree except the automatically created
[group_name] home group for which they have write access. This does not apply if the new user group
is an administrator group. Edit the settings 204 of objects in your device tree, libraries, maps, or
reports, and set access rights for the new user group in the Access Rights section.
The easiest way to set access rights is in the root group settings 436 and to use the inheritance of
settings 140 .
The multi-edit option is not available for the predefined user groups PRTG Administrators and PRTG
Users Group.
You cannot delete predefined objects such as the PRTG System Administrator user account, the
PRTG Users Group, or the PRTG Administrators group.
If you want to delete an Active Directory group from PRTG, you must delete all users that are in the
user group first. This is because the Active Directory users have this user group as their primary
group, and user accounts must have a primary group.
2923
User Group Settings
User Group Settings
Setting Description
User Group Name Enter a name for the user group.

Administrative Rights Define if the user group members have administrative rights:
§ Give user group members administrative rights: Give administrative
rights to all user group members.
If you select this option, all user group members have full access
to all device tree objects, libraries, maps, reports, and the ticket
system. In addition, they can manage user accounts and user groups,
and they can change the monitoring configuration of PRTG.
§ Do not give user group members administrative rights: Do not give the
user group member administrative rights. Access to device tree
objects, libraries, maps, and reports for user group members are
defined in an object's settings.
Home Page URL Define the default home page for the user group members. This is the
page that the user sees after logging in or when selecting Home 253 from
the main menu. Enter a PRTG-internal web page.
This applies to new users that were either added via Active Directory
Integration 3091 or using the Add Multiple Users option 2913 .
Active Directory or Single Define whether to connect this user group to external users:
Sign-On Integration
2924
Setting Description
§ Do not use Active Directory or single sign-on integration: Do not

connect this user group to a user group in your Active Directory or to a
single sign-on integration. Use local user accounts instead.
§ Use Active Directory integration: Connect this user group to a user
group in your Active Directory.
For more information, see section Active Directory Integration 3091 .
§ Use single sign-on integration: Connect this user group to a single sign-
on integration.
Microsoft Entra ID into PRTG?
Okta SSO into PRTG?
You cannot change credentials for users that are members of an
Active Directory group.
Active Directory Group This setting is only visible if you select Use Active Directory integration
above.
Select the user group whose members can log in to PRTG using their
Active Directory domain credentials. The according user accounts have
the access rights 149 of the user group you just created.
You need to configure a valid Active Directory domain in the Core &
Probes 2897 settings for user groups to appear in the dropdown list.
For more information, see section Active Directory Integration 3091 .
If your Active Directory contains more than 1,000 entries in total,

PRTG displays an input field instead of a dropdown list. This is for
performance reasons. In the input field, you can only enter the name of
the user group in your Active Directory. PRTG then automatically adds
the domain name prefix.
PRTG caches the list of the user groups in your Active Directory for
one hour. You can update this list earlier by manually clearing the
cache via the Administrative Tools 2928 by clicking Go! in the Clear Caches
section.
SSO Group Claim This setting is only visible if you select Use single sign-on integration
above.
Enter the access claim for the SSO group, for example a scope name or
an Azure group object ID.
2925
Setting Description
User Type This setting is only visible if you select Use Active Directory integration
above.
Define the default user access rights for all new users in this user group:
§ Read/write user: Can only view monitoring results, libraries, maps,
reports, and also edit the according settings. In addition, they can add
and delete objects, libraries, maps, and reports. The user can
acknowledge alarms, edit notification templates, notification contacts,
and schedules.
§ Read-only user: Can only view monitoring results, libraries, maps,
reports, and the according settings. The user can acknowledge alarms
and change their own password if allowed. This is a good choice for
public or semi-public logins.
Read-only users cannot be members of groups with administrative
rights.
If a user logs in to PRTG for the first time using Active Directory
credentials, PRTG automatically creates a new, local user account
for this user with the user type that you define.
Acknowledge Alarms This setting is only visible if you select Read-only user above.
Acknowledging an alarm is an action that requires write access. However,

you can explicitly allow a read-only user to acknowledge alarms 206 :
§ Allow user group members to acknowledge alarms: Allow read-only

user group members to acknowledge alarms.
§ Do not allow user group members to acknowledge alarms (default): Do
not allow read-only user group members to acknowledge alarms.
Sensor Creation Rights Define if user group members can create all sensors or only specific
sensors:
§ Allow user group members to create all sensors: No restrictions for
group members apply.
§ Allow user group members to create certain sensors only: Select the
allowed sensors from the list of available sensors.
Allowed Sensors This setting is only visible if you select Allow user group members to
create certain sensors only above.
2926
Setting Description
A list of all available sensors is shown. Select the sensors that user
group members can create by enabling check boxes in front of the
respective sensor names.
PRTG displays sensors that are in use in bold print.

This setting does not apply when a user group member runs an auto-
discovery 270 . The auto-discovery adds all sensors that are defined in
the used device templates. This setting does also not apply when a user
group member adds recommended sensors 200 .
Ticket System Access Define if user group members can use the ticket system 216 :
§ Allow user group members to use the ticket system: Users in this user
group can read, create, assign, and modify tickets.
Group members that are read-only users never have access to the
ticket system.
§ Do not allow user group members to use the ticket system: The
Tickets 263 menu item in the main menu bar is not visible to users in
this user group.
Group Members
Group Members
Setting Description
Members This setting is only visible if you select Do not use Active Directory or
single sign-on integration above.
Define which local user accounts are members of this user group. To add
a user account from the list, enable the check box in front of the user
name. The available user accounts depend on your setup.
2927
Primary Group Users
Primary Group Users
Setting Description
User List Shows a list of all user accounts that have this user group as their
primary group. This is only shown for your information. You can change
the primary group of a user account in the user account's settings 2911 .
More
KNOWLEDGE BASE

How to integrate Microsoft Entra ID into PRTG?

How to integrate Okta SSO into PRTG?

Others
see sections:
8.12.2.7 Administrative Tools
On the Administrative Tools tab, you can start system-specific processes for debugging purposes.
2928
Administrative Tools For The PRTG Core Server
Administrative Tools For The PRTG Core Server
Setting Description
Create Configuration Create a snapshot of the PRTG configuration. This action might take up
Snapshot to 100 seconds. Once it finishes, you can find a .zip file that contains a
*.dat file in the \Configuration Auto-Backups subfolder of the PRTG data
directory 3219 .
The name of the .zip file has the format PRTG Configuration
(Snapshot YYYY-MM-DD HH-MM-SS).zip.
If you run PRTG in a cluster, this action is executed on the cluster

node you are logged in to.
Write Core Status File Create status files of the PRTG core server. You can find the two text files
in the \Logs\debug subfolder of the PRTG data directory. PRTG creates
new files every time you click Go!.
The files have the names Core State (Global Debug Data).txt and
Core State (Memory Debug Data).txt.

node you are logged in to.
2929
Setting Description
Clear Caches PRTG caches tiles for Geo Maps 2741 , user data for Active Directory
Integration 3091 , and the Active Directory Group 2922 list. Click Go! to delete
the cache if you encounter broken Geo Maps tiles, if you changed a
user's password in the Active Directory, or if you added groups in the
Active Directory.
Load Lookups and File (Re)load the lookup files 3186 from the \lookups\custom subfolder of the
Lists PRTG program directory 3218 . In this subfolder, your customized lookup
files are stored. If you have created a new lookup file or changed
something in a lookup file, it might be necessary to load or to reload
these files.
With this option, you can also manually reload file lists in the PRTG web
interface. If you have added new device icons 616 , device templates 2735 ,
report templates 2774 , .oidlib files for the SNMP Library sensor, or language
files to the PRTG program directory on the PRTG core server system
while the server was running, reloading the file lists might be necessary to
display new files in the PRTG web interface.
Usually you do not need to reload file lists manually. A list is
automatically reloaded when opening the according settings page
with a latency of 10 seconds. If you save new device templates via
the PRTG web interface, the template list is refreshed immediately.
Recalculate PRTG Graph PRTG constantly writes monitoring data to disk and keeps the graphs for
Data Cache your graph tabs in memory. If PRTG unexpectedly ends, the graph cache
might become corrupted. In this case, graphs might be empty or show
wrong data.
If you experience graph display problems, a graph recalculation fixes the
problem. Click Go! to delete the data cache file and to automatically
recalculate it.
If you apply the recalculation, PRTG needs to restart the PRTG core
server. Because of this, all users of the PRTG web interface, the
PRTG app for desktop 2994 , or the PRTG apps for iOS or Android 2998 are
disconnected. After you click Go!, a dialog window appears that asks you
to confirm the required restart. Click OK to trigger the restart.
Directly after this action, your graphs are empty. PRTG successively
refills them while the recalculation in the background progresses.
Until the recalculation is finished, the performance of the PRTG web
interface might be affected because of the high disk input/output (I/O)
activity.
2930
Setting Description
Restart PRTG Core Restart the PRTG core server service manually. Click Go! to restart it.
Server Service
If you restart the PRTG core server service, all users of the PRTG
web interface, the PRTG app for desktop, or the PRTG apps for iOS
or Android are disconnected. Clicking Go! immediately restarts the PRTG
core server service.
If you want to schedule an automatic restart of Windows services for

both the PRTG core server service and the PRTG probe service, you
can do this in the corresponding probe settings 536 .
Reload Logging For debugging reasons, it might be necessary to change the log levels of
Configuration the PRTG core server. The Paessler support team takes you through the
necessary steps that are required to change your logging configuration.
The log level changes vary according to the PRTG installation, its setup,
and the solution of an issue.
To apply the changes, click Go!.
Administrative Tools For Probes
Administrative Tools For Probes
Setting Description
Write Probe Status Files Create status files of all probes. PRTG writes status files for the local
probe on the PRTG core server (in a cluster, on the cluster node you are
logged in to) as well as for all classic remote probes. PRTG creates new
files each time you click Go!.
2931
Setting Description
On the respective systems, you find six text files in the \Logs\debug
subfolder of the PRTG data directory. The files have the names Probe
State (Global Debug Data).txt, Probe State (Memory Debug Data).txt,
Probe State (Scheduler Debug Data).txt, Probe State (Syslog).txt, Probe
State (Trap).txt, and Probe State (xFlow Debug Data).txt.
This setting does not apply to any multi-platform probes 3352 . For
more information, see the Multi-Platform Probe for PRTG manual.
Restart All Probes Restart all probes as well as the local probe Windows service. If you have
classic remote probes 3201 , this restarts the probe Windows services on
the remote probe systems as well. To restart single probes only, see
below.
You cannot restart disconnected probes here. Use the PRTG
Administration Tool 3050 on the probe system to start a disconnected
probe on a Windows system. Restart disconnected probes on non-
Windows systems directly from the probe system.

node you are logged in to. In this case, remote probes are only
restarted if you are logged in to the primary master node. The cluster
probe Windows service of failover nodes is not restarted if you execute
this action on the primary master node. If you want to restart the cluster
probe Windows service of a failover node, log in to the PRTG web
interface of this failover node and click Go! there.
This setting does not apply to any multi-platform probes 3352 . For
more information, see the Multi-Platform Probe for PRTG manual.
Probe [#Number] This section shows information about the connection status. If the probe
"[Name]" is connected, the field shows the source IP address and port number that
the probe uses. For the local probe, the IP address is always 127.0.0.1.
You also see information about the date when the last data packet was
received from the probe.
If you want to restart a single probe, click the corresponding Restart
Probe button. Entries for every single probe follow.
You cannot restart disconnected probes here. Use the PRTG
Administration Tool 3050 on the probe system to start a disconnected
probe on a Windows system. Restart disconnected probes on non-
Windows systems directly from the probe system.

Monitor instance.
Others
see sections:
2932
8.12.2.8 Cluster
On the Cluster tab, you can change cluster-related settings. See the cluster status 2970 to see if all
cluster nodes are properly connected.
Cluster Node Setup
Cluster Node Setup
Setting Description
Node Name Enter the name of the cluster node. PRTG uses it for display purposes
only.
NodeID The ID is unique for every cluster node.

Node Status Set the state for each failover node:

§ Active: Set the failover node to active.
§ Inactive: Set the failover node to inactive. PRTG disables it in the

cluster configuration. The failover node is no longer an active part of the
cluster and it does not appear in the cluster status anymore.
2933
Setting Description
This setting is not available for the master node of a cluster. The
master node is always Active.
IP Addresses/DNS Define the IP addresses or Domain Name System (DNS) names that
Names Used for Node- PRTG uses for the node-node connections. You can enter different values
Node Connections for every connection.
For example, in the field #2 => #1, enter the address under which the
master node is reachable from the second cluster node. Usually, this is
the IP address or DNS name of the master node. Do this for all available
cluster node connections, for example, if you have three cluster nodes,
enter the address under which the second cluster node is reachable from
the third cluster node in the field #3 => #2.
For more information, see the Paessler website: How to set up a
failover cluster in PRTG in 6 steps.
If you use remote probes 3203 outside your local network or outside
your network address translation (NAT), make sure that the IP
addresses or DNS names that you enter are valid for both the cluster
nodes to reach each other and for remote probes to reach all cluster
nodes individually. These addresses must not be private and must be
reachable from the outside, otherwise the remote probes cannot connect.
Multi-platform probes do not support clusters.
settings are lost.
For more information on how to set a cluster node into Maintenance Mode, see section Cluster
Status 2970 .
The entire setup process for a cluster requires several different steps. For more information and step-
by-step guidance, see the Paessler website: How to set up a failover cluster in PRTG in 6 steps.
More
KNOWLEDGE BASE

PAESSLER WEBSITE
How to set up a failover cluster in PRTG in 6 steps

§ https://www.paessler.com/support/how-to/failover-cluster
2934
Others
see sections:
8.12.2.9 Single Sign-On
On the Single Sign-On tab, you can select a single sign-on (SSO) provider and configure other related
settings.
Requirements and Restrictions

SSO has the following requirements and restrictions.
For more information, see also section Notes 2940 .
Requirement/Restricti Description
on
SSO configuration You must first configure Microsoft Entra ID or Okta accordingly before you
can integrate it into PRTG or PRTG Hosted Monitor for SSO. For
example, you must register PRTG as an application.
§ For more information, see the Knowledge Base: How to integrate
Microsoft Entra ID into PRTG?
§ For more information, see the Knowledge Base: How to integrate
Microsoft Entra ID into PRTG Hosted Monitor?
§ For more information, see the Knowledge Base: How to integrate Okta
SSO into PRTG?
Freeware edition § SSO is not available for the freeware edition 21 .
SSO users § Do not have access to the PRTG API 3094 .
§ Cannot log on to a failover node in a cluster.
§ Cannot change the Login Name in PRTG.
2935
Single Sign-On Settings
Single Sign-On Settings
Setting Description
SSO Login Define if you want to enable login via SSO:

§ Enable
Provider This setting is only visible if you select Enable above.
Select an SSO provider from the dropdown list:

§ Microsoft Entra ID: Use Microsoft Entra ID as the SSO provider.
§ Okta: Use Okta as the SSO provider.
Configuration Endpoint This setting is only visible if you select Enable above.
2936
Setting Description
Enter the configuration endpoint URL.

Click Load Configuration to automatically fill in the values for
Authorization Endpoint, Token Endpoint, JSON Web Key Set
(JWKS) URI, and Issuer. If this does not work, then manually enter the
values.
Microsoft Entra ID URL format example:

https://login.microsoftonline.com/<tenant-ID>/v2.0/.well-
known/openid-configuration

Microsoft Entra ID.
Okta URL format example:
https://<your-Okta-domain>/oauth2/<authorization-server-ID>/
.well-known/oauth-authorization-server
You can find the URL in the field Metadata URI under Security | API
in the Okta administrator console.
Authorization Endpoint This setting is only visible if you select Enable above.
Enter the entire endpoint URL for authorization purposes, not only the
server part.
Microsoft Entra ID example:

Microsoft Entra ID.
Okta example:
https://<your-Okta-domain>/oauth2/default/v1/authorize
Make sure to replace <your-Okta-domain> with the Okta domain of

your application from the Okta administrator console.
Token Endpoint This setting is only visible if you select Enable above.
Enter the entire token endpoint URL, not only the server part.

Microsoft Entra ID.
Okta example:
2937
Setting Description
https://<your-Okta-domain>/oauth2/default/v1/token

JSON Web Key Set This setting is only visible if you select Enable above.
(JWKS) URI
Enter the URI of the JWKS, not only the server part.
ID>/discovery/v2.0/keys

Microsoft Entra ID.
Okta example:
https://<your-Okta-domain>/oauth2/default/v1/keys

Issuer This setting is only visible if you select Enable above.
Enter the SSO issuer.

https://login.microsoftonline.com/<tenant-ID>/v2.0

Microsoft Entra ID.
Okta example:
https://<your-Okta-domain>/oauth2/default

Scope This setting is only visible if you select Enable above.
Enter the scope for SSO.

openid profile offline_access email api://<client-
ID>/<scope-name>
Make sure to replace <client-ID> with the application (client) ID from

Microsoft Entra ID and the <scope-name> with a scope name.
Okta example:
openid offline_access email profile
2938
Setting Description
Application (Client) ID This setting is only visible if you select Enable above.
Enter the application (client) ID from Microsoft Entra ID or the Client ID of

Client Secret This setting is only visible if you select Enable above.
Enter the client secret to verify the integrity of the SSO token.
Group Claim Retrieval This setting is only visible if you select Microsoft Entra ID above.
Select if you want to use an access token or GraphQL to retrieve the

group claims from Microsoft Graph:
§ Access token (default)
§ GraphQL
If you select GraphQL to retrieve the group claims, PRTG

automatically adds user.read to the scope.
If you select GraphQL and log in for the first time, a window opens
and asks for the needed permissions. Click Accept to grant the
permissions.
Endpoint Handling This setting is only visible if you select Enable above.
Define whether to select the callback from a list of callbacks or to

manually enter a callback:
§ Select from a list of endpoints (default): Select an endpoint from a list of
available endpoints.
§ Manually enter a URL: Manually enter an endpoint URL below.
You need to enter a manual callback if you access PRTG via a
different DNS name. For example, if you access PRTG via
myPRTG.example.com but the actual DNS name of the PRTG core
server is myPRTG.internal.example.com, you need to enter a manual
callback.
Available Callback URLs This setting is only visible if you select Enable and select Select from a
list of endpoints (default) above.
This list shows the available callbacks of this PRTG instance. Select the
callbacks that your users use to connect to PRTG.
If you define an HTTPS endpoint in this field, you need to configure
the HTTPS endpoint as a valid redirection URI in your SSO provider's
settings.
2939
Setting Description
External Callback URL This setting is only visible if you select Enable and select Manually enter
a URL above.
If you access PRTG via a different DNS name, define the HTTPS
endpoint.
This is necessary if the DNS name that you configured under Setup |
System Administration | User Interface does not appear in the Available
Callback URLs list. For example, if you access PRTG via
myPRTG.example.com but the actual DNS name of the PRTG core
server is myPRTG.internal.example.com, then enter
myPRTG.example.com. Also make sure to add the port used by PRTG
for HTTPS and the endpoint in the URL, for example:
myPRTG.example.com:PORT/cb.
If you define an HTTPS endpoint in this field, you need to configure
the HTTPS endpoint as a valid redirection URI in your SSO provider's
settings.
Available Callback URLs This setting is only visible if you select Enable and select Manually enter
(for reference) a URL above.
This list shows the available callbacks URLs of this PRTG instance for
reference purposes.
Test Single Sign-On Click Test Single Sign-On Authorization Endpoint to call the authorization
Authorization Endpoint endpoint to check if starting the single sign-on process will succeed.
In case of errors, check the answer from the endpoint.
settings are lost.
Notes
§ If you want to further improve the security for sign-in events, we recommend that you enable multi-
factor authentication for Microsoft Entra ID or Okta.
ú For more information, see the Knowledge Base: How can I enable Microsft Entra ID multifactor
authentication?
ú For more information, see the Knowledge Base: How can I enable Okta multi-factor authentication?
§ When an SSO user logs in to the PRTG web interface 157 , PRTG automatically creates a
corresponding local account on the PRTG core server.
2940
§ By default, no access rights for monitoring objects, libraries, maps, or reports are set for the new user
group in PRTG. This is why, initially, users in this user group do not see monitoring objects, libraries,
maps, or reports. This does not apply if the new user group has administrative rights. Edit the
monitoring object's settings 204 and the settings of libraries, maps, and reports, and set access rights
for the newly created user group in the respective Access Rights section.
We recommend that you set these access rights in the root group settings 469 and use the
inheritance of settings 140 .
§ A local user account for an SSO user is only created if this SSO user has successfully logged in to
PRTG. If you want to send email notifications 2825 to an SSO group in PRTG, using the option Send to
User Group in the notification settings, a member of this SSO group must log in to PRTG at least once
to receive email notifications. To avoid this, enter the email address of the SSO group in the Send to
Email Address field in the notification settings and select None for the Send to User Group option.
§ If you want to delete an SSO group from PRTG, you must delete all users that are in this user group
first. This is because SSO users always have this user group set as their primary group, and user
accounts cannot be without a primary group.
§ If a license is not valid, is temporarily unavailable, or is being updated, SSO does not work during this
time.
More
KNOWLEDGE BASE

How to integrate Microsoft Entra ID into PRTG Hosted Monitor?

How to integrate Okta SSO into PRTG?

How can I enable Microsft Entra ID multifactor authentication?
How can I enable Okta multi-factor authentication?

Others
see sections:
8.12.2.10 Maintainer Mode
Use the Maintainer Mode to pause and resume devices or check the status of devices without an active
user session or user account.
2941
Maintainer Mode Settings
Maintainer Mode Settings
Setting Description
Maintainer Mode Define if you want to enable Maintainer Mode:

§ Enable
Access Key This setting is only visible if you select Enable above.
Shows the access key that you need for the API for authentication
purposes.
The access keys are URL friendly.
Generate new access This setting is only visible if you select Enable above.
key
Enable the check box next to Generate new access key, click Save, and
reload the page to generate a new access key.
Maintainer Mode API Endpoints and Parameters

You can execute the following actions by using the following endpoints:
1. Query Device Status
Endpoint Parameter Description
\api\public\maintain NodeID Use this parameter to define the object ID of the device of
er_querydevicestat which you want to query the status. Enter an integer.
us.htm
You can find the object ID in the info box on the
Overview tab of the device.
accesskey Use this parameter to define the access key that you
need for the API for authentication purposes. Enter a
string.
2942
Example
https://yourserver/api/public/maintainer_querydevicestatus.htm?
nodeid=deviceID&accesskey=myaccesskey
2. Pause Device
er_pausedevice.ht which you want to query the status. Enter an integer.
m
string.
name Use this parameter to define a name for the user that
pauses the device. Enter a string.
The name appears in the status on the Overview tab
of the device.
comment Use this parameter to define a comment for the paused

device. Enter a string.
The comment appears in the status on the Overview
tab of the device.
Example
https://yourserver/api/public/maintainer_pausedevice.htm?
nodeid=deviceID&accesskey=myaccesskey&name=myname&comment=mycomment
3. Resume Device
er_resumedevice.ht which you want to query the status. Enter an integer.
m
2943
string.
name Use this parameter to define a name for the user that
resumes the device. Enter a string.
The name appears in the log on the Log tab of the
device.
Example
https://yourserver/api/public/maintainer_resumedevice.htm?
nodeid=deviceID&accesskey=myaccesskey&name=myname
Others
see sections:
2944
8.12.3 PRTG Status
To view the status of your PRTG installation, select Setup | PRTG Status from the main menu bar 265 .
PRTG Status Tabs
In this section:
§ System Status 2945
8.12.3.1 System Status
On the System Status tab, you can view relevant system information. Furthermore, this page shows
interesting usage statistics. Use the quick links for fast access to status information.
You might need this data for debugging or when you contact the Paessler support team. They ask
you in some cases to provide system status information to analyze any issues with PRTG.
Quick Links
In this section:
§ Software Version and Server Information 2946
§ System Startup Log 2949
§ System Warnings 2950
§ Local Status 2951
§ Cluster Connections 2952
§ PRTG Core Server System Memory 2953
§ Thread Information 2956
2945
§ Activity History 2958
§ Auto-Discovery Tasks 2959
§ Background Tasks 2959
§ Database Objects 2960
§ Sensors Sorted by Impact on System Performance 2962
§ Sensors Sorted by Interval 2963
§ Probes 2963
§ System Settings 2964
§ Web Server Activity 2967
§ Synchronization 2969
Software Version and Server Information

This section shows information about the software version and the PRTG core server system.
Softw are Version and Server Information
Category Description
PRTG Version Shows the exact build version of the PRTG installation.
Auto-Update Status Shows the latest auto-update message available from the auto-update 2979 .
For example, the message indicates that an update was successfully
installed.
This information is not displayed in PRTG Hosted Monitor.
2946
Operating System Shows the exact Windows version, build, and service packs, the number
and kind of CPUs, and the computer name of the PRTG core server
system.
If you run PRTG in a cluster, this shows information for the system of
the cluster node you are logged in to.
If you run PRTG on virtual systems, some of the information might

not be available.
This information is not displayed in PRTG Hosted Monitor.
Server Time Shows the date and time of the PRTG core server system.
Server CPU Load Shows the CPU load of the PRTG core server system.
User Name Shows the user name 2811 of the user account that you are logged in to
PRTG with.
Active User Sessions Shows the user names of all user accounts that are logged in to PRTG.
When a user account logs out, it takes up to 1 minute until the user
name disappears.
Browser Shows the name and user agent string of the browser that you are viewing
this page with.
License Information
This section shows information about your license.
2947
License Information
Setting Description
License Status Shows the activation status of this PRTG installation. Usually, PRTG
automatically completes the activation during installation or when you
change your license information.
If PRTG cannot directly connect to the internet, a manual activation
is necessary.
For more information, see section Activate the Product 107 .
License Name Shows the owner of the license 105 that you use for this PRTG
installation, for example ExampleOrganization.
The License Name (PRTG Network Monitor only), license key, and
system ID make up your license information.
You can find the label License Owner in some documents from the
Paessler shop. License Owner is the same as License Name. PRTG
might ask you for this information during installation or when you change
your license key 105 .
License Key Shows the license 105 key that you use for this PRTG installation.
System ID The system ID is a fixed value that is automatically assigned to a PRTG

installation.
2948
Setting Description
Licensed Edition Shows the license that you use for this PRTG installation. This
determines how many sensors you can use in PRTG.
Last Update Shows the date of the last update for this PRTG installation. We
recommend that you use the auto-update 2979 .
Maintenance until Shows the expiration date and the number of days that remain for your
active maintenance. Manage your license at the Paessler shop for
continued access to any available updates and to our premium email
support.
This information is not visible in Paessler PRTG Enterprise Monitor.
Number of Sensors Shows the number of sensors that you can use in PRTG. If you reach the
limit, PRTG automatically sets each new sensor that you add to the
Paused status 184 .
Editions that allow an unlimited number of sensors do not restrict the
number of possible sensors by license, so you can create sensors until
you reach the performance limit 28 . This means that you can use about
10,000 sensors per PRTG core server. However, this number depends on
the performance of the PRTG core server system, and sensors and
scanning intervals.
For more information, see section System Requirements 23 .
System Startup Log

This section shows the log information that was created during the last startup of the PRTG core server.
If you run PRTG in a cluster, this shows information for the system of the cluster node you are
logged in to.
2949
System Startup Log
System Warnings
This section shows if there are any warnings. Usually, you see None.
System Warnings
Cluster Status
This setting is only visible if you have a failover cluster 132 . This section shows all of your cluster nodes.
2950
Cluster Status
Node x Shows the name and type of the cluster node (primary node or secondary
node) and its status (current master node or failover node). It also shows
all connections from this cluster node to the other cluster nodes.
For more information, see section Cluster Status 2970 .
Local Status
This setting is only visible if you have a failover cluster 132 . This section shows information about the
cluster node that you are logged in to.
Local Status
Server State Shows the name of the cluster node and its status (current master node
or failover node).
Cluster Messages Shows internal summary information about the cluster node and the
communication between the cluster nodes. You might be asked about
this by the Paessler support team.
2951
Cluster Connections
This setting is only visible if you have a failover cluster 132 . This section shows information about the
connections between the cluster nodes.
Cluster Connections
State of Local Node Shows the treeversion and size of the server volume, both types of
internal system information.
State of Cluster Shows the name and IP address, a state cyclic redundancy check (CRC)
Members code, the time stamp of the last "keep alive" signal, the size of the buffer,
and the remote IP address of each cluster node.
Message State of Cluster Shows the name and unique identifier, the connection state, and
Members statistics about the cluster message system of each cluster node.
2952
PRTG Core Server System Memory
This section shows machine-oriented information regarding the memory usage of the PRTG core server
system.
logged in to.
2953
2954
Committed The amount of memory that your system commits to the PRTG core
server system.
Allocated The amount of memory that the PRTG core server system is currently
using.
Unused The amount of allocated memory that the PRTG core server system is
currently not using.
Free Physical The amount of free memory that is currently available in the physical
memory of the PRTG core server system.
Total Physical The total amount of memory that is provided by the physical memory of
Free Pagefile The amount of free memory that is currently available in your system’s
pagefile(s).
Total Pagefile The total amount of memory of your system’s pagefile(s).
Free Virtual The amount of free memory that is available in the virtual memory of the
PRTG core server system.
Total Virtual The total amount of memory of the virtual memory of the PRTG core
server system.
Free Effective The effective amount of free memory on your PRTG core server system.
This corresponds to Free Pagefile.
Object Count The number of PRTG-internal data structures, also known as tree nodes,
for example, the number of sensors, users, and reports.
BaseInstance The amount of memory that is used for the tree node Instance.
BaseAccess The amount of memory that is used for the tree node Access Rights.
BaseHistory The amount of memory that is used for the tree node History of
Configuration Changes.
BaseCurrent The amount of memory that is used for the tree node Current
Configuration Information.
BaseData The amount of memory that is used for the tree node Configuration Data.
2955
BaseChannel The amount of memory that is used for the tree node Channel Settings.
BaseTrigger The amount of memory that is used for the tree node Trigger.
BaseIDs The amount of memory that is used for the tree node IDs.
BaseLookup The amount of memory that is used for the tree node Sensor Lookups.
BaseCheck The amount of memory that is used for the tree node Check Requests.
BaseDeplist The amount of memory that is used for the tree node Dependency List.
Datasets The amount of memory that is currently used for datasets, like for graphs.
State The amount of memory that is currently used for user-specific datasets.
Interface The amount of memory that is currently used for tree node-specific table
objects.
IndexCache The amount of memory that is currently used for the index dataset cache
that is particularly important in a cluster.
TreeTotal The total amount of memory that is used by the PRTG tree.
DatasetCache The amount of memory that is currently used for the dataset cache, in
particular regarding historic data. In parentheses, you see the number of
datasets that are saved in the cache.
StorageSystem The amount of memory space that is currently used for the storage
system.
Sessions The amount of memory that is currently used for sessions. A user can
activate more than one session. In parentheses, you see the number of
currently activated sessions.
StateObjects The number of user-specific state objects that are found in the memory of
Thread Information
The section shows machine-oriented information regarding threads that are running on the PRTG core
server system.
2956
logged in to.
Thread Information
2957
Activity History
This section shows how busy PRTG was for you in the past. The graphs indicate the number of activities
in the last 365 days. Below the graphs, you see statistics about the past day.
Activity History
Sensor Scans Shows how often all sensors 138 refreshed their data in the past.
Sensor Status Changes Shows how often the sensor states 184 changed in the past.
Notifications Sent Shows how many notifications 2745 PRTG sent out in the past.
Reports Generated Shows how many reports 2764 PRTG created in the past.
Page Views Shows how often pages in the PRTG web interface were opened in the
past.
Sensors Shows how many sensors existed in the past.
2958
Devices Shows how many devices 138 existed in the past.
Reports Shows how many reports existed in the past.
Maps Shows how many maps 2786 existed in the past.
Auto-Discovery Tasks
This section shows information on the auto-discovery 270 .
Auto-Discovery Tasks
Running Shows the number of auto-discovery tasks that are running.

A high number of auto-discovery tasks can negatively influence
system performance.
Background Tasks
This section shows information on background tasks.
Background Tasks
2959
Historic Data Shows if PRTG is recalculating the historic data cache in the background.
If so, you see the tasks to do until done. Usually, PRTG does this
calculation after every PRTG core server restart.
Toplist Buffer Shows the size of the Toplist buffer. When you use Flow (NetFlow, jFlow,
sFlow, IPFIX) 3021 or Packet Sniffer 3019 sensors, PRTG stores Toplist data.
The data stream received is buffered and written to the data directory of
Depending on the number and size of the data stream as well as the
hard disk and system performance of the PRTG core server system,
the buffer size can rise. When the buffer size reaches 500, PRTG drops
Toplist data, which can lead to incorrect Toplist values for the sensors.
Similar Sensors Shows the status and the selected setting for the depth of the similar
Detection sensors 195 analysis.
Recommended Sensors Shows the status of the detection engine and the tasks of the
Detection recommended sensors detection 2884 .
Database Objects
This section shows statistic information about your monitoring configuration. This information might be
necessary when contacting the Paessler support team.
2960
Database Objects
Probes Shows the total number of probes 474 in the PRTG installation.
Groups Shows the total number of groups 541 in the PRTG installation.
Devices Shows the total number of devices in the PRTG installation.
Sensors Shows the total number of sensors in the PRTG installation.
Channels Shows the total number of channels 138 in the PRTG installation.
User Groups Shows the total number of user groups 2922 in the PRTG installation.
Users Shows the total number of users 2911 in the PRTG installation.
Notifications Shows the total number of notifications 2818 in the PRTG installation.
2961
Schedules Shows the total number of schedules 2856 in the PRTG installation.
Maps Shows the total number of created maps in the PRTG installation.
Libraries Shows the total number of created libraries 2748 in the PRTG installation.
Reports Shows the total number of reports in the PRTG installation.
BitField/Boolean/Integer/ Shows the total number of used lookups by lookup type 3194 .
Range Lookups
Requests/Second Shows a value that is 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 probes to the devices in
your network.
There are no general guidelines on what a good value is here. This
depends on the sensors that you use as well as on the performance
of the probe system.
Sensors Sorted by Impact on System Performance

This section shows all sensors that you use in your configuration in order of performance impact (from
very low to very high). If the CPU load of the probe system is very high, you can see which sensors might
be causing this issue. Consider the recommended number of sensors in the respective sections for
sensors with a high or very high performance impact.
In the list, internal short names are used for sensors instead of the official designations. You can
find a list of all sensors and their internal IDs, among others, via /sensorlist.htm, for example
https://yourserver/sensorlist.htm.
You can also see the performance impact of a sensor on the sensor's Overview tab or in the Add
Sensor 430 dialog.
Types 3237 .
2962
Sensors Sorted by Impact on System Performance
Sensors Sorted by Interval

Shows all sensors used in your configuration in order of scanning interval. Choose reasonable scanning
intervals for sensors that can affect the system performance. See the respective sections for sensors for
more information.
In the list, internal short names are used for sensors instead of the official designations. You can
find a list of all sensors and their internal IDs, among others, via /sensorlist.htm, for example
https://yourserver/sensorlist.htm.
Sensors Sorted by Interval
Probes
This section lists all probes in your monitoring setup. If there are no remote probes, only the local probe
or the hosted probe appears in the list, which always runs on the PRTG core server.
logged in to. Remote probes (if any) are only shown when you are logged in to the primary master
node. When you are logged in to a failover node, the cluster probe on this cluster node appears as local
probe.
2963
Probes
Probe #x "[Name]" Shows information about the connection status. If the probe is connected,
the field shows the source IP address and port number used by the
probe. For the local probe, the IP address is always 127.0.0.1. You also
see information about the date when the last data packet was received
from the probe.
If you want to restart a single probe, open the Administrative Tools 2928
settings.
System Settings
This sections shows information about system settings.
2964
System Settings
Web Server URL Shows the URL to access the PRTG web interface 156 .
Web Server IP Shows all IP addresses that the PRTG web server runs on.
Addresses
2965
Web Server Ports Shows the ports that the PRTG web server runs on.
Web Server Port Usage Shows the type of port used by the PRTG web server.
SSL/TLS Versions for Shows the Secure Sockets Layer (SSL)/Transport Layer Security (TLS)
Web Server versions used for connections to and from the PRTG web server.
This is only shown if you use an SSL/TLS-secured connection.
Web Server Ciphers Shows the ciphers used by the PRTG web server.
SSL/TLS Versions for Shows the SSL/TLS versions used for the probe port.
Probe Port
Probe Ciphers Shows the ciphers used for the remote probe connection.
DH Parameters Size Shows the length of the Diffie-Hellman (DH) parameters.
Incoming Probe Shows a combination of the incoming probe connection IP address and
Connection Binding the incoming probe connection port.
Incoming Probe Shows a list of all IP addresses on which PRTG listens for incoming
Connection IP Addresses remote probe connections.
This is the same information as in the Core & Probes 2900 settings.
0.0.0.0 means that the PRTG core server listens on all local network
adapter IP addresses.
Incoming Probe Shows the port number on which the PRTG listens for incoming remote
Connection Port probe connections. The default port is 23560.
Probe Allow IP Shows all source IP addresses that PRTG accepts for incoming remote
Addresses probe connections.
2966
any means that all remote probe connections are accepted,
regardless of the IP address of the remote probe system.
Probe Deny IP Shows all source IP addresses that PRTG denies for incoming remote
Addresses probe connections.
Denied IP addresses are superior to allowed IP addresses. If this
field is empty, there are no denied IP addresses.
PRTG automatically adds the IP address of a remote probe system
to this list when you delete a remote probe from the device tree 136 .
Data Path Shows the path where PRTG stores its configuration, monitoring
database, etc.
To change this setting, open the PRTG Administration Tool 3057 on
the PRTG core server system (or of the respective cluster node, if
applicable).
Web Server Activity

This section shows statistics about the PRTG web server since the last startup. All values are reset
when the PRTG core server is restarted.
logged in to.
2967
Web Server Activity
Time Since Startup Shows the time that has passed since the PRTG web server was started.
Page Views Shows the total number of page views on this PRTG core server.
Geo Maps Shows the total number of geographical maps shown on this PRTG core
server.
HTTP Requests Shows the total number of HTTP requests to this PRTG core server.
HTTP Requests > 500 Shows for how many (percent) of the HTTP requests above the page
ms delivery took longer than 500 milliseconds (ms).
ms delivery took longer than 1,000 ms.
ms delivery took longer than 5,000 ms.
Slow Request Ratio Shows a calculated number of the HTTP request values above.
The lower this number is, the faster the PRTG web interface is.
Failed Logins Shows the number of recent failed logins and failed logins in total.
(Recent/Total)
PRTG only shows this statistic when the number of failed logins is
larger than 50.
2968
Synchronization
The PRTG core server holds the configuration of the entire monitoring setup and deploys it to the probes.
This section shows statistics about the synchronization of the PRTG core server with the local probe and
all connected remote probes (if any), since the last startup of the PRTG core server. All values are reset
when the PRTG core server is restarted.
logged in to. You must log in to the primary master node to see synchronization data for remote
probe connections.
Synchronization
Last Synchronization Shows the time stamp of the last probe synchronization, and if there is
with a Probe still something to do.
Probe/Core Message Shows the total number of messages sent between the PRTG core server
Count and probes, as well as a calculated message speed value.
Raw Buffer Count Shows the number of raw buffers and a corresponding status indicator.
Configuration Requests Shows the total number of configuration requests and the requests that
Sent still need to be sent.
Configuration Requests Internal debug information. Usually, this value is 0.

Deleted
2969
Configuration Requests Internal debug information. Usually, this value is 0.

With Response
More
KNOWLEDGE BASE

Others
see sections:
8.12.3.2 Cluster Status
On the Cluster Status tab, you can view all cluster nodes.
This tab is only available if you run PRTG in a failover cluster 132 .
The following information is available:
§ Cluster Status: Shows all connected cluster nodes
§ Cluster Log: Shows all log entries for cluster connections
2970
Cluster Status
Click the Start Maintenance Mode link to put a cluster node in maintenance mode. A cluster node in this
mode is still connected to the cluster, but PRTG discards its monitoring results until you click the Stop
Maintenance Mode link. You can use this to explicitly exclude a cluster node from monitoring if you
know that the monitoring values are not accurate, for example, because you are reconfiguring the server.
During maintenance, PRTG displays a cluster node with a transparent color in the overview graphic.
On the Cluster Status tab, you do not see if your remote probes are connected to failover nodes 3215 .
Connect to your failover nodes and explicitly check if remote probes are connected, for example, in
the device tree of the PRTG web interface on a cluster node.
For more information about cluster settings, see section Cluster 2933 .
Others
see sections:
2971
8.12.4 License Information
On the License Information tab, you can view information about your license and enter your license key.
License Tabs
In this section:
§ Status 2972
§ Log 2974
§ Change and Update License Information 2975
§ Update Your License Information 2975
§ Proxy Configuration 2976
Status
Click the Status tab to view information about your license.
2972
License Information
License Information
Setting Description
License Status Shows the activation status of this PRTG installation. Usually, PRTG
automatically completes the activation during installation or when you
change your license information.
If PRTG cannot directly connect to the internet, a manual activation
is necessary.
For more information, see section Activate the Product 107 .
License Name Shows the owner of the license 105 that you use for this PRTG
installation, for example ExampleOrganization.
Paessler PRTG Enterprise Monitor subscription licenses do not have
a License Name.
Customer ID Shows your customer ID you have a Paessler PRTG Enterprise Monitor
subscription license.
This information is not visible in PRTG Network Monitor.
2973
Setting Description
License Key Shows the license 105 key that you use for this PRTG installation.
System ID The system ID is a fixed value that is automatically assigned to a PRTG

installation.
Licensed Edition Shows the license that you use for this PRTG installation. This
determines how many sensors you can use in PRTG.
Last Update Shows the date of the last update for this PRTG installation. We
recommend that you use the auto-update 2979 .
Maintenance until Shows the expiration date and the number of days that remain for your
active maintenance. Manage your license at the Paessler shop for
continued access to any available updates and to our premium email
support.
This information is not visible in Paessler PRTG Enterprise Monitor.
Subscription until Shows the expiration date and number of days that remain for your
Paessler PRTG Enterprise Monitor subscription license.
This information is not visible in PRTG Network Monitor.
Number of Sensors Shows the number of sensors that you can use in PRTG. If you reach the
limit, PRTG automatically sets each new sensor that you add to the
Paused status 184 .
Editions that allow an unlimited number of sensors do not restrict the
number of possible sensors by license, so you can create sensors until
you reach the performance limit 28 . This means that you can use about
10,000 sensors per PRTG core server. However, this number depends on
the performance of the PRTG core server system, and sensors and
scanning intervals.
For more information, see section System Requirements 23 .
To upgrade your license right now, click Need more sensors? Click
here to upgrade! to visit our web shop.
Log
Click the Log tab to show a table list 221 of all system log entries with all messages and status changes
regarding your license.
2974
Change and Update License Information
Use the following buttons to edit your license or refresh your maintenance information.
Button Description
<%B_Manage_License% Click to open the Paessler shop and manage your PRTG Network Monitor
> license. This button is only visible to users of a commercial license.
Deactivate this License If you want to use the license of a PRTG installation on a different
computer, click this button to deactivate the license. This is necessary,
for example, when you move PRTG to a different computer, because a
PRTG license can be active on only one computer at the same time.
Once you have deactivated the license, the PRTG installation on this
computer reverts to the freeware edition 21 after a grace period of 30
days.
See also section Activate the Product 107 .
Update Your License Information

Click Change License Key or Refresh Information on the Status tab to update your license. Provide the
necessary information and click Update License to complete the activation of your license.
If you have any issues with license activation or updates, click Contact Support in the page footer to
contact us directly via the Paessler Service Center in our shop. This requires internet access.
Step 1: Choose Activation Type
Setting Description
Activation Type Define how you want to validate and activate your license:
§ Automatic (online activation with optional HTTP proxy): Activate the
license online. PRTG connects to the activation server and validates
your license. The license is activated automatically. For automatic
activation, the PRTG core server system must have internet access.
§ Manual (offline activation): Activate the license manually. Use this if the
PRTG core server system has no access to the internet and cannot
connect to activation.paessler.com.
This is the default selection if the PRTG core server system is
offline.
Step 2: Verify Your PRTG License
2975
Setting Description
License Key Enter the license key you have received from us, the Paessler AG. To
avoid typing errors, copy and paste the License Key. It must exactly
match your license key.
License Name Enter the License Name that you have received from us, the Paessler
AG. It must exactly match. To avoid typing errors, copy and paste the
License Name.
Paessler PRTG Enterprise Monitor subscription licenses do not have
a License Name.
System ID This field shows the system ID, a fixed value assigned to your PRTG
installation.
For offline activation, click Save to File to write your license information into a text file.
Step 3a: Activate Your PRTG
If you select the automatic activation type, you can now update your license. Define if you need an HTTP
proxy for the HTTPS connection to the activation server and click Update License.
Proxy Configuration
Setting Description
Proxy Server Handling Define if you want to use PRTG with a direct internet connection or if a
proxy is necessary:
§ Do not use a proxy server (default): Do not use a proxy. Use this
setting if a direct internet connection to the PRTG core server system
is available.
§ Use a proxy server: Define proxy settings below. Use this setting if a
proxy is mandatory in your network.
We recommend that you use PRTG with a direct internet connection.
2976
Setting Description
The proxy settings are valid for auto-update 2979 , activating the
product 107 , obtaining Geo Maps 2741 tiles, and for sending HTTP,
push, and SMS text message notifications 2825 .
Server This setting is only visible if you select Use a proxy server above
Enter the address of the proxy server that you use for outbound
connections. Enter a valid address.
Port This setting is only visible if you select Use a proxy server above
Enter the port number of the proxy server that you use for outbound
connections. Enter an integer.
Proxy Authentication This setting is only visible if you select Use a proxy server above
Determine whether the proxy server needs credentials or not:

§ Do not use authentication: Do not use credentials for proxy
connections.
§ User name and password: Define credentials (user name and
password) below. Use this setting if the proxy server requires
credentials.
Enter a user name for proxy authentication. Enter a string.
Enter a password for proxy authentication. Enter a string.
Step 3b: Request Activation Data
The following step only applies to PRTG Network Monitor. If you use PRTG Enterprise Monitor, see
the Paessler website: How to use PRTG Enterprise Monitor in an offline environment in 5 steps.
If you select Manual (offline activation), you must request your activation data at
https://shop.paessler.com/service/licenseactivation/ using your license information. Open the activation
page from a computer with internet access and provide your license information.
Generate the key file for your license and provide this data below.
Step 4: Provide Activation Data
2977
This step is only necessary if you activate your license offline.
§ Copy the content of the key file that you have generated on
https://shop.paessler.com/service/licenseactivation/.
§ Paste it into the Activation Data field. Alternatively, click Load from File if you have saved the key file
with your activation data.
§ Click Update License to complete the activation of your license.
More
KNOWLEDGE BASE
How do I upgrade to a later edition of PRTG?

The automatic license activation of my PRTG Enterprise Monitor license does not work. What can I do?
PAESSLER WEBSITE
How to use PRTG Enterprise Monitor in an offline environment in 5 steps
§ https://www.paessler.com/support/how-to/prtg-enterprise-monitor-offline
Others
see sections:
2978
8.12.5 Auto-Update
In the Auto-Update settings, you can check the status of the auto-update, view logs, and edit settings.
When a new version of PRTG is available on the Paessler website, PRTG automatically downloads the
setup file if a direct internet connection is available. The PRTG System Administrator user then receives
a ToDo ticket 216 with instructions to initiate the update installation.
If you use the freeware edition or trial edition 21 , automatic software updates are available at any
time. If you use a commercial edition 21 , you need to have active maintenance to receive updates.
Auto-Update
Auto-update has the following tabs:
§ Status: Click the Status tab to download and install updates.
§ Log: Click the Log tab to show log information about the update status of PRTG, newest first. In the
table list 221 , you can filter the items by using the respective options 221 .
§ Settings: Click the Settings tab to configure the auto-update and release channel. See Software Auto-
Update 2980 below.
2979
Using Auto-Update
If there is a new version available, you see detailed information about the available version. Read these
notes carefully. You find a summary of current and past release notes below the update section. For
more information about the release notes, see the Paessler website: PRTG Release Notes and Version
History.
To install the latest available version, click Install Update [version number]. PRTG asks you to confirm
installation and license.
Downloaded software versions are automatically saved in the \download subfolder of the PRTG
program directory 3218 . The prtg.zip that contains all necessary files is also cached in this subfolder.
Manually Install an Interim Update

Not all available updates from Paessler are pushed to all customers but they are still available on the
website. Sometimes the Paessler support team might ask you to update to the latest version.
In this case, click Check For Latest Update and Download. PRTG connects to the Paessler servers and
downloads the setup file, regardless of the status of the update check. Then click Install Update [version
number].
To manually install an interim update, a direct internet connection is necessary on the PRTG core
server system.
Software Auto-Update
Softw are Auto-Update
Setting Description
When a New Version is Define what PRTG does when software updates are available:
Available
§ Automatically download and install: Download and install any new
version as soon as PRTG detects that a newer version is available.
PRTG checks for a newer version once per day.
The installation of a new version restarts the PRTG core server
service and PRTG probe service and might also include a system
restart.
2980
Setting Description
§ Automatically download and alert the admin: Download any new version
as soon as PRTG detects that a newer version is available. PRTG
checks for a newer version once per day. After successful download,
PRTG creates a ToDo ticket 216 for the PRTG System Administrator
user.
§ Alert the admin only: Do not download updates. Only create a ToDo
ticket. You can still manually download updates via the auto-update 2980 .
Installation Time This setting is only visible if you select Automatically download and install
above.
Select the desired time for the installation of updates from the dropdown
list. You can select As soon as the update is available to install updates
at any time of the day.
Release Channel Define the release channel that PRTG delivers updates in:
§ Stable: Updated about once every 8 weeks (most conservative option,
default): Deliver updates in the Stable release channel. These are our
best tested versions.
Use these software versions for live environments that you depend
on.
§ Preview: Updated twice between stable releases (thoroughly tested in
our labs, do not use on production systems): Deliver updates in the
Preview release channel. Versions in this channel were thoroughly
tested in our labs but might still contain limitations in certain monitoring
configurations.
Use this release channel if you are willing to take a little risk for the
benefit of getting new features and bug fixes a little earlier.
We strongly recommend that you not use these software versions

in live environments that you depend on.
§ Canary: Updated daily (testing only, should not be used on production
systems): Deliver updates in the Canary release channel. These
versions are updated every night.
Use with caution. Software versions in this channel have not been
tested, might contain severe bugs, and are provided for testing
purposes only.
We strongly recommend that you not use these software versions in
live environments that you depend on.
settings are lost.
Notes
There are a few things that we ask you to consider regarding automatic software updates:
2981
§ For automatic software updates to work, the PRTG core server system must have direct internet
access. If a proxy connection is necessary, configure it in the Core & Probes 2898 settings.
For more information about the update servers, see the Knowledge Base: Which servers does
PRTG connect to for software auto-update, activation, etc.?.
§ During installation, the PRTG core server system might restart without notice.
§ PRTG automatically updates classic remote probes, which might cause short downtimes in the
monitoring of remote locations. In rare cases, a manual update of classic remote probes is required
after you update the PRTG core server. In these cases, you are notified in the device tree, and the
monitoring of remote locations is interrupted until you perform the manual update 109 on the remote
probe system. If a probe system uses several network connections with different IP addresses, make
sure that these IP addresses are included in the list of allowed IP addresses 2900 . Otherwise, the
remote probe on this system might be disconnected after an update.
§ PRTG does not automatically update multi-platform probes. If you installed a multi-platform probe via
the Paessler Linux package repository, your package manager notifies you when there is an update.
Otherwise, manually update your multi-platform probes with the updated package. For more
information, see the Multi-Platform Probe for PRTG manual.
§ In a cluster, you only need to install the update on one cluster node. PRTG automatically deploys the
new version to all other cluster nodes. This might cause a short amount of downtime for the monitoring
on the cluster nodes, one after the other.
§ If you run several individual PRTG core servers that are not in a cluster, you must initiate and confirm
an update for each single PRTG core server.
§ You can disable automatic downloading on the auto-update Settings 2979 tab. PRTG then only
downloads updates when you click Check For Latest Update and Download.
§ PRTG does not start auto-update downloads if less than 500 MB disk space is available on the PRTG
core server system. If this is the case, you can check this on the Log 2979 tab.
§ Virus scanners might potentially cause issues when downloading or installing software updates. To
avoid such issues, we recommend that you make the appropriate exclusions for the PRTG program
directory.
More
KNOWLEDGE BASE
Which servers does PRTG connect to for software auto-update, activation, etc.?
Which information does PRTG send back to Paessler?

PAESSLER WEBSITE

2982
Others
see sections:
2983
8.12.6 Optional Downloads
To see optional downloads, select Setup | Optional Downloads from the main menu bar 265 . Click a tab
to switch between different options.
Optional Dow nloads Tabs
In this section:
§ PRTG Apps 2984
§ PRTG MultiBoard 2984
§ Classic Remote Probe Installer 2984
PRTG Apps
To monitor your network while on the go, use our free PRTG apps for smartphones and tablets. They run
on iOS and Android.
For more information, see section PRTG Apps for Mobile Network Monitoring 2998 .
For more information about PRTG for iOS and PRTG for Android, see the Paessler website: PRTG
apps for iOS or Android.
PRTG MultiBoard
Download PRTG MultiBoard to your system. You can run it on Windows, macOS, or Linux to manage
one or several independent PRTG core servers 128 or PRTG Hosted Monitor instances with a native,
cross-platform application.
For more information, see section PRTG MultiBoard 2994 .
Classic Remote Probe Installer

With remote probes, you can extend your monitoring to distributed networks that are not directly
reachable from your PRTG core server system. The version of the classic remote probe installer must
match your version of PRTG, so it is a good idea to download it from here.
For more information, see section Install a Remote Probe 109 .
If you want to extend your monitoring to non-Windows systems, learn more about the multi-platform
probe: Multi-Platform Probe for PRTG (PDF).
More
PAESSLER WEBSITE
PRTG MultiBoard
§ https://www.paessler.com/prtg/extensions/prtg-multiboard
PRTG app for desktop
2984
§ https://www.paessler.com/prtg-desktop
PRTG apps for iOS or Android

§ https://www.paessler.com/apps
Others
see sections:
2985
8.12.7 Help and Support Center
In the Help and Support Center, you can access help and support information for PRTG.
Help and Support Center
The following help and support topics are available:
§ PRTG Manual 14
§ Knowledge Base
§ Video Tutorials
§ Advanced Topics 3090
§ Technical Support 2987
§ Customer Service 165
Others
see sections:
2986
8.12.8 Contact Support
The Contact Support feature is only available for users with active maintenance with their PRTG
Network Monitor, PRTG Enterprise Monitor, or PRTG Hosted Monitor license. This feature is not
available for freeware edition licenses.
For technical issues, use the Contact Paessler Support / Send Your Feedback to Paessler form in
PRTG. To open the form, select Setup | Contact Support from the main menu bar 265 . You can also open
the form via Contact Support in the footer on every page in the PRTG web interface.
2987
How to Open the Contact Support Form
When you click Contact Support, the following form appears:
2988
Contact Paessler Support / Send Your Feedback to Paessler
On the one hand, you can use this form 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 that contains several selected PRTG log files and status files. This information really
helps the Paessler support team to analyze any issue you might have with PRTG. Also consider the
suggested links to articles regarding the scope of your issue.
On the other hand, you can use this form to give us feedback. Help improve PRTG by providing criticism,
praise, bug reports, and feature requests. Any comments are welcome. Your feedback is handled
directly by the Paessler support team.
PRTG securely transmits your feedback or support question including the support bundle to Paessler via
the PRTG Cloud. Read more in our Knowledge Base on how we handle your feedback.
2989
Make sure that your PRTG core server system has access to the internet and can reach the URL
https://api.prtgcloud.com:443
Form Details
Ask a Question or Give Feedback
Provide the following information in this section of the contact form.
Field Description
Your Ticket ID PAE<id> If you already have an open ticket (directly via our Help Desk portal), enter
the ticket ID. You can find it in your confirmation email regarding the
request we received. You can provide the ID with PAE in front or only the
number.
If you leave this field empty, you create a new ticket when you
submit this form.
Your Email Address Enter your email address. You can provide any of your addresses.
However, by default, PRTG uses the email address of your user account
to be able to associate you with your license.
Scope of Your Question Select a topic regarding your issue and consider the suggested links.
Emotional State If you want to, you can express your feelings about PRTG.
Enter a Subject for Your Provide short information with a maximum of 60 characters to indicate the
Question/Feedback topic of your issue.
Enter a Detailed Leave any comments. They can be feedback or support questions. If you
Description have a support question, describe your issue with as much detail as
possible.
Attach a Screenshot and/or Support Bundle
To provide the most helpful information possible, you can attach a screenshot of the selected page and a
support bundle with useful analytical data about your PRTG installation.
Setting Description
Do not attach screenshot Send the ticket without a screenshot.

If you ask for technical help, we recommend that you attach a
screenshot. This helps us a lot to analyze your issue and to provide
a solution.
2990
Setting Description
Create and attach PRTG creates a screenshot of the selected page and sends it with your
screenshot ticket. You can see a preview below the screenshot section.
(recommended)
We recommend that you open the contact support form directly on
the page where you encountered an issue. Taking screenshots is not
possible on some generic error pages that are not meaningful enough for
the Paessler support team.
In section Support Bundle, you can choose from several packages that differ in coverage of information.
Setting Description
Support Bundle Select the information you want to send to the Paessler support team:
§ Attach Base Pack with log files (recommended): Contains the following
data about PRTG:
ú System status
ú Lists of sensors in the Down status or the Unknown status
ú Core and probe health data
ú Current log entries
§ Attach Base Pack with log files and PRTG configuration file: Contains
the Base Pack and the PRTG configuration file.
Send this package only if the Paessler support team asks you to.
User names, encrypted passwords in the config.dat file, and
passwords that your browser masks while you enter them on settings
pages are removed before PRTG sends this package to the Paessler
support team.
§ Do not attach a Support Bundle: The ticket does not contain files.
Choose this option only when sending feedback.
Click Submit to send your request directly to the Paessler support team, or click Cancel to return to the
page where you opened the contact form.
Helpdesk
Write us in English or German and communicate via the Helpdesk.The Paessler support team works
closely with our development department to guarantee the fastest and most constructive assistance
possible. As they need to analyze a lot of data over the course of a support case, like log files and
screenshots, they use the Helpdesk as their primary support mechanism. Their office is staffed Monday
to Friday from 07:00 to 22:00 (UTC+1), so you receive an answer within 24 hours on business days.
Depending on the complexity of the case, they might need to ask for remote access to your system, or
to schedule a remote desktop session.
2991
Other Resources
Knowledge Base
Find answers to common questions in our Knowledge Base.
Supported Versions
Note that we only support PRTG versions that were released in the last 12 months. For more information
on released versions, see the Paessler website: Release notes for the "stable" release channel.
License and Upgrades
If you have questions or feedback regarding your license purchase or want to upgrade your license,
contact our customer service 165 .
Network Planning
If you need help with your network setup or detailed installation planning, our partners are always happy
to help. Please contact a partner near you.
Security Reports
If you are a user of PRTG or any of our other services and would like to file a security report, send an
email to security@paessler.com. Always include a detailed technical summary in your email. If you wish
to send us an encrypted email, use the public key on this page https://www.paessler.com/support.
More
KNOWLEDGE BASE
How can I propose new features or sensors for PRTG?

PAESSLER WEBSITE

Others
see sections:
2992
Part 9
PRTG MultiBoard
5/2/2024 2993
9 PRTG MultiBoard
PRTG MultiBoard is a PRTG extension that functions as an alternative interface for PRTG. It is available
on Windows, macOS, and Linux and you can use it to connect to one or several independent PRTG core
servers 128 or PRTG Hosted Monitor instances to configure your setup, view monitoring results, and keep
an eye on your network. It is a cross-platform application for fast access to data and monitoring
management.
PRTG MultiBoard natively includes most PRTG features. For a few options, the application opens an
external browser window using your default browser, for example, for system setup or probe installation.
PRTG MultiBoard is mainly designed to review and manage PRTG installations that you already set
up. If you have just started with monitoring, we recommend that you first run through the smart
setup 42 in the PRTG web interface 156 and add your network devices there. Once finished, you can
seamlessly switch to PRTG MultiBoard.
PRTG Hosted Monitor supports connections from PRTG MultiBoard. For more information, see
section Using PRTG Hosted Monitor.
Download the PRTG MultiBoard from the Paessler website: PRTG MultiBoard.
Requirements
For more information, see the PRTG MultiBoard and PRTG app for desktop manual (PDF).
PRTG version Your PRTG core server or PRTG Hosted Monitor instance must run as of
PRTG 17.4.35.
PRTG license type You must be a Paessler PRTG Enterprise Monitor user.
PRTG Network Monitor users can use the general features of PRTG
MultiBoard with the Paessler PRTG app for desktop.
General Features
General features include Multi-Edit, Desktop Alerts, and Compare Sensors.
These features are available for PRTG Network Monitor users.
2994
PRTG app for desktop w indow
MultiBoard Features
MultiBoard features include the MultiBoard, Probe Transfer, Configuration Viewer, and Template Transfer
features.
MultiBoard w indow
2995
With MultiBoard, you can connect to several independent servers to view their data and manage your
monitoring centrally. Within the MultiBoard pages, you can find the following:
§ Dashboard: Use different widget types to show overviews of your configured servers at a glance.
§ Details: Display all sensors of all configured servers as a sensor list or in a more detailed table view.
§ Report: Display an overview of the number of sensors on each connected server and in total, and the
number of sensors that show a specific status.
§ Sets: Group sensors into customized sensor sets across all your PRTG core servers and PRTG
Hosted Monitor instances.
§ Overview: View and edit all device tree objects in all of your PRTG core servers and PRTG Hosted
Monitor instances.
More
KNOWLEDGE BASE
PAESSLER WEBSITE
How to set up notifications for the PRTG app for desktop

§ https://www.paessler.com/support/how-to/notifications-desktop
Paessler PRTG MultiBoard

§ http://www.paessler.com/prtg/extensions/prtg-multiboard
2996
Part 10
PRTG Apps for Mobile Network
Monitoring
4/9/2024 2997
10 PRTG Apps for Mobile Network
Monitoring
You can access your PRTG installation on your mobile devices with PRTG apps for iOS or Android. You
can download and use these apps for free. PRTG for iOS 2998 and PRTG for Android 2999 let you monitor
your network while on the go.
The basic requirements to use these free PRTG apps are a running PRTG core server that is accessible
from the network your device is connected to (either directly or via a VPN connection) and a recent
operating system version on your mobile device. For details about requirements, see below.
PRTG for iOS

PRTG for iOS is the iOS app that you can use as of PRTG 13. You can use the newest PRTG app
version on iPhone, iPad, and iPod touch as of iOS version 9. You can also use free push notifications 2840
with this PRTG app (required: at least PRTG for iOS 14.3.6; PRTG 15.4.20).
For more information and to download this PRTG app, see the Paessler website: PRTG for iOS. For
troubleshooting solutions, see the Knowledge Base: I have an issue with PRTG for iOS. What can I
do?
2998
Sensor and channels on PRTG for iOS
PRTG for Android

PRTG for Android is the Android app that you can use as of PRTG 14. Use it on your smartphone or
tablet as of Android version 4.0, or on a Kindle Fire. For full functionality, we recommend that you use at
least Android 4.1. You can also use free push notifications 2840 with the PRTG app (required: at least
PRTG for Android 14.3.2; PRTG 15.4.20).
For more information and to download this PRTG app, see the Paessler website: PRTG for Android.
For troubleshooting solutions, see the Knowledge Base: I have an issue with PRTG for Android.
What can I do?
2999
Sensor List on PRTG for Android
More
KNOWLEDGE BASE
I have an issue with PRTG for iOS. What can I do?

I have an issue with PRTG for Android. What can I do?

Which features do the PRTG apps for iOS or Android support?


3000
PAESSLER WEBSITE
PRTG apps for iOS or Android

§ https://www.paessler.com/apps
3001
Part 11
Desktop Notifications
3002 8/24/2023
11 Desktop Notifications
While you are logged in to the PRTG web interface with Google Chrome or Mozilla Firefox, PRTG can
show notifications on your desktop whenever there are new alarms in your monitoring.
PRTG shows desktop notifications (by default, in the lower-right corner of your desktop) whenever there
are new alarms after a page refresh in the PRTG web interface. The notification displays the number of
new alarms and the current number of each sensor status 184 .
Example of a Desktop Notification in Google Chrome
Desktop notifications are not available for Internet Explorer.
Desktop Notifications Settings

When you log in to the PRTG web interface, a message appears, asking you to allow desktop
notifications. You must initially allow the notifications for each installation or profile of Firefox or Google
Chrome.
Desktop notifications in Google Chrome are not available for HTTP connections. See section User
Interface 2866 for more information.
§ In Google Chrome, click Allow to add the URL of the PRTG web interface to the allowed sites.
§ In Firefox, click Allow Notifications to add the URL of the PRTG web interface to the allowed sites.
Click 'Allow ' to enable Desktop Notifications in Google Chrome
Click 'Allow Notifications' to enable Desktop Notifications in Mozilla Firefox
3003
Disabling or Re-Enabling Desktop Notifications
To disable or re-enable desktop notifications for the PRTG web interface, edit your browser options:
§ In Google Chrome: Click the View site information icon in the address bar of the browser. You can
block or re-enable notifications for the PRTG web interface in section Notifications.
§ In Mozilla Firefox: Click the Notification permission icon in the address bar of the browser. You can
block or re-enable notifications for the PRTG web interface in section Permissions.
Others
see sections:
3004
Part 12
Sensor Technologies
2/28/2023 3005
12 Sensor Technologies
This section introduces different technologies that PRTG uses for monitoring to give you more
background information.
In this section:
§ Monitoring via SNMP 3007
§ Monitoring via WMI 3014
§ Monitoring via SSH 3017
§ Monitoring Bandwidth via Packet Sniffing 3019
§ Monitoring Bandwidth via Flows 3021
§ Bandwidth Monitoring Comparison 3024
§ Monitoring Quality of Service 3026
§ Monitoring Backups 3031
§ Monitoring Virtual Environments 3032
§ Monitoring Databases 3038
§ Monitoring via HTTP 3042
3006
12.1 Monitoring via SNMP
Monitoring via the Simple Network Management Protocol (SNMP) is the most basic method of gathering
bandwidth and network usage data.
How SNMP Monitoring Works

SNMP is a set of standards for communication with devices in a Transmission Control Protocol (TCP)/IP
network. SNMP monitoring is useful if you are responsible for servers and network devices such as
hosts, routers, hubs, and switches. It enables you to keep an eye on network and bandwidth usage, and
to monitor important metrics such as uptime and traffic levels.
You can use SNMP to monitor the bandwidth usage of routers and switches on a port-by-port basis, as
well as device readings such as memory and CPU load. The target devices must support SNMP. Most
devices with enabled SNMP require the same configuration (identical SNMP version and community
string). To learn how to set up SNMP on a specific device, search the internet for its name and SNMP
configuration.
Netw ork Monitoring via SNMP
When you use a sensor with this technology, PRTG sends small data packets to a device, which in turn
trigger reply packets. Compared to other bandwidth monitoring technologies via World Wide Name
(WWN), packet sniffing, or Windows Management Instrumentation (WMI), the SNMP option creates the
least CPU and network load.
Reasons to Choose SNMP Monitoring

SNMP is the most commonly used method because it 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 that you start with SNMP.
Besides network usage monitoring, another well-known feature of SNMP is the ability to also monitor
other network parameters such as CPU load, disk usage, temperature, as well as many other readings,
depending on the queried device.
3007
SNMP Network Issues
To use SNMP for monitoring purposes, it is necessary that User Datagram Protocol (UDP) packets can
be bidirectionally sent from the PRTG core server to the target device. This is usually the case in LANs
and intranets. For connections across the internet, to a perimeter network (also known as DMZ,
demilitarized zone, and screened subnet), or for WAN connections, some changes to the traversed
firewalls might be necessary.
Keep in mind that SNMP v1 and v2c are no secure protocols, so you should not use them on the internet
or with data connections that are not secure. Only SNMP v3 supports encryption.
Understanding SNMP Sensors

To better understand and set up SNMP sensors, you might want to learn more about the principles of
object identifiers (OID) and Management Information Base (MIB) files.
For more information, see the Knowledge Base: How do SNMP, MIBs and OIDs work?
For more information about all SNMP sensors, see section Available Sensor Types 3284 .
SNMP Versions
PRTG supports three versions of the SNMP protocol: version 1, 2c, and 3.
SNMP v1
This is the oldest and most basic version of SNMP.
§ Pro: Supported by most SNMP-compatible devices.
§ Con: Limited security because it only uses a simple password (community string 3010 ) and sends data
in clear text (unencrypted). Because of this, you should only use it inside LANs behind firewalls, but
not in WANs. SNMP v1 only supports 32-bit counters, which are not enough for high-load
(gigabits/second) bandwidth monitoring.
SNMP v2c
This version adds 64-bit counters.
§ Advantage: Supports 64-bit counters to monitor bandwidth usage in networks with gigabits/second
loads.
§ Disadvantage: Limited security (see SNMP v1).
SNMP v3
This version adds authentication and encryption to SNMP.
§ Advantage: Offers user accounts and authentication for multiple users and optional data packet
encryption to increase available security. Has all advantages of SNMP v2c.
§ Disadvantage: Difficult to configure and higher overhead for the probe, which reduces the number of
devices that you can monitor (see SNMP Overload and Limitations of the SNMP System 3009 for more
information).
3008
SNMP Traps
Various devices can send SNMP trap messages to notify you of system events.
§ PRTG supports SNMP v1 and SNMP v2c traps.
§ The destination for SNMP traps is the IP address of the trap receiver, which is the IP address of the
probe system to which you add the SNMP Trap Receiver sensor.
Which SNMP Version Should I Choose?
This depends on your environment. Here are some guidelines:
§ If your network is publicly accessible, you might want to use SNMP v3, which has encryption and
secure access. However, this also adds overhead, which results in less performance.
§ If your network is isolated or well-protected behind firewalls, the lower security level of SNMP v1 or
SNMP v2c might be sufficient.
§ If you have a lot of devices to monitor, SNMP v2c is preferable since it has a shorter scanning interval
and supports 64-bit counters.
Make sure to set the same SNMP version in the PRTG settings (for example, in the root group
settings 436 ) as in the target device. If you select an SNMP version that is not supported by the server or
target device, you receive an error message. These error messages often do not explicitly say that you
are using the wrong SNMP version and only provide minimum information, such as cannot connect.
Similar errors occur when community strings, user names, or passwords do not match.
For more information about basic requirements for SNMP monitoring, see the Knowledge Base: My
SNMP sensors don’t work. What can I do?
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 can monitor 30,000 SNMP v1 sensors in a 60-second scanning interval with one PRTG core
server (and local probe) plus two remote probes with 10,000 sensors each.
SNMP v3 has performance limitations because of the use of encryption. Furthermore, keep in mind that
SNMP v3, unlike SNMP v1 and v2c, does not scale with more CPU power. Because of this limitation,
PRTG can only handle a limited number of requests per second so that you can use only a limited
number of sensors using SNMP v3.
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 Health sensor
(values above 0 % indicate that the SNMP requests cannot be performed at the desired interval), you
need to distribute the load among probes. SNMP v1 and v2 do not have this limitation.
If you run into SNMP overload problems, you have the following options:
§ Increase the scanning interval of the SNMP v3 sensors.
§ Distribute the SNMP v3 sensors among two or more probes.
§ Evenly distribute the SNMP v3 sensors on your devices (about 10 to 100 sensors per device).
3009
§ Check if your target devices answer fast enough. Performance issues might also result from slow
SNMP v3 devices.
§ Switch to SNMP v1 or v2 if you can go without encryption.
What is the SNMP Community String?

The SNMP community string is similar to a user ID or password that allows access to the statistics of a
device. PRTG 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 discards the request and does not respond.
SNMP community strings are only used by devices that support SNMP v1 and SNMP v2c. SNMP v3
uses safer user name/password authentication, along with an encryption key.
By convention, most SNMP v1/v2c equipment ships with a read-only community string set to the value
public. It is standard practice for network managers to change all the community strings to customized
values during device setup.
Check SNMP Capability

Make sure that each target device supports SNMP, and that SNMP is enabled. You can find out whether
a device supports SNMP by either going to the vendor’s website or checking that it is enabled in the
configuration of the device.
If you are uncertain whether SNMP is enabled on the target device and works, we recommend that
you try SNMP Tester. You can scan for uptime to perform a basic check for SNMP availability of the
target device.
Setup Checklist
1. Enable SNMP on the device.

2. In the security settings of the device, allow SNMP access for the PRTG core server system.
3. Allow User Datagram Protocol (UDP) packages to be sent bidirectionally from the PRTG core server
to the device.
4. SNMP requires the use of UDP ports >1023 to the PRTG client side. This is important for your
firewall settings.
5. Make sure that the firmware of the device is up to date.
6. Select the appropriate SNMP protocol.
It is important to know which SNMP version you need to select, because if it is not supported by the
server or device you want to monitor, you receive an error message.
For more information, see the Knowledge Base: My SNMP sensors don’t work. What can I do?
3010
SNMP Monitoring Overview
Vendor-specific SNMP Sensors

PRTG offers many vendor-specific SNMP sensors for some common vendors. These sensors are
programmed to match the respective end devices. There are also workarounds for known vendor
implementation issues, for example, if SNMP has not been fully implemented on an end device
according to the RFCs. Here, our vendor-specific sensors still automatically receive the most important
values.
Supported Vendors
§ APC
§ Buffalo
§ Cisco
§ Dell
§ Fujitsu
§ HP
3011
§ HPE
§ IBM
§ Jacarta
§ Juniper
§ LenovoEMC
§ NetApp
§ Nutanix
§ Poseidon
§ QNAP
§ Rittal
§ SonicWall
§ Synology
Generic SNMP Sensors

PRTG offers several generic sensors that work with almost every device that supports SNMP, the
corresponding Management Information Base (MIB) file and OIDs, and it correctly implements the
respective RFCs. The standard SNMP libraries of PRTG include predefined, common values for the
generic SNMP sensors. You can monitor the following parameters with the generic sensors.
Operating System-based SNMP Sensors

PRTG also offers several operating system-based SNMP sensors that extend your SNMP monitoring.
You can monitor the following parameters with these sensors.
Custom SNMP Sensors

PRTG also offers custom SNMP sensors. The monitoring capabilities of these sensors extend the scope
of the generic sensors. With custom sensors, you can show certain values that are not included in the
standard libraries of PRTG. With these sensors, you can monitor most devices that support SNMP and
for which PRTG does not have native sensors. Basically, you only need to find out the required OIDs for
the desired device readings, for example, in the vendor’s documentation for your hardware device.
For more information, see the Knowledge Base: How do I find out which OID I need for an SNMP
Custom sensor?
More
KNOWLEDGE BASE
How do SNMP, MIBs and OIDs work?


3012
The interface numbers on my switch keep changing. What can I do?
What can I check if SNMP and SSH sensors throw timeout and auth errors?
What can I monitor with the SNMP Custom Table sensor?

How can I import my MIB files into PRTG?

Can't find a sensor for my device in PRTG but I believe it supports SNMP. How to proceed?
PAESSLER TOOLS
MIB Importer and SNMP Tester

§ https://www.paessler.com/tools
PAESSLER WHITE PAPER
Introducing SNMP and Putting SNMP into Practice

§ https://www.paessler.com/learn/whitepapers/introducing_snmp
VIDEO TUTORIAL
SNMP basics
§ https://www.paessler.com/support/videos-and-webinars/videos/snmp-basics
SNMP debugging
§ https://www.paessler.com/support/videos-and-webinars/videos/snmp-debugging
3013
12.2 Monitoring via WMI
You can monitor Windows systems via Windows Management Instrumentation (WMI) and Windows
performance counters 3014 . WMI is the Microsoft base technology for monitoring and managing Windows-
based systems. PRTG uses it to access data of various Windows configuration parameters and status
values. Note that sensors that use the WMI protocol generally have a high impact on system
performance. In addition to strict WMI sensors, there are sensors that can use performance counters to
monitor Windows systems.
To monitor via WMI and performance counters, it is usually sufficient to provide credentials for Windows
systems 438 in PRTG. However, monitoring via WMI is not always trivial and can cause issues.
If you run into issues with WMI, see the Knowledge Base: My WMI sensors don't work. What can I
do?
It is also possible to use Simple Network Management Protocol (SNMP) for Windows devices. The same
information is often available using any of these protocols. Regarding performance, the preference is
SNMP, then WMI or performance counters.
How WMI Works

WMI allows access to the data of many Windows configuration parameters, as well as 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 versions as of Windows Server 2000. PRTG officially supports WMI as of
Windows 7.
WoW64 (Windows 32-bit on Windows 64-bit) must be installed on target systems that run Windows
Server 2016. This allows 32-bit applications to be run on 64-bit systems. This is necessary because
the PRTG probe service only runs with 32-bit support. Without it, WMI sensors do not work.
To monitor remote machines, WMI sensors need Active Directory account credentials to have access to
the WMI interface. You can enter these credentials in the settings of the parent device or group, or in the
root group 436 . The sensor then inherits these settings.
Sensors using the WMI protocol generally have a high impact on the system performance. Try to
stay below 200 WMI sensors per probe 127 . Above this number, consider using remote probes 3203 for
load balancing.
For more information about all WMI sensors, see section Available Sensor Types 3315 .
Monitoring Windows Systems: Performance Counters

Besides sensors that can monitor Windows systems only via WMI, PRTG provides sensors that can use
a hybrid approach. If you choose the hybrid approach, these sensors first try to query data via Windows
performance counters using the Remote Registry service. 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 tries to connect to performance counters again after 24 hours. You can change the Preferred Data
Source in the Windows Compatibility Options in the device settings 612 .
You can identify these hybrid sensors by looking at their categories, for example, in the Add
Sensor 430 dialog. Search directly 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.
3014
Limitations of WMI on Windows Server 2008 (R1)
You should be aware that the performance of WMI-based monitoring is drastically limited when the
monitoring station or the monitored client runs on Windows Server 2008 (R1). When it comes to network
monitoring via WMI, Windows Server 2008 R2 is many times faster than Windows Server 2008 (R1).
These are not limitations of PRTG. They arise from the WMI functionality built into the Windows
operating systems mentioned.
These limitations also apply to Windows Vista, which is no longer officially supported. You can still
monitor machines that run Windows Vista, but the PRTG core server and probes are no longer
supported on this operating system.
The results of our tests are:
§ As of Windows Server 2008 R2 or Windows 7, you can run most WMI sensors if you provide optimal
conditions, such as running the PRTG core server system and the target systems exclusively under
Windows Server 2008 R2 and being located within the same LAN segment. Actual performance can be
significantly lower depending on the network topology and the WMI health of the target systems. We
have seen configurations that could not go beyond 500 sensors (and even less).
§ On Windows 2008 (R1), you can run about 300 WMI sensors with a 1-minute scanning interval.
§ The more Windows 2008/Windows 7 client systems you have in your network, the more the WMI
monitoring performance is 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, consider the following
rules:
§ Do not use Windows 2008 (R1) as monitoring stations for WMI-based network monitoring.
§ Use at least Windows Server 2008 R2 for WMI-based network monitoring instead.
§ Consider setting up remote probes for the WMI monitoring. You still get far better WMI monitoring
performance with a remote probe on a virtual machine (VM) running Windows Server 2008 R2 than on
any physical system running Windows 2008.
§ Consider switching to SNMP-based monitoring for large networks. Using SNMP, you can monitor 10
times as many objects than with WMI on the same hardware.
More
KNOWLEDGE BASE

Which WQL queries are used by the PRTG WMI sensors?

Why do I receive the sensor error message 'Connection could not be established (code: PE015)'?
3015
VIDEO TUTORIAL
Bandwidth monitoring with SNMP and WMI

§ https://www.paessler.com/support/videos-and-webinars/videos/bandwidth-monitoring-basic
PAESSLER TOOLS
WMI Tester
§ https://www.paessler.com/tools/wmitester
3016
12.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 macOS X systems. If your system is supported, this
monitoring technology works without any additional software on the target systems.
How Monitoring via SSH Works

To monitor remote machines via SSH, PRTG needs the credentials (preferably root access) of the
devices. If you use SSH sensors, you can enter the necessary credentials in the settings 204 of the
parent device or group, or in the root group, in the Credentials for Linux/Solaris/macOS (SSH/WBEM)
Systems section. The sensors then inherit these settings by default.
With each scanning interval, PRTG logs in to your devices and queries data by executing specific
commands.
For more information about all SSH sensors, see section Available Sensor Types 3237 .
For a list of encryption algorithms that the SSH sensors support, see the Knowledge Base: Which
encryption algorithms do PRTG SSH sensors support?
Limitations When Using SSH Monitoring

Because of the plurality of Linux/Unix derivatives, SSH sensors cannot support all distributions on the
market. Also, only certain macOS systems are supported.
For a list of successfully tested distributions, see the Knowledge Base: Which Linux or macOS
distributions are supported by the Linux/Unix sensors (SSH, SNMP)?
Authentication via SSH Private Key

PRTG supports authentication via password or via private key.
When you use a private key, make sure to note the following:
§ Provide the key in OpenSSH RSA format.
§ The key cannot be encrypted. PRTG does not support password-protected keys.
§ The key must be provided as an RSA key; you cannot use DSA keys.
When you provide an unencrypted RSA private key in OpenSSH RSA format, copy the entire key,
including the
-----BEGIN RSA PRIVATE KEY-----
and
-----END RSA PRIVATE KEY-----
lines, into the designated text field in PRTG and Save your settings. Once you have pasted in and saved
the private key, PRTG shows it as
***************************
3017
For more information about how to convert and use an SSH key, see the Knowledge Base: How can
I use private keys for my SSH sensors with PRTG?
More
KNOWLEDGE BASE

Which Linux or macOS distributions are supported by the Linux/Unix sensors (SSH, SNMP)?
How can I use private keys for my SSH sensors with PRTG?
How do I enable SSH on my macOS system?

3018
12.4 Monitoring Bandwidth via Packet Sniffing
Packet sniffing comes into consideration if your network devices do not support the Simple Network
Management Protocol (SNMP) or Flow (NetFlow, jFlow, sFlow, IPFIX) to measure bandwidth usage and if
you need to differentiate the bandwidth usage by network protocol and/or IP addresses.
Packet Sniffer sensors support Toplists 2718 (for example, Top Talkers or Top Connections).
How Packet Sniffing Works

If you need to know what applications or IP addresses cause the traffic in your network, you can use a
packet sniffer. A packet sniffer looks at every single data package that travels through your network for
accounting purposes.
Monitoring w ith PRTG via Packet Sniffer Sensors
PRTG can analyze the packets that pass the network card of a PC or you can connect it to the
monitoring port of a switch. To calculate bandwidth usage, PRTG inspects all network data packets
either passing the PC's network card (shown on the left side in the schema above) or the data packages
that a monitoring port of a switch (right side) sends with its built-in packet sniffer. Using remote probes,
you can set up packet sniffers anywhere in your network.
Packet Sniffer sensors use the npcap library to monitor traffic.
Comparing 3024 the four bandwidth monitoring technologies that PRTG provides (SNMP, Windows
Management Instrumentation (WMI), flows, and packet sniffing), packet sniffing creates the most CPU
and network load, so you should only use it in small to medium-sized networks, on dedicated computers
for larger networks, or for individual computers.
3019
Reasons to Choose Packet Sniffing
It is important to understand that the packet sniffer can only access and inspect data packages that
actually flow through the network interfaces of the probe system. This is fine if you only want to monitor
the traffic of this machine (for example, your web server). In switched networks, only the traffic for a
specific machine is sent to each machine's network card, so PRTG usually cannot discern the traffic of
the other machines in the network.
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 Switched Port Analyzer (SPAN)). In this
case, the switch sends a copy to the monitoring port of all data packages traveling through the switch.
As soon as you connect one of the probe system's network cards to the switch's monitoring port, PRTG
can analyze the entire traffic that passes through the switch.
An alternative is to set up the PRTG core server system as the gateway for all other computers in the
network.
Packet Sniffer Sensors

PRTG offers the following packet sniffer sensors:
§ Packet Sniffer
§ Packet Sniffer (Custom)
Header-Based Packet Sniffing

For packet sniffing, PRTG looks at the IP addresses and ports of source and destination to assess the
protocol. This is a very fast method and saves system resources.
Sometimes, this method is not fully accurate. For example, it is not possible to identify HTTP traffic
on ports other than 80, 8080, and 443 as HTTP. HTTP traffic on non-standard ports would not be
accounted as such.
More
KNOWLEDGE BASE
3020
12.5 Monitoring Bandwidth via Flows
Using Flow (NetFlow, jFlow, sFlow, IPFIX) protocols, you can monitor the bandwidth usage of all packets
going through a device. In PRTG, you can view Toplists 2718 for all xFlow sensors.
xFlows are monitoring data pushed from network devices to PRTG. You can use them to monitor where
and how much data is traveling to and from. This way, they determine which machine, protocol, or user
is consuming bandwidth. PRTG supports the following xFlow types:
§ NetFlow v5/v9 and IPFIX: Originally introduced by Cisco and supported by several vendors.
§ jFlow: Traffic sampling technology introduced by Juniper networks.
§ sFlow: Short for sampled flow, introduced by HP. sFlow uses statistical sampling of the traffic at
defined intervals to achieve scalability for high volume interfaces.
You can also use packet sniffing 3019 for bandwidth monitoring if your hardware does not support any of
these xFlow versions.
How Flow Monitoring works

You can measure bandwidth usage by IP address or by application in a network, using one of the flow
protocols. They are the best choice especially for networks with high traffic (connections with hundreds
of megabits or gigabits).
For flow monitoring, the router gathers bandwidth usage data (flows), aggregates it, and sends
information about it to PRTG using User Datagram Protocol (UDP) packets. When you use sampling
(mandatory for sFlow), only information about every n-th packet is sent to PRTG, which reduces CPU
load a lot. Because the switch already performs an aggregation of traffic data beforehand, the flow of data
to PRTG is much smaller than the monitored traffic. This makes flow 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 a
NetFlow or IPFIX packet for each data flow to the monitoring system running on a probe. You can filter
and evaluate the data in PRTG. Different NetFlow and IPFIX sensors are available: The basic sensors
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 server system compared to Packet Sniffer sensors.
You must enable NetFlow or IPFIX export on the target device. The device must send a flow data
stream to the IP address of the probe system on which you set up the NetFlow or IPFIX sensor.
You can monitor Juniper jFlow with the corresponding sensors as well. Basically they are adjusted
NetFlow v5 sensors.
3021
NetFlow Lite monitoring is possible using the Sampling Mode of the NetFlow v9 sensor or of the
NetFlow v9 (Custom) sensor. You can turn on the sampling mode and define a suitable Sampling
Rate in the sensor settings. Note that NetFlow Lite monitoring might not work in every case even with
active sampling mode.
sFlow Monitoring
sFlow works similar to NetFlow monitoring. The router sends data flow packets to the monitoring system
running on a probe. The most obvious difference between the two flow protocols: With sFlow, not all of
the traffic is analyzed, but only every n-th packet.
The advantage is clear: There is less data to analyze, there is less CPU load needed, and less
monitoring traffic is generated. Nevertheless, you can get a good insight into your network bandwidth
usage.
PRTG supports sFlow v5.
Set Up Flow Sensors

Find details on how to set up the different flow sensors in the following sections:
§ NetFlow v5
§ NetFlow v9
§ IPFIX
§ IPFIX (Custom)
§ sFlow
§ sFlow (Custom)
§ jFlow v5
§ jFlow v5 (Custom)
Limitations
For example, with a dual core, 2.5 Ghz hardware system, you can process about 100,000 flows per
second for one flow stream. Using sampling, the number of actual flows can be much higher. When
using complex filters, the value can be much lower. For example, with a router sending about 2,000
flows/second (which corresponds to mixed traffic at gigabit/second level without sampling) you can
expect to configure up to 50 flow sensors operating properly.
PRTG internally monitors its own flow processing. You can see decreased values in the Health channels
of the Core Health and Probe Health sensors as soon as flow packets are not processed because of an
overload (you find these sensors on the local probe device).
If you experience an overload, consider using sampling or setting up multiple probes and distributing the
flow streams to them. We recommend that you do not add more than 50 flow sensors per probe.
3022
IPv6 flows are supported by NetFlow v9 sensors and IPFIX sensors, other flow sensors only support
IPv4.
More
KNOWLEDGE BASE
Can I add custom channels to standard Packet Sniffer and NetFlow sensors?
What filter rules can be used for custom Packet Sniffing, Flow, or IPFIX sensors?
How do the channel definitions for custom Packet Sniffing, Flow, and IPFIX sensors work?
Does my Cisco device (router/switch) support NetFlow export?

Do you have any configuration tips for Cisco routers and PRTG?
How do I monitor Cisco ASA firewalls using NetFlow 9 and PRTG?


PAESSLER TOOLS
NetFlow Generator and NetFlow Tester

§ https://www.paessler.com/tools
3023
12.6 Bandwidth Monitoring Comparison
The following table shows the differences between the four bandwidth monitoring methods available in
PRTG:
Category WMI 3014 SNMP Packet Flow (IPFIX,

3007 Sniffer 3019 NetFlow,
sFlow,
jFlow) 3021
Setup Medium Low Low to high Can be high

(depending (for
on filter rules example,
used) the switch
must be
configured)
Traffic filtering No No Yes Yes
Differentiate bandwidth usage by protocol or No No Yes Yes

IP addresses
PRTG can show Toplists (Top Talkers, Top No No Yes Yes

Connections, Top Protocols, custom)
Filter bandwidth usage by IP address No No Yes Yes
Filter bandwidth usage by MAC address No No Yes No
Filter bandwidth usage by physical network Yes Yes No No

port
Monitor network parameters other than Yes Yes No No

bandwidth usage
CPU load on the PRTG core server system Medium Low Higher, Higher,
depends on depends on
the amount the amount
of traffic of traffic
Excess bandwidth usage of monitoring Small Small None (except Depends on

when the traffic
monitoring
switch ports
are used)
3024
More
KNOWLEDGE BASE
Should I use SNMP, Flow (IPFIX/NetFlow/sFlow) or Packet Sniffing for my monitoring?

How do I differentiate between excessive bandwidth usage with PRTG?
3025
12.7 Monitoring Quality of Service
PRTG can monitor the Quality of Service (QoS) in a network with dedicated QoS sensors, as well as
Cisco IP service level agreement (SLA) and Cisco Class Based Quality of Service (CBQoS). Slight
variations in network parameters like jitter, packet loss, or packet delay variation (PDV) usually have only
little effect on Transmission Control Protocol (TCP) based services (for example, HTTP and Simple Mail
Transfer Protocol (SMTP)). But for User Datagram Protocol (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 noticeably when UDP packets are not received in time, or if packets are lost or in the wrong order.
As a rule of thumb for good quality of service (from a VoIP perspective), it is important to have 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 QoS measurements, four sensors are available:
§ QoS (Quality of Service) One Way
§ QoS (Quality of Service) Round Trip
§ Cisco IP SLA
§ SNMP Cisco CBQoS
QoS (Quality of Service) Sensors

The QoS sensors monitor the quality of a network connection by measuring the following parameters:
§ Jitter in ms according to RFC 3550
§ PDV in ms according to RFC 3393
§ Lost packets in %
§ Out-of-order packets in %
§ Duplicated packets in %
The QoS sensors measure the quality of service by sending UDP packets between two probes. This
means that you can test any network connection in your network by placing a remote probe 3201 on (or
near) each end of the connection and measuring the connection quality between them. This way, you
can find network issues that can affect VoIP sound quality or cause video streaming issues.
You can also use the QoS (Quality of Service) Round Trip sensor without installing a remote probe
at the connection endpoint. For more information about the PRTG QoS Reflector, see the
Knowledge Base: How can I monitor QoS round trips without using remote probes?
3026
Monitoring Quality of Service w ith PRTG
The measurements for QoS monitoring are taken between two probes. So the first step is to place two
PCs running a remote probe on (or near) both ends of the connection that you want to monitor. As an
alternative, the local probe on the PRTG core server system can also be used as one end, or you can
use the PRTG QoS Reflector (see the Knowledge Base) to bounce the packets when monitoring QoS
roundtrips. If any firewalls, packet filters, or network address translation (NAT) systems are used, you
must configure them as necessary so that the UDP packets can reach the target probe.
Create a new QoS sensor on a probe device, or, if you use the QoS (Quality of Service) Round Trip
sensor, on any device. With the settings for the number and for the 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 might 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.
Find details about settings in the sections QoS (Quality of Service) One Way sensor and QoS
(Quality of Service) Round Trip sensor.
3027
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 have not done so already, add a device that represents the Cisco target device. Then create a new
Cisco IP SLA sensor on this device.
Find details about settings in section Cisco IP SLA sensor.
This feature is only available in the more expensive Cisco devices. If you do not have IP SLA-capable
routers and switches, you can still get similar information with QoS sensors (see above 3026 ) that do not
require any special hardware.
PRTG monitors the following parameters: Impairment Calculated Planning Impairment Factor (ICPIF),
Mean Opinion Score (MOS), Average Jitter, Packets Lost, Packets Out of Sequence, Packets Late,
Average Round Trip Time (RTT), Domain Name System (DNS) RTT, TCP RTT, Transaction RTT.
Two of these parameters are especially interesting for VoIP: MOS and ICPIF.
SNMP Cisco CBQoS Sensor

Cisco CBQoS provides information about QoS of Cisco network devices that support the Modular QoS
Command-Line Interface (MQC). With Class Based QoS, you can obtain monitoring data that includes
summary counts and rates by traffic class before and after the enforcement of QoS policies, according to
Cisco's CBQoS Management Information Base (MIB) definition.
PRTG determines CBQoS data via SNMP. The corresponding sensor is available as of PRTG 13.x.5.
CBQoS is available in Cisco IOS by default as of version 12.4(4)T.
To monitor CBQoS, add a device to PRTG for the Cisco target device. Then create a new SNMP Cisco
CBQoS sensor on this device.
See section SNMP Cisco CBQoS sensor for more details.
This sensor supports the following CBQoS classes:
§ Class Map: statistical data about class maps, such as pre-policy and post-policy packets and sizes,
drop packets and size, as well as no-buffer drop packets
§ Match Statement: statistical data about match statement specific information, such as pre-policy
packets and size
§ Queueing: statistical data about queuing actions, such as current and maximum queue depth, drop
packets, and drop size
You can select the desired CBQoS entries that you want to monitor while creating the sensor. The
available entries are specified with their particular connections, their descriptions, and class types.
3028
Voice over IP
For MOS measurements, Cisco conducted a panel test where a wide range of listeners judged the
quality of voice samples sent using particular codecs, on a scale of 1 (poor quality) to 5 (excellent
quality). The Cisco device calculates the corresponding value for the network connection based on
network parameter measurements like jitter and packet loss.
The Cisco IP SLA sensor reads out the MOS directly from the Cisco device. For the QoS (Quality of
Service) One Way sensor and the QoS (Quality of Service) Round Trip sensor, PRTG calculates the
MOS by itself. For more information, see the Knowledge Base: How does PRTG calculate the MOS
score for QoS sensors?
The values and their meanings are:
MOS Quality Expected Quality Impairment
5 Excellent Imperceptible
4 Good Perceptible, but not annoying
3 Fair Slightly annoying
2 Poor Annoying
1 Bad Very annoying
The second interesting parameter ICPIF is the sum of measured impairment factors minus a user-defined
access Advantage Factor that is intended to represent the user's expectations, based on how the call
was placed (for example, a mobile call versus a land-line call) (quoted from the Cisco website).
Upper Limit for ICPIF VoIP Call Communication Quality
5 Very good
10 Good
20 Adequate
30 Limiting case
45 Exceptional limiting case
55 Customers likely to react strongly (complaints, change of network

operator)
3029
More
KNOWLEDGE BASE
How can I monitor QoS round trips without using remote probes?
How does PRTG calculate the MOS score for QoS sensors?
PAESSLER WEBSITE

3030
12.8 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 to do two things for
backup monitoring:
1. Configure your backup software to send emails to a dedicated email account.

2. Configure the IMAP sensor for backup monitoring.
PRTG analyzes the backup emails for you and sets the status of the IMAP sensor accordingly. This way
you see the states of all your backup jobs.
Backup Monitoring via Email
Setting up Backup Monitoring

Refer to our Knowledge Base for a step-by-step tutorial on how to monitor your backup jobs: How
can I monitor my backup software to be sure backup succeeded last night?
More
KNOWLEDGE BASE
How can I monitor my backup software to be sure backup succeeded last night?
Can I analyze multipart emails using the IMAP sensor?

3031
12.9 Monitoring Virtual Environments
Monitoring your complete IT infrastructure in a comprehensive way usually means monitoring not only
your physical infrastructure, but also your virtual environments. With the layer of virtualization added to
the layers that represent your physical hardware, it also becomes necessary to plan beforehand how you
want to logically set up your monitoring infrastructure.
Monitoring All Layers of Your IT Infrastructure

In general, you can assume that with the layer of virtualization, you need to monitor a total of four layers
in your IT infrastructure.
Layer Description
Hardware (Server Racks) Usually, you monitor most of the hardware components in your network
with SNMP sensors 3284 . With this monitoring technology 3007 , you can
gather monitoring data such as CPU load, memory, and disk space. You
can also get information about the network traffic and bandwidth usage of
your routers and switches.
Alerts can tell you if there is an issue with a hardware component or if
hardware resources are running out. In addition, you can identify potential
bottlenecks that might affect your virtualized infrastructure.
Host Server Hardware We recommend that you explicitly monitor the host hardware of your
virtualization solution. If you have issues with your virtual machines (VM),
the origin might be a host hardware failure. You should closely monitor
your VM host servers to be alerted if the hardware status changes in any
significant way.
Besides the standard hardware sensors, PRTG provides specific sensors
for various virtualization host servers. The following monitoring data of your
host servers can prevent issues in virtualized environments:
§ VMware: current reading and health status (via Web-based Enterprise
Management (WBEM)), a general status as shown in vSphere (via
Simple Object Access Protocol (SOAP)), and disk space of a VMware
data store (via SOAP)
§ Hyper-V: host health-critical values; deposited pages; network traffic;
CPU usage of guests, hypervisor, and in total
§ Citrix XenServer: CPU, memory, and network usage; the number of
running VMs on the host server; and load average
Resource Usage of VMs VMs run on their particular host servers. PRTG can show you the status
of single VMs and several of their performance counters. You might want
to know which resources a single VM uses and needs, but we do not
recommend that you monitor single VMs in every case because it has a
noticeable influence on overall performance. Often, it is sufficient to only
monitor VMs that are critical for your network. If a VM reaches its
capacity limits, PRTG can alert you so that you can take the respective
steps to solve the issue.
3032
Layer Description
Indicators for a healthy VM that you can monitor with PRTG:

§ VMware: CPU and memory usage, disk read and write speed, read and
write latency, and network usage
§ Hyper-V: CPU usage, disk read and write speed
§ Citrix XenServer: CPU usage and free memory
Operating Systems of You can monitor, for example, the Windows operating system of a single
VMs VM with the standard WMI sensors 3315 . With this technology 3014 , you can
access data of various Windows parameters. Other operating systems
like Linux/macOS can make data available via SSH 3017 and SNMP.
The status of the operating systems on your VMs can indicate potential
issues. You can monitor these but be careful with regard to performance
considerations. This is because sensors using the WMI protocol have a
high impact on system performance, so you should only monitor
operating systems that are critical for your infrastructure. Furthermore,
you do not need to monitor every item multiple times. For example, it
might be sufficient to monitor free disk space only as a needed resource
of the actual VM, not for the VM's operating system itself.
Monitoring the Virtual Infrastructure

To monitor your IT infrastructure, best practice is to first set up the monitoring of your data center's
hardware layer in PRTG. This way, you can detect potential bottlenecks that might have an impact on
your virtual servers. Then, you can prepare to start monitoring your virtual environment. If you use several
solutions for virtual hosting, it is also a good idea to group related host servers, their VMs, and the
operating systems. The screenshot below shows a possible structure of monitoring a virtual environment
with PRTG.
3033
Grouped Virtual Components
At the top level, you can see the Virtual Hosting group. This group contains several subgroups for the
virtualization solutions Citrix XenServer, Microsoft Hyper-V, and VMware vSphere. The vSphere group, for
example, has three subgroups: we monitor the vCenter VMs and the vCenter Windows operating system
(vCenter group), the performance of the host server (Host Performance group), and the storage system of
the host (Host Storage group).
Devices for Physical Hosts

In PRTG, set up devices that represent the physical hosts of your VMs. For example, for your VMware
hosts, add devices that represent the ESXi servers. For Hyper-V, add devices that represent your Hyper-
V host servers. For Citrix, add devices that represent your XenServers.
Then you can add suitable sensors to the host server devices. If you run the auto-discovery 270 , many
sensors are automatically created. Several preconfigured host hardware sensors are available:
These sensors monitor hardware-specific counters to make sure that no hardware issues affect your
actual VMs. Additional sensors can monitor the host hardware via the Simple Network Management
Protocol (SNMP) (for example, traffic and custom requests), and the data storage on ESXi servers via
SOAP. There are also sensors for network adapters and storage devices that are connected to a Hyper-
V host server.
3034
Devices for Virtual Machines
To monitor your actual VMs, add them to your host servers in PRTG. For a better overview, you might
want to add a device to PRTG that represents your host server and add sensors for your VM there. The
respective sensors for VMs show you the performance of single VMs as well as their resource usage.
This identifies VMs with low performance so that you can react before there is an issue with one or more
of your VMs. As mentioned before, you can additionally monitor the operating systems of your VMs, if
necessary. See the following sections for details about particular virtualization solutions.
VMware Virtual Machine
The VMware Virtual Machine (SOAP) sensor monitors VMs on a VMware host server via SOAP. The
general idea is to add a vCenter server as a device to your vCenter group and use it as a parent device to
which you add the sensors for your VMs. This way, in the case of vMotion, when your VMs change their
host server, PRTG can follow these movements and does not lose the monitored VMs.
For this sensor, .NET 4.7.2 or later must be installed on the probe system. If you use many VMware
sensors, we also recommend that you adjust the settings on your VMware host server to accept more
incoming connections.
vSphere Group
This screenshot shows an example of a vSphere group. As recommended, the sensors for the VMware
virtual machines are added to the vCenter 1 device. There is also a dedicated vCenter 2 device for the
vCenter Windows operating system with common WMI sensors for CPU, memory, disk, and network
usage. The ESXi host servers are organized in their own groups regarding performance and storage. In
this example, PRTG monitors the hosts with the standard SNMP hardware sensors as well as with the
specific VMware ESXi host sensors.
Microsoft Hyper-V Virtual Machine
3035
The Hyper-V Virtual Machine sensor monitors VMs via Windows Management Instrumentation (WMI) or
Windows performance counters, as configured in the Windows Compatibility Options 663 of the parent
device. With this hybrid approach, the sensor first tries to query data via performance counters and uses
WMI as a fallback if no performance counters are available. Performance counters generally need less
system resources than WMI. The parent device of this sensor must be a Windows server running Hyper-
V. You should also disable the User Account Control (UAC) in the Windows operating system of the VM.
Otherwise, the sensor might change to the Down status with the error message The virtual machine is
not running or is powered off. Also, this sensor does not support Live Migration.
Hyper-V Group
This screenshot shows an example of a Hyper-V group. There is a dedicated group for failover clusters
where two cluster nodes are monitored with several SNMP and WMI sensors, as well as Hyper-V Host
Server sensors and sensors for the Hyper-V virtual machines. This makes sure that Hyper-V and failover
clusters work without any issues. The Hyper-V hosts are monitored the same way, organized in a
dedicated group for hosts.
Citrix XenServer Virtual Machine
The Citrix XenServer Virtual Machine sensor monitors VMs via HTTP. For this sensor, you must add a
device that represents a Citrix XenServer running at least version 5.0. Another requirement is the
Microsoft .NET Framework. You must install .NET 4.7.2 or later on the probe system.
In a XenServer pool, each host knows each running VM. Because of this, there is no central instance
that provides all available data, so it does not matter on which host you query your VMs. All queries on
any host are automatically forwarded to the pool master that manages the XenServer pool. Therefore, it is
sufficient to create the desired sensors for your XenServer VMs on a device that represents one host
server of your pool. The XenServer sensors find out which host is running and retrieve the respective data.
3036
XenServer Group
This screenshot shows an example of a XenServer group. There are two devices for XenServer hosts, Xen
1 and Xen 2, that each have a Citrix XenServer Host sensor and several Citrix XenServer Virtual Machine
for the particular VMs on this host. Furthermore, the Windows operating system is represented as a
dedicated virtualcontrol device that PRTG monitors with several WMI sensors regarding CPU, disk,
memory, and network usage.
Performance Considerations
For best performance when monitoring virtual environments, we strongly recommend that you use a
computer with at least Windows Server 2016 installed on the probe system. For example, you can run
up to 300 VMware sensors with a 60-second scanning interval as of Windows Server 2016, while you can
only use 30 VMware sensors with the same scanning interval on Windows Server 2008 R2.
3037
12.10 Monitoring Databases
Monitoring your databases lets you make sure that database queries are processed in time, and that the
database itself performs within the defined parameters. Furthermore, database monitoring with PRTG can
alert you via a corresponding sensor status if database queries return unexpected result values.
PRTG comes with built-in native sensors for the most common databases:
§ Microsoft SQL servers
§ MySQL servers
§ PostgreSQL servers
§ Oracle SQL servers
It is also possible to monitor many other database servers. For this case, PRTG uses the ActiveX Data
Objects (ADO) interface.
There are two types of database sensors:
§ Sensors that monitor databases directly 3038 : Monitor databases from the user perspective. These
sensors send a request to the database server and receive corresponding values. You can optionally
process data tables and show values in individual channels or monitor transactions.
§ Sensors that monitor database performance 3041 : Monitor databases with a more abstract view on the
servers. Usually, these sensors monitor performance counters via Windows Management
Sensors Monitoring Databases Directly

PRTG provides several sensors that can monitor the content of databases. Sensors of this type connect
to the database server, execute a defined query, and show the execution time of the whole request and
the query. You can use these sensors to process the data table and show requested values in individual
channels.
The following sensors are available for this kind of monitoring:
§ Microsoft SQL v2
§ MySQL v2
§ Oracle SQL v2
§ PostgreSQL
For these sensors, you can define valid Structured Query Language (SQL) statements that the sensors
send to the database server. Define the queries in an SQL script file and store it in the respective
\Custom Sensors\sql subfolder of the PRTG program directory 3218 .
You can select this SQL script when you add the sensor. With every scanning interval 466 , the sensor
executes this script with the defined query against the database and the database returns corresponding
values in individual channels (see the example 3039 below for sample channel value selections). Use the
channel settings 2693 to define limits for specific values.
These sensors need .NET 4.7.2 or later installed on the probe system.
3038
Alternatively, you can monitor almost all available database servers with the ADO SQL v2 sensor via an
ADO connection.
Example: SQL Channel Value Selection

The SQL (v2) sensors determine their channel values by using column numbers, column names, row
numbers, or key value pairs. This section shows which option you can choose to get the desired value
from an SQL data table.
Consider the following data table that an SQL query might return from a database:
article_id articles_av first_listing orders

ailable
00 12 2001 4
01 345 2005 56
02 678 2008 290
03 90 2012 32
This data table has four columns with the following numbering:
§ Column 0 has the name "article_id"
§ Column 1 has the name "articles_available"
§ Column 2 has the name "first_listing"
§ Column 3 has the name "orders"
The numbering of columns starts with 0, as well as the numbering for rows starts with 0. The table has
four rows, each row contains the properties of one "article". The "articles" have the IDs 00, 01, 02, 03.
This also illustrates the proper row numbering (0, 1, 2, 3).
With the options for channel value selection in SQL sensors, you can read out the following values:
§ All values that are in row 0 (here: 00, 12, 2001, 4)
§ All values that are in column 0 (here: 00, 01, 02, 03)
§ All values that are in column 1 (here: 12, 345, 678, 90)
It is not possible to get values from any other cell in a data table. If you need this, you must reconstruct
your data table.
The following samples show possible results for channel value selections regarding this data table:
3039
Sample Channel Description
Value Selection
Channel Value Selection This channel shows the value in row 0 of the column you specify.
by Column Number Consider you define "1" as column number. Then the channel value is
"12" because it is the cell in column 1 and row 0.
Possible return values for this option:
§ Column number "0" returns "00"
Channel Value Selection This channel shows the value in row 0 of the column you specify.
by Column Name Consider you define "orders" as column name. Then the channel value is
"4" because it is the cell in column "orders" and row 0.
§ Column name "article_id" returns "00"
§ Column name "articles_available" returns "12"
§ Column name "first_listing" returns "2001"
§ Column name "orders" returns "4"
Channel Value Selection This channel shows the value in column 0 of the row you specify.
by Row Number Consider you define "1" as row number. Then the channel value is "01"
because it is the cell in row 1 and column 0.
§ Row number "0" returns "00"
Channel Value Selection This channel shows the value in column 1 of the same row where the key
by Key Value Pair in column 0 was found. Consider you define "02" as key. Then the
channel value is "678" because it is the cell in the same row in column 1
as the key in column 0.
§ Key "00" returns "12"
3040
This sample channel value selection illustrates how to choose the correct option to get needed values
from an SQL data table and shows which cells the SQL sensors can address.
UDF: Counting Returned Rows
If you execute a User-defined Function (UDF) on the SQL server and want to know how many rows this
UDF returns, follow these steps:
§ A command to execute your UDF on the SQL server might look like this, for example:
exec myUDF
§ To get the information how many rows this UDF returns, extend the query in your SQL script:
exec myUDF;
select @@rowcount as row_count
§ Create a new SQL v2 sensor and select Data Processing during sensor creation.
§ In the settings of your SQL sensor, select Column name under Select Channel Value by.
§ Enter row_count into the Channel #x Column Name field of the channel to show the value from this
column in the channel.
§ To count table rows returned by a SELECT statement, choose the option Count table rows in the
sensor settings section Data Processing.
Sensors Monitoring Database Performance

Performance sensors for database servers have a more abstract view on databases and observe
performance externally. They do not read out any values of the database, neither do they send SQL
queries to databases. This sensor is only available for Microsoft SQL.
The Microsoft SQL server sensors monitor performance via 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, 2012, 2014,
2016, 2017, and 2019:
§ WMI Microsoft SQL Server 2008
3041
12.11 Monitoring via HTTP
HTTP is a standard application layer protocol and the basis for data communication on the internet. It is
a request-response method for client-server architectures, where the client sends a request and the
server processes and responds to the request.
Monitoring via HTTP is useful if you want to monitor websites or web servers. It enables you to keep an
eye on the availability and download times of a website or the performance statistics of a web server.
There are also a lot of other possible use cases for HTTP sensors. For example, you can request any
application programming interface (API) that is reachable via HTTP and monitor returned values. This
approach lets you include almost any type of device or application into your monitoring.
PRTG comes with sensors for HTTP monitoring:
§ AWS Alarm v2
§ AWS EBS v2
§ AWS EC2 v2
§ AWS ELB v2
§ AWS RDS v2
§ Cloud HTTP v2
§ Common SaaS
§ HTTP
§ HTTP Advanced
§ HTTP Apache ModStatus PerfStats
§ HTTP Apache ModStatus Totals
§ HTTP Content
§ HTTP Data Advanced
§ HTTP Full Web Page
3042
§ HTTP IoT Push Data Advanced
§ HTTP Push Count
§ HTTP Push Data
§ HTTP Push Data Advanced
§ HTTP Transaction
§ HTTP v2
§ HTTP XML/REST Value
§ NetApp I/O v2
§ NetApp LIF v2
§ NetApp LUN v2
§ NetApp NIC v2
§ NetApp Volume v2
§ REST Custom
§ REST Custom v2
§ SSL Certificate
Use Cases
§ Monitor the availability and loading times of a website
§ Monitor the source code and specific content of a website
§ Test the login, purchasing, and shipping processes of a web shop
§ Monitor performance statistics and activity of Apache web servers
3043
Types of HTTP Monitoring
Availability Monitoring
This type monitors the availability of a website or a specific website element. For example, the HTTP
sensor shows how long the HTML code of a website takes to load. If the sensor shows a loading time
that is much longer than expected, the website might not be responding or might be unavailable.
Cloud Monitoring w ith HTTP Provides Better Performance Statistics
The HTTP sensor uses different HTTP requests to request the specified URL:
§ GET (default): requests the website directly
§ POST: sends post form data to the URL
§ HEAD: requests the HTTP header only, without the actual web page body, saving bandwidth
The HTTP Advanced sensor also monitors the availability of a website, along with other parameters such
as bytes received, download bandwidth (speed), and time to first byte, which shows you how fast your
web server responds. This sensor lets you use a (custom) user agent when connecting to the target URL
and lets you send custom HTTP headers to the target URL.
The Cloud HTTP v2 sensor monitors a web server from various locations across the globe. For example,
the URL of a website to measure the loading time of a page’s source code or the URL of a page asset to
measure its availability and loading time. The sensor also shows the global average response time.
3044
The Common SaaS monitors the availability of your cloud services and is an important pillar for unified
monitoring.
Content Monitoring
This type monitors internal values of a web server based application or changes to specific content on a
website. The HTTP Full Web Page sensor measures the time it takes to download a web page including
all embedded page elements, for example Flash content or images.
This monitoring option can create a lot of bandwidth traffic, depending on the page size and the
scanning interval.
Additionally, the HTTP Content sensor monitors a numeric value returned by an HTTP request. It can
also optionally trigger a ‘change’ notification to notify you of changes to the content.
Example: Content Monitoring

For example, consider a URL http://www.example.com/status.html that returns a PHP script with
the current system status in a simple HTML page.
<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 script URL from above,
§ value type Float,
§ and number of channels 2.
The sensor calls the URL with every scanning interval and only regards the two values in brackets [ ],
handling each of them in one channel. The additional description text and HTML tags are not necessary.
In this example, they are added in case a human calls the URL.
If you define the number of channels as 1, the sensor only reads the first value. The second value is
ignored. Using 3 as number of channels results in a sensor error message.
To be notified when the website content changes, you first need to configure a Trigger 'change'
notification in the sensor's settings and then the notification itself.
Performance Monitoring
3045
The HTTP Transaction sensor checks if a web shop is working as expected: with a series of requests, for
example, you can simulate the login, purchasing, and shipping processes. Only if all actions can be
completed successfully in a row, the check returns an "OK" message. If anything goes wrong, you are
immediately alerted and can react instantly to avoid loss of earnings for your company because the web
shop is unavailable or very slow.
Apache Web Server Monitoring
The HTTP Apache ModStatus PerfStats and HTTP Apache ModStatus Totals sensors monitor
performance statistics and the activity of an Apache web server using mod_status over HTTP. Among
other HTTP sensors, these sensors let you enter credentials for web pages that need authentication and
let you choose the necessary authentication method.
Security Monitoring
PRTG also provides the option to monitor the security of your website by checking the status of Secure
Sockets Layer (SSL) certificates and the security of a connection:
§ SSL Certificate sensor: monitors the certificate of an SSL/TLS-secured connection. For example, it
displays whether a certificate has been revoked, or is trusted as root authority, or is self-signed.
§ SSL Security Check sensor: monitors the SSL connectivity to the port of a device. It tries to connect
to the specified TCP/IP port number of a device with different SSL/TLS versions and shows if a specific
protocol is supported.
Push Monitoring
PRTG provides the option to monitor passively received data. For this purpose, you can set up a device
in a way that it automatically sends the data to PRTG. Specific sensors can receive this data and alert
you based on your individual settings. For example, all Linux/Unix and most network devices support
remote devices generating data, which has to be configured on each device, and sending the messages
to a probe system. Usually, only the destination IP and port are required.
For more information, see the Paessler website: How to use push monitoring via HTTP.
Other Data
You can also monitor other types of data from your website, for example the number of website visitors
via the HTTP XML/REST Value sensor. The sensor lets you monitor values within the returned Extensible
Markup Language (XML) code, provided your web analytics tool has an XML export option. The HTTP
Data Advanced sensor accesses a web server and retrieves XML or JavaScript Object Notation (JSON)
encoded data.
The REST Custom sensor queries a Representational State Transfer (REST) application programming
interface (API) endpoint and maps the JSON or XML result to sensor values. The mapping rule has to be
available as a REST configuration file in JSON template (*.template) format according to the PRTG API
definition.
For more information about the return value format, see section Custom Sensors 3145 .
3046
HTTP Status Codes
The HTTP sensors show their status depending on the HTTP status codes that they receive. By default,
the sensor states are the following:
HTTP Status Code HTTP Sensor Status
2xx Success Up
3xx Redirection Warning, Down for too many redirects)
4xx Client Error Down
5xx Server Error Down
You need to configure your HTTP sensors manually only if you want to change these default
reactions. In this case, you can change the sensor status based on limits and/or keyword checks.
Other HTTP Sensor Settings

§ Server Name Indication: You can configure SNI, which has to be a fully qualified domain name (FQDN)
and must match the configuration of the target server. For more information, see the Knowledge Base:
§ HTTP Version: You can choose the HTTP version that the sensor uses when connecting to the target
URL.
§ Authentication Method: You can define if the configured URL needs authentication, enter credentials,
and choose an authentication method.
§ Custom User Agent: You can enter a string to be used as user agent when connecting to the target
URL.
§ Custom HTTP Headers: You can send custom HTTP headers to the target URL.
HTTP Sensor Troubleshooting

For troubleshooting and other tips for monitoring with HTTP sensors, see More 3047 below.
More
KNOWLEDGE BASE
HTTP Full Web Page sensor is unable to navigate. What can I do?
3047
What to do when I see a CreateUniqueTempDir() error message for my HTTP Full Web Page sensor?
Where can I find more information about the HTTP XML/REST Value sensor?
Why does my HTTP XML/REST Value sensor return a 404 error?
3048
Part 13
PRTG Administration Tool
1/10/2023 3049
13 PRTG Administration Tool
The PRTG Administration Tool is part of every PRTG installation. You can use it to edit the administrative
settings of local probe and remote probe installations.
You can start the PRTG Administration Tool from the Windows Start menu on the PRTG core server
system or on the remote probe system. If you start the PRTG Administration Tool on the PRTG core
server system, you can change settings that affect the entire installation and the local probe. If you run
the PRTG Administration Tool on a remote probe system, you can only change settings that are related
to the remote probe.
Any settings that you change require a restart of the affected PRTG core server service and PRTG probe
service to apply any changes to the configuration.
You can also change many administrative settings via the Setup 2809 in the PRTG web interface. For
probes, administrative settings are also available on the Settings tab 536 in the PRTG web interface.
You can review the history of all changes to the settings of the PRTG Administration Tool in the
\Logs\serveradmin subfolder of the PRTG program directory 3218 . The name of the corresponding log
file is ServerAdmin.log.
In this section:
3050
13.1 PRTG Administration Tool on PRTG Core Server Systems
With the PRTG Administration Tool, you can define various system settings regarding the PRTG core
server installation, restart services, and view log information. You can also change many of these
settings via the system administration 2865 in the PRTG web interface.
In this section:
§ Start the PRTG Administration Tool 3051
§ PRTG Web Server 3051
§ PRTG Core Server 3056
§ Cluster 3057
§ Administrator 3064
§ Probe Settings for Core Connection 3065
§ Probe Settings for Monitoring 3068
§ Service Start/Stop 3069
§ Logs and Info 3072
§ Send Logs to Paessler 3073
§ Activate Changed Settings 3075
This section describes the settings that are available in the PRTG Administration Tool when you
open it on the PRTG core server system. This means that you can edit settings for the PRTG core
server or PRTG web server and the local probe.
Settings that you define are only valid for the PRTG core server system on which you start the
PRTG Administration Tool. Make sure that you log in to the system that you want to make changes
to and open the PRTG Administration Tool there.
Start the PRTG Administration Tool

§ From the Windows Start menu, select the PRTG Network Monitor folder and click PRTG
Administration Tool to open the application.
§ Confirm the question of the Windows User Account Control with Yes to allow the PRTG Administration
Tool to start.
PRTG Web Server

Edit IP addresses, ports, access methods, and language for the PRTG web interface.
You can also change these settings under Setup | System Administration | User Interface in the
PRTG web interface. For more information, see section User Interface 2870 .
3051
PRTG Web Server Tab
Setting Description
TCP Port for PRTG Web Specify how the PRTG web server accepts incoming web page requests:
Server
3052
Setting Description
§ Secure HTTPS server (default port 443, recommended, mandatory for

internet access): Use a Secure Sockets Layer (SSL)/Transport Layer
Security (TLS) secured HTTPS connection on port 443.
This setting is required if you want to access the PRTG web
interface via the internet.

warning in your browser when you log in to the PRTG web interface
because the default certificate is unknown to your browser. For more
information, see the Knowledge Base: Why does my browser show an
SSL certificate warning when I open the PRTG web interface?. You can
install a different SSL certificate for PRTG. For more information, see
section How to use your own SSL certificate with the PRTG web server.
If port 80 is available, PRTG reserves it as well. If port 80 is not

available, PRTG tries port 8080 as fallback. If this port is also not
sends a ticket 216 that shows you the currently used port number and
switches back to port 80 as soon as it is available again. When users
try to connect on port 80 via HTTP, they are redirected to port 443 via
HTTPS. You can change this behavior via a registry setting. If port 443
is not available, PRTG tries port 8443 as fallback. If this port is also not
sends a ticket that shows you the currently used port number and
switches back to port 443 as soon as it is available again.
§ Unsecure HTTP server (default port 80, not recommended): Use the
PRTG web server without SSL/TLS on port 80.
This setting is not recommended for WAN connections.
If you use the PRTG web server via the internet without connection
security, attackers could potentially spy on credentials that you
enter in PRTG. We strongly recommend that you use this option only
in a LAN.
§ Custom configuration: Specify a custom port for the PRTG web server
and the security of the connection. This option is intended for systems
that already have a web server on the standard port.
If PRTG always uses a fallback port after a server restart, check for
other programs that use the same port as PRTG. For example, the
Microsoft Microsoft Internet Information Services (IIS) web server also
uses port 80 (port 443 for secure connections) by default and blocks it.
We recommend that you disable such programs and services on
startup.
Custom configuration: This setting is only visible if you select Custom configuration above.
Connection security
Specify if you want to use connection security:
3053
Setting Description
§ Use HTTPS (secured with SSL/TLS): Use an SSL/TLS secured HTTPS

connection on the port that you define as PRTG Web Server Port.
warning in your browser when you log in to the PRTG web
interface, because the default certificate is unknown to your browser.
You can install a different SSL certificate for PRTG later. For more
information, see the Paessler website: How to use your own SSL
certificate with the PRTG web server.
§ Do not use connection security (not recommended): Use the PRTG
web server without SSL/TLS on the port that you define as PRTG Web
Server Port.
We recommend that you do not use this setting for WAN
connections.
If you use the PRTG web server without connection security on the
internet, attackers could potentially spy on credentials that you
enter in PRTG. We strongly recommend that you use this setting in a
LAN only.
Custom configuration: This setting is only visible if you select Custom configuration above.
Web server port
PRTG web server to run on.
PRTG web server to run on. Enter an integer.
If you use a secure connection and port 80 is free, PRTG also
reserves it. When users try to connect on port 80 via HTTP, they are
redirected to the custom port via HTTPS. You can change this behavior
via a registry setting.
If the port that you define for secure connections is not available,
PRTG tries port 8443 as fallback. If this port is also not available,
PRTG searches from port 8444 upwards for a free port. PRTG sends a
ticket 216 that shows you the currently used port and switches back to
the original port as soon as it is available again.
IP Address for PRTG The PRTG web server provides access via the PRTG web interface and
Web Server the PRTG app for desktop 2994 . Once you specify an IP address, you use
it to log in to the PRTG web interface in your browser. Specify on which
IP address the PRTG web server runs:
3054
Setting Description
§ Localhost, 127.0.0.1 (PRTG is not accessible from other computers):

Use 127.0.0.1 only. The PRTG web interface and the PRTG app for
desktop are only accessible from the PRTG core server system.
to 8089 must be available on 127.0.0.1.
If you run PRTG on localhost, do not use the DNS name

http://localhost to log in to the PRTG web server. This might
considerably slow down the PRTG web interface. Use your local IP
address or http://127.0.0.1 instead.
§ All IP addresses available on this computer (recommended): Use all IP
addresses that are available on the PRTG core server system and
enable access to the PRTG web server for all of these IP addresses.
The selected Transmission Control Protocol (TCP) port for the
PRTG web server must be available on all selected IP addresses.
§ Specify IP addresses: Select specific IP addresses on which the PRTG
web server runs. The list is specific to your setup. Enable check boxes
in front of every IP address that you want the PRTG web server to be
available at. You can also select all IP addresses by clicking the Select
all IP addresses button or deselect all addresses by clicking the
Deselect all IP addresses button.
to 8089 must be available on the specified IP address.
Regardless of the setting that you select, one port in the range from
8080 to 8180 must be available on the specified IP address so that
PRTG can create reports. The report engine tries to connect to the PRTG
core server on one of these ports.
If PRTG does not find a network card on startup, it switches this
setting to Localhost, 127.0.0.1 (PRTG is not accessible from other
computers). This setting remains even if a network card is available later
on. If you disable or remove the network card on the PRTG core server
system, check this setting.
Select System Language Select the language. The default language is English.
This setting defines the language of the PRTG web interface and the
PRTG Administration Tool 3050 .
§ Deutsch (German)
§ English
3055
Setting Description
§ (Russian)
§ (Japanese)
PRTG Core Server

Define settings for the PRTG core server.
PRTG Core Server Tab
3056
Setting Description
Probe Connection Define how PRTG handles incoming connections from probes:
Management
§ Accept connections from the local probe only (default, does not allow
remote probes): Only accept connections from the local probe. If you
select this option, you cannot use remote probes 3203 .
§ Accept connections from remote probes on all IP addresses: Accept

incoming connections from remote probes, no matter on which IP
address of the PRTG core server they come in.
§ Accept connections from remote probes on selected IP addresses
only: Accept incoming connections from remote probes on the selected
IP address(es) of the PRTG core server. In the list, select the IP
addresses by enabling a check box in front of the desired IP
addresses.
You can also change this setting under Setup | System
Administration | Core & Probes 2900 in the PRTG web interface.
Local Storage of Data Select the directory where PRTG stores configuration and monitoring
Files and Monitoring data. Click to choose a different folder on the system.
Database
Before you change the path, make sure you stop both the PRTG
core server service and the PRTG probe service and copy all data to
the new location.
The directory name must include only ANSI characters. PRTG does
not support data paths with non-ANSI characters.
Click Revert to default folder to reset this setting to the default.
Cluster
On the Cluster tab, you can change how the PRTG core server behaves in a cluster. Before you change
settings here, see section Failover Cluster Configuration 3213 .
3057
Cluster Tab
Setting Description
Cluster Settings Depending on the cluster settings, different options are available.
§ Cluster Mode: Shows the cluster mode of the PRTG core server.
Possible values are Standalone (no cluster mode), Cluster Mode:
Master Node, or Cluster Mode: Failover Node.
§ Cluster Port: This setting is only visible if PRTG runs in cluster mode.
§ Cluster Access Key: This setting is only visible if PRTG runs in cluster
mode.
§ Cluster NodeID: This setting is only visible if PRTG runs in cluster
mode.
3058
Setting Description
Cluster Mode Actions Depending on the cluster settings, you see different active buttons.
§ Create a Cluster
§ Join a Cluster
§ Change Cluster Settings
§ Revert to Standalone
For details, see section Cluster Mode Actions 3059 below.
Master Heartbeat This section is only visible if PRTG runs in cluster mode. The current
master node can execute an external executable file on a regular basis.
We call this a heartbeat.
You can use this, for example, to report the IP address of the current
master node to a dynamic Domain Name System (DNS) provider, so that
a DNS name is always redirected to the current master node in case the
primary master node fails and a failover node (with a different IP address)
becomes the current master node.
§ No heartbeat: Do not execute a file on a regular basis.
§ Run an external executable file every 5 minutes: Click to browse for

the file that you want to execute. This can be, for example, a
command-line tool or a batch file. PRTG executes it on the current
master node only, in a fixed interval of five minutes. You cannot change
the interval.
Make sure that the selected file is available under the same (local)
path on all failover nodes. In case one of your failover nodes becomes
the current master node, PRTG can only execute the heartbeat reliably if
the executable file exists on all of your failover nodes.
Cluster Mode Actions
Follow these instructions to create or to join a cluster, to change a cluster's settings, or to revert a
cluster node to standalone mode:
Create a Cluster
§ Click Create a Cluster to create a cluster. The current PRTG core server is then the master node of the
cluster.
§ Click Yes to convert this installation to a master node.
3059
Converting an Installation to a Master Node
§ A dialog box appears.
Creating a Master Node
§ Enter a Cluster Port. This is the port on which PRTG sends the internal communication between the
cluster nodes. Make sure that connections between the cluster nodes are possible on the port that
you select.
§ Enter or paste a Cluster Access Key. This is a unique access key. All cluster nodes must use the
same cluster access key to join the cluster. Connection attempts with a different access key are not
possible.
§ Save the Cluster Access Key so that you have it at hand when you configure the failover nodes.
§ After confirming your settings, you are asked to restart Windows services. Click OK to restart the
Windows services so that your changes take effect.
Restart Services to Apply Changes
3060
Join a Cluster
§ Click Join a Cluster to add this installation to a cluster that already has a master node. The current
PRTG core server is then a failover node.
§ This button is also available if the PRTG core server is in Cluster Mode: Master Node. This option then
changes the master node to a failover node.
§ Click Yes to convert this installation into a failover node.
Converting an Installation to a Failover Node
Cluster Connection Setup
§ Enter a Master Node (IP address/DNS name) for the cluster. It must be reachable from the machine
that runs the failover node.
§ Enter the other settings as defined in the settings of the master node. Make sure that you use the
same settings on all cluster nodes.
you select.
possible.
3061
Change Cluster Settings
§ If you run PRTG in cluster mode, you can change the settings. Click Change Cluster Settings to do
so.
Edit Cluster Node Settings
you select.
possible.
§ Make sure that you use the same settings on all cluster nodes.
3062
Revert to Standalone
§ Click Revert to Standalone to revert this cluster node to a standalone installation.
Revert Cluster to Standalone Installation
§ Click Yes to convert this cluster node to a standalone installation.
§ A dialog box appears where PRTG asks you to agree to restart the PRTG core server service. Click
OK to proceed.
Restart Services
When you revert a cluster node to Standalone mode, the cluster probe remains in the device tree to
keep your device and sensor setup. If you want to completely remove the cluster probe from the
device tree, you need to delete it manually.
3063
Administrator
On the Administrator tab, you can change settings for the PRTG System Administrator user.
You can also change the password for the PRTG System Administrator user account under Setup |
Account Settings | My Account 2812 in the PRTG web interface.
Administrator Tab
Setting Description
Email Address Enter a valid email address for the PRTG System Administrator user
account. By default, PRTG sends notifications and important messages
3064
Setting Description
to this address.
Login Name Enter a login name for the PRTG System Administrator user account.
You use it when you log in to the PRTG web interface or the PRTG app
for desktop.
The default login name is prtgadmin.
Password Click Generate new password and confirm to generate a new password
for the PRTG System Administrator user account. Click Save & Close to
set the new password. You use it when you log in to the PRTG web
interface or the PRTG app for desktop.
The default password is prtgadmin.
Probe Settings for Core Connection

Define general settings regarding the local probe and connections.
3065
Probe Settings for Core Connection Tab
Probe Settings
Setting Description
Probe Name Enter a meaningful name to identify the local probe. By default, PRTG
shows this name in the device tree 168 , as well as in alarms 205 , logs 213 ,
notifications 2745 , reports 2764 , maps 2786 , libraries 2748 , and tickets 216 . Enter
a string.
Reconnect Time Define the time that PRTG waits for the local probe to reconnect to the
PRTG core server if the connection fails. Enter an integer.
3066
Connection to PRTG Core Server
These settings affect the way that the local probe connects to the PRTG core server.
Setting Description
Server (IPv4 Address or The local probe connects to the PRTG core server via 127.0.0.1. You
DNS Name) cannot change this.
GID The probe GID is a unique identifier for the local probe. You cannot
change the GID on the PRTG core server system.
Edit GID and Generate new GID are only available on the remote
probe system. For more information, see section PRTG
Administration Tool on Remote Probe Systems 3077 .
You can deny GIDs under Setup | System Administration | Core &
Probes 2900 in the PRTG web interface.
Access Key Access Key is only available on the remote probe system.
For more information, see section PRTG Administration Tool on
Remote Probe Systems 3077 .
Confirm Access Key Confirm Access Key is only available on the remote probe system.
For more information, see section PRTG Administration Tool on
Remote Probe Systems 3077 .
Path for the PRTG Data Directory on the Probe System
Setting Description
Path This setting is not available on the PRTG core server system. Please use
Local Storage of Data Files and Monitoring Database on the PRTG Core
Server 3056 tab instead.
3067
Probe Settings for Monitoring
Probe Settings for Monitoring Tab

3068
Setting Description
IPv4: Outgoing IP for Define the IP address for outgoing requests that use the IPv4 protocol.
Monitoring Requests The list shows all available IP addresses on the system. Choose a
Service Start/Stop
You can manually start and stop the PRTG core server service and PRTG probe service. Click the
respective buttons to start or stop the respective service. Both actions usually take from a few seconds
up to several minutes. You can also restart the PRTG core server service and PRTG probe service under
Setup | System Administration | Administrative Tools 2929 in the PRTG web interface.
We recommend that you schedule automatic system restarts.
3069
Service Start/Stop Tab
Restart Options
Setting Description

§ No scheduled restart of the system or PRTG services: Do not
automatically perform a scheduled restart of services. We recommend
that you manually restart the PRTG core server system every few
weeks. You can also restart the PRTG core server service and PRTG
probe service under Administrative Tools 2928 in the PRTG web interface.
§ Scheduled restart of PRTG services: Restart the PRTG core server
service on the PRTG core server system. If you select this option, the
PRTG probe service restarts as well. Define a schedule under Restart
Schedule.
3070
Setting Description

Monitor instance.

Restart Schedule. We recommend that you restart every PRTG core
server system once a month for best performance.
Restart Schedule This setting is only visible if you select Scheduled restart of PRTG
services or Scheduled system restart (recommended) above.
Choose how often you want to restart the PRTG core server service,
PRTG probe service, or the PRTG core server system:
below.
Day This setting is only visible if you select Scheduled restart of PRTG
Select a day of the week (Monday to Sunday) or month (1st to 30th or

If you select a date that does not exist in every month (for example,
the 30th day in February), PRTG automatically restarts the PRTG
core server system on the last day of this month.
Time This setting is only visible if you select Scheduled restart of PRTG
Select the time of the day when PRTG restarts the PRTG core server
system.
here.
You can also define a restart schedule on the Settings tab 538 of a remote probe in the PRTG web
interface.
3071
Logs and Info
Logs and Info Tab
Logs
Button Description
Open Log Folder Open the PRTG data directory 3219 to access all logs that PRTG creates.
Send Logs to Paessler Open an assistant to send logs to the Paessler support team. See Send
Logs to Paessler 3073 for details.
3072
Button Description
This feature is only available with the commercial edition 21 of

PRTG.
You can also send logs with the support bundle via Contact
Support 2990 in the PRTG web interface.
Open Support Ticket Open the Help Desk portal on the Paessler website in a browser window.
If you need help, we recommend that you use the Contact Support
option in the PRTG web interface instead.
About
The About section shows information about the version of installed PRTG programs and copyright
information.
Send Logs to Paessler

You can also send logs with the support bundle via Contact Support in the PRTG web interface.
3073
If you open a support ticket, the Paessler support team might ask you to send logs for further analysis.
Field Description
Name Enter your name.
Email Enter a valid email address. You can provide any email address but we
recommend that you use the email address of your user account, which
PRTG enters by default.
Ticket # This field is optional. If you have already opened a ticket with the Paessler
support team, provide the ticket number you received. Your files are then
automatically associated with your ticket.
3074
Field Description
Enter the ticket number starting with PAE followed by four or more digits,
for example, PAE12345. If you do not have a ticket number, leave this
field empty.
Configuration Define if you want to include the configuration file. PRTG removes all
passwords from the configuration file before sending it to the Paessler
support team.
If a configuration file is too large, some 32-bit systems might not be
able to send the file with hidden passwords. In these cases, PRTG
confirms that you still want to send the configuration file to the Paessler
support team. The passwords are still encrypted.
Click Send to start the data upload. PRTG then automatically collects, compresses, and sends your
logs to our FTP over SSL (FTPS) server. Make sure that FTPS and HTTP connections are allowed on the
Activate Changed Settings

After you change settings, click Save & Close. A new dialog box appears where PRTG asks you to
agree to restart the PRTG core server service. Click OK to proceed.
Restart Services
More
KNOWLEDGE BASE

Which ports does PRTG use on my system?
3075
3076
13.2 PRTG Administration Tool on Remote Probe Systems
If you start the PRTG Administration Tool on a remote probe system, you can define various probe-
related settings, restart services, and view log information. You can also change many of these settings
via the system administration 2865 and the probe settings 536 in the PRTG web interface.
The PRTG Administration Tool is only available on Windows systems and does not affect multi-
platform probes. For more information on how to configure and restart multi-platform probes, see the
Multi-Platform Probe for PRTG manual.
In this section:
§ Start the PRTG Administration Tool 3077
§ Probe Settings for Core Connection 3077
§ Probe Settings for Monitoring 3081
§ Service Start/Stop 3082
§ Scheduled Restart Settings 3083
§ Logs and Info 3085
§ Send Logs to Paessler 3086
§ Activate Changed Settings 3088
This section describes the available settings in the PRTG Administration Tool when you open it on a
remote probe system. This is not the complete set of available settings. If you need access to all
settings regarding the entire PRTG installation, open the PRTG Administration Tool on the PRTG core
server system.
Settings you make here are only valid for the remote probe system on which you open the PRTG
Administration Tool. Make sure that you log in to the system that you want to make changes to and
open the PRTG Administration Tool there.
Start the PRTG Administration Tool

§ From the Windows Start menu, select the PRTG Network Monitor folder and click PRTG
Administration Tool to open the application.
§ Confirm the question of the Windows User Account Control with Yes to allow the PRTG Administration
Tool to start.
Probe Settings for Core Connection

Define general settings regarding the remote probe and connections.
3077
Probe Settings for Core Connection Tab
Probe Settings
Setting Description
Probe Name Enter a name to identify the remote probe. PRTG shows this name, for
example, in the device tree, and in all alarms by default. Enter a string.
3078
Setting Description
Reconnect Time Define the time that PRTG waits for the remote probe to reconnect to the
PRTG core server if the connection fails. Enter an integer.
Connection to PRTG Core Server
These settings affect the way the remote probe connects to the PRTG core server.
Setting Description
Server (IPv4 Address or Enter the IP address or Domain Name System (DNS) name of the PRTG
DNS Name) core server.
GID The probe GID (global ID (GID)) is a unique identifier for the remote probe.
We recommend that you do not change it.
Exceptions: If you substitute a remote probe from a different computer,
you must copy the GID from the old probe to the new probe. To do so,
click Edit GID and confirm the warning with Yes. You can then change
the GID. PRTG checks if the GID is valid. You can also generate a new
GID if necessary. To do so, click Generate new GID and confirm the
warning with Yes.
You can deny GIDs under Setup | System Administration | Core &
Probes 2900 in the PRTG web interface. If you remove a remote probe
from the device tree or if you deny a remote probe after installation 109 ,
PRTG automatically enters its GID in the Deny GIDs list.
Access Key The probe access key must match one of the access keys in the PRTG
core server installation. If it does not match, the remote probe is not able
to connect to the PRTG core server.
For more information, see section Core & Probes 2900 .
Also check the allowed and denied IP addresses in the Core &
Probes 2900 settings to make sure that the PRTG core server accepts
the IP address of the remote probe.
Confirm Access Key If you enter an access key for a remote probe, enter it in this field again to
confirm it.
Path for the PRTG Data Directory on the Probe System
3079
Setting Description
Path Select the directory where PRTG stores configuration and monitoring
data. Click to choose a different folder on the system.
Before you change the path, make sure you stop both the PRTG
core server service and the PRTG probe service and copy all data to
the new location.
The directory name must include only ANSI characters. PRTG does
not support data paths with non-ANSI characters.
Language for the PRTG Administration Tool for Remote Probes
Setting Description
[your language] Choose the language for the PRTG Administration Tool on the remote
probe. The default is English.
§ Deutsch (German)
§ English
§ (Russian)
§ (Japanese)
3080
Probe Settings for Monitoring
Probe Settings for Monitoring Tab

3081
Setting Description
Service Start/Stop
You can manually start and stop the PRTG probe service. Click Start Service to start the service or Stop
Service to stop it. Both actions usually take from a few seconds up to several minutes. You can also
restart the PRTG probe service under Setup | System Administration | Administrative Tools 2929 in the
PRTG web interface.
We recommend that you schedule automatic service restarts.
3082
Service Start/Stop Tab

This setting is not available on the hosted probe of a PRTG Hosted Monitor instance.
Setting Description

§ No scheduled system or service restart: Do not automatically perform a
scheduled restart of services. We recommend that you manually restart
the PRTG core server system every few weeks. You can initiate a
restart of the PRTG probe service in the Administrative Tools 2928 in the
PRTG web interface.
3083
Setting Description
§ Scheduled restart of PRTG services: Restart the PRTG probe service

on the probe system. If you select this option on the local probe, the
PRTG core server service restarts as well. Define a schedule under
Restart Schedule.
Restart Schedule. We recommend that you restart probe systems
once a month for best performance.
Restart Schedule This setting is only visible if you select Scheduled restart of PRTG
Choose how often you want to restart the PRTG probe service or the
probe system:
below.
Day This setting is only visible if you select Scheduled restart of PRTG
Select a day of the week (Monday to Sunday) or month (1st to 30th or

If you select a date that does not exist in every month (for example,
the 30th day of February), PRTG automatically initiates the restart on
the last day of this month.
Time This setting is only visible if you select Scheduled restart of PRTG
Select the time of day when PRTG performs the restart.

here.
You can also define a restart schedule on the Settings tab 538 of a remote probe in the PRTG web
interface.
3084
Logs and Info
Logs and Info Tab
Logs
Button Description
Open Log Folder Open the PRTG data directory 3219 to access all logs that PRTG creates.
Send Logs to Paessler Open an assistant to send logs to the Paessler support team. See Send
Logs to Paessler 3086 for details.
This feature is only available with the commercial edition 21 of
PRTG.
3085
Button Description
You can also send logs with the support bundle via Contact
Support 2990 in the PRTG web interface.
Open Support Ticket Open the Help Desk portal on the Paessler website in a browser window.
If you need help, we recommend that you use the Contact Support
option in the PRTG web interface instead.
About
The About section shows information about the version of installed PRTG programs and copyright
information.

You can also send logs with the support bundle via Contact Support in the PRTG web interface.
3086
If you open a support ticket, the Paessler support team might ask you to send logs for further analysis.
Field Description
Name Enter your name.
Email Enter a valid email address. You can provide any email address but we
recommend that you use the email address of your user account, which
PRTG enters by default.
Ticket # This field is optional. If you have already opened a ticket with the Paessler
support team, provide the ticket number you received. Your files are then
automatically associated with your ticket.
3087
Field Description
Enter the ticket number starting with PAE followed by four or more digits,
for example, PAE12345. If you do not have a ticket number, leave this
field empty.
Click Send to start the data upload. PRTG then automatically collects, compresses, and sends your
logs to our FTP over SSL (FTPS) server. Make sure that FTPS and HTTP connections are allowed on the
Activate Changed Settings

After you change settings, click Save & Close. A new window opens where PRTG asks you to agree to
restart the PRTG probe service. Click OK to proceed.
Restart Services
More
KNOWLEDGE BASE

Which ports does PRTG use on my system?

3088
Part 14
Advanced Topics
3/1/2023 3089
14 Advanced Topics
In this section, we cover more advanced topics. If you already have some experience with PRTG, you
might want to learn more about the following topics.
In this section:
§ Active Directory Integration 3091
§ Application Programming Interface (API) Definition 3094
ú HTTP API 3095
ú Live Data 3098
ú Live Graphs 3129
ú Historic Data 3132
ú Object Manipulation 3135
ú Custom Sensors 3142
ú Custom Notifications 3156
ú Mini Probe API 3158
§ Filter Rules for Flow, IPFIX, and Packet Sniffer Sensors 3178
§ Channel Definitions for Flow, IPFIX, and Packet Sniffer Sensors 3183
§ Define IP Address Ranges 3185
§ Define Lookups 3186
§ Regular Expressions 3198
§ Calculating Percentiles 3200
§ Add Remote Probe 3201
ú Remote Probes and Multiple Probes 3203
ú Classic Remote Probe Setup via Device Tools 3207
§ Failover Cluster Configuration 3213
§ Data Storage 3218
3090
14.1 Active Directory Integration
You can add PRTG user groups to PRTG, or you can add user groups from an Active Directory (AD).
When you integrate the AD into PRTG, you map a user group from the AD to a user group in PRTG. All
members of the AD group can then log in to PRTG with their AD domain credentials.
You cannot add single AD users to PRTG. You can only allow access for entire AD groups. PRTG
automatically creates a user account for each AD user that successfully logs in to PRTG.
Step 1: Prepare the AD

§ In the AD, make sure that the users that you want to give access to PRTG are members of the same
user group in the AD.
§ You can also organize users into different user groups, for example, one user group whose members
have administrative rights in PRTG, and one user group whose members only have read access in
PRTG.
Step 2: Prepare the PRTG Core Server

§ Make sure that the PRTG core server system is a member of the domain that you want to integrate it
into. To check this setting, open the Windows Control Panel and click the Change settings link under
System, section Computer name, domain, and workgroup settings.
Step 3: Add AD Domain and Credentials (optional) to System Settings

§ In the PRTG web interface 127 , select Setup | System Administration | Core & Probes from the main
menu.
§ In section Active Directory Integration, enter the name of the local AD domain in the Domain Name
field.
You can only integrate one AD domain into PRTG.
§ The following process is optional. PRTG uses the same Windows user account from which a user runs
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 user groups from the AD, provide the credentials of a
user account that has full AD access by using the Use explicit credentials option as Access Type.
If you cannot save changes to the Core & Probes settings because you get an Error (Bad
Request) with the message Active Directory Domain not accessible, select Use explicit
credentials as Access Type and provide the correct credentials for your AD domain.
§ Save your settings.
Step 4: Add a New User Group

§ Go to the User Groups tab 2922 .
§ Hover over and click Add User Group to add a new user group.
§ Enter a User Group Name to identify the group and select Use Active Directory integration under
Active Directory or Single Sign-On Integration.
3091
§ From the Active Directory Group dropdown list, select the group in the AD whose members have
access to PRTG. If you have a very large AD with more than 1,000 entries, you see an input field
instead of a dropdown list. In this case, you can only enter the name of the user group in the AD.
PRTG automatically adds the domain name prefix.
§ For User Type, define the access rights 149 that a user from the selected AD group has when they log
in to PRTG for the first time. You can choose between Read/write user and Read-only user. Read-only
access is useful to only show data to a large group of users.
§ Click Create.
All users in this newly created AD group can now log in to PRTG with their AD domain credentials. Their
user accounts have the group access rights 149 of the user group that you just created.
Notes and Restrictions

§ AD users can log in 157 to the PRTG web interface with their Windows user name and password. Do
not enter any domain information in the Login Name field. When an AD user logs in, PRTG
automatically creates a corresponding local account on the PRTG core server. PRTG synchronizes
credentials every hour.
§ Do not change the Login Name in PRTG for AD users unless the name changes in the AD. If you
change the Login Name in PRTG, it has no effect on the name in the AD.
§ AD queries are in read-only mode and are compatible with Read-only Domain Controllers (RODC).
§ For performance reasons, PRTG caches all requests to AD servers for one hour. If a password
changes, if you add a new user group in the AD, or if you change the group membership of an AD
user, you must either wait one hour or manually clear the cache by selecting Setup | System
Administration | Administrative Tools from the main menu and clicking Go! in the Clear Caches
section.
§ By default, no access rights for monitoring objects, libraries, maps, or reports are set for the new user
group in PRTG. This is why, initially, users in this user group do not see monitoring objects, libraries,
maps, or reports. This does not apply if the new user group has administrative rights. Edit the
monitoring object's settings 204 and the settings of libraries, maps, and reports, and set access rights
for the newly created user group in the respective Access Rights section.
We recommend that you set these access rights in the root group settings 469 and use the
inheritance of settings 140 .
§ PRTG only supports explicit user group rights. If the AD uses groups that are members of other user
groups, PRTG does not regard the inherited implicit rights of the parent group and therefore refuses the
login for members of these user groups.
§ PRTG ignores AD information about organization units (OU). PRTG cannot read these values.
However, if you use the AD in an auto-discovery group 278 , you can restrict the auto-discovery to
machines that are part of an OU.
§ You can integrate only one AD domain into PRTG.
§ PRTG does not support trusted domains or AD subdomains.
§ If you have a very large AD with more than 1,000 entries, you see an input field instead of a dropdown
list. In this case, you can only enter the name of the user group in the AD. PRTG automatically adds
the domain name prefix.
§ A local user account for an AD user is only created if this AD user has successfully logged in to
PRTG. If you want to send email notifications 2825 to an AD group in PRTG using the option Send to
User Group in the notification settings, a member of this AD group has to log in to PRTG at least once
to receive email notifications. To avoid this, enter the email address of the AD group in the Send to
Email Address field in the notification settings and select None for the Send to User Group option.
3092
§ If you want to delete an AD group from PRTG because of some changes to the AD, for example, you
must delete all users that are in this user group first. This is because AD users always have this user
group set as their primary group, and user accounts must have a primary group.
§ If you change the group membership of an AD user, this change is only reflected in the respective user
groups in PRTG if this AD user has logged in to PRTG again.
§ If you delete an AD user from all user groups in the AD that are related to PRTG access, this user
cannot log in to PRTG anymore. However, you still see the user in the user account list in PRTG.
More
KNOWLEDGE BASE

3093
14.2 Application Programming Interface (API) Definition
The PRTG API enables you to access monitoring data and manipulate objects using HTTP requests, run
your own written sensors and notifications, and implement mini probes.
In this section:
§ HTTP API 3095
§ Live Data 3098
ú Single Object Property 3099
ú Single Object Status 3102
ú Multiple Object Property or Status 3109
ú System Information 3125
§ Live Graphs 3129
§ Historic Data 3132
§ Object Manipulation 3135
§ Custom Sensors 3142
§ Custom Notifications 3156
§ Mini Probe API 3158
More
KNOWLEDGE BASE
How can I share my self-written PRTG script/program with other PRTG users?
Where can I find PRTG mini probes which are ready to use?
3094
14.2.1 HTTP API
All calls to the PRTG API are performed by HTTP GET requests. The URLs consist of a path to the API
function and some parameters.
§ If you are accessing the PRTG API inside your secure LAN, you can use HTTP. In environments that
are not secure (for example, when accessing your PRTG core server via the internet), you should use
HTTPS requests to make sure that your parameters and passwords are encrypted. This way, all
communication between the PRTG core server and your client is Secure Sockets Layer (SSL)
encrypted.
§ For every API call, the default limit of items is 500. If you want to receive more items per call, add a
count=xxx parameter with enough room for all sensors.
§ You must include authentication with API key or user name and passhash 2813 (or user name and
password) in each request.
See section Authentication 3096 for more information.
§ All data in the GET parameters must be UTF-8-encoded and URL encoded.
Output Formats
Most data that you can request from the PRTG API is available in data tables in the Extensible Markup
Language (XML), the JavaScript Object Notation (JSON) format, and the comma-separated values (CSV)
format (using the XML format is recommended). Here are some sample calls with different output
formats.
Examples
XML
https://yourserver/api/table.xml?content=sensors&columns=sensor
JSON
https://yourserver/api/table.json?content=sensors&columns=sensor
CSV
https://yourserver/api/table.xml?content=sensors&columns=sensor&output=csvtable
The example URLs consist of the following elements.
Element Description
yourserver The name of your PRTG server.
/api/table.xml Addresses an API function. Here, the function renders a table in the XML
or format or in the JSON format.
/api/table.json
content=sensors Parameter for additional control. In this case, it includes all sensors in the
table.
3095
Element Description
columns=sensor Parameter for additional control. In this case, only the names of all
sensors are shown in the table.
output=csvtable Renders a table in the CSV format.

(optional)
Authentication
All requests to the PRTG API are stateless, which means that there is no multi-step login process of any
kind. You must include the authentication with an API key or with a user name and a passhash (or a
user name and a password) in each request by using the apitoken parameter or the user name and
passhash (or user name and password) parameters:
apitoken parameter
§ apitoken=myapitoken
You can add, edit, and delete your API keys in the account settings on the API Keys 2861 tab.
user name and passhash (or user name and password) parameters
§ username=myuser&passhash=hash (or password=mypassword)
You can request the passhash for an account with the following API call:
https://yourserver/api/getpasshash.htm?username=myuser&password=mypassword
Make sure that the user name and password are URL-encoded.
Examples
https://yourserver/api/table.xml?content=sensors&columns=sensor&apitoken=myapitoken
or:
https://yourserver/api/table.xml?
content=sensors&columns=sensor&username=myuser&password=mypassword
or:
https://yourserver/api/table.xml?
content=sensors&columns=sensor&username=myuser&passhash=hash
3096
Versioning
Most XML replies from the PRTG API contain a <version> field that contains the program version and
buildnumber of the server's PRTG installation. Your client must look at this version number and compare
it to the version number that was used to develop the client. Do not accept version numbers older
(smaller) than this one. You should display a warning to the user (or stop processing) if the version
number differs by 0.1 or more (for example, version 18.1 vs. 18.2, or version 17.x vs. 18.x). PRTG API
conventions or parameters might have changed between versions.
Newer versions of the same major version of PRTG reply to API calls just like previous versions did.
Error Handling
Depending on whether an API call was successfully processed or not, the PRTG core server replies with
the following HTTP status codes:
HTTP Status Code Meaning Comments
200 OK The API call was successfully completed , the XML

response contains the result data.
302 Found The API call was successfully completed and a new
object was created (the redirection URL contains the
new object ID).
400 Bad Request The API call could not be successfully completed. The
XML response contains the error message.
401 Unauthorized The user name/password credentials cannot be

accepted.
For 400 error codes, the error .xml document includes the error message as follows:
<prtg>
<version>23.4.90.1235+</version>
<error>Sorry, there is no object with the specified id.</error>
</prtg>
More
KNOWLEDGE BASE
How can I use the PRTG Application Programming Interface (API)?

3097
14.2.2 Live Data
You can access live data and live status data of objects using the PRTG API.
In this section:
§ Single Object Property 3099
§ Single Object Status 3102
§ Multiple Object Property or Status 3109
§ System Information 3125
Getting PRTG System Status

You can also get the PRTG system status such as the number of alarms or messages using the
following API calls.
Examples
Live system status in the Extensible Markup Language (XML) format:

/api/getstatus.xml?id=0
Live system status in the JavaScript Object Notation (JSON) format:

/api/getstatus.htm?id=0
All sensors in use in the JSON format:

/api/sensortypesinuse.json
Number of all sensor states:

/api/gettreenodestats.xml
Getting PRTG Health Status

You can also get the overall PRTG system health status such as probe connection status and if login is
possible using the following API calls:
Examples
Live overall system status of PRTG in the JSON format:

/api/healthstatus.json
Live overall system status of PRTG Hosted Monitor in the JSON format:
/api/healthstatus.json&mode=hosted
3098
Getting PRTG Health Data
You can also get the PRTG health data such as system CPU used (%), system memory used (%), disk
space used (%), disk space used (GB), health (%), total number of probes, disconnected probes, total
sensors, and sensor in the Unknown status using the following API calls:
Example
Live health data of PRTG in the JSON format using maxage:

/api/health.json&maxage=age
maxage is the age in seconds for data to be considered "old". For example, if data is older than 4
minutes and maxage=120, the data will be refreshed and then sent to the client.
Live health data of PRTG in the JSON format using refreshnow:
/api/health.json&refreshnow=1/anything_else
If refreshnow=1, the data will be refreshed before the API call is returned. Also, if refreshnow=1 is
present in the API call, maxage will not be considered.
More
KNOWLEDGE BASE

14.2.2.1 Single Object Property
You can access live data and live status data of single objects using the PRTG API.
Authentication with API key or user name and passhash 2813 (or user name and password) must
always be included in each PRTG API request. See section HTTP API 3096 for more information.
In this section:
§ Property/Setting of an Object 3099
§ Supported Object Types 3100
§ Available Channel Parameters 3101
§ Property of a Channel 3101
Property/Setting of an Object
You can get the properties or settings of an object (name, hostname, url) using the following API calls.
Because properties might contain HTML content, we recommend that you include
&show=nohtmlencode in all getobjectproperty API calls.
3099
Examples
Get an object property/setting:

/api/getobjectproperty.htm?id=objectid&name=propertyname&show=nohtmlencode
For propertyname, look at the name of the INPUT fields while editing an object. You can discern
the propertyname parameter by opening the Settings tab of an object and looking at the HTML
source of the INPUT fields. For example, the INPUT field for the tags of an object has the name tags_.
Leave away the underscore _ and use tags as a value for the propertyname parameter.
Get a list of all tags for object ID 1003

/api/getobjectproperty.htm?id=1003&name=tags&show=nohtmlencode
The Extensible Markup Language (XML) result looks like this:

<prtg>
<result>probehealthsensor</result>
</prtg>
Supported Object Types

getobjectproperty.htm supports the following object types:
§ probe
§ group
§ device
§ sensor
§ channel
§ library
§ map
§ notification
§ report
§ schedule
§ user account
getobjectproperty.htm does not support the object types ticket and user group.
3100
Available Channel Parameters
Name of Input Field Setting Name (as displayed in the PRTG web interface)
name Name
limitmode Limit disabled or enabled (0 or 1)
limitmaxerror Upper Error Limit
limitmaxwarning Upper Warning Limit
limitminwarning Lower Warning Limit
limitminerror Lower Error Limit
limiterrormsg Error Limit Message
limitwarningmsg Warning Limit Message
Property of a Channel
With this API call, you can get a sensor's channels settings 2692 , for example channel limits. In general,
this works like getting properties of any other object. To get channel properties via the PRTG API, you
need to provide
§ the ID of a sensor (parameter id),
§ a subtype (channel for channels), and
§ a subid (ID of the channel that you want to edit)
Because properties might contain HTML content, we recommend that you include
&show=nohtmlencode in all getobjectproperty API calls.
Examples
Get a channel limit

/api/getobjectproperty.htm?
id=sensorid&subtype=channel&subid=channelid&name=limitname&show=nohtmlencode
For example, the following API call gets the upper warning limit of a channel with the ID 0 of a sensor
with the ID 1003
/api/getobjectproperty.htm?
id=1003&subtype=channel&subid=0&name=limitmaxwarning&show=nohtmlencode
3101
The XML result looks like this:
<prtg>
<result>25</result>
</prtg>
More
KNOWLEDGE BASE

14.2.2.2 Single Object Status
You can access live data and live status data of single objects using the PRTG API.
In this section:
§ Status of an Object 3102
§ Supported Object Types 3103
§ Supported getobjectstatus Output Columns ("Name=" Parameter) 3103
§ Sensor Details 3108
§ Ticket Status and Message 3109
Status of an Object
You can get the status information (lastvalue, downtime) of an object using the following API calls:
Examples
Get object status:

/api/getobjectstatus.htm?id=objectid&name=columnname
The Extensible Markup Language (XML) result looks like this:
3102
<prtg>
<<version>23.4.90.1235+</version>
<result>True</result>
</prtg>
In some cases, the result can contain HTML formatting elements.
Supported Object Types

getobjectstatus.htm supports the following object types:
§ probe
§ group
§ device
§ sensor
Supported getobjectstatus Output Columns ("Name=" Parameter)

With getobjectstatus.htm, you can use the following column names for the name parameter.
Only one column name is allowed in the API call.
If you want to use combinations of column names or more than one object in a single API call, use a
table API call instead. For more information, see section Multiple Object Property or Status 3109 .
Column Name What It Displays Can Be Used for
objid ID of the object probes, groups, devices, sensors
type Object type or sensor type probes, groups, devices, sensors
name Name of the object probes, groups, devices, sensors
tags List of all tags. This includes tags probes, groups, devices, sensors
from the object itself plus tags that
are inherited from parent objects.
active True/false depending on whether an probes, groups, devices, sensors

object is set to paused by a user
downtime Cumulated downtime of the sensor sensors

(displayed as percentage of
uptime+downtime)
3103
downtimetime Cumulated downtime of the sensor (in sensors

minutes/hours)
downtimesince Elapsed time since the last Up status sensors

of the sensor
uptime Cumulated uptime of the sensor sensors

uptime+downtime)
uptimetime Cumulated uptime of the sensor (in sensors

minutes/hours)
uptimesince Elapsed time since the last Down sensors

status of a sensor
knowntime Sum of cumulated uptime and sensors

downtime of the sensor
The output contains HTML.
cumsince Time stamp when accumulation of sensors

uptimes/downtimes began
sensor Name of the sensor sensors
interval Effective interval setting for the sensor sensors
lastcheck Time stamp of the last sensor result sensors

lastup Time stamp of the most recent Up sensors

status of the sensor
lastdown Time stamp of the most recent Down sensors

device For sensors: ID of the associated devices, sensors

device
3104
For devices: name of the associated

device
group For sensors: ID of the associated groups, devices, sensors

group
For devices: name of the associated

group
probe Name of the associated probe probes, groups, devices, sensors
grpdev Name of the associated device and sensors

associated group, separated by slash
notifiesx Returns a string containing the probes, groups, devices, sensors

number of each trigger type defined for
this object. If trigger inheritance is
active, it displays Inherited.
intervalx Either Inherited or the current interval probes, groups, devices, sensors
setting of the object
dependency Name of an associated dependency probes, groups, devices, sensors

or Parent
probegroupdevice Partial object hierarchy with names of probes, groups, devices, sensors
associated device, group, and probe
separated by angle brackets (>).
probegroupdevice is not
available in the CSV format.
For the complete object
hierarchy, use probe, group,
device instead.
status Integer of the status of the object probes, groups, devices, sensors
(0=None, 1=Unknown, 2=Scanning,
3=Up, 4=Warning, 5=Down, 6=No
Probe, 7=Paused by User, 8=Paused
by Dependency, 9=Paused by
Schedule, 10=Unusual, 11=Not
Licensed, 12=Paused Until, 13=Down
Acknowledged, 14=Down Partial)
3105
message Detailed message of the object probes, groups, devices, sensors

priority Priority setting of the object probes, groups, devices, sensors
lastvalue Last sensor result value sensors
upsens Number of sensors in the Up status probes, groups, devices, sensors

PRTG only counts the sensor
itself or sensors below the object
in the hierarchy.
If the count is <1 PRTG returns
"".
downsens Number of sensors in the Down status probes, groups, devices, sensors
in the hierarchy.
"".
downacksens Number of sensors in the Down probes, groups, devices, sensors

(Acknowledged) status
in the hierarchy.
"".
partialdownsens Number of sensors in the Down probes, groups, devices, sensors

(Partial) status
in the hierarchy.
"".
warnsens Number of sensors in the Warning probes, groups, devices, sensors

status
3106

in the hierarchy.
"".
pausedsens Number of sensors in the Paused probes, groups, devices, sensors

status
in the hierarchy.
"".
unusualsens Number of sensors in the Unusual probes, groups, devices, sensors

status
in the hierarchy.
"".
undefinedsens Number of sensors in an undefined probes, groups, devices, sensors

status, like None, Unknown, No Probe
in the hierarchy.
"".
totalsens Number of all sensors probes, groups, devices, sensors

in the hierarchy.
"".
favorite An exclamation mark (!) if the object groups, devices, sensors

is marked as favorite
schedule Name of the associated schedule probes, groups, devices, sensors
3107
minigraph Numeric data for the minigraphs. sensors

Numbers are 5-minute averages for
the last 24 hours (must be scaled to
the maximum of the series). There are
two datasets: "|" separates measured
value series and error series.
comments Object comments probes, groups, devices, sensors
host Hostname or IP address devices
condition For probes: If the probe is connected probes, groups

or disconnected (0=Disconnected,
1=Unauthorized, 2=Connected,
3=Banned, 4=Init)
For groups: The auto-discovery status
basetype Object type (string) probes, groups, devices, sensors
baselink URL of the object probes, groups, devices, sensors
icon URL of the device icon devices
parentid ID of the parent object probes, groups, devices, sensors
location Location property (used in Geo Maps) devices

groupnum Number of groups or devices in the probes, groups

devicenum probe or group
Sensor Details
You can get details about a sensor (sensortype, interval, uptime) using the following API calls:
You need the sensor ID to get details about a sensor. You can find the ID on the sensor's Overview
tab or by hovering over a sensor in the device tree, for example.For more information about the
Overview tab, see the Knowledge Base: What options do I have to review my monitoring data in
detail?
3108
Examples
Get details about a sensor in the XML format:

/api/getsensordetails.xml?id=sensorid
Get details about a sensor in the JavaScript Object Notation (JSON) format:
/api/getsensordetails.json?id=sensorid
Ticket Status and Message

The following API calls return status and message of a ticket.
Examples
The status of a ticket:

/api/getticketstatus.htm?id=ticketid
The subject and assignee of a ticket:

/api/getticketmessage.htm?id=ticketid
More
KNOWLEDGE BASE

14.2.2.3 Multiple Object Property or Status
You can access live data and live status data of multiple objects using the PRTG API.
In this section:
§ Property or Status of Multiple Objects 3110
§ Table Query Builder 3110
§ Output Data Format 3110
§ RAW Date/Time Format 3111
§ Common Data Table Parameters 3111
§ Filtering by Object ID 3112
3109
§ Sorting and Advanced Filtering 3113
§ Supported Output Columns ("columns=" Parameter) 3116
Property or Status of Multiple Objects

Most data that you can request from the PRTG API is available in data tables in the Extensible Markup
Language (XML) format, the JavaScript Object Notation (JSON) format, and the comma-separated values
(CSV) format (using the XML format is recommended). The API function /api/table.xml is used to access
data in tables. Here are some sample calls (URLs are shown without authentication parameters to
enhance readability).
The example URLs only show the XML URLs. Use the API function /api/table.csv or the
output=constable parameter to select the CSV format, or /api/table.json to return the JSON format.
Examples
A hierarchical list of all groups, devices, and sensors with their status information:
/api/table.xml?content=sensortree
sensortree does not support JSON output.

All sensors (with status information):
/api/table.xml?
content=sensors&columns=objid,group,device,sensor,status,message,lastvalue,priority
,favorite
All recent log entries:

/api/table.xml?
content=messages&columns=objid,datetime,parent,type,name,status,message
You have the easiest start if you use the table query builder 3110 or click , which most data tables have
in the PRTG web interface. Navigate to the information that you want to use, click , and you are taken
to a URL that renders the content of the table in XML format. You can now use the URL as it is or
change various parameters to suit your needs.
For more information on possible raw message status values returned by table-based API calls, see
the Knowledge Base: Is there a list of log status values for the PRTG API?
Table Query Builder

You can use the query builder tool to experiment with the PRTG API and to fine-tune your queries. You
can find it in the PRTG web interface under Setup | PRTG API, section Live Data.
Output Data Format

XML data from the PRTG API contains the fields that you requested in the columns parameter. In most
cases, numeric values are included twice: One field contains the value in human-readable format and an
additional _RAW field contains the value as a number, which is better suited for further processing and
calculations.
3110
Example
<status>Up</status>
<status_RAW>3</status_RAW>
<lastvalue>98 %</lastvalue>
<lastvalue_RAW>97.7583</lastvalue_RAW>
<message>Created. 18.3.43.1360</message>
<message_RAW>Created. 18.3.43.1360</message_RAW>
§ The status field shows the value Up (the according RAW value is 3).
§ The lastvalue field shows the value 98% (the according RAW value is 97.7583).
§ The message field shows the text Created. 18.3.43.1360 (the according RAW value is Created.
18.3.43.1360).
Strings returned from _RAW columns are surrounded by double quotation marks (") in JSON
output.
RAW Date/Time Format

For columns with date/time value, the RAW value is defined as follows: The integral part of a value is the
number of days that have passed since Dec 30th, 1899. The fractional part of a value is a fraction of a 24-
hour day that has elapsed. To find the fractional number of days between two dates, subtract the two
values. Similarly, to increment a date and time value by a certain fractional number of days, add the
fractional number to the date and time value.
Here are some examples of date/time RAW values and their corresponding dates and times:
RAW Date/Time Value Description
0 12/30/1899 00h00m (12:00 midnight)
2.75 1/1/1900 18h00m (6:00 pm)
35065 1/1/1996 00h00m (12:00 midnight)
Common Data Table Parameters

The following parameters are common to all data table API calls:
Parameter Description Possible Values
content Select the objects that you sensortree (JSON output not supported)
want to have in your table.
3111
devices
sensors
tickets
ticketdata
messages
values
channels
reports
storedreports
toplists
sysinfo (only JSON output supported)
columns Comma-separated list of see Supported Output Columns ("columns="

columns per record Parameter) 3116
output Control the output format xml: default format (recommended)

xmltable: an HTML table in the XML format
csvtable: CSV format
html: HTML table
json: JSON format
jsontable: a table in the JSON format
count Maximum number of items 1-50000

(The default count is 500)
start Start with this entry number any

(can be used with "count" to
request the data page by
page)
Filtering by Object ID
Add an ID parameter (for example, id=1) to the API URL to select a subset of items for the data table, for
example, to reduce the amount of data transferred for each data table API call. The data table only
contains information for this object ID and its child objects.
Some table types require an ID. If you omit the ID parameter or if it has the value zero (0), all
available objects are used.
3112
Table Type ID Required or Description Object Types
(content=) Optional Allowed for the ID
sensortree optional You only get a part of the tree Probe

(the object with the specified ID
and all child objects below it). Group
JSON output is not

supported.
sensors optional You only get the object with the Probe
devices specified ID and all child objects
below it. Group
Device
tickets optional You only get tickets or log file Any object
messages entries that are related to the
object with the specified ID or
any child objects below it.
values required You get the data values (or Sensor

channels channels) of the sensor with the
specified ID.
reports not used This data table always includes n/a

all reports.
storedreports required You get a list of stored .pdf files Report

of the report selected by the ID.
ticketdata required You get the history of the ticket Ticket

selected by the ID.
sysinfo required You get system information of Device

the object with the specified ID.
Sorting and Advanced Filtering

There are various options to further filter and to sort the data for each data table API call:
filter_drel Only include records today

younger than this setting
yesterday
3113
For content=messages 7days

and content=tickets
only. 30days
12months
6months
filter_status Only include sensors with a Unknown=1

specific status. Using
multiple filter_status fields Collecting=2
performs a logical OR. Up=3
For content=sensors Warning=4
only.
Down=5
NoProbe=6
PausedbyUser=7
PausedbyDependency=8
PausedbySchedule=9
Unusual=10
PausedbyLicense=11
PausedUntil=12
DownAcknowledged=13
DownPartial=14
filter_tags Only include sensors with a @tag(tagname)

specific tag. Using multiple
filter_tag fields performs a
logical OR.
For content=sensors
only.
filter_xyz Filter the data. (Samples: filter_xyz where xyz is any column name
filter_type=ping, used in the columns parameter
filter_favorite=1). Using Substrings: use
multiple filter_xyz fields filter_xyz=@sub(substring1,substring2)
performs a logical OR. Values not equal/above/below: use
filter_xyz=@neq(value),
filter_xyz=@above(value),
filter_xyz=@below(value)
3114
Filtering using columns is

only possible for tree
objects. You cannot use
columns to filter objects
like messages or tickets,
for example. For
content=tickets, you can
use the special filter terms
filter_status
filter_user, and
filter_type (this corresponds
to column tickettype).
Like for messages, you can
also use
filter_drel,
filter_dstart,
and filter_dend.
Multiple filters are not
available for tickets.
sortby Sort the data. If this Any column name used in the columns
parameter is omitted, the parameter.
table is sorted based on the
first column. Add a leading Log tables with content=messages are
"-" to reverse sort order. always sorted by descending date.
(Samples: sortby=name,
sortby=lastvalue, sortby=-
lastvalue, sortby=uptime)
Examples
Here are some samples for filtered API calls:

All sensors that are not in the Up status 184 (with their status and downtime information):
/api/table.xml?
content=sensors&columns=objid,downtimesince,device,sensor,lastvalue,status,message,
priority
&filter_status=5&filter_status=4&filter_status=10&filter_status=13&filter_status=14
&sortby=priority
Fastest Ping sensors:

/api/table.xml?
content=sensors&columns=objid,sensor,lastvalue,status,message&sortby=lastvalue
&filter_type=ping
Log entries of the last 7 days for object id 2003:
3115
/api/table.xml?content=messages&id=2003&start=0&filter_drel=7days&columns=
objid,datetime,type,name,status,message
Supported Output Columns ("columns=" Parameter)

You can use the following column names for the columns parameter (separated by comma, for example,
columns=objid,name,type).
objid ID of the object all object tables
type Object type (group, device, all object tables

report, etc.), or the sensor type
(ping, http, etc.), or event type
for tickets (relevant for ToDo
tickets)
name Name of the object or channel. all object tables

For log messages/tickets: the channels
name of the related object.
messages
For stored reports: the name of
the report file. storedreports
toplists
tickets
tags List of all tags (for tickets: tags all object tables (except for user)
for the related object). This
includes tags from the object
itself plus tags that are inherited
from parent objects.
active True/false depending on whether all object tables

an object is set to paused by a
user (for tickets: related object).
For notifications that are paused
by schedule, it also displays the
end of the schedule.
downtime Cumulated downtime of the sensors

sensor (displayed as percentage
of uptime+downtime)
downtimetime Cumulated downtime of the sensors

sensor (in minutes/hours)
3116
downtimesince Elapsed time since last Up sensors

uptime Cumulated uptime of the sensor sensors

uptime+downtime)
uptimetime Cumulated uptime of the sensor sensors

(in minutes/hours)
uptimesince Elapsed time since the last sensors

Down status of the sensor
knowntime Sum of cumulated uptime and sensors

downtime of the sensor
cumsince Time stamp when accumulation sensors

of uptimes/downtimes began
sensor Name of the sensor sensors

toplists
interval Effective interval setting for the sensors

sensor
lastcheck Time stamp of the last sensor sensors

result
lastup Time stamp of the most recent sensors

Up status of the sensor
lastdown Time stamp of the most recent sensors

Down status of the sensor
device Name of the associated device sensors

devices
group Name of the associated group sensors

devices
groups
probe Name of the associated probe sensors
3117
devices
groups
probes
grpdev Name of the associated device sensors

and the associated group
separated by a forward slash (/) devices
notifiesx Number of each trigger type probes

defined for the object
groups
devices
sensors
intervalx Either Inherited or the current probes

interval setting of the object
groups
devices
sensors
accessrights Access rights of the current all objects (except for user), for example:
user for the sensor tree object
probes
groups
devices
sensors
dependency Name of an associated probes

dependency or Parent
groups
devices
sensors
probegroupdevice Partial object hierarchy with sensor

names of associated device,
group, and probe separated by a device
forward slash (/). group
The output contains HTML. probe
probegroupdevice is not
available in the CSV
format.
3118
For the complete object

hierarchy, use probe, group,
device instead.
status For sensor tree objects: status sensors

of the object (0=None,
1=Unknown, 2=Scanning, 3=Up, devices
4=Warning, 5=Down, 6=No groups
Probe, 7=Paused by User,
8=Paused by Dependency, probes
9=Paused by Schedule,
messages
10=Unusual, 11=Not Licensed,
12=Paused Until, 13=Down tickets
Acknowledged, 14=Down
Partial)
For messages: category of the
log message
For tickets: status of ticket
(open, resolved, closed)
message Detailed message of the sensor sensors

tree object (for example, last
error of the sensor) or the devices
history entry, log entry, ticket groups
subject
probes
messages
tickets
ticketdata
history
priority Priority setting of the sensor sensors

tree object or the priority of the
log entry/ticket devices
groups
probes
messages
tickets (not supported: schedule,
notification, user)
lastvalue Last sensor result value or sensors

channel values
channels
3119
When used with channels, you

must use lastvalue_ to
automatically display volumes
and speed.
upsens Number of sensors in the Up all sensors

status
devices
PRTG only counts the
sensor itself or sensors groups
below the object in the probes
hierarchy.
downsens Number of sensors in the Down all sensors

status
devices
hierarchy.
downacksens Number of sensors in the Down all sensors

(Acknowledged) status
devices
hierarchy.
partialdownsens Number of sensors in the Down all sensors

(Partial) status
devices
hierarchy.
warnsens Number of sensors in the all sensors

Warning status
devices
hierarchy.
pausedsens Number of sensors in the all sensors

Paused status. This includes all
Paused states ('paused by devices
user', 'paused by dependency, groups
'paused by schedule', etc.).
3120
probes
unusualsens Number of sensors in the all sensors

Unusual status
devices
hierarchy.
undefinedsens Number of sensors in an all sensors

undefined status, like None,
Unknown, No Probe devices
PRTG only counts the groups

sensor itself or sensors probes
below the object in the
hierarchy.
totalsens Number of all sensors all sensors

PRTG only counts the devices
sensor itself or sensors
below the object in the groups
hierarchy. probes
size Performance impact of the sensors

sensor (1=Very Low, 2=Low,
3=Medium, 4=High, 5=Very
High)
value The channel value or the Toplist values

value
topdata
Should only be used as value_,
because then it is expanded for
all visible channels/toplist
columns
coverage Sensor coverage of the time values

span in a value table.
favorite An exclamation mark (!) if the sensors

sensor tree object is marked as
favorite devices
groups
probes
3121
user User responsible for a history history

entry or the user (or user group)
a ticket is assigned to. tickets
ticketdata
parent Name of the parent object of the messages

associated object of a log
message
datetime Time stamp or time span of the messages

object (for tickets: last
modification) tickets
ticketdata
values
history
storedreports
topidx
dateonly Like datetime but only the date messages

part
tickets
history
values
timeonly Like datetime but only the time messages

part
tickets
history
values
schedule For sensor tree objects: Name probes

of the associated schedule
groups
For reports: Report generation
schedule devices
sensors
reports
period Period of the report (day, week, reports

etc.)
email Email address of the report reports
3122
template Template used by the report reports
lastrun Time stamp of the last reports

generation of a report
nextrun Time stamp of the next reports

generation of a report
size Size of a stored report size of a stored report
minigraph Numeric data for the minigraphs. sensors

Numbers are 5-minute averages
for the last 24 hours (must be
scaled to the maximum of the
series). There are two datasets:
"|" separates measured value
series and error series.
deviceicon Device icon devices
comments Object comments all objects

For tickets: related object
host Hostname or IP address devices
devices For probes: probe status probes

(0=Disconnected,
1=Unauthorized, 2=Connected, groups
3=Banned, 4=Init)
For groups: auto-discovery
status
basetype Object type (string) all tree objects
baselink URL of the object all tree objects
icon URL of the device icon devices
parentid ID of the parent object or ID of a all tree objects

ticket
tickets
3123
location Location property (used in Geo devices

Maps)
fold Subobjects are folded up (true) probes

or down (false)
groups
For tickets: user (or user group)
to which a ticket is assigned tickets
read it since last change
groupnum Number of groups or devices in probes

devicenum the probe or group
groups
tickettype Type of ticket: user, notification, tickets

todo
modifiedby User who edited the ticket most tickets

recently
ticketdata
actions Types of all ticket edits ticketdata
content Text of the ticket that was ticketdata

added with the last edit
channel Number of channels with an ID sensors

greater than or equal to 0
_key, _value Key value pair from the system sysinfo (category: system)
table
_displayname, _class, Display name, class, and sysinfo (category: hardware)

_caption caption from the system table
_user, _domain User and domain pair from the sysinfo (category: loggedonusers)
system table
_displayname, Display name, creation date, sysinfo (category: processes)

_creationdate, and process id from the system
_processid table
_displayname, _state, Display name, state, and start sysinfo (category: services)
_startmode mode from the system table
3124
_displayname, Display name and version pair sysinfo (category: software)

_version from the system table
More
KNOWLEDGE BASE
Is there a list of log status values for the PRTG API?


14.2.2.4 System Information
You can access live data and live status data for system information using the PRTG API.
To retrieve system information using API calls, we recommend that you use the following order:
1. Refresh the system information so that it is up to date, if necessary.

For details, see Scan Now 3125 .
2. Retrieve generic system information to make sure that the last scan (step 1) was successful and that
there are no errors.
For details, see Generic Data 3126 .
3. Retrieve system information in the form of data tables.
For details, see Data Tables 3127 .
System information API calls only support the JavaScript Object Notation (JSON) output.
Scan Now
The following API calls to retrieve new information for a system information 208 category. To refresh
system information via the API, you need to provide
§ the ID of a device (parameter id), and
§ a kind (system information category 3126 ).
We recommend that you only refresh system information if absolutely necessary because the
refresh triggers a rescan of all system information tables.
Examples
3125
Refresh process information
/api/sysinfochecknow.json?id=deviceid&kind=processes
Refresh hardware information

/api/sysinfochecknow.json?id=deviceid&kind=hardware
sysinfochecknow only supports JSON output.
Supported Output Columns ("kind=" Parameter)
Column Name Category (as displayed in the PRTG web interface)
system System
hardware Hardware
processes Processes
services Services
software Software
loggedonusers Users
Generic Data
The following API calls retrieve generic data about the system information category since the last scan,
for example time stamps and if the last scan was successful. To retrieve this information via the PRTG
API, you need to provide
§ the ID of a device (parameter id), and
§ a kind (system information category).
Examples
Users
/api/sysinfo.json?id=deviceid&kind=loggedonusers
Services
/api/sysinfo.json?id=deviceid&kind=services
sysinfo only supports JSON output.
3126
Data Tables
The following API calls retrieve all information from a system information category table. To retrieve this
information via the PRTG API, you need to provide
§ the content type (always sysinfo),
§ the category (as displayed in the PRTG web interface),
§ columns (see Supported Output Columns ("columns=" Parameter) 3127 ), and
§ the ID of a device (parameter id).
Examples
System
/api/table.json?
id=deviceid&content=sysinfo&category=system&usecaption=true&headers=key,value&colum
ns=_key,_value
Software
/api/table.json?
id=deviceid&content=sysinfo&category=software&usecaption=true&headers=key,value&col
umns=_displayname,_version
Data tables for system information only support JSON output.
Supported Output Columns ("columns=" Parameter)

You can use the following sysinfo-specific column names for the columns parameter (separated by
comma, for example, columns=_key,_value).
For a list of all supported column names, see section Multiple Object Property or Status 3116 .
Column Name Description Can Be Used for
_key, _value Key value pair from the system sysinfo (category: system)
table
_displayname, _class, Display name, class, and sysinfo (category: hardware)

_caption caption from the system table
_user, _domain User and domain pair from the sysinfo (category: loggedonusers)
system table
3127
Column Name Description Can Be Used for
_displayname, Display name, creation date, sysinfo (category: processes)

_creationdate, _processid and process id from the system
table
_displayname, _state, Display name, state, and start sysinfo (category: services)
_startmode mode from the system table
_displayname, _version Display name and version pair sysinfo (category: software)
from the system table
More
KNOWLEDGE BASE

3128
14.2.3 Live Graphs
You can use live sensor graphs from PRTG in other web pages using the PRTG API. PRTG renders
graphs as .png or .svg files. You can include them in other web pages.
Examples
Live graph as a .png file:

/chart.png?type=graph&width=300&height=160&graphid=2&id=0
Live graph as an .svg file:

/chart.svg?type=graph&width=300&height=160&graphid=2&id=0
To switch between PNG and SVG images, change the file extension of /chart to .png or .svg.
The URL does not start with /api. When placing these URLs on web pages, keep in mind that the
URLs contain the account user name and password/passhash. This can imply security issues. We
recommend that you set up a dedicated read-only 149 user account in PRTG that is member of a
dedicated user group, for example, that only has read access to the root group and all underlying entries
or, even better, only for the object IDs that are used for graph URLs.
Parameters for Live Graph URLs (chart.png or chart.svg)
Parameter Description
type Must be graph
graphid Select time span of the graph:

§ 0=live
§ 1=last 48 hours
§ 2=30 days
§ 3=365 days
width Width of the image in pixels
height Height of the image in pixels
id The object ID of the desired graph object. This is usually the ID of a sensor.
clgid The NodeID of the cluster node of the desired graph object
3129
Use the format clgid=%7BXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX%

7D. You can also use clgid=%7B00000000-0000-0000-0000-
000000000000%7D to return a graph that has data from all cluster nodes.
graphstyling Allow control of some graph styles:
§ Display legend: graphstyling=showLegend%3D%271%27
§ Hide legend: graphstyling=showLegend%3D%270%27
§ Control font size: graphstyling=baseFontSize%3D%27XX%27 (XX is the

font size)
§ Control legend and font size at the same time: graphstyling=showLegend
%3D%271%27+baseFontSize%3D%275%27
bgcolor Background color of the PNG image, for example, #fffff. This affects the
area that surrounds the graph.
The value must be URL encoded, for example, %23fffff.
plotcolor Color of the graph's plot area, for example, #fffff. This affects the whole area
within the graph box.
plotcolor1 Alternating color of the graph's plot area, for example, #fffff. This affects the
tiles within the graph box alternating with plotcolor2. The result is a striped
graph box.

This parameter is overwritten when using the parameter plotcolor.
plotcolor2 Alternating color of the graph's plot area, for example, #fffff. This affects the
tiles within the graph box alternating with plotcolor1. The result is a striped
graph box.
This parameter is overwritten when using the parameter plotcolor.
gridcolor Color of grid lines in the graph's plot area, for example, #fffff. This affects the
horizontal and vertical lines within the graph box.
3130
hide Do not show defined channels in the graph. Use the ID of a channel to hide
it. For example, use hide=-4 to not show the Downtime channel in the
graph. To hide more than one channel, use commas to separate the IDs.
Retrieving Chart Legends (JSON)

You can show the legend of a sensor graph (channel IDs, colors, units, channel names) in the JavaScript
Object Notation (JSON) format.
Example
Chart legend in the JSON format:

/api/chartlegend.json?id=sensorid
More
KNOWLEDGE BASE

3131
14.2.4 Historic Data
You can download the historic monitoring data for one sensor in the Extensible Markup Language (XML)
format or the comma-separated values (CSV) format using the following API calls. You can either request
the results of each single monitoring request (called raw data) or you can let PRTG calculate averages of
the data (for example, hourly or daily averages).
To avoid potential server overload, the number of requestable values per API call is limited by means of
automatic averaging as follows:
Minimum Level of Detail (Average Interval) Maximum Timeframe per API Call
Raw data (all single monitoring requests) For up to 40 days per API request
60 minutes/1 hour averages 40 to 500 days per API request

If you try to use a larger time span than 500
days, PRTG automatically reduces it to 365
days.
API calls for historic data are limited to 5 requests per minute.
API Calls for Historic Data

The API calls for historic data tables look like this:
Examples
XML:
/api/historicdata.xml?id=objectid&avg=0&sdate=2023-01-20-00-00-00&edate=2023-01-21-
00-00-00
CSV:
/api/historicdata.csv?id=objectid&avg=0&sdate=2023-01-20-00-00-00&edate=2023-01-21-
00-00-00
JavaScript Object Notation (JSON):

/api/historicdata.json?id=objectid&avg=0&sdate=2023-01-20-00-00-00&edate=2023-01-
21-00-00-00&usecaption=1
You must supply the object ID of a sensor as well as a start date/time sdate and end date/time
edate.
3132
If you use the JSON call, additionally provide the parameter usecaption=1 to get more information
than just the raw data table.
API Call for Historic Graphs

Historic graphs are also available (in the PNG format):
Example
PNG:
/chart.png?id=objectid&avg=15&sdate=2023-01-20-00-00-00&edate=2023-01-21-00-00-
00&width=850&height=270&graphstyling=baseFontSize='12'%20showLegend='1'&graphid=-1
Common Parameters for Historic Data API Calls

You can use the following parameters for the graphs and the data tables:
id ID of the specific sensor integer
sdate Start of the time span (date and time) yyyy-mm-dd-hh-mm-ss
edate End of the time span (date and time) yyyy-mm-dd-hh-mm-ss
avg Average interval in seconds; use 0 to integer

download raw data (= results of all single
monitoring requests)
width/height Width and height of the graph in pixels integer
graphstyling baseFontSize='x' sets the size of the font baseFontSize='x'%

showLegend='x' enables (1) or disables 20showLegend='x'
(0) the graph legend
Historic Data Query Builder

You can also use the historic data reports 188 to manually generate and analyze historic sensor data via
the PRTG web interface.
More
KNOWLEDGE BASE
How can I export historic data from the PRTG API?
3133
How can I export raw sensor data automatically from PRTG?

3134
14.2.5 Object Manipulation
You can use the following functions to manipulate objects (URLs are shown without user name or
passhash to enhance readability).
In this section:
§ Changing Object Settings 3135
§ Supported Object Types for rename.htm 3136
§ Switch Inheritance Off/On 3136
§ Changing Properties of Channels 3136
§ Pausing/Resuming 3137
§ Supported Object Types for pause.htm 3137
§ Error Handling 3138
§ Rescanning, Triggering Auto-Discovery 3138
§ Reordering Objects in the Sensor Tree 3138
§ Report-related 3138
§ Notification-related 3139
§ Adding/Deleting Objects 3139
§ Supported Object Types for duplicateobject.htm 3139
§ Duplicating Sensors and Changing Clone Settings 3140
§ Setting Geo Location 3141
Changing Object Settings

Examples
Rename an object:
/api/rename.htm?id=objectid&value=newname
Set priority of an object (valid values for x are 1 to 5):

/api/setpriority.htm?id=objectid&prio=x
Change properties of objects:

/api/setobjectproperty.htm?id=id_of_object&name=property_name&value=new_value
This function can change most string and number properties of objects (names, numeric values,
object identifiers (OID), etc.). Use it with caution. You can discern the property_name parameter
by opening the Settings page of an object and looking at the HTML source of the INPUT fields. For
example, the INPUT field for the tags of an object has the name tags_. Leave away the underscore _
and use tags as a value for the property_name parameter.
3135
Supported Object Types for rename.htm
rename.htm supports the following object types:
§ group
§ device
§ sensor
§ map
§ report
§ library
§ notification template
§ schedule
§ user
§ user group
rename.htm does not support other object types.
Switch Inheritance Off/On

This API call sets the inherit setting of objects (location, credentials, compatibility options, proxy
settings, scanning interval, access rights, channel unit). In general, this works like changing properties
for any other object.
Example
Replace the parameter inheritType with the name of the inheritance type:
/api/setobjectproperty.htm?id=id_of_object&name=inheritType_&value=0_or_1
This internal name must be followed by an underscore (_), in contrast to changing properties
above. Use the value 0 for switching off inheritance, and 1 for switching on inheritance. For
example, the inheritance type for the scanning interval setting has the name intervalgroup_. Thus, this
specific part in the URL is &name=intervalgroup_&value=0 (switches off inheritance for scanning
interval).
This call does not work with the Schedules, Dependencies, and Maintenance Window settings.
Changing Properties of Channels

With this API call, you can change a sensor's channel settings 2692 . In general, this works like changing
properties of any other object. To set channel properties via the PRTG API, you need to provide
§ the ID of a sensor (parameter id),
§ a subtype (channel for channels), and
§ a subid (ID of the channel that you want to edit).
3136
Example: Enabling and Setting Limits for Channels
Set limits for channels:

/api/setobjectproperty.htm?
id=sensorid&subtype=channel&subid=0&name=limitmaxerror&value=limitvalue
You must set the limits for a channel before you can enable limits.
Enable limits for channels:
id=sensorid&subtype=channel&subid=0&name=limitmode&value=1
For example, the following API call sets the upper error limit of a channel with the ID 0 of a sensor
with the ID 2970 to the value 25.
id=2970&subtype=channel&subid=0&name=limitmaxerror&value=25
For Toplists, you can use the subtype toplist to change the properties. When using this subtype,
subid is the ID of a Toplist.
For a list of available channel parameters, see section Single Object Property 3101 .
Pausing/Resuming
Examples
Pause a sensor or object indefinitely:

/api/pause.htm?id=objectid&pausemsg=yourmessage&action=0
Pause a sensor or object for x minutes:

/api/pauseobjectfor.htm?id=objectid&pausemsg=yourmessage&duration=x
The pause message is optional. You can leave out the parameter &pausemsg=yourmessage if
you do not want to display a message.
Simulate an error for a sensor:
/api/simulate.htm?id=objectid&action=1
simulate.htm only works for sensors in the Up, Warning, Unusual, or Unknown status 184 .
Resume monitoring of a sensor or object:
/api/pause.htm?id=objectid&action=1
Supported Object Types for pause.htm

pause.htm supports the following object types:
§ probe
§ group
3137
§ device
§ sensor
§ notification
§ user account
pause.htm does not support other object types.
Error Handling (Acknowledge Alarm)
Example
Acknowledge the Down status:

/api/acknowledgealarm.htm?id=objectid&ackmsg=yourmessage
Rescanning, Triggering Auto-Discovery
Examples
Scan a sensor now:

/api/scannow.htm?id=objectid
Run an auto-discovery for a group or device:

/api/discovernow.htm?id=objectid&template=filename
Providing a device template 2735 for auto-discovery is optional. You can leave out the parameter
&template=filename to run the auto-discovery with the options defined in the object's settings. If
you use a template, provide the whole file name including file extension surrounded by double
quotation marks (") and encode whitespaces, if necessary. Example: &template="Linux%
20SNMP.odt"
discovernow.htm overrides the Auto-Discovery setting of the target group or device. If it is set to
No auto-discovery, it automatically changes to Standard auto-discovery (default).
Reordering Objects in the Sensor Tree
Example
Move an object in the sensor tree (x can be up, down, top, bottom):
/api/setposition.htm?id=objectid&newpos=x
Report-related
Example
3138
Add a group, device, or sensor to a report:
/api/reportaddsensor.htm?id=reportid&addid=objectid
Notification-related
Example
Trigger a notification immediately for testing purposes:

/api/noti

Prt g Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Prt g Manual

Uploaded by

Copyright:

Available Formats

PRTG Manual

Printed: May 2024 in Nuremberg

Part 1 Welcome to PRTG ......................................................................................................... 13

1.1 About this Document ..................................................................................................... 16

2.1 Step 1: Download, Installation, and First Login ................................................................. 40

3.1 Create a PRTG Hosted Monitor Instance ......................................................................... 51

4.1 Download PRTG ............................................................................................................ 94

5.1 Architecture and User Interfaces ................................................................................... 127

6.1 Login .......................................................................................................................... 157

7.1 Auto-Discovery ............................................................................................................ 270

8.1 Toplists ..................................................................................................................... 2718

Part 10 PRTG Apps for Mobile Network Monitoring .................................................................... 2997

Part 11 Desktop Notifications .................................................................................................. 3002

Part 12 Sensor Technologies ................................................................................................... 3005

12.1 Monitoring via SNMP .................................................................................................. 3007

14.1 Active Directory Integration ......................................................................................... 3091

15.1 Abbreviations ............................................................................................................. 3226

A Standard Installation of PRTG

Why Network Monitoring is Important

1. Set up a well-planned network with reliable components.

§ Plan monitoring results

§ Achieve the best monitoring results

§ Use a cluster for fail-safe monitoring

§ Set up devices, sensors, dependencies, and much more

§ To use PRTG right away, see section Quick Start Guide 39 .

PRTG can monitor:

§ Uptimes, downtimes, and slow servers

§ System health of hardware devices

§ Network devices and bandwidth

§ Service level agreements (SLA)

§ Database performance and table values

§ Physical network environments

§ Classify network traffic and content by source or destination

§ Measure Quality of Service (QoS) and Voice over IP (VoIP) parameters

§ Collect system information for hardware

§ Detect unusual behavior by devices or users

§ Assess the real usage of network and hardware

§ Fail-safe monitor a cluster

§ Customizable alerts for specific needs:

§ Network analysis modules to automatically find network devices and sensors.

§ Distributed monitoring to monitor several networks in different locations.

What security features does PRTG include?

PRTG Network Monitor has three release channels:

Release notes for the "stable" release channel

PRTG version history

Trial edition The trial edition is intended for evaluation purposes:

§ Supports all available sensors.

PRTG Hosted Monitor provides a 10-day trial. Afterward, your

Each PRTG Network Monitor license includes one single failover

§ Free for personal and commercial use.

§ Allows you to use up to 100 sensors.

§ Supports all available sensors.

The freeware edition is not available in PRTG Hosted Monitor.

Each PRTG Network Monitor license includes one single failover

Download PRTG and get a trial license key

§ Basic System Requirements 23

ú Requirements for the PRTG Core Server 23

ú Requirements for Remote Probes 24

ú General Performance Impact Considerations 25

ú Running PRTG in Virtual Environments 26

ú Running PRTG in a Cluster 27

ú Large PRTG Installations 27

§ Detailed System Requirements 27

ú Hardware and Network Size Requirements for Classic Remote Probes 29