PRT G Manual

PRTG Manual
© 2022 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: August 2022 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 ................................................................................. 33
Part 2 Quick Start Guide .......................................................................................................... 42
2.1 Step 1: Download, Installation, and First Login ................................................................. 44

2.2 Step 2: Smart Setup ...................................................................................................... 47
Part 3 Using PRTG Hosted Monitor ........................................................................................... 54
3.1 Create a PRTG Hosted Monitor Instance ......................................................................... 56

3.2 Manage a PRTG Hosted Monitor Subscription ................................................................. 70
3.3 Use Multi-Factor Authentication with PRTG Hosted Monitor .............................................. 84
Part 4 Installing the Software ..................................................................................................... 94
4.1 Download PRTG ............................................................................................................ 96

4.2 Update From Previous Versions ...................................................................................... 97
4.3 Install a PRTG Core Server ........................................................................................... 103
4.4 Install a Cluster ........................................................................................................... 110
4.5 Enter a License Key .................................................................................................... 111
4.6 Activate the Product .................................................................................................... 113
4.7 Install a Remote Probe ................................................................................................. 115
4.8 Uninstall PRTG Products ............................................................................................. 128
Part 5 Understanding Basic Concepts ...................................................................................... 131
5.1 Architecture and User Interfaces ................................................................................... 133

5.2 Failover Cluster ........................................................................................................... 137
5.3 Object Hierarchy ......................................................................................................... 140
5.4 Inheritance of Settings ................................................................................................. 144
5.5 Tags ........................................................................................................................... 146
5.6 Dependencies ............................................................................................................. 148
5.7 Scheduling .................................................................................................................. 149
5.8 Notifying ..................................................................................................................... 150
5.9 Access Rights Management ......................................................................................... 153
5.10 Data Reporting ............................................................................................................ 157
5.11 IPv6 Support ............................................................................................................... 158
Part 6 Basic Procedures ......................................................................................................... 159
6.1 Login .......................................................................................................................... 161

6.2 Welcome Page ........................................................................................................... 165
6.2.1 Customer Service .................................................................................................. 170
3
6.3 General Layout ............................................................................................................ 173
6.4 Sensor States ............................................................................................................. 186
6.5 Historic Data Reports ................................................................................................... 189
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 ........................................................................................................................... 214
6.12 Tickets ....................................................................................................................... 217
6.13 Working with Table Lists .............................................................................................. 222
6.14 Object Selector ........................................................................................................... 225
6.15 Priority and Favorites ................................................................................................... 227
6.16 Pause ........................................................................................................................ 230
6.17 Context Menus ............................................................................................................ 232
6.18 Hover Popup ............................................................................................................... 250
6.19 Main Menu Structure ................................................................................................... 252
Part 7 Device and Sensor Setup .............................................................................................. 267
7.1 Auto-Discovery ............................................................................................................ 269

7.2 Create Objects Manually .............................................................................................. 272
7.2.1 Add an Auto-Discovery Group ................................................................................. 273
7.2.2 Add a Group ......................................................................................................... 316
7.2.3 Add a Device ........................................................................................................ 351
7.2.4 Add a Sensor ........................................................................................................ 391
7.3 Manage Device Tree .................................................................................................... 394
7.4 Root Group Settings .................................................................................................... 396
7.5 Probe Settings ............................................................................................................ 426
7.6 Group Settings ............................................................................................................ 479
7.7 Device Settings ........................................................................................................... 535
7.8 Sensor Settings .......................................................................................................... 586
7.8.1 Active Directory Replication Errors Sensor ............................................................... 587
7.8.2 ADO SQL v2 Sensor .............................................................................................. 595
7.8.3 AWS Alarm v2 Sensor ........................................................................................... 610
7.8.4 AWS Cost Sensor ................................................................................................. 618
7.8.5 AWS EBS v2 Sensor ............................................................................................. 627
7.8.6 AWS EC2 v2 Sensor ............................................................................................. 636
7.8.7 AWS ELB v2 Sensor ............................................................................................. 646
7.8.8 AWS RDS v2 Sensor ............................................................................................. 656
7.8.9 Beckhoff IPC System Health Sensor ....................................................................... 666
7.8.10 Business Process Sensor ...................................................................................... 672
7.8.11 Cisco IP SLA Sensor ............................................................................................. 682
7.8.12 Cisco Meraki License Sensor (BETA) ..................................................................... 690
7.8.13 Cisco Meraki Network Health Sensor (BETA) ........................................................... 698
7.8.14 Citrix XenServer Host Sensor .................................................................................. 707
7.8.15 Citrix XenServer Virtual Machine Sensor .................................................................. 714
7.8.16 Cloud HTTP v2 Sensor ........................................................................................... 721
7.8.17 Cloud Ping v2 Sensor ............................................................................................ 731
7.8.18 Cluster Health Sensor ............................................................................................ 740
7.8.19 Common SaaS Sensor .......................................................................................... 745
7.8.20 Core Health Sensor ............................................................................................... 751
7.8.21 Core Health (Autonomous) Sensor .......................................................................... 758
4
7.8.22 Dell EMC Unity Enclosure Health v2 Sensor ............................................................ 765
7.8.23 Dell EMC Unity File System v2 Sensor ................................................................... 773
7.8.24 Dell EMC Unity Storage Capacity v2 Sensor ............................................................ 780
7.8.25 Dell EMC Unity Storage LUN v2 Sensor .................................................................. 787
7.8.26 Dell EMC Unity Storage Pool v2 Sensor .................................................................. 795
7.8.27 Dell EMC Unity VMware Datastore v2 Sensor .......................................................... 803
7.8.28 Dell PowerVault MDi Logical Disk Sensor ................................................................ 811
7.8.29 Dell PowerVault MDi Physical Disk Sensor ............................................................. 818
7.8.30 DHCP Sensor ....................................................................................................... 826
7.8.31 DICOM Bandwidth Sensor ...................................................................................... 834
7.8.32 DICOM C-ECHO Sensor ........................................................................................ 841
7.8.33 DICOM Query/Retrieve Sensor ............................................................................... 848
7.8.34 DNS v2 Sensor ..................................................................................................... 856
7.8.35 Docker Container Status Sensor ............................................................................. 865
7.8.36 Enterprise Virtual Array Sensor .............................................................................. 874
7.8.37 Event Log (Windows API) Sensor ........................................................................... 882
7.8.38 Exchange Backup (PowerShell) Sensor .................................................................. 892
7.8.39 Exchange Database (PowerShell) Sensor ................................................................ 900
7.8.40 Exchange Database DAG (PowerShell) Sensor ........................................................ 909
7.8.41 Exchange Mail Queue (PowerShell) Sensor ............................................................. 918
7.8.42 Exchange Mailbox (PowerShell) Sensor .................................................................. 926
7.8.43 Exchange Public Folder (PowerShell) Sensor .......................................................... 933
7.8.44 EXE/Script Sensor ................................................................................................ 941
7.8.45 EXE/Script Advanced Sensor ................................................................................. 951
7.8.46 File Sensor ........................................................................................................... 961
7.8.47 File Content Sensor ............................................................................................... 969
7.8.48 Folder Sensor ....................................................................................................... 978
7.8.49 FortiGate System Statistics Sensor (BETA) ............................................................ 987
7.8.50 FortiGate VPN Overview Sensor (BETA) .................................................................. 994
7.8.51 FTP Sensor ........................................................................................................ 1001
7.8.52 FTP Server File Count Sensor ............................................................................... 1008
7.8.53 HL7 Sensor ......................................................................................................... 1017
7.8.54 HPE 3PAR Common Provisioning Group Sensor .................................................... 1025
7.8.55 HPE 3PAR Drive Enclosure Sensor ....................................................................... 1033
7.8.56 HPE 3PAR Virtual Volume Sensor ........................................................................ 1041
7.8.57 HTTP Sensor ...................................................................................................... 1049
7.8.58 HTTP Advanced Sensor ....................................................................................... 1057
7.8.59 HTTP Apache ModStatus PerfStats Sensor ........................................................... 1072
7.8.60 HTTP Apache ModStatus Totals Sensor ................................................................ 1080
7.8.61 HTTP Content Sensor .......................................................................................... 1088
7.8.62 HTTP Data Advanced Sensor ................................................................................ 1097
7.8.63 HTTP Full Web Page Sensor ................................................................................ 1108
7.8.64 HTTP IoT Push Data Advanced Sensor .................................................................. 1117
7.8.65 HTTP Push Count Sensor .................................................................................... 1126
7.8.66 HTTP Push Data Sensor ...................................................................................... 1134
7.8.67 HTTP Push Data Advanced Sensor ....................................................................... 1143
7.8.68 HTTP Transaction Sensor ..................................................................................... 1152
7.8.69 HTTP XML/REST Value Sensor ............................................................................ 1164
7.8.70 Hyper-V Cluster Shared Volume Disk Free Sensor ................................................. 1176
7.8.71 Hyper-V Host Server Sensor ................................................................................. 1184
7.8.72 Hyper-V Virtual Machine Sensor ........................................................................... 1191
7.8.73 Hyper-V Virtual Network Adapter Sensor ............................................................... 1199
7.8.74 Hyper-V Virtual Storage Device Sensor .................................................................. 1207
7.8.75 IMAP Sensor ...................................................................................................... 1214
7.8.76 IP on DNS Blacklist Sensor .................................................................................. 1228
5
7.8.77 IPFIX Sensor ....................................................................................................... 1235
7.8.78 IPFIX (Custom) Sensor ......................................................................................... 1248
7.8.79 IPMI System Health Sensor ................................................................................. 1259
7.8.80 jFlow v5 Sensor ................................................................................................... 1268
7.8.81 jFlow v5 (Custom) Sensor ..................................................................................... 1281
7.8.82 LDAP Sensor ...................................................................................................... 1292
7.8.83 Local Folder Sensor (BETA) ................................................................................. 1298
7.8.84 Microsoft 365 Mailbox Sensor (BETA) ................................................................... 1306
7.8.85 Microsoft 365 Service Status Sensor ..................................................................... 1317
7.8.86 Microsoft 365 Service Status Advanced Sensor ...................................................... 1324
7.8.87 Microsoft Azure SQL Database Sensor ................................................................. 1332
7.8.88 Microsoft Azure Storage Account Sensor .............................................................. 1341
7.8.89 Microsoft Azure Subscription Cost Sensor ............................................................. 1349
7.8.90 Microsoft Azure Virtual Machine Sensor ................................................................ 1358
7.8.91 Microsoft SQL v2 Sensor ...................................................................................... 1367
7.8.92 Modbus RTU Custom Sensor ............................................................................... 1382
7.8.93 Modbus TCP Custom Sensor ............................................................................... 1394
7.8.94 MQTT Round Trip Sensor ..................................................................................... 1404
7.8.95 MQTT Statistics Sensor ....................................................................................... 1411
7.8.96 MQTT Subscribe Custom Sensor .......................................................................... 1417
7.8.97 MySQL v2 Sensor ............................................................................................... 1425
7.8.98 NetApp Aggregate Sensor .................................................................................... 1440
7.8.99 NetApp I/O Sensor .............................................................................................. 1450
7.8.100 NetApp LIF Sensor .............................................................................................. 1461
7.8.101 NetApp LUN Sensor ............................................................................................ 1471
7.8.102 NetApp NIC Sensor ............................................................................................. 1482
7.8.103 NetApp Physical Disk Sensor ............................................................................... 1492
7.8.104 NetApp SnapMirror Sensor ................................................................................... 1502
7.8.105 NetApp System Health Sensor ............................................................................. 1513
7.8.106 NetApp System Health v2 Sensor (BETA) .............................................................. 1525
7.8.107 NetApp Volume Sensor ........................................................................................ 1533
7.8.108 NetApp Volume v2 Sensor (BETA) ........................................................................ 1546
7.8.109 NetFlow v5 Sensor ............................................................................................... 1555
7.8.110 NetFlow v5 (Custom) Sensor ................................................................................ 1568
7.8.111 NetFlow v9 Sensor ............................................................................................... 1579
7.8.112 NetFlow v9 (Custom) Sensor ................................................................................ 1592
7.8.113 Network Share Sensor (BETA) .............................................................................. 1604
7.8.114 OPC UA Certificate Sensor .................................................................................. 1613
7.8.115 OPC UA Custom Sensor ...................................................................................... 1619
7.8.116 OPC UA Server Status Sensor ............................................................................. 1627
7.8.117 Oracle SQL v2 Sensor ......................................................................................... 1634
7.8.118 Oracle Tablespace Sensor ................................................................................... 1649
7.8.119 Packet Sniffer Sensor .......................................................................................... 1658
7.8.120 Packet Sniffer (Custom) Sensor ............................................................................ 1669
7.8.121 PerfCounter Custom Sensor ................................................................................. 1679
7.8.122 PerfCounter IIS Application Pool Sensor ................................................................ 1686
7.8.123 Ping Sensor ........................................................................................................ 1693
7.8.124 Ping Jitter Sensor ................................................................................................ 1700
7.8.125 POP3 Sensor ...................................................................................................... 1706
7.8.126 Port Sensor ........................................................................................................ 1713
7.8.127 Port Range Sensor .............................................................................................. 1721
7.8.128 PostgreSQL Sensor ............................................................................................. 1728
7.8.129 Probe Health Sensor ............................................................................................ 1742
7.8.130 Python Script Advanced Sensor ............................................................................ 1749
7.8.131 QoS (Quality of Service) One Way Sensor ............................................................. 1758
6
7.8.132 QoS (Quality of Service) Round Trip Sensor ........................................................... 1766
7.8.133 RADIUS v2 Sensor .............................................................................................. 1775
7.8.134 Redfish Power Supply Sensor ............................................................................... 1783
7.8.135 Redfish System Health Sensor ............................................................................. 1793
7.8.136 Redfish Virtual Disk Sensor (BETA) ...................................................................... 1804
7.8.137 RDP (Remote Desktop) Sensor ............................................................................ 1813
7.8.138 REST Custom Sensor .......................................................................................... 1819
7.8.139 REST Custom v2 Sensor (BETA) .......................................................................... 1842
7.8.140 Sensor Factory Sensor ........................................................................................ 1857
7.8.141 sFlow Sensor ...................................................................................................... 1871
7.8.142 sFlow (Custom) Sensor ........................................................................................ 1884
7.8.143 SFTP Secure File Transfer Protocol Sensor ........................................................... 1895
7.8.144 Share Disk Free Sensor ....................................................................................... 1902
7.8.145 SIP Options Ping Sensor ..................................................................................... 1908
7.8.146 SMTP Sensor ..................................................................................................... 1916
7.8.147 SMTP&IMAP Round Trip Sensor ........................................................................... 1924
7.8.148 SMTP&POP3 Round Trip Sensor .......................................................................... 1935
7.8.149 SNMP APC Hardware Sensor ............................................................................... 1946
7.8.150 SNMP Buffalo TS System Health Sensor ............................................................... 1953
7.8.151 SNMP Cisco ADSL Sensor .................................................................................. 1959
7.8.152 SNMP Cisco ASA VPN Connections Sensor ......................................................... 1965
7.8.153 SNMP Cisco ASA VPN Traffic Sensor ................................................................... 1971
7.8.154 SNMP Cisco ASA VPN Users Sensor ................................................................... 1978
7.8.155 SNMP Cisco CBQoS Sensor ................................................................................ 1984
7.8.156 SNMP Cisco System Health Sensor ..................................................................... 1991
7.8.157 SNMP Cisco UCS Blade Sensor ........................................................................... 1998
7.8.158 SNMP Cisco UCS Chassis Sensor ....................................................................... 2006
7.8.159 SNMP Cisco UCS Physical Disk Sensor ............................................................... 2014
7.8.160 SNMP Cisco UCS System Health Sensor ............................................................. 2021
7.8.161 SNMP CPU Load Sensor ..................................................................................... 2029
7.8.162 SNMP Custom Sensor ......................................................................................... 2035
7.8.163 SNMP Custom Advanced Sensor .......................................................................... 2042
7.8.164 SNMP Custom String Sensor ............................................................................... 2050
7.8.165 SNMP Custom String Lookup Sensor .................................................................... 2060
7.8.166 SNMP Custom Table Sensor ................................................................................ 2068
7.8.167 SNMP Dell EqualLogic Logical Disk Sensor ........................................................... 2077
7.8.168 SNMP Dell EqualLogic Member Health Sensor ...................................................... 2084
7.8.169 SNMP Dell EqualLogic Physical Disk Sensor ........................................................ 2092
7.8.170 SNMP Dell Hardware Sensor ................................................................................ 2101
7.8.171 SNMP Dell PowerEdge Physical Disk Sensor ........................................................ 2108
7.8.172 SNMP Dell PowerEdge System Health Sensor ...................................................... 2116
7.8.173 SNMP Disk Free Sensor ...................................................................................... 2125
7.8.174 SNMP Fujitsu System Health v2 Sensor ................................................................ 2132
7.8.175 SNMP Hardware Status Sensor ............................................................................ 2141
7.8.176 SNMP HP LaserJet Hardware Sensor .................................................................... 2147
7.8.177 SNMP HPE BladeSystem Blade Sensor ............................................................... 2153
7.8.178 SNMP HPE BladeSystem Enclosure System Health Sensor ................................... 2160
7.8.179 SNMP HPE ProLiant Logical Disk Sensor ............................................................. 2166
7.8.180 SNMP HPE ProLiant Memory Controller Sensor ..................................................... 2173
7.8.181 SNMP HPE ProLiant Network Interface Sensor ...................................................... 2181
7.8.182 SNMP HPE ProLiant Physical Disk Sensor ........................................................... 2189
7.8.183 SNMP HPE ProLiant System Health Sensor .......................................................... 2197
7.8.184 SNMP IBM System X Logical Disk Sensor ............................................................ 2205
7.8.185 SNMP IBM System X Physical Disk Sensor .......................................................... 2212
7.8.186 SNMP IBM System X Physical Memory Sensor ..................................................... 2219
7
7.8.187 SNMP IBM System X System Health Sensor ......................................................... 2226
7.8.188 SNMP interSeptor Pro Environment Sensor ........................................................... 2234
7.8.189 SNMP Juniper NS System Health Sensor .............................................................. 2240
7.8.190 SNMP LenovoEMC Physical Disk Sensor .............................................................. 2246
7.8.191 SNMP LenovoEMC System Health Sensor ............................................................ 2252
7.8.192 SNMP Library Sensor .......................................................................................... 2258
7.8.193 SNMP Linux Disk Free Sensor ............................................................................. 2269
7.8.194 SNMP Linux Load Average Sensor ........................................................................ 2278
7.8.195 SNMP Linux Meminfo Sensor ............................................................................... 2283
7.8.196 SNMP Linux Physical Disk Sensor ....................................................................... 2289
7.8.197 SNMP Memory Sensor ........................................................................................ 2296
7.8.198 SNMP NetApp Disk Free Sensor .......................................................................... 2303
7.8.199 SNMP NetApp Enclosure Sensor .......................................................................... 2310
7.8.200 SNMP NetApp I/O Sensor .................................................................................... 2318
7.8.201 SNMP NetApp License Sensor ............................................................................. 2324
7.8.202 SNMP NetApp Logical Unit Sensor ....................................................................... 2330
7.8.203 SNMP NetApp Network Interface Sensor ............................................................... 2337
7.8.204 SNMP NetApp System Health Sensor ................................................................... 2344
7.8.205 SNMP Nutanix Cluster Health Sensor ................................................................... 2350
7.8.206 SNMP Nutanix Hypervisor Sensor ......................................................................... 2357
7.8.207 SNMP Poseidon Environment Sensor .................................................................... 2364
7.8.208 SNMP Printer Sensor .......................................................................................... 2370
7.8.209 SNMP QNAP Logical Disk Sensor ........................................................................ 2376
7.8.210 SNMP QNAP Physical Disk Sensor ...................................................................... 2382
7.8.211 SNMP QNAP System Health Sensor .................................................................... 2389
7.8.212 SNMP Rittal CMC III Hardware Status Sensor ........................................................ 2395
7.8.213 SNMP RMON Sensor .......................................................................................... 2400
7.8.214 SNMP SonicWall System Health Sensor ............................................................... 2408
7.8.215 SNMP SonicWall VPN Traffic Sensor .................................................................... 2414
7.8.216 SNMP Synology Logical Disk Sensor .................................................................... 2422
7.8.217 SNMP Synology Physical Disk Sensor ................................................................. 2428
7.8.218 SNMP Synology System Health Sensor ................................................................ 2434
7.8.219 SNMP System Uptime Sensor ............................................................................. 2440
7.8.220 SNMP Traffic Sensor ........................................................................................... 2445
7.8.221 SNMP Trap Receiver Sensor ................................................................................ 2454
7.8.222 SNMP Windows Service Sensor ........................................................................... 2465
7.8.223 SNTP Sensor ...................................................................................................... 2471
7.8.224 Soffico Orchestra Channel Health Sensor .............................................................. 2476
7.8.225 SSH Disk Free Sensor ......................................................................................... 2484
7.8.226 SSH INodes Free Sensor ..................................................................................... 2496
7.8.227 SSH Load Average Sensor ................................................................................... 2504
7.8.228 SSH Meminfo Sensor .......................................................................................... 2512
7.8.229 SSH Remote Ping Sensor .................................................................................... 2520
7.8.230 SSH SAN Enclosure Sensor ................................................................................ 2528
7.8.231 SSH SAN Logical Disk Sensor ............................................................................. 2537
7.8.232 SSH SAN Physical Disk Sensor ........................................................................... 2546
7.8.233 SSH SAN System Health Sensor ......................................................................... 2556
7.8.234 SSH Script Sensor .............................................................................................. 2567
7.8.235 SSH Script Advanced Sensor ............................................................................... 2578
7.8.236 SSL Certificate Sensor ......................................................................................... 2588
7.8.237 SSL Security Check Sensor ................................................................................. 2598
7.8.238 Syslog Receiver Sensor ....................................................................................... 2605
7.8.239 System Health Sensor ......................................................................................... 2615
7.8.240 TFTP Sensor ....................................................................................................... 2620
7.8.241 Traceroute Hop Count Sensor ............................................................................... 2626
8
7.8.242 Veeam Backup Job Status Sensor ........................................................................ 2633
7.8.243 Veeam Backup Job Status Advanced Sensor ......................................................... 2640
7.8.244 VMware Datastore (SOAP) Sensor ....................................................................... 2648
7.8.245 VMware Host Hardware (WBEM) Sensor ............................................................... 2656
7.8.246 VMware Host Hardware Status (SOAP) Sensor ...................................................... 2663
7.8.247 VMware Host Performance (SOAP) Sensor ........................................................... 2671
7.8.248 VMware Virtual Machine (SOAP) Sensor ............................................................... 2679
7.8.249 Windows CPU Load Sensor ................................................................................. 2688
7.8.250 Windows IIS 6.0 SMTP Received Sensor ............................................................... 2696
7.8.251 Windows IIS 6.0 SMTP Sent Sensor ..................................................................... 2705
7.8.252 Windows IIS Application Sensor ........................................................................... 2714
7.8.253 Windows MSMQ Queue Length Sensor ................................................................. 2722
7.8.254 Windows Network Card Sensor ............................................................................. 2730
7.8.255 Windows Pagefile Sensor ..................................................................................... 2739
7.8.256 Windows Physical Disk I/O Sensor ....................................................................... 2746
7.8.257 Windows Print Queue Sensor ............................................................................... 2755
7.8.258 Windows Process Sensor .................................................................................... 2765
7.8.259 Windows System Uptime Sensor .......................................................................... 2773
7.8.260 Windows Updates Status (PowerShell) Sensor ...................................................... 2780
7.8.261 WMI Battery Sensor ............................................................................................ 2789
7.8.262 WMI Custom Sensor ........................................................................................... 2796
7.8.263 WMI Custom String Sensor .................................................................................. 2804
7.8.264 WMI Disk Health Sensor ...................................................................................... 2814
7.8.265 WMI Event Log Sensor ........................................................................................ 2821
7.8.266 WMI Exchange Server Sensor .............................................................................. 2831
7.8.267 WMI Exchange Transport Queue Sensor ............................................................... 2839
7.8.268 WMI File Sensor ................................................................................................. 2849
7.8.269 WMI Free Disk Space (Multi Disk) Sensor ............................................................. 2856
7.8.270 WMI HDD Health Sensor ...................................................................................... 2866
7.8.271 WMI Logical Disk I/O Sensor ................................................................................ 2875
7.8.272 WMI Memory Sensor ........................................................................................... 2883
7.8.273 WMI Microsoft SQL Server 2005 Sensor (Deprecated) ............................................ 2890
7.8.274 WMI Microsoft SQL Server 2008 Sensor ................................................................ 2899
7.8.280 WMI Remote Ping Sensor .................................................................................... 2953
7.8.281 WMI Security Center Sensor ................................................................................ 2960
7.8.282 WMI Service Sensor ............................................................................................ 2967
7.8.283 WMI Share Sensor .............................................................................................. 2974
7.8.284 WMI SharePoint Process Sensor .......................................................................... 2983
7.8.285 WMI Storage Pool Sensor .................................................................................... 2990
7.8.286 WMI Terminal Services (Windows 2008+) Sensor ................................................... 2997
7.8.287 WMI Terminal Services (Windows XP/Vista/2003) Sensor ....................................... 3003
7.8.288 WMI UTC Time Sensor ........................................................................................ 3009
7.8.289 WMI Vital System Data v2 Sensor ........................................................................ 3015
7.8.290 WMI Volume Sensor ............................................................................................ 3023
7.8.291 WSUS Statistics Sensor ...................................................................................... 3030
7.8.292 Zoom Service Status Sensor ................................................................................ 3038
7.9 Additional Sensor Types (Custom Sensors) ................................................................. 3047
7.10 Channel Settings ....................................................................................................... 3052
7.11 Notification Triggers Settings ...................................................................................... 3063
9
Part 8 Advanced Procedures ................................................................................................. 3075
8.1 Toplists ..................................................................................................................... 3077

8.2 Move Objects ............................................................................................................ 3082
8.3 Clone Object ............................................................................................................. 3084
8.4 Multi-Edit .................................................................................................................. 3088
8.5 Create Device Template .............................................................................................. 3093
8.6 Show Dependencies .................................................................................................. 3096
8.7 Geo Maps ................................................................................................................. 3099
8.8 Notifications .............................................................................................................. 3104
8.9 Libraries .................................................................................................................... 3107
8.9.1 Library Management ............................................................................................ 3110
8.9.2 Libraries and Node Settings .................................................................................. 3113
8.9.3 Library Context Menus ......................................................................................... 3120
8.10 Reports ..................................................................................................................... 3123
8.10.1 Run Reports ........................................................................................................ 3128
8.10.2 Report Settings ................................................................................................... 3133
8.11 Maps ........................................................................................................................ 3145
8.11.1 Map Designer ...................................................................................................... 3148
8.11.2 Maps Settings ..................................................................................................... 3159
8.11.3 Map Rotation ...................................................................................................... 3164
8.12 Setup ....................................................................................................................... 3166
8.12.1 Account Settings ................................................................................................. 3168
8.12.1.1 My Account ......................................................................................................................................... 3168
8.12.1.2 Notification Templates ......................................................................................................................... 3175
8.12.1.3 Notification Contacts ........................................................................................................................... 3209
8.12.1.4 Schedules ........................................................................................................................................... 3213
8.12.2 System Administration ......................................................................................... 3219
8.12.2.1 User Interface ..................................................................................................................................... 3219
8.12.2.2 Monitoring ............................................................................................................................................ 3233
8.12.2.3 Notification Delivery ............................................................................................................................. 3241
8.12.2.4 Core & Probes ..................................................................................................................................... 3250
8.12.2.5 User Accounts .................................................................................................................................... 3260
8.12.2.6 User Groups ........................................................................................................................................ 3270
8.12.2.7 Administrative Tools ............................................................................................................................ 3276
8.12.2.8 Cluster ................................................................................................................................................. 3280
8.12.2.9 Single Sign-On ..................................................................................................................................... 3282
8.12.2.10 Maintainer Mode .................................................................................................................................. 3288
8.12.3 PRTG Status ...................................................................................................... 3291
8.12.3.1 System Status ..................................................................................................................................... 3291
8.12.3.2 Cluster Status ...................................................................................................................................... 3315
8.12.4 License Information .............................................................................................. 3317
8.12.5 Auto-Update ........................................................................................................ 3323
8.12.6 Optional Downloads ............................................................................................. 3327
8.12.7 Help and Support Center ...................................................................................... 3329
8.12.8 Contact Support .................................................................................................. 3330
Part 9 PRTG Desktop ........................................................................................................... 3337
Part 10 PRTG Apps for Mobile Network Monitoring .................................................................... 3340
Part 11 Desktop Notifications .................................................................................................. 3343
Part 12 Sensor Technologies ................................................................................................... 3346
10
12.1 Monitoring via SNMP .................................................................................................. 3348
12.1.1 Choosing the Right SNMP Sensor ........................................................................ 3353
12.2 Monitoring via WMI .................................................................................................... 3360
12.3 Monitoring via SSH .................................................................................................... 3363
12.4 Monitoring Bandwidth via Packet Sniffing ..................................................................... 3365
12.5 Monitoring Bandwidth via Flows ................................................................................... 3367
12.6 Bandwidth Monitoring Comparison ............................................................................... 3370
12.7 Monitoring Quality of Service and VoIP ........................................................................ 3372
12.8 Monitoring Email Round Trip ....................................................................................... 3377
12.9 Monitoring Backups ................................................................................................... 3379
12.10 Monitoring Virtual Environments .................................................................................. 3380
12.11 Monitoring Databases ................................................................................................ 3386
12.12 Monitoring Syslogs and SNMP Traps .......................................................................... 3390
12.13 Monitoring via Push .................................................................................................... 3397
12.14 Monitoring via HTTP ................................................................................................... 3401
Part 13 PRTG Administration Tool ........................................................................................... 3406
13.1 PRTG Administration Tool on PRTG Core Server Systems ............................................ 3408
13.2 PRTG Administration Tool on Remote Probe Systems .................................................. 3432
Part 14 Advanced Topics ........................................................................................................ 3444
14.1 Active Directory Integration ......................................................................................... 3446

14.2 Application Programming Interface (API) Definition ........................................................ 3449
14.2.1 HTTP API ........................................................................................................... 3450
14.2.2 Live Data ............................................................................................................ 3453
14.2.2.1 Single Object Property ......................................................................................................................... 3454
14.2.2.2 Single Object Status ............................................................................................................................ 3457
14.2.2.3 Multiple Object Property or Status ....................................................................................................... 3464
14.2.2.4 System Information .............................................................................................................................. 3480
14.2.3 Live Graphs ......................................................................................................... 3483
14.2.4 Historic Data ....................................................................................................... 3486
14.2.5 Object Manipulation ............................................................................................. 3489
14.2.6 Custom Sensors ................................................................................................. 3496
14.2.7 Custom Notifications ............................................................................................ 3511
14.2.8 Mini Probe API .................................................................................................... 3513
14.3 Filter Rules for Flow, IPFIX, and Packet Sniffer Sensors ................................................ 3533
14.4 Channel Definitions for Flow, IPFIX, and Packet Sniffer Sensors ..................................... 3538
14.5 Define IP Address Ranges .......................................................................................... 3540
14.6 Define Lookups .......................................................................................................... 3541
14.7 Regular Expressions .................................................................................................. 3552
14.8 Calculating Percentiles ............................................................................................... 3554
14.9 Add Remote Probe .................................................................................................... 3555
14.9.1 Remote Probes and Multiple Probes ..................................................................... 3557
14.9.2 Remote Probe Setup via Device Tools ................................................................... 3561
14.10 Failover Cluster Configuration ...................................................................................... 3567
14.10.1 Failover Cluster Step by Step ............................................................................... 3572
14.11 Data Storage ............................................................................................................. 3579
14.12 Using Your Own SSL Certificate with the PRTG Web Server .......................................... 3583
Part 15 Appendix ................................................................................................................... 3585
15.1 Differences between PRTG Network Monitor and PRTG Hosted Monitor .......................... 3587
11
15.2 Glossary ................................................................................................................... 3605
15.3 Legal Notices ............................................................................................................ 3614
15.4 List of Abbreviations ................................................................................................... 3616
15.5 List of Available Sensor Types .................................................................................... 3626
15.6 List of Default Ports ................................................................................................... 3676
15.7 List of Icons .............................................................................................................. 3680
15.8 List of New Sensors ................................................................................................... 3681
15.9 List of Notification Triggers and Supported Sensors ....................................................... 3682
15.10 List of Placeholders for Notifications ............................................................................ 3704
15.11 List of Sensors by Performance Impact ........................................................................ 3713
15.12 List of Sensors in the Beta Status ............................................................................... 3727
15.13 List of Sensors with IPv4 Support Only ........................................................................ 3728
15.14 List of Sensors with Meta-Scan Functionality ............................................................... 3731
15.15 List of Sensors without Device Template Capability ....................................................... 3739
15.16 List of Standard Lookup Files ...................................................................................... 3742
15.17 List of Supported AWS Regions and their Codes .......................................................... 3756
15.18 Support and Troubleshooting ....................................................................................... 3758
12
Part 1
Welcome to PRTG
8/5/2022 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
ensure 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 may fail from time to time and may
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 (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 (as well as IPFIX, sFlow, and jFlow),
and many other industry standard protocols. It runs on a Windows-based machine in your network for 24
hours 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. It shows you how to:
§ 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 43 .
§ To learn more about monitoring with PRTG, see section Introduction: Monitoring with PRTG 33 .
§ For more detailed instructions, 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 3586 .
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 Applications
Monitoring w ith PRTG
PRTG can monitor:
§ Uptimes, downtimes, and slow servers
§ System health of hardware devices
§ Network devices and bandwidth
17
§ Applications
§ Virtual servers
§ service level agreement (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
PRTG 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.
§ 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.
18
§ 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 (private and public maps), 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 and to monitor
multiple sites or network segments from one central core installation. 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.
We provide three release channels for PRTG Network Monitor:
§ Stable: Best tested version for live systems. It is updated about once or twice a month. Use it on live
systems.
§ Preview: Offers the latest features and fixes and is updated several times a month. 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 Release notes for the "stable"
release channel on our website.
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 142 . Three different license editions are available.
Trial Edition
The Trial Edition is intended for evaluation purposes:
§ Monitors 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 137 that consists of two
cluster nodes. A cluster with two or three failover nodes requires an additional trial license key. A
cluster with four failover nodes requires two additional trial license keys.
After the trial period, the PRTG Network Monitor Trial Edition automatically turns into a Freeware Edition
that lets you monitor 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.
§ Monitors 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.
The Freeware Edition is not available in PRTG Hosted Monitor.
Commercial Editions
There are several licenses available that suit the demands of smaller as well as larger customers and
organizations:
§ Monitors a maximum number of sensors (consider our recommendations 28 ).

§ Each PRTG Network Monitor license includes one single failover cluster 137 that consists of two
cluster nodes. A cluster with two or three failover nodes requires an additional license of the same
size. A cluster with four failover nodes requires two additional licenses of the same size.
For more information about available commercial licenses, see the Paessler website: Pricing.
21
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 26
ú 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 Remote Probes 29
ú Performance Impact Considerations Based on Sensor Types 29
ú Supported Web Browsers 30
§ Further System Requirements 31
ú Screen Resolution 31
ú Requirements for Monitored Devices 31
ú Requirements for Smartphones and Tablets 32
§ More 32
Basic System Requirements

PRTG consists of two main system parts 133 , the PRTG core server and the 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 detailed information, see the hardware and network size requirements 28 for the PRTG
core server.
For installations of the PRTG core server 134 , 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, Microsoft Windows Server 2016, or Microsoft
Windows Server 2012 R2.
Microsoft .NET Microsoft .NET Framework .NET 4.7.2 or later must be installed on the
Framework PRTG core server system or the remote probe system. For new
installations of the PRTG core server or 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
(in order of performance and reliability):
§ Google Chrome 72
§ Mozilla Firefox 65
§ Microsoft Internet Explorer 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 detailed information, see the hardware and network size requirements 29 for remote
probes.
For installations of remote probes 3557 , 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, Microsoft
Windows Server 2012 R2, or Microsoft Windows 10.
24
.NET Framework 4.8.
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.
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.
Channels We recommend that you use sensors with less than 50 channels. Note
that sensors with more than 50 channels are not officially supported and
can 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.
25
Category Performance Impact Considerations
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 3145 ,

§ The frequent generation of huge reports 3123 ,
§ Heavy usage of packet sniffing 3365 , Sensor Factory sensors, and
Toplists 3077 ,
§ Frequent automatically scheduled auto-discoveries 269 for large network
segments, and
§ Constant queries of monitoring data via the PRTG API 3449 .
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.
Running PRTG in a Cluster

We recommend a single failover cluster 137 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.
26
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 Server 2012 R2*
§ Microsoft Windows 11
§ Microsoft Windows 8.1
§ Microsoft Windows Server 2008 R2*
* Windows servers in Core mode or Minimal Server Interface are not

officially supported.
Operating system version The version (32-bit or 64-bit) of the PRTG core server depends on the
version of your operating system.
27
.NET Framework 4.8.
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 space Concurrently Number of

PRTG core 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
Up to 10,000 10 - 12 16 GB 1,500 GB < 15 < 80
28
Sensors per CPU cores RAM Disk space Concurrently Number of
PRTG core active remote
server administrator probes
sessions
> 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 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 remote probe CPU cores RAM Disk space
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.
Performance Impact Considerations Based on Sensor Types

You can find the performance impact 3307 of a specific sensor on the Overview tab of the sensor or in the
Add Sensor 391 dialog.
For an overview list of sensors sorted by performance impact, see section List of Sensors by
Performance Impact 3713 .
In general, consider the following rules for the of 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.
29
Sensor Type Performance Impact Considerations
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.
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 Windows Server 2012 R2 or later, you can use more
VMware sensors. These limitations issue 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
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?
Microsoft Internet § Microsoft Internet Explorer 11 and older versions of Microsoft Edge, as
Explorer 11 and well as other browsers that are not officially supported, have issues with
unsupported browsers 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.
30
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.
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 3348 .
Windows/WMI monitoring To monitor via WMI, you need a Windows network. Use only the officially
supported operating systems 27 except for Microsoft Windows Server
2008 that has strong performance issues when you monitor via WMI.
For more information, see section Monitoring via WMI 3360 .
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 3367 .
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 3365 .
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.
31
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 3341 .
More
Knowledge Base
Which .NET version does PRTG require?


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/requirements
32
1.6 Introduction: Monitoring with PRTG
This section shows you how to prepare your IT infrastructure so that you can monitor it with PRTG. Learn
more about the following topics:
§ What PRTG Does 33
§ How to Monitor with PRTG 34
§ What PRTG Monitors 34
§ How to Prepare Monitoring 35
§ Which Hardware Do I Want to Monitor 35
§ Types of Logins and Credentials 36
§ Monitoring Technologies 36
§ Notifications from PRTG 40
To immediately start monitoring with PRTG, go to section Quick Start Guide 43 .
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 134 and one or more probes 134 :
§ The PRTG core server is responsible for configuration, data management, PRTG web server, and more.
§ Probes collect data and monitor processes on devices 142 via sensors 142 .
PRTG Architecture
Sensors are the building blocks of PRTG. A sensor can tell you about one or more aspects of a device:
§ Uptime
33
§ Load
§ Interface throughput
§ 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 (bandwidth monitoring), 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 Monitoring Technologies 36 .
What PRTG Monitors

PRTG comes with more than 250 different sensors 3626 .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 3660 to learn more about ready-to-use
custom sensors.
34
Areas of Applications w ith PRTG
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?
You can use the following sections as a basis for your monitoring plan.
Which Hardware Do I Want to Monitor?

We recommend that you start with your Business Critical Tier-1: the core network and other
infrastructure that all network devices depend upon. This usually includes:
§ Key infrastructure, such as core routers, switches, VPN and firewalls
35
§ 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:
§ Core infrastructure
a. Routers, switches, firewalls
b. Core network services: DNS, Active Directory (AD), LDAP servers

1. For your hardware devices, you need statistics on availability, usage, and performance.
2. 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)
Types of Logins and Credentials

Many of the sensors included in PRTG rely on access through logins to specific systems. You need
different credentials with sufficient permission for all of your devices, operating systems, and domains.
The configuration might also be different if you want PRTG to act as a Syslog or SNMP trap receiver or to
use it for flow-based monitoring.
In most cases, PRTG uses the following credential types to access the devices that you want to
monitor:
§ SNMP credentials
§ Windows credentials (WMI)
§ Linux, Solaris, and macOS credentials (SSH/Web-based Enterprise Management (WBEM))
§ VMware and XenServer credentials
§ Database management system (DBMS) credentials
§ Other credentials (for example, Amazon Web Services (AWS) keys, HTTP proxy)
Define your (administrative) credentials for all types of target devices that you want to monitor in the root
group of the device tree. Devices that you add to PRTG automatically inherit 144 these credentials, so
you usually do not need to reenter credentials.
Monitoring Technologies
This section briefly describes the most common monitoring technologies.
For more information, see section Sensor Technologies 3347 .
36
Monitoring with Simple Network Management Protocol (SNMP)
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.
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 3351 ) 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.
37
§ 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 3350 for more
information).
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 2454 .
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 396 ) 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 this Knowledge Base
article: My SNMP sensors don’t work. What can I do?
Monitoring via WMI
You can monitor Windows systems via Windows Management Instrumentation (WMI) and Windows
performance counters 3360 . 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 399 in PRTG. However, monitoring via WMI is not always trivial and can cause issues.
38
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.
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 3077 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 3365 for bandwidth monitoring if your hardware does not support any of
these xFlow versions.
Monitoring Passively Received Data
PRTG has the option to monitor passively received data. For this purpose, you can set up a device in a
way that it automatically sends data to PRTG. Specific sensors can receive this data and alert you
based on your individual settings. Usually, only the destination IP address and the port are required.
Examples for this monitoring technology are HTTP Push sensors 3397 , as well as Syslog Receiver 2605 and
SNMP Trap Receiver sensors 2454 .
For more information, watch this video tutorial: SNMP Trap receiver and syslog receiver sensors.
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.
39
Notifications from PRTG
PRTG can notify you in various ways 3182 if it detects that there is something wrong in your network. You
can individually define when (for example, based on sensor states 186 ) and how you want to receive
notifications. The most common methods are email, SMS text message, and push notifications to your
smartphone that runs the PRTG app for iOS or Android 3341 .
For your critical infrastructure, we recommend that you set up two redundant notifications with different
delivery methods (for example, email and SMS via a gateway).
For more information about notifications, watch this video tutorial: Notifications.
Email Notifications
The most common notification method is to send emails with the PRTG SMTP server. This means that
no SMTP server setup or configuration is required. However, if you want to deliver emails through your
email server, you must configure it in the SMTP settings 3242 .
SMS Notifications
PRTG Network Monitor can also notify you on your mobile phone. To deliver SMS notifications 3246 , select
one of the SMS service providers that PRTG includes by default and use it with your credentials for this
provider. Of course, you can also use any other service provider if you define a custom URL (search the
documentation of your provider for the required format). You can also use an SMS gateway to receive
messages even if your internet connection is down.
For a list of third-party tools, see the Knowledge Base: How can I send SMS text message
notifications via a modem or a mobile phone with PRTG?
Push Notifications
PRTG can send push notifications to your iOS and Android devices when you run the PRTG app on your
smartphone.
For more information, see the Knowledge Base: How can I use push notifications with PRTG?
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?
40
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
41
Part 2
Quick Start Guide
42 8/5/2022
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 47 and PRTG immediately starts to monitor your
network. You can adjust the setup to your needs later on.
43
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 56 .
Download PRTG
Download the latest stable version of PRTG from the Paessler website as a trial version 21 . Buy or
upgrade your license or renew your maintenance at the Paessler shop.
Dow nload PRTG
Once you have installed PRTG, the auto-update 3323 automatically downloads and installs new
software versions.
Install PRTG
Double-click the setup file on the system that you want to use as the PRTG core server. Follow the
installation wizard 103 and install the software.
At the end of the installation, open the PRTG web interface with one of the officially supported browsers:
§ Google Chrome 72,
§ Mozilla Firefox 65, or
§ Microsoft Internet Explorer 11.
44
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.
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 47 for more information about the initial configuration of PRTG. 47
More
VIDEO TUTORIAL
45
All video tutorials
§ https://www.paessler.com/support/videos-and-webinars/videos
46
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 173 . PRTG Network Monitor already includes
several devices 142 with sensors 142 that monitor your network, sorted into different groups 141 . PRTG
automatically creates the device tree during the installation process via the auto-discovery 269 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.
47
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 48
§ Step 2: Enter Location Information 50
§ Step 3: Change Your PRTG Login Password 50
§ Step 4: Confirm Your Email Address 51
§ Step 5: Switch to SSL/TLS 52 (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.
48
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 3360 .
§ 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 3363 .
§ 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 3380 .
§ 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 3348 .
§ 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 144 at
any level if you want to enter other credentials instead.
For more information about the available options, see section Root Group Settings 399 .
49
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 3099 . 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 398 .
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.
50
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 3169 .
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.
51
Verify Your Email Address
For more information about the available options, see section My Account 3168 .
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 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 3219 .
52
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 173 .
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
53
Part 3
Using PRTG Hosted Monitor
54 6/15/2022
3 Using PRTG Hosted Monitor
The following sections show you how to create a PRTG Hosted Monitor instance 56 , how to manage a
PRTG Hosted Monitor subscription 70 , and how to use multi-factor authentication 84 .
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-hosted-monitor/faq
55
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
web page.
We recommend that you use Google Chrome 72.
Start Your Free Trial Now
In this section:
§ Create a PRTG Hosted Monitor Instance 57
§ Smart Setup for PRTG Hosted Monitor 68
56
Create a PRTG Hosted Monitor Instance
1. On the PRTG Hosted Monitor web page, click Start 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 73 at any time.
Sign Up to PRTG Hosted Monitor
57
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 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
§ 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
58
4. Go to your inbox and open the email.
Verify Email Address
59
5. Click Verify Email Address to verify your email address and to go to the login screen.
Login Screen
60
6. Enter your credentials and click Log In to log in to PRTG Hosted Monitor.
Create New Subscription
61
7. Click Create New Subscription.
Subscription Setup
8. Select the region in which PRTG Hosted Monitor hosts your instance.
62
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
63
10. You see an overview of your order. Click Proceed To Checkout.
Account Details
64
11. Optionally enter your first name and last name and click Next.
Billing Address
65
12. Enter your billing information. Then click Next.
Account and Billing Details Overview
66
13. You see an overview of your account and billing details. Click Subscribe to finish.
Subscription Progress
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.
67
16. Enter your credentials on the login screen 60 .
Welcome
Your PRTG Hosted Monitor instance is now up and running. To open the device tree 173 , click View
Results, or click Devices in the main menu bar 252 .
PRTG Hosted Monitor automatically creates a hosted probe 134 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 3557 , which is required for monitoring your LAN. We strongly recommend that you do so.
68
Smart Setup: Install a Remote Probe
Click Install Remote Probe to start the installation.
For more information, see section Install a Remote Probe 115 .
For more information about other steps of the smart setup, see section Smart Setup 47 for PRTG
Network Monitor.
69
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 web portal. To manage your subscription, open a web browser, go
to the PRTG Hosted Monitor web portal, and log in.
Login Screen
70
Provide the credentials that 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.
In this section:
§ Subscription Overview 72
§ Manage Subscription 73
ú Change PRTG Subdomain 73
ú Change PRTG Timezone 74
ú Cancel Subscription 75
ú Change Subscription 75
§ Account Settings 76
ú Reset Password 77
ú Billing Details 78
ú Payment Details 79
§ Invoices 80
§ Upload 81
ú Upload Device Templates 81
ú Upload Custom Files 82
§ Logout 83
§ Upload 81
ú Upload Device Templates 81
ú Upload Custom Files 82
71
Subscription Overview
Subscription Overview
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.
72
Manage Subscription
Manage Subscription
Change PRTG Subdomain
Here you can change your subdomain. The domain name can be anywhere from 4 to 60 characters long.
73
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 3434 .
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.
Time Zone Options
74
Select a time zone from the dropdown list. You see the following message.
Time Zone Changed
Cancel Subscription
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
75
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 web 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 84 .
76
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.
77
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
78
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.
79
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.
80
Invoices
Upload
Here you can upload custom device templates 81 and custom files 82 .
Upload
Upload Device Templates
81
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
82
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.
83
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 84
§ Manually Enter the QR Code 89
§ Log In With Multi-Factor Authentication 89
§ Disable Multi-Factor Authentication 90
§ Use The Recovery Code 91
Initial Setup
To set up multi-factor authentication for your PRTG Hosted Monitor instance, open a web browser, go to
the PRTG Hosted Monitor web 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. Other users can
separately enable or disable it in their settings.
84
Account Overview
85
1. To enable multi-factor authentication, click .
If you enable multi-factor authentication for the first time, you must log in again.
Login Screen
86
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
87
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 89 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 web portal.
If you lose your recovery code, contact the Paessler support team 3330 .
88
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 web
portal, you see an additional login screen.
89
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 91 for more information.
Disable Multi-Factor Authentication

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

2. Click your account in the upper-right corner.
3. Click under Multi-Factor Authentication.
You see the following message.
90
Multi-Factor Authentication Now Disabled
The next time you log in to the PRTG Hosted Monitor web 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.
91
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.
92
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 web portal.
If you lose your recovery code, contact the Paessler support team 3330 .
More
Knowledge Base
Can I enable multi-factor authentication for my PRTG Hosted Monitor instance?

93
Part 4
Installing the Software
94 6/15/2022
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 56 to get started.
95
4.1 Download PRTG
Download the latest stable version of PRTG from the Paessler website as a trial version 21 . Buy or
upgrade your license or renew your maintenance at the Paessler shop.
Dow nload PRTG
Once you have installed PRTG, the auto-update 3323 automatically downloads and installs new
software versions.
96
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 97
§ Update from PRTG 16.1.22 or later 97
§ Update from PRTG 13.1.1 through 16.1.21 98
§ Removed Sensors as of PRTG 16.2.25 98
§ PRTG Web Interface Customizations as of PRTG 13.2.3 99
§ Update from PRTG 9 and 12 99
§ Update from PRTG 7 or 8 100
§ Update from Older PRTG Products 101
§ More 101
Update to PRTG 22.2.77

As of PRTG 22.2.77, PRTG is signed with renewed certificates. To seamlessly update to PRTG 22.2.77
or later, 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 (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 217 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 PRTG 16.1.22 or later, install 103 the newest version on top of the previous version. Your
configuration is kept. PRTG automatically updates remote probes 3557 as well. If you have configured
PRTG as a failover cluster 137 , 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.
97
We recommend that you use the auto-update 3323 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 version .NET 4.7.2 or later. For more
information, see the Knowledge Base: Which .NET version does PRTG require?
§ 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 27 .
§ 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. For more information, see the Knowledge Base: How can I re-brand and
customize the PRTG web interface using CSS and JavaScript?
§ PRTG 16.3.26: The Mobile Web GUI was removed from PRTG.
§ PRTG 16.2.25: Several sensors were removed from PRTG 98 .
Update from PRTG 13.1.1 through 16.1.21

As of PRTG 16.1.22, PRTG is signed with renewed certificates. To seamlessly update to PRTG 16.1.22
or later, an intermediate update is required for the PRTG core server and all probes if you run a version
previous to PRTG 16.1.21.1691/1692. If you auto-update from previous versions (lower than PRTG
16.1.21.1691/1692), PRTG automatically installs an intermediate version first. The intermediate version
you receive via auto-update or from the Paessler support team is PRTG 16.1.21.1924. You must perform
an additional auto-update to install the newest version. PRTG notifies you with a ticket 217 about this.
Your configuration is kept.
We recommend that you use the auto-update to install the newest PRTG version. If you update
manually with an installer downloaded from the Paessler online shop, the intermediate update is
only necessary if you run a version previous to PRTG 16.1.21.1691/1692 with one or more remote probes
or in a cluster. If you do not perform this intermediate update, you must update your remote probes and
cluster nodes manually. Contact the Paessler support team 3330 to get the installer for this version if you
do not use the auto-update.
§ As of PRTG 14, Internet Explorer 9 is no longer officially supported for access to the PRTG web
interface.
§ Also as of PRTG 14, PRTG core server and probes no longer officially support Windows XP and
Windows Server 2003 (including SP1 and SP2).
§ As of PRTG 15, Internet Explorer 10 is no longer officially supported for access to the PRTG web
interface.
Removed Sensors as of PRTG 16.2.25

We removed several sensors as of PRTG 16.2.25. Sensors of these types that you still use in your
PRTG installation stop monitoring and show the Down status as soon as you update to PRTG 16.2.25 or
later. Most of the affected sensors were deprecated in PRTG 16.2.23 or before. PRTG notifies you with a
ticket if your setup is affected.
98
The sensors concerned were used by very few users and/or created substantial load for both the
Paessler support team and development team. We therefore decided to focus on features that many
users use every day.
For a list of all discontinued sensors, possible alternatives, and more details about this approach,
see the Knowledge Base: Which sensor types will you remove from PRTG and what are the
alternatives?
PRTG Web Interface Customizations as of PRTG 13.2.3

As of PRTG 13.2.3, the website subfolder of the PRTG program directory is not used anymore. This
means that if you update from a version older than PRTG 13.2.3 to the newest version, all
customizations to the PRTG web interface are disabled and you must revise them. You might find a way
for a similar customization that you can add to the files in the webroot subfolder that now contains the
PRTG web interface files.
For more information, see the Knowledge Base: What about my web interface customizations as of
PRTG 13.2.3?.
Update from PRTG 9 and 12

We strongly recommend that you perform a clean install of the newest PRTG version instead of
updating from PRTG 9 or 12.
If you use PRTG 9 or 12 now, your configuration is kept when you install the newest PRTG version in
Standalone Mode or when you install a master node. However, there are a few things you should
consider.
We recommend that you always have a backup of your monitoring data.
§ Intermediate versions: You must install two intermediate versions before you can update to the newest
version.
ú If you run PRTG 12.4.5.3164/3165 or lower, install the intermediate version PRTG 12.4.7.3507 before
you proceed.
ú If you have installed version 12.4.7.3507, install the intermediate version PRTG 16.1.21 before you
proceed. Afterward, you can seamlessly update to the newest version. For details about this
intermediate update, see section Update from PRTG 13.1.1 through 16.1.21 98 .
ú We recommend that you use the auto-update. In this case, PRTG automatically installs the
intermediate versions. Run the auto-update three times if you come from a version previous to PRTG
12.4.7.3507, run it twice if you come from a version previous to PRTG 16.1.21.1691/1692. If you do
not use the auto-update, contact the Paessler support team 3330 to get the installers for these
intermediate versions.
· Discontinued sensors: Instances of the following sensors stop working as of PRTG 12 and must be
replaced with their successor sensors.
ú VMware Host Server (SOAP)
ú VMware Virtual Machine (SOAP)
99
ú Xen Virtual Machine
If your configuration contains these sensors, they stop monitoring after you update to the newest
version. We recommend that you pause them to keep their data. To continue monitoring, add the
sensors anew (for example, via the auto-discovery).
§ Install .NET 4.0: We strongly recommend that you install .NET 4.0 on every PRTG core server system
(and remote probe system). Otherwise, the following features do not work: VMware 3626 auto-discovery
and monitoring, Citrix XenServer 707 auto-discovery and monitoring, SIP Options Ping sensor 1908 ,
Windows Last Update sensor (deprecated as of PRTG 16.x.23).
§ Changed Geo Maps provider: When you update to the newest version, the provider for geographical
maps automatically switches from Google Maps to MapQuest (using Open Street Map data).
§ Windows 2000 not supported: As of PRTG 7, we do not officially support Windows 2000 systems
anymore. This means that you cannot install PRTG on systems that run Windows 2000, and you
cannot officially monitor Windows 2000 systems (for example, via WMI). However, if you were able to
successfully monitor your Windows 2000 systems with PRTG 9, this might actually not be possible
anymore with the newest version.
We recommend that you have a look at the system requirements 23 before you update. Officially
supported operating systems, browsers, and other requirements may have changed since PRTG 9.
Update from PRTG 7 or 8

We strongly recommend that you perform a clean install of the newest version instead of updating
from PRTG 7 or 8.
If you use PRTG 7 or 8 now, you must update PRTG to intermediate versions first to ensure all data is
transferred correctly. You cannot update to PRTG 15 or later directly from PRTG 7 or 8.
§ We recommend that you first update to the newest PRTG 8 version.
§ From the newest PRTG 8 version, update to PRTG version 9.
§ From PRTG 9, update to both intermediate versions 99 PRTG 12.4.7.3507 and 16.1.21.1691/1692,
then to the newest PRTG version.
Contact the Paessler support team 3758 to obtain download links for these versions. Always keep a proper
backup of your configuration and monitoring data.
Updating from PRTG 7 or 8 to Newest PRTG Version
§ Packet Sniffer (Content) sensors are not supported anymore. Sensors of this type automatically
switch to Packet Sniffer (Header) sensors after the update. As a benefit, you can now also sniff IPv6
traffic.
§ Internet Explorer 8 is no longer supported for access to the PRTG web interface.
§ You might experience a slow Enterprise Console (deprecated; former 'Windows GUI') because different
reasons.
§ When you install a failover node on top of a standalone PRTG 7, 8, 9, 12, or 13+ installation, the
configuration cannot be kept and is written to a backup folder. Afterward, the new configuration is
received from the master node. As all cluster nodes work with the same configuration, a failover node's
old configuration and monitoring data can no longer be used. If you want to keep a configuration of
PRTG 7, install the master node on top of the old installation and use other servers for the failover node
installations.
100
§ Since PRTG 9, SNMP sensors use the IPv4 outgoing IP set for the PRTG probe service (this setting
was formerly ignored by those sensors, which used the automatic setting instead). If you experience
sensors that fail, check the setting in the probe settings 474 .
§ If you (manually) configured the PRTG probe service or PRTG core server service to run under a
different Windows user account (for example, for successful internet access through an ISA server
firewall), apply the respective Windows user account for the PRTG probe service and/or PRTG core
server service again after you install the newest PRTG version.
§ For system requirements for the PRTG core server and probes, see section System Requirements 23 .
§ If you use the default data path in your PRTG setup, it is changed automatically. Up to PRTG 8, all
data was stored in a subfolder that reflected a PRTG version number (v7 or v8). As of PRTG 9, this
subfolder is omitted, and data is stored directly in %ALLUSERSPROFILE%\Application
data\Paessler\PRTG Network Monitor. During setup, all data is moved to the new directory. If you use
a custom data path, it is not changed.
§ Up to PRTG 8, all data in the registry was stored in a subkey that reflected a PRTG version number (v7
or v8). As of PRTG 9, this subkey is omitted and registry data is stored directly under the key
HKEY_LOCAL_MACHINE\SOFTWARE\Paessler\PRTG Network Monitor (on 32-bit systems),
respectively HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Paessler\PRTG Network Monitor
(on 64-bit systems). During setup, all registry values are moved to the new key.
We strongly recommend that you see the system requirements before you update to the newest
version. Officially supported operating systems, browsers, and other requirements may have
changed since PRTG 8.
Updating from PRTG 7 to Newest PRTG Version
§ Regarding custom sensors, the interpretation of returned values is handled more strictly as of PRTG 8.
If you use custom sensors with PRTG 7, these may not work with the newest PRTG version if they do
not fully apply to the API definition 3449 .
Update from Older PRTG Products

For all other previous products, a direct data import to the newest version is not possible.
If you use IPCheck 5 or PRTG Traffic Grapher 6, perform a clean installation of PRTG and set up your
configuration anew. Use the auto-discovery 269 to quickly configure monitoring of your entire network.
For more information, see section Quick Start Guide 43 .
More
Knowledge Base
How do I back up all data and configuration of my PRTG installation?


How can I re-brand and customize the PRTG web interface using CSS and JavaScript?
101
Which sensor types will you remove from PRTG and what are the alternatives?
What about my web interface customizations as of PRTG 13.2.3?

Updating from version 7, 8, 9, or 12? Read this important message!

Can I update from PRTG Traffic Grapher or IP Check 5 to the current PRTG version?
What does error code PE252 mean?

The signature of my PRTG server is not valid. What can I do?

I have issues with additional services after updating to PRTG 19.2.50. What can I do?
Why do I get an error message when trying to restart Windows Server 2019 after a PRTG update?
102
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
103
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
104
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 3579 , if necessary. Click Next.
Setup Dialog: Location for Installation and Data Storage
105
7. This page is only visible if you use the Custom installation mode. Select if you want to run an auto-
discovery 269 of your network or if you want to skip the auto-discovery. Click Next.
Setup Dialog: Run or Skip Auto-Discovery
8. This page is only visible if you select Run auto-discovery. You can enter an Simple Network
Management Protocol (SNMP) community string. The default SNMP community string is public.
Click Next.
Setup Dialog: Auto-Discovery Configuration
106
9. PRTG is installed on your computer.
Setup: Installing PRTG
10. Click Finish to complete the setup of PRTG.
After installation, you can open the PRTG web interface 160 in your system's default browser. Make sure
that Google Chrome 72, Mozilla Firefox 65, or Microsoft Internet Explorer 11 is available on the system.
For more information, see section System Requirements 30 .
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 trial installation, PRTG asks you for your License Key and License
Name. In this case, you are directed to our website.
Enter both License Key and License Name exactly as received from Paessler.
107
Setup Dialog: Enter License Information
For more information, see section Enter a License Key 111 .
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, for which you might be asked when you install PRTG or when you
change your license key 111 .
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
108
Terms and conditions of Paessler AG
§ https://www.paessler.com/company/terms
Privacy policy
§ https://www.paessler.com/company/terms
109
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) that each run 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 3567 .
More
Knowledge Base
What is the clustering feature in PRTG?

110
4.5 Enter a License Key
A license key for PRTG Network Monitor consists of the License Name and a License Key. The license
key is a string that consists of 10 blocks with six characters each.
Your License Information

You have received the License Name (PRTG Network Monitor only) and the License Key from Paessler
via email or in a license document in the Paessler Software Shop and Customer Service Portal. Copy
this information and paste it when PRTG asks you to enter your license information in the setup dialog.
You can find the label License Owner in some documents from the Paessler shop. License Owner is
the same as License Name, for which you might be asked when you install PRTG or when you
change your license key 111 .
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. For the Commercial Edition, use
your commercial license information.
License Information Example
License Name Example Organization

Paessler PRTG Enterprise Monitor subscription licenses
do not have a License Name.
License Key P10000-FFSEJ3-ZHGRD5-UR1CS9-U73FG2-G645F1-YVF1D0-

H83234
There are two license key types:
§ Trial Edition/Freeware Edition license key: With a Trial Edition license key, you can experience
unlimited functionality of PRTG during the 30-day trial period. Your installation automatically switches
to the Freeware Edition afterward.
For more information about how to get your free Trial Edition, see section Download PRTG 96 .
§ Commercial Edition license key: You can only enter this key if you have purchased the Commercial
Edition. Your installation allows the number of sensors according to your license 21 .
During the setup process for installing the Commercial Edition, PRTG asks you to enter your license
information. We recommend that you copy and paste your license data. If you install the Trial Edition,
you do not need to enter a license key.
Change License Key

Because PRTG already asks for a key during installation, you usually do not need to manually enter one
afterward. However, there are still scenarios where you need to change your key and activate the
respective license. For example, you must provide your Commercial Edition license key if you have
purchased the Commercial Edition and want to upgrade your Freeware Edition or Trial Edition, or if you
upgrade a Commercial Edition license to a higher edition.
111
1. To enter a new license key, log in to the PRTG web interface 133 .
2. Select Setup | License Information from the main menu bar 265 .
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 3322 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.
For more information, see section License Information 3320 .
The PRTG core server needs an internet connection on port 443 to activate. If a proxy connection is
needed, see step 3 3321 on the Update Your License page. If the activation fails, you can also try an
offline activation.
Update Your License: Click Change License Key
More
Knowledge Base
How do I upgrade to a higher edition of PRTG?

The automatic license activation of my PRTG Enterprise Monitor license does not work. What can I do?
112
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 key during installation, you usually do not need to manually enter one
afterward. However, there are still scenarios where you need to change your key and activate the
respective license. For example, you must provide your Commercial Edition license key if you have
purchased the Commercial Edition and want to upgrade your Freeware Edition or Trial Edition, or if you
upgrade a Commercial Edition license to a higher edition.
1. To enter a new license key, log in to the PRTG web interface 133 .
2. Select Setup | License Information from the main menu bar 265 .
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 3322 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 3321 on the Update Your License page. If the activation fails, you can also try an
offline activation.
Offline Activation
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.
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 3322 and step 4 3322 on the Update
Your License page.
113
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 after you renew your
maintenance. This ensures 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.?
114
4.7 Install a Remote Probe
Remote probes can extend your monitoring with PRTG.
§ With remote probes, you can monitor different subnetworks that are separated from your PRTG core
server by a firewall, and you can keep an eye on remote locations. You can install one or more remote
probes 3557 .
§ Remote probes are useful if you want to 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 remote probe if you want to monitor your local network with a PRTG Hosted Monitor
instance.
PRTG automatically updates remote probes but, in rare cases, you must manually update remote
probes. You receive a ToDo ticket 217 in this case. Follow the steps below 115 to manually update
remote probes.
If you run PRTG in a cluster, see Cluster and Remote Probes Outside the LAN 118 in this section.
If you have issues after the installation, see section Debugging Remote Probe Connection Issues 124
For a partially automatic installation of a remote probe directly from the device tree in the PRTG web
interface, see section Remote Probe Setup via Device Tools 3561 . 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 remote probe with the Remote Probe Installer, follow these steps:
§ Step 1: Meet the Requirements 115
§ Step 2: Prepare the PRTG Core Server 116 : start here if you use PRTG Network Monitor
§ Step 3: Download the Remote Probe Installer from the PRTG Web Interface 118 : start here if you use
PRTG Hosted Monitor
§ Step 4: Install a New Remote Probe 119
§ Step 5: Approve the New Remote Probe 122
Step 1: Meet the Requirements

To install a remote probe on a target system, make sure that you meet the following requirements.
§ The target system runs the operating system Windows 7 or later.
§ 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.
§ 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.
115
§ Because the probe initiates the connection, you must ensure 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
the probe to reach the PRTG core server via the Transmission Control Protocol (TCP) port 23560.
Then, the 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?
PRTG Network Monitor and PRTG Hosted Monitor already include a local probe or hosted probe on
the PRTG core server. This is why you cannot additionally install a remote probe on your PRTG core
server system.
For more information on the requirements for remote probes, see section System Requirements 24 .
Step 2: Prepare the PRTG Core Server

If you use PRTG Hosted Monitor, you can start with Step 3: Download the Remote Probe Installer from
the PRTG Web Interface 118 right away.
Because your remote probe needs 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 the remote probe.
Edit the relevant settings in section Core & Probes 3250 . From the main menu in the PRTG web
interface 133 , select Setup | System Administration | Core & Probes to access the probe settings and go
to the Probe Connection Settings.
116
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.
Other settings are not required. For details about the fields for Access Keys, Deny IP Addresses, and
Deny GIDs, see section Core & Probes 3252 .
When you are done, click Save to save your settings.
117
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, of PRTG Desktop 3338 , or of PRTG Apps
for Mobile Network Monitoring 3341 are disconnected and reconnected.
To edit the core–probe connection settings, you can also use the PRTG Administration Tool 3408 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 3280 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 3280 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 3569 , section Remote Probes in a Cluster.
Step 3: Download the Remote Probe Installer from the PRTG Web Interface
1. On the computer on which you want to install a remote probe, log in to the PRTG web interface.
2. From the main menu bar, select Setup | Optional Downloads | 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 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 Remote Probe Installer directly, you must install the remote probe without the assistant.
If you connect your remote probe to PRTG Network Monitor, prepare 116 your Probe Connection
Settings first.
118
Add Remote Probe Assistant
The PRTG version numbers of the PRTG core server service and PRTG probe service must match.
PRTG automatically updates remote probes when you install a new version on the PRTG core
server. If PRTG advises you to manually update your remote probe, open a web browser on the remote
computer and download the remote probe installer as described in this section.
Step 4: Install a New 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.
119
Remote Probe Setup Installing
Wait until the installation is complete. The remote probe then automatically connects to your PRTG core
server.
120
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 3252 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.
121
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.
122
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 269 . 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.
123
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 3251 . 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 ensure 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 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.
Debugging Remote Probe Connection Issues

If you have issues with the connection between the PRTG core server and remote probe, make sure that
you meet the following requirements:
§ Recheck if you fulfilled all the requirements as described in step 1 115 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 3251 .
§ You can also take a look at the log files of the 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:
124
11/6/2017 1:21:58 PM PRTG Probe V17.4.36.3253
11/6/2017 1:21:58 PM System time zone: (UTC+01:00) Amsterdam, Berlin, Bern, Rome,
Stockholm, Vienna
11/6/2017 1:21:58 PM libeay32.dll=1.0.2.11
11/6/2017 1:21:58 PM ssleay32.dll=1.0.2.11
11/6/2017 1:21:58 PM PRTG Probe "example-DNS" starting on "example-
DNS" (GID={AAAA1111-22BB-33CC-DD44-EEEEEE555555})
11/6/2017 1:21:58 PM Memory Manager: NexusMM4
11/6/2017 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/2017 1:21:58 PM Data Path: C:\ProgramData\Paessler\PRTG Network Monitor\
11/6/2017 1:21:58 PM System Path: C:\Program Files (x86)\PRTG Network Monitor\
11/6/2017 1:21:58 PM Local IP: 0.0.0.0
11/6/2017 1:21:58 PM Core Server IP: example-DNS.exampledomain.com
11/6/2017 1:21:58 PM Core Server Port: 23560
11/6/2017 1:21:58 PM SSL Enabled
11/6/2017 1:21:58 PM Probe GID: {AAAA1111-22BB-33CC-DD44-EEEEEE555555}
[...]
11/6/2017 1:21:58 PM Start Connection
11/6/2017 1:21:58 PM Start Done
11/6/2017 1:21:58 PM (14608):Initializing WMIConnectionPool
11/6/2017 1:21:58 PM (14608):WMIConnectionPool maximum number of concurrent
establishings is set to: 20
11/6/2017 1:22:03 PM Connect from to example-DNS.exampledomain.com:23560
11/6/2017 1:22:03 PM TCP connected from 10.49.12.51:55199 to example-
DNS.exampledomain.com:23560
11/6/2017 1:22:03 PM State changed to connected (example-DNS.exampledomain.com:23560)
11/6/2017 1:22:03 PM Reconnect
11/6/2017 1:22:04 PM Connected
11/6/2017 1:22:10 PM Send Login
11/6/2017 1:22:10 PM Local: 11/6/2017 1:22:10 PM UTC: 11/6/2017 12:22:10 PM
11/6/2017 1:22:10 PM MarkUnused
11/6/2017 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 116 ), you see:
11/6/2017 1:42:02 PM Try to connect...
11/6/2017 1:42:02 PM Connected to 10.0.2.167:23560
11/6/2017 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 3432 on the remote probe system.
125
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 3251 .
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 3432 .
126
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?
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
127
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.
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.
128
Step 5
Confirm a system restart with Yes.
129
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 3579 .
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 remote probe?

130
Part 5
Understanding Basic Concepts
6/15/2022 131
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.
132
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 134

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 134
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 Windows 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 Desktop 3338
PRTG Desktop is a cross-platform application that you can use as an
alternative interface for fast access to data and monitoring management.
With PRTG 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 3341
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 3408
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.
133
Category Components
PRTG Administration Tool on Remote Probe Systems 3432

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 137 , 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.
134
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.
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.
For more information, see section Add Remote Probe 3555 .
For more information, see the video tutorial: Distributed monitoring
with PRTG.
135
Probe Type Description
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.
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 3513 .
System Health Monitoring

PRTG automatically monitors the system health of the PRTG core server and of each probe to discover
overload situations that can distort monitoring results. To monitor the status of the probe system, PRTG
automatically creates the Core Health 751 and Probe Health 1742 sensor, the System Health 2615 sensor,
the Cluster Health 740 sensor, some disk free 2856 and bandwidth 2730 sensors for all installed network
cards, as well as a Common SaaS sensor 745 that checks the availability of widely used software as a
service (SaaS) providers.
We recommend that you keep these sensors. However, you can remove all of them except for the health
sensors.
The health sensors measure various internal system parameters of the probe system hardware and the
probe's internal processes and compute the results. Investigate frequent values below 100%.
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
What is a sensor?
§ https://www.paessler.com/support/videos-and-webinars/videos/what-is-a-sensor
136
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.
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.
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.
137
Feature Description
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 remote probes in a cluster 3569 , 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 474 .
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 26 . 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 3567 .
138
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
139
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 144 .
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 396 . This is because all other objects in
the device tree inherit 144 these standard settings by default so that you do not need to set up the same
configuration for each object anew.
140
Probe
Each group (except the root group) is part of a probe. 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 137 , 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
141
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 3237 .
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:
142
§ 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
143
5.4 Inheritance of Settings
The hierarchically structured 140 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 3063
§ Credentials for different systems
§ Compatibility settings for specific sensor types
§ Channel and unit configurations
§ User access rights 153
§ Tags 146
§ Paused status : If an object is paused by the user or by a schedule, PRTG sets all sensors on this
186
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.
144
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
§ 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 396 .
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 3063 .
145
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 272 , 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.
Use the multi-edit 3088 feature to simultaneously change tags for several objects.
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 144 by all other objects underneath in the object
hierarchy 140 . 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 3136 . PRTG
adds all sensors with the tag netflow to the report so that you do not need to manually tag every single
sensor.
146
You cannot disable the inheritance of tags.
Filter by Tags
You can use one or more tags to filter table lists 222 for specific objects, or to add sensors to libraries 3107
and reports 3123 .
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 256 . 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.
147
5.6 Dependencies
You can use dependencies to pause sensors based on the status 186 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 269 feature, PRTG sets the Ping sensor 1693 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 148 if you manually pause a master object or if
you pause it by schedule 149 . For more details, see the Knowledge Base: Why will dependent
objects not go into paused status automatically 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 253 . From there you can also access the dependencies graph 3096 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 go into paused status automatically when I pause the master object?
148
5.7 Scheduling
With schedules, you can automatically pause 230 specific objects for a specific time span, for example,
on Sundays between 16:00 and 20:00. A sensor in the Paused status 186 does not collect monitoring
data, does not change its status, and does not trigger any notifications 150 . 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 148 if you manually pause a master object or if
you pause it by schedule 149 . For more details, see the Knowledge Base: Why will dependent
objects not go into paused status automatically 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 3213 .
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 3567 .
More
Knowledge Base
149
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 186 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 3052 of a sensor.
PRTG triggers a sensor status 186 change when a sensor measures values that exceed or fall below a
defined limit. For example, you can set an SNMP CPU Load sensor 2029 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 3060 .
For more information, see the video tutorial: How to set channel limits.
150
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 3541 .
Notifications
PRTG can send a notification 3104 when it discovers, for example, downtime, an overloaded system,
threshold breaches, or similar situations. Notifications use various methods 3182 to notify you of issues.
After you create notification templates 3175 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 3063 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 3104 .
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 .
151
Logs
The logs list shows the logfile 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 214 .
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 217 .
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
152
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 153 for each object in the
device tree except channels, as well as for libraries, maps, and reports. Objects can also inherit 144
access rights according to the object hierarchy 140 .
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 (read-only user
or read/write user) in the user account settings.
For more information, see section User Accounts 3260 .
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).
153
The access rights apply to device tree objects and to libraries, maps, and reports.
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 3264 .
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.
154
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 object group
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
ú can also manage user accounts, user groups, and cluster setups
155
ú 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.
156
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 189 .
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 3123 .
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 3449 .
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 153 and section Maps 3145 .
157
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 535 . 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 3424 , 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
more information, see section List of Sensors with IPv4 Support Only 3728 .
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.
158
Part 6
Basic Procedures
6/15/2022 159
6 Basic Procedures
The following sections introduce the basic features and concepts of PRTG.
§ Login 161
§ Welcome Page 165
§ General Layout 173
§ Sensor States 186
§ Historic Data Reports 189
§ Similar Sensors 195
§ Recommended Sensors 200
§ Object Settings 204
§ Alarms 205
§ System Information 208
§ Logs 214
§ Tickets 217
§ Working with Table Lists 222
§ Object Selector 225
§ Priority and Favorites 227
§ Pause 230
§ Context Menus 232
§ Hover Popup 250
§ Main Menu Structure 252
160
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 3408 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 Knowledge Base: Why does my browser show an SSL certificate warning
when I open the PRTG web interface?
The PRTG web interface is your access to PRTG via a web browser. The PRTG web interface is based
on Asynchronous JavaScript and XML (AJAX). It uses a responsive design to adjust to the size of your
screen.
Use the PRTG web interface as the default interface to set up your monitoring. You can use it to
configure devices and sensors, to set up notifications, to review monitoring results, to create reports, and
to visualize your monitoring on dashboards.
While you are logged in 161 , the PRTG web interface continuously refreshes the data on the screen via
AJAX calls. This way, you are always up to date regarding your monitoring results. You can individually
set 3266 the refresh interval and method.
With the Single Page Application (SPA) technology, your system stays highly performant because only
single page elements are refreshed when necessary.
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 3260 with
administrative rights or users with more restricted user access rights (for example, read-only users).
161
Login Screen
Login as Predefined Administrator (First Time Login)

This only applies to PRTG Network Monitor, not to 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.
162
Login 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 72 or Mozilla
Firefox 65 for best performance.
Although you can log in with Microsoft Internet Explorer 11, the PRTG web interface might not be
fully compatible with Internet Explorer. If you use Microsoft Internet Explorer 11, set the security
level to Medium-high (or lower) and make sure that no Compatibility View is enabled.
§ Download apps for Windows, macOS, iOS, Android (optional): Opens Setup | Optional Downloads in
the PRTG web interface. You can optionally download 3327 the PRTG apps 3341 for iOS or Android or
PRTG Desktop 3338 .
If you use this download option, you require your login name and password (or the default
credentials) for login.
Only Google Chrome 72 and Mozilla Firefox 65 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 3282 , you see a new button on the login screen of the PRTG web interface.
163
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
Why does my browser show an SSL certificate warning when I open the PRTG web interface?
164
6.2 Welcome Page
After you completed the smart setup 47 , 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 3173 . Of course, you can also use the Maps 3145 feature to create customized dashboards that
you can use as your homepage.
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:
165
Sensor Overview on the Welcome Page
§ Click Sensors to open the top 10 lists 256 for sensors.

§ Click View All Alarms to open a list of alarms 205 in your installation.
§ Click a sensor status 186 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 173 that shows your monitoring results.
Install PRTG Apps Open the download page for the PRTG apps for iOS or Android 3327 .
Install PRTG Desktop Open the download page for PRTG Desktop 3327 .
166
Option Description
Get Help and Support Open the Help and Support Center 3329 from where you can access the
PRTG Manual, the Knowledge Base, and video tutorials. You can also
open support tickets 3330 and contact our customer service 170 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.
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 Get Maintenance to open the Paessler shop and extend
your maintenance for PRTG Network Monitor installations. Click Get More
Sensors to open the Paessler shop and upgrade your license. See also
section License Information 3317 .
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.
167
Section Description
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 3303 . Click Show Tickets under My Open Tickets to display
all open tickets that are assigned to you.
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 3323 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
168
§ 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 3219 . 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 3262 . 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.
169
6.2.1 Customer Service
If you have any questions about license purchases, upgrades, or maintenance extensions, you can
directly contact the Paessler Customer Service from the Help and Support Center 3329 in the PRTG web
interface. We readily assist you with quotes or information about licenses and maintenance, 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.
170
Contact Paessler Customer Service Form
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.
171
Field Description
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 3330 .
172
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 253 . The Devices view presents the device
tree and your monitoring results.
Welcome Page
When you log in to the PRTG web interface, you see the Welcome page 165 by default. You can set a
different home page in your account settings 3173 .
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
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.
173
Screen Page Area Description
Number Name
1 Global header This area contains the main menu bar at the very top, the global
area 175 status bar, breadcrumbs that show the path to the selected
object, a quick search box, and the logout button.
2 Page header This area contains the page heading with the name of the
bar 176 selected object, several tabs with settings, and quick action
buttons.
3 Page content 177

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.
4 Viewing These buttons are part of the page content. Here you can adjust
options 180 how your device tree is displayed.
5 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 3266 for the logged in user).
A timer counts down how much time remains until the next
automatic page refresh. Click to pause the refresh timer and
click to 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 you can configure in
your account settings.
Long table lists 222 that are set to display 1000 items at a
time are excluded from the automatic refresh to ensure
system performance.
Page footer icons Click for quick access to the auto-update 3323 settings if a
new version is available. To open the Contact Support form 3330 ,
click . For context-sensitive help, click .
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 3315 . 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:
174
§ 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 250 ).
§ 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.
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.
175
Screen Part Description
Number
1 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 252 .
2 New Alarms, New The information boxes show how many new alarms, new log entries,
Log Entries, and updated tickets have occurred. Click the respective box to view
Updated Tickets the lists of alarms 205 , logs 214 , or tickets 217 .
3 Global Sensor This area shows the accumulated states of all configured sensors,
Status Symbols grouped 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 186 .
4 Search Box, You can start a search ( ) or log out ( ) via the respective buttons
Logout in the top-right corner.
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.
5 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.
Page Header Bar

176
Page Header Bar
The page header bar below the global header area consists of the following elements.

Number
1 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 object's priority as well. To do so, click one of the five stars
( ) next to the object's name (this setting is not available for
the root group).
For more information, see section Priority and Favorites 227 .
2 Quick Action On the right side is a row of icons for several actions. Depending on
Buttons 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 per email ( ), or perform an
immediate scan ( ).
Click to open the context menu of the selected object for further
options.
For more information, see section Context Menus 232 .
3 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.
177
Page Content
178
Number
1 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 186 .
2 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 180 below.
3 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.
4 Add Button Click to add new objects to your monitoring setup. For a
detailed description, see Add Button 183 below.
5 Object Status, This element displays the status of the selected object, the
Scanning Interval, interval in which PRTG scans the object, the ID of the object,
Object ID, QR Code and the QR code for the selected page. If you use a PRTG app
for iOS or Android 3341 , 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 148 .
§ Groups and devices display the time that has elapsed since
the last execution of the auto-discovery 269 on the selected
object.
§ Devices show their DNS name or IP address as defined in the
device settings 535 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 3307 .
179
Switch Device Tree View
Wherever a probe or group is displayed, you can choose between a number of viewing options.
Device Tree View ing Options
Classic Device Tree View

Via the Switch Device Tree View buttons in the page header bar, you can adjust how much information is
included next to each object. Use the buttons 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.
Collapsed Device w ith Summarized Up and Unusual States and Individual Dow n States
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.
180
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.
181
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.
A tile shows the color of the sensor status with the highest priority. For example, if a device has sensors
in the Up (green), Paused (blue), and Warning (yellow) status, the corresponding tile shows a yellow
color to indicate that at least one sensor on this device is in the Warning status. If a single sensor
changes to the Down status, the corresponding tile turns red.
In the following table, you can find all sensor states sorted by the highest priority to the lowest priority:
182
Status Color Status Name Meaning
Icon
Red Down At least one sensor on this object shows the Down
status. Hover over an object's name to view the
total number of alarms for this object.
Light Pink Down (Acknowledged) At least one sensor on this object shows the Down
(Acknowledged) status. There is no sensor in the
Down status.
Yellow Warning At least one sensor on this object shows the

Warning status. There is no sensor in the Down or
Down (Acknowledged) status.
Orange Unusual At least one sensor on this object shows the

Unusual status. There is no sensor in the Down,
Down (Acknowledged), or Warning status.
Green Up All sensors on this object show the Up status.

There is no sensor in the Down, Down
(Acknowledged), Warning, Paused, or Unusual
status.
Blue Paused All sensors on this object show the Paused status.
There is no sensor in the Down, Down
(Acknowledged), Warning, Unusual, or Up status.
Grey Unknown All sensors on this object show the Unknown

status. There is no sensor in the Down, Down
(Acknowledged), Warning, Unusual, Paused, or Up
status.
Size by: Sensors / Size by: Priority
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.
183
The content of the menu varies depending on the selected object.
Add Button Menu
See the following sections for more information:
§ Add Remote Probe 3555
§ Add an Auto-Discovery Group 273
§ Add a Group 316
§ Add a Device 351
§ Add a Sensor 391
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 sensor 751
§ Probe Health sensor 1742
§ System Health sensor 2615
§ Some device-specific sensors for disk usage and bandwidth.
In a cluster, PRTG also creates a cluster probe device with a Cluster Health sensor 740 that monitors the
system health of the cluster.
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.
184
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 176 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?

185
6.4 Sensor States
The color of a sensor indicates its status. In the table below, you find a list of states that a sensor can
show. This list also reflects the priority of the sensor states whenever PRTG shows summarized sensor
states, for example, in the device tree 173 or on geographical maps 3099 . For example, if all sensors on a
specific 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 as
a red tile in the extended device tree views 180 .
The Down and Down (Partial) states are considered to be equal regarding status priority.
Status Icon Color Status Name Meaning
Red Down § 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 187 .
In this case, a sensor does not record any
data in its channels while it shows the
Down status.
§ There is an error limit in the channel
settings 3052 or the sensor shows the Down
status because of a lookup 3541 .
In this case, the sensor continues to
record data in all channels although it
shows the Down status.
Green/Re Down (Partial) In a cluster, at least one cluster node reports that
d 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 137 .
Light Down (Acknowledged) The sensor is down and the status has been
Pink acknowledged via the Acknowledge Alarm
feature. This indicates that an alarm has already
been brought to attention. For acknowledged
alarms, PRTG does not send further
notifications 3104 .
To show the Down (Acknowledged) status, right-
click the 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.
If a sensor in the Down (Acknowledged)
status was paused and resumed, it shows
the Down status again.
186
Status Icon Color Status Name Meaning
Yellow Warning § The sensor detected an error and shows the

Warning status, but PRTG 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 187 .
§ There is a warning limit in the channel settings

or the sensor shows the Warning status
because of a lookup.
Orange Unusual The sensor reports unusual values for this

weekday and 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 3234 .
You can also disable the unusual detection for
specific groups.
For more information, see section Group
Settings 531 .
Green Up The last scan was okay and the sensor receives
data.
Blue Paused The sensor is paused for a specific time span,

indefinitely, or because of a dependency 148 .
A sensor in the Paused status does not

count towards the maximum number of
sensors that your license allows.
Gray Unknown 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 extended troubleshooting, see the
Knowledge Base: What to check if sensors
are gray? and My sensors show an Unknown
status after a PRTG core server restart. What
can I do?
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.
187
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 418 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.
More
Knowledge Base
What to check if sensors are gray?

My sensors show an 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
188
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 3123 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 256 .
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.
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 .
189
Historic Data Report Settings
Historic Data Report Settings
Setting Description
Sensor This setting is only visible if you open the View Historic Data option 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 3257 after the specified start date. Set the start of the report to
a date for which data is available.
End Specify the end date and time for the data that you want to review. Use
the date time picker to enter the date and time.
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 to the
224
respective day or days. The current time of the current day is the end
date.
190
Setting Description
§ 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. You can choose
from:
§ 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 194 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. 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.
191
Setting Description
§ .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 3554 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.
192
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 enable 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 enable Show percentiles above. Enter a
Interval 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 enable 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.
Click Start to generate a historic data report.
193
You cannot generate the historic data report if monitoring data was deleted 3257 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 enable via the Show in graphs option in
the channel settings 3052 .
§ Reports show statistics for the uptime (the Up and Down states in percent) and for requests (Good
186
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 1857 .
§ 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 3449 to generate reports.
More
Knowledge Base
Why is there missing data in historic data reports?

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 144 in the object's settings 204 , section Advanced Network Analysis.
Activation of the Similar Sensors Detection
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 197 of all similar
sensors.
195
To edit the list of similar sensors results, use the available filters 198 .
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.
Similar Sensors Section on a Sensor's Overview Tab
196
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.
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 (recommended)
option as Analysis Depth in the Monitoring 3236 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 also section Working with Table Lists 222 .
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.
197
Similar Sensors Overview
You can click the column headers to sort the list. The Similar Sensors Overview provides the following
information.
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 (recommended) option as Analysis Depth in the Monitoring 3236 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.
198
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 3271 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 176
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 3237 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 3626 for a device, the
detection engine uses the SNMP version that you defined in the Credentials for SNMP Devices
section of the device settings 548 .
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 2445 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.
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.
202
Recommended Sensors Detection Settings
If you use the Manage automatically based on sensor count (recommended) 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 357 , you can manually start 270 it at any time, or you can choose if you want PRTG to
analyze a whole section 538 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 396
§ Probe Settings 426
§ Group Settings 479
§ Device Settings 535
§ Sensor Settings 586
You cannot open channel settings 3052 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.
For more information, see section Notification Triggers Settings 3063 .
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 176 to access the history of subordinate
objects. This includes system administration 3219 settings and account settings 3168 , reports 3123 ,
libraries 3107 , and maps 3145 . For more information, see section Logs 214 .
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 222 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 252 .
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 186 . 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
(Acknowledged) status.
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 3063 any more
notifications 3104 .
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 3088 .
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.
If the alarm condition still exists after the specified date, the sensor
shows the Down status again.
206
Field Description
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 3260 or administrators may acknowledge alarms. However, you can
give read-only users the right to acknowledge alarms, too. See the system administration settings,
section User Accounts 3262 .
More
Knowledge Base
Which audible notifications are available in the PRTG web interface and in PRTG 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 542 and the credentials for SNMP devices 548 that you entered
in the device settings or that the device inherits 140 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 535 .
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, via
(RPC) Windows service 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 3360 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 535 or as inherited
from a parent object like the root group.
For more information, see section Monitoring via SNMP 3348 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 140 .
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 the WMI
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 222 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 3579 .
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
Why do I get DoS alarms on my QNAP?
213
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.
For more information, see section Working with Table Lists 222 .
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 261 .
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:
214
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 show 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 show the following event types:
§ Report Related
§ Cluster Related
§ 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
215
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 176 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?
216
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 269 has finished, and you can create tickets for every kind of issue as well. In addition,
you can set up notifications 3104 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 221 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 221 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 3260 or user group 3270 .
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.
217
Type Description
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.
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 3175 .
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.
218
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 217 . 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 meaningful 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 222 , 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
219
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. There you can find all related information and take several
actions.
An Open ToDo Ticket w ith Instructions
Actions
The following actions are available for a specific ticket:
220
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 153 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.
221
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 3107 , maps 3145 , reports 3123 , notifications 3104 , and schedules 3213 , as well as in
logs 214 and tickets 217 . 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.
222
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 Date
Ranges 224 .
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 .
Enter one or more tags 146 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.
223
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.2019)
Today Start: 00:00 of today 2019-01-14 (00:00) - 2019-01-15 (00:00)

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

End: 00:00 of today
7 days Start: 00:00 of 7 days ago 2019-01-07 (00:00) - 2019-01-15 (00:00)

30 days Start: 00:00 of the same 2018-12-14 (00:00) - 2019-01-15 (00:00)

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

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

day 12 months ago
Unlimited Start: 00:00 of the same 2012-01-14 (00:00) - 2019-01-15 (00:00)

day 7 years ago (historic
data 189 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 222 . 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 176 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 252 .
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 173 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 250 , 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 3213 . 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 go into paused
status automatically when I pause the master object?
While a sensor is in the Paused status 186 , it does not collect any monitoring data, it does not
change its status, and it does not trigger any notifications 150 . 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 140 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 1693 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 148 .
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.
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.
The content of the context menu varies depending on the type of object. See the following subsections
for an overview of the available options.
§ 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 141 .
Probe Context Menu
232
Action Description
Scan Now Perform an immediate scan of the object. This queries data for all objects
underneath in the object hierarchy 140 .
Details Show the Overview tab of the object.
For more information about the Overview tab, see the Knowledge
Base: What options do I have to review my monitoring data in detail?
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 426 .

§ Notification Triggers: Open the Notification Triggers 3104 tab of the object.
§ Access Rights: Open a dialog to edit user access rights 153 for the
object.
§ Rename: Open a dialog to edit the name of the object.
§ Management: Open the Management tab 394 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 316 .
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 273 .
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 351 .
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
234
Action Description
§ Pause monitoring for the object and for all objects underneath in the
object hierarchy. 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 time. 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 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 or if it shows the
186
Down status because of a simulated error, the Resume option appears.

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?
235
Action Description
§ 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.
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 141 .
The context menu of the root group differs from the other groups' menu.
Group Context Menu
236
Action Description
Edit Context Menu
§ Settings: Open a dialog to edit group settings 479 for the group.
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 316 .
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 351 .
237
Action Description
Auto-Discovery This option is only available for auto-discovery groups or devices that have
the auto-discovery feature enabled 482 . 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 482 in the group settings under Device Identification and Auto-
Discovery. If there are new devices and sensors, you see them after a
few minutes.
For more information, see section Auto-Discovery 270 .
§ 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.
object.
Clone Open a dialog that guides you through the process of cloning the object.
For more information, see section Clone Object 3084 .
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
period.
239
Action Description

the past.
186

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 142 .
240
Device Context Menu
Action Description
Edit Context Menu
§ Settings: Open a dialog to edit device settings 535 for the device.
241
Action Description
object.
Add Sensor Open a dialog that guides you through the process of adding a new sensor
to the device.
For detailed instructions, see section Add a Sensor 391 .
Auto-Discovery This option is only available for auto-discovery groups or devices that have
the auto-discovery feature enabled 482 . 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 Device Identification and Auto-Discovery. If there are new sensors,
you see them after a few minutes.
For more information, see section Auto-Discovery 270 .
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 (recommended).
§ 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 3093 .
Recommend Now 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.
This option is only available if the Recommended Sensors
Detection 3237 is enabled.
242
Action Description

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

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.
Device Tools Hover over Device Tools to open the Device Tools menu.

Monitor instance.
244
Action Description
Device Tools Menu
The following actions are available:

§ Go to Service URL: Open the service page that you defined in the device
settings 535 . 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 remote probe on the
device. For more details, see Remote Probe Setup via Device Tools 3561 .
This option is only available on devices on local probes.
This option is not available in PRTG Hosted Monitor.
Find Duplicates In your configuration, search for devices with the same IP address or DNS
name as the selected device.

245
Sensor Context Menu
The Sensor Context Menu contains actions for your sensors 142 .
Sensor Context Menu
Action Description
Scan Now Perform an immediate scan of the object.
§ Settings: Open a dialog to edit settings 586 for the sensor.
object.
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 3063 any more notifications 3104 .
246
Action Description
Acknow ledge Alarm Context Menu
The following actions are available:

You can select Acknowledge Indefinitely, or you can acknowledge the
alarm For 5 Minutes, For 15 Minutes, For 1 Hour, For 3 Hours, For 1 Day,
or Until a specific time. If you select Until, you can additionally define a
time period. Use the date time picker to enter the date and time. 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 details about acknowledging an alarm, see section Alarms 206 .
object.
available:
Move Context Menu
247
Action Description
available:
or
Resume
Pause Context Menu
period.
the past.
186

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.
248
Action Description
§ View Historic Data: Open the Historic Data tab 189 .

More
Knowledge Base
PAESSLER WEBSITE
How to set up reports in PRTG in 5 easy steps

§ https://www.paessler.com/support/how-to/reports
249
6.18 Hover Popup
When you rest the mouse pointer over an object's icon in the device tree 173 or in table lists 222 , 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.
For more information about the Overview tab, see the Knowledge Base: What options do I have to
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.
Quick Action Buttons

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.
250
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 140 . 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

251
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
The following menu items are available:
§ Home 252
§ Devices 253
§ Libraries 255
§ Sensors 256
§ Alarms 259
§ Maps 259
§ Reports 260
§ Logs 261
§ Tickets 262
§ Setup 264
§ Search Box 266
§ Logout 266
Home
Click to open your homepage. The default homepage is the Welcome page 173 . Hover over Home to show
other options.
Main Menu: Home
252
Option Description
Sample Dashboard Open a preconfigured dashboard to view monitoring data in a different

layout. This dashboard is one of the default maps 3145 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 259 . You can include up to 10 map entries in the menu. For
more information, see section Home Menu 3147 .
You can change the appearance of the default dashboard with the
Map Designer 3148 . 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 137 .
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 homepage 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 3168 settings.
Devices
Click to show the device tree. Hover over Devices to show other options.
253
Main Menu: Devices
Option Description
All Open the Overview tab of the root group 140 that shows the device tree 173 .
Favorite Devices Open a table list 222 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 148 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 272 .
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.
254
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 272 .
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 3107 .
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.
255
Sensors
Click to open a list of all sensors 142 . 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 142 . 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 391 . During
the process, you can also choose to create a new device via the Add a
Device 351 dialog, which you can also open directly from the Devices
menu 253 .
Favorite Sensors Open a list of all sensors that you marked as favorites.
256
Option Description
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 186 .
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
§ Best Uptime (%)
§ Highest Uptime (Time)
257
Option Description
§ Worst Downtime (%)
§ Highest Downtime (Time)
By Type Open a list of sensors filtered by sensor type 3626 . 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 146 . 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 147 .
By Performance Impact Open a list of sensors filtered by performance impact 3307 . 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. You can choose between the
following levels of impact:
§ Very High
§ High
§ Medium
§ Low
§ Very Low
For an overview list of sensors sorted by performance impact, see

also section List of Sensors by Performance Impact 3713 .
Cross Reference Open the sensor cross reference to show information about all sensors
including priority and favorite 227 status, scanning interval 418 , access
rights 153 , notification trigger settings 204 , schedules 149 , and
dependencies 148 . 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 189 .
Similar Sensors Overview Open an overview with a list of similar sensors.

For more information, see section Similar Sensors 195 .
258
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
(Acknowledged) status.
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.
For more information, see section Maps 3145 .
259
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 3123 .
Main Menu: Reports
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.
260
Option Description
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 3126 . 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.
For more information, see section Logs 214 .
Logs for monitoring objects (for example, 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 show the following sensor states:
§ Up & Down
§ Down
§ Warning
§ Unusual
§ Up
§ Paused/Resumed
261
Option Description
§ Acknowledged Alarms
System Events Open a list with log information about specific system event types. Hover
over System Events to show the following event types:
§ Report Related
§ Cluster Related
§ 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 176 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.
262
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 217 .
Setup
Click to show the setup page. Hover over Setup to show other options.
For more information, see section Setup 3166 .
263
Main Menu: Setup
Option Description
Overview Open the setup page 3166 .
Account Settings Open the My Account 3168 settings. Hover over Account Settings to directly
show and open the account settings tabs:
§ My Account 3168
§ Notification Templates 3175
§ Notification Contacts 3209
§ Schedules 3213
System Administration Open the System Administration 3219 settings. Hover over System
Administration to directly show and open the system administration tabs:
§ Manage Subscription 70 (PRTG Hosted Monitor only)

§ User Interface 3219
§ Monitoring 3233
§ Notification Delivery 3241
§ Core & Probes 3250
§ Cluster 3280 (PRTG Network Monitor only)
264
Option Description
§ User Accounts 3260
§ User Groups 3270
§ Administrative Tools 3276
§ Single Sign-On 3282
PRTG Status Open the System Status 3291 page. If you run PRTG in a cluster, hover over
PRTG Status to show other options:
§ System Status 3291
§ Cluster Status 3315
License Information Open the license information 3317 page.
Auto-Update Open information about the Software Auto-Update 3323 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 3323 : View the update status and manually check for the latest
update.
§ Settings 3323 : Define your update settings.
Optional Downloads Open the download page 3327 for additional downloads. Hover over Optional
Downloads to show other options:
§ PRTG Apps 3327
§ PRTG Desktop 3327
§ Remote Probe Installer 3327
PRTG API Open the Application Programming Interface (API) Definition 3449 .
Help and Support Center Open the Help and Support Center 3329 from where you can access the
PRTG Manual, the Knowledge Base, and video tutorials. You can also
open support tickets 3330 and contact our customer service 170 from this
page.
Contact Support Open the Contact Paessler Support / Send Your Feedback to
Paessler 3330 form.
265
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 161 .
266
Part 7
Device and Sensor Setup
6/15/2022 267
7 Device and Sensor Setup
The PRTG web interface is your access to PRTG via a web browser. The PRTG web interface is based
on Asynchronous JavaScript and XML (AJAX). It uses a responsive design to adjust to the size of your
screen.
Use the PRTG web interface as the default interface to set up your monitoring. You can use it to
configure devices and sensors, to set up notifications, to review monitoring results, to create reports, and
to visualize your monitoring on dashboards.
While you are logged in 161 , the PRTG web interface continuously refreshes the data on the screen via
AJAX calls. This way, you are always up to date regarding your monitoring results. You can individually
set 3266 the refresh interval and method.
With the Single Page Application (SPA) technology, your system stays highly performant because only
single page elements are refreshed when necessary.
The following sections introduce how to set up devices and sensors in the PRTG web interface.
§ Auto-Discovery 269
§ Create Objects Manually 272
§ Manage Device Tree 394
§ Root Group Settings 396
§ Probe Settings 426
§ Group Settings 479
§ Device Settings 535
§ Sensor Settings 586
§ Additional Sensor Types (Custom Sensors) 3047
§ Channel Settings 3052
§ Notification Triggers Settings 3063
268
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 3093 .
You can use auto-discovery groups 273 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 217 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 3174 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
140
the parent device. If possible, we recommend that you define these settings in the root group 396 .
§ If a device has more than one IP address, it may 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 .
269
§ 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 3271 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 (not
available on hosted probes), 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 176 , you can always see
when PRTG ran the last auto-discovery on a selected group or device.
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 272 .
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 parameter. This may 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?

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

271
7.2 Create Objects Manually
We recommend that you use the auto-discovery 269 feature to create a basic monitoring setup for your
network. Afterward, you can manually add devices that were not discovered, or arrange 3082 detected
devices in groups.
The procedure depends on the kind of object that you want to add:
§ Add a Group 316
§ Add a Device 351
§ Add a Sensor 391
Add a Remote Probe

272
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 253 . 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 276 .
In this section:
§ Step 1: Select a Parent 275
§ Step 2: Define Auto-Discovery Group Settings 276
§ Basic Group Settings 277
§ Device Identification and Auto-Discovery 278
§ Inherited Settings 285
§ Credentials for Windows Systems 285
§ Credentials for Linux/Solaris/macOS (SSH/WBEM) Systems 286
§ Credentials for VMware/XenServer 290
§ Credentials for SNMP Devices 291
§ Credentials for Database Management Systems 294
§ Credentials for AWS 296
§ Credentials for Cisco Meraki 297
§ Credentials for Dell EMC 298
§ Credentials for FortiGate 298
§ Credentials for HPE 3PAR 299
§ Credentials for Microsoft 365 301
§ Credentials for Microsoft Azure 302
§ Credentials for MQTT 303
§ Credentials for NetApp 305
§ Credentials for OPC UA 306
§ Credentials for Soffico Orchestra 309
273
§ Credentials for Redfish 310
§ Credentials for REST API 311
§ Credentials for Veeam 313
§ Access Rights 313
§ More 315
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 479 .
274
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.
275
Step 2: Define Auto-Discovery Group Settings
Add Auto-Discovery Group Assistant Step 2
276
Basic Group Settings
Setting Description
Group Name Enter a name to identify the group. By default, PRTG shows this name in
the device tree 173 , as well as in alarms 205 , logs 214 , notifications 3104 ,
reports 3123 , maps 3145 , libraries 3107 , and tickets 217 .
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 146 .
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
277
Device Identification and Auto-Discovery
278
279
Setting Description
Auto-Discovery Level Select the level of detail for the auto-discovery 269 :
§ No auto-discovery: Select this option if you only want to manually
create devices and sensors.
§ Standard auto-discovery (recommended): 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.
You can also select all items or cancel the selection by using the
check box in the table header.
PRTG uses the device templates that you select for the auto-discovery on
the device. Choose from:
§ 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)
280
Setting Description
§ Generic Device (SNMP Enabled, Detailed)
§ HTTP Web Server
§ 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)
281
Setting Description
§ VMware ESXi / vCenter Server
§ Web Server
§ 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 217 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 270 .
§ 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 3238 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.
IP Address Selection Select how you want to define the IP address range for the auto-discovery:
Method
§ Class C base IP address with start/end (IPv4): 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.
282
Setting Description

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 3256 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) 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
start/end (IPv4) above. 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
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.
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.
283
Setting Description
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 3256 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 536
shows the DNS name or IP address that PRTG uses to access the target
device. Choose between:
§ Use DNS names (recommended): 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 (recommended):
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.
284
Setting Description
§ 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 396 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 144 .
285
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 for Linux/Solaris/macOS (SSH/WBEM) Systems

286
287
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 login:
§ Password: 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 details, see section Monitoring via SSH 3363 .
Password This setting is only visible if you select Password above. Enter a password
for access to the Linux/Solaris/macOS system via SSH and WBEM.
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 3276 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:
§ 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.
288
Setting Description
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 3626 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.
SSH Connection Mode Select the connection mode that you want to use to access data with
SSH sensors 3363 :
§ Default (recommended): This is the default monitoring method for SSH
sensors. It provides the best performance and security.
§ Compatibility mode (deprecated): Use this mode only if the default mode
does not work on the target system. The compatibility mode is the SSH
engine that PRTG used in previous versions and it is deprecated.
We strongly recommend that you use the default SSH connection
mode.
289
Setting Description
You can also individually select the SSH connection mode for each
SSH sensor in the sensor settings.
Credentials for VMware/XenServer

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 details, see the VMware sensors sections.
290
Setting Description
VMware Protocol Select the protocol for the connection to VMware ESXi, vCenter Server, or
Citrix XenServer:
§ HTTPS (recommended): Use a Secure Sockets Layer (SSL)/Transport
Layer Security (TLS) secured connection.
§ HTTP: Use an unsecure connection.
Session Handling Select if you want to reuse a session for VMware sensors:
§ Reuse a session for multiple scans (recommended): 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

291
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 (recommended): Use SNMP v2c for the connection. SNMP
v2c also only offers clear-text data transmission but it supports 64-bit
counters.
292
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 1742 , distribute the
load over multiple probes 3557 . 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
(recommended) 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: Use message-digest algorithm 5 (MD5) for authentication.
§ SHA: Use Secure Hash Algorithm (SHA) 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 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.
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: Use Data Encryption Standard (DES) as the encryption algorithm.
§ AES: Use Advanced Encryption Standard (AES) as the encryption

algorithm.
293
Setting Description
Net-SNMP does not support AES-192 and AES-256. They do not

have RFC specifications.
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).
Credentials for Database Management Systems

The settings you define in this section apply to the following sensors:
§ ADO SQL v2 sensor 595
§ Microsoft SQL v2 sensor 1367
§ MySQL v2 sensor 1425
§ Oracle SQL v2 sensor 1634
§ PostgreSQL sensor 1728
294
Setting Description
Port Select the port that PRTG uses for connections to the monitored
databases:
§ Default (recommended): 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.
295
Setting Description
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: PRTG uses the Windows

credentials that you define in settings that are higher in the object
hierarchy 140 , for example, in the settings of the parent device; 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

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?
296
Credentials for AWS
Setting Description
Access Key Enter the Amazon Web Services (AWS) access key.
Secret Key Enter the AWS secret key.
Credentials for Cisco Meraki

Setting Description
API Key Enter an API key that the sensor uses for authentication against the
Cisco Meraki Dashboard API.
297
Credentials for Dell EMC
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.
Credentials for FortiGate

298
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

299
Setting Description
User Name Enter the user name for access to the HPE 3PAR system.
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:
Security (TLS) secured connection.
300
Setting Description
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 Microsoft 365

The Microsoft 365 Mailbox sensor 1306 , the Microsoft 365 Service Status sensor 1317 , and the
Microsoft 365 Service Status Advanced sensor 1324 use the following credentials to authenticate with
Azure Active Directory (Azure AD).
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?
301
Setting Description
Tenant ID Enter the Azure AD tenant ID.

A tenant ID must be a 32-digit sequence in hexadecimal notation.
Client ID Enter the Azure AD client ID.
Client Secret Enter the Azure AD client secret.
Credentials for Microsoft Azure

The Microsoft Azure SQL Database sensor 1332 , Microsoft Azure Storage Account sensor 1341 ,
Microsoft Azure Subscription Cost sensor 1349 , and the Microsoft Azure Virtual Machine sensor 1358
use the following credentials to authenticate with Azure AD.
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?
302
Setting Description

Subscription ID Enter the Azure AD subscription ID.
Credentials for MQTT

303
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.
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.
304
Setting Description
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: 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 enable Server Authentication 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 enable Client Authentication 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 enable Client Authentication above. Enter
the client key for access to the MQTT broker.
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 enable Client Authentication above. Enter
the password for the client key.
Credentials for NetApp

The NetApp System Health v2 sensor 1525 and the NetApp Volume v2 sensor 1546 use the following
credentials for access to the ONTAP System Manager.
305
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
Protocol Select the protocol that you want to use for the connection to the ONTAP
System Manager. Choose between:
§ HTTPS (default)
§ HTTP
Credentials for OPC UA

306
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.
307
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 Paste 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.
§ 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 Enter the client key for access to the OPC UA server.
Client Key Password Enter the password for the client key.
Select if you want to connect without credentials or define credentials for

Authentication Method access to the OPC UA server:
§ Anonymous (default): Connect without credentials.
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.
Enter the user name for access to the OPC UA server.
Enter the password for access to the OPC UA server.
308
Credentials for Soffico Orchestra
Setting Description
access to the Orchestra platform:
Enter the user name for access to the Orchestra platform.
309
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

310
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. Choose between:

Port Enter the port for the connection to the Redfish system. The default port
Credentials for REST API

Setting Description
Authentication Method Select the authentication method for access to the Representational State
Transfer (REST) application programming interface (API):
§ 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 REST API.
311
Setting Description
Password This setting is only visible if you select Basic authentication above. Enter
the password for access to the REST API.
Bearer Token This setting is only visible if you select Bearer authentication above. Enter
a bearer token for access to the REST API.
Placeholder 1 Description Enter a description for Placeholder 1, for example information about the
purpose or content of the placeholder.
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 does
not display the value in the sensor log or the sensor's settings.
312
Credentials for Veeam
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
313
Setting Description
User Group Access Select the user groups 3270 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,
enable the Revert children's access rights to inherited option.
For more details on access rights, see section Access Rights
Management 153 .
Click OK to save your settings. If you close the dialog without saving, all changes to the settings are
lost.
314
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?
315
7.2.2 Add a Group
There are several ways to manually add a group:
§ Select Devices | Add Group from the main menu bar 253 . 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 319 .
In this section:
§ Add a Group 317
§ Step 2: Define Group Settings 319
316
§ More 350
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 479 .
317
Add Group Assistant Step 1
Select the probe or group that you want to add the new group to. Click OK.
318
Step 2: Define Group Settings
Add Group Assistant Step 2
319
Setting Description
inherited 146 .
Inherited Settings
320
Setting Description
Windows Management Instrumentation (WMI) sensors and other Windows
sensors.
321
322
323
Setting Description
via WBEM:

324
Setting Description
22.

settings.
system:
password.
su command.
SSH sensors 3363 :
mode.
325
Setting Description

Setting Description
326
Setting Description
Citrix XenServer:

327
Setting Description
counters.
328
Setting Description
limitation.
device.
device.
encryption type:

algorithm.
329
Setting Description

of your device.
error message.

330
Setting Description
Port Enter a custom port for database connections. Enter an integer.

Authentication Method This setting is only visible if you select SQL server authentication above.
Password Enter a timeout in seconds for the request. Enter an integer. The
331
Setting Description
Credentials for AWS

Credentials for AWS
Setting Description

332
Setting Description

333
Setting Description

Setting Description

334
Setting Description
3PAR system:
335
Setting Description
system?

Status sensors?
336
Setting Description


337
Setting Description


338
Setting Description
is 1883.
339
Setting Description
MQTT broker.
MQTT broker.

340
Setting Description
§ HTTPS (default)
§ HTTP

341
Setting Description

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


to use.
343
Setting Description
344
Setting Description
Orchestra platform:

345
Setting Description


Setting Description
346
Setting Description
347
Setting Description
Manager.
Access Rights
348
Setting Description
rights settings.
Management 153 .
lost.
349
More
Knowledge Base

PRTG?
350
7.2.3 Add a Device
There are several ways to manually add a device:
§ Select Devices | Add Device from the main menu bar 253 . 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 354 .
In this section:
§ Add a Device 352
§ Step 2: Define Device Settings 354
§ Device Name and Address 355
351
§ More 390
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 535 .
352
Add Device Assistant Step 1
Select the group that you want to add the new device to. Click OK.
353
Step 2: Define Device Settings
Add Device Assistant Step 2
354
Device Name and Address
Device Name and Address
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.
355
Setting Description
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. 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.
for monitoring.
which they connect.
inherited 146 .
Device Icon Select a device icon. PRTG shows it in the device tree.
356
Setting Description
installations.
sensors available.
list.

357
Setting Description
minutes.
Auto-Discovery.
Discovery.
§ ADSL
§ Cisco ASA VPN
§ Dell EqualLogic
§ Dell MDi Disk
§ DNS Server
§ FTP Server
§ HTTP Web Server
358
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
359
Setting Description
§ XenServer Hosts
Inherited Settings

360
Setting Description
sensors.

361
362
Setting Description
via WBEM:

363
Setting Description
22.

settings.
system:
password.
su command.
SSH sensors 3363 :
mode.
364
Setting Description

Setting Description
365
Setting Description
Citrix XenServer:

366
Setting Description
counters.
367
Setting Description
limitation.
device.
device.
encryption type:

algorithm.
368
Setting Description

of your device.
error message.

369
Setting Description
databases:
ú MySQL: 3306
ú Oracle SQL: 1521
ú PostgreSQL: 5432
370
Setting Description
Credentials for AWS

371
Credentials for AWS
Setting Description

Setting Description
372
Setting Description

373
Setting Description

374
Setting Description
3PAR system:
375
Setting Description
system?

Status sensors?
376
Setting Description


377
Setting Description


378
Setting Description
is 1883.
379
Setting Description
MQTT broker.
MQTT broker.

380
Setting Description
§ HTTPS (default)
§ HTTP

381
Setting Description

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


to use.
383
Setting Description
384
Setting Description
Orchestra platform:

385
Setting Description


Setting Description
386
Setting Description
387
Setting Description
Manager.
Access Rights
388
Access Rights
Setting Description
rights settings.
Management 153 .
389
lost.
More
Knowledge Base
PRTG?
390
7.2.4 Add a Sensor
There are several ways to manually add a sensor:
§ Select Sensors | Add Sensor from the main menu bar 256 . 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 393 .

§ 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
§ Select Add sensor to a device.
§ Select the device you want to add the new sensor to.
§ Click Continue.
The Add Sensor dialog appears.
391
Step 1: Choose Sensor
Add Sensor Dialog
In the Add Sensor dialog, you can:
§ 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 List of Available Sensor Types 3660 , section PRTG Sensor Hub
Sensors.
§ Click the sensor box to select the sensor.
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.
392
Also consider whether a sensor’s performance impact 3307 is high or low. To do so, check the bar in
the lower-left corner of the sensor box. For further information, see the Knowledge Base: How can I
speed up PRTG—especially for large installations? (especially section 4 - Sensor Type and Monitoring).
For an overview list of sensors sorted by performance impact, see section List of Sensors by
Performance Impact 3713 .
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. You can
also go to the List of Available Sensor Types 3626 section to find a comprehensive overview of
sensors.
Step 2: Define Sensor Settings

The sensor settings dialog opens where you can define the sensor settings 586 and create the sensor.
More
Knowledge Base
How can I change the number of entries in most used sensor types?
How can I speed up PRTG—especially for large installations?

PAESSLER WEBSITE
You can find useful scripts for sensors in the PRTG Sensor Hub
§ https://www.paessler.com/sensor-hub
393
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 3084 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 3089 .
Related Topics
For other ways to arrange objects, see
394
§ Arrange Objects 3082
§ Create Device Template 3093
§ Clone Object 3084
395
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 398
§ Windows Compatibility Options 411
§ SNMP Compatibility Options 412
§ Proxy Settings for HTTP Sensors 417
§ Scanning Interval 418
§ Schedules, Dependencies, and Maintenance Window 420
§ Channel Unit Configuration 422
§ Advanced Network Analysis 423
§ More 424
396
Setting Description
Group Name Enter a name to identify the group. By default, PRTG displays it in the
device tree 173 .
Status Select the monitoring status of the group:
§ Started: 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.
397
Location
Location
Setting Description
Location (for Geo Maps) If you want to use Geo Maps 3099 , 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 186
(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 3223 .
398
Setting Description
sensors.
399
400
401
Setting Description
via WBEM:

402
Setting Description
22.

settings.
system:
§ Run the command as the connecting user (default): Use the rights of
the user who establishes the SSH connection.
password.
su command.
SSH sensors 3363 :
§ Compatibility mode (deprecated): Use this mode only if the default
mode does not work on the target system. The compatibility mode is
the SSH engine that PRTG used in previous versions and it is
deprecated.
mode.
403
Setting Description
Setting Description
404
Setting Description

Citrix XenServer:

405
Setting Description
counters.
406
Setting Description
limitation.
device.
device.
encryption type:

algorithm.
407
Setting Description

of your device.
error message.

408
Setting Description
databases:

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

Credentials for AWS
410
Setting Description
Windows Compatibility Options

If you experience problems when you monitor via Windows sensors, use the following compatibility
options for troubleshooting.
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). The
setting does not apply to other sensors.
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.
411
Setting Description
§ WMI only (recommended): Query data via WMI only. If this is not
possible, the sensor returns no data. We recommend that you use this
option.
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 (recommended): 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. 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.
412
413
Setting Description
SNMP Delay (ms) Enter the time in milliseconds (ms) that PRTG waits between two SNMP
requests. This can increase device compatibility. Enter an integer. You
can define a delay between 0 and 100. PRTG does not support higher
delays.
If you experience SNMP connection failures, try increasing the

delay.
Failed Requests Select if an SNMP sensor tries again after a request fails:
§ Retry (recommended): 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.
§ Ignore overflow values: 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 overflow
values in this case. For more details, 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.
§ Ignore zero values for delta sensors (recommended): Ignore zero values
and do not include them in the monitoring data. We recommend that
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 (recommended): The interface scan
uses 64-bit traffic counters, if available. This can avoid buffer overflows
in the devices

414
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 (recommended): 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
has to 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 (recommended): 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 version v2c
or higher. 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 140 .
§ 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.
415
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 2445 and SNMP RMON 2400 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): 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: SNMP Traffic sensors when the device changes
them.
Port Identification Select the field that PRTG uses for SNMP interface identification:
§ Automatic identification (recommended): 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.
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 2445 and to Cisco IP
SLA sensors 682 .
Enter the index at which PRTG starts to query the interface range during
sensor creation. Enter 0 for the automatic mode.
416
Setting Description
End Interface Index This setting only applies to SNMP Traffic sensors 2445 and to Cisco IP
SLA sensors 682 .
Enter the index at which PRTG stops querying the interface range during
Proxy Settings for HTTP Sensors

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 HTTP sensors and how they monitor. To change the proxy settings for
the PRTG core server, see section Core & Probes 3251 .
The SSL Certificate sensor 2588 and the SSL Security Check sensor 2598 do not support HTTP proxies
but you can configure connections via SOCKS proxies in the sensors' settings.
417
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, HTTP sensors do not use a proxy.
Port Enter the port number of the proxy. The default is 8080. Enter an integer.
User Name If the proxy requires authentication, enter the user name for the proxy
login.
Only basic authentication is available. Enter a string or leave the field
empty.
Password If the proxy requires authentication, enter the password for the proxy login.
empty.
Scanning Interval
Scanning Interval
Setting Description
Scanning Interval Select a scanning interval from the dropdown list. The scanning interval
determines the amount of time that the sensor waits between two scans.
Choose from:
§ 30 seconds
§ 60 seconds
§ 5 minutes
§ 10 minutes
418
Setting Description
§ 15 minutes
§ 30 minutes
§ 1 hour
§ 4 hours
§ 6 hours
§ 12 hours
§ 24 hours
You can change the available intervals in the system

administration 3233 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 186 . 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. Choose from:
§ 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
(recommended): 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 3541 values, the sensor immediately shows
the Down status. None of the interval options apply.
419
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. Choose from:
§ 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 3215 .
Maintenance Window Select if you want to set up a one-time maintenance window. During a
maintenance window, monitoring stops for the selected object and all
child objects. They show the Paused status instead. Choose between:
§ Do not set up a one-time maintenance window: 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. You can define a time span
for the pause below.
420
Setting Description
To close an active one-time maintenance window before the end date,

select Do not set up a one-time maintenance window.
Maintenance Begins This setting is only visible if you enable 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 enable Set up a one-time maintenance
window above. Use the date time picker to enter the end date and time of
Access Rights
Access Rights
421
Setting Description
rights settings.
Management 153 .
Channel Unit Configuration
422
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
423
Setting Description
Unusual Detection Select if you want to use the unusual detection 3234 for sensors:
§ Enabled: Activates the unusual detection for this object and, by default,
for all objects underneath in the object hierarchy 140 . Sensors that are
affected by this setting show the Unusual status if PRTG detects
unusual activity.
§ Disabled: 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 3234 .
Similar Sensors Select if you want to activate the similar sensors 195 analysis:
Detection
§ Enabled: 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.
§ Disabled: 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 3236 .
System Information Select if you want to retrieve and show system information 208 for your
devices:
§ Enabled: Activates the system information feature for this object and, by
default, for all objects underneath in the hierarchy.
§ Disabled: 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 542 and the credentials for SNMP devices 548 that you entered in
the device settings or that the device inherits 140 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
424
PRTG?
What is the Overflow Values setting in the SNMP Compatibility Options?

How can I change the defaults for names automatically generated for new SNMP sensors?
SNMP Traffic sensors when the device changes them

425
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 396 so that
you can inherit them to all other objects in the object hierarchy 140 .
In this section:
§ Basic Probe Settings 427
§ Location 428
426
§ Administrative Probe Settings 474
§ Scheduled Restart Settings 476
§ More 477
Basic Probe Settings
Basic Probe Settings
Setting Description
Probe Name Enter a meaningful name to identify the probe. By default, PRTG shows
this name in the device tree 173 , as well as in alarms 205 , logs 214 ,
notifications 3104 , reports 3123 , maps 3145 , libraries 3107 , and tickets 217 .
427
Setting Description
inherited 146 .
Status Select the monitoring status of the probe:

§ Started: 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
428
Location
Setting Description
49.452778 any 11.077778 text.
geographical map.

429
Setting Description
sensors.

430
431
Setting Description
via WBEM:

432
Setting Description
22.

settings.
system:
password.
su command.
SSH sensors 3363 :
deprecated.
mode.
433
Setting Description

Setting Description
434
Setting Description
Citrix XenServer:

435
Setting Description
counters.
436
Setting Description
limitation.
device.
device.
encryption type:

algorithm.
437
Setting Description

of your device.
error message.

438
Setting Description
databases:
ú MySQL: 3306
ú Oracle SQL: 1521
ú PostgreSQL: 5432
439
Setting Description
Credentials for AWS

440
Credentials for AWS
Setting Description
Setting Description
441
Setting Description

442
Setting Description
443
Setting Description
3PAR system:
444
Setting Description
system?

Status sensors?
445
Setting Description


446
Setting Description

447
Setting Description
is 1883.
448
Setting Description
MQTT broker.
MQTT broker.

449
Setting Description
§ HTTPS (default)
§ HTTP
450
Setting Description

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


to use.
452
Setting Description
Setting Description
453
Setting Description
Orchestra platform:
454
Setting Description


455
Setting Description
456
Setting Description
457
Setting Description
Manager.

Setting Description
458
Setting Description

WMI.
option.

timeout value.
Timeout (Sec.) This setting is only visible if you select Set manually above. 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).

459
460
Setting Description
delays.

delay.
§ Use 64-bit counters if available (recommended): The interface scan uses
64-bit traffic counters, if available. This can avoid buffer overflows in the
devices

461
Setting Description
counters, even if 64-bit counters are available. This can make monitoring
more reliable for some devices.
response size.
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:

the local device.
462
Setting Description

(Kbit/s).
them.
interface names.
available.
identification.
SLA sensors 682 .
463
Setting Description
SLA sensors 682 .

464
Setting Description
login.
empty.
empty.
465
Scanning Interval
Scanning Interval
Setting Description
Choose from:
§ 30 seconds
§ 60 seconds
§ 5 minutes
§ 10 minutes
§ 15 minutes
§ 30 minutes
§ 1 hour
§ 4 hours
§ 6 hours
§ 12 hours
§ 24 hours

466
Setting Description
Down status.
options can apply.

apply.
Cluster Monitoring Exclusion

467
Setting Description
Exclude Cluster Nodes This setting is only visible if you have a failover cluster 137 .
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 144 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.
Setting Description
§ None
468
Setting Description
§ Saturdays
§ Sundays
§ Weekdays
§ Weekends

maintenance window, monitoring stops for the selected object and all child
objects. They show the Paused status instead. Choose between:
§ Set up a one-time maintenance window: Set up a one-time maintenance
window and pause monitoring. You can define a time span for the pause
below.
To close an active one-time maintenance window before the defined
end date, change the time entry in Maintenance Ends to a date in the
past.
Dependency Type Select a dependency type. You can use dependencies to pause
monitoring for an object depending on the status of a different object. You
can choose from:
§ Use parent: 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.
469
Setting Description
To test your dependencies 3096 , 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 enable Select a sensor above. Click
and use the object selector 225 to select a sensor on which the current
object will depend.
Dependency Delay (Sec.) This setting is only visible if you select Select a sensor above. Define a
time span in seconds for the dependency delay.
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
470
Setting Description
rights settings.
Management 153 .

471
Setting Description
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
472
Setting Description
unusual activity.
473
Setting Description
Detection
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.
474
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
specific IP address or select auto.
For more information, see section IPv6 Support 158 .
Cluster Connectivity This setting is only visible if you have a failover cluster 137 .
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.
475
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.
Scheduled Restart Settings
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 3276 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.
476
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 This setting is only visible if you select a schedule option above. 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?
477

478
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 396 .
In this section:
§ Location 487
479
§ Number of Sensors Limitation 532
§ More 533
480
Setting Description
Status Select the monitoring status of the group:

§ Started: 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 146 that this group inherits 146 from its parent probe 141 .
This setting is for your information only. You cannot change it.
inherited 146 .
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
).
481
Setting Description
installations.
sensors available.
list.
§ ADSL
482
Setting Description
§ Cisco ASA VPN
§ 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
483
Setting Description
§ Server (Dell)
§ Server (Fujitsu)
§ Server (IBM)
§ SonicWall
§ UPS Health (APC)
§ Web Server
§ XenServer Hosts

minutes.
Auto-Discovery.
484
Setting Description
start at the time that you define in the Monitoring settings, section
Auto-Discovery.
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): 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 3256 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) 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
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
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.
485
Setting Description
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.
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 3256 settings.
486
Setting Description
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 536
shows the DNS name or IP address that PRTG uses to access the target
device. Choose between:
§ Use DNS names (recommended): 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 (recommended):
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
487
Location
Setting Description
49.452778 any 11.077778 text.
geographical map.

488
Setting Description
sensors.

489
490
Setting Description
via WBEM:

491
Setting Description
22.

settings.
system:
password.
su command.
SSH sensors 3363 :
deprecated.
mode.
492
Setting Description

Setting Description
493
Setting Description
Citrix XenServer:

494
Setting Description
counters.
495
Setting Description
limitation.
device.
device.
encryption type:

algorithm.
496
Setting Description

of your device.
error message.

497
Setting Description

498
Setting Description
Credentials for AWS

Credentials for AWS
Setting Description

499
Setting Description

500
Setting Description

Setting Description

501
Setting Description
3PAR system:
502
Setting Description
system?

Status sensors?
503
Setting Description


504
Setting Description


505
Setting Description
is 1883.
506
Setting Description
MQTT broker.
MQTT broker.

507
Setting Description
§ HTTPS (default)
§ HTTP

508
Setting Description

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


to use.
510
Setting Description
511
Setting Description
Orchestra platform:

512
Setting Description


Setting Description
513
Setting Description
514
Setting Description
Manager.

515
Setting Description

WMI.
option.
516
Setting Description

timeout value.

517
518
Setting Description
delays.

delay.
devices

519
Setting Description
response size.
for example:

the local device.
520
Setting Description

(Kbit/s).
them.
interface names.
available.
identification.
SLA sensors 682 .
521
Setting Description
SLA sensors 682 .

522
Setting Description
login.
empty.
empty.
523
Scanning Interval
Scanning Interval
Choose from:
§ 30 seconds
§ 60 seconds
§ 5 minutes
§ 10 minutes
§ 15 minutes
§ 30 minutes
§ 1 hour
§ 4 hours
§ 6 hours
§ 12 hours
§ 24 hours

524
Choose from:
§ 30 seconds
§ 60 seconds
§ 5 minutes
§ 10 minutes
§ 15 minutes
§ 30 minutes
§ 1 hour
§ 4 hours
§ 6 hours
§ 12 hours
§ 24 hours

Down status.
options can apply.
apply.
525
Setting Description
§ None
§ Saturdays
§ Sundays
§ Weekdays
§ Weekends

526
Setting Description

To terminate an active maintenance window before the defined end
date, change the time entry in Maintenance Ends to a date in the
past.
Maintenance Begins Select if you want to set up a one-time maintenance window. During a
can choose from:

pause a master object or if you pause it by schedule.
object will depend.
527
Setting Description
an integer.
Access Rights
528
Setting Description
rights settings.
Management 153 .

529
Setting Description
§ Bandwidth
§ Memory
§ Disk
§ File
§ Custom
530
Setting Description
unusual activity.
531
Setting Description
Detection
devices:


Monitor instance.
Number of Sensors Limitation
Number of Sensors Limitation
532
Setting Description
Sensor Limit This setting allows you to set a limit for the maximum number of sensors
in this group, including subgroups. If the amount of sensors exceeds the
limitation, PRTG sets the surplus sensors to the Paused status. Choose
between:
§ 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.
§ Limit number of sensors: Set a limitation for the number of sensors in
this group. Only a defined number of sensors are allowed in this group
and its subgroups.
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 status.
Enter an integer.
Sensors that are in the Paused status 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?
533

534
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 3088 .
In this section:
§ Basic Device Settings 536
§ Additional Device Information 538
§ Location 542
535
§ More 584
Basic Device Settings
Basic Device Settings
Setting Description
Device Name Enter a name to identify the device. By default, PRTG shows this name in
Status Select the monitoring status of the device:

§ Started: Monitor the device.
536
Setting Description
§ 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.
for monitoring.
which they connect.
for monitoring.
which they connect.
Parent Tags Shows tags 146 that this device inherits 146 from its parent group 141 and
its parent probe 141 .
inherited 146 .
We recommend that you use the default value. You can also add
additional tags.
537
Setting Description
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
).
Additional Device Information
Additional Device Information
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.
538
Setting Description
installations.
sensors available.
list.

minutes.
Auto-Discovery.
Discovery.
539
Setting Description
§ ADSL
§ Cisco ASA VPN
§ 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
540
Setting Description
§ Server (Dell)
§ Server (Fujitsu)
§ Server (IBM)
§ SonicWall
§ UPS Health (APC)
§ Web Server
§ XenServer Hosts
Inherited Settings
541
Location
Location
Setting Description
49.452778 any 11.077778 text.
geographical map.

542
Setting Description
sensors.

543
544
Setting Description
via WBEM:

545
Setting Description
22.

settings.
system:
password.
su command.
SSH sensors 3363 :
deprecated.
mode.
546
Setting Description

Setting Description
547
Setting Description
Citrix XenServer:

548
Setting Description
counters.
549
Setting Description
limitation.
device.
device.
encryption type:

algorithm.
550
Setting Description

of your device.
error message.

551
Setting Description

Custom Port Select the authentication method for the connection to the Structured
552
Setting Description
Credentials for AWS

Credentials for AWS
Setting Description
553
Setting Description

554
Setting Description

Setting Description

555
Setting Description
3PAR system:
556
Setting Description
system?

Status sensors?
557
Setting Description


558
Setting Description


559
Setting Description
is 1883.
560
Setting Description
MQTT broker.
MQTT broker.

561
Setting Description
§ HTTPS (default)
§ HTTP

562
Setting Description

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


to use.
564
Setting Description
565
Setting Description
Orchestra platform:

566
Setting Description


Setting Description
567
Setting Description
568
Setting Description
Manager.

569
Setting Description

WMI.
option.
570
Setting Description

timeout value.

571
572
Setting Description
delays.

delay.
devices

573
Setting Description
response size.
for example:

the local device.
574
Setting Description

(Kbit/s).
them.
interface names.
available.
identification.
SLA sensors 682 .
575
Setting Description
SLA sensors 682 .

576
Setting Description
login.
empty.
empty.
577
Scanning Interval
Scanning Interval
For more information, see section Root Group Settings 418 , section Scanning Interval.

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

below.
To cancel an active maintenance window before the defined end date,
change the time entry under Maintenance Ends to a date in the past.
Maintenance Begins Select if you want to set up a one-time maintenance window. During a
below.
can choose from:
579
Setting Description

pause a master object or if you pause it by schedule.
object will depend.
an integer.
Access Rights
580
Setting Description
rights settings.
Management 153 .
581
For more information, see section Root Group Settings 422 , section Channel Unit Configuration.

582
Setting Description
unusual activity.
Detection
583
Setting Description
devices:


Monitor instance.
settings are lost.
More
Knowledge Base

PRTG?
584


585
7.8 Sensor Settings
There is a dedicated section for every sensor with details about the available settings.
For more information, see section List of Available Sensor Types 3626 .
For sensor settings, multi-edit is also available. This enables you to change properties of many
sensors at the same time. For more information, see section Multi-Edit 3088 .
To detect unexpected correlations between your network components, PRTG provides a similar
sensors 195 analysis.
Lists of Sensors for Different Topics

There are different overview lists of sensors:
§ List of New Sensors 3681
§ List of Sensors by Performance Impact 3713
§ List of Sensors with IPv4 Support Only 3728
§ List of Sensors with Meta-Scan Feature 3731
§ List of Sensors without Device Template Capability 3739
586
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 594 .
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
587
Remarks
§ This sensor has a high performance impact. Use it with care. We recommend that you use no more
than 200 sensors of this sensor type on each probe.
§ The parent device must be a DC.
§ This sensor requires 588 the probe system to be part of the domain whose Active Directory you want to
monitor.
§ This sensor requires Microsoft .NET 4.7.2 or later on the probe system. If the sensor shows the error
PE087, you must additionally install .NET 3.5 on the probe system.
§ This sensor requires credentials for Windows systems in the settings of the parent device.
§ We recommend Windows Server 2012 R2 on the probe system for best performance of this sensor.
§ This sensor supports the IPv6 protocol.
§ This sensor uses lookups to determine the status values of one or more channels. This means that
possible states are defined in a lookup file. You can change the behavior of a channel by editing the
lookup file that the channel uses. For details, see section Define Lookups 3541 .
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.
Detailed Requirements
Requirement Description
.NET 4.7.2 or later This sensor requires .NET 4.7.2 or later to be installed on the probe
system (on every cluster node, if on a cluster probe).
If the framework is missing, you cannot create this sensor.
does PRTG require?
Member of Windows This sensor only works if the probe system is part of the domain whose
domain Active Directory you want to monitor. You must add the sensor to a device
that represents the DC.
Windows credentials This sensor requires credentials for Windows systems 542 in the settings
of the parent device. Preferably, 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 computer. Otherwise, the sensor cannot
correctly connect.
Add Sensor
The Add Sensor 391 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.
588
Setting Description
Replication Neighbor Select the replication neighbor whose replication connection you want to
monitor.
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.
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.
§ ForestDnsZones: Includes information about domain controllers in the
forest.
Basic Sensor Settings

Click the Settings tab of a sensor to change its settings.
Setting Description
Sensor Name Enter a name to identify the sensor. By default, PRTG shows this name in
589
Setting Description
Parent Tags Shows tags 146 that the sensor inherits 146 from its parent device 142 ,
parent group 141 , and parent probe 141 .
inherited 146 .
The sensor has the following default tags that are automatically predefined
in the sensor's settings when you add the sensor:
§ ptfsensor
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 ( ).
Usually, a sensor connects to the IP Address/DNS Name of the parent device. See the device
settings 535 for details. For some sensors, you can explicitly define the monitoring target in the
sensor settings.
Sensor Settings
Sensor Settings
590
Setting Description
Replication Neighbor Shows the replication neighbor whose replication connection this sensor
monitors.
PRTG shows this value for reference purposes only. If you need to
change this value, add the sensor anew.
Naming Context Shows the Active Directory naming context that this sensor monitors.
Debug Options
Debug Options
Setting Description
Result Handling Define what PRTG does with the sensor result:
§ Discard result: Do not store the sensor result.
§ Store result: Store the last sensor result in the \Logs\sensors subfolder
of the PRTG data directory 3579 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
591
Setting Description
Primary Channel Select a channel from the list to define it as the primary channel. In the
device tree, the last value of the primary channel is always displayed
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.
Graph Type Define how different channels are shown for this sensor:
§ 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 3052 ).
Stack Unit This setting is only visible if you enable Stack channels on top of each
other as Graph Type. Select a unit from the list. All channels with this unit
are stacked on top of each other. By default, you cannot exclude single
channels from stacking if they use the selected unit. However, there is an
advanced procedure to do so.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
592
For more information, see section Root Group Settings 420 , section Schedules, Dependencies, and
Maintenance Window.
Access Rights
Access Rights
For more information, see section Root Group Settings 421 , section Access Rights.

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.
593
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 in percent.
Is Deleted Source If the source is deleted

§ Up status 186 : 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


594
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.
The sensor can monitor any data source that is available via Object Linking and Embedding,
Database or Open Database Connectivity (ODBC).
ADO SQL v2 Sensor
List 608 .

§ 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
595
§ This sensor requires Microsoft .NET 4.7.2 or later on the probe system.
§ You must store your Structured Query Language (SQL) query in a file on the probe system. In a
cluster, copy the file to every cluster node.
§ Define credentials, custom port (if required), and timeout in the credentials for database management
systems 551 settings of the parent device, or in the settings of a group or probe above.
§ If you use an ODBC connection, you must define the ODBC connection in the Windows ODBC
Connection Manager first. If it is a 64-bit Windows, you must define the ODBC connection as an
ODBC 32-bit connection.
§ See section Monitoring Databases 3386 for an example 3387 for channel value selection.
§ See the Knowledge Base: How to set up the SQL v2 sensors in PRTG? Is there a guide?
§ See the Knowledge Base: How can I monitor strings from an SQL database and show a sensor status
depending on it?
§ See the Knowledge Base: How can I monitor error tables in SQL databases?
§ See the Knowledge Base: Why do I have to store SQL sensor queries and custom scripts in files on
the probe computer?

does PRTG require?
Add Sensor
Database Specific
Setting Description
Connection String Enter the connection string that the sensor uses to connect to the
database. A connection string can look like this, for example:
596
Setting Description
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 551 of the parent device.
Data
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 3579 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 the 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?
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.
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 data channel, so
you see all available settings for Channel #1. Specify how to handle all
other possible channels:
597
Setting Description
§ 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.
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 (recommended): 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.
Channel #x Unit This setting is only visible if you select Process data table above. Define
the unit of the channel value:
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
598
Setting Description
§ Custom
§ Lookup
For more information about the available units, see section Custom
Sensors 3501 .
To use lookups 3541 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.

Setting Description
Sensor Name Enter a name to identify the sensor.
inherited 146 .
599
Setting Description
§ sqlsensor
sensor settings.
Database Specific
Database Specific
Setting Description
Connection String Shows the string that the sensor uses to connect to the database. You
can change the string if necessary.
Data
Sensor Display
Setting Description
SQL Query File Shows the SQL script file that the sensor executes on the server.
600
Setting Description
Input Parameter Handling Define if you want to pass a parameter to the SQL query file:
§ Do not use input 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 Input Parameter Handling above.
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 details, see section Custom Sensors 3508 .
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 Shows how the sensor processes data from the database.
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 a Down status if the query returns DBNull.
§ Number 0: Recognize the result DBNull as a valid value and interpret it

as the number 0.
Select Channel Value by This setting is only visible if you select Process data table for the setting
Data Processing during sensor creation. Define how to select the desired
cell in the database table:
601
Setting Description
§ 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 details, see
setting Use Data Table Value in Sensor Message.
For an example for channel value selection, see section Monitoring
Databases 3387 .
Channel #x This setting is only visible if you select Process data table for the setting
Data Processing during sensor creation. The setting shows if the channel
is disabled.
Channel #x Name This setting is only visible if you select Process data table for the setting
Data Processing during sensor creation. Enter a name for the channel.
Enter a string. Enter a name for the channel. Enter a string. The sensor
dynamically generates channels with this name as identifier.
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 for
the setting Select Channel Value by. Provide the name of the column to
use to determine the channel value in row 0. Enter an integer.
602
Setting Description
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. Provide the number of the column to
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
for the setting Select Channel Value by. 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 for the setting
Data Processing during sensor creation. The setting shows how you want
to display the determined value in the channel.
Channel #x Unit This setting is only visible if you select Process data table for the setting
Data Processing during sensor creation. Define the unit of the channel
value:
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
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.
603
Setting Description
Channel #x Lookup This setting is only visible if you select the channel unit Lookup above.
Select a lookup 3541 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
Sensor 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.
Sensor 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 number for
the setting Select Channel Value by, and if you enable Use Data Table
Value in Sensor Message. Enter the number of a column. The sensor
message shows the value in row 0 of this column. Enter an integer.
Name Data Processing during sensor creation, if you select Column name for
Value in Sensor Message. 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.
Sensor Message Row This setting is only visible if you select Process data table for the setting
Number Data Processing during sensor creation, if you select Row number for the
setting Select Channel Value by, and if you enable Use Data Table Value
in Sensor Message. Enter the name of a column. The sensor message
shows the value in row 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.
Sensor 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
Value in Sensor Message. 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.
Sensor Message This setting is only visible if you enable Use Data Table Value in Sensor
Message. 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}
604
Setting Description
The number sign (#) is not supported in sensor messages. If a

message contains a number sign, the message is clipped at this
point.
If Sensor Message This setting is only visible if you select Process data table for the setting
Changes Data Processing during sensor creation.
Define what the sensor does when the sensor message changes:
§ Ignore changes (default): Take no action on change.
§ Trigger 'change' notification: Send an internal message indicating that

the sensor value has changed. In combination with a change trigger 3182 ,
you can use this mechanism to trigger a notification 3063 whenever the
sensor value changes.
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
Setting Description
605
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
606
Maintenance Window.

Access Rights
Access Rights
607
Channel List
Channel Description
Affected Rows The number of rows that were addressed by the query (including SELECT
statements if you process data tables)
Execution Time The execution time of the entire request (including connection buildup,
query execution, transaction handling, disconnection) in milliseconds
(msec)
Query Execution Time The execution time of the specified query in msec
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?
608
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?


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

609
7.8.3 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 the Amazon
CloudWatch Alarm sensor, you must update it. For more information, see the Knowledge Base:
PRTG?
If you monitor an AWS alarm that is based on a metric math expression, the 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 List of Supported AWS Regions and Their
Codes 3756 .
List 617 .

§ Dutch: AWS Alarm v2
§ French: AWS Alarm v2
§ German: AWS Alarm v2
§ Japanese: AWS Alarm v2
§ Portuguese: AWS Alarm v2
610
§ Russian: AWS Alarm v2
§ Simplified Chinese: AWS Alarm v2
§ Spanish: AWS Alarm v2
Remarks
§ This sensor requires credentials for AWS 553 in settings that are higher in the object hierarchy 140 , for
example, in the settings of the parent device.
§ This sensor requires permissions 611 for the AWS API key.
§ Amazon charges 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).
§ This sensor supports MetricAlarm and CompositeAlarm.
§ This sensor has a low performance impact.
Credentials for AWS This sensor requires credentials for AWS 553 in settings that are higher in
the object hierarchy 140 , for example, in the settings of the parent device.
Permissions for the AWS This sensor requires sufficient rights to query data from the AWS API
API key
For more information, see the Knowledge Base: How do I set
permissions for the Amazon Web Services (AWS) API key to use
Add Sensor
PRTG looks for available AWS alarms.
This can take up to several minutes.
The settings that you select in the Add Sensor dialog are valid for all sensors that you create when
you finish the dialog.
AWS Alarm Specific
611
Setting Description
Name Select the AWS alarms that you want to monitor. PRTG creates one
sensor for each name that you select.
right corner.

Setting Description
inherited 146 .
612
Setting Description
§ aws
§ cloudwatch
§ alarm
§ cloudwatchsensor
sensor settings.
AWS Alarm Specific
AWS Alarm Specific
Setting Description
Name Shows the name of the AWS alarm that this sensor monitors.
Type Shows the type of the AWS alarm that this sensor monitors.
Description Shows the description of the AWS alarm that this sensor monitors.
613
Setting Description
Region Shows the region in which the AWS alarm that this sensor monitors
occurs.
For a list of regions that this sensor supports, see section List of
Supported AWS Regions and Their Codes 3756 .
Sensor Display
Sensor Display
Setting Description

614
Debug Options
Debug Options
Setting Description
of the PRTG data directory 3579 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
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 3233 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.
Scanning Interval
615

objects' settings.
Maintenance Window.
Access Rights
Access Rights

616
Channel List
Channel Description
Alarm State The status of the alarm

[Metric] The metric on which the alarm is based
More
Knowledge Base
PRTG?

617
7.8.4 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 625 .

§ Dutch: AWS Cost
§ French: AWS Cost
§ German: AWS Cost
§ Japanese: AWS Cost
§ Portuguese: AWS Cost
§ Russian: AWS Cost
618
§ Simplified Chinese: AWS Cost
§ Spanish: AWS Cost
Remarks
§ This sensor requires the AWS Cost Explorer to be activated in your AWS account.
§ This sensor requires IAM User and Role Access to Billing Information enabled in your AWS account.
§ After sensor creation, the first data is available after 24 hours. Forecast data is available after a few
days.
§ The recommended scanning interval for this sensor is 6 hours. You can use a shorter scanning interval
but it could create extra costs.
§ Amazon charges you for each API call that the sensor sends to the Amazon servers. For more
information, see AWS Cost Management Pricing | Amazon Simple Storage Service.
§ You can only set up this sensor for one AWS account per PRTG installation.
§ See the Knowledge Base: What settings do I have to define in my AWS account to set up the AWS
Cost sensor?
§ See the Knowledge Base: How do I set permissions for the Amazon Web Services (AWS) API key to
use certain sensors in PRTG?
Permissions for the AWS This sensor requires sufficient rights to query data from the AWS API The
API key AWS API key requires the following permissions:
§ "ce:GetCostAndUsage"
§ "ce:GetCostForecast"
§ "ce:GetDimensionValues"
§ "ce:GetCostAndUsageWithResources"
§ "ce:GetUsageForecast"

619
Add Sensor

Setting Description
inherited 146 .
§ aws
§ cost
§ awscost
620
Setting Description
sensor settings.
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.
Select Additional Cost This setting is only visible if you select Enable for Additional Cost Types
Types above. 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.
Select Additional This setting is only visible if you select Enable for Additional Cost Types
Forecast Types above. Select additional forecast types:
§ Blended cost
621
Setting Description
§ Amortized cost
§ Net amortized cost
§ Unblended cost
§ 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

622
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
The minimum scanning interval of this sensor is 1 hour.
The recommended scanning interval of this sensor is 6 hours.
Scanning Interval
623

objects' settings.
Maintenance Window.
Access Rights
Access Rights

624
Channel List
Channel Description
Amortized Monthly The amortized cost per month
Amortized Yearly The amortized cost per year
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
625
Channel Description
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
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?

626
7.8.5 AWS EBS v2 Sensor
The AWS EBS v2 sensor monitors the performance of an Elastic Block Store (EBS) volume by reading
its data from Amazon CloudWatch via the AWS API.
CloudWatch EBS 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?
AWS EBS v2 Sensor
For a list of metrics that this sensor supports, see section Supported Metrics 634 .
For a list of dimensions that this sensor supports, see section Supported Dimensions 634 .
Codes 3756 .
List 634 .
627
§ 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
API key
Add Sensor
628
PRTG looks for available volumes.
AWS EBS Specific
Setting Description
ID Select the volumes that you want to monitor. PRTG creates one sensor
for each volume that you select.
right corner.

Setting Description
629
Setting Description
inherited 146 .
§ aws
§ cloudwatch
§ cloudwatchsensor
§ ebs
sensor settings.
AWS EBS Specific
AWS EBS Specific
Setting Description
ID Shows the ID of the Amazon EBS volume that this sensor monitors.
630
Setting Description
Name Shows the name of the Amazon EBS volume that this sensor monitors.
Region Shows the region in which the Amazon EBS instance runs.
Sensor Display
Sensor Display
Setting Description

631
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval
632

objects' settings.
Maintenance Window.
Access Rights
Access Rights

633
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)
§ VolumeWriteOps (Sum)
Supported Dimensions
The AWS EBS v2 sensor supports the following dimensions:
§ Volume
Channel List
634
Channel Description
Average Queue Length The average queue lengths
Average Read Latency The average read latency in milliseconds (msec)
Average Write Latency The average write latency in msec
Burst Balance The burst balance in percent
Read Bandwidth The read bandwidth in KB/s
Read Throughput The read throughput in input/output operations per second (IOPS)
Time Spent Idle The time spent idle in percent
Volume State The volume status

§ Up status 186 : Available, In Use
§ Warning status: Creating, Deleting, Deleted
§ Down status: Error
§ Unknown status: Not Set
Write Bandwidth The write bandwidth in KB/s
Write Throughput The write throughput in IOPS
More
Knowledge Base
PRTG?

635
7.8.6 AWS EC2 v2 Sensor
The AWS EC2 v2 sensor monitors the performance of an Elastic Compute Cloud (EC2) instance by
reading its data from Amazon CloudWatch via the AWS API.
CloudWatch EC2 sensor, you must update it. For more information, see the Knowledge Base: How
AWS EC2 v2 Sensor
Codes 3756 .
List 644 .
636
§ 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
API key
Add Sensor
637
PRTG looks for available instances or auto scaling groups.
AWS EC2 Specific
Setting Description
ID Select the IDs that you want to monitor. PRTG creates one sensor for
each ID that you select.
right corner.

Setting Description
638
Setting Description
inherited 146 .
§ aws
§ cloudwatch
§ cloudwatchsensor
§ ec2
sensor settings.
AWS EC2 Specific
AWS EC2 Specific
Setting Description
ID Shows the ID of the AWS EC2 instance that this sensor monitors.
639
Setting Description
Name Shows the name of the AWS EC2 instance that this sensor monitors.
Region Shows the region in which the AWS EC2 instance runs.
Sensor Display
Sensor Display
Setting Description

640
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
The minimum scanning interval of this sensor is 5 minutes.
Scanning Interval
641

objects' settings.
Maintenance Window.
Access Rights
Access Rights

642
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)
§ NetworkOut (Average)
§ StatusCheckFailed (Average)
§ StatusCheckFailed_Instance (Average)
§ StatusCheckFailed_System (Average)
The AWS EC2 v2 sensor supports the following dimensions:
§ Instance
643
Channel List
Channel Description
CPU Credit Balance The CPU credit balance
CPU Credit Usage The CPU credit usage
CPU Utilization The CPU usage in percent

Disk Read The disk read speed in bytes
Disk Read Ops The number of disk read operations
Disk Write The disk write speed in bytes
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 in bytes
Network Out The outgoing network load in bytes
System Status The AWS EC2 system status

§ Up status: Passed
More
Knowledge Base
PRTG?
644

645
7.8.7 AWS ELB v2 Sensor
The AWS ELB v2 sensor monitors the performance of an Elastic Load Balancing (ELB) load balancer by
CloudWatch ELB sensor, you must update it. For more information, see the Knowledge Base: How
AWS ELB v2 Sensor
Codes 3756 .
List 654 .
646
§ 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
§ This sensor supports Application Load Balancer and Network Load Balancer.
API key
Add Sensor
PRTG looks for available load balancers.
647
AWS ELB Specific
Setting Description
Name Select the load balancers that you want to monitor. PRTG creates one
sensor for each load balancer that you select.
right corner.

Setting Description
inherited 146 .
648
Setting Description
§ aws
§ cloudwatch
§ elb
§ cloudwatchelb
sensor settings.
AWS ELB Specific
AWS ELB Specific
Setting Description
ID Shows the ID of the AWS ELB load balancer that this sensor monitors.
Name Shows the name of the AWS ELB load balancer that this sensor
monitors.
649
Setting Description
Type Shows the type of the AWS ELB load balancer that this sensor monitors.
Region Shows the region in which the AWS ELB load balancer runs.
Sensor Display
Sensor Display
Setting Description

650
Setting Description
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
651
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

652
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)
§ 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)
653
The AWS ELB v2 sensor supports the following dimensions:
§ Load Balancer
Channel List
Channel Description
Active Connection Count The total number of concurrent active Transmission Control Protocol (TCP)
connections
Active Flow Count The total number of concurrent flows
Consumed LCU's The number of load balancer capacity units (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 total number of new TCP connections
New Flow Count The total number of new flows
Peak Bytes Highest average throughput
Processed Bytes The total 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
654
Channel Description
Target Response Time The response time of the target
TCP Client Reset Count The total number of reset (RST) packets sent from a client to a target
TCP ELB Reset Count The total RST packets generated by the load balancer
TCP Target Reset Count The total RST packets sent from a target to a client
Unhealthy Host Count The number of targets that are considered unhealthy
More
Knowledge Base
PRTG?

655
7.8.8 AWS RDS v2 Sensor
The AWS RDS v2 sensor monitors the performance of a Relational Database Service (RDS) database by
If you use the same Identity and Access Management (IAM) policy that you use for theAmazon
CloudWatch RDS sensor, you must update it. For more information, see the Knowledge Base: How
AWS RDS v2 Sensor
Codes 3756 .
656
List 664 .

§ 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
API key
Add Sensor
657
PRTG looks for available databases.
AWS RDS Specific
Setting Description
Name Select the load balancers that you want to monitor. PRTG creates one
sensor for each name that you select.
right corner.

Setting Description
658
Setting Description
inherited 146 .
§ aws
§ cloudwatch
§ rds
§ cloudwatchsensor
sensor settings.
AWS RDS Specific
AWS RDS Specific
Setting Description
Database Identifier Shows the database identifier of the Amazon RDS database that this
sensor monitors.
659
Setting Description
Engine Shows the engine family name of the Amazon RDS database that this
sensor monitors.
Region Shows the region in which the Amazon RDS instance runs.
Sensor Display
Sensor Display
Setting Description

660
Setting Description
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
661
The minimum scanning interval of this sensor is 5 minutes.
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

662
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)
§ 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)
663
The AWS RDS v2 sensor supports the following dimensions:
§ DBInstanceIdentifier
Channel List
Channel Description
Bin Log Disk Usage The bin log disk usage in bytes
CPU Credit Balance The CPU credit balance
CPU Credit Usage The CPU credit usage

Database Connections The number of database connections in use in percent
Disk Queue Depth The number of outstanding I/Os (read/write requests) waiting to access
the disk
Free Storage Space The amount of available storage space in bytes
Freeable Memory The freeable memory in bytes
Network Receive The incoming (receive) network traffic in bytes per second
Throughput
Network Transmit The outgoing (transmit) network traffic in bytes per second
Throughput
Read IOPS The average number of disk read I/O operations per second
Read Latency The read latency in milliseconds (msec)
Read Throughput The average number of bytes read from disk per second
664
Channel Description
Replica Lag The amount of time a read replica DB instance lags behind the source DB
instance in seconds
Swap Usage The swap usage in bytes
Write IOPS The average number of disk write I/O operations per second
Write Latency The average amount of time taken per disk I/O operation in msec
Write Throughput The number of disk write operations per second
More
Knowledge Base
PRTG?

665
7.8.9 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 671 .

§ Dutch: Beckhoff IPC System Health
§ French: Beckhoff IPC System Health
§ German: Beckhoff IPC System Health
§ Japanese: Beckhoff IPC System Health
§ Portuguese: Beckhoff IPC System Health
§ Russian: Beckhoff IPC System Health
§ Simplified Chinese: Beckhoff IPC System Health
§ Spanish: Beckhoff IPC System Health
666
Remarks
§ This sensor requires a valid port for the connection to the OPC UA server. Enter the port and,
depending on the configuration, further credentials in the credentials for OPC UA 562 section in the
settings of the parent device.

Setting Description
inherited 146 .
§ opcua
667
Setting Description
Sensor Display
Sensor Display
Setting Description

Debug Options
Debug Options
668
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
669
Maintenance Window.
Access Rights
Access Rights

670
Channel List
Channel Description
Available Memory The available memory in bytes
Available Memory % The available memory in percent
CPU % The CPU load in percent
CPU Temperature The temperature of the CPU in degree Celsius
Mainboard Temperature The temperature of the mainboard in degree Celsius
RAID Controller Status The status of the RAID controller

§ Up status: Good
§ Warning status: Offline
§ Unknown status: Power Off
More
Knowledge Base

671
7.8.10 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 sensor 1857 instead.
Business Process Sensor
List 680 .

§ Dutch: Bedrijfs Proces
§ French: Processus métier
§ German: Business Process
§ Japanese:
§ Portuguese: Processo empresarial
§ Russian: Бизн ес-п ро цесс
672
§ Spanish: Proceso empresarial
Remarks
§ This sensor does not officially support more than 50 channels. Depending on the data used with this
sensor, you might exceed the maximum number of supported channels. In this case, PRTG tries to
display all channels. Be aware, however, that you experience limited usability and performance.
§ This sensor has a medium performance impact.
§ See the Knowledge Base: How does the Business Process sensor calculate summarized sensor
states?
Add Sensor

Setting Description
673
Setting Description
inherited 146 .
§ factorysensor
§ businessprocesssensor
sensor settings.
Business Process Specific Settings
Business Process Specific Settings
674
Setting Description
Channel Name Enter a name for the channel.. To add a new channel to the 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 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 186 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 676 ).
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 676 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 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
675
Setting Description
§ Warning
§ Unusual
§ Down (Partial)
PRTG maps all other sensor states to the "down" condition (see Up and
Down Conditions 676 ).
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 676 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 225 . You can also start to type the object's ID, name, or a
tag. PRTG then suggests the possible objects.
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 a
Status Condition specific Business Process condition?
Up Up The monitored object works, so everything is fine.
676
Channel Object Business Process Reason: Why does a specific sensor status correspond to a
Status Condition specific Business Process condition?
Up The sensor might show a warning, but the monitored object

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

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
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 3330 , send us your exact configuration. Click in the upper-right corner of the
Business Process Specific Settings table to copy your configuration:
677
The Business Process Sensor Configuration Clipboard
A window opens that contains your configuration. Copy the highlighted text and paste it into the support
form 3330 to send it to the Paessler support team.
Sensor Display
Sensor Display
Setting Description
678
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
679
Maintenance Window.
Access Rights
Access Rights
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 186 : 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.
680
Channel Description
Global State The overall and summarized status of all channels in the Global State
channel
§ Up status: Up
§ Down status: Down
§ 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?

681
7.8.11 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 688 .

§ Dutch: Cisco IP SLA
§ French: Cisco IP SLA
§ German: Cisco IP SLA
§ Japanese: Cisco IP SLA
§ Portuguese: Cisco IP SLA
§ Russian: Cisco IP SLA
§ Simplified Chinese: Cisco IP SLA
§ Spanish: Cisco IP SLA
682
Remarks
§ In certain cases, the object identifiers (OID) that the sensor uses are not available on the target device.
The sensor shows the following error message: No such object (SNMP error # 222). If you encounter
this issue, open the SNMP Compatibility Options setting 571 of the parent device or group and set the
Request Mode to Use single get.
§ 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.
§ This sensor only supports the IPv4 protocol.
Add Sensor
IP SLA Specific
Setting Description
IP SLAs Select the IP SLAs that you want to monitor. PRTG creates one sensor
for each SLA that you select.
The list options depend on the configuration of the target device that you
query. If a type is missing, check the configuration of the target device.
The 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)
683
Setting Description
§ dlsw (10)
§ dhcp (11)
§ ftp (12)
§ icmp-jitter (16)
§ path-jitter (23)
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 first column of the list. If
the target device returns other values, the 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.
right corner.

Setting Description
684
Setting Description
inherited 146 .
§ ipslasensor
sensor settings.
IP SLA Specific
IP SLA Specific
Setting Description
ID
Shows the ID of the SLA that this sensor monitors.
685
Setting Description
Type Shows the type of the SLA that this sensor monitors.
Name (Tag) Shows the name of the SLA that this sensor monitors.
Owner Shows the owner of the SLA that this sensor monitors.
Frequency Shows the frequency of the SLA that this sensor monitors.
Sensor Display
Sensor Display
Setting Description
686
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
687
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Avg. Jitter The average jitter in milliseconds (msec)
Avg. Jitter Destination - The average jitter between destination and source in msec
Source
Avg. Jitter Source - The average jitter between source and destination in msec
Destination
Avg. Latency Destination The average latency between destination and source in msec
- Source
Avg. Latency Source - The average latency between source and destination in msec
Destination
688
Channel Description
Average Round Trip Time The average round-trip time (RTT) in msec
(RTT)
ICPIF The Impairment Calculated Planning Impairment Factor (ICPIF)
Late Packets The number of late packets
Max. Latency Destination The maximum latency between destination and source in msec
- Source
Max. Latency Source - The maximum latency between source and destination in msec
Destination
Max. RTT The maximum RTT in msec
Min. Latency Destination The minimum latency between destination and source in msec
- Source
Min. Latency Source - The minimum latency between source and destination in msec
Destination
Min. RTT The minimum RTT in msec
MOS The mean opinion score (MOS)
Packets Lost The number of lost packets
Packets Lost % The number of lost packets in percent
Packets Lost The number of out-of-sequence packets
More
Knowledge Base

689
7.8.12 Cisco Meraki License Sensor (BETA)
The Cisco Meraki License sensor monitors Meraki licenses of an organization via the Cisco Meraki
Dashboard API.
This sensor is in beta status. The operating methods and the available settings can change at
any time. Do not expect that all functions work properly, or that this sensor works as expected at
all. Be aware that this sensor can be removed from PRTG at any time.
Cisco Meraki License Sensor
List 696 .

§ Dutch: Cisco Meraki License
§ French: Cisco Meraki License
§ German: Cisco Meraki License
§ Japanese: Cisco Meraki License
§ Portuguese: Cisco Meraki License
§ Russian: Cisco Meraki License
§ Simplified Chinese: Cisco Meraki License
§ Spanish: Cisco Meraki License
690
Remarks
§ This sensor requires that the access of an organization to the Cisco Meraki Dashboard API is enabled.
§ This sensor requires credentials for Cisco Meraki 554in settings that are higher in the object
hierarchy 140 , for example, in the settings of the parent device.
§ This sensor requires an API key with Cisco Meraki Dashboard API permissions.
§ This sensor has a very low performance impact.
Enabled Beta Sensors This sensor requires that the Beta Sensors experimental feature 3239 of
experimental feature PRTG is enabled.
For more information, see the Knowledge Base: What are beta
sensors and how can I use them?
Enabled organization API Cisco Meraki sensors require that the access of an organization to the
access Cisco Meraki Dashboard API is enabled. 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.
The API key inherits the permissions of the Cisco Meraki Dashboard
Administrator account that was used to generate the API key.
The API key that is used for the Cisco Meraki License sensor must
inherit the permissions of a Cisco Meraki Dashboard Administrator
account with at least Read-only admin permissions.
Add Sensor
PRTG looks for available organizations.
Cisco Meraki License Specific
691
Setting Description
Organization Select the organizations whose licenses you want to monitor. PRTG
creates one sensor for each organization that you select.
right corner.

Setting Description
inherited 146 .
692
Setting Description
§ cisco
§ license
§ meraki
Setting Description
Organization Shows the name of the organization that the monitored licenses belong to.
Sensor Display
Sensor Display
Setting Description
693
Setting Description

Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
694
Scanning Interval
The minimum scanning interval of this sensor is 10 seconds.
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
695
Channel List
Channel Description
Days to Expiration The days to expiration with a predefined lower warning limit (90 days) and
lower error limit (30 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
696
More
Knowledge Base
What are beta sensors and how can I use them?

697
7.8.13 Cisco Meraki Network Health Sensor (BETA)
The Cisco Meraki Network Health sensor monitors the health of Cisco Meraki network devices via the
Cisco Meraki Netw ork Health Sensor
List 704 .

§ Dutch: Cisco Meraki Network Health
698
§ French: Cisco Meraki Network Health
§ German: Cisco Meraki Network Health
§ Japanese: Cisco Meraki Network Health
§ Portuguese: Cisco Meraki Network Health
§ Russian: Cisco Meraki Network Health
§ Simplified Chinese: Cisco Meraki Network Health
§ Spanish: Cisco Meraki Network Health
Remarks
§ This sensor requires that the access of an organization to the Cisco Meraki Dashboard API is enabled.
§ This sensor requires credentials for Cisco Meraki 554in settings that are higher in the object
Enabled organization API Cisco Meraki sensors require that the access of an organization to the
access Cisco Meraki Dashboard API is enabled. 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.
The API key inherits the permissions of the Cisco Meraki Dashboard
Administrator account that was used to generate the API key.
Add Sensor
PRTG looks for available networks.
Cisco Meraki Specific
699
Setting Description
Network Select the networks that you want to monitor. PRTG creates one sensor
for each network that you select.
right corner.

Setting Description
inherited 146 .
700
Setting Description
§ cisco
§ meraki
Setting Description
Network Shows the name of the network that this sensor monitors.
Organization Shows the name of the organization that the monitored network belongs
to.
Sensor Display
Sensor Display
701
Setting Description

Debug Options
Debug Options
Setting Description
master node.
702
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
703
Access Rights
Access Rights

Channel List
Channel Description
704
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

Uplinks "Failed" Uplinks in failed status
Uplinks "Not Connected" Uplinks in not connected status
Uplinks "Ready" Uplinks in ready status
705
More
Knowledge Base

706
7.8.14 Citrix XenServer Host Sensor
The Citrix XenServer Host sensor monitors a Xen host server via HTTP.
Citrix XenServer Host Sensor
List 713 .

§ 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
707
§ Spanish: Host Citrix XenServer
Remarks
§ The parent device must be a Citrix XenServer version 5.0 or later.
§ The parent device must represent one host server of your XenServer pool.
§ This sensor requires credentials for VMware/XenServer 547 in the settings of the parent device.
§ This sensor does not fully support Transport Layer Security (TLS) 1.2 connections and cannot be
added to XenServers with the security protocol setting "TLS 1.2 only".
does PRTG require?
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.
Add Sensor
Host Settings
708
Setting Description
Hosts Select the XenServer hosts that you want to monitor, including hosts that
do not run. PRTG creates one sensor for each host that you select.
right corner.

Setting Description
inherited 146 .
709
Setting Description
§ xenhostsensor
sensor settings.
Host Settings
Host Settings
Setting Description
UUID Shows 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 Shows the name of the host that this sensor monitors.
Debug Options
Debug Options
710
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

711
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
712
Access Rights
Access Rights
Channel List
Channel Description
CPU [Value] Usage The CPU usage in percent

Load Average The load average amount
VMs Running The number of running virtual machines (VM)
Total Memory Free The total memory available in bytes
Total Memory Used The total memory used in bytes
More
Knowledge Base


Does PRTG impair my Citrix environment?

713
7.8.15 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 720 .

§ 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
§ The parent device must be a Citrix XenServer version 5.0 or later.
§ The parent device must represent one host server of your XenServer pool.
714
§ This sensor requires credentials for VMware/XenServer 547 in the settings of the parent device.
§ This sensor does not fully support Transport Layer Security (TLS) 1.2 connections and cannot be
added to XenServers with the security protocol setting "TLS 1.2 only".
does PRTG require?
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.
Add Sensor
PRTG requests a full list of all VMs that are configured on the Citrix XenServer. Therefore, it may
take a few seconds before the dialog loads.
Virtual Machine Settings
Setting Description
Virtual Machines Select the VMs that you want to monitor, including VMs that do not run.
PRTG creates one sensor for each VM that you select.
715
Setting Description

right corner.

Setting Description
inherited 146 .
§ xenhostsensor
716
Setting Description
sensor settings.
Setting Description
UUID Shows the universally unique identifier (UUID) of the VM that this sensor
monitors.

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

718
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
719
Access Rights
Access Rights
Channel List
Channel Description
CPU [Value] Usage The CPU usage in percent

Memory Available The available memory in bytes
Memory Used The used memory in bytes
VM Balloon Driver Target The balloon driver target size in bytes
More
Knowledge Base



720
7.8.16 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 729 .

§ Dutch: Cloud HTTP v2
§ French: Cloud HTTP v2
§ German: Cloud HTTP v2
§ Japanese: Cloud HTTP v2
§ Portuguese: Cloud HTTP v2
§ Russian: Cloud HTTP v2
§ Simplified Chinese: Cloud HTTP v2
721
§ Spanish: Cloud HTTP v2
Remarks
§ The probe system must have access to the internet and must be able to reach
https://api.prtgcloud.com:443 to communicate with the PRTG Cloud.
§ The address that you define in the settings of the parent device must be reachable over the
536
internet. You cannot use this sensor to monitor localhost (127.0.0.1).

§ This sensor inherits proxy settings for HTTP sensors 576 from the parent device.
§ To use this sensor to monitor a probe system, enter the URL of the probe system that is reachable
over the internet as Custom URL in the Cloud HTTP Specific 724 settings or add a device with the URL
in the settings of the device.
§ This sensor supports smart URL replacement.
§ This sensor has predefined limits for several metrics. You can individually change these limits in the
channel settings. For detailed information about channel limits, see section Channel Settings 3052 .
§ See the Knowledge Base: What is the PRTG Cloud Bot?
Add Sensor

Setting Description
722
Setting Description
inherited 146 .
§ cloud
§ cloudhttpsensor
§ http
sensor settings.
723
Cloud HTTP Specific
Cloud HTTP Specific
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 option is only visible if you select Custom above. Enter a custom
URL that the sensor connects to.
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 728 .
724
Setting Description
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 option is only visible if you select POST as Request Method 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)
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
725
Setting Description

Debug Options
Debug Options
Setting Description
master node.
726
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
727
Access Rights
Access Rights

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.mycompany.com and you add an HTTP
sensor to it, you can provide values in the following ways:
728
§ If you enter https:/// in the URL field, PRTG automatically creates the URL
https://www.mycompany.com/
§ If you enter /help in the URL field, PRTG automatically creates and monitor the URL
http://www.mycompany.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 in msec
Asia Pacific (Singapore) - The response code of the target server at the location
HTTP Response Code
Asia Pacific (Singapore) - If the query of the PRTG Cloud was successful or not:
PRTG Cloud Response
§ Up status: OK
Asia Pacific (Sydney) The response time of the target server at the location in msec
Asia Pacific (Sydney) - The response code of the target server at the location
HTTP Response Code
Asia Pacific (Sydney) - If the query of the PRTG Cloud was successful or not:
PRTG Cloud Response
§ Up status: OK
Europe (Ireland) The response time of the target server at the location in msec
Europe (Ireland) - HTTP The response code of the target server at the location
Response Code
Europe (Ireland) - PRTG If the query of the PRTG Cloud was successful or not:
Cloud Response
§ Up status: OK
729
Channel Description
Global Average The global average in msec

US East (Northern The response time of the target server at the location in msec
Virginia)
US East (Northern The response code of the target server at the location
Virginia) - HTTP
Response Code
US East (Northern If the query of the PRTG Cloud was successful or not:
Virginia) - PRTG Cloud
§ Up status: OK
Response
US West (Northern The response time of the target server at the location in msec
California)
US West (Northern The response code of the target server at the location
California) - HTTP
Response Code
US West (Northern If the query of the PRTG Cloud was successful or not:
California) - PRTG Cloud
§ Up status: OK
Response
More
Knowledge Base
What is the PRTG Cloud Bot?


730
7.8.17 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. These locations are distributed among four
continents around the globe.
Cloud Ping v2 Sensor
List 738 .

§ Dutch: Cloud Ping v2
§ French: Cloud Ping v2
§ German: Cloud Ping v2
§ Japanese: Cloud Ping v2
§ Portuguese: Cloud Ping v2
§ Russian: Cloud Ping v2
§ Simplified Chinese: Cloud Ping v2
§ Spanish: Cloud Ping v2
731
Remarks
§ This sensor uses Transmission Control Protocol (TCP) ping.
§ The probe system must have access to the internet and must be able to reach
https://api.prtgcloud.com:443 to communicate with the PRTG Cloud.
§ The address that you define in the settings of the parent device must be reachable over the
536
internet. You cannot use this sensor to monitor localhost (127.0.0.1).

§ To use this sensor to monitor the probe system, enter the IP address or the fully qualified domain
name (FQDN) of the probe system that is reachable over the internet as Custom Target Address in the
Cloud Ping Specific 734 settings or add a device with the IP address or the DNS name of the probe
system.
§ See the Knowledge Base: What is the PRTG Cloud Bot?
Add Sensor

Setting Description
732
Setting Description
inherited 146 .
§ cloud
§ cloudpingsensor
§ ping
sensor settings.
733
Cloud Ping Specific
Cloud Ping Specific
Setting Description
Target Address Select if you want to inherit the IP address or the fully qualified domain
name (FQDN) from the parent device or if you want to enter a custom
target address:
§ Inherit (default)
§ Custom
Custom Target Address This option 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 the 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:
734
Setting Description
§ Asia Pacific (Singapore)
§ Asia Pacific (Sydney)
§ Europe (Ireland)
§ US East (Northern Virginia)
§ US West (Northern California)
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
Setting Description

735
Setting Description
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
736
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

737
Channel List
Channel Description
Asia Pacific (Singapore) The response time of the target server at the location in msec
Asia Pacific (Singapore) - If the query of the PRTG Cloud was successful or not:
PRTG Cloud Response
§ Up status: OK
Asia Pacific (Sydney) The response time of the target server at the location in msec
Asia Pacific (Sydney) - If the query of the PRTG Cloud was successful or not:
PRTG Cloud Response
§ Up status: OK
Europe (Ireland) The response time of the target server at the location in msec
738
Channel Description
Europe (Ireland) - PRTG If the query of the PRTG Cloud was successful or not:
Cloud Response
§ Up status: OK
Global Average The global average response time in msec

US East (Northern The response time of the target server at the location in msec
Virginia)
US East (Northern If the query of the PRTG Cloud was successful or not:
Virginia) - PRTG Cloud
§ Up status: OK
Response
US West (Northern The response time of the target server at the location in msec
California)
US West (Northern If the query of the PRTG Cloud was successful or not:
California) - PRTG Cloud
§ Up status: OK
Response
More
Knowledge Base
What is the PRTG Cloud Bot?


739
7.8.18 Cluster Health Sensor
The Cluster Health sensor monitors the health of a failover cluster 137 and indicates the system health
status of PRTG.
Cluster Health Sensor
List 743 .

§ Dutch: Cluster Status
§ French: État du cluster
§ German: Cluster-Zustand
§ Japanese:
§ Portuguese: Funcionamento do cluster
§ Russian: Рабо то сп о со бн о сть кластера
§ Spanish: Salud de clúster
740
Remarks
§ PRTG automatically creates this sensor with a cluster installation. You cannot manually delete it or
add it.
§ If at least one cluster node is disconnected, this sensor shows the Down status 186 by default.
§ You can review the states of each cluster node on the sensor's Overview tab.
§ 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

Setting Description
inherited 146 .
741
Setting Description
§ clusterhealthsensor
sensor settings.
Sensor Display
Sensor Display
Setting Description

742
Inherited Settings
Scanning Interval
Scanning Interval
Access Rights
Access Rights
Channel List
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
Connects The number of connects per minute
743
Channel Description
Outbound Cluster The number of outbound cluster connections

Connections
More
Knowledge Base

744
7.8.19 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 749 .

§ Dutch: Algemene SaaS
§ French: SaaS courants
§ German: Verbreitete SaaS-Dienste
§ Japanese: Common SaaS
§ Portuguese: SaaS Comuns
§ Russian: О бщ ий для SaaS
§ Simplified Chinese: SaaS
745
§ Spanish: SaaS común
Remarks
§ The probe system must have access to the internet.
§ This sensor has a fixed scanning interval of 15 minutes. You cannot change it.
§ PRTG automatically creates this sensor on every probe device. If the probe system has no connection
to the internet, manually pause 230 or delete 246 this sensor to avoid error messages.
Add Sensor
Common SaaS Specific
Setting Description
SaaS Checklists Select the services that you want to monitor. The sensor creates one
channel for each service that you select.

746
Setting Description
inherited 146 .
§ commonsaas
§ saas
sensor settings.
Debug Options
Debug Options
Setting Description
747
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

748
Inherited Settings

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
749
Channel Description
Available Services The available services in percent

Bing The response time of the SaaS provider in milliseconds (msec)
Dropbox The response time of the SaaS provider in msec
Facebook The response time of the SaaS provider in msec
GitHub The response time of the SaaS provider in msec
Google Apps The response time of the SaaS provider in msec
Office 365 The response time of the SaaS provider in msec
Salesforce The response time of the SaaS provider in msec
Twitter The response time of the SaaS provider in msec
Youtube The response time of the SaaS provider in msec
More
Knowledge Base

750
7.8.20 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 755 .

§ Dutch: Core Status
§ French: État du serveur central
§ German: Serverzustand
§ Japanese:
§ Portuguese: Funcionamento do servidor central
751
§ Russian: Рабо то сп о со бн о сть базо во го сервера
§ Spanish: Salud de servidor central
Remarks
§ PRTG automatically creates this sensor. You cannot delete it.
§ You can only set up this sensor on a local probe device.
§ You can also find information related to PRTG core server system memory under Setup | PRTG
Status.

Setting Description
inherited 146 .
752
Setting Description
§ corehealthsensor
sensor settings.
Sensor Display
Sensor Display
Setting Description

753
Inherited Settings
Scanning Interval
Scanning Interval
Access Rights
Access Rights

754
Channel List
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 3323 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 in percent. Extensive CPU load can lead to false,
incomplete, and incorrect monitoring results. This value should usually
stay below 50%.
755
Channel Description
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.
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 core 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.
Renew your maintenance in time to make sure that you get updates 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 per second from all probes to the PRTG
Second core server
Raw Data Buffer The amount of raw data that is temporarily stored on the physical memory
during input/output (I/O) operations on the disk. Usually, this value should
be 0 (or very low). Investigate increasing values.
756
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

757
7.8.21 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 sensor 751 .
The only difference is that the Core Health (Autonomous) sensor runs independently of the probe.
This means that if the probe disconnects, the sensor still monitors the status of the PRTG core server.
Core Health (Autonomous) Sensor
List 762 .

§ Dutch: Core Health (autonoom)
§ French: État du serveur central (autonome)
§ German: Serverzustand (Autonom)
§ Japanese:
758
§ Portuguese: Funcionamento do servidor central (autônomo)
§ Russian: Рабо то сп о со бн о сть базо во го сервера (авто н о м н о )
§ Spanish: Salud de servidor central (autónomo)
Remarks
§ You cannot add this sensor to a probe.
§ You can also find information related to PRTG core server system memory under Setup | PRTG
Status.

Setting Description
inherited 146 .
759
Setting Description
§ corehealthsensor
§ autonomous
sensor settings.
Sensor Display
Sensor Display
Setting Description

760
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval
Access Rights
Access Rights

761
Channel List
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 3323 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 in percent. Extensive CPU load can lead to false,
incomplete, and incorrect monitoring results. This value should usually
stay below 50%.
762
Channel Description
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.
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 core state as a value between 100% (healthy) and 0%
Maintenance Days The remaining maintenance days of your PRTG Network Monitor license.
Renew your maintenance in time to make sure that you get updates 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 per second from all probes to the PRTG
Second core server
Raw Data Buffer The amount of raw data that is temporarily stored on the physical memory
during input/output (I/O) operations on the disk. Usually, this value should
be 0 (or very low). Investigate increasing values.
763
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

764
7.8.22 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 771 .

§ Dutch: Dell EMC Unity Enclosure Health v2
§ French: Dell EMC Unity Enclosure Health v2
§ German: Dell EMC Unity Enclosure Health v2
§ Japanese: Dell EMC Unity Enclosure Health v2
§ Portuguese: Dell EMC Unity Enclosure Health v2
§ Russian: Dell EMC Unity Enclosure Health v2
§ Simplified Chinese: Dell EMC Unity Enclosure Health v2
§ Spanish: Dell EMC Unity Enclosure Health v2
765
Remarks
§ This sensor requires credentials for Dell EMC 554 in settings that are higher in the object hierarchy 140 ,
for example, in the settings of the parent device.
§ This sensor only supports systems from the Dell EMC Unity family with Unity OE 5.x.
§ Dell EMC systems that provide a REST API are EMC Unity Family, EMC Unity All Flash, EMC Unity
Hybrid, and EMC UnityVSA.
Add Sensor
Dell EMC Specific
Setting Description
Enclosure Name Select the enclosure that you want to monitor.

right corner.

766
Setting Description
inherited 146 .
§ dellemc
§ dellemcstorage
§ dellemcenclosure
§ restsensor
sensor settings.
Dell EMC Specific
Dell EMC Specific
767
Setting Description
Enclosure Name Shows the name of the enclosure that the sensor monitors.
Enclosure Type Shows the type of the enclosure that the sensor monitors.
Sensor Display
Sensor Display
Setting Description

768
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval
769
objects' settings.
Maintenance Window.
Access Rights
Access Rights

770
Channel List
Channel Description
Cooling Modules The status of cooling modules

§ 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 status of drives

Health Status The health status
771
Channel Description
Power Consumption The power consumption in watts (W)
Link Control Cards The status of link control cards

Power Supplies The status of power supplies

Temperature The temperature in degree Celsius (°C)
More
Knowledge Base

772
7.8.23 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 779 .

§ Dutch: Dell EMC Unity File System v2
§ French: Dell EMC Unity File System v2
§ German: Dell EMC Unity File System v2
§ Japanese: Dell EMC Unity File System v2
§ Portuguese: Dell EMC Unity File System v2
§ Russian: Dell EMC Unity File System v2
§ Simplified Chinese: Dell EMC Unity File System v2
§ Spanish: Dell EMC Unity File System v2
Remarks
773
Add Sensor

Setting Description
inherited 146 .
774
Setting Description
§ dellemc
§ dellemcfilesystem
§ dellemcstorage
§ emcfilesystemsensor
§ emcsensor
§ restsensor
sensor settings.
Dell EMC Specific
Dell EMC Specific
Setting Description
File System Name Shows the name of the file system that the sensor monitors.
File System Type Shows the type of the file system that the sensor monitors.
Protocol Shows the protocol under which the monitored file system operates.
775
Setting Description
Sensor Display
Sensor Display
Setting Description

Debug Options
Debug Options
776
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
777
Maintenance Window.
Access Rights
Access Rights

778
Channel List
Channel Description
Allocated Size The allocated size in bytes
Free Size The free size in bytes
Free Size % The free size in percent

Snapshot Count The snapshot count
Snapshot Used Size The used snapshot size in bytes
Total Size The total size in bytes
More
Knowledge Base

779
7.8.24 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 785 .

§ Dutch: Dell EMC Unity Storage Capacity v2
§ French: Dell EMC Unity Storage Capacity v2
§ German: Dell EMC Unity Storage Capacity v2
§ Japanese: Dell EMC Unity Storage Capacity v2
§ Portuguese: Dell EMC Unity Storage Capacity v2
§ Russian: Dell EMC Unity Storage Capacity v2
§ Simplified Chinese: Dell EMC Unity Storage Capacity v2
§ Spanish: Dell EMC Unity Storage Capacity v2
780
Remarks
Add Sensor

Setting Description
inherited 146 .
781
Setting Description
§ dellemc
§ dellemccapacity
§ dellemcstorage
§ emccapacitysensor
§ emcsensor
§ restsensor
sensor settings.
Sensor Display
Sensor Display
Setting Description
782
Setting Description

Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
783
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
784
Channel List
Channel Description

Preallocated Size The preallocated size in bytes
Preallocated Size % The preallocated size in percent
Subscribed Size The subscribed size in bytes
785
Channel Description
Subscribed Size % The subscribed size in percent
Used Size The used size in bytes
Used Size % The used size in percent
More
Knowledge Base

786
7.8.25 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 793 .

§ Dutch: Dell EMC Unity Storage LUN v2
§ French: Dell EMC Unity Storage LUN v2
§ German: Dell EMC Unity Storage LUN v2
§ Japanese: Dell EMC Unity Storage LUN v2
§ Portuguese: Dell EMC Unity Storage LUN v2
§ Russian: Dell EMC Unity Storage LUN v2
§ Simplified Chinese: Dell EMC Unity Storage LUN v2
§ Spanish: Dell EMC Unity Storage LUN v2
Remarks
787
Add Sensor
PRTG performs a meta-scan before you can add this sensor and requires basic information in advance.
Provide the required information in the dialog box that appears. PRTG then recognizes all items that are
available for monitoring based on your input.
Dell EMC Specific
Setting Description
LUN Select the logical unit numbers (LUN) that you want to monitor. PRTG
creates one sensor for each LUN that you select.

right corner.

788
Setting Description
inherited 146 .
§ dellemc
§ dellemclun
§ dellemcstorage
§ emclunsensor
§ emcsensor
§ restsensor
sensor settings.
Dell EMC Specific
Dell EMC Specific
789
Setting Description
LUN Shows the name of the LUN that the sensor monitors.
LUN ID Shows the ID of the LUN that the sensor monitors.
Sensor Display
Sensor Display
Setting Description

790
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval
791
objects' settings.
Maintenance Window.
Access Rights
Access Rights

792
Channel List
Channel Description
Allocated Metadata Size The allocated metadata size in bytes
Allocated Size The allocated size in bytes
Allocated Snapshot Size The allocated snapshot size in bytes

793
Channel Description
More
Knowledge Base

794
7.8.26 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 801 .

§ Dutch: Dell EMC Unity Storage Pool v2
§ French: Dell EMC Unity Storage Pool v2
§ German: Dell EMC Unity Storage Pool v2
§ Japanese: Dell EMC Unity Storage Pool v2
§ Portuguese: Dell EMC Unity Storage Pool v2
§ Russian: Dell EMC Unity Storage Pool v2
§ Simplified Chinese: Dell EMC Unity Storage Pool v2
795
§ Spanish: Dell EMC Unity Storage Pool v2
Remarks
Add Sensor
Dell EMC Specific
Setting Description
Storage Pool Name Select the storage pools that you want to monitor. PRTG creates one
sensor for each storage pool that you select.
right corner.

796
Setting Description
inherited 146 .
§ dellemc
§ dellemcpool
§ dellemcstorage
§ emcpoolsensor
§ emcsensor
§ restsensor
797
sensor settings.
Dell EMC Specific
Dell EMC Specific
Setting Description
Storage Pool Name Shows the name of the storage pool that the sensor monitors.
Storage Pool ID Shows the ID of the storage pool that the sensor monitors.
Sensor Display
Sensor Display
Setting Description
798
Setting Description

Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
799
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
800
Channel List
Channel Description

801
Channel Description
Metadata Subscribed The subscribed metadata size in bytes

Size
Metadata Used Size The used metadata size in bytes
Preallocated Size The preallocated size in bytes
Preallocated Size % The preallocated size in percent
Snapshot Subscribed The subscribed snapshot size in bytes

Size
Subscribed Size The subscribed size in bytes
Subscribed Size % The subscribed size in percent
Used Size The used size in bytes
Used Size % The used size in percent
More
Knowledge Base

802
7.8.27 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 809 .

§ Dutch: Dell EMC Unity VMware Datastore v2
§ French: Dell EMC Unity VMware Datastore v2
§ German: Dell EMC Unity VMware Datastore v2
§ Japanese: Dell EMC Unity VMware Datastore v2
§ Portuguese: Dell EMC Unity VMware Datastore v2
§ Russian: Dell EMC Unity VMware Datastore v2
§ Simplified Chinese: Dell EMC Unity VMware Datastore v2
§ Spanish: Dell EMC Unity VMware Datastore v2
803
Remarks
Add Sensor
Dell EMC Specific
Setting Description
VMware Datastore Name Select the VMware datastores that you want to monitor. PRTG creates
one sensor for each VMware datastore that you select.
right corner.

804
Setting Description
inherited 146 .
§ dellemc
§ dellemcvmware
§ dellemcdatastore
§ emcsensor
§ restsensor
sensor settings.
Dell EMC Specific
Dell EMC Specific
805
Setting Description
VMware Datastore Name Shows the name of the VMware datastore that the sensor monitors.
VMware Datastore Type Shows the type of the VMware datastore that the sensor monitors.
Sensor Display
Sensor Display
Setting Description

806
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval
807
objects' settings.
Maintenance Window.
Access Rights
Access Rights

808
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
809
More
Knowledge Base

810
7.8.28 Dell PowerVault MDi Logical Disk Sensor
The Dell PowerVault MDi Logical Disk sensor monitors a virtual disk on a Dell PowerVault system.
The sensor supports Dell PowerVault MD3000i, MD3420, MD3620i, MD3000f, MD3620f, or
MD3820i. It might work with other models, too.
Dell Pow erVault MDi Logical Disk Sensor
List 817 .

§ 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
811
Remarks
§ This sensor requires Dell Modular Disk Storage Manager on the probe system. See the Knowledge
Base: Where do I find the Dell PowerVault Modular Disk Storage Manager for use with my MDi SAN?
§ This sensor requires the IP address of the storage area network (SAN) defined in the settings of the
parent device.
§ This sensor works with Dell PowerVault MD3000i, MD3420, MD3620i, MD3000f, MD3620f, or
MD3820i, and might support other models.
Dell Modular Disk This sensor requires the installation of the Dell Modular Disk Storage
Storage Manager Manager program. 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.
Add Sensor
Sensor Settings
Setting Description
Virtual Disks Select the virtual disks that you want to monitor. PRTG creates one
sensor for each virtual disk that you select.
812
Setting Description

right corner.

Setting Description
inherited 146 .
§ powervault
813
Setting Description
sensor settings.
Sensor Settings
Sensor Settings
Setting Description
Virtual Disk Shows the name of the virtual disk that this sensor monitors.
scanning interval.
master node.
Sensor Display
Sensor Display
814
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
815
Maintenance Window.
Access Rights
Access Rights

816
Channel List
Channel Description
Cache Hit Percentage The cache hits in percent
Current IOs The number of current input/output (I/O) operations per second
Current Speed The current disk speed per second
Maximum IOs The number of maximum I/O operations per second
Maximum Speed The maximum disk speed per second
Read Percentage The read operations in percent
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?

817
7.8.29 Dell PowerVault MDi Physical Disk Sensor
The Dell PowerVault MDi Physical Disk sensor monitors a physical disk on a Dell PowerVault system.
The sensor supports Dell PowerVault MD3000i, MD3420, MD3620i, MD3000f, MD3620f, or
MD3820i. It might work with other models, too.
Dell Pow erVault MDi Physical Disk Sensor
List 824 .

§ 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
§ This sensor requires Dell Modular Disk Storage Manager on the probe system. See the Knowledge
Base: Where do I find the Dell PowerVault Modular Disk Storage Manager for use with my MDi SAN?
818
§ This sensor requires the IP address of the storage area network (SAN) defined in the settings of the
parent device.
§ This sensor only supports devices with one drawer of hard-drives. Multiple drawers are not supported
and prevent sensor creation.
§ This sensor works with Dell PowerVault MD3000i, MD3420, MD3620i, MD3000f, MD3620f, or
MD3820i, and might support other models.
Dell Modular Disk This sensor requires the installation of the Dell Modular Disk Storage
Storage Manager Manager program. 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.
Add Sensor
Sensor Settings
Setting Description
Disk Select the physical disks that you want to monitor. PRTG creates one
sensor for each physical disk that you select.
right corner.
819
Setting Description
inherited 146 .
§ powervault
sensor settings.
820
Sensor Settings
Sensor Settings
Setting Description
Physical Disk Shows the physical disk that this sensor monitors.
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
821
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
822
Maintenance Window.
Access Rights
Access Rights

823
Channel List
The 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 186 : 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
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 incorrect
§ Unassigned
drive type or drive size, or by its operational
§ Hot Spare In Use 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 Self-Monitoring, Analysis and Reporting

Failure Technology (S.M.A.R.T.) error has been
§ Unassigned
detected on the physical disk in the indicated
§ Hot Spare In Use slot
§ Hot Spare Standby
Warning status: None None The indicated slot is empty, or the array cannot
detect the physical disk
Down status: Undefined
824
More
Knowledge Base
Where do I find the Dell PowerVault Modular Disk Storage Manager for use with my MDi SAN?
825
7.8.30 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.
The 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 3552 .
DHCP Sensor
List 833 .

§ Dutch: DHCP
§ French: DHCP
§ German: DHCP
§ Japanese: DHCP
§ Portuguese: DHCP
§ Russian: DHCP
§ Simplified Chinese: DHCP
§ Spanish: DHCP
Remarks
§ You can only create this sensor on a probe device, either a local probe device or a remote probe
device.
826
§ The probe device where you create a DHCP 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.
§ Your DHCP sensors show a timeout error if no DHCP is available, or if you use more than two DHCP
sensors per device.
§ Adding a DHCP 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.
§ 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 section Core & Probes 3252 .
§ See the Knowledge Base: How can I monitor a DHCP server in a specific network if there are several
DHCP networks?
Add Sensor
DHCP Specific
Setting Description
Network Interfaces Select the network interfaces that you want to monitor. PRTG creates one
sensor for each network interface that you select.
Choose the network card on the probe system that is used to send
the broadcast message.

right corner.

827
Setting Description
inherited 146 .
§ dhcpsensor
sensor settings.
828
DHCP Specific
DHCP Specific
Setting Description
MAC Address Shows 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 enable Check the IP address using a
Include (Down Status if regular expression above. In the response of the DHCP server, search by
Not Included) using a regex. If the response for the client IP address does not contain
this string, the sensor shows the Down status 186 .
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 details, see section Regular Expressions 3552 .
829
Setting Description
Client IP Address Must This setting is only visible if you enable Check the IP address using a
Not Include (Down Status regular expression above. In the response of the DHCP server, search by
if Included) using a regex. If the response for the client IP address contains this
string, the 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 enable Check the IP address using a
Include (Down Status if regular expression above. In the response of the DHCP server, search by
Not Included) using a regex. If the response for the server IP address does not contain
this string, the 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 enable Check the IP address using a
Not Include (Down Status regular expression above. In the response of the DHCP server, search by
if Included) using a regex. If the response for the server IP address contains this
string, the sensor shows the Down status. See the example above. Leave
this field empty if you do not want to use it.

If the reply takes longer than this value, the sensor cancels the
request and shows a corresponding error message.
DHCP Server Change 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 214 . Specify how PRTG
handles DHCP server changes:
§ Ignore: Do not write a log entry if the DHCP server changes.
830
Setting Description
§ 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.
Offered IP Address If the IP address offered by the DHCP server changes between two sensor
Change scans, PRTG can write an entry to the system logs 214 . Specify how
PRTG handles IP address changes:
§ Ignore: Do not write a log entry if the offered IP address changes.
§ 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
Setting Description

831
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
832
Access Rights
Access Rights
Channel List
Channel Description
Lease Time The lease time reported by the server
Response Time The response time in msec

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

833
7.8.31 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 the sensor to test your picture archiving and communication system (PACS), for
example.
DICOM Bandw idth Sensor
List 840 .

§ Dutch: DICOM Bandbreedte
§ French: Bande passante (DICOM)
§ German: DICOM-Bandbreite
§ Japanese: DICOM
§ Portuguese: Largura de banda DICOM
§ Russian: П ро п ускн ая сп о со бн о сть DICOM
§ Simplified Chinese: DICOM
§ Spanish: Anchura de banda DICOM
834
Remarks
does PRTG require?
Add Sensor

Setting Description
835
Setting Description
inherited 146 .
§ dicom
§ bandwidth
sensor settings.
DICOM Connection
DICOM Connection
836
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.
Bandwidth Settings
Bandw idth Settings
Setting Description
File Path Enter the full path to the folder where you have stored your DICOM files
and images (ending with .dcm). The sensor sends all files in the folder to
the target DICOM device with each request. 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
837
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

838
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
839
Access Rights
Access Rights
Channel List
Channel Description
C-STORE Bandwidth The bandwidth usage of the sent files in bytes per second
C-STORE Response The response time of the C-STORE request in milliseconds (msec)
Time
C-STORE Size The total size of the sent files in bytes
More
Knowledge Base


840
7.8.32 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 the sensor to verify that the DICOM handshake is executed and that your target
system is capable of answering DICOM messages.
List 847 .
DICOM C-ECHO Sensor

§ 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
841
does PRTG require?
Add Sensor

Setting Description
842
Setting Description
inherited 146 .
§ dicom
§ cecho
§ ping
sensor settings.
DICOM Connection
DICOM Connection
843
Setting Description
Title connection.
Title
C-ECHO Settings
C-ECHO Settings
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.
Debug Options
Debug Options
844
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

845
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
846
Access Rights
Access Rights
Channel List
Channel Description
C-ECHO Response Avg The average response time of the C-ECHO request in milliseconds (msec)
C-ECHO Response Max The maximum response time of the C-ECHO request in msec
C-ECHO Response Min The minimum response time of the C-ECHO request in msec
More
Knowledge Base


847
7.8.33 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 855 .

§ Dutch: DICOM Query/Retrieve
§ French: Recherche / récupération (DICOM)
§ German: DICOM-Abfrage
§ Japanese: DICOM /
§ Portuguese: Consulta/recuperação DICOM
§ Russian: Зап ро с/п о лучен ие DICOM
§ Simplified Chinese: DICOM /

§ Spanish: Consulta/Recuperación DICOM
848
Remarks
does PRTG require?
Add Sensor

Setting Description
849
Setting Description
inherited 146 .
§ dicom
§ query
§ retrieve
sensor settings.
DICOM Connection
DICOM Connection
850
Setting Description
Title connection.
Title
Query/Retrieve Settings
Query/Retrieve Settings
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.
851
Setting Description
§ 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. Enter a string.
Channel Field 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
Debug Options
Debug Options
Setting Description
852
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

853
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
854
Channel List
Channel Description
Avg Query Entry Time The average query entry time in milliseconds (msec)
Max Query Entry Time The maximum query entry time in msec
Min Query Entry Time The minimum query entry time in msec
Total The total number of items found

Total Time The total time of the C-FIND request or MWL query in msec
The sensor also adds channels for the number of items in each field it finds.
More
Knowledge Base


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

§ 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
856
Remarks
Add Sensor

Setting Description
inherited 146 .
857
Setting Description
§ dns
§ dnssensor
sensor settings.
DNS Sensor Specific
DNS Sensor Specific
858
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 a zone of authority marker (SOA)
§ Text resource record (TXT)
§ 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 Filter Usage 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 the sensor tries to connect. This
must be the port on which the parent device answers queries. The default
port is 53.
859
Setting Description

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

860
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval
861
objects' settings.
Maintenance Window.
Access Rights
Access Rights

862
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
863
864
7.8.35 Docker Container Status Sensor
The Docker Container Status sensor monitors the status of a Docker container.
Docker Container Status Sensor
List 872 .

§ Dutch: Docker Container Status
§ French: État 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.
865
Remarks
§ The parent device of this sensor must be the Docker machine on which the container that you want to
monitor runs.
§ You need to provide certificates and private keys to monitor Docker with this sensor. For details, see
the Knowledge Base: How can I create private key and certificate for the Docker sensor?
Add Sensor
PRTG requires an authentication with a certificate and a private key before you can add this sensor.
Provide Port (usually 2376), Private Key, and Certificate in the dialog box that appears and click OK.
PRTG can now scan Docker for containers.
Docker Specific
Setting Description
Container Select the Docker containers that you want to monitor. PRTG creates one
sensor for each container that you select.
right corner.

866
Setting Description
inherited 146 .
§ docker
§ dockercontainer
sensor settings.
867
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 certificate 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-----
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?
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-----
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?
868
Docker Specific
Docker Specific
Setting Description
Container ID Shows the ID of the container that this sensor monitors.

Container Name Shows the name of the container that this sensor monitors.
Image Shows 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 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
869
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

870
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
871

Channel List
Channel Description
CPU Usage The CPU usage in percent
Eth0 Packets In The number of ingoing packets per second
Eth0 Packets Out The number of outgoing packets per second
872
Channel Description
Eth0 Traffic In The incoming traffic in bytes per second
Eth0 Traffic Out The outgoing traffic in bytes per second
Exit Code The exit code
Status The overall status

§ Up status 186 : 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?

873
7.8.36 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 880 .

§ 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
§ You must explicitly specify the credentials for the EVA in the sensor settings.
§ This sensor requires 874 the HPE P6000 Command View Software (previously known as HP Command
View EVA Software) on the 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?
HPE P6000 Command This sensor needs the HPE P6000 Command View Software (previously
View Software known as HP Command View EVA Software) installed on the probe
system.
874
If you do not want to install the whole command view tool, you can
use a different option. For details, see the Knowledge Base: Do I
really have to install the whole Command View on the probe to use the
EVA sensor?
Add Sensor
EVA Credentials
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.
EVA Settings
Setting Description
Modules Select the modules that you want to monitor. PRTG creates one sensor
for each module that you select.
right corner.
875
Setting Description
inherited 146 .
§ eva
sensor settings.
876
EVA Credentials
Setting Description
User Name Enter the user name for the EVA.
Password Enter the password for the EVA.
EVA Settings
Setting Description
Module Shows 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 Shows the system of the module that this sensor monitors.
Module Type Shows the type of the module that this sensor monitors.
Description Shows the description of the module that this sensor monitors.
scanning interval.
master node.
877
Sensor Display
Sensor Display
Setting Description

Inherited Settings
878
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

879
Channel List
The sensor can show the status of several HPE EVA modules:
§ System controllers
§ Enclosures
§ Disks
§ Disk groups
§ Folders
§ Hosts
§ Snapshots
§ Data replication
§ Cabinets
§ If the devices have measuring tools for fans and temperature, the 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
880
§ 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?

881
7.8.37 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 890 .

§ 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)
882
Remarks
§ This sensor has a very high performance impact. Use it with care. We recommend that you use no
more than 50 sensors of this sensor type on each probe.
§ See the Knowledge Base: My Event Log (Windows API) sensors fail after installing Windows updates.
What can I do?
§ See the Knowledge Base: My Event Log sensor ignores changes in the event log. What can I do?
§ See the Knowledge Base: How can I configure sensors using speed limits to keep the status for more
than one interval?
Add Sensor

Setting Description
883
Setting Description
inherited 146 .
§ wmiapieventlogsensor
sensor settings.
Windows API Event Log Specific
Window s API Event Log Specific
Setting Description
Log File Specify the log file that this sensor monitors. The Windows event log
provides several log files:
§ Application
§ System
884
Setting Description
§ Security
§ Directory Service
§ DNS Server
§ File Replication Service
Filter Event Log Entries
885
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.
Filter by Source Filter all events for a certain event source:

§ Off: Do not filter by event source.
§ On: Filter by event source.

If you enable this option, this sensor only processes messages
that match the value that you define below.
Filter Type This setting is only visible if you enable Filter by Source 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 enable Filter by Source above. Enter an
Source) 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 events for a certain event ID:

§ Off: Do not filter by event ID.
§ On: Filter by event ID.

Filter Type This setting is only visible if ID filtering is On above. Select a filter type:
Match Values (Event ID) This setting is only visible if you enable Filter by ID 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).
886
Setting Description
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.
Filter by Category Filter all events for a certain event category:
§ Off: Do not filter by event category.
§ On: Filter by event category.

Filter Type This setting is only visible if you enable Filter by Category above. Select a
filter type:
Match String (Event This setting is only visible if you enable Filter by Category above. Enter a
Category) 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
Filter by User Filter all received events for a certain event user:
§ Off: Do not filter by event user.
§ On: Filter by event user.

Filter Type This setting is only visible if you enable Filter by User above. Select a filter
type:
Match String (Event This setting is only visible if you enable Filter by User above. Enter a user
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 does not
process it (Exclude filter option). Enter a string.
Filter by Computer Filter all received events for a certain event computer:
§ Off: Do not filter by event computer.
§ On: Filter by event computer.

887
Setting Description
Filter Type This setting is only visible if you enable Filter by Computer above. Select a
filter type:
Match String (Event This setting is only visible if you enable Filter by Computer above. Enter a
Computer) 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:
§ Off: Do not filter by event message.
§ On: Filter by event message.

Filter Type This setting is only visible if you enable Filter by Message above. Select a
filter type:
Match String (Event This setting is only visible if message filtering is On above. Enter a
Message) 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 instead.
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.
Sensor Display
Sensor Display
888
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
889
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
New Records The number of new records per second

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?
890
How can I configure sensors using speed limits to keep the status for more than one interval?

891
7.8.38 Exchange Backup (PowerShell) Sensor
The Exchange Backup (PowerShell) sensor monitors backups of an Exchange server via Remote
PowerShell.
Exchange Backup (Pow erShell) Sensor
List 898 .

§ 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
892
§ The parent device for this sensor must be the Exchange server (version 2010 or higher) that hosts the
database that you want to monitor.
§ This sensor requires Remote PowerShell and Remote Exchange Management Shell on the target
servers and PowerShell on the probe system.
§ This sensor requires credentials for Windows systems 542 in the settings of the parent device.
§ This sensor requires Exchange user account permissions.
§ This sensor requires the fully qualified domain name (FQDN) of the Exchange server in the settings of
the parent device 536 .
§ See the Knowledge Base: Where can I find more information about PowerShell sensors?
Remote PowerShell and This sensor uses PowerShell commands. To monitor Exchange servers
Remote Exchange with this sensor, you must enable Remote PowerShell and Remote
Management Shell Exchange Management Shell on the target servers that you want to
monitor. Also ensure you have installed PowerShell 2.0 or later 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?
Exchange user account This sensor requires a user account that must be either in the Exchange
permissions 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
893
FQDN To connect to Exchange servers, this sensor needs the FQDN. In the
device settings 536 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?
does PRTG require?
Add Sensor
Sensor Settings
Setting Description
Databases Select the databases that you want to monitor. PRTG creates one sensor
for each database that you select.

right corner.

894
Setting Description
inherited 146 .
§ exchange
§ powershell
§ backup
sensor settings.
895
Sensor Settings
Sensor Settings
Setting Description
Database Shows the name of the database that this sensor monitors.
master node.
Sensor Display
Sensor Display
Setting Description
896
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
897
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Backup In Progress If a backup is running

§ Up status 186 : 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
898
Channel Description
Last Incremental Backup The time since the last incremental backup
More
Knowledge Base
Where can I find more information about PowerShell sensors?

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
899
7.8.39 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 907 .

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

§ Portuguese: Banco de dados Exchange (PowerShell)
§ Russian: База дан н ы х Exchange (PowerShell)

§ Spanish: Base de datos Exchange (PowerShell)
Remarks
900
§ See the Knowledge Base: How can I monitor additional values of Exchange databases?
probe system.
§ Monitoring
the IP address.
901
does PRTG require?
Add Sensor
Sensor Settings
Setting Description

right corner.

902
Setting Description
inherited 146 .
§ exchange
§ powershell
§ database
sensor settings.
Sensor Settings
Sensor Settings
903
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
904
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
905
Maintenance Window.
Access Rights
Access Rights

906
Channel List
Channel Description
Database Size The size of the database in bytes

Is Valid If the database is recognized as valid

§ Up status 186 : Yes
§ Down status: Critical Issue, Major Issue, Non Recoverable
Mounted If the database is mounted

§ Up status: Yes
§ Down status: No
More
Knowledge Base

How can I monitor additional values of Exchange databases?




907

908
7.8.40 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 915 .

§ 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)
909
Remarks
§ The Exchange server must be part of a valid DAG. See also the Knowledge Base: Why doesn't PRTG
show available databases when adding the Exchange Database DAG (PowerShell) sensor?
§ Make sure that the Exchange database is mounted on the target device. Otherwise, you might not be
able to properly add the sensor.
§ See the Knowledge Base: How can I monitor additional values of Exchange databases?
probe system.
910
§ Monitoring
the IP address.
does PRTG require?
Add Sensor
Sensor Settings
Setting Description

right corner.
911
Setting Description
inherited 146 .
§ exchange
§ powershell
§ database
§ dag
912
sensor settings.
Sensor Settings
Sensor Settings
Setting Description
master node.
Sensor Display
Sensor Display
913
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
914
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Activation Suspended If the activation is suspended

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

§ Up status: Active, Not Active
§ 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 state

§ Up status: Healthy, Not Supported In 2019
§ Warning status: Crawling
915
Channel Description
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
Why doesn't PRTG show available databases when adding the Exchange Database DAG (PowerShell)
sensor?

How can I monitor additional values of Exchange databases?

916




917
7.8.41 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 924 .

§ 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)
§ Russian: О чередь п о что вы х со о бщ ен ий Exchange (PowerShell)

§ Spanish: Cola de correo Exchange (PowerShell)
Remarks
918
§ This sensor requires credentials for Windows systems
542 in the settings of the parent device. The
user name for access to the Windows system must be in the same domain as the Exchange server or
a domain that the Exchange server trusts.
§ This sensor only supports Kerberos authentication.
§ See the Knowledge Base: What types of Exchange transport queues are there?
probe system.
§ Monitoring
919
the IP address.
does PRTG require?
Add Sensor
Sensor Settings
Setting Description
Hub Transport Server or Select the roles that you want to monitor. PRTG creates one sensor for
Edge-Server each role that you select.
right corner.

920
Setting Description
inherited 146 .
§ exchange
§ powershell
§ mailqueue
sensor settings.
921
Sensor Settings
Sensor Settings
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description
922
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
923
Maintenance Window.
Access Rights
Access Rights
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
924
More
Knowledge Base

What types of Exchange transport queues are there?





925
7.8.42 Exchange Mailbox (PowerShell) Sensor
The Exchange Mailbox (PowerShell) sensor monitors mailboxes of an Exchange server via Remote
PowerShell.
Exchange Mailbox (Pow erShell) Sensor
List 932 .

§ 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)
§ Russian: П о что вы й ящ ик Exchange (PowerShell)

§ Spanish: Buzón Exchange (PowerShell)
Remarks
926
§ This sensor requires elevated rights for the user of this sensor on the Exchange system. It is not
sufficient to have administrative rights. For details, see the Knowledge Base: I have problems with the
PowerShell Exchange sensors, what can I do? (solution (2) in the reply).
probe system.
the IP address.
does PRTG require?
927
Add Sensor
Sensor Settings
Setting Description
Mailboxes Select the Exchange server mailboxes that you want to monitor. PRTG
creates one sensor for each mailbox that you select.
right corner.

Setting Description
928
Setting Description
inherited 146 .
§ exchange
§ powershell
§ mailbox
sensor settings.
Sensor Settings
Sensor Settings
Setting Description
Mailbox Name Shows the name of the mailbox that this sensor monitors.
929
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


930
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
931
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 in bytes
More
Knowledge Base





932
7.8.43 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 939 .

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

§ Portuguese: Pasta pública Exchange (PowerShell)
§ Russian: О бщ ая п ап ка Exchange (PowerShell)

§ Spanish: Carpeta pública Exchange (PowerShell)
Remarks
933
probe system.
§ Monitoring
the IP address.
934
does PRTG require?
Add Sensor
Sensor Settings
Setting Description
Public Folders Select the public folders that you want to monitor.PRTG creates one
sensor for each mailbox that you select.
right corner.

935
Setting Description
inherited 146 .
§ exchange
§ powershell
§ publicfolder
sensor settings.
Sensor Settings
Sensor Settings
936
Setting Description
Public Folder Shows the name of the public folder that this sensor monitors.
PRTG applies this filter in real time. If the configuration underneath
the linked object changes, the library node accordingly shows
matching sensors.
master node.
Sensor Display
Sensor Display
Setting Description

937
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
938
Access Rights
Access Rights
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 in bytes
More
Knowledge Base



939


940
7.8.44 EXE/Script Sensor
The EXE/Script sensor runs an executable file (.exe, .dll) or a script (batch file, VBScript, PowerShell) on
the probe system. This option is available as part of the PRTG API.
EXE/Script Sensor
List 949 .

§ Dutch: EXE/Script
§ French: Script/EXE
§ German: Programm/Skript
§ Japanese: EXE/
§ Portuguese: EXE/Script
§ Russian: EXE/скрип т
§ Simplified Chinese: EXE/
§ Spanish: EXE/Script
Remarks
§ You must store the executable or script file on the probe system. In a cluster, copy the file to every
cluster node.
§ This sensor requires that Remote PowerShell is enabled on the target system and PowerShell 3.0
942
on both the probe system and the target system.

941
§ If you want to execute a custom Windows Management Instrumentation Query Language (WQL)
script, use the WMI Custom sensor 2796 .
§ See the Knowledge Base: What is the Mutex Name in the EXE/Script sensor settings?
§ See the Knowledge Base: How can I test if parameters are correctly transmitted to my script when
using an EXE/Script sensor?
§ See the Knowledge Base: How can I show special characters with EXE/Script sensors?
the probe computer?
does PRTG require?
Remote PowerShell This sensor uses PowerShell commands. To monitor devices with this
sensor, Remote PowerShell access must be enabled on the target
computer. Also make sure that you have installed PowerShell 3.0 or later
If you receive an error message regarding issues with the WinRM
connection, make sure that remote commands have been enabled in
PowerShell. For more details, see the Knowledge Base: How do I enable
and use remote commands in Windows PowerShell?
Add Sensor
Sensor Settings
942
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 3579 on the probe system. For a
file to appear in this list, store the file ending in .bat, .cmd, .dll, .exe, .ps1,
or .vbs into this subfolder.
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 186 .
If you use a PowerShell script (.ps1) and if the PowerShell Security
Enhancement experimental feature 3239 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 3605 , copy your files to
every cluster node.
For detailed information on how to create custom sensors and for the
return format, see section Custom Sensors 3498 .
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.
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 3052 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.
If you want to change the unit after sensor creation, you can change it
in the sensor's channel settings 3052 .
943
Setting Description
inherited 146 .
§ exesensor
sensor settings.
944
Sensor Settings
Sensor Settings
Setting Description
EXE/Script Shows the executable or script file that the sensor executes with each
sensor scan.
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
For a full list of all placeholders, see section Custom Sensors 3508 .
You need to escape special characters and whitespaces in your
parameters and surround them with double quotes. See section
Escape Special Characters and Whitespaces in Parameters 949 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.
945
Setting Description
§ Set placeholders as environment values: From within your executable or

script, the values of the PRTG command-line parameters are available
via environment variables. For example, you can then 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 provided in
several variables as well.
For a full list of all available variables, see section Custom

Sensors 3509 .
Security Context Define the Windows user account that the sensor uses to run the
executable or script file:
§ Use security context of probe service: Run the file under the same
Windows user account that the probe 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 535 .
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 Shows the value type.

If Value Changes Define what the sensor does when the sensor value changes:

946
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.
Enable 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

947
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
948
Access Rights
Access Rights
Escape Special Characters and Whitespaces in Parameters

You need to escape special characters in parameters that you pass to an executable or script and
surround them with quotation marks to make sure that the characters are correctly interpreted.
PowerShell scripts in particular require adequate escaping so that the parameters are passed in a valid
PowerShell syntax. PRTG automatically does most of the escaping for you.
Follow these rules to escape special characters and whitespaces in the parameters fields:
§ Use quotes for parameters that contain whitespaces.

-name "Mr John Q Public"
-name 'Mr John Q Public'
§ Use double quotes for parameters that contain single quotes.

-name "Mr 'John Q' Public"
§ Use single quotes for parameters that contain double quotes.

-name 'Mr "John Q" Public'
§ Use a backslash (\) to escape and pass a literal double quote.

-name pub\"lic
§ Use double quotes for parameters that contain double and single quotes and escape double quotes.
-name "pu'b\"lic"
In SSH scripts, you can use alphanumeric characters and the special characters ".", "_", "-", "=",
and "/" outside of quoted strings.
We recommend that you do not pass passwords in parameters. Use placeholders instead. See
section Custom Sensors 3509 for details.
Channel List
949
Channel Description
Execution Time The execution time in milliseconds (msec)
[Value] The value that the executable file or script file returns in one channel
For details about the return value format, see section Custom
Sensors 3498 .
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?
How can I show special characters with EXE/Script sensors?




For which sensor types do you recommend Windows Server 2012 R2 or later and why?
950
7.8.45 EXE/Script Advanced Sensor
The EXE/Script Advanced sensor runs an executable file (.exe, .dll) 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).
EXE/Script Advanced Sensor
List 960 .

§ Dutch: EXE/Script Geavanceerd
§ French: Script/EXE avancé
§ German: Programm/Skript (Erweitert)
§ Japanese: EXE/
§ Portuguese: EXE/Script avançado
§ Russian: Расш ирен н ы й сен со р EXE/скрип та
§ Simplified Chinese: EXE/

§ Spanish: EXE/Script (avanzado)
951
Remarks
§ You must store the executable or script file on the probe system. In a cluster, copy the file to every
cluster node.
952

§ If you want to execute a custom Windows Management Instrumentation Query Language (WQL)
script, use the WMI Custom sensor 2796 .
§ See the Knowledge Base: How can I test if parameters are correctly transmitted to my script when
using an EXE/Script sensor?
§ See the Knowledge Base: How can I show special characters with EXE/Script sensors?
the probe computer?
§ See the Knowledge Base: How can I use meta-scans for custom EXE/Script sensors?
does PRTG require?
952
Add Sensor
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 3579 on the probe system. For a
file to appear in this list, store the file ending in .bat, .cmd, .dll, .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 3239 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.

953
Setting Description
inherited 146 .
§ xmlexesensor
sensor settings.
954
Sensor Settings
Sensor Settings
Setting Description
EXE/Script Shows the executable or script file that the sensor executes with each
sensor scan.
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
You need to escape special characters and whitespaces in your
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: From within your executable or
script, the values of the PRTG command-line parameters are available
via environment variables. For example, you can then 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 provided in
several variables as well.
955
Setting Description
For a full list of all available variables, see section Custom

Sensors 3509 .
Security Context Define the Windows user account that the sensor uses to run the
executable or script file:
§ Use security context of probe service: Run the file under the same
Windows user account that the probe runs under. By default, this is the
Windows system user account.
account in the parent device settings 535 .
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.
sensor settings?
Result Handling Define what the sensor does with the result that the executable file gives
back:
scanning interval.
Enable this option if you do not want failures to be overwritten by a
following success of the script.
master node.
956
Sensor Display
Sensor Display
Setting Description

The Stack Unit setting for stacking graphs only works if you explicitly
define the same <unit> for at least two channels. For detailed
information about sensor settings, see section Custom Sensors 3501 .
Inherited Settings
957
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

958





-name pub\"lic
-name "pu'b\"lic"
959
Channel List
Channel Description
[Value] The values that the executable file or script file returns in several channels
Sensors 3499 .
More
Knowledge Base


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




960
7.8.46 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 sensor 978 , you can also monitor changes to the actual content of a file.
File Sensor
List 967 .

§ Dutch: Bestand
§ French: Fichier
§ German: Datei
§ Japanese:
§ Portuguese: Arquivo
§ Russian: Файл
§ Spanish: Archivo
Remarks
§ This sensor requires that the LanmanServer service runs on the target computer.
961
§ Try using the fully qualified domain name (FQDN) of the target device if the sensor does not get a
connection with the IP address.
§ See the Knowledge Base: What can I do if PRTG doesn't succeed with monitoring a share? PE029
PE032
§ See the Knowledge Base: Can I use placeholders in file names to monitor log_files?
LanmanServer service To monitor shares on Windows machines, make sure that the
LanmanServer service runs on the target computer.
The display name of the service is Server.
To enable the service, log in to the respective computer and open the
services manager (for example, via services.msc). In the list, find the
respective service and set its Start Type to Automatic.
Add Sensor

962
Setting Description
inherited 146 .
§ filesensor
sensor settings.
Sensor Specific
Sensor Specific
963
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\johnqpublic\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 535 . Enter a valid path and file name.
To monitor Windows shares, the LanmanServer service must run on
the target computer.
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 that the sensor shows the Down status if a .txt
file exists in the defined directory.
Sensor Behavior Specify when the sensor shows the Down status 186 :
§ 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.
Monitor File Content Specify if the sensor sends a notification when the content of the file
changes (based on a checksum):
§ Ignore changes: Take no action on change.
§ Trigger 'change' notification: Send an internal message that indicates

that its value has changed. In combination with a change trigger 3182 , you
can use this mechanism to trigger a notification 3063 whenever the sensor
value changes.
Monitor File Time Stamp Specify if the sensor sends a notification when the content of the file's
time stamp changes:

that its value has changed. In combination with a change trigger, you
can use this mechanism to trigger a notification whenever the sensor
value changes.
964
Sensor Display
Sensor Display
Setting Description

Inherited Settings
965
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

966
Channel List
Channel Description
File Size The file size in bytes

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?

967
968
7.8.47 File Content Sensor
The File Content sensor checks a text file (for example, a log file) for certain strings.
Additionally, the sensor quotes matching lines in the sensor message.
File Content Sensor
List 976 .

§ Dutch: Bestands inhoud
§ French: Contenu du fichier
§ German: Datei-Inhalt
§ Japanese:
§ Portuguese: Conteúdo de arquivo
§ Russian: Со держим о е ф айла
§ Spanish: Contenido de archivo
Remarks
969
§ This sensor does not support UTF-16 encoded files. In this case, try to use a custom sensor like the
EXE/Script sensor 941 or the EXE/Script Advanced sensor 951 .
§ This sensor does not officially support binary files. If you would still like to monitor binary files contrary
to our recommendation, choose the option Always transmit the entire file in the sensor settings, option
File Transmission Handling.
§ This sensor supports Unix line feeds.
§ To monitor files on a Linux system, the folder must be accessible via Server Message Block (SMB).
§ Try using the fully qualified domain name (FQDN) of the target device if the sensor does not get a
connection with the IP address.
Add Sensor

970
Setting Description
inherited 146 .
§ filesensor
971
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\johnqpublic\file.txt.
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 535 . Enter a valid path and file name.
To monitor Linux files, the folder with these files must be accessible
via SMB.
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) 3552 .
The search string must be case sensitive.
972
Setting Description
Search Method Define the method with which you want to provide the search string:
§ Simple string search: 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
sensor 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.
The 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.
The 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)
§ UTF-8
§ UTF-16
Sensor Behavior Define the condition for which the sensor shows the Warning status 186 :
§ Shows the warning status when the string is not found: Show the
Warning status if there is no match. Otherwise it remains in the Up
status.
973
Setting Description
§ Shows the 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

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

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
975
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Last Occurrence (Line) The line number of the last match

Matches The number of matches
More
Knowledge Base
976
977
7.8.48 Folder Sensor
The Folder sensor monitors a folder via Server Message Block (SMB). You can monitor file changes and
file ages.
Folder Sensor
List 985 .

§ Dutch: Map
§ French: Dossier
§ German: Ordner
§ Japanese:
§ Portuguese: Pasta
§ Russian: П ап ка
§ Spanish: Carpeta
Remarks
978
§ This sensor counts all files in a folder, including hidden files.
PE032
Add Sensor
Folder Monitor
Setting Description
File Age Check Specify if the sensor monitors the folder for certain file ages and shows a
corresponding status 186 :
§ 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 the file age check later via the Limits section in the
channel settings 3053 of Newest File and Oldest File.
979
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.

Setting Description
inherited 146 .
980
Setting Description
§ foldersensor
Folder Monitor
Folder Monitor
Setting Description
Folder Name Enter the full path to the folder this sensor monitors. For example, enter
C:\Windows.
Convention (UNC) path without the server part (only enter share\folder).
The server part (\\server\) is taken from the parent device settings 535 of
this sensor. Enter a valid path name.
Recurse Subfolders Specify if the sensor includes subfolders in the folder monitoring:
§ Do not recurse subfolders: Only monitor the folder. Do not monitor its
subfolders.
981
Setting Description
§ 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 may cause timeout errors or performance
issues.
If Folder Contents Specify if the sensor sends a notification when the content of the folder
Change changes:
§ Ignore changes: Changes to the folder do not trigger a notification.
§ Trigger 'change' notification: The sensor triggers a notification if a file

changes its time stamp or file name, or if there are new or deleted files.
Create a change trigger 3072 on the Notification Triggers tab of this
sensor to receive a notification whenever there is a change.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
982
Sensor Display
Sensor Display
Setting Description

Inherited Settings
983
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

984
Channel List
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 in bytes

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)
985
More
Knowledge Base
986
7.8.49 FortiGate System Statistics Sensor (BETA)
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 992 .

§ Dutch: FortiGate System Statistics
§ French: FortiGate System Statistics
§ German: FortiGate System Statistics
§ Japanese: FortiGate System Statistics
§ Portuguese: FortiGate System Statistics
§ Russian: FortiGate System Statistics
§ Simplified Chinese: FortiGate System Statistics
987
§ Spanish: FortiGate System Statistics
Remarks
§ This sensor requires credentials for FortiGate 555 in settings that are higher in the object hierarchy 140 ,

Setting Description
988
Setting Description
inherited 146 .
§ fortigate
§ fortios
§ fortinet
§ firewall
§ systemstatistics
Sensor Display
Sensor Display
Setting Description
989
Setting Description

Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
990
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
991
Channel List
Channel Description
Conserve Mode The status of the conserve mode

§ Up status: Inactive
§ Down status: Active
Memory Usage The memory usage in percent
Session Rate The number of sessions per second
992
Channel Description
Sessions The number of sessions
Uptime The uptime of the system
More
Knowledge Base


993
7.8.50 FortiGate VPN Overview Sensor (BETA)
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 999 .

§ Dutch: FortiGate VPN Overview
§ French: FortiGate VPN Overview
§ German: FortiGate VPN Overview
§ Japanese: FortiGate VPN Overview
§ Portuguese: FortiGate VPN Overview
§ Russian: FortiGate VPN Overview
§ Simplified Chinese: FortiGate VPN Overview
§ Spanish: FortiGate VPN Overview
994
Remarks
§ This sensor requires credentials for FortiGate 555 in settings that are higher in the object hierarchy 140 ,

Setting Description
inherited 146 .
995
Setting Description
§ fortigate
§ fortios
§ fortinet
§ vpn
Sensor Display
Sensor Display
Setting Description
996
Setting Description

Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
997
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
998
Channel List
Channel Description
Connected SSL Clients The number of SSL clients that are connected
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
999

1000
7.8.51 FTP Sensor
The FTP sensor monitors file servers via the File Transfer Protocol (FTP) and FTP over SSL (FTPS).
The sensor also shows the response message of the server in the sensor message.
FTP Sensor
List 1007 .

§ Dutch: FTP
§ French: FTP
§ German: FTP
§ Japanese: FTP
§ Portuguese: FTP
§ Russian: FTP
§ Simplified Chinese: FTP
§ Spanish: FTP
Remarks
1001
Add Sensor

Setting Description
inherited 146 .
§ ftpsensor
1002
sensor settings.
Sensor Specific
Sensor Specific
Setting Description
Port Enter the number of the FTP port that the sensor tries to connect to. Enter
an integer.
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: If you cannot establish a connection, use the passive
mode.
§ Passive mode (default)
Connection Security
Connection Security
1003
Setting Description
Transport-Level Security Specify if the sensor uses connection security:

§ Use transport-level security if available: The 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, the
§ Do not use transport-level security: 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.
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.
1004
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

1005
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1006
Access Rights
Access Rights
Channel List
Channel Description

More
Knowledge Base

1007
7.8.52 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 1015 .

§ 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
PE087, additionally install .NET 3.5 on the probe system.
1008

does PRTG require?
Add Sensor

Setting Description
1009
Setting Description
inherited 146 .
§ ptfsensor
Sensor Settings
Sensor Settings
1010
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: The sensor uses a URL of an FTP server to access the target
directory. Define the URL below.
§ Folder on parent device: The 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.
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:
subfolders.
issues.
User Name Enter the user name for the login to the FTP server. Enter a string.
Password Define the password for the login to the FTP server. Enter a string.
1011
Setting Description
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 1014 .
With every scanning interval, the sensor considers any new files
from the previous scanning interval to be old.
Connection Security Define the security of the connection:

§ Do not use transport-level security: The sensor connects without
§ 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.

Debug Options
Debug Options
Setting Description
1012
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

1013
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
1014

Channel List
Channel Description
Files The number of files that are available in the directory listing
More
Knowledge Base
1015

1016
7.8.53 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 3579 .
The sensor sends them to the HL7-capable system with each scanning interval.
HL7 Sensor
List 1023 .

§ Dutch: HL7
§ French: HL7
§ German: HL7
§ Japanese: HL7
§ Portuguese: HL7
§ Russian: HL7
§ Simplified Chinese: HL7
§ Spanish: HL7
Remarks
1017
does PRTG require?
Add Sensor
HL7 Message Specific
Setting Description
HL7 Messages Select an .hl7 file from the list. The 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.

1018
Setting Description
inherited 146 .
§ dicom
§ hl7
sensor settings.
1019
HL7 Connection
HL7 Connection
Setting Description
Port Enter the port of the HL7 interface that the sensor uses for the connection.
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.
1020
Setting Description
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.
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
message. Enter a string.
HL7 Message Shows the .hl7 message file that the sensor uses to send the message
with each scanning interval.
Debug Options
Debug Options
Setting Description
master node.
1021
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1022
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
1023
Channel Description
ACK Status Acknowledgment (ACK) status

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

§ Up status: Yes
§ Down status: No

More
Knowledge Base

1024
7.8.54 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 1031 .

§ Dutch: HPE 3PAR Common Provisioning Group
§ French: HPE 3PAR Common Provisioning Group
§ German: HPE 3PAR Common Provisioning Group
§ Japanese: HPE 3PAR Common Provisioning Group
§ Portuguese: HPE 3PAR Common Provisioning Group
§ Russian: HPE 3PAR Common Provisioning Group
§ Simplified Chinese: HPE 3PAR Common Provisioning Group
1025
§ Spanish: HPE 3PAR Common Provisioning Group
Remarks
§ This sensor requires credentials for HPE 3PAR 555in settings that are higher in the object
§ See the Knowledge Base: Where can I find the Web Services API (WSAPI) port for the connection to
the HPE 3PAR system?
Add Sensor
HPE 3PAR Specific
Setting Description
Common Provisioning Select the CPGs that you want to monitor.

Groups
right corner.

1026
Setting Description
inherited 146 .
§ cpg
§ hpe
§ hpe3par
§ rest
HPE 3PAR Specific
HPE 3PAR Specific
Setting Description
Name Shows the name of the CPG that this sensor monitors.
1027
Setting Description
ID Shows the ID of the CPG that this sensor monitors.
Virtual Domain Shows the virtual domain to which the CPG that this sensor monitors
belongs.
Sensor Display
Sensor Display
Setting Description

1028
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval
1029
objects' settings.
Maintenance Window.
Access Rights
Access Rights

1030
Channel List
Channel Description
Logical Space Free The free logical space in gigabytes
Logical Space Free % The free logical space in percent
Logical Space Total The allocated logical space in gigabytes
Logical Space Used The space that is already in use in gigabytes
Snapshot Space Free The free snapshot space in gigabytes
Snapshot Space Free % The free snapshot space in percent
Snapshot Space Total The allocated snapshot space in gigabytes
Snapshot Space Used The snapshot space that is already in use in gigabytes
1031
Channel Description
State The overall state of the CPG

§ Up status: Normal
§ Warning status: Degraded
§ Unknown: Unknown
User Space Free The free user space in gigabytes
User Space Free % The free user space in percent
User Space Total The allocated user space in gigabytes
User Space Used The user space that is already in use in gigabytes
More
Knowledge Base
1032
7.8.55 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 Drive Enclosure
§ French: HPE 3PAR Drive Enclosure
§ German: HPE 3PAR Drive Enclosure
§ Japanese: HPE 3PAR Drive Enclosure
§ Portuguese: HPE 3PAR Drive Enclosure
§ Russian: HPE 3PAR Drive Enclosure
§ Simplified Chinese: HPE 3PAR Drive Enclosure
§ Spanish: HPE 3PAR Drive Enclosure
1033
Remarks
Add Sensor
HPE 3PAR Specific
Setting Description
Drive Enclosures Select the drive enclosures that you want to monitor. PRTG creates one
sensor for each drive enclosure that you select.
right corner.

Setting Description
1034
Setting Description
inherited 146 .
§ hpe
§ hpe3par
§ ssh
§ enclosure
HPE 3PAR Specific
HPE 3PAR Specific
1035
Setting Description
ID Shows the ID of the drive enclosure that this sensor monitors.
Enclosure Name Shows the name of the drive enclosure that this sensor monitors.
Drive Count Shows the number of drives in the enclosure that this sensor monitors.
Model Shows the model of the drive enclosure that this sensor monitors.
Form Factor Shows the form factor of the drive bays of the enclosure that this sensor
monitors.
Sensor Display
Sensor Display
Setting Description

1036
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval
1037
objects' settings.
Maintenance Window.
Access Rights
Access Rights

1038
Channel List
Channel Description
Average Drive The average temperature of all drives in the drive bay in degree Celsius
Temperature
Drives The overall state of the drives

§ Unknown: Unknown
Highest Drive The highest temperature of all drives in the drive bay in degree Celsius
Temperature
Interface Cards The overall state of the interface cards

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

§ Unknown: Unknown
State The overall state of the drive enclosure

§ Unknown: Unknown
More
Knowledge Base

1040
7.8.56 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 1047 .

§ Dutch: HPE 3PAR Virtual Volume
§ French: HPE 3PAR Virtual Volume
§ German: HPE 3PAR Virtual Volume
§ Japanese: HPE 3PAR Virtual Volume
§ Portuguese: HPE 3PAR Virtual Volume
§ Russian: HPE 3PAR Virtual Volume
1041
§ Simplified Chinese: HPE 3PAR Virtual Volume
§ Spanish: HPE 3PAR Virtual Volume
Remarks
Add Sensor
HPE 3PAR Specific
Setting Description
Virtual Volumes Select the virtual volumes that you want to monitor.
right corner.

1042
Setting Description
inherited 146 .
§ hpe
§ hpe3par
§ rest
§ virtualvolume
HPE 3PAR Specific
HPE 3PAR Specific
Setting Description
Name Shows the name of the virtual volume that this sensor monitors.
1043
Setting Description
Provisioning Type Shows the provisioning type of the virtual volume that this sensor
monitors.
Volume Type Shows the volume type of the virtual volume that this sensor monitors.
Size Shows the size of the virtual volume that this sensor monitors.
Sensor Display
Sensor Display
Setting Description

1044
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval
1045
objects' settings.
Maintenance Window.
Access Rights
Access Rights

1046
Channel List
Channel Description
Snapshot Space Free The free snapshot space in gigabytes
Snapshot Space Free % The free snapshot space in percent
Snapshot Space The reserved snapshot space in gigabytes

Reserved
Snapshot Space Used The snapshot space that is already in use in gigabytes
State The overall state of the virtual volume

§ Unknown: Unknown
1047
Channel Description
Total Space The total space in gigabytes
Total Space Free The total free space in gigabytes
Total Space Free % The total free space in percent
Total Space Reserved The total reserved space in gigabytes
Total Space Used The total space that is already in use in gigabytes
User Space Free The free user space in gigabytes
User Space Free % The free user space in percent
User Space Reserved The reserved user space in gigabytes
User Space Used The user space that is already in use in gigabytes
More
Knowledge Base

1048
7.8.57 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 1056 .

§ Dutch: HTTP
§ French: HTTP
§ German: HTTP
§ Japanese: HTTP
§ Portuguese: HTTP
§ Russian: HTTP
§ Simplified Chinese: HTTP
§ Spanish: HTTP
Remarks
§ This sensor does not support Secure Remote Password (SRP) ciphers.
1049
§ See the Knowledge Base: My HTTP sensors fail to monitor websites which use SNI. What can I do?
§ See the Knowledge Base: Which HTTP status code leads to which HTTP sensor status?
Add Sensor

Setting Description
inherited 146 .
§ httpsensor
1050
Setting Description
sensor settings.
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.
1051
Setting Description
Replacement 1055 .
URL:
§ GET: Directly request the website.
We recommend that you use this setting for a simple check of the
web page.
If you select this setting, you must enter the data in the Postdata
field below.
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.
Postdata This setting is only visible if you select POST above. Enter the data part
for the POST request.
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 Shows the Server Name Indication (SNI) that the sensor automatically
determines from the host address of the parent device 536 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 details, 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.
1052
Setting Description
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.
Sensor Display
Sensor Display
Setting Description

1053
Inherited Settings

For more information, see section Root Group Settings 417 , section Proxy Settings for HTTP
Sensors.
Scanning Interval
Scanning Interval

objects' settings.
1054
Maintenance Window.
Access Rights
Access Rights

1055
Channel List
Channel Description
Loading Time The loading time of the web page or element in milliseconds (msec)
More
Knowledge Base
My HTTP sensors fail to monitor websites which use SNI. What can I do?


1056
7.8.58 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 1070 .

§ Dutch: HTTP Geavanceerd
§ French: HTTP avancé
§ German: HTTP (Erweitert)
§ Japanese: HTTP
§ Portuguese: HTTP (avançado)
§ Russian: HTTP (Расш ирен н ы й)
§ Spanish: HTTP (avanzado)
Remarks
§ This sensor does not support Secure Remote Password (SRP) ciphers. If you need to use SRP
ciphers, use the Compatibility engine in the sensor settings.
1057
§ This sensor does not support HTTP compression. If you need to use HTTP compression, use the
Compatibility engine in the sensor settings.
§ Bandwidth monitoring of fast internet connections may be inaccurate.
§ See the Knowledge Base: Which user agent should I use in the HTTP Advanced sensor's settings?
§ See the Knowledge Base: My HTTP sensors fail to monitor websites which use SNI. What can I do?
Add Sensor

Setting Description
inherited 146 .
1058
Setting Description
§ httpsensor
sensor settings.
HTTP Specific
HTTP Specific
Setting Description
1059
Setting Description
loading time.

Replacement 1069 .
URL:
web page.
field below.
web page.
HTTP.
1060
Setting Description
This sensor implicitly supports SNI, an extension to the Transport

Layer Security (TLS) protocol.
Monitoring Engine
Monitoring Engine
Setting Description
Monitoring Engine Choose the monitoring engine that the sensor uses:
§ Default engine (recommended): 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 option is only visible if you select Compatibility engine above. Choose
from:
1061
Setting Description
§ 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 option is only visible if you select Compatibility engine above. Specify
if the sensor checks the certificate of the URL:
§ Do not check certificates: Do not check the certificates of the web
pages. This is the default setting.
§ 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 186 and displays a corresponding message.
Advanced Sensor Data
1062
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.
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 enable 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 enable 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.
Ensure that the HTTP header statement is valid. Otherwise, the
sensor request cannot be successful.
If Content Changes Define what the sensor does if the content of the web page (element)
changes:
· Ignore changes: Take no action on change.
· Trigger 'change' notification: Send an internal message that indicates

that the web page content has changed. In combination with a change
trigger 3182 , you can use this mechanism to trigger a notification 3063
whenever the web page content changes.
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.
1063
Setting Description
§ 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.
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) 3552 .
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
1064
Setting Description
§ Set sensor to down status if keyword is found: Check if a keyword

work with other target URLs. For example, binary files are not
supported.
Response Must Not This setting is only visible if you selectSet 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 is transferred 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 3579 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.
1065
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
§ Web page needs authentication
login.
Only basic authentication is available. 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: Use simple HTTP authentication.
This authentication method transmits credentials as plain text.
§ 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.
1066
Sensor Display
Sensor Display
Setting Description

Inherited Settings

1067
Sensors.
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1068
Access Rights
Access Rights


1069
Channel List
Channel Description
Bytes Received The received bytes
Download Bandwidth The download speed in bytes per second
Loading Time The loading time in milliseconds (msec)

Time To First Byte The time to the first byte in msec
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?

1070
1071
7.8.59 HTTP Apache ModStatus PerfStats Sensor
The HTTP Apache ModStatus PerfStats sensor monitors performance statistics of an Apache web server
via mod_status over HTTP.
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
1072
Add Sensor

Setting Description
inherited 146 .
§ httpsensor
1073
Setting Description
§ httpapachemodstatusperfstatssensor
§ apache
sensor settings.
HTTP Specific
HTTP Specific
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 1077 .
This sensor implicitly supports SNI, an extension to the Transport Layer Security (TLS) protocol.
Authentication
Authentication
1074
Setting Description

login.
authentication.
Sensor Display
Sensor Display
Setting Description
1075
Setting Description

Inherited Settings

Sensors.
1076
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1077
Channel List
Channel Description
BusyWorkers The number of busy worker threads
BytesPerReq The number of bytes per request
CPULoad The CPU load

IdleWorkers The number of idle worker threads
ReqPerSec The number of requests per second
Uptime The server uptime
More
Knowledge Base

1078

1079
7.8.60 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 1086 .

§ 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
Add Sensor

Setting Description
inherited 146 .
§ httpsensor
§ httpapachemodstatustotalssensor
§ apache
1081
Setting Description
sensor settings.
HTTP Specific
HTTP Specific
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 1085 .
Authentication
Authentication
1082
Setting Description

login.
authentication.
Sensor Display
Sensor Display
Setting Description
1083
Setting Description

Inherited Settings

Sensors.
1084
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1085
Channel List
Channel Description
Accesses The number of accesses per second
KBytes The data transferred in bytes per second
More
Knowledge Base



For more information about sensor settings, see the following sections:
§ List of Available Sensor Types 3626
1086
1087
7.8.61 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 1095 .
HTTP Content Sensor
List 1096 .

§ Dutch: HTTP (Inhoud)
§ French: Contenu (HTTP)
§ German: HTTP (Inhalt)
§ Japanese: HTTP
§ Portuguese: Conteúdo HTTP
§ Russian: HTTP: Со держим о е
§ Spanish: Contenido HTTP
Remarks
1088
§ For an example configuration, see section Example 1095 .

§ See the Knowledge Base: How can I monitor internal values of a web application with PRTG?
Add Sensor
HTTP Specific
Setting Description
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.
Number of Channels Define how many values the .html file returns. The sensor handles each
value in its own channel 142 . 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 smaller than the number of values that
the HTTP request returns. Otherwise, you get an error message.

1089
Setting Description
inherited 146 .
§ httpsensor
sensor settings.
HTTP Specific
HTTP Specific
1090
Setting Description
Script URL Enter the URL that the sensor connects to. If you enter an absolute URL,
setting of the parent device.
Replacement 1095 .
Value Type Shows the kind of values that the .html file returns.
Setting Description
If Content Changes Define what the sensor does if the content of the web page changes:

changes to the web page content. In combination with a change
when the web page content changes.
1091
Setting Description
scanning interval.
master node.
Authentication
Authentication
Setting Description

login.
1092
Setting Description

authentication.
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1093
Sensors.
Scanning Interval
Scanning Interval

objects' settings.
1094
Maintenance Window.
Access Rights
Access Rights
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,
§ 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.

1095
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?




1096
7.8.62 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 1106 .

§ 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
§ The requested web server must return XML-encoded or JSON-encoded data that matches the format
as defined in section Custom Sensors 3499 .
1097
§ For best sensor performance, we recommend that you specify the content type on the target server,
which is application/xml or application/json.
Add Sensor

Setting Description
inherited 146 .
1098
Setting Description
§ httpsensor
sensor settings.
HTTP Specific
HTTP Specific
Setting Description
loading time.
1099
Setting Description

Replacement 1106 .
URL:
web page.
field below.
web page.
HTTP.
1100
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:
1101
Setting Description
target URL:
agent below.
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 enable 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

login.
1102
Setting Description
authentication.
Sensor Display
Sensor Display
Setting Description

1103
Setting Description
Inherited Settings

Sensors.
Scanning Interval
Scanning Interval
1104

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1105

Channel List
1106
Channel Description
[Value] The values that the web server returns in several channels

Sensors 3499 .
More
Knowledge Base



1107
7.8.63 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 1115 .

§ 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
1108
§ See the Knowledge Base: What to do when I see a CreateUniqueTempDir() error message for my
HTTP Full Web Page sensor?
§ See the Knowledge Base: HTTP Full Web Page sensor is unable to navigate. What can I do?
§ See the Knowledge Base: How can I change the size of PhantomJS full web page screenshots?
§ See the Knowledge Base: Why is my HTTP Full Web Page sensor generating so many temporary
files?
Add Sensor

Setting Description
1109
Setting Description
inherited 146 .
§ httpfullsensor
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.
1110
Setting Description

Replacement 1114 .
Browser Engine Define which browser engine the sensor uses to load the web page:
§ Chromium (recommended): 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 1111 are available.
§ 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
Internet Explorer 11 or higher 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 the 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 runs
under. By default, this is the local Windows "system" user account.
account from the parent device settings 542 .
We recommended that you use this setting if you use Chromium
(recommended) as 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:
1111
Setting Description
§ Discard result (recommended): Do not store the sensor 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 3579 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.
§ 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 3257 settings.
If necessary, you can change the window size of the rendered
screenshots. For details, 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.
1112
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1113
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1114
Channel List
Channel Description
Loading Time The loading time of the full web page in milliseconds (msec)
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?
Why is my HTTP Full Web Page sensor generating so many temporary files?
1115

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?

1116
7.8.64 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.2).
This sensor is especially useful when you want to push data to a PRTG Hosted Monitor instance.
HTTP IoT Push Data Advanced Sensor
For more information about the sensor usage, see section How to Use 1123 .
List 1124 .

§ 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: До п о лн ительн ы е дан н ы е push-о бъекта HTTP IoT
§ Simplified Chinese: HTTP IoT
§ Spanish: Datos push IoT (avanzado) (HTTP)
Remarks
§ This sensor has a fixed port (5051). You cannot change it.
§ This sensor has a fixed SSL/TLS version (HTTPS secured with TLS 1.2 only). You cannot change it.
1117
§ 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 but, in this case, all
other channels record the value of 0 for this push message.
§ If you want to install this sensor on a remote probe and use an HTTPS connection to send push
notifications, you need to make sure that you import the same Secure Sockets Layer (SSL)
certificates to the \cert subfolder of the PRTG program directory 3579 on the remote probe that you use
on the PRTG core server. For more information, see the PRTG Manual: Using Your Own SSL
Certificate with the PRTG Web Server 3583
§ You cannot use this sensor in cluster mode. You can only set it up on a local probe or a remote probe
but not on a cluster probe.
§ 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).
§ For more information about the sensor usage, see the PRTG Manual: How to Use 1123 .
Add Sensor

Setting Description
1118
Setting Description
inherited 146 .
§ pushsensor
§ pushdata
§ httppushsensor
§ iot
§ sigfox
sensor settings.
TLS Settings
TLS Settings
Setting Description
TLS Version The security of the incoming HTTPS push requests:
1119
Setting Description
§ HTTPS (secured with TLS 1.2 only): Send push messages to the probe
system via HTTPS. The sensor only supports connections that are
secured with TLS 1.2. It uses the SSL certificate that is delivered with
PRTG or your own trusted SSL certificate 3583 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 as you use
on the PRTG core server.
PRTG shows this setting for your information only. You cannot
change it.
TLS Port The number of the port on which this sensor listens for incoming HTTPS
requests. This is always 5051.
PRTG shows this setting for your information only. You cannot
change it.
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.
HTTP Push Data
HTTP Push Data
1120
Setting Description
No Incoming Data Define which status 186 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
Setting Description
1121
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1122
Maintenance Window.
Access Rights
Access Rights
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 details about the return value format, see section Custom Sensors 3499 .
The HTTP IoT Push Data Advanced sensor uses the following URLs depending on the type of HTTPS
request.
§ GET 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 3499 .
§ 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 3499 . We strongly recommend
the HTTPS content type application/xml or application/json.
1123
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 3501 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
Channel Description
[Value] The data received from the message encoded in valid Extensible Markup
Language (XML) or JavaScript Object Notation (JSON) in several channels
Sensors 3499 .
1124
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?


1125
7.8.65 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 1132 .

§ 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
1126
Add Sensor
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).
system via HTTPS. The sensor only supports connections secured with
TLS 1.2. It uses the SSL certificate that is delivered with PRTG or your
own trusted SSL certificate 3583 that you imported for the PRTG web
server.
import the same SSL certificates to the remote probe that you use
Port This setting is only visible if you enable HTTP (unsecure) above. Enter the
number of the port on which this sensor listens for incoming HTTP
requests. The default port is 5050.
TLS Port This setting is only visible if you enable HTTPS (secured with TLS 1.2
only) above. Enter the number of the port on which this sensor listens for
incoming HTTPS requests. The default port is 5051.

1127
Setting Description
inherited 146 .
§ pushsensor
§ pushcount
§ httppushsensor
sensor settings.
1128
HTTP Push
HTTP Push
Setting Description
TLS Settings Shows whether the sensor accepts push messages via HTTP or HTTPS.
Port This setting is only visible for sensors that accept push messages via
HTTP. It shows the port number on which this sensor listens for incoming
HTTP requests.
TLS Port This setting is only visible for sensors that accept push messages via
HTTPS. It shows the port number on which this sensor listens for
incoming HTTPS requests.
Request Method Select the request method of the webhook:

§ ANY: Do not use any filter for the request method.
§ GET: 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.
1129
Setting Description

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
Setting Description

1130
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1131
Access Rights
Access Rights
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.
§ 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 per second
1132
Channel Description
More
Knowledge Base


1133
7.8.66 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 1142 .

§ Dutch: HTTP Push Data
§ French: Données HTTP Push
§ German: HTTP Push-Daten
§ Japanese: HTTP
§ Portuguese: Dados de Push (HTTP)
§ Russian: Дан н ы е push-о бъекта HTTP
§ Spanish: Datos push (HTTP)
1134
Remarks
Add Sensor
HTTP Push
Setting Description
(not secure).
server.
1135
Setting Description

Setting Description
inherited 146 .
§ pushsensor
§ pushdata
1136
Setting Description
§ httppushsensor
sensor settings.
HTTP Push
HTTP Push
Setting Description
HTTP requests.

1137
Setting Description

interval.
HTTP Push Data
HTTP Push Data
1138
Setting Description
probe disconnected.
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.
Sensor Display
Sensor Display
Setting Description
1139
Setting Description


Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1140
Maintenance Window.
Access Rights
Access Rights
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 186 .
§ 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.
1141
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

More
Knowledge Base


1142
7.8.67 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 1150 .

§ Dutch: HTTP Push Data geavanceerd
§ French: Données avancé (HTTP Push)
§ German: HTTP Push-Daten (Erweitert)
§ Japanese: HTTP
§ Portuguese: Dados de Push (avançado) (HTTP)
§ Russian: HTTP: Дан н ы е push-о бъекта (Расш ирен н ы й)
§ Spanish: Datos push (avanzado) (HTTP)
Remarks
§ 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 but, in this case, all
other channels record the value of 0 for this push message.
1143
Add Sensor
HTTP Push
Setting Description
(not secure).
server.
1144
Setting Description
inherited 146 .
§ pushsensor
§ pushdata
§ httppushsensor
1145
sensor settings.
HTTP Push
HTTP Push
Setting Description
HTTP requests.


1146
Setting Description

interval.
HTTP Push Data
HTTP Push Data
Setting Description
probe disconnected.
1147
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1148
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
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.
1149
The data that is pushed to this sensor must be valid XML or JSON.
For details about the return value format, see section Custom Sensors 3499 .
The HTTP Push Data Advanced sensor uses the following URLs depending on the type of HTTP request.
§ GET 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 3499 .
§ 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 3499 . 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 3501 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
1150
Channel Description
[Value] The data received from the message encoded in valid Extensible Markup
Language (XML) or JavaScript Object Notation (JSON) in several channels
Sensors 3499 .
More
Knowledge Base


1151
7.8.68 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 1163 .

§ Dutch: HTTP (Transactie)
§ French: Transaction (HTTP)
§ German: HTTP (Transaktion)
§ Japanese: HTTP
§ Portuguese: Transação HTTP
§ Russian: Тран закция HTTP
§ Spanish: Transacción HTTP
Remarks
§ This sensor does not support Secure Remote Password (SRP) ciphers. If you need to use SRP
ciphers, use the Compatibility engine in the sensor settings.
1152
§ See the Knowledge Base: Configuration tips for HTTP Transaction sensors needed
§ See the Knowledge Base: Which user agent should I use in the HTTP Advanced sensor's settings?
Add Sensor

Setting Description
inherited 146 .
1153
Setting Description
§ httptransactionsensor
HTTP Specific
HTTP Specific
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
shows the Down status 186 .
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:
1154
Setting Description
§ Default engine (recommended): 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 option is only visible if you select Compatibility engine above. Choose
from:
§ 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 option is only visible if you select Compatibility engine above. Specify
if the sensor checks the certificate of the URL:
§ Do not check certificates: Do not check the certificates of the web
pages. This is the default setting.
§ 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 186 and displays a corresponding message.
1155
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 (recommended): Allow cookies to be set and read during
the transaction cycle. We recommend that you use this option.
§ Ignore cookies: Do not allow cookies. Use this option if you want to test
the transaction without the use of cookies.
target URL:
agent below.
target URL.
Result Handling Define what PRTG does with the web page that is loaded at the URL:
1156
Setting Description
§ Store result: Store the last result of the web page in the \Logs\sensors
subfolder of the PRTG data directory 3579 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

login.
authentication.
1157
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.
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: 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.
The URL must not be URL encoded.
Replacement 1162 .
1158
Setting Description
URL:
web page.

field below.
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
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.
not possible.
Exclude Keyword Define if the sensor checks the result at the URL for keywords:
1159
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.
not possible.
Sensor Display
Sensor Display
Setting Description
1160
Setting Description

Inherited Settings

Sensors.
1161
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1162
Channel List
Channel Description
Sum The loading time of the complete transaction in milliseconds (msec)

Time of URL [#] The loading time of single URLs in msec
More
Knowledge Base
Configuration tips for HTTP Transaction sensors needed

Which user agent should I use in the HTTP Advanced sensor's settings?


1163
7.8.69 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 1174 .

§ 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
1164
§ This sensor can monitor only one single node in an .xml file and shows the value in one channel. If you
need to monitor more than one node of an .xml document, add the sensor for each target node anew.
§ See the Knowledge Base: Where can I find more information about the HTTP XML/REST Value
sensor?
does PRTG require?
Add Sensor
Sensor Settings
Setting Description
Channel Name Enter a name for the channel that displays the value at the URL.

1165
Setting Description
inherited 146 .
§ ptfsensor
1166
Sensor Settings
Sensor Settings
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 1174 .
XML Node (and optional Enter the name of the node that this sensor checks, or enter a node name
property) 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 1173 .
1167
Setting Description
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 further documentation 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.
§ 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 1174 .
Content Type Define what to include in the header of the request that the sensor sends
to the URL:
§ Enable (recommended): This works for most web servers and is the
recommended setting.
1168
Setting Description
§ 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.
Custom Content Type This setting is only visible if you select Custom above. 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.
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 leave the field empty.
Custom Message Optionally enter a custom sensor message. Use %1 as a placeholder to

automatically fill in the returned XML value. Enter a string or leave the field
empty.
If Channel Value Define what the sensor does when the channel value changes:
Changes

The notification for this sensor can only be triggered if the returned
value is a numeric value. This option does not support strings.
1169
Setting Description
tables, and gauges.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
1170
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1171
Maintenance Window.
Access Rights
Access Rights

1172
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.
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).
1173
About Namespaces
In an .xml document, tags may use namespaces.
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
1174
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?
Is there a tool available that can help me build queries for 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?


1175
7.8.70 Hyper-V Cluster Shared Volume Disk Free Sensor
The Hyper-V Cluster Shared Volume Disk Free sensor monitors a Microsoft Hyper-V cluster shared
volume via PowerShell.
Hyper-V Cluster Shared Volume Disk Free Sensor
List 1182 .

§ Dutch: Hyper-V Cluster Shared Volume Disk Free
§ French: Espace disponible du volume partagé du Cluster Hyper-V
§ 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
§ The parent device of this sensor must be a Windows server that runs Hyper-V.
§ This sensor requires 1177 Remote PowerShell on the target device.

§ This sensor requires WSFC PowerShell Interface on the target device.
1176
§ See the Knowledge Base: Why don't my Hyper-V sensors work after changing names?
sensor, Remote PowerShell must be enabled.
WSFC PowerShell This sensor requires the WSFC (Windows Server Failover Clustering)
Interface PowerShell Interface to be installed on the target machine. You can list all
modules in the PowerShell console with the command Get-Module -
ListAvailable. Here, FailoverClusters has to appear. Under Windows Server
2008 (not officially supported) and Windows Server 2012, 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).
does PRTG require?
1177
Add Sensor
Disk Free Settings
Setting Description
Disk Select the disks that you want to monitor. PRTG creates one sensor for
each disk that you select.
right corner.
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
detailed information, see the Knowledge Base: Why don't my Hyper-V
sensors work after changing names?

Setting Description
1178
Setting Description
inherited 146 .
§ hyperv
§ powershell
§ diskfree
sensor settings.
Disk Free Settings
Disk Free Settings
Setting Description
Disk Shows the name of the disk that this sensor monitors.
1179
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

1180
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
1181

Channel List
Channel Description
Free Bytes The free space in bytes
Free Space The free space in percent

Total The total space in bytes
1182
More
Knowledge Base
Why don't my Hyper-V sensors work after changing names?






1183
7.8.71 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 569 of the parent device.
Hyper-V Host Server Sensor
List 1189 .

§ 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
1184
Remarks
§ This sensor requires Windows Server 2008 R2 or later on the probe system.
§ This sensor requires that the Remote Registry Windows service runs on the target computer.
§ This sensor can use a hybrid approach with Windows performance counters and WMI as fallback to
query data.
probe system and the target computer. Otherwise, a connection via
performance counters is not possible. However, WMI connections might
still work.
Windows version For this sensor to work with Windows performance counters, make sure
that Windows Server 2008 R2 or later is installed 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 For this sensor to work with Windows performance counters, make sure
Windows service that the Remote Registry Windows service runs on the target computer. If
this service does not run, a connection via performance counters is not
possible. However, WMI connections might still work.
1185
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 569 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 133 . Above this number, consider using multiple remote
probes 3557 for load balancing.
For a general introduction to the technology behind WMI, see section Monitoring via WMI 3360 .
Add Sensor

Setting Description
inherited 146 .
1186
Setting Description
§ hypervserversensor
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
1187
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1188
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
1189
Channel Description
CPU Usage Guests The CPU usage of the guests in percent
CPU Usage Hypervisor The CPU usage of the hypervisor in percent
CPU Usage Total The total CPU usage in percent
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 per second (received and sent) on all ports of
the virtual switch
More
Knowledge Base

1190
7.8.72 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 569 of the parent device.
Hyper-V Virtual Machine Sensor
List 1198 .

§ 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
1191
Remarks
query data.
§ This sensor does not support Live Migration.
§ 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 showing the error message The virtual machine is not running or is powered off.
still work.
1192

Add Sensor
Setting Description
Virtual Machines Select the VMs that you want to monitor, including the ones that do not
run. PRTG creates one sensor for each VM that you select.
right corner.
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 detailed
information, see the Knowledge Base: Why don't my Hyper-V sensors
work after changing names?
1193
Setting Description
inherited 146 .
§ wmihypervsensor
sensor settings.
1194
Setting Description
GUID Shows the globally unique identifier (GUID) of the VM that this sensor
monitors.
Virtual Machine Name Shows the name of the VM that this sensor monitors.
Description Shows the description of the VM that this sensor monitors.

Powered-Off VM Handling Define how the sensor reacts to VMs that are powered off:
§ Alarm when VM is powered off (default): Change to the Down status 186
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.
1195
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

1196
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
1197
Channel List
Channel Description
CPU Usage Guest The CPU usage of the guests in percent
CPU Usage Hypervisor The CPU usage of the hypervisor in percent
CPU Usage Total The total CPU usage in percent

IDE: Read Bytes/Sec The disk read speed of the integrated development environment (IDE) in
bytes per second
IDE: Write Bytes/Sec The disk write speed of the IDE in bytes per second
More
Knowledge Base


1198
7.8.73 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 569 of the parent device.
Hyper-V Virtual Netw ork Adapter Sensor
List 1205 .

§ 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
1199
§ Russian: Виртуальн ы й сетево й адап тер Hyper-V
§ Spanish: Adaptador de red virtual Hyper-V
Remarks
query data.
still work.
1200

Add Sensor
Setting Description
Virtual Network Adapters Select the virtual network adapters that you want to monitor. PRTG
creates one sensor for each virtual network adapter that you select.
right corner.
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
detailed information about VM naming, see the Knowledge Base: Why
don't my Hyper-V sensors work after changing names?
1201
Setting Description
inherited 146 .
§ wmihypervvirtualnetworkadapter
1202
Hyper-V Virtual Network Adapter Settings
Hyper-V Virtual Netw ork Adapter Settings
Setting Description
Virtual Network Adapter Shows the name of the virtual network adapter that this sensor monitors.
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
1203
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1204
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Broadcast Packets The number of broadcast packets received per second

Received
Broadcast Packets Sent The number of broadcast packets sent per second
Bytes The number of bytes transferred in total

Bytes Received The number of received bytes
Bytes Sent The number of sent bytes
1205
Channel Description
Directed Packets The number of directed packets received per second

Received
Directed Packets Sent The number of directed packets sent per second
Multicast Packets The number of multicast packets received per second

Received
Multicast Packets Sent The number of multicast packets sent per second
Packets The number of packets transferred in total per second
Packets Received The number of packets received per second
Packets Sent The number of packets sent per second
More
Knowledge Base


1206
7.8.74 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 569 of the parent device.
Hyper-V Virtual Storage Device Sensor
List 1213 .

§ 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
1207
query data.
§ This sensor does not support Live Migration.
still work.

1208
Add Sensor
Hyper-V Virtual Storage Device Settings
Setting Description
Virtual Storage Devices Select the virtual storage devices that you want to monitor. PRTG creates
one sensor for each virtual storage device that you select.
right corner.

1209
Setting Description
inherited 146 .
§ wmihypervvirtualstoragesensor
Setting Description
Virtual Storage Device Shows the unique identifier of the virtual storage device that this sensor
monitors.
1210
Setting Description
Host Operating System Shows the host operating system of the virtual storage device that this
sensor monitors.
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

1211
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1212
Access Rights
Access Rights
Channel List
Channel Description
Errors The number of errors
Read Bytes/Sec The read speed in bytes per second

Write Bytes/Sec The write speed in bytes per second
More
Knowledge Base


1213
7.8.75 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 1226 .

§ Dutch: IMAP
§ French: IMAP
§ German: IMAP
§ Japanese: IMAP
§ Portuguese: IMAP
§ Russian: IMAP
§ Simplified Chinese: IMAP
§ Spanish: IMAP
Remarks
1214
§ 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.
§ This sensor might not work properly when monitoring subfolders of mailboxes. If it has to check
subsequent emails with identical subjects, emails coming in later might not be recognized.
§ 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.
§ See the Knowledge Base: My IMAP sensor does not process HTML emails correctly using regex.
What can I do?
§ See the Knowledge Base: How can I monitor my backup software to be sure backup succeeded last
night?
§ See the Knowledge Base: Can I analyze multipart emails using the IMAP sensor?
§ See the Knowledge Base: My IMAP sensor does not find emails when I check for message date.
What can I do?
Add Sensor

Setting Description
1215
Setting Description
inherited 146 .
§ imapsensor
§ mailsensor
sensor settings.
Connectivity
Connectivity
Setting Description
1216
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 (default): 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.
§ 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 186 .
§ Enforce transport-level security: Try to connect to the server via an
SSL/TLS-secured connection. If the server does not support this, the
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.
1217
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.
scanning interval.
master node.
1218
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.
1219
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 3552 that the "From" field of the email must contain or
match.
Only Include Emails with Define if you want to check the "Subject" field of the emails:
Matching "Subject"
1220
Setting Description
§ 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.

or Check using regular expression above. 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.

or Check using regular expression above. Enter the simple string in plain
text or the regex that the body of the email must contain or match.
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.
1221
Setting Description
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 186 the sensor shows if it does not find any email in
Above Filters the 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.
Validate Latest Email
1222
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: Search the email subject or body with a simple
string in plain text.
§ 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
email contains the Search String you define below.
1223
Setting Description
§ 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
email contains the Search String you define below.
§ 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: Search the email subject or body with a simple
string in plain text.
§ 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.
Ensure 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.
1224
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1225
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
1226
Channel Description
Available The response time in msec

Mailbox Size 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?
1227
7.8.76 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 1233 .

§ 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: Ч ерн ы й сп исо к IP-адресо в н а DNS
§ Simplified Chinese: DNS IP

§ Spanish: IP en lista negra de DNS
Remarks
1228
§ 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.
§ During normal operation, there should be 0 hits and the sensor should show the Up status 186 . 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 3052 .
§ See the Knowledge Base: Is there a list of anti spam black list servers?
does PRTG require?
Add Sensor

Setting Description
1229
Setting Description
inherited 146 .
§ ptfsensor
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).
1230
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
1231
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1232
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Sum The number of blacklist hits found

More
Knowledge Base
Is there a list of anti spam black list servers?
1233


1234
7.8.77 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 1246 .

§ Dutch: IPFIX
§ French: IPFIX
§ German: IPFIX
1235
§ Japanese: IPFIX
§ Portuguese: IPFIX
§ Russian: IPFIX
§ Simplified Chinese: IPFIX
§ Spanish: IPFIX
Remarks
§ You must enable IPFIX export on the device for this sensor to work. The device must send the flow
data stream to the IP address of the probe system.
§ For a general introduction to the technology behind flow monitoring, see section Monitoring Bandwidth
via Flows 3367 .
§ See the Knowledge Base: What is the Active Flow Timeout in flow sensors?
Add Sensor

1236
Setting Description
inherited 146 .
§ bandwidthsensor
§ netflowsensor
sensor settings.
1237
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 UDP
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.
Active Flow Timeout Enter a time span in minutes after which the sensor must receive new flow
(Minutes) data. If the timeout elapses and the sensor receives no new data during
this time, it shows the Unknown status 186 . Enter an integer. The
maximum timeout is 60 minutes.
1238
Setting Description
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 details, 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. If you enable this setting, it can create huge data
files. We recommend that you only use this setting for a short time.
1239
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 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. For each group, choose
from:
§ 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.
1240
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 details, see the Knowledge Base: How can I change the default
groups and channels for flow and Packet Sniffer sensors?
Filtering
For detailed information, see section Filter Rules 1244 .
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.
1241
Sensor Display
Sensor Display
Setting Description

Primary Toplist
Primary Toplist
Setting Description
Primary Toplist Define which Toplist is the primary Toplist of the sensor:
§ Top Talkers
§ Top Connections
1242
Setting Description
§ Top Protocols
§ [Any custom Toplists you add]
PRTG shows the primary Toplist in maps when you add a Toplist
object.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1243
Access Rights
Access Rights

_configuration_traffic.ipp" src-expanded="ss_channel_unit_configuration_traffic.ipp" scale="60.00%" w idth="523"
height="154" styleclass="Image Caption">
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 3077 .
Filter Rules
The following filter rules apply to all Flow (NetFlow, jFlow, sFlow, IPFIX) and Packet Sniffer sensors.
For more information, see section Filter Rules for Flow, IPFIX, and Packet Sniffer Sensors 3536 .
Field Possible Filter Values
IP IP address or DNS name
1244
Port Any number
SourceIP IP address or DNS name
SourcePort Any number
DestinationIP IP address or DNS name
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 IPFIX 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
MAC Physical address
SourceMAC Physical address
1245
DestinationMAC Physical address
Mask Mask values represent subnet masks in the form of a single number
(number of contiguous bits).
DestinationMask Mask values represent subnet masks in the form of a single number
NextHop IP address or DNS name
VLAN VLAN values represent a VLAN identifier (any number).
SourceVLAN VLAN values represent a VLAN identifier (any number).
DestinationVLAN VLAN values represent a VLAN identifier (any number).
Channel List
Channel Description
Chat The traffic from chat and instant messaging (Internet Relay Chat (IRC),
AOL Instant Messenger (AIM)) in bytes per second
Citrix The traffic from Citrix applications in bytes per second
FTP/P2P The traffic from file transfer (File Transfer Protocol (FTP)/Peer-to-Peer
(P2P)) in bytes per second
Infrastructure The traffic from network services (Dynamic Host Configuration Protocol
(DHCP), Domain Name System (DNS), Ident, Internet Control Message
Protocol (ICMP), Simple Network Management Protocol (SNMP)) in bytes
per second
Mail The internet mail traffic (Internet Message Access Protocol (IMAP), Post
Office Protocol version 3 (POP3), Simple Mail Transfer Protocol (SMTP))
in bytes per second
1246
Channel Description
NetBIOS The traffic from NetBIOS communication in bytes per second
Other The traffic from various other protocols (User Datagram Protocol (UDP),
Transmission Control Protocol (TCP)) in bytes per second
Remote Control The traffic from remote control applications (Remote Desktop Protocol
(RDP), Secure Shell (SSH), Telnet, Virtual Network Computing (VNC)) in
bytes per second
Total The total traffic in bytes per second

Various The traffic from various other sources in bytes per second
WWW The traffic from the web (HTTP, HTTPS) in bytes per second
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
1247
7.8.78 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 1258 .

§ Dutch: IPFIX (aangepast)
§ French: IPFIX personnalisé
§ German: IPFIX (Benutzerdef.)
1248
§ Japanese: IPFIX
§ Portuguese: IPFIX (customizado)
§ Russian: IPFIX (н естан дартн ы й)
§ Simplified Chinese: IPFIX ( )

§ Spanish: IPFIX (personalizado)
Remarks
§ You must enable IPFIX export on the device for this sensor to work. The device must send the flow
data stream to the IP address of the probe system.
§ For a general introduction to the technology behind flow monitoring, see section Monitoring Bandwidth
via Flows 3367 .
Add Sensor

1249
Setting Description
inherited 146 .
§ bandwidthsensor
§ netflowsensor
sensor settings.
1250
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
port.
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.
1251
Setting Description

Sampling Rate This setting is only visible when sampling mode is On above. 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 detailed information, see section Channel Definitions for Flow,
IPFIX, and Packet Sniffer Sensors 3538 .
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.
interval.
1252
Sensor Display
Sensor Display
Setting Description

Filtering
1253
Filtering
Setting Description
Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
1254
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
1255
Toplists
Filter Rules
Port Any number
1256

(OSPF), any number
The following filter rules apply to IPFIX sensors only.
ASI Any number
1257
Channel List
Channel Description
[Custom] The traffic by type according to the channel definition
Other All traffic for which no channel is defined in bytes per second

More
Knowledge Base


PAESSLER TOOLS
NetFlow Tester
1258
7.8.79 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 1266 .

§ Dutch: IPMI System Health
§ French: IPMI état du système
§ German: IPMI Systemzustand
§ Japanese: IPMI
§ Portuguese: Funcionamento do sistema IPMI
§ Russian: Рабо то сп о со бн о сть систем ы IPMI
§ Simplified Chinese: IPMI
1259
§ Spanish: Salud de sistema IPMI
Remarks
§ You must explicitly specify the credentials of the IPMI in the sensor settings.
does PRTG require?
Add Sensor
Before you can add this sensor, PRTG asks you to provide your credentials for the IPMI.
1260
IPMI Credentials
Setting Description
User Name Enter the user name for the IPMI.
Password Enter the password for the IPMI. Click OK to define the sensor settings.
This sensor only supports passwords with a maximum of 16
characters.
IPMI Specific
Setting Description
Groups Select the metrics that you want to monitor. PRTG creates one sensor for
each metric that you select.
right corner.

1261
Setting Description
inherited 146 .
§ ipmi
sensor settings.
1262
IPMI Credentials
IPMI Credentials
Setting Description
User Name Enter the user name for the IPMI. If you did not change it already, this field
shows the user name that you defined during sensor creation.
Password Enter the password for the IPMI. If you did not change it already, this field
shows the encrypted password that you defined during sensor creation.
This sensor only supports passwords with a maximum of 16
characters.
IPMI Specific
IPMI Specific
Setting Description
Group Shows the metric that this sensor monitors.

Result Handling Define what PRTG does with the logfile results:
1263
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

1264
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
1265

Channel List
Channel Description
[Value] The status of the value, for example

§ Fan revolutions per minute (RPM)
§ Status of a power supply
§ Temperatures, for example, the system temperature or the peripheral

temperature
§ Voltages
1266
More
Knowledge Base

1267
7.8.80 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 1278 .

§ Dutch: jFlow v5
§ French: jFlow v5
§ German: jFlow v5
§ Japanese: jFlow v5
§ Portuguese: jFlow v5
1268
§ Russian: jFlow v5
§ Simplified Chinese: jFlow v5
§ Spanish: jFlow v5
Remarks
§ You must enable jFlow export of the respective version on the target device for this sensor to work. The
device must send the flow data stream to the IP address of the probe system.
§ For cloning this sensor, the following rules apply. If you add the clone to the same probe, PRTG keeps
the selected IP addresses on which it listens for Flow (NetFlow, jFlow, sFlow, IPFIX) packets. If you
add the clone to a different probe, PRTG selects all available IP addresses by default. You can change
the selected IP addresses in the sensor settings.
§ See the Knowledge Base: How can I change the default groups and channels for flow and Packet
Sniffer sensors?
Add Sensor

1269
Setting Description
inherited 146 .
§ bandwidthsensor
§ jflowsensor
sensor settings.
1270
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
port.
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.
1271
Setting Description

packet data.
interval.
1272
Setting Description


ICMP, and SNMP.
from:
Other.
1273
Setting Description
the Content column.
Filtering
Filtering
Setting Description
1274
Sensor Display
Sensor Display
Setting Description

Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
1275
Setting Description
§ Top Protocols
object.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1276
Access Rights
Access Rights
Toplists
Filter Rules
Port Any number
1277

(OSPF), any number
The following filter rules apply to jFlow v5 sensors only.
ASI Any number
Channel List
1278
Channel Description
per second
in bytes per second
bytes per second

More
Knowledge Base

1279

Where is the volume line in graphs?

1280
7.8.81 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 1290 .

§ Dutch: jFlow v5 (Klant specifiek)
§ French: jFlow v5 personnalisé
§ German: jFlow v5 (Benutzerdefiniert)
§ Japanese: jFlow v5
1281
§ Portuguese: jFlow v5 (customizado)
§ Russian: jFlow v5 (н естан дартн ы й)
§ Simplified Chinese: jFlow v5 ( )

§ Spanish: jFlow v5 (personalizado)
Remarks
§ You must enable jFlow export of the respective version on the target device for this sensor to work. The
device must send the flow data stream to the IP address of the probe system.
Add Sensor

Setting Description
1282
Setting Description
inherited 146 .
§ bandwidthsensor
§ jflowsensor
sensor settings.
1283
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
port.
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.
1284
Setting Description

an integer.
packet data.
1285
Setting Description
interval.
Filtering
Filtering
Setting Description
1286
Sensor Display
Sensor Display
Setting Description

Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
1287
Setting Description
§ Top Protocols
object.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1288
Access Rights
Access Rights
Toplists
Filter Rules
Port Any number
1289

(OSPF), any number
The following filter rules apply to jFlow v5 sensors only.
ASI Any number
Channel List
1290
Channel Description

More
Knowledge Base



1291
7.8.82 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 1297 .

§ Dutch: LDAP
§ French: LDAP
§ German: LDAP
§ Japanese: LDAP
§ Portuguese: LDAP
§ Russian: LDAP
§ Simplified Chinese: LDAP
§ Spanish: LDAP
Remarks
§ This sensor officially supports Microsoft implementations of LDAP. Other third-party LDAP
implementations might work but are not officially supported.
§ This sensor requires a DNS name in the settings of the parent device if you use a Secure Sockets
536
Layer (SSL)/Transport Layer Security (TLS) secured connection to the LDAP server.
1292
Add Sensor

Setting Description
inherited 146 .
§ ldapsensor
1293
Setting Description
sensor settings.
LDAP Specific
LDAP Specific
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 536 . 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. Enter a custom
port for the connection to the LDAP server. Enter an integer.
1294
Setting Description
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

1295
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
1296
Channel List
Channel Description

More
Knowledge Base

1297
7.8.83 Local Folder Sensor (BETA)
The Local Folder sensor monitors a local folder on a probe system.
Local Folder Sensor
List 1304 .

§ Dutch: Local Folder
§ French: Local Folder
§ German: Local Folder
§ Japanese: Local Folder
§ Portuguese: Local Folder
§ Russian: Local Folder
§ Simplified Chinese: Local Folder
§ Spanish: Local Folder
1298
Remarks
device.
Add Sensor

Setting Description
1299
Setting Description
inherited 146 .
§ filesystem
§ folder
Local Folder Specific
Local Folder Specific
Setting Setting
Path Enter the path of the folder that you want to monitor. For example, enter
1300
Setting Setting
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).
Recurse Subfolders Specify if the sensor includes subfolders in the folder monitoring. Choose
between:
subfolders.
issues.
Filter by File Name Select if you want to filter by file name. Choose between:
§ 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 field 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 (*).
File Age Filter Select if you want to filter by file age. Choose between:
§ Disable (default): Do not filter by file age.
§ Enable: Filter by file age.
Newer Than This field 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 field is only visible if you select Enable above Enter a file age. The
sensor only counts files that are older than this age.
1301
Setting Setting
Leave this field empty if you only want to filter for files with the Newer
Than setting.
File Age Filter Unit This field is only visible if you select Enable above. Select the time unit
that you want to use for the File Age Filter. Choose between:
§ Days (default)
§ Hours
§ Minutes
Sensor Display
Sensor Display
Setting Setting


1302
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval
1303
objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description

1304
Channel Description
Folder Count The number of folders

the future.
More
Knowledge Base


1305
7.8.84 Microsoft 365 Mailbox Sensor (BETA)
The Microsoft 365 Mailbox sensor monitors a Microsoft 365 mailbox.
Microsoft 365 Mailbox Sensor
List 1315 .

§ Dutch: Microsoft 365 Mailbox
§ French: Microsoft 365 Mailbox
§ German: Microsoft 365 Mailbox
§ Japanese: Microsoft 365 Mailbox
§ Portuguese: Microsoft 365 Mailbox
§ Russian: Microsoft 365 Mailbox
§ Simplified Chinese: Microsoft 365 Mailbox
§ Spanish: Microsoft 365 Mailbox
1306
Remarks
§ This sensor requires credentials for Microsoft 365 557 in the settings of an object that is higher in the
object hierarchy 140 .
§ This sensor requires 1307 that the Beta Sensors experimental feature is enabled.
§ This sensor requires 1307 that the PRTG web server accepts incoming HTTPS requests.
§ This sensor requires 1307 permissions for Microsoft Graph.
§ This sensor requires 1308 that you provide a redirect URI in the Microsoft Azure Portal.
§ See the Knowledge Base: How do I obtain credentials and set permissions for the Microsoft 365
Mailbox sensor?
Limitations and Known Issues

§ This sensor currently only monitors the Inbox folder of a Microsoft 365 mailbox.
§ This sensor currently does not support reauthorization. If you change OAuth 2.0 settings in Microsoft
Azure that require a reauthorization, you must add the sensor anew.
§ To use this sensor, add it to a device that inherits the credentials for Microsoft 365 from a parent
object. Alternatively, create a device without credentials, open the device settings, enter the
credentials for Microsoft 365, and click Save. If you want to add the sensor to an existing device, open
the device settings and save the settings without changes again. We will improve the usability with the
next PRTG version.
This sensor requires that the Beta Sensors experimental feature 3239 of
Enabled Beta Sensors PRTG is enabled.
experimental feature
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 3224 .
This sensor requires the following delegated permissions to query data

Permission for the APIs from Microsoft Graph:
§ Microsoft Graph / User.Read
§ Microsoft Graph / Mail.Read
§ Microsoft Graph / Mail.Read.Shared (optional)
1307
§ 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 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 or
http://localhost.
If you access the PRTG web interface via localhost, you can provide
http://localhost/ms365.htm as redirect URI.
credentials and set permissions for the Microsoft 365 Mailbox
sensor?
Add Sensor

Setting Description
1308
Setting Description
inherited 146 .
§ mailsensor
§ microsoft365
§ microsoft365sensor
sensor settings.
Microsoft OAuth 2.0 Specific
Setting Description
Authorization The OAuth 2.0 authorization renew feature is currently under

development. If you change OAuth 2.0 settings in Microsoft Azure
that require a reauthorization, you must add the sensor anew.
1309
Microsoft 365 Mailbox Settings
Microsoft 365 Mailbox Settings
Setting Description
Filter by 'Subject' Select if you want to filter the emails by their subject. Choose between:
§ Disable (default): Do not use Filter by 'Subject'.
§ Equals: Filter emails whose subject equals the defined string.
§ Contains: Filter emails whose subject contains the defined string.
If you enable Filter by 'Subject', Filter by 'From', or Filter by 'Body', the

sensor creates three additional channels that monitor the emails that
match your filters.
1310
Setting Description
If you disable the filters, the additional channels remain, but do not
receive data anymore.
Search for Enter a string that you want to use for Filter by 'Subject'.
If you select Contains above, you can also enter a comma-separated
list of strings to search for items that contain more than one string.
For example, if you enter backup and failed, the sensor counts all items
that contain both strings.
Filter by 'From' Select if you want to filter the 'From' field of the emails. Choose between:
§ Disable (default): Do not use Filter by 'From'.
§ Equals: Filter emails whose 'From' field equals the defined string.
§ Contains: Filter emails whose 'From' field contains the defined string.

match your filters.
Search for Enter a string that you want to use for Filter by 'From'.
Filter by 'Body' Select if you want to filter the emails by their body. Choose between:
§ Disable (default): Do not use Filter by 'Body'.
§ Equals: Filter emails whose body equals the defined string.
§ Contains: Filter emails whose body contains the defined string.

match your filters.
Search for Enter a string that you want to use for Filter by 'Body'.
1311
Setting Description
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) Enter the maximum age in minutes. The sensor only processes emails
that are younger. Enter an integer.
Shared Mailbox User Enter the user principal name of a shared mailbox to which the
Principal Name authenticated user account has access. Leave the field empty to use the
mailbox of the authenticated user account.
Sensor Display
Sensor Display
Setting Description


1312
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval
1313
objects' settings.
Maintenance Window.
Access Rights
Access Rights

1314
Channel List
Channel Description
Matching Emails The number of emails that match the defined filters
This channel will only be 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
1315
Channel Description
Oldest Matching Email The age of the oldest email that matches the defined filters
More
Knowledge Base
How do I obtain credentials and set permissions for the Microsoft 365 Mailbox sensor?

1316
7.8.85 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 1322 .

§ Dutch: Microsoft 365 Service Status
§ French: Microsoft 365 Service Status
§ German: Microsoft 365 Service Status
§ Japanese: Microsoft 365 Service Status
§ Portuguese: Microsoft 365 Service Status
§ Russian: Microsoft 365 Service Status
§ Simplified Chinese: Microsoft 365 Service Status
§ Spanish: Microsoft 365 Service Status
Remarks
1317
Service Status sensors?
Permission for the APIs This sensor requires sufficient rights to query data from Microsoft Graph:
§ API / Permissions name: Microsoft Graph / ServiceHealth.Read.All

credentials and set permissions for the Microsoft 365 Service Status
sensors?
Add Sensor

Setting Description
1318
Setting Description
inherited 146 .
§ microsoft365
sensor settings.
Sensor Display
Sensor Display
Setting Description
1319
Setting Description

Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
1320
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
1321
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 a warning state
1322
More
Knowledge Base
1323
7.8.86 Microsoft 365 Service Status Advanced Sensor
The Microsoft 365 Service Status Advanced sensor monitors the detailed status of all services of a
Microsoft 365 subscription.
Microsoft 365 Service Status Advanced Sensor
List 1330 .

§ Dutch: Microsoft 365 Service Status Advanced
§ French: Microsoft 365 Service Status Advanced
§ German: Microsoft 365 Service Status Advanced
§ Japanese: Microsoft 365 Service Status Advanced
§ Portuguese: Microsoft 365 Service Status Advanced
§ Russian: Microsoft 365 Service Status Advanced
§ Simplified Chinese: Microsoft 365 Service Status Advanced
§ Spanish: Microsoft 365 Service Status Advanced
Remarks
1324
Service Status sensors?
Permission for the APIs This sensor requires sufficient rights to query data from Microsoft Graph:
§ API / Permissions name: Microsoft Graph / ServiceHealth.Read.All

credentials and set permissions for the Microsoft 365 Service Status
sensors?
Add Sensor
Microsoft 365 Specific
Setting Description
Service Select the services that you want to monitor. PRTG creates one sensor
for each service that you select.
right corner.

1325
Setting Description
inherited 146 .
§ microsoft365
sensor settings.
1326
Setting Description
Service Shows the name of the Microsoft 365 service that this sensor monitors.
Workload ID Shows the Microsoft 365 Workload ID of the service that this sensor
monitors.
Microsoft 365 Settings
Microsoft 365 Settings
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
1327
Setting Description

Debug Options
Debug Options
Setting Description
master node.
1328
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1329
Access Rights
Access Rights

Channel List
Channel Description
1330
Channel Description
Overall Status The overall status of all services

§ Up status 186 : 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

1331
7.8.87 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 1339 .

§ Dutch: Microsoft Azure SQL Database
§ French: Microsoft Azure SQL Database
§ German: Microsoft Azure SQL Database
§ Japanese: Microsoft Azure SQL Database
§ Portuguese: Microsoft Azure SQL Database
1332
§ Russian: Microsoft Azure SQL Database
§ Simplified Chinese: Microsoft Azure SQL Database
§ Spanish: Microsoft Azure SQL Database
Remarks
§ This sensor requires credentials for Microsoft Azure 558 in settings that are higher in the object
§ This sensor requires 1333 an Azure custom role with permissions for specific actions.
§ See the Knowledge Base: How do I obtain credentials and create custom roles for the Microsoft Azure
sensors?
Permissions for the This sensor requires an Azure custom role with specific permissions.
Azure custom role 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/Read",
§ "Microsoft.Insights/Components/providers/Microsoft.Insights/MetricDefin
itions/Read"

credentials and create custom roles for the Microsoft Azure sensors?
Add Sensor
Microsoft Azure Specific
1333
Setting Description
Azure SQL Databases You see a list of all Azure SQL Databases that are available in the
monitored Microsoft Azure subscription. All databases are listed by
database name, server name, resource type, region, purchase model, and
elastic pool name.

right corner.

Setting Description
inherited 146 .
1334
Setting Description
§ microsoftazure
§ microsoftazuresqldatabase
§ azure
sensor settings.
Setting Description
Azure SQL Database Shows the name of the Azure SQL Database that this sensor monitors.
Name
If you change the database name in your Microsoft Azure
subscription, you need to add the sensor anew.
Azure SQL Database ID Shows the ID of the Azure SQL Database that this sensor monitors.
Azure SQL Server Name Shows the name of the Azure SQL server that hosts the Azure SQL
Database.
1335
Setting Description
Resource Type Shows 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 need to add the sensor anew.
Region Shows the Azure region of the Azure SQL Database that this sensor
monitors.
Purchasing Model Shows the purchasing model of the Azure SQL Database. This can be
vCore based or DTU based.
Elastic Pool Shows 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

1336
Setting Description
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
1337
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1338
Channel List
Channel Description
Connections Failed The number of failed connections
CPU Used % The CPU usage in percent

Data I/O % The data input/output (I/O) operations in percent
Data Space Used The data space usage in bytes
Data Space Used % The data space usage in percent
Deadlocks The number of deadlocks
DTU % The Database Transaction Units (DTUs) in percent
1339
Channel Description
DTU Limit The DTU limit
DTU Used The used DTU
eDTU Limit The elastic Database Transaction Unit (eDTU) limit
eDTU Used The used eDTU
Log I/O The log I/O operations in percent
Sessions % The sessions in percent
More
Knowledge Base

1340
7.8.88 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 1348 .

§ Dutch: Microsoft Azure Storage Account
§ French: Microsoft Azure Storage Account
§ German: Microsoft Azure Storage Account
§ Japanese: Microsoft Azure Storage Account
§ Portuguese: Microsoft Azure Storage Account
§ Russian: Microsoft Azure Storage Account
§ Simplified Chinese: Microsoft Azure Storage Account
§ Spanish: Microsoft Azure Storage Account
1341
Remarks
§ This sensor requires credentials for Microsoft Azure in settings that are higher in the object
558

sensors?
actions:
§ "Microsoft.Storage/storageAccounts/read",
§ "Microsoft.Insights/Metrics/Read"

Add Sensor
Setting Description
Storage Accounts You see a list of all storage accounts that are available in the monitored
Microsoft Azure subscription. All storage accounts are listed by name,
account kind, region, and resource group.
1342
Setting Description

right corner.

Setting Description
inherited 146 .
§ microsoftazure
§ microsoftazurestorageaccount
1343
Setting Description
§ azure
sensor settings.
Setting Description
Storage Account Name Shows the name of the storage account that this sensor monitors.
Storage Account ID Shows the ID of the storage account that this sensor monitors.
Account Kind Shows the kind of the storage account that this sensor monitors.
Region Shows the Azure region of the storage account that this sensor monitors.
Resource Group Shows the Microsoft Azure resource group of the storage account that
this sensor monitors.
1344
Sensor Display
Sensor Display
Setting Description

Debug Options
Debug Options
Setting Description
1345
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1346
Maintenance Window.
Access Rights
Access Rights

1347
Channel List
Channel Description
Average E2E Latency The average E2E latency in milliseconds (msec)

Request Breakdown The number of request breakdowns
Storage Latency The latency of the storage in msec
Total Egress The total egress in bytes
Total Ingress The total ingress in bytes
Used Capacity The used capacity in bytes
More
Knowledge Base

1348
7.8.89 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 1356 .

§ Dutch: Microsoft Azure Subscription Cost
§ French: Microsoft Azure Subscription Cost
§ German: Microsoft Azure Subscription Cost
§ Japanese: Microsoft Azure Subscription Cost
§ Portuguese: Microsoft Azure Subscription Cost
§ Russian: Microsoft Azure Subscription Cost
§ Simplified Chinese: Microsoft Azure Subscription Cost
1349
§ Spanish: Microsoft Azure Subscription Cost
Remarks
558

§ This sensor does not support cloud solution provider (CSP) subscriptions.
§ This sensor currently does not support the new billing concept.
sensors?
actions:
§ "Microsoft.Consumption/*/read",
§ "Microsoft.Consumption/*/action",
§ "Microsoft.CostManagement/query/read",
§ "Microsoft.Billing/*/read"

Add Sensor
Setting Description
Budgets PRTG creates two default channels, one for the last period cost and one
for the current period cost. Select if you want to create additional channels
for the budget usage in your Microsoft Azure subscription.
1350
Setting Description
Cost Forecast Select if you want to create an additional channel with a cost forecast for
your Microsoft Azure subscription.

Setting Description
inherited 146 .
1351
Setting Description
§ microsoftazure
§ microsoftazuresubscriptioncost
§ azure
sensor settings.
Setting Description
Budgets Shows if additional channels for the budget usage in your Microsoft Azure
subscription are enabled or disabled.
Cost Forecast Shows 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.
1352
Setting Description
Most Expensive Service This field is only visible if you select Most Expensive Service above.
Category Select the category for which you want to show the most expensive
service in the sensor message. Choose between:
§ Resource group
§ Resource type
§ Resource ID
§ Location
§ Service name
Sensor Display
Sensor Display
Setting Description


1353
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval
1354
objects' settings.
Maintenance Window.
Access Rights
Access Rights

1355
Channel List
Channel Description
Current Period Cost The current period cost
Forecast The cost forecast
[Budget] Used The used budget

[Budget] Used % The used budget in percent
Previous Period Cost The previous period cost
More
Knowledge Base
1356

1357
7.8.90 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 1365 .

§ Dutch: Microsoft Azure Virtual Machine
§ French: Microsoft Azure Virtual Machine
§ German: Microsoft Azure Virtual Machine
§ Japanese: Microsoft Azure Virtual Machine
§ Portuguese: Microsoft Azure Virtual Machine
§ Russian: Microsoft Azure Virtual Machine
§ Simplified Chinese: Microsoft Azure Virtual Machine
§ Spanish: Microsoft Azure Virtual Machine
1358
Remarks
558

sensors?
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/Read"
§ "Microsoft.Insights/Components/providers/Microsoft.Insights/MetricDefin
itions/Read"

Add Sensor
1359
Setting Description
Virtual Machines You see a list of all VMs available in the monitored Microsoft Azure
subscription. All VMs are listed by name, resource group, region, and the
operating system that they run on. Select the VMs that you want to
monitor. PRTG creates one sensor for each VM that you select.
right corner.

Setting Description
inherited 146 .
1360
Setting Description
§ microsoftazure
§ microsoftazurevirtualmachine
§ azure
sensor settings.
Setting Description
Virtual Machine Name Shows the name of the VM that this sensor monitors.
Virtual Machine ID Shows the ID of the VM that this sensor monitors.
1361
Setting Description
Operating System Shows the operating system of the server on which the VM runs.
Resource Group Shows the Microsoft Azure resource group of the VM that this sensor
monitors.
Region Shows the Azure region of the VM that this sensor monitors.
Sensor Display
Sensor Display
Setting Description

1362
Setting Description
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
1363
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1364
Channel List
Channel Description
Average CPU Usage The average CPU load in percent

CPU Credits Consumed The number of consumed CPU credits
CPU Credits Remaining The number of remaining CPU credits
Status The overall status of the virtual machine

§ Up status 186 : Running (Billed), Starting (Not Billed)
§ Warning status: Stopped (Billed), Stopping (Billed)
§ Down status: Deallocated (Not Billed), Deallocating (Not Billed)
1365
More
Knowledge Base
1366
7.8.91 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 1380 .

§ 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
1367
§ This sensor supports Microsoft SQL server 2005 or later.
depending on it?
the probe computer?
does PRTG require?
Add Sensor
Data
1368
Setting Description
cluster nodes.

edited).
1369
Setting Description

the data table.
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
Sensors 3501 .

1370
Setting Description
inherited 146 .
§ sqlsensor
1371
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.
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.
1372
Data
Sensor Display
Setting Description
using variables.
into the query.
content:
1373
Setting Description

as the number 0.
Number.
Databases 3387 .
is disabled.
1374
Setting Description
string.
value:
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
1375
Setting Description
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup

integer.
1376
Setting Description
point.

master node.
1377
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1378
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1379
Channel List
Channel Description
(msec)
Execution Time The execution time of the specified query in msec
More
Knowledge Base

1380



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

1381
7.8.92 Modbus RTU Custom Sensor
The Modbus RTU Custom sensor connects to a Modbus Remote Terminal Unit (RTU) server and
monitors up to five returned numeric values.
Modbus RTU Custom Sensor
List 1392 .

§ Dutch: Modbus RTU Custom
§ French: Modbus RTU Custom
§ German: Modbus RTU Custom
§ Japanese: Modbus RTU Custom
§ Portuguese: Modbus RTU Custom
§ Russian: Modbus RTU Custom
§ Simplified Chinese: Modbus RTU Custom
§ Spanish: Modbus RTU Custom
Remarks
device.
1382
§ This sensor always uses the serial port of the probe device.
§ See the Knowledge Base: How can I apply Zoom Service Status sensors and Modbus sensors via
device templates?
Add Sensor
Modbus Channel Specific
Setting Description
Channel #1 - #5 Name Enter a name for the channel.

After sensor creation, you can change the name of the channel in the
channel settings 3052 under Name.
Channel #1 - #5 Register Select the type of the register. Choose between:

Type
§ Coil: 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.
It is not possible to change the register type after sensor creation.
Channel #1 - #5 Data This field is only visible if you select Input register or Holding register
Type above. Select the data type of the register. Choose between:
§ 16-bit integer
1383
Setting Description
§ Unsigned 16-bit integer
§ 32-bit integer
§ 64-bit integer
§ Float
§ Double
It is not possible to change the data type after sensor creation.
Channel #1 - #5 Unit This field is only visible if you select Input register or Holding register
under Channel #x Register Type. Enter a unit for the channel.
After sensor creation, you can change the unit of the channel in the
channel settings under Unit.
Channel #2 - #5 You can create up to 5 different channels for this sensor. You must define
at least one data channel, so you see all available settings for Channel #1
without manually enabling it. Additionally, you can define Channel #2 to
Channel #5. To do so, choose between:
§ Disable (default): The sensor does not create this channel.
§ Enable: The sensor creates this channel. Specify at least the name,
type, and register number for this channel below.
You cannot add additional channels after sensor creation.

1384
Setting Description
inherited 146 .
§ modbus
1385
Modbus RTU Specific
Modbus RTU Specific
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. Choose between:

§ None (default)
§ Even
§ Odd
Data Bits Select the number of the data bits of the serial connection. Choose
between:
§ 8 (default)
1386
Setting Description
§ 7
§ 6
§ 5
Stop Bits Select the number of stop bits of the serial connection. Choose between:
§ 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. Choose between:
§ Big-endian (AB CD)
§ Little-endian (DC BA)
§ Big-endian byte swap (BA DC)
§ Little-endian byte swap (CD AB)
1387
Setting Description
Channel #1 - #5 Register Shows the register type of the channel value.

Type
Channel #1 - #5 Register Enter the register number from which you want to retrieve information.
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 may 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 - #5 Value This field is only visible if you select Input register or Holding register
Type under Channel #x Register Type. Select the value type that the channel
displays. Choose between:
§ Absolute: 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.
Type under Channel #x Register Type. Shows the Data Type of the Register
Number.
Channel #1 - #5 Register This field is only visible if you select Input register bit or Holding register
Width bit under Channel #x Register Type. Select the width of the value in the
register. Choose between:
§ 16 bits wide (default)
§ 32 bits wide
§ 64 bits wide
Channel #1 - #5 Bit Index This field is only visible if you select Input register or Holding register
under Channel #x Register Type. Enter the index of the bit that you want
to monitor.
1388
Setting Description
Enter a value between 0 and 15, 31, or 63, depending on the Channel
#1 - #5 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

1389
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval
1390
objects' settings.
Maintenance Window.
Access Rights
Access Rights

1391
Channel List
Channel Description
[Value] The returned numeric values in up to five channels
More
Knowledge Base
How can I apply Zoom Service Status sensors and Modbus sensors via device templates?

1392
1393
7.8.93 Modbus TCP Custom Sensor
The Modbus TCP Custom sensor connects to a Modbus Transmission Control Protocol (TCP) server and
monitors up to five returned numeric values.
Modbus TCP Custom Sensor
List 1402 .

§ Dutch: Modbus TCP Custom
§ French: Modbus TCP Custom
§ German: Modbus TCP Custom
§ Japanese: Modbus TCP Custom
§ Portuguese: Modbus TCP Custom
§ Russian: Modbus TCP Custom
§ Simplified Chinese: Modbus TCP Custom
§ Spanish: Modbus TCP Custom
Remarks
1394
device templates?
Add Sensor
Setting Description
Channel #1 - #5 Name Enter a name for the channel.

Channel #1 - #5 Register Select the type of the register. Choose between:

Type
§ Coil: 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.
It is not possible to change the register type after sensor creation.
Type above. Select the data type of the register. Choose between:
§ 16-bit integer
§ 32-bit integer
1395
Setting Description
§ 64-bit integer
§ Float
§ Double
It is not possible to change the data type after sensor creation.
Channel #1 - #5 Unit This field is only visible if you select Input register or Holding register
under Channel #x Register Type. Enter a unit for the channel.
After sensor creation, you can change the unit of the channel in the
channel settings under Unit.
Channel #2 - #5 You can create up to 5 different channels for this sensor. You must define
at least one data channel, so you see all available settings for Channel #1
without manually enabling it. Additionally, you can define Channel #2 to
Channel #5. To do so, choose between:
§ Disable (default): The sensor does not create this channel.
§ Enable: The sensor creates this channel. Specify at least the name,
type, and register number for this channel below.
You cannot add additional channels after sensor creation.

Setting Description
1396
Setting Description
inherited 146 .
§ modbus
sensor settings.
Modbus TCP Specific
Modbus TCP Specific
1397
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.

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. Choose between:
§ Big-endian (AB CD)
§ Little-endian (DC BA)
§ Big-endian byte swap (BA DC)
§ Little-endian byte swap (CD AB)
Setting Description
Channel #1 - #5 Register Shows the register type of the channel value.

Type
Channel #1 - #5 Register Enter the register number from which you want to retrieve information.
Number
1398
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 may 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 - #5 Value This field is only visible if you select Input register or Holding register
Type under Channel #x Register Type. Select the value type that the channel
displays. Choose between:
§ Absolute: 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.
Type under Channel #x Register Type. Shows the Data Type of the Register
Number.
Channel #1 - #5 Register This field is only visible if you select Input register bit or Holding register
Width bit under Channel #x Register Type. Select the width of the value in the
register. Choose between:
§ 16 bits wide (default)
§ 32 bits wide
§ 64 bits wide
Channel #1 - #5 Bit Index This field is only visible if you select Input register or Holding register
under Channel #x Register Type. 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 - #5 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.
1399
Sensor Display
Sensor Display
Setting Description

Debug Options
Debug Options
Setting Description
1400
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1401
Maintenance Window.
Access Rights
Access Rights

Channel List
1402
Channel Description
[Value] The returned numeric values in up to five channels
More
Knowledge Base

1403
7.8.94 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 1409 .

§ Dutch: MQTT Round Trip
§ French: MQTT Round Trip
§ German: MQTT Round Trip
§ Japanese: MQTT Round Trip
§ Portuguese: MQTT Round Trip
§ Russian: MQTT Round Trip
§ Simplified Chinese: MQTT Round Trip
§ Spanish: MQTT Round Trip
Remarks
§ This sensor requires credentials for MQTT 559 in settings that are higher in the object hierarchy 140 , for
1404
§ 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.
Add Sensor

Setting Description
inherited 146 .
§ roundtrip
§ mqttroundtrip
1405
sensor settings.
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 (default): 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
1406
Setting Description

Debug Options
Debug Options
Setting Description
master node.
1407
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
1408

Channel List
Channel Description
Publisher Connection The time it takes the publisher to connect in milliseconds (msec)
Time
Round Trip Time The round-trip time (RTT) of the message (after both publisher and
subscriber connect) in msec
Status The status of the round trip
1409
Channel Description
§ Up status 186 : Roundtrip Complete

§ Down status: Message Not Received, Message Not Sent, Publisher
Could Not Connect, Subscriber Could Not Connect
Subscribe Connection The time it takes the subscriber to connect in msec

Time
More
Knowledge Base

1410
7.8.95 MQTT Statistics Sensor
The MQTT Statistics sensor monitors a Message Queue Telemetry Transport (MQTT) topic.
MQTT Statistics Sensor
List 1416 .

§ Dutch: MQTT Statistics
§ French: MQTT Statistics
§ German: MQTT Statistics
§ Japanese: MQTT Statistics
§ Portuguese: MQTT Statistics
§ Russian: MQTT Statistics
§ Simplified Chinese: MQTT Statistics
§ Spanish: MQTT Statistics
Remarks
1411
Add Sensor

Setting Description
inherited 146 .
§ mqtt
§ mqttstatistics
1412
Setting Description
sensor settings.
MQTT Specific
MQTT Specific
Setting Description
Topic Enter the topic that you want to monitor.

The sensor supports single-level (+) and multi-level (#) wildcards.
Sensor Display
Sensor Display
Setting Description
1413
Setting Description

Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
1414
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1415
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 in bytes
More
Knowledge Base

1416
7.8.96 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 1424 .

§ Dutch: MQTT Subscribe Custom
§ French: MQTT Subscribe Custom
§ German: MQTT Subscribe Custom
§ Japanese: MQTT Subscribe Custom
§ Portuguese: MQTT Subscribe Custom
§ Russian: MQTT Subscribe Custom
§ Simplified Chinese: MQTT Subscribe Custom
§ Spanish: MQTT Subscribe Custom
1417
Remarks
Add Sensor
MQTT Specific
Setting Description
Channel #1 Name Enter a name for the channel.

Channel #1 Unit Enter the unit for the numeric value that this sensor monitors.
After sensor creation, you can change the unit in the channel settings
under Unit.
Channel #1 - #10 Value Select the value type that the channel displays:
Type
§ 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.
§ Delta (counter): Counter values. PRTG calculates the difference

between the last and the current value. Enter an integer. PRTG
additionally divides the delta value by a time period to indicate a speed
value.
It is not possible to change the value type after sensor creation.
Channel #2 - #10 You can define up to 10 channels. You must define at least one data
channel, so you see all available settings for Channel #1. Specify how to
handle all other possible channels:
§ Enable: Create this channel. Specify name, unit, and JSONPath for this
channel below.
1418
Setting Description
You can add additional channels after creation in the sensor's

Settings tab.

Setting Description
inherited 146 .
§ mqtt
§ mqttsubscribecustom
1419
Setting Description
sensor settings.
MQTT Specific
MQTT Specific
Setting Description
Topic Enter the topic that you want to monitor.

The sensor supports single-level (+) and multi-level (#) wildcards.
Sensor Message Optionally enter the path to the value in the JSON data that the sensor
JSONPath shows as sensor message.
The data must be in valid JSON format. For details about the format,
see Channel #x JSONPath below.
The sensor only shows the received string 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:
1420
Setting Description
{
"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 Shows the value type that the channel displays.
Channel #2 - #10 Shows if the channel is enabled or disabled. If you enabled a channel, you
can define the settings of the channel as described above.
You can select Disable (default) if you no longer need the according
channels. You can still see the channels, but they do not receive data
anymore.
Sensor Display
Sensor Display
Setting Description
1421
Setting Description

Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
1422
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1423
Channel List
Channel Description
[Value] The returned numeric values in up to ten channels
More
Knowledge Base

1424
7.8.97 MySQL v2 Sensor
The MySQL v2 sensor monitors a database on a MySQL server and executes a query.
channels.
MySQL v2 Sensor
List 1438 .

§ 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
1425
§ This sensor supports MySQL server versions as of 5.7.
depending on it?
the probe computer?
does PRTG require?
Add Sensor
Data
1426
Setting Description
cluster nodes.

edited).
1427
Setting Description

the data table.
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
Sensors 3501 .

1428
Setting Description
inherited 146 .
§ sqlsensor
sensor settings.
1429
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 the login
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.
§ 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 details about the MySQL SSL modes, refer to the MySQL
documentation.
Data
Sensor Display
1430
Setting Description
using variables.
into the query.
content:

as the number 0.
1431
Setting Description
Number.
Databases 3387 .
is disabled.
1432
Setting Description
string.
value:
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
1433
Setting Description

integer.
1434
Setting Description

point.

master node.
Sensor Display
Sensor Display
Setting Description
1435
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1436
Maintenance Window.
Access Rights
Access Rights

1437
Channel List
Channel Description
(msec)
More
Knowledge Base




1438
1439
7.8.98 NetApp Aggregate 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 1448 .

§ Dutch: NetApp Aggregate
§ French: NetApp agrégat de stockage
§ German: NetApp Aggregat
§ Japanese: NetApp
§ Portuguese: Agregado NetApp
§ Russian: Статистическо е вы ражен ие NetApp
§ Simplified Chinese: NetApp
§ Spanish: Agregado NetApp
1440
Remarks
§ The ONTAPI user account that you use with this sensor needs access to the DATA ONTAP API
1441
(ONTAPI) so that the sensor can request data from it. The access is enabled by default.
§ 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
§ This sensor supersedes the deprecated NetApp cDOT Aggregate (SOAP) sensor.
§ This sensor supports NetApp cDOT as of version 8.3 and NetApp ONTAP as of version 9.0.
§ You can define NetApp API credentials (User Name and Password) in the credentials for Windows
systems 542 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.
does PRTG require?
Enabled ONTAPI access NetApp sensors require access to ONTAPI for the utilized user account.
This 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
Add Sensor
1441
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.
§ Use Windows credentials from parent device: Use the credentials (User
Name and Password) in the parent device settings 542 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.
1442
Setting Description
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.
Click OK to define the sensor settings 1443 .
NetApp Specific
Setting Description
Aggregates Select the aggregates that you want to monitor. PRTG creates one sensor
for each aggregate that you select.
right corner.

1443
Setting Description
inherited 146 .
§ netapp
§ cdot
§ ontap
§ soap
sensor settings.
1444
NetApp Connection
NetApp Connection
Setting Description
string.
1445
NetApp Specific
NetApp Specific
Setting Description
Aggregates Shows the identifier of the aggregate that this sensor monitors.
Debug Options
Debug Options
Setting Description
master node.
1446
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1447
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
1448
Channel Description
Aggregate State The status of the aggregate

§ Up status 186 : Online
§ Warning status: Restrict
§ Down status: Offline, Other Error
Blocks Read The number of blocks read per second
Blocks Written The number of blocks written per second
Bytes Free The free bytes in total
Bytes Free % The free bytes in percent

Data Read The data read speed in bytes per second
Data Written The data write speed in bytes per second
Disks # The number of disks on the aggregate
Files The number of files on the aggregate
Latency The latency in milliseconds (msec)
User Reads The number of user reads per second
User Writes The number of user writes per second
More
Knowledge Base


1449
7.8.99 NetApp I/O Sensor
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 1458 .

§ Dutch: NetApp I/O
§ French: NetApp E/S
§ German: NetApp I/O
1450
§ Japanese: NetApp I/O
§ Portuguese: NetApp E/S
§ Russian: Вво д-вы во д NetApp
§ Simplified Chinese: NetApp I/O
§ Spanish: E/S de NetApp
Remarks
§ The ONTAPI user account that you use with this sensor needs access 1441 to the DATA ONTAP API
§ This sensor supersedes the deprecated NetApp cDOT I/O (SOAP) sensor.
does PRTG require?
true
Add Sensor
1451
NetApp Connection
NetApp Connection
Setting Description
1452
Setting Description
string.
NetApp Specific
Setting Description
System Nodes Select the system nodes that you want monitor. PRTG creates one
sensor for each system node that you select.
right corner.
1453
Setting Description
inherited 146 .
§ netapp
§ cdot
§ ontap
§ soap
1454
sensor settings.
NetApp Connection
NetApp Connection
Setting Description
string.
1455
Setting Description
NetApp Specific
NetApp Specific
Setting Description
System Nodes Shows the ID of the system node that this sensor monitors.
Debug Options
Debug Options
Setting Description
1456
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1457
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
1458
Channel Description
CIFS Ops The number of Common Internet File System (CIFS) operations per
second
Disk Read The disk read speed in bytes per second
Disk Write The disk write speed in bytes per second
FCP Ops The number of Fibre Channel Protocol (FCP) operations per second
FCP Read The FCP read speed in bytes per second
FCP Write The FCP write speed in bytes per second
HDD Read The hard disk drive (HDD) read speed in bytes per second
HDD Write The HDD write speed in bytes per second
HTTP Ops The number of HTTP operations per second
ISCSI Ops The number of Internet Small Computer System Interface (iSCSI)
operations per second
ISCSI Partner Ops The number of iSCSI partner operations per second
ISCSI Partner Read The iSCSI partner read speed in bytes per second
ISCSI Partner Write The iSCSI partner write speed in bytes per second
ISCSI Read The iSCSI read speed in bytes per second
ISCSI Write The iSCSI write speed in bytes per second
Network Read The network read speed in bytes per second
Network Write The network write speed in bytes per second
NFS Ops The number of network file system (NFS) operations per second
1459
Channel Description
SSD Read The solid-state drive (SSD) read speed in bytes per second
SSD Write The SSD write speed in bytes per second
Tape Read The tape read speed in bytes per second
Tape Write The tape write speed in bytes per second
More
Knowledge Base


1460
7.8.100 NetApp LIF 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 1469 .

§ Dutch: NetApp LIF
§ French: NetApp LIF
§ German: NetApp LIF
§ Japanese: NetApp LIF
§ Portuguese: LIF NetApp
§ Russian: LIF NetApp
§ Simplified Chinese: NetApp LIF
§ Spanish: LIF NetApp
Remarks
1461
does PRTG require?
true
Add Sensor
1462
NetApp Connection
NetApp Connection
Setting Description
1463
Setting Description
string.
NetApp Specific
Setting Description
LIFs Select the LIFs that you want to monitor. PRTG creates one sensor for
each LIF that you select.
right corner.

1464
Setting Description
inherited 146 .
§ netapp
§ cdot
§ ontap
§ soap
sensor settings.
1465
NetApp Connection
NetApp Connection
Setting Description
string.
1466
NetApp Specific
NetApp Specific
Setting Description
LIFs Shows the ID of the LIF that this sensor monitors.

Debug Options
Debug Options
Setting Description
Result of Sensor [ID].Data.txt and Result of Sensor [ID].log. This setting
scanning interval.
master node.
1467
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1468
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
1469
Channel Description
Data Received The data received in bytes per second

Data Sent The data sent in bytes per second
Errors Received The number of errors received per second
Errors Sent The number of errors sent per second
Is Home If the logical interface (LIF) is on the home port

§ Up status: Yes
§ Down status: No
More
Knowledge Base


1470
7.8.101 NetApp LUN Sensor
The NetApp LUN sensor monitors the logical unit number (LUN) of a NetApp cDOT or ONTAP storage
(SOAP).
NetApp LUN Sensor
List 1479 .

§ Dutch: NetApp LUN
§ French: NetApp LUN
§ German: NetApp LUN
§ Japanese: NetApp LUN
§ Portuguese: LUN NetApp
§ Russian: LUN NetApp
§ Simplified Chinese: NetApp LUN
1471
§ Spanish: LUN NetApp
Remarks
§ The ONTAPI user account that you use with this sensor needs access to the DATA ONTAP API
1441
does PRTG require?
true
Add Sensor
1472
NetApp Connection
NetApp Connection
Setting Description
1473
Setting Description
string.
NetApp Specific
Setting Description
LUNs Select the logical unit numbers (LUN) that you want to monitor. PRTG
creates one sensor for each LUN that you select.
right corner.

1474
Setting Description
inherited 146 .
§ netapp
§ cdot
§ ontap
§ soap
sensor settings.
1475
NetApp Connection
NetApp Connection
Setting Description
string.
1476
NetApp Specific
NetApp Specific
Setting Description
LUNs Shows the ID of the LUN that this sensor monitors.

Debug Options
Debug Options
Setting Description
scanning interval.
master node.
1477
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1478
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
1479
Channel Description
Bytes Free The free space in bytes
Bytes Free % The free bytes in percent
LUN State The status of the LUN

§ 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 per second
Read Blocks The number of read blocks per second
Read Ops The number of disk read operations per second
SCSI Errors The number of Small Computer System Interface (SCSI) errors per second
Write Blocks The number of write blocks per second
Write Ops The number of disk write operations per second
More
Knowledge Base

1480
1481
7.8.102 NetApp NIC Sensor
The NetApp NIC sensor monitors the network interface card (NIC) of a NetApp cDOT or ONTAP cluster
NetApp NIC Sensor
List 1490 .

§ Dutch: NetApp NIC
§ French: NetApp NIC
§ German: NetApp NIC
§ Japanese: NetApp NIC
§ Portuguese: NIC NetApp
§ Russian: NIC NetApp
§ Simplified Chinese: NetApp NIC
§ Spanish: NIC NetApp
Remarks
1482
does PRTG require?
true
Add Sensor
1483
NetApp Connection
NetApp Connection
Setting Description
1484
Setting Description
string.
NetApp Specific
Setting Description
NICs Select the NICs that you want to monitor. PRTG creates one sensor for
each NIC that you select.
right corner.

1485
Setting Description
inherited 146 .
§ netapp
§ cdot
§ ontap
§ soap
sensor settings.
1486
NetApp Connection
NetApp Connection
Setting Description
string.
1487
NetApp Specific
NetApp Specific
Setting Description
NICs Shows the ID of the NIC that this sensor monitors.

Debug Options
Debug Options
Setting Description
scanning interval.
master node.
1488
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1489
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
1490
Channel Description
Bytes Received The number of bytes received per second

Bytes Sent The number of bytes sent per second
Errors Received The errors received per second
Errors Sent The errors sent per second
Healthy If the system is healthy

§ Up status 186 : Healthy
§ Down status: Unhealthy
§ Unknown status: Not Available
Link Up to Down The number of up to down links per second
More
Knowledge Base


1491
7.8.103 NetApp Physical Disk Sensor
The NetApp Physical Disk sensor monitors disks of a NetApp cDOT or ONTAP storage system
NetApp Physical Disk Sensor
List 1500 .

§ Dutch: NetApp Fysieke Schijf
§ French: NetApp disque physique
§ German: NetApp Physikal. Laufwerk
§ Japanese: NetApp
§ Portuguese: Disco físico NetApp
§ Russian: Физический диск NetApp
§ Spanish: Disco físico NetApp
Remarks
1492
§ This sensor supersedes the deprecated NetApp cDOT Physical Disk (SOAP) sensor.
does PRTG require?
true
Add Sensor
1493
NetApp Connection
NetApp Connection
Setting Description
1494
Setting Description
string.
NetApp Specific
Setting Description
right corner.

1495
Setting Description
inherited 146 .
§ netapp
§ cdot
§ ontap
§ soap
sensor settings.
1496
NetApp Connection
NetApp Connection
Setting Description
string.
1497
NetApp Specific
NetApp Specific
Setting Description
Disk Shows the physical disk that this sensor monitors.

Debug Options
Debug Options
Setting Description
master node.
1498
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1499
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
1500
Channel Description

Data Write The data write speed in bytes per second
Ops Latency The latency of operations in milliseconds (msec)
More
Knowledge Base


1501
7.8.104 NetApp SnapMirror Sensor
The NetApp SnapMirror sensor monitors SnapMirror relationships of a NetApp cDOT or ONTAP storage
(SOAP).
NetApp SnapMirror Sensor
List 1510 .

§ Dutch: NetApp SnapMirror
§ French: NetApp SnapMirror
§ German: NetApp SnapMirror
§ Japanese: NetApp SnapMirror
§ Portuguese: NetApp SnapMirror
§ Russian: NetApp SnapMirror
1502
§ Simplified Chinese: NetApp SnapMirror
§ Spanish: NetApp SnapMirror
Remarks

does PRTG require?
true
Add Sensor
1503
NetApp Connection
NetApp Connection
Setting Description
1504
Setting Description
string.
NetApp Specific
Setting Description
SnapMirrors Select the SnapMirrors that you want to monitor. PRTG creates one
sensor for each SnapMirror that you select.
right corner.
1505
Setting Description
inherited 146 .
§ netapp
§ cdot
§ ontap
§ soap
1506
sensor settings.
NetApp Connection
NetApp Connection
Setting Description
string.
1507
Setting Description
NetApp Specific
NetApp Specific
Setting Description
SnapMirrors Shows the SnapMirror that this sensor monitors.

Debug Options
Debug Options
Setting Description
1508
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1509
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
1510
Channel Description
Healthy If the system is healthy
§ Up status: Yes
§ Down status: No
Lag The lag transfer duration
Last Transfer Duration The duration of the last transfer
Last Transfer Size The size of the last transfer
Last Transfer Timestamp The time stamp of the last transfer
Mirror State The mirror state

§ 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 per second
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 per second
More
Knowledge Base
1511

1512
7.8.105 NetApp System Health Sensor
IMPORTANT INFORMATION
This sensor supports NetApp cDOT as of version 8.3 or ONTAP from version 9.0 to version 9.5. If you
want to use ONTAP as of version 9.6, use the NetApp System Health v2 sensor 1525 instead. The
NetApp System Health v2 sensor is currently part of the Beta Sensors experimental feature 3239 of
PRTG. For more information, see the Knowledge Base: What are beta sensors and how can I use
them?
The NetApp System Health sensor monitors the health of a NetApp cDOT or ONTAP storage system
NetApp System Health Sensor
List 1523 .

§ Dutch: NetApp Systeem Gesteldheid
§ French: NetApp état du système
1513
§ German: NetApp Systemzustand
§ Japanese: NetApp
§ Portuguese: NetApp Funcionamento do sistema
§ Russian: Рабо то сп о со бн о сть систем ы NetApp
§ Spanish: Estado del sistema de NetApp
Remarks
§ The ONTAPI user account that you use with this sensor requires access 1514 to the DATA ONTAP API
§ 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 |
§ This sensor supersedes the deprecated NetApp cDOT System Health (SOAP) sensor.
§ As an alternative to administrator rights, you can add a specific Role Attribute and use read-only
rights. For details, see section Permissions: Alternative to Administrator Rights 1522
does PRTG require?
1514

true
Add Sensor
1515
NetApp Connection
NetApp Connection
Setting Description
1516
Setting Description
string.
NetApp Specific
Setting Description
System Nodes Select the system nodes that you want to monitor. PRTG creates one
sensor for each system node that you select.
right corner.

1517
Setting Description
inherited 146 .
§ netapp
§ cdot
§ ontap
§ soap
sensor settings.
1518
NetApp Connection
NetApp Connection
Setting Description
string.
1519
NetApp Specific
NetApp Specific
Setting Description
System Nodes Shows the ID of the system node that this sensor monitors.
Debug Options
Debug Options
Setting Description
master node.
1520
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1521
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
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.
1522
§ 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
Channel Description
CPU The CPU load in percent

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 186 : 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
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
1523
Channel Description
§ 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


1524
7.8.106 NetApp System Health v2 Sensor (BETA)
The NetApp System Health v2 sensor monitors the health of a node of a NetApp storage cluster via the
Representational State Transfer (REST) application programming interface (API) using ONTAP 9.6 or
later.
This sensor was converted to a new framework so that it will continue to function after the changes
of the ONTAP REST API. This sensor now requires permissions for the ONTAP REST API and
credentials for NetApp 561 in settings that are higher in the object hierarchy 140 , for example, in the
NetApp System Health Sensor
List 1532 .

§ Dutch: NetApp System Health
§ French: NetApp System Health
§ German: NetApp System Health
1525
§ Japanese: NetApp System Health
§ Portuguese: NetApp System Health
§ Russian: NetApp System Health
§ Simplified Chinese: NetApp System Health
§ Spanish: NetApp System Health
Remarks
§ This sensor requires credentials for NetApp 561 in settings that are higher in the object hierarchy 140 ,
for example, in the settings of the parent device. For more information about the required access rights
for the user account, see Detailed Requirements 1526 below.
§ This sensor requires permissions for the ONTAP REST API. For more information, see Detailed
Requirements 1526 below.
§ 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 System Health sensor 1513 instead.
Credentials for NetApp This sensor requires a 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 the role readonly with the following permissions for
ONTAP REST API the ONTAP REST API:
Access level Read-Only:
§ /api
§ /api/security/audit/destinations
Access level Read/Write:

§ /api/security/authentication/password
1526
Access level None:

§ /api/security
Add Sensor
NetApp Specific
Setting Description
Node Name Select the nodes that you want to monitor. PRTG creates one sensor for
each system node that you select.
right corner.

Setting Description
1527
Setting Description
inherited 146 .
§ netapp
§ ontap
§ rest
sensor settings.
NetApp Specific
NetApp Specific
Setting Description
Node Name Shows the name of the node that this sensor monitors.
1528
Sensor Display
Sensor Display
Setting Description

Debug Options
Debug Options
Setting Description
1529
Setting Description
master node.
Inherited Settings
Scanning Interval
The recommended scanning interval of this sensor is 1 minute.
Scanning Interval

objects' settings.
1530
Maintenance Window.
Access Rights
Access Rights

1531
Channel List
Channel Description
Failed PSUs The number of failed power supplies with a predefined upper error limit (0)
Node Health The node health

§ Up status 186 : Up
§ Warning status: Booting, Taken Over, Waiting for Giveback
§ Down status: Down, Degraded, Unknown
§ Unknown status: Channel Value Not Set
Spare Disks Available The number of spare disks with a predefined lower warning limit (2) and
lower error limit (1)
Spare Size Usable The usable spare size in bytes
Temperature State The temperature status
§ Down status: Over
Uptime The uptime in days
More
Knowledge Base


1532
7.8.107 NetApp Volume Sensor
IMPORTANT INFORMATION
This sensor supports NetApp cDOT as of version 8.3 or ONTAP from version 9.0 to version 9.5. If you
want to use ONTAP as of version 9.6, use the NetApp Volume v2 sensor 1546 instead. The NetApp
Volume v2 sensor is currently part of the Beta Sensors experimental feature 3239 of PRTG. For more
information, see the Knowledge Base: What are beta sensors and how can I use them?
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 1543 .

§ Dutch: NetApp Volume
1533
§ French: NetApp volume de stockage
§ German: NetApp Volume
§ Japanese: NetApp
§ Portuguese: NetApp Volume
§ Russian: То м NetApp
§ Spanish: Volumen de NetApp
Remarks
§ The ONTAPI user account that you use with this sensor requires access to DATA ONTAP API
1534
does PRTG require?
true
1534
Add Sensor
NetApp Connection
NetApp Connection
1535
Setting Description
string.
NetApp Specific
Setting Description
Volumes Select the volumes that you want to monitor. PRTG creates one sensor
1536
Setting Description

right corner.
Volumes that are offline do not appear in this list.

Setting Description
inherited 146 .
1537
Setting Description
§ netapp
§ cdot
§ ontap
§ soap
sensor settings.
NetApp Connection
NetApp Connection
Setting Description
1538
Setting Description
string.
NetApp Specific
NetApp Specific
Setting Description
Volumes Shows the volume that this sensor monitors.

Debug Options
Debug Options
1539
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

1540
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1541
Setting Description
§ None
§ Saturdays
§ Sundays
§ Weekdays
§ Weekends

below.
past.
can choose from:

1542
Setting Description
§ Master sensor for parent: Make this sensor the master object for its
parent device. The sensor influences the behavior of its parent device: If
the sensor is in the Down status, the device is paused. For example, it
is a good idea to make a Ping sensor the master object for its parent
device to pause monitoring for all other sensors on the device in case
the device cannot even be pinged. Additionally, the sensor is paused if
the parent group is paused by another dependency.
object will depend.
an integer.
This setting is not available if you set this sensor to Use parent or to
be the Master sensor for parent. In this case, define delays in the
parent device settings 535 or in its parent group settings 479 .
Access Rights
Access Rights
Channel List
1543
Channel Description
Busy Snapshots % The number of busy snapshots in percent
Compression Savings % The compression savings in percent
Compression Savings The compression savings in bytes

Bytes
Deduplication Savings % The deduplication savings in percent
Deduplication Savings The deduplication savings in bytes

Bytes
Files Free The free files in total
Files Free % The free files in percent
Latest Snapshot The age of the last snapshot
Oldest Snapshot The age of the oldest snapshot
Physical Bytes Free The free physical bytes in total
Physical Bytes Free % The free physical bytes in percent
Size Free The free size in total
Size Free % The free size in percent

Size Free For Snapshots The free size for snapshots
Snapshot Reserve Free The free snapshot reserve in percent

%
Snapshots # The number of snapshots
Total Savings % The total savings in percent
Total Savings Bytes The total savings in bytes
1544
More
Knowledge Base

1545
7.8.108 NetApp Volume v2 Sensor (BETA)
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 9.6 or later.
This sensor was converted to a new framework so that it will continue to function after the changes
of the ONTAP REST API. This sensor now requires permissions for the ONTAP REST API and
credentials for NetApp 561 in settings that are higher in the object hierarchy 140 , for example, in the
NetApp Volume Sensor
List 1553 .

§ Dutch: NetApp Volume
§ French: NetApp Volume
1546
§ German: NetApp Volume
§ Japanese: NetApp Volume
§ Portuguese: NetApp Volume
§ Russian: NetApp Volume
§ Simplified Chinese: NetApp Volume
§ Spanish: NetApp Volume
Remarks
§ This sensor requires credentials for NetApp 561 in settings that are higher in the object hierarchy 140 ,
for example, in the settings of the parent device. For more information about the required access rights
for the user account, see Detailed Requirements 1547 below.
§ This sensor requires permissions for the ONTAP REST API. For more information, see Detailed
Requirements 1547 below.
§ 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 Volume sensor 1533 instead.
Credentials for NetApp This sensor requires a 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 the role readonly with the following permissions for
ONTAP REST API the ONTAP REST API:
Access level Read-Only:
§ /api
§ /api/security/audit/destinations
Access level Read/Write:
1547
§ /api/security/authentication/password
Access level None:

§ /api/security
Add Sensor
NetApp Specific
Setting Description
Volume Name Select the volumes that you want to monitor. PRTG creates one sensor
right corner.

1548
Setting Description
inherited 146 .
§ netapp
§ ontap
§ rest
sensor settings.
NetApp Specific
NetApp Specific
1549
Setting Description
Volume Name Shows the name of the node that this sensor monitors.
Aggregate Names Shows the names of the aggregates that contains the volume that this
sensor monitors.
Sensor Display
Sensor Display
Setting Description


1550
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
The recommended scanning interval of this sensor is 1 minute.
Scanning Interval
1551
objects' settings.
Maintenance Window.
Access Rights
Access Rights

1552
Channel List
Channel Description
Autogrow The autogrow status

§ Up status 186 : 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 in percent with a
predefined lower warning limit (25) and lower error limit (10)
Latest Snapshot The time since the latest snapshot
Oldest Snapshot The age of the oldest snapshot
1553
Channel Description
Physical Bytes Free % The free physical bytes in percent with a predefined lower warning limit
(25) and lower error limit (10)
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.
Size Free % The free size in percent with a predefined lower warning limit (25) and
lower error limit (10)
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 with a predefined upper error limit (1024)
Volumes can contain up to 1023 snapshot copies. The limit of this
channel is set to define a fixed size of the gauge 3606 that reflects the
maximum number of snapshot copies that the volume can contain.
More
Knowledge Base


1554
7.8.109 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 1565 .

§ Dutch: NetFlow v5
§ French: NetFlow v5
1555
§ German: NetFlow v5
§ Japanese: NetFlow v5
§ Portuguese: NetFlow v5
§ Russian: NetFlow v5
§ Simplified Chinese: NetFlow v5
§ Spanish: NetFlow v5
Remarks
§ You must enable NetFlow export of the respective version on the target device for this sensor to work.
The device must send the flow data stream to the IP address of the probe system.
Sniffer sensors?
Add Sensor

1556
Setting Description
inherited 146 .
§ bandwidthsensor
§ netflowsensor
1557
NetFlow v5 Specific Settings
Setting Description
Receive Packets on UDP Enter the User Datagram Protocol (UDP) port number on which the flow
Port packets are received. 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
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 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.
1558
Setting Description
If the target device sends incorrect time information that results in
wrong monitoring data, try to use 0 as 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 all data is captured.


packet data.
interval.
1559
Setting Description


ICMP, and SNMP.
from:
Other.
1560
Setting Description
the Content column.
Filtering
Filtering
Setting Description
1561
Sensor Display
Sensor Display
Setting Description

Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
1562
Setting Description
§ Top Protocols
object.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1563
Access Rights
Access Rights
Toplists
Filter Rules
Port Any number
1564

(OSPF), any number
The following filter rules apply to NetFlow v5 sensors only.
ASI Any number
Channel List
1565
Channel Description
per second
in bytes per second
bytes per second

More
Knowledge Base

1566


PAESSLER TOOLS
NetFlow Tester
1567
7.8.110 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 1577 .

§ Dutch: NetFlow v5 (aangepast)
1568
§ French: NetFlow v5 personnalisé
§ German: NetFlow v5 (Benutzerdefiniert)
§ Portuguese: NetFlow v5 (customizado)
§ Russian: NetFlow v5 (н астраиваем ы й)
§ Simplified Chinese: NetFlow v5 ( )
§ Spanish: NetFlow v5 (personalizado)
Remarks
Add Sensor

1569
Setting Description
inherited 146 .
§ bandwidthsensor
§ netflowsensor
1570
Setting Description
specified port.
1571
Setting Description

an integer.
1572
Setting Description

packet data.
interval.
Filtering
Filtering
Setting Description
1573
Sensor Display
Sensor Display
Setting Description

Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
1574
Setting Description
§ Top Protocols
object.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1575
Access Rights
Access Rights
Toplists
Filter Rules
Port Any number
1576

(OSPF), any number
ASI Any number
Channel List
1577
Channel Description

More
Knowledge Base



PAESSLER TOOLS
NetFlow Tester
1578
7.8.111 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 1590 .

§ Dutch: NetFlow v9
§ French: NetFlow v9
1579
§ German: NetFlow v9
§ Portuguese: NetFlow v9
§ Russian: NetFlow v9
§ Simplified Chinese: NetFlow v9
§ Spanish: NetFlow v9
Remarks
Sniffer sensors?
Add Sensor

1580
Setting Description
inherited 146 .
§ bandwidthsensor
§ netflowsensor
1581
Setting Description
specified port.
1582
Setting Description


packet data.
interval.
1583
Setting Description


ICMP, and SNMP.
from:
Other.
1584
Setting Description
the Content column.
Filtering
Filtering
Setting Description
1585
Sensor Display
Sensor Display
Setting Description

Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
1586
Setting Description
§ Top Protocols
object.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1587
Access Rights
Access Rights
Toplists
Filter Rules
Port Any number
1588

(OSPF), any number
ASI Any number
1589
Channel List
Channel Description
per second
in bytes per second
1590
Channel Description
bytes per second

More
Knowledge Base


PAESSLER TOOLS
NetFlow Tester
1591
7.8.112 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 1602 .

§ Dutch: NetFlow v9 (aangepast)
1592
§ French: NetFlow v9 personnalisé
§ German: NetFlow v9 (Benutzerdefiniert)
§ Portuguese: NetFlow v9 (customizado)
§ Russian: NetFlow v9 (н астраиваем ы й)
§ Simplified Chinese: NetFlow v9 ( )
§ Spanish: NetFlow v9 (personalizado)
Remarks
Add Sensor

1593
Setting Description
inherited 146 .
§ bandwidthsensor
§ netflowsensor
1594
Setting Description
specified port.
1595
Setting Description

an integer.
1596
Setting Description

packet data.
interval.
Filtering
Filtering
Setting Description
1597
Sensor Display
Sensor Display
Setting Description

Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
1598
Setting Description
§ Top Protocols
object.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1599
Access Rights
Access Rights
Toplists
Filter Rules
Port Any number
1600

(OSPF), any number
ASI Any number
1601
Channel List
Channel Description

More
Knowledge Base


1602
PAESSLER TOOLS
NetFlow Tester
1603
7.8.113 Network Share Sensor (BETA)
The Network Share sensor monitors a Server Message Block (SMB) or Common Internet File System
(CIFS) network share.
Netw ork Share Sensor
List 1611 .

§ Dutch: Network Share
§ French: Network Share
§ German: Network Share
§ Japanese: Network Share
§ Portuguese: Network Share
§ Russian: Network Share
§ Simplified Chinese: Network Share
1604
§ Spanish: Network Share
Remarks
Add Sensor

Setting Description
1605
Setting Description
inherited 146 .
§ networkshare
§ smb
§ cifs
§ folder
Network Share Specific
Netw ork Share Specific
1606
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).
Recurse Subfolders Specify if the sensor includes subfolders in the folder monitoring. Choose
between:
subfolders.
issues.
Filter by File Name Select if you want to filter by file name. Choose between:
§ 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 field 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 (*).
File Age Filter Select if you want to filter by file age. Choose between:
§ Disable (default): Do not filter by file age.
§ Enable: Filter by file age.
Newer Than This field 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 field 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.
1607
Setting Setting
File Age Filter Unit This field is only visible if you select Enable above. Select the time unit
that you want to use for the File Age Filter. Choose between:
§ Days (default)
§ Hours
§ Minutes
Sensor Display
Sensor Display
Setting Setting

1608
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval
1609
objects' settings.
Maintenance Window.
Access Rights
Access Rights

1610
Channel List
Channel Description

Folder Count The number of folders
the future.
1611
More
Knowledge Base

1612
7.8.114 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 1618 .

§ Dutch: OPC UA Certificate
§ French: OPC UA Certificate
§ German: OPC UA Certificate
§ Japanese: OPC UA Certificate
§ Portuguese: OPC UA Certificate
§ Russian: OPC UA Certificate
§ Simplified Chinese: OPC UA Certificate
§ Spanish: OPC UA Certificate
Remarks
1613
Add Sensor

Setting Description
inherited 146 .
1614
Setting Description
§ opcua
§ opcuacertificate
§ certificate
sensor settings.
Sensor Display
Sensor Display
Setting Description

1615
Setting Description
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
1616
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1617
Channel List
Channel Description
Public Key Length The public key length with a predefined lower warning limit (1025 bits) and
a lower error limit (1024 bits)
Self Signed If a self-signed certificate is used
More
Knowledge Base

1618
7.8.115 OPC UA Custom Sensor
The OPC UA Custom sensor monitors up to ten numeric values returned by specific OPC Unified
Architecture (OPC UA) node IDs.
OPC UA Custom Sensor
List 1626 .

§ Dutch: OPC UA Custom
§ French: OPC UA Custom
§ German: OPC UA Custom
§ Japanese: OPC UA Custom
§ Portuguese: OPC UA Custom
§ Russian: OPC UA Custom
§ Simplified Chinese: OPC UA Custom
§ Spanish: OPC UA Custom
1619
Remarks
§ See the Knowledge Base: Which OPC UA data types does the OPC UA Custom sensor support?
Add Sensor
OPC UA Specific
Setting Description
Channel #1 – #10 Select the naming method for the channels of the sensor. Choose
Naming Method between:
§ Use automatic naming (default): The sensor uses the name provided by
the OPC UA node.
You cannot use automatic naming after you created the sensor.
§ Enter custom name: Enter a custom name in field Channel #1 - #10
Name.
Channel #1 - #10 Unit Enter the unit for the numeric value that this sensor monitors.
After sensor creation, you can change the unit in the channel settings
under Unit.
Channel #1 – #10 Node Enter the node ID from which you want to receive numeric data.
ID
A node ID looks like this, for example: ns=1;i=1234 or
ns=2;s=test_one. The sensor supports string identifiers and numeric
identifiers.
1620
Setting Description
§ Enable: Create this channel. Specify name, unit, and node ID for this
channel below.
sensor settings.

Setting Description
inherited 146 .
1621
Setting Description
§ opcua
§ opcuacustom
OPC UA Specific
OPC UA Specific
Setting Description
Sensor Message Node ID Optionally enter the node ID from which you want to receive a string that
the sensor shows as sensor message.
A node ID looks like this, for example: ns=1;i=1234 or
ns=2;s=test_one. The sensor supports string identifiers and numeric
identifiers.
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 Node ID Shows the node ID from which the sensor receives numeric data.
1622
Sensor Display
Sensor Display
Setting Description

Debug Options
Debug Options
Setting Description
1623
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1624
Maintenance Window.
Access Rights
Access Rights

1625
Channel List
Channel Description
[Value] The returned numeric values in up to ten channels
More
Knowledge Base
Which OPC UA data types does the OPC UA Custom sensor support?

1626
7.8.116 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 1632 .

§ Dutch: OPC UA Server Status
§ French: OPC UA Server Status
§ German: OPC UA Server Status
§ Japanese: OPC UA Server Status
§ Portuguese: OPC UA Server Status
1627
§ Russian: OPC UA Server Status
§ Simplified Chinese: OPC UA Server Status
§ Spanish: OPC UA Server Status
Remarks
§ This sensor requires 1628 activated diagnostic summary information settings on your OPC UA server to
create all diagnostic channels.

Activated server This sensor requires activated diagnostic summary information settings on
diagnostics on your OPC your OPC UA server to create all diagnostic channels. Without activated
UA server diagnostic summary information settings, the sensor can only show the
server status and the uptime.
Note that not all vendors support diagnostic summary information.
Add Sensor

1628
Setting Description
inherited 146 .
§ opcua
§ opcuaserverstatus
§ serverstatus
1629
Sensor Display
Sensor Display
Setting Description

Debug Options
Debug Options
Setting Description
1630
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1631
Maintenance Window.
Access Rights
Access Rights

Channel List
1632
Channel Description
Rejected Requests Count The number of rejected requests
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 186 : 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 per second
Session Timeout Count The number of session timeouts
Subscription Count The number of subscriptions per second
Uptime The uptime
More
Knowledge Base

1633
7.8.117 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 1647 .

§ 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
1634
§ This sensor supports Oracle database servers version 10.2 or higher.
depending on it?
the probe computer?
does PRTG require?
Add Sensor
Data
Setting Description
cluster nodes.
1635
Setting Description


edited).
the data table.
1636
Setting Description
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
Sensors 3501 .

1637
Setting Description
inherited 146 .
§ sqlsensor
sensor settings.
1638
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.
The type of identifier that you need to use depends on the
configuration of the Oracle server.
1639
Data
Data
Setting Description
using variables.

into the query.
content:
1640
Setting Description

as the number 0.
Number.
Databases 3387 .
is disabled.
1641
Setting Description
string.
value:
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
1642
Setting Description
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup

1643
Setting Description
integer.
point.

master node.
1644
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1645
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1646
Channel List
Channel Description
(msec)
More
Knowledge Base

1647



1648
7.8.118 Oracle Tablespace Sensor
The Oracle Tablespace sensor monitors a tablespace on an Oracle server.
Oracle Tablespace Sensor
List 1656 .

§ Dutch: Oracle Tablespace
§ French: Tablespace Oracle
§ German: Oracle Tablespace
§ Japanese: Oracle
§ Portuguese: Oracle Tablespace
§ Russian: Tablespace Oracle
§ Simplified Chinese: Oracle
§ Spanish: Oracle Tablespace
1649
Remarks
§ This sensor requires sufficient privileges for the account that you use for the connection. We
1650
recommend that you use the SYSTEM account.

§ This sensor does not support overprovisioning.
§ This sensor supports Oracle database servers version 10.2 or higher.
§ See the Knowledge Base: Why is my Oracle Tablespace sensor showing negative values?

does PRTG require?
Sufficient account Use an account for the connection that has the privileges to see all (or
privileges 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.
Add Sensor
In the appearing dialog box in the Add Sensor dialog, enter an identifier to access the tablespace
selection and click OK.
1650
Oracle Specific
Tablespace Specific
Setting Description
Tablespaces Select the tablespaces that you want to monitor. PRTG creates one
sensor for each tablespace that you select.
right corner.

1651
Setting Description
inherited 146 .
§ sqlsensor
1652
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.
§ 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.
1653
Tablespace Specific
Tablespace Specific
Setting Description
Tablespaces Shows the tablespace that this sensor monitors.

Sensor Display
Sensor Display
Setting Description

1654
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
1655

Channel List
Channel Description
Free Blocks The number of free blocks
Free Blocks % The number of free blocks in percent
Free Space The free space in bytes
Free Space % The free space in percent
Online Status The online status
1656
Channel Description
§ Up status 186 : 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?


1657
7.8.119 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.
The sensor analyzes only header traffic.
Packet Sniffer Sensor
List 1667 .

§ Dutch: Packet Sniffer
§ French: Reniflage de paquets
§ German: Packet Sniffer
1658
§ Japanese:
§ Portuguese: Sniffer de pacotes
§ Russian: Ан ализато р п акето в
§ Spanish: Analizador de paquetes
Remarks
§ By default, this sensor works only on a probe device.
§ 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.
Sniffer sensors?
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.
Add Sensor

1659
Setting Description
inherited 146 .
§ bandwidthsensor
§ sniffersensor
Sniffer Specific
For detailed information on filters, see section Filter Rules 1666 .
1660
Sniffer Specific
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.
1661
Setting Description
interval.
master node.
Setting Description

1662
Setting Description

ICMP, and SNMP.
from:
Other.
the Content column.
Sensor Display
Sensor Display
Setting Description
1663
Setting Description

Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
Inherited Settings
1664
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
1665
Toplists
Filter Rules
Port Any number

(OSPF), any number
1666
The following filter rules apply to Packet Sniffer sensors only.
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
1667
Channel Description
per second
in bytes per second
bytes per second

More
Knowledge Base


1668
7.8.120 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 1677 .

§ Dutch: Packet Sniffer (Aangepast)
1669
§ French: Reniflage de paquets personnalisé
§ German: Packet Sniffer (Benutzerdef.)
§ Japanese:
§ Portuguese: Sniffer de pacotes (customizado)
§ Russian: Ан ализато р п акето в (н естан дартн ы й)
§ Simplified Chinese: ( )
§ Spanish: Analizador de paquetes (personalizado)
Remarks
§ By default, this sensor works only on a probe device.
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.
Add Sensor

1670
Setting Description
inherited 146 .
§ bandwidthsensor
§ sniffersensor
Sniffer Specific
For detailed information on filters, see section Filter Rules 1676 .
1671
Sniffer Specific
Setting Description
1672
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
1673
Setting Description

Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
Inherited Settings
1674
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
1675
Toplists
Filter Rules
Port Any number

(OSPF), any number
1676
The following filter rules apply to Packet Sniffer sensors only.
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
1677
Channel Description
More
Knowledge Base


1678
7.8.121 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 1685 .

§ Dutch: Prestatie Meters Klantspecifiek
§ French: Windows PerfCounter personnalisé
§ German: Leistungsindikator (benutzerdef.)
§ Japanese:
§ Portuguese: PerfCounter (customizado)
§ Russian: Сп ециальн ы е н астро йки PerfCounter
§ Spanish: PerfCounter (personalizado)
Remarks
§ You cannot add different performance counters with the same name to one sensor.
1679
§ If a performance counter contains angle brackets (< or >), do not edit the channel settings because
this might cause an error.
§ See the Knowledge Base: How can I find out the names of available performance counters?
§ See the Knowledge Base: My performance counter sensor does not work. What can I do?
still work.
The user account has to be a member of the Performance Monitor
Users user group on the target system.
that a Windows Server 2008 R2 or later or later is installed on the probe
possible.
Add Sensor
Performance Counter Settings
1680
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 3047 . 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.
If a custom performance counter includes angle brackets (< or >), do
not edit the channel settings 3052 (for example, limits) after sensor
creation. This might lead to a malfunctioning sensor.
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 (recommended): 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.

Setting Description
1681
Setting Description
inherited 146 .
§ performancecounter
§ performancecountercustom
sensor settings.
Setting Description
Performance Counters Shows the performance counters that this sensor monitors.
1682
Setting Description
Value Display Mode Shows the mode in which the sensor displays the returning values.
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1683
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1684
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?


1685
7.8.122 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 1692 .

§ Dutch: PerfCounter IIS Application Pool
§ French: IIS Pool d'applications via Windows 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)
1686
Remarks
§ This sensor requires 1687 Microsoft Internet Information Services (IIS) version 7.5 or later on the target
system.
IIS version 7.5 or later To monitor IIS application pools, this sensor needs IIS version 7.5 or later
or later to be installed on the target system.
still work.
The user account has to be a member of the Performance Monitor
Users user group on the target system.
that a Windows Server 2008 R2 or later or later is installed on the probe
possible.
1687
Add Sensor
IIS Application Pool Specific
Setting Description
Application Pools Select the application pools that you want to monitor. PRTG creates one
sensor for each application pool that you select.
right corner.

Setting Description
1688
Setting Description
inherited 146 .
§ performancecounter
§ pciisapppool
Setting Description
Application Pools Shows the name of the application pool that this sensor monitors.
Sensor Display
Sensor Display
1689
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1690
Maintenance Window.
Access Rights
Access Rights

1691
Channel List
Channel Description
Application Pool State The overall status of the application pool

§ Up status 186 : Running, Unavailable for Total
§ Warning status: Initialized, Shutdown Pending
§ Down status: Delete Pending, Stopped, Stopping, Unavailable,

Uninitialized
Worker Process Failures The number of failures in worker processes per second
Worker Process Ping The number of failures in worker process pings per second
Failures
Worker Process The number of failures in worker process shutdowns per second
Shutdown Failures
Worker Process Startup The number of failures in worker process startups per second
Failures
Worker Processes The number of worker processes
More
Knowledge Base

1692
7.8.123 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 1698 .

§ Dutch: Ping
§ French: Ping
§ German: Ping
§ Japanese: Ping
§ Portuguese: Ping
§ Russian: П ин г
§ Simplified Chinese: Ping
§ Spanish: Ping
Remarks
1693
§ See the Knowledge Base: How to create/customize statistical Ping sensor?
§ See the Knowledge Base: Can I create an inverse Ping sensor?
Add Sensor

Setting Description
inherited 146 .
§ pingsensor
1694
Setting Description
sensor settings.
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.
1695
Setting Description
§ Send multiple Ping requests: 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 default.
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 186 . 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.
Acknowledge Define if you want to automatically acknowledge 206 the Down status of
Automatically the 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
1696
Setting Description


Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1697
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Maximum The maximum Ping time when using more than one Ping per interval
Minimum The minimum Ping time when using more than one Ping per interval
Packet Loss The packet loss in percent when using more than one Ping per interval
Ping Time The Ping time in milliseconds (msec)

1698
More
Knowledge Base
How to create/customize statistical Ping sensor?

Can I create an inverse Ping sensor?

1699
7.8.124 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 1705 .

§ Dutch: Ping Jitter
§ French: Gigue du Ping
§ German: Ping Jitter
§ Japanese: Ping
§ Portuguese: Jitter Ping
§ Russian: Дро жан ие п ин га
§ Simplified Chinese: Ping
§ Spanish: Jitter de Ping
Remarks
1700

does PRTG require?
Add Sensor

Setting Description
1701
Setting Description
inherited 146 .
§ ptfsensor
sensor settings.
Sensor Settings
Sensor Settings
Setting Description
Ping Count Define the number of ICMP Pings that the sensor sends. Enter an integer.
Debug Options
Debug Options
1702
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

1703
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1704
Access Rights
Access Rights
Channel List
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


1705
7.8.125 POP3 Sensor
The POP3 sensor monitors an email server via the Post Office Protocol version 3 (POP3).
POP3 Sensor
List 1712 .

§ Dutch: POP3
§ French: POP3
§ German: POP3
§ Japanese: POP3
§ Portuguese: POP3
§ Russian: POP3
§ Simplified Chinese: POP3
§ Spanish: POP3
Remarks
1706
Add Sensor

Setting Description
inherited 146 .
§ pop3sensor
§ mailsensor
1707
Setting Description
sensor settings.
POP3 Specific
POP3 Specific
Setting Description
Port Specify the port that the sensor uses for the POP3 connection. The
default port for unsecure connections is 110 and the default port for secure
Connection Security
Connection Security
1708
Setting Description

Authentication
Authentication
1709
Setting Description
POP3 Authentication Select the authentication method for the POP3 connection:
Method
§ 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-
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
1710
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1711
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description

More
Knowledge Base

1712
7.8.126 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 1720 .

§ Dutch: Poort
§ French: Port
§ German: Port
§ Japanese:
§ Portuguese: Porta
§ Russian: П о рт
§ Spanish: Puerto
Remarks
1713
Add Sensor

Setting Description
inherited 146 .
§ portsensor
1714
Setting Description
sensor settings.
Port Specific
Port Specific
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:

§ Do not use transport-level security (default): Establish the connection
without connection security.
1715
Setting Description

Secure Sockets Layer (SSL)/Transport Layer Security (TLS) method
that the target device provides.
Advanced Sensor Settings
Advanced Sensor Settings
Setting Description
Goal Define how the sensor reports on the port:

§ Open: Show the Up status 186 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: 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.
1716
Setting Description
Response Define if the sensor further processes the response:

§ Ignore response: 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. Check
(positive) if the response contains a specific keyword. If the response does not
contain the keyword, the sensor shows the Down status.
§ Disable: Do not check for positive keywords.
§ Enable keyword check (positive): Check if a specific keyword exists in

the received value. Define the keyword below.
Response Must Include This setting is only visible if you select Enable keyword check (positive)
(Down Status if Not above. Define the search string that the response must contain. You can
Included) enter a simple string in plain text or a regular expression (regex) 3552 .
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 above. Check
(negative) if the response does not contain a specific keyword. If the response does
contain the keyword, the sensor shows the Down status.
§ Disable: Do not check for negative keywords.
1717
Setting Description
§ Enable keyword check (negative): Check if a specific keyword does not

exist in the received value. Define the keyword below.
Response Must Not This setting is only visible if you select Enable keyword check (negative)
Include (Down Status if above. Define the search string that the response must not contain. You
Included) 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.


scanning interval.
master node.
Sensor Display
Sensor Display
1718
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1719
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Available The time until a request to a port is accepted in milliseconds (msec)

More
Knowledge Base

1720
7.8.127 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 3052 . This way, you can get alerts about open
and closed ports.
Port Range Sensor
List 1726 .

§ Dutch: Poortbereik
§ French: Plage de port
§ German: Portbereich
§ Japanese:
§ Portuguese: Intervalo de portas
§ Russian: Диап азо н п о рто в
§ Spanish: Rango de puerto
1721
Remarks
Add Sensor

Setting Description
inherited 146 .
1722
Setting Description
§ portrangesensor
sensor settings.
Port Range Specific
Port Range Specific
Setting Description
1723
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. 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:
§ Ignore changes: No action is taken if there is a change.
§ Trigger 'change' notification: The sensor sends an internal message

indicating that its value has changed. In combination with a change
whenever the sensor value changes.
Sensor Display
Sensor Display
Setting Description
1724
Setting Description


Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1725
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Available The time until requests to ports are accepted in milliseconds (msec)
Closed Ports The number of closed ports
Open Ports The number of open ports
More
Knowledge Base
1726
1727
7.8.128 PostgreSQL Sensor
The PostgreSQL sensor monitors a database on a PostgreSQL server and executes a query.
channels.
PostgreSQL Sensor
List 1741 .

§ Dutch: PostgreSQL
§ French: PostgreSQL
§ German: PostgreSQL
§ Japanese: PostgreSQL
§ Portuguese: PostgreSQL
§ Russian: PostgreSQL
§ Simplified Chinese: PostgreSQL
§ Spanish: PostgreSQL
Remarks
1728
§ Save the SQL script with the query in the \Custom Sensors\sql\postgresql subfolder of the PRTG
program directory 3579 .
§ This sensor supports PostgreSQL 7.x or later.
depending on it?
does PRTG require?
Add Sensor
Data
Setting Description
cluster nodes.
1729
Setting Description


edited).
the data table.
1730
Setting Description
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
Sensors 3501 .

1731
Setting Description
inherited 146 .
§ sqlsensor
1732
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.
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 details about the PostgreSQL SSL modes, refer to the
PostgreSQL documentation.
Data
Sensor Display
1733
Setting Description
using variables.
into the query.
content:

as the number 0.
1734
Setting Description
Number.
Databases 3387 .
is disabled.
1735
Setting Description
value:
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
1736
Setting Description

integer.
point.
1737
Setting Description

master node.
Sensor Display
Sensor Display
Setting Description
1738
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1739
Maintenance Window.
Access Rights
Access Rights

1740
Channel List
Channel Description
(msec)
More
Knowledge Base


1741
7.8.129 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.
Probe Health Sensor
List 1746 .

§ Dutch: Probe Status
§ French: État de la sonde
§ German: Zustand der Probe
§ Japanese:
§ Portuguese: Funcionamento da sonda
1742
§ Russian: Рабо то сп о со бн о сть зо н да
§ Spanish: Salud de sonda
Remarks
device.
§ See the Knowledge Base: My probe system is running out of disk space. What can I do?

Setting Description
inherited 146 .
1743
Setting Description
§ probehealthsensor
sensor settings.
Sensor Display
Sensor Display
Setting Description

1744
Inherited Settings
Scanning Interval
Scanning Interval
Access Rights
Access Rights

1745
Channel List
Channel Description
CPU Load The CPU load in percent that the probe process causes. Extensive CPU
load can lead to false, incomplete, and incorrect monitoring results. This
value should usually stay below 50%.
Health The sum of the probe state as a value between 100% (healthy) and 0%
Interval Delay non- The interval delay in percent for all sensors that are not of the type Simple
WMI&SNMP Network Management Protocol (SNMP) or Windows Management
Instrumentation (WMI). If this value is above 0%, try to increase the
scanning intervals 418 or distribute your sensors among probes 3557 .
1746
Channel Description
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).
Lost Flow Packets The number of lost Flow (NetFlow, jFlow, sFlow, IPFIX) 3367 packets in
percent. 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 3557 .
Message Queue The number of monitoring results that have not been processed by the
core 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.
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
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 3077 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.
Trap Buffer The number of buffered SNMP traps. Usually, this value should be 0 (or
very low). Investigate increasing values.
1747
More
Knowledge Base
My probe system is running out of disk space. What can I do?

1748
7.8.130 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 1756 .

§ 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
§ You must store the script file on the probe system. In a cluster, copy the file to every cluster node.
1749
§ 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 prtg Python package.
§ Print commands in the Python script are not supported and lead to an invalid JSON result.
§ Exceptions in the script are not supported.
§ Channel values greater than 2^62 are not supported.
§ The timeout of the sensor is its scanning interval 1755 minus 1 second. Make sure that your Python
script does not run longer than this.
§ For best sensor usage, we recommend that the return value is JSON encoded.
the probe computer?
§ See the Knowledge Base: After updating to PRTG 20.1.55, my Python Script Advanced sensors are
down
Add Sensor
Sensor Settings
Setting Description
Script Select a Python script from the list. The sensor executes it with every
scanning interval 1755 .
This list shows all Python script files that are available in the \Custom
Sensors\python subfolder of the PRTG program directory 3579 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.
1750
Setting Description
inherited 146 .
§ pythonxml
§ python
§ xml
§ json
§ script
1751
sensor settings.
Sensor Settings
Sensor Settings
Setting Description
Script Shows the Python script file that the sensor executes with each scanning
interval.
Security Context Define the Windows user account that the sensor uses to run the Python
interpreter:
§ Use security context of PRTG probe service: Run the Python script file
under the same Windows user account that the probe runs under. By
default, this is the Windows system user account.
account from the settings of the parent device 535 .
Device Credentials Define if you want to transmit device credentials to the Python script.
PRTG adds the device credentials to the JSON object that is passed to
the script as a command-line parameter. Choose between:
§ Do not transmit device credentials: Transmit no device credentials to the
script.
§ Transmit Windows credentials: Transmit Windows credentials 542 to the
script.
§ Transmit Linux credentials: Transmit Linux credentials 543 to the script.
1752
Setting Description
§ Transmit SNMP credentials: Transmit SNMP credentials 548 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.
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.
sensor settings?
Debug Options
Debug Options
1753
Setting Description
scanning interval.
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. This does not apply for PRTG Hosted
Monitor.
PRTG masks transmitted passwords in the logfile.
master node.
Sensor Display
Sensor Display
Setting Description

1754
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1755
Access Rights
Access Rights

Channel List
Channel Description
1756
Channel Description
[Value] The values that the Python script returns in several channels
Sensors 3499 .
More
Knowledge Base

After updating to PRTG 20.1.55, my Python Script Advanced sensors are down

1757
7.8.131 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 1764 .

§ 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
1758
§ Portuguese: Unidirecional QoS (qualidade de serviço)
§ Russian: О дн о сто ро н н ее качество о бслуживан ия
§ Simplified Chinese: QoS ( )

§ Spanish: Unidireccional QoS (calidad de servicio)
Remarks
§ You must configure at least one remote probe 3555 in your PRTG Network Monitor setup for this sensor
to work, and at least two remote probes in PRTG Hosted Monitor.

§ You can create this sensor on the probe device of a local probe or a remote probe.
Add Sensor

Setting Description
1759
Setting Description
inherited 146 .
§ qossensor
sensor settings.
Quality of Service Measurement
Setting Description
1760
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 3555 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 ensure 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.

If you do not use NAT rules, this is usually the IP address in
parentheses next to the probe name under 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.
Use a different port for each QoS (Quality of Service) One Way
sensor to make sure that packets can be assigned 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
1761
Setting Description
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

1762
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
1763
Channel List
Channel Description
Jitter Average The average jitter in milliseconds (ms)
Jitter Max The maximum jitter in ms

Jitter Min The minimum jitter in ms
Packet Delay Variation The average packet delay variation in ms

Average
Packet Delay Variation The maximum packet delay variation in ms

Max
Packet Delay Variation The minimum packet delay variation in ms

Min
Packets Corrupted The corrupted packets in percent
Packets Duplicated The duplicated packets in percent
Packets Lost The lost packets in percent
Packets Out Of Order The out of order packets in percent
Time To Last Packet The time to the last packet in msec
More
Knowledge Base

1764
PAESSLER WEBSITE

1765
7.8.132 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 1772 .

§ Dutch: QoS (Quality of Service) Heen en weer
§ French: Quality of Service (QoS) aller-retour
§ German: QoS (Quality of Service) Round Trip
§ Japanese: QoS Quality of Service
1766
§ Portuguese: Ida e volta QoS (qualidade de serviço)
§ Russian: Цикл тестиро ван ия качества о бслуживан ия
§ Simplified Chinese: QoS ( )

§ Spanish: Ida y vuelta QoS (calidad de servicio)
Remarks
§ You must configure at least one remote probe 3555 in your PRTG Network Monitor setup and at least
two remote probes in PRTG Hosted Monitor, or you need to set up the PRTG QoS Reflector tool on
the target machine at the endpoint of the connection that you want to monitor.
§ See the Knowledge Base: How can I monitor QoS round trips without using remote probes?
§ See the Knowledge Base: How does PRTG calculate the MOS score for QoS sensors?
§ See the Knowledge Base: What connection settings are necessary for the QoS (Quality of Service)
Round Trip sensor?
Add Sensor

1767
Setting Description
inherited 146 .
§ qossensor
1768
Setting Description
QoS Target Define the type of target that receives the UDP packets:
§ PRTG probe (recommended): 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 PRTG probe (recommended)
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 3555 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 ensure 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
details, 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.
If you do not use NAT rules, this is usually the IP address in
parentheses next to the probe name under Target Probe.
1769
Setting Description
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 packets can be assigned 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
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
1770
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1771
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Jitter Average The average jitter in in milliseconds (msec)
Jitter Max The maximum jitter in msec

Jitter Min The minimum jitter in msec
MOS The mean opinion score (MOS)
1772
Channel Description
Packet Delay Variation The average packet delay variation in msec

Average
Packet Delay Variation The maximum packet delay variation in msec

Max
Packet Delay Variation The minimum packet delay variation in msec

Min
Packets Corrupted The corrupted packets in percent
Packets Duplicated The duplicated packets in percent
Packets Lost The lost packets in percent
Packets Out Of Order The out of order packets in percent
RTT (Average) The average round-trip time (RTT) in msec
RTT (Maximum) The maximum RTT in msec
RTT (Minimum) The minimum RTT in msec
More
Knowledge Base
How can I monitor QoS round trips without using remote probes?
How does PRTG calculate the MOS score for QoS sensors?
What connection settings are necessary for the QoS (Quality of Service) Round Trip sensor?

PAESSLER WEBSITE

1773
1774
7.8.133 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 186 .
RADIUS v2 Sensor
List 1781 .

§ 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
1775
§ This sensor only supports plain text authentication (Password Authentication Protocol (PAP)).
does PRTG require?
Add Sensor

Setting Description
1776
Setting Description
inherited 146 .
§ radiussensor
sensor settings.
1777
RADIUS Specific
RADIUS Specific
1778
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: 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 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.
1779
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1780
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
1781
Channel Description
RADIUS Code The RADIUS code
§ Up status 186 : Accept-Accept

§ Warning status: Access-Challenge
§ Down status: Access-Reject
More
Knowledge Base


1782
7.8.134 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 1791 .

§ Dutch: Redfish Power Supply
§ French: Redfish Power Supply
§ German: Redfish Power Supply
§ Japanese: Redfish Power Supply
§ Portuguese: Redfish Power Supply
§ Russian: Redfish Power Supply
§ Simplified Chinese: Redfish Power Supply
§ Spanish: Redfish Power Supply
1783
Remarks
§ This sensor requires credentials for Redfish in settings that are higher in the object hierarchy
566 140 ,
§ Supporters of the Redfish standard are Broadcom, Dell, Emerson, HPE, Intel, Lenovo, Microsoft,
Supermicro, and VMware.
Add Sensor
Redfish Specific
Setting Description
Name Select the power supplies that you want to monitor. PRTG creates one
sensor for each power supply that you select.
right corner.

1784
Setting Description
inherited 146 .
§ redfish
§ powersupply
1785
Redfish Specific
Redfish Specific
The information in the Redfish Specific settings reflect 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 Setting
Name Shows the name of the power supply that this sensor monitors.
Model Shows the model of the power supply that this sensor monitors.
Manufacturer Shows the manufacturer of the power supply that this sensor monitors.
Serial Number Shows the serial number of the power supply that this sensor monitors.
Sensor Display
Sensor Display
1786
Setting Setting

Debug Options
Debug Options
Setting Description
scanning interval.
master node.
1787
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Setting Description
§ None
§ Saturdays
§ Sundays
§ Weekdays
1788
Setting Description
§ Weekends

below.
past.
can choose from:

1789
Setting Description
object will depend.
an integer.
Access Rights
Access Rights

1790
Channel List
Channel Description
Input Voltage The input voltage in volts (V)
Input Watts The input watts in watts (W)
Output Load The output load in percent (%)
Output Watts The output watts in watts (W)
Power Efficiency The power efficiency in percent (%)
Power Supply Status The status of the power supply

§ Up status: OK
§ Down status: Critical
§ Unknown status: Offline / Absent
1791
Channel Description
More
Knowledge Base
I want to know which of my systems support the PRTG Redfish sensors. Can you help me?

1792
7.8.135 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 1801 .

§ Dutch: Redfish System Health
§ French: Redfish System Health
§ German: Redfish System Health
§ Japanese: Redfish System Health
§ Portuguese: Redfish System Health
§ Russian: Redfish System Health
§ Simplified Chinese: Redfish System Health
1793
§ Spanish: Redfish System Health
Remarks
566 140 ,
Add Sensor
Redfish Specific
Setting Description
Name Select the system that you want to monitor. PRTG creates one sensor for
each system that you select.
right corner.

1794
Setting Description
inherited 146 .
§ redfish
§ restsensor
1795
Redfish Specific
Redfish Specific
Setting Setting
Name Shows the name of the system that this sensor monitors.
Model Shows the model of the system that this sensor monitors.
Manufacturer Shows the manufacturer of the system that this sensor monitors.
Serial Number Shows the serial number of the system that this sensor monitors.
Asset Tag Shows the asset tag of the system that this sensor monitors.
1796
Sensor Display
Sensor Display
Setting Setting

Debug Options
Debug Options
Setting Description
1797
Setting Description
scanning interval.
master node.
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1798
Setting Description
§ None
§ Saturdays
§ Sundays
§ Weekdays
§ Weekends

below.
past.
1799
Setting Description
can choose from:

object will depend.
an integer.
1800
Access Rights
Access Rights

Channel List
Channel Description
Chassis Status The status of the chassis

§ Up status: OK
1801
Channel Description
Drives Status The status of the drives

§ Up status: OK
Fans Status The status of the fans

§ Up status: OK
Memory Status The status of the memory

§ Up status: OK
PCIe Devices Status The status of the PCIe drives

§ Up status: OK
Power Supplies Status The status of the power supplies

§ Up status: Off, On, Powering Off, Powering On
Processor Status The status of the processor
1802
Channel Description
§ Up status: OK
System Power Status The status of the system power

§ Up status: OK
System Status The status of the system

§ Up status: OK
Thermal Status The thermal status

§ Up status: OK
More
Knowledge Base

1803
7.8.136 Redfish Virtual Disk Sensor (BETA)
The Redfish Virtual Disk sensor monitors the virtual disk of a Redfish Scalable Platforms Management
API (Redfish)-capable server.
Redfish Virtual Disk Sensor
List 1811 .

§ Dutch: Redfish Virtual Disk
§ French: Redfish Virtual Disk
§ German: Redfish Virtual Disk
§ Japanese: Redfish Virtual Disk
§ Portuguese: Redfish Virtual Disk
§ Russian: Redfish Virtual Disk
§ Simplified Chinese: Redfish Virtual Disk
1804
§ Spanish: Redfish Virtual Disk
Remarks
566 140 ,
§ See the Knowledge Base: I want to know which of my systems support the PRTG Redfish sensors.
Can you help me?
Add Sensor
Redfish Specific
Setting Description
Virtual Disk Name Select the virtual disk that you want to monitor. PRTG creates one sensor
for each virtual disk that you select.
1805
Setting Description

right corner.

Setting Description
inherited 146 .
§ logicaldisk
§ redfish
1806
Setting Description
§ virtualdisk
§ virtualvolume
Redfish Specific
Redfish Specific
Setting Setting
Virtual Disk Name Shows the name of the virtual disk that this sensor monitors.
Capacity Shows the capacity of the virtual disk that this sensor monitors.
Raid Level Shows the raid level of the virtual disk that this sensor monitors.
Physical Disks Count Shows the number of physical disks connected to the virtual disk that this
sensor monitors.
1807
Setting Setting
System Name Shows the name of the system that the virtual disk belongs to.
Sensor Display
Sensor Display
Setting Setting

1808
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Inherited Settings
Scanning Interval
Scanning Interval
1809
objects' settings.
Maintenance Window.
Access Rights
Access Rights

1810
Channel List
Channel Description
Capacity The capacity of the virtual disk in GB
Physical Disks "Critical" Physical disks in critical status
Physical Disks "Offline" Physical disks in offline status
Physical Disks "OK" Physical disks in OK status
Physical Disks Physical disks in warning status

"Warning"
Virtual Disk Status The status of the virtual disk

§ Up status: OK
1811
Channel Description
More
Knowledge Base


1812
7.8.137 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 1817 .

§ 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
1813
Add Sensor

Setting Description
inherited 146 .
§ rdpsensor
1814
sensor settings.
Sensor Specific
Sensor Specific
Setting Description
integer. The default value is 3389.
Sensor Display
Sensor Display
Setting Description
1815
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1816
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description

More
Knowledge Base

1817
1818
7.8.138 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 1840 .

§ Dutch: REST Aangepast
§ French: REST personnalisé
§ German: REST (Benutzerdef.)
§ Japanese: REST
§ Portuguese: REST (customizado)
1819
§ Russian: Сп ециальн ы е н астро йки REST
§ Simplified Chinese: REST
§ Spanish: REST (personalizado)
Remarks
§ You must store the REST configuration file that contains the mapping rules on the probe system. In a
display all channels. Be aware, however, that you experience limited usability and performance. If you
have more than 50 channel mappings in your REST configuration file, the sensor shows an error.
§ In a cluster, status changes triggered by limits only work on the master node.
Add Sensor
REST Specific
Setting Description
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 3579 on the
probe system. For the files to appear in this list, store the files as JSON
template (*.template) in this subfolder.
To use custom REST configurations in PRTG Hosted Monitor,
contact the Paessler support team 3330 , 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 details, see
section Define Channels and Select Channel Values 1828 .
1820
Setting Description
every cluster node.

Setting Description
inherited 146 .
1821
Setting Description
§ restcustomsensor
§ restsensor
sensor settings.
REST Specific
REST Specific
1822
Setting Description
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).
§ 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.
a user name for the REST API. Enter a string.
1823
Setting Description
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. 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.
Make sure that the HTTP header statement is valid. Otherwise, the
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 Shows 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=sensorxr
ef&noraw=1&filter_basetype=probe&columns=totalsens=textraw
1824
Setting Description
REST Configuration Shows the REST configuration file that the sensor uses to map the
returned JSON or XML into sensor values.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
1825
Setting Description

Inherited Settings

1826
Sensors.
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1827
Access Rights
Access Rights

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.
§ A channel is defined by the channel key in your REST configuration. See the JSON Return Format:
Minimum Example in section Custom Sensors 3499 .
§ A channel value is defined by an expression that retrieves and processes the value from the JSON
source. The expression can contain JSONPath 1830 , gval operators 1834 , and functions 1836 .
Example
1828
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 3579 on the
probe system. See section Custom Sensors 3499 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.
1829
{
"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 1838 using the command line.
To test simple JSONPath expressions and calculations, you can also use JSONPath Online
Evaluator 1840 , 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.
1830
{
"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.
Child You can match a child with .<key> or [<key>]
1831
§ .<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.
§ The default approach is to go step by step from the first array element
to the last element.
1832
§ 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.
Constant § Numeric constants as 64-bit floating point: 12345.678
§ String constants with double quotes: "switch"
1833
§ 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 details, refer to the gval documentation 1840 .
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
<< shift left number number
>> shift right number number
1834
REST Custom Sensor: Operators
Logical Infix > greater than number/string bool

Operators
>= equal or greater number/string bool

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
! not bool bool
1835
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
sum([1,2,3])
This expression returns 6.
mean(array-/object-of- § Returns the average value of an array of numbers.

numbers)
Example
1836
REST Custom Sensor: Functions
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.
1837
{
"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 3579 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
template § Fully qualified path and file name of your REST configuration file used to
map the JSON result to the sensor
1838
rest.exe: Parameters
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
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'
1839
rest.exe: Flags
-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

Sensors 3499 .
More
PRTG MANUAL
§ Data Storage 3579
Knowledge Base

Can I create a sensor to monitor the number of paused or unknown sensors?

1840
MISCELLANEOUS
Paessler JSONPath
§ https://github.com/PaesslerAG/jsonpath
Paessler Gval
§ https://github.com/PaesslerAG/gval
JSONPath Online Evaluator

§ https://jsonpath.com/
1841
7.8.139 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.
REST Custom v2 Sensor
List 1855 .

§ Dutch: REST Custom v2
§ French: REST Custom v2
§ German: REST Custom v2
§ Japanese: REST Custom v2
§ Portuguese: REST Custom v2
§ Russian: REST Custom v2
§ Simplified Chinese: REST Custom v2
§ Spanish: REST Custom v2
Remarks
1842
§ In a cluster, status changes triggered by limits only work on the master node.
§ You can define credentials for REST API 567 in settings that are higher in the object hierarchy 140 , for
Add Sensor
Channel Settings
Setting Description
Channel #x Enter the JSONPath or XPath that you want to monitor.

JSONPath/XPath
JSONPath example:
$.sensorxref[0].totalsens
If the JSONPath points to a boolean, the sensor translates TRUE as

1 and FALSE as 0.
XPath example:
1843
Setting Description
/bookstore/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 Custom Unit Enter the unit for the value that this sensor monitors. For example, #.
Channel #x 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.

between the last and the current value. Enter an integer. PRTG
additionally divides the delta value by a time period to indicate a speed
value.

Setting Description
1844
Setting Description
inherited 146 .
§ rest
sensor settings.
REST Specific
REST Specific
1845
Setting Description
Request URL Enter the URL of the JSON or XML REST API endpoint that you want to
request.
JSON REST API endpoint URL example:
https://mycompany.com/api/table.json?
id=1&passhash=<passhash>&username=<username>&content=sensorxr
ef&
noraw=1&filter_basetype=probe&columns=totalsens=textraw,upsen
s=textraw,
downsens=textraw,partialdownsens=textraw,warnsens=textraw,pau
sedsens=textraw,
unusualsens=textraw,undefinedsens=textraw,downacksens=textraw
XML REST API endpoint URL example:

https://mycompany.com/api/table.xml?sortby=year
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.
POST Body This setting is only visible if you select POST above. Enter the data part
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.
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
1846
Setting Description
Content Type Select the type of the content that the sensor queries. Choose between:
§ 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.
JSONPath example:
$..prtg-version
XPath example:
/bookstore/book[1]/title
Channel Settings
Channel Settings
Setting Description
Channel #x Enter the JSONPath or XPath that you want to monitor.

JSONPath/XPath
JSONPath example:
$.sensorxref[0].totalsens
If the JSONPath points to a boolean, the sensor translates TRUE as

1 and FALSE as 0.
1847
Setting Description
XPath example:
/bookstore/book[1]/year
Channel #x Type Shows the value type that the channel displays.
Channel #2 - #10 Shows if the channel is enabled or disabled.

Sensor Display
Sensor Display
Setting Description

1848
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Inherited Settings
Scanning Interval
Scanning Interval
1849
objects' settings.
Maintenance Window.
Access Rights
Access Rights

1850
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 1855 , 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.
1851
{
"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 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>]
1852
§ .<key> must only contain letters, numbers, and underscore (_).

Hyphens (-) are not supported.
§ [<key>] must only contain a number or a quoted string.
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)"]
Wildcard To match multiple values, you can use the asterisk symbol (*).
§ .*
§ [*]
Example

$.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.
§ The default approach is to go step by step from the first array element
to the last element.
1853
§ 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.
Constant § Numeric constants as 64-bit floating point: 12345.678
§ String constants with double quotes: "switch"
1854
§ 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>
For more information about JSONPath, see JsonCons JSONPath.
REST Custom v2 Sensor: XPath

For more information about XPath, see XPath Syntax.
Channel List
Channel Description
HTTP Status The HTTP status that the requested URL returns
[Value] The values that a REST API returns in several channels

Sensors 3499 .
More
PRTG MANUAL
§ Data Storage 3579
Knowledge Base
1855

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/
1856
7.8.140 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 sensor 672 instead.
Sensor Factory Sensor
List 1869 .

§ Dutch: Sensor Fabriek
§ French: Capteur combiné
§ German: Formelsensor
§ Japanese:
§ Portuguese: Sensor de fórmula
§ Russian: Фабрика сен со ро в
§ Spanish: Sensor combinado
1857
Remarks
§ 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 Sensor Factory sensors per PRTG core server.
§ This sensor does not support channel definitions 1862 that refer to channels of Sensor Factory sensors.
§ Make sure that the scanning interval of this sensor is equal to or greater than the scanning interval
1862
of the source sensors to avoid incorrect sensor behavior. For example, "no data" messages or erratic
changes of the sensor status can be a result of an invalid scanning interval.
§ The Sensor Factory sensor might not work with Flow sensors 3367 . Sensors that use active flow
timeout, for example NetFlow and jFlow sensors 3626 , are not supported by the Sensor Factory sensor.
§ Uptime or downtime data for this sensor is not available in reports 189 .
§ See the Knowledge Base: How can I monitor the overall status of the business process "email"?
Add Sensor

Setting Description
1858
Setting Description
inherited 146 .
§ factorysensor
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 1862 .
1859
Setting Description
Status Handling Define the behavior of the Sensor Factory sensor if one of the source
sensors is in the Down status 186 . In this case, you can set the Sensor
Factory sensor either to the Down status or to the Warning status.
Choose from:
§ Show down status when one or more source sensors are in 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 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 3541 or an error limit 3053 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 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. 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 1868 .
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: 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.
1860
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1861
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
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.
1862
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.
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 are:
§ <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() 1863 , min() 1865 , max() 1865 , avg() 1865 , or percent() 1865 .
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>)
The parameters are:
§ <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 3053 .
1863
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.
§ 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 1865 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.
1864
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() 1863 functions.
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() 1863 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>)
The parameters are:
§ <source> is the value the percent is calculated for. This is usually a channel() 1863 function.
§ <maximum> is the limit value used for the percent calculation.
1865
§ <unit> is an optional unit the maximum is provided in. You can use constants with this function (see
Define Channels: Constants 1867 below for a list). This can be used for absolute values (for example,
Ping sensors 1693 ) 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
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>
The parameters are:
§ <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.
1866
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
1867
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 1858 . 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)
The parameters are:
§ <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
1868
§ 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 1862 . 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 137 , 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.
1869
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 a 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
1870
7.8.141 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 1881 .
1871
§ Dutch: sFlow
§ French: sFlow
§ German: sFlow
§ Japanese: sFlow
§ Portuguese: sFlow
§ Russian: sFlow
§ Simplified Chinese: sFlow
§ Spanish: sFlow
Remarks
§ You must enable sFlow v5 export on the target device for this sensor to work. The device must send
the flow data stream to the IP address of the probe system with this sensor (either a local probe or a
remote probe).
§ This sensor accepts RAW data only. The stream must be sent via IPv4.
§ This sensor has several limitations 1872 .
Sniffer sensors?
§ See the Knowledge Base: Where is the volume line in graphs?
§ See the Paessler tools: Paessler sFlow Tester
Limitations
There are some limitations that you should consider before you use this sensor:
§ The sensor only supports sFlow v5 datagrams.
§ The sensor only supports IPv4 flows.
§ The sensor only supports the "raw packet header" format.
1872
§ The sensor only supports the "Flow sample" and "Extended flow" formats. It cannot process "Counter"
formats.
§ The sensor only processes samples where the source ID matches the ifIndex of the input interface
(avoiding double-counted traffic) and ascending sequence numbers.
§ The sensor only supports sample packets of the Ethernet type "IP" (with optional VLAN tag)
§ The sensor only supports sampled packets of the types TCP and UDP.
We recommend that you use sFlow Tester for debugging.
Add Sensor

Setting Description
inherited 146 .
1873
Setting Description
§ bandwidthsensor
§ sflowsensor
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 value is 6343. Enter an integer.
sFlow from. Enter an IP address to only receive data from a specific
specified port.
1874
Setting Description
Receive Packets on IP Select the IP addresses on which PRTG listens to sFlow packets. The list
must match the IP address in the sFlow export options of the hardware
router device.
appropriate sFlow v5 for this sensor
packet data.
interval.
1875
Setting Description

ICMP, and SNMP.
from:
Other.
the Content column.
Filtering
1876
Filtering
Setting Description
Sensor Display
Sensor Display
Setting Description
1877
Setting Description

Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
Inherited Settings
1878
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
1879
Toplists
Filter Rules
Port Any number

(OSPF), any number
1880
The following filter rules apply to sFlow sensors only.
Channel List
Channel Description
1881
Channel Description
per second
in bytes per second
bytes per second

More
Knowledge Base


PAESSLER TOOLS
sFlow Tester
1882
§ https://www.paessler.com/tools/sflowtester
1883
7.8.142 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 1893 .
1884
§ Dutch: sFlow (Custom)
§ French: sFlow personnalisé
§ German: sFlow (Benutzerdef.)
§ Japanese: sFlow
§ Portuguese: sFlow (customizado)
§ Russian: sFlow (н естан дартн ы й)
§ Simplified Chinese: sFlow ( )

§ Spanish: sFlow (personalizado)
Remarks
§ You must enable sFlow v5 export on the target device for this sensor to work. The device must send
the flow data stream to the IP address of the probe system with this sensor (either a local probe or a
remote probe).
§ This sensor has several limitations 1885 .
§ This sensor accepts RAW data.
§ See the Paessler tools: Paessler sFlow Tester
Limitations
There are some limitations that you should consider before you use this sensor:
§ The sensor only supports sFlow v5 datagrams.
§ The sensor only supports IPv4 flows.
§ The sensor only supports the "raw packet header" format.
§ The sensor only supports the "Flow sample" and "Extended flow" formats. It cannot process "Counter"
formats.
§ The sensor only processes samples where the source ID matches the ifIndex of the input interface
(avoiding double-counted traffic) and ascending sequence numbers.
1885
§ The sensor only supports sample packets of the Ethernet type "IP" (with optional VLAN tag)
§ The sensor only supports sampled packets of the types TCP and UDP.
We recommend that you use sFlow Tester for debugging.
Add Sensor

Setting Description
inherited 146 .
1886
Setting Description
§ bandwidthsensor
§ sflowsensor
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 value is 6343. Enter an integer.
sFlow from. Enter an IP address to only receive data from a specific
specified port.
1887
Setting Description
Receive Packets on IP Select the IP addresses on which PRTG listens to sFlow packets. The list
must match the IP address in the sFlow export options of the hardware
router device.
packet data.
interval.
Filtering
1888
Filtering
Setting Description
Sensor Display
Sensor Display
Setting Description
1889
Setting Description

Primary Toplist
Primary Toplist
Setting Description
§ Top Talkers
§ Top Connections
§ Top Protocols
object.
Inherited Settings
1890
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
1891
Toplists
Filter Rules
Port Any number

(OSPF), any number
1892
The following filter rules apply to sFlow sensors only.
Channel List
Channel Description
1893
Channel Description
More
Knowledge Base


PAESSLER TOOLS
sFlow Tester
§ https://www.paessler.com/tools/sflowtester
1894
7.8.143 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 1901 .

§ 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
§ This sensor requires credentials for Linux/Solaris/macOS (SSH/WBEM) systems 543 in the settings of
the parent device.
§ This sensor cannot support all Linux/Unix and macOS distributions.
1895
§ See the Knowledge Base: SSH and SFTP sensors in Unknown status
Add Sensor

Setting Description
inherited 146 .
§ sftpsensor
1896
Setting Description
sensor settings.
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).
Ensure 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.
Ensure that the shell timeout is a value that is lower than the
connection timeout to avoid potential errors.
1897
Setting Description
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 543 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.
Enter the port number (between 1 and 65535) that this sensor uses for the
SSH connection. Enter an integer.
SSH Engine Select the method that you want to use to access data with this SSH
sensor 3363 . We strongly recommend that you use the default engine. You
can still use the legacy mode for some time to ensure compatibility with
your target systems. Choose between:
§ Inherit from parent device (default): Use the SSH engine that you defined
in the parent device settings or higher up in the object hierarchy 140 . If
you have not changed the SSH engine, this is the recommended default
engine.
§ Default: This is the default monitoring method for SSH sensors. 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): Try this legacy method only if the
default mode 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 running with 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.
1898
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1899
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1900
Channel List
Channel Description

More
Knowledge Base
SSH and SFTP sensors in Unknown status


1901
7.8.144 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 1907 .

§ 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
§ 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.
1902
PE032
Add Sensor

Setting Description
1903
Setting Description
inherited 146 .
§ diskspacesensor
§ smbdiskspacesensor
sensor settings.
Share Configuration
Share Configuration
Setting Description
Share Enter the name of the share that you want to monitor.
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.
1904
Setting Description
To provide any shares under Windows, the LanmanServer service

must run on the target computer.
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1905
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1906
Channel List
Channel Description

More
Knowledge Base

1907
7.8.145 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 1914 .

§ 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
§ An SIP server might return the error '480 Service temporarily unavailable' until at least one reachable
SIP client is connected to the server.
1908
does PRTG require?
Add Sensor

Setting Description
1909
Setting Description
inherited 146 .
§ pingsensor
§ sipsensor
SIP Specific
SIP Specific
1910
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 186 . Enter an integer.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
1911
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1912
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

1913
Channel List
Channel Description
Response Code The response code

You can individually define the status for each individual response
code by editing the lookup 3541 file
prtg.standardlookups.sip.statuscode.
More
Knowledge Base

1914
1915
7.8.146 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 1923 .

§ Dutch: SMTP
§ French: SMTP
§ German: SMTP
§ Japanese: SMTP
§ Portuguese: SMTP
§ Russian: SMTP
§ Simplified Chinese: SMTP
§ Spanish: SMTP
Remarks
1916
Add Sensor

Setting Description
inherited 146 .
§ smtpsensor
§ mailsensor
1917
Setting Description
sensor settings.
SMTP Specific
SMTP Specific
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
1918
Setting Description
SMTP Authentication Define if you want to use authentication for the SMTP connection:
Method
§ None: 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.
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
1919
Setting Description

Monitoring
Monitoring
Setting Description
Email Handling Define the monitoring approach when connecting to the SMTP server:
§ Do not send an email: 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 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 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.
Topic This setting is only visible if you select Send email above. Specify the
subject that the email contains. Enter a string or leave the field empty.
1920
Setting Description
Content This setting is only visible if you select Send email above. Specify the
body that the email contains. Enter a string or leave the field empty.
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

1921
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
1922
Access Rights
Access Rights
Channel List
Channel Description

More
Knowledge Base

1923
7.8.147 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 1933 .

§ 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
1924
Remarks
§ The parent device must be an SMTP server.
§ Use dedicated email accounts with this sensor. If you use more sensors of this type, make sure that
each sensor uses its own email accounts.
Add Sensor

Setting Description
inherited 146 .
1925
Setting Description
§ imapsensor
§ roundtrip
§ mailsensor
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.
1926
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).
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
1927
Setting Description
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
Setting Description
1928
Step 2: Check an IMAP Mailbox until Email Arrives
In this step, you configure how to receive the emails that the sensor sends.
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 default
port for unsecure connections is 143 and the default port for secure
to.. Enter an integer.
Connection Interval (Sec.) Enter the number of seconds the sensor waits between two connections
to the IMAP server. PRTG repeatedly checks the mailbox in this scanning
interval until the email arrives. Enter an integer.
1929
Setting Description
Maximum Trip Time Enter the number of seconds an email may take to arrive in the IMAP
(Sec.) 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
1930
Setting Description

Debug Options
Debug Options
Setting Description
scanning interval.
master node.
1931
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1932
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
1933
Channel Description
Response Time (IMAP) The response time of the IMAP server in milliseconds (msec)
Response Time (SMTP) The response time of the SMTP server in msec
Total The sum of the response time of the IMAP server and the SMTP server in
msec
More
Knowledge Base

1934
7.8.148 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 1944 .

§ 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
1935
Remarks
§ The parent device must be an SMTP server.
§ Use dedicated email accounts with this sensor. If you use more sensors of this type, make sure that
each sensor uses its own email accounts.
Add Sensor

Setting Description
inherited 146 .
1936
Setting Description
§ pop3sensor
§ roundtrip
§ mailsensor
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.
1937
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).
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
1938
Setting Description
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
Setting Description
1939
Step 2: Check a POP3 Mailbox until Email Arrives
In this step, you configure how to receive the sent emails.
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
default port for unsecure connections is 110 and the default port for secure

Connection Interval (Sec.) Enter the number of seconds the sensor waits between two connections
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 number of seconds an email may take to arrive in the POP3
(Sec.) 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
§ 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.
1940
Setting Description
§ 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-
Connection Security
Connection Security
Setting Description
1941
Setting Description

Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
1942
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1943
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Response Time (POP3) The response time of the POP3 server in milliseconds (msec)
Response Time (SMTP) The response time of the SMTP server in msec
Total The sum of the response time of the SMTP server and the POP3 server in
msec
1944
More
Knowledge Base

1945
7.8.149 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 sensor 2042 .
SNMP APC Hardw are Sensor
List 1951 .

§ 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
1946
§ See the Knowledge Base: How can I monitor additional counters with the SNMP APC Hardware
sensor?
§ See the 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.
right corner.

Setting Description
1947
Setting Description
inherited 146 .
§ apcups
sensor settings.
APC UPS Specific
APC UPS Specific
Setting Description
Interface Shows the name of the interface (performance counter) that this sensor
monitors.
1948
Setting Description
Unit String Define the unit of the numeric data that the 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.

Sensor Display
Sensor Display
Setting Description
1949
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1950
Maintenance Window.
Access Rights
Access Rights
Channel List
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
1951
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?

What SNMP sensors does PRTG offer?


1952
7.8.150 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 269 with the device template Buffalo TeraStation NAS to automatically create
SNMP Custom Table sensors 2068 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 3626 for traffic, memory, and load
average on the TeraStation.
SNMP Buffalo TS System Health Sensor
List 1957 .

§ Dutch: SNMP Buffalo TS Systeem Status
§ French: Buffalo TS état du système (SNMP)
§ German: SNMP Buffalo TS System Health
§ Japanese: SNMP Buffalo TS
§ Portuguese: Funcionamento do sistema Buffalo TS (SNMP)
1953
§ Russian: Рабо то сп о со бн о сть систем ы Buffalo TS п о SNMP
§ Simplified Chinese: SNMP Buffalo TS
§ Spanish: Salud de sistema Buffalo TS (SNMP)
Remarks
§ This sensor supports the TeraStation 3000, 3010, 3020, 5000, 5010, 6000, and 7000 series.
§ In certain cases, this sensor might show an error message. If you encounter such an issue, open the
settings of the parent device 571 , section SNMP Compatibility Options, and set the Walk Mode to Use
GETNEXT requests.
Add Sensor

Setting Description
1954
Setting Description
inherited 146 .
§ snmpbuffalots
§ buffalots
§ systemhealth
sensor settings.
Sensor Display
Sensor Display
Setting Description
1955
Setting Description


Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1956
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
1 Min CPU Load Average The average CPU load in percent
Errors The number of errors

Failover Status The failover status

§ Up status 186 : Busy, Idle
1957
Channel Description
§ Warning status: Initializing, Starting Backup, Starting Main, Stopping
Firmware Update If a firmware update is available

Available
§ Up status: No, Unknown
Percent Available The available memory in percent

Memory
Uptime The system uptime
Warnings The number of warnings
More
Knowledge Base



1958
7.8.151 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 1963 .

§ 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
1959
§ For a general introduction to the technology behind SNMP, see section Monitoring via SNMP 3348 .
Add Sensor
Cisco ADSL Settings
Setting Description
Line Index Select the performance counters that you want to monitor. PRTG creates
one sensor for each performance counter that you select.
right corner.

Setting Description
1960
Setting Description
inherited 146 .
§ snmpciscoadsl
sensor settings.
Cisco ADSL Settings
Cisco ADSL Settings
Setting Description
Line Index Shows the line index (performance counter) that this sensor monitors.
1961
Sensor Display
Sensor Display
Setting Description

Inherited Settings
1962
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
1963
Channel Description
Local Attenuation The local attenuation in decibels (db)
Local Power Output The local power output in db
Local SNR The local signal-to-noise ratio (SNR) in db
Remote Attenuation The remote attenuation in db
Remote Power Output The remote power output in db
Remote SNR The remote SNR in db
Speed Downlink The downlink speed in bytes per second

Speed Uplink The uplink speed in bytes per second
More
Knowledge Base



1964
7.8.152 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 1969 .

§ 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)
1965
Remarks
Add Sensor

Setting Description
inherited 146 .
1966
Setting Description
§ snmpciscoasavpnsensor
§ snmpciscoasavpnconnectionssensor
sensor settings.
Sensor Display
Sensor Display
Setting Description

1967
Setting Description
Inherited Settings
For more information, see section Root Group Settings 399 , section Credentials for SNMP Devices.
Scanning Interval
Scanning Interval
1968
objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Active Email Sessions The number of active email sessions
Active IPSec Sessions The number of active Internet Protocol Security (IPsec) sessions
Active L2L Sessions The number of active LAN-to-LAN (L2L) sessions
Active LB Sessions The number of active LB sessions
1969
Channel Description
Active Sessions The total number of active sessions

Active SVC Sessions The number of active switched virtual circuit (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


1970
7.8.153 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 1976 .

§ 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)
§ Russian: Траф ик SNMP Cisco ASA VPN
§ Spanish: Trafico VPN Cisco ASA (SNMP)
Remarks
§ This sensor can monitor IPsec connections only.
§ This sensor is intended to monitor permanent connections. It shows an error if a connection is

interrupted.
1971
§ See the Knowledge Base: I get the error PE123 when using the SNMP Cisco ASA VPN Traffic sensor.
What can I do?
Add Sensor
ASA VPN Specific
Setting Description
Connections Select the IPsec VPN connections that you want to monitor. PRTG
creates one sensor for each IPsec VPN connection that you select.
right corner.
This sensor can only monitor VPN connections based on IPsec. This
means, for example, that connections that use Cisco AnyConnect do
not appear in this list.

Setting Description
1972
Setting Description
inherited 146 .
§ snmpciscoasavpntrafficsensor
sensor settings.
ASA VPN Specific
ASA VPN Specific
Setting Description
Remote IP Address Shows the IP address of the connection that this sensor monitors.
1973
Setting Description

monitoring data.
This sensor can only monitor VPN connections based on IPsec.
Sensor Behavior Define the sensor status 186 if no active connection is available:
§ Show down status if no connection is active (recommended): 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
1974
Setting Description

Inherited Settings
1975
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
1976
Channel Description
Traffic In The incoming traffic in bytes per second

Traffic Out The outgoing traffic in bytes per second
More
Knowledge Base
I get the error PE123 when using the SNMP Cisco ASA VPN Traffic sensor. What can I do?


1977
7.8.154 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 1982 .

§ 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)
§ Russian: П о льзо ватели SNMP Cisco ASA VPN
§ Spanish: Usuarios VPN Cisco ASA (SNMP)
Remarks
§ 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?
1978
Add Sensor

Setting Description
inherited 146 .
§ snmpciscoasavpntrafficsensor
1979
Setting Description
sensor settings.
Sensor Display
Sensor Display
Setting Description

1980
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1981
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
[Account] The account status

§ Up status 186 : Offline, Online
Connected Accounts The number of connected accounts

More
Knowledge Base
1982
My SNMP Cisco ASA VPN Users sensor shows a user limit error. Why? What can I do?



1983
7.8.155 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 1989 .

§ 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
1984
§ For a general introduction to the technology behind Quality of Service (QoS) monitoring, see section
Monitoring Quality of Service 3372 .
Add Sensor
Class Based QoS Specific
Setting Description
Entries Select the entries that you want to monitor. PRTG creates one sensor for
each entry that you select.
right corner.

Setting Description
1985
Setting Description
inherited 146 .
§ cbqossensor
sensor settings.
1986
Setting Description
Object Type Shows the object type of the parameter that this sensor monitors.
Interface Shows the interface of the parameter that this sensor monitors.
Description Shows the description of the parameter that this sensor monitors.
BitMask Shows the number of available channels for the parameter that this sensor
monitors.
ObjectID Shows the ObjectID of the parameter that this sensor monitors.
ConfigID Shows the ConfigID of the parameter that this sensor monitors.
Sensor Display
Sensor Display
Setting Description
1987
Setting Description


Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1988
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Current Queue Depth The current queue depth
Drop Packets The number of drop packets per second
Drop Size The drop size per second
Maximum Queue Depth The maximum queue depth
No Buffer Drop Packets The number of drop packets without buffer per second
1989
Channel Description
Post Policy Size The post policy size per second
Pre Policy Packets The number of pre-policy packets per second
Pre Policy Size The pre-policy size per second
More
Knowledge Base



1990
7.8.156 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 1997 .

§ Dutch: SNMP Cisco System Health
§ French: Cisco état du système (SNMP)
§ German: SNMP Cisco Systemzustand
§ Japanese: SNMP Cisco
§ Portuguese: Funcionamento do sistema Cisco (SNMP)
§ Russian: Рабо то сп о со бн о сть систем ы устро йства SNMP Cisco
§ Simplified Chinese: SNMP Cisco
§ Spanish: Salud de sistema Cisco (SNMP)
Remarks
1991
§ SNMP Cisco System Health sensors that are created with the Cisco Device (Generic) device template
for auto-discovery can have additional tags.
Add Sensor
Cisco System Health Specific
Setting Description
Measurements Select the measurements that you want to monitor. PRTG creates one
sensor for each measurement that you select.
right corner.

Setting Description
1992
Setting Description
inherited 146 .
§ snmpciscosystemhealthsensor
§ systemhealth
sensor settings.
Setting Description
Measurements Shows the ID of the measurement that this sensor monitors.

1993
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
1994
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
1995
Maintenance Window.
Access Rights
Access Rights

1996
Channel List
PRTG creates one sensor per component.
Channel Description
Available Memory [#] The available memory in bytes
CPU [#] The CPU load in percent
Fan [#] State The state of fans

§ Up status 186 : Normal
§ Down status: Critical, Not Functioning, Shutdown
§ Unknown status: Not Present

Memory [#]
Power Supply [#] The state of power supplies
§ Down status: Critical, Not Functioning, Shutdown
§ Unknown status: Not Present
More
Knowledge Base



1997
7.8.157 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 2004 .

§ 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
1998
Add Sensor
Sensor Settings
Setting Description
Blade Servers Select the blade servers that you want to monitor. PRTG creates one
sensor for each blade server that you select.
right corner.

Setting Description
1999
Setting Description
inherited 146 .
§ systemhealth
§ ucssystemhealth
§ ucs
§ blade
sensor settings.
Sensor Settings
Sensor Settings
2000
Setting Description
Blade Servers Shows the blade server that this sensor monitors.
Channel Mask Shows the available channels for the blade server that this sensor
monitors.
Model Shows the model of the blade server that this sensor monitors.
Serial Number Shows the serial number blade server that this sensor monitors.
Sensor Display
Sensor Display
Setting Description
2001
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2002
Maintenance Window.
Access Rights
Access Rights

2003
Channel List
Channel Description
Oper State The oper state

§ Up status186 : 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 state

§ 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 state

§ 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
2004


2005
7.8.158 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 2011 .

§ Dutch: SNMP Cisco UCS Chassis
§ French: Cisco UCS châssis (SNMP)
§ German: SNMP Cisco UCS Chassis
§ Portuguese: Chassi Cisco UCS (SNMP)
§ Russian: Ко рп ус SNMP Cisco UCS
§ Spanish: Chasis Cisco UCS (SNMP)
Remarks
2006
Add Sensor
Sensor Settings
Setting Description
Chassis Select the chassis that you want to monitor. PRTG creates one sensor for
each chassis that you select.
right corner.

Setting Description
2007
Setting Description
inherited 146 .
§ systemhealth
§ ucssystemhealth
§ ucs
§ chassis
sensor settings.
Sensor Settings
Sensor Settings
Setting Description
Chassis Shows the chassis that this sensor monitors.

2008
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2009
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2010
Channel List
Channel Description
Config State The configuration state

§ Up status 186 : Acknowledged, Auto Acknowledge, OK
§ Warning status: Ack in Progress, Evaluation
§ Down status: Removing, UnAcknowledged, UnInitalized, Unsupported

Connectivity
License State The license state

§ Up status: License Ok
§ Warning status: License Grace Period, Unknown
§ Down status: License Expired, License Insufficient
§ Unknown status: Not Applicable
Oper State The oper state
2011
Channel Description

Operability The operability state


Power State The power state

§ 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 state
2012
Channel Description
§ 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



2013
7.8.159 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 2019 .

§ 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)
§ Russian: Физический диск SNMP Cisco UCS
§ Spanish: Disco físico Cisco UCS (SNMP)
Remarks
2014
Add Sensor
UCS Physical Disk
Setting Description
right corner.
This list only shows working disks that have the status Up or
Warning.

Setting Description
2015
Setting Description
inherited 146 .
§ snmpciscophysicaldisksensor
§ ucs
§ snmp
sensor settings.
UCS Physical Disk
UCS Physical Disk
Setting Description

Display Name Shows the display name of the physical disk that this sensor monitors.
2016
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2017
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2018
Channel List
Channel Description
Operability The operability status of the disk

§ Up status 186 : Auto Upgrade, Operable

Problem, Performance Problem, Post Failure, Powered Off, Power
Problem, Removed, Thermal Problem, Upgrade Problem, Voltage
Problem
Presence The connection status of the disk

§ Up status: Equipped, Equipped Not Primary
2019
Channel Description
§ 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



2020
7.8.160 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 2025 .

§ Dutch: SNMP Cisco UCS System Health
§ French: Cisco UCS état du système (SNMP)
§ German: SNMP Cisco UCS Systemzustand
§ Portuguese: Funcionamento do sistema Cisco UCS (SNMP)
§ Russian: Рабо то сп о со бн о сть систем ы SNMP Cisco UCS
§ Spanish: Salud de sistema Cisco UCS (SNMP)
2021
Remarks
Add Sensor

Setting Description
inherited 146 .
2022
Setting Description
§ systemhealth
§ ucssystemhealth
§ ucs
sensor settings.
Sensor Display
Sensor Display
Setting Description

2023
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2024
Access Rights
Access Rights

Channel List
Channel Description
Critical Faults Count The number of critical faults (that are not yet acknowledged in the UCS
logs)
2025
Channel Description
Fan Failure Predicted The predicted fan failure status
§ Up status 186 : No, Not Available

§ Down status: Yes
Fan Module Failure The predicted fan module failure status

Predicted
§ Up status: No, Not Available
§ 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
Fan Modules Operable The number of inoperable fan modules
Fan Performance The fan performance

§ Up status: Ok

Fan Thermal The fan thermal status
2026
Channel Description
§ 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
§ Up status: No, Not Available
§ Down status: Yes
Power Supply The power supply performance

Performance
§ Up status: Ok

Power Supply Thermal The power supply thermal status

§ Up status: Ok

2027
Channel Description
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



2028
7.8.161 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 2034 .

§ Dutch: SNMP CPU Load
§ French: Charge CPU (SNMP)
§ German: SNMP Prozessorlast
§ Japanese: SNMP CPU
§ Portuguese: Carga CPU (SNMP)
§ Russian: Загрузка ЦП SNMP
§ Simplified Chinese: SNMP CPU
§ Spanish: Carga CPU (SNMP)
Remarks
2029
§ It might not work to query data from a probe device via SNMP (querying localhost, 127.0.0.1, or ::1).
Add this device to PRTG 351 with the IP address that it has in your network and create the SNMP
sensor on this device instead.
Add Sensor

Setting Description
inherited 146 .
§ snmp
2030
Setting Description
§ cpu
§ cpuloadsensor
sensor settings.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
2031
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2032
Maintenance Window.
Access Rights
Access Rights

2033
Channel List
Channel Description
Processor [#] The CPU load in percent
Total The total CPU load in percent

More
Knowledge Base



2034
7.8.162 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 2040 .

§ Dutch: SNMP (Klant specifiek)
§ French: SNMP personnalisé
§ German: SNMP (Benutzerdef.)
§ Japanese: SNMP
§ Portuguese: SNMP (customizado)
§ Russian: П о льзо вательские п арам етры SNMP
§ Simplified Chinese: SNMP
§ Spanish: SNMP (personalizado)
Remarks
§ See the Knowledge Base: How do I find out which OID I need for an SNMP Custom sensor?
2035
Add Sensor
OID Settings
Setting Description
Channel Name Enter a name for the channel in which the sensor shows the results for the
OID. Enter a string.
sensor.
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.

between the last and the current value. PRTG additionally divides the
delta value by a time period to indicate a speed value.
tables, and gauges.

2036
Setting Description
inherited 146 .
§ snmpcustomsensor
sensor settings.
2037
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 Shows the value type of the numeric data that this sensor receives from
the OID.
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.

2038
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2039
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2040
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?



VIDEO TUTORIAL
SNMP Custom sensor and SNMP Custom Library sensor

§ https://www.paessler.com/support/videos-and-webinars/videos/snmp-custom-and-library-sensor
2041
7.8.163 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 sensor 2258 automatically creates SNMP Custom Advanced sensors when the
Management Information Base (MIB) file that you import contains single values.
SNMP Custom Advanced Sensor
List 2048 .

§ Dutch: SNMP Aanpasbaar Geavanceerd
§ French: SNMP personnalisé avancé
§ German: SNMP (Benutzerdef. erweitert)
§ Japanese: SNMP
§ Portuguese: SNMP (customizado / avançado)
§ Russian: До п о лн ительн ы е п о льзо вательские п арам етры SNMP
2042
§ Spanish: SNMP (personalizado / avanzado)
Remarks
Add Sensor
OID Settings
Setting Description
as 10 or 120.
or 120.

Absolute (float) and Delta (counter) are not compatible with the unit
Lookup.
§ Enable: Create this channel. Define further settings below.
2043
Setting Description
inherited 146 .
§ snmpcustomsensor
§ snmpcustomadvanced
sensor settings.
2044
OID Settings
OID Settings
Setting Description
Channel #x Name Enter a name for the channel in which the sensor shows the results at the
Channel #x OID Enter the OID of the SNMP object from which you want to receive numeric
data.
Channel #x Value Type Shows the value type of the numeric data that this sensor receives from
the OID.
Channel #x Unit Define the unit of the numeric data that this sensor receives from the OID:
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
2045
Setting Description
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
Sensors 3501 .
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.
Channel #2 - #10 Shows if the channel is enabled or disabled. If you enabled a channel, you
can define the settings of the channel as described above.
Sensor Display
Sensor Display
Setting Description
2046
Setting Description


Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2047
Maintenance Window.
Access Rights
Access Rights
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
2048


2049
7.8.164 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 2053 for and the reason for the
Warning or Down status 186 .
The SNMP Library sensor 2258 automatically creates SNMP Custom String sensors when the
Management Information Base (MIB) file that you import contains string values.
SNMP Custom String Sensor
List 2059 .

§ 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)
2050
Remarks
§ For an example, see section Number Extraction with Regular Expression 2058
Add Sensor

Setting Description
inherited 146 .
2051
Setting Description
§ snmpcustomstringsensor
sensor settings.
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.
2052
Setting Description

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) 3552 .
Down status.
2053
Setting Description
Search Method Define the method with which you want to provide the search string.
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.

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.
2054
Setting Description

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.
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.
2055
Setting Description
§ 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: Do not extract a float value. Use the result as a
string value.
§ 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 2058 .
For more information, see section Channel Settings 3052 .
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 string or leave the field empty.
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
Sensor Display
Sensor Display
2056
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2057
Maintenance Window.
Access Rights
Access Rights
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
§ Group 2 contains 3.49
Keep this note about index and capturing groups in mind when using number extraction.
2058
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 details, see section
Regular Expressions 3552 .
Channel List
Channel Description
Extracted Value The value extracted from the string (optional)

More
Knowledge Base



2059
7.8.165 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 186 by using a defined lookup file 3541 .
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 3549 SingleInt). For more information, see section
Example 2065 .
SNMP Custom String Lookup Sensor
List 2066 .

§ Dutch: SNMP Aangepaste Tekst Lookup
§ French: Requête de chaîne 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)
2060
Remarks
§ See section Example 2065 for a sample lookup definition for this sensor.
Add Sensor
OID Settings
Setting Description
Channel Name Enter a name for the channel in which the sensor shows the results for the
sensor.
Lookup Select a lookup file that is available in the \lookups\custom subfolder of

the PRTG program directory 3579 on the probe system.
The lookup file must contain all potential strings that the OID can
return.

2061
Setting Description
inherited 146 .
§ snmpcustomsensor
sensor settings.
2062
OID Settings
OID Settings
Setting Description
OID Enter the OID of the SNMP object that you want to receive a string from.
Lookup Shows the lookup file that this sensor uses.


Sensor Display
Sensor Display
2063
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2064
Maintenance Window.
Access Rights
Access Rights
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 3541 for this sensor that contains all these possible string values as text, each text value in one
lookup entry:
2065
<?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 186
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 2265 (this is an .oidlib file) that contains lookups 3541 (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 3547 for details about this mechanism.
Channel List
2066
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
2067
7.8.166 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 sensor 2258 automatically creates SNMP Custom Table sensors when the
Management Information Base (MIB) file that you import contains tables.
SNMP Custom Table Sensor
List 2076 .

§ 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
2068
§ See the Knowledge Base: What can I monitor with the SNMP Custom Table sensor?
Add Sensor
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.
Setting Description
Sensor Name Enter a meaningful name to identify the sensor. You can use the
placeholders [tablename] and [rowidentifier]. PRTG replaces them with the
name of the table and the identifying value of the chosen row respectively.
You can select the column that provides the row identifier in the
Identification Column option below.
You can also enter a valid OID that is part of a different SNMP table, for
example, [1.3.6.1.2.1.2.2.1.2], to query information that the current table
does not contain. PRTG adds the same index as in the original table to
the OID.
Table Specific
2069
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.
right corner.
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.
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.
Channel #2 - #10 You can create up to 10 different channels for this sensor. You must
define at least one data channel, so you already see all available settings
for Channel #1. Additionally, you can define Channel #2 up to Channel
#10. To do so, choose between:
§ Enable: Create this channel. Define further settings below.

All channels that you define during the creation of an SNMP
Custom Table sensor are the same for all sensors for each table
row.
as 10 or 120.
or 120.

Absolute (float) and Delta (counter) are not compatible with the unit
Lookup.
2070
Setting Description
See below 2072 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 186 . For example, if you monitor an ifTable, we recommend that you
do not select an ifDescr column because this results in an error.

Setting Description
inherited 146 .
2071
Setting Description
§ snmpcustomsensor
§ snmpcustomtable
sensor settings.
SNMP Table
SNMP Table
Setting Description
Table OID Shows the OID of the SNMP table that this sensor monitors.
Table Specific
Table Specific
2072
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. You can change the identifier if you want to.
Identification Column 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 Shows the value type of the data that this sensor receives in this channel.
Channel #x Unit Define the unit of the data that this sensor receives in this channel:
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Lookup
Sensors 3501 .
2073
Setting Description
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.
Channel #2 - #10 Shows if the channel is enabled or disabled.

Sensor Display
Sensor Display
Setting Description

2074
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2075
Access Rights
Access Rights
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?
2076
7.8.167 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 2082 .

§ 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
2077
Add Sensor
Dell EqualLogic Specific
Setting Description
right corner.

Setting Description
2078
Setting Description
inherited 146 .
§ dellequallogic
§ snmpdell
§ dell
sensor settings.
Setting Description
Volumes Shows the volume that this sensor monitors.
2079
Setting Description
Member ID Shows the member ID of the volume that this sensor monitors.
Volume ID Shows the ID of the volume that this sensor monitors.

Volume Description Shows the description of the volume that this sensor monitors.
Sensor Display
Sensor Display
Setting Description

2080
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2081
Access Rights
Access Rights

Channel List
Channel Description
Availability The availability status

§ Up status 186 : Available
§ Down status: Missing Members
2082
Channel Description
Average Write Latency The average write latency in msec
Connections The number of connections
Operations Status The operations status:

§ Up status: Available
§ 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,
More
Knowledge Base



2083
7.8.168 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 2090 .

§ 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)
2084
§ Russian: Рабо то сп о со бн о сть элем ен та Dell EqualLogic п о SNMP
§ Spanish: Salud de miembro Dell EqualLogic (SNMP)
Remarks
§ 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 548 of the parent device or inherit it from objects higher in
the hierarchy 140 .
Add Sensor
Setting Description
Array Member Select the array members that you want to monitor. PRTG creates one
sensor for each array member that you select.
right corner.

2085
Setting Description
inherited 146 .
§ dellequallogic
§ snmpdell
§ dell
sensor settings.
2086
Setting Description
Array Member Shows the name of the member that this sensor monitors.
Group ID Shows the group ID of the member that this sensor monitors.
Member ID Shows the ID of the group member that this sensor monitors.
Sensor Display
Sensor Display
Setting Description
2087
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2088
Maintenance Window.
Access Rights
Access Rights

2089
Channel List
Channel Description
Average Read Latency The average write latency in msec
Fan Power Cooling The power of the cooling module fan in revolutions per minute (RPM)
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 status of the power supply cooling module
Cooling Module [#]
§ Up status: On and Operating
§ Down status: Failed or No Data, No AC Power
RAID Status The status of the RAID

§ Up status: Expanding, Mirroring, Ok, Verifying
2090
Channel Description
§ Warning status: Degraded, Reconstructing
§ Down status: Catastrophic Loss, Failed
Storage Free % The free storage in percent
Temperature Control The control module temperature

Module [#] [Module]
More
Knowledge Base



2091
7.8.169 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 2099 .

§ 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
2092
Add Sensor
Setting Description
right corner.

Setting Description
2093
Setting Description
inherited 146 .
§ dellequallogic
§ snmpdell
§ dell
sensor settings.
2094
Setting Description

Group ID Shows the group ID of the physical disk that this sensor monitors.
Member ID Shows the group member ID of the physical disk that this sensor
monitors.
Disk Slot Shows the slot number of the physical disk that this sensor monitors.
Serial Number Shows the serial number of the physical disk that this sensor monitors.
Manufactured Shows 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
Setting Description
2095
Setting Description


Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2096
Setting Description
§ None
§ Saturdays
§ Sundays
§ Weekdays
§ Weekends

below.
past.
2097
Setting Description
can choose from:

object will depend.
an integer.
2098
Access Rights
Access Rights

Channel List
Channel Description
Bytes Read The bytes read per second
Bytes Written The bytes written per second
2099
Channel Description
Disk Status The health status of the disk

§ Up status 186 : 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 per second
More
Knowledge Base


2100
7.8.170 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 sensor 2042 or an SNMP Custom Table sensor 2068 .
SNMP Dell Hardw are Sensor
List 2106 .

§ 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
§ This sensor requires 2102 that the Dell OpenManage Server Administrator is installed on the monitored
Dell device.
2101
§ See the Knowledge Base: What do I need to monitor Dell servers?
Dell OpenManage Server This sensor needs the Dell OpenManage Server Administrator (OMSA)
Administrator tool to be installed on the target device to monitor it. Make sure that you
enable SNMP in the OMSA.
For details, see the Knowledge Base: What do I need to monitor Dell
servers?
Add Sensor
Dell Hardware Specific
Setting Description
Category Select the performance counters that you want to monitor. PRTG creates
one SNMP Custom Advanced sensor or SNMP Custom Table sensor with
up to 10 channels for each category that you select. If your selection
results in more than 10 channels, PRTG creates the corresponding
amount of SNMP Custom Advanced sensors or SNMP Custom Table
sensors.
Select the counters that you want to monitor with caution. We
recommend that you select only a few counters in this 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.
right corner.
2102
Setting Description
inherited 146 .
§ dell
2103
Dell Hardware Specific
Dell Hardw are Specific
Setting Description
Interface Shows 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.

Sensor Display
Sensor Display
2104
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2105
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
[Performance Counter] The value returned by a specific Dell hardware object identifier (OID), for
example
§ Data about the system management software
§ Data about system status
§ Information about chassis and BIOS
§ Various hardware parameters
§ Other valuable data
2106
More
Knowledge Base
What do I need to monitor Dell servers?



2107
7.8.171 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 2114 .

§ 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
§ This sensor requiresthat Integrated Dell Remote Access Controller (iDRAC) 7 or the Dell
2109
OpenManage Server Administrator (OMSA) are installed on the monitored server.

2108
§ See the Knowledge Base: I can't add Dell PowerEdge sensors to PRTG. What can I do?
§ See the Knowledge Base: My Dell PowerEdge sensor fails to validate disks and I can't add it. What
can I do?
Administrator or iDRAC 7 tool to be installed on the target device to monitor it. Make sure that you
servers?
You can also monitor Dell PowerEdge servers with this sensor via
iDRAC 7.
Add Sensor
Dell PowerEdge Physical Disk Settings
Setting Description
right corner.

2109
Setting Description
inherited 146 .
§ snmpdellphysicaldisksensor
§ physicaldisk
§ snmpdell
§ dell
sensor settings.
2110
Dell PowerEdge Physical Disk Settings
Dell Pow erEdge Physical Disk Settings
Setting Description

Data Source Shows the interface that PRTG uses to get monitoring data. This is either
Dell OMSA or iDRAC.
Sensor Display
Sensor Display
Setting Description
2111
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2112
Maintenance Window.
Access Rights
Access Rights

2113
Channel List
Channel Description
Component Status The component status

§ Up status 186 : Ok
§ Warning status: Non Critical
§ Down status: Critical, Non Recoverable, Other, Unknown
Disk State The disk state

§ Up status: Non-Raid, Online, Ready
§ Warning status: Foreign
§ Down status: Blocked, Critical, Failed, Non Recoverable, Other,

Removed, Unknown
Roll Up Status The roll up status

§ Up status: Ok
S.M.A.R.T. Warning The Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.)

status warning
§ Up status: No
§ Down status: Yes
More
Knowledge Base

I can't add Dell PowerEdge sensors to PRTG. What can I do?

2114
My Dell PowerEdge sensor fails to validate disks and I can't add it. What can I do?



2115
7.8.172 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 2122 .

§ Dutch: SNMP Dell PowerEdge Systeem Status
§ French: Dell PowerEdge état du système (SNMP)
§ German: SNMP Dell PowerEdge Systemzustand
§ Japanese: SNMP Dell PowerEdge
§ Portuguese: Funcionamento do sistema Dell PowerEdge (SNMP)
§ Russian: Рабо то сп о со бн о сть систем ы Dell PowerEdge п о SNMP
§ Simplified Chinese: SNMP Dell PowerEdge
§ Spanish: Salud de sistema Dell PowerEdge (SNMP)
2116
Remarks
§ This sensor requiresthat Integrated Dell Remote Access Controller (iDRAC) 7 or the Dell
2117
OpenManage Server Administrator (OMSA) are installed on the monitored server.

§ See the Knowledge Base: Why does my Dell PowerEdge System Health sensor show a power unit
status error after iDRAC update?
§ See the Knowledge Base: I can't add Dell PowerEdge sensors to PRTG. What can I do?
Administrator or iDRAC 7 tool to be installed on the target device to monitor it. Make sure that you
servers?
You can also monitor Dell PowerEdge servers with this sensor via
iDRAC 7.
Add Sensor
Dell PowerEdge System Health Specific
Setting Description
Chassis Select the chassis that you want to monitor. PRTG creates one sensor for
each chassis that you select.
2117
Setting Description

right corner.

Setting Description
inherited 146 .
§ snmpdellsystemhealthsensor
§ systemhealth
2118
Setting Description
§ snmpdell
§ dell
sensor settings.
Dell PowerEdge System Health Specific
Dell Pow erEdge System Health Specific
Setting Description
Chassis Shows the chassis that this sensor monitors.

Channel Mask Shows the channel mask that describes which channels are available.
Data Source Shows the interface that PRTG uses to get monitoring data. This is either
Dell OMSA or iDRAC.
2119
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2120
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2121
Channel List
Channel Description
Ampere Status The ampere status

Battery Status The battery status

§ Up status: OK
Chassis Status The chassis status

§ Up status: OK
Cooling Device Status The cooling device status
2122
Channel Description
§ 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
Power Supply Status The power supply status

§ Up status: OK
Power Unit Status The power unit status

§ Up status: OK
2123
Channel Description
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?

I can't add Dell PowerEdge sensors to PRTG. What can I do?




2124
7.8.173 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 2130 .

§ Dutch: SNMP vrije schijf ruimte
§ French: Espace disponible du disque (SNMP)
§ German: SNMP Datenträgerspeicher
§ Japanese: SNMP
§ Portuguese: Disco livre (SNMP)
§ Russian: Сво бо дн о е п ро стран ство п о SNMP
§ Spanish: Espacio libre en disco (SNMP)
Remarks
§ This sensor uses more generic object identifier (OID) values compared to the SNMP Linux Disk Free
sensor 2269 .
2125
Add Sensor
Disk Free Settings
Setting Description

Setting Description
2126
Setting Description
inherited 146 .
§ snmpdiskfreesensor
§ diskspacesensor
§ diskfree
§ snmp
sensor settings.
Disk Free Settings
Disk Free Settings
Setting Description

monitoring data.
2127
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2128
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2129
Channel List
Channel Description

More
Knowledge Base


2130
2131
7.8.174 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 2138 .

§ Dutch: SNMP Fujitsu System Health v2
§ French: Fujitsu état du système v2 (SNMP)
§ German: SNMP Fujitsu Systemzustand v2
§ Japanese: SNMP Fujitsu v2

§ Portuguese: Funcionamento do sistema Fujitsu (SNMP) v2
§ Russian: Рабо то сп о со бн о сть систем ы Fujitsu п о SNMP, версия 2
§ Simplified Chinese: SNMP Fujitsu 2

§ Spanish: Salud de sistema Fujitsu (SNMP) v2
2132
Remarks
§ Use an iRMC interface as parent device for this sensor.
§ Make sure that you enable SNMP in the iRMC via ServerView.
§ This sensor does not support SNMPv1.
§ As of iRMC S5, additional counters for physical disks and logical disks are supported.
§ This sensor supersedes the deprecated SNMP Fujitsu System Health sensor.
Add Sensor
System Specific
Setting Description

right corner.

2133
Setting Description
inherited 146 .
§ snmpfujitsusystemhealthsensor
§ snmp
§ systemhealth
§ fujitsu
§ irmc
sensor settings.
2134
System Specific
System Specific
Setting Description
Measurement Shows the type of measurement that this sensor monitors.

Sensor Version Shows the version of the sensor definition that was used to create this
sensor.
Identifier Shows 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 Shows the OID table index that this sensor uses.
Debug Options
Debug Options
2135
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

2136
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2137
Access Rights
Access Rights

Channel List
Channel Description
CPU Status The CPU status

2138
Channel Description
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
Power Supply Status The power supply status

§ Up status: OK
Temperature Status The temperature status

§ Up status: OK
2139
Channel Description
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


2140
7.8.175 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 2146 .

§ 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
2141
Add Sensor
Hardware Specific
Setting Description
Hardware Components Select the hardware components that you want to monitor. PRTG creates
one sensor for each hardware component that you select.
right corner.

Setting Description
2142
Setting Description
inherited 146 .
§ hardwarestatus
sensor settings.
Hardware Specific
Hardw are Specific
Setting Description
Hardware Components Shows the hardware component that this sensor monitors.
2143
Setting Description
Product ID Shows the product ID of the hardware component that this sensor
monitors.
Description Shows the description of the hardware component that this sensor
monitors.
Type Shows the type of the hardware component that this sensor monitors.
Sensor Display
Sensor Display
Setting Description

2144
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2145
Access Rights
Access Rights
Channel List
Channel Description
Errors The number of errors per second
Status The status of the hardware component

§ Up status 186 : Running
§ Warning status: Warning, Testing
§ Down status: Down, Unknown
More
Knowledge Base



2146
7.8.176 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 sensor 2042 .
SNMP HP LaserJet Hardw are Sensor
List 2152 .

§ 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)
Remarks
2147
Add Sensor
HP LaserJet Specific
Setting Description
Category Select the categories that you want to monitor. PRTG creates one SNMP
Custom Advanced sensor including all performance counters that you
select.
The following performance counters for your printer are available:
§ Toner/Status
§ Paper/Status
§ Jam/Status

right corner.

2148
Setting Description
inherited 146 .
§ hplaserjet
sensor settings.
Setting Description
Interface Shows the name of the category (performance counter) that this sensor
monitors.
2149
Setting Description

Sensor Display
Sensor Display
Setting Description


2150
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2151
Channel List
Channel Description
Jam The paper jam status

§ Up status 186 : 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
More
Knowledge Base



2152
7.8.177 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 2158 .

§ 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
§ Make sure that you add this sensor to a device whose IP address or Domain Name System (DNS)
name points to the HPE BladeSystem Enclosure hosting the Onboard Administrator.
2153
Add Sensor
HPE BladeSystem Specific
Setting Description
Server Blades Select the blades that you want to monitor. PRTG creates one sensor for
each server blade that you select.
right corner.

Setting Description
2154
Setting Description
inherited 146 .
§ snmp
§ hpe
§ blade
§ bladesystem
sensor settings.
Setting Description
Server Blades Shows the server blade that this sensor monitors.
2155
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2156
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2157
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
2158
More
Knowledge Base


2159
7.8.178 SNMP HPE BladeSystem Enclosure System Health Sensor
The SNMP HPE BladeSystem Enclosure System Health sensor monitors the system health of an HPE
BladeSystem device via the Simple Network Management Protocol (SNMP).
SNMP HPE BladeSystem Enclosure System Health Sensor
List 2164 .

§ Dutch: SNMP HPE BladeSystem Behuizing Systeem Gesteldheid
§ French: HPE BladeSystem Enclosure état du système (SNMP)
§ German: SNMP HPE BladeSystem Enclosure Systemzustand
§ Japanese: SNMP HPE BladeSystem
§ Portuguese: Funcionamento do sistema de gabinete HPE BladeSystem (SNMP)
§ Russian: Рабо то сп о со бн о сть систем ы ко рп уса HPE BladeSystem п о SNMP
§ Simplified Chinese: SNMP HPE BladeSystem
§ Spanish: Salud de sistema de gabinete HPE BladeSystem (SNMP)
Remarks
§ Make sure that you add this sensor to a device whose IP address or Domain Name System (DNS)
name points to the HPE BladeSystem Enclosure hosting the Onboard Administrator.
2160
Add Sensor

Setting Description
inherited 146 .
§ snmp
2161
Setting Description
§ hpe
§ blade
§ bladesystem
§ systemhealth
§ health
sensor settings.
Sensor Display
Sensor Display
Setting Description

2162
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2163
Access Rights
Access Rights

Channel List
Channel Description
2164
Channel Description
Enclosure Condition The enclosure condition

§ Up status: OK
Enclosure Manager The enclosure manager condition

Condition
§ Up status: OK
More
Knowledge Base



2165
7.8.179 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 2172 .

§ 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
§ For Gen9 servers or earlier: This sensor requires HPE Insight Management Agents and HPE Insight
Management WBEM Providers to be installed on the target device.
§ For Gen10 servers: This sensor requires HPE Agentless Management and the HPE Agentless
Management Service to be installed on the target device.
§ For Gen10 servers: Use the HPE Integrated Lights Out (iLO) interface as the parent device for this
sensor.
2166
§ This sensor supports monitoring iLO as of iLO version 3. We recommend that you use iLO 4 or later.
HPE system For Gen9 servers or earlier, this sensor needs a specific HPE system
management tools management tool to be installed on the target device to report data via
SNMP: HPE Insight Management Agents. To receive SNMP data from
redundant array of independent disks (RAID) controllers, you additionally
need HPE Insight Management Agents. For Gen10 servers, this sensor no
longer requires HPE system management tools. Instead, the sensor
needs the HPE Agentless Management Service to be installed on the
target device.
For more details 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.
Add Sensor
HPE ProLiant Logical Disk Settings
2167
Setting Description
Disk Select the logical disks that you want to monitor. PRTG creates one
sensor for each logical disk that you select.
right corner.

Setting Description
inherited 146 .
2168
Setting Description
§ snmphpelogicaldisksensor
§ logicaldisk
§ snmphpe
§ hpe
sensor settings.
Setting Description
Sensor Display
Sensor Display
2169
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2170
Maintenance Window.
Access Rights
Access Rights

2171
Channel List
Channel Description
Completion The completion in percent

This is only important when the disk status is "Reconstructing" or
"Expanding" and illustrates the progress of this task.
Disk Status The disk status

§ Up status 186 : 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




2172
7.8.180 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 2179 .

§ 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)
§ Russian: Ко н тро ллер п ам яти HPE ProLiant п о SNMP
§ Spanish: Controlador de memoria HPE ProLiant (SNMP)
2173
Remarks
sensor.
§ If modules are inserted at a later point, you must add this sensor anew.
§ See the Knowledge Base: Which lookup values are supported by the SNMP HPE ProLiant Memory
Controller sensor?
target device.
for this sensor.
2174
Add Sensor
HPE ProLiant Memory Controller Settings
Setting Description
Controllers Select the memory controllers that you want to monitor. PRTG creates
one sensor for each memory controller that you select.
right corner.

Setting Description
2175
Setting Description
inherited 146 .
§ snmphpememorycontrollersensor
§ memorycontroller
§ snmphpe
§ hpe
sensor settings.
Setting Description
Controller Shows the name of the controller that this sensor monitors.
2176
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2177
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2178
Channel List
Channel Description
Controller Condition. The condition of the controller

§ Up status: OK
Controller Error Status The error status of the controller

§ 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
2179
Channel Description
Module [#] Condition The condition of the module

§ Up status: OK
§ Down status: Degraded, Failed
Module [#] Status The status of the module

§ 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?



2180
7.8.181 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 2187 .

§ Dutch: SNMP HPE ProLiant Netwerkinterface
§ French: HPE ProLiant interface réseau (SNMP)
§ German: SNMP HPE ProLiant Netzwerkschnittstelle
§ Portuguese: Interface de rede HPE ProLiant (SNMP)
§ Russian: Сетево й ин терф ейс HPE ProLiant п о SNMP
§ Spanish: Interfaz de red HPE ProLiant (SNMP)
2181
Remarks
sensor.
§ 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)".
target device.
for this sensor.
Add Sensor
2182
HPE ProLiant Network Interface Settings
Setting Description
Network Interfaces Select the network interfaces that you want to monitor. PRTG creates one
sensor for each interface that you select.
right corner.
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).

Setting Description
2183
Setting Description
inherited 146 .
§ snmphpenetworkinterfacesensor
§ snmphpe
§ hpe
sensor settings.
HPE ProLiant Network Interface Settings
HPE ProLiant Netw ork Interface Settings
Setting Description
Network Interfaces Shows the name of the network interface that this sensor monitors.
2184
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2185
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2186
Channel List
Channel Description
Alignment Errors The number of alignment errors per second
Bad Frames Received The number of bad frames received per second
Bad Frames Transmitted The number of bad frames transmitted per second
Carrier Sense Errors The number of carrier sense errors per second
Excessive Collisions The number of excessive collisions per second
FCS Errors The number of Frame Check Sequence (FCS) errors per second
Frames Too Long The number of frames that are too long per second
Good Frames Received The number of good frames received per second
2187
Channel Description
Good Frames The number of good frames transmitted per second

Transmitted
Late Collisions The number of late collisions per second

More
Knowledge Base



2188
7.8.182 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 2195 .

§ 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)
§ Russian: Физический диск HPE ProLiant п о SNMP
§ Spanish: Disco físico HPE ProLiant (SNMP)
2189
Remarks
sensor.
§ The sensor only shows Disk Status and no other channels if it runs in "Limited Monitoring" mode. For
more information, see SNMP HPE ProLiant Physical Disk sensor not showing all information.
target device.
for this sensor.
Add Sensor
2190
HPE ProLiant Physical Disk Settings
Setting Description
right corner.

Setting Description
inherited 146 .
2191
Setting Description
§ snmphpephysicaldisksensor
§ physicaldisk
§ snmphpe
§ hpe
sensor settings.
Setting Description
Disk Shows the ID of the physical disk that this sensor monitors.
Sensor Display
Sensor Display
2192
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2193
Maintenance Window.
Access Rights
Access Rights

2194
Channel List
Channel Description
Corrected Read Errors The corrected read errors per second
Corrected Write Errors The corrected write errors per second
Disk Status The overall disk status

§ 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 per second
Hard Write Errors The number of hard write errors per second
S.M.A.R.T. Status The Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.)

status
§ Up status: OK
§ Warning status: Replace Drive
Sectors Read The number of sectors read per second
2195
Channel Description
Sectors Written The number of sectors written per second
Threshold Passed If the threshold is passed

§ Up status: No
§ Down status: Yes
More
Knowledge Base
SNMP HPE ProLiant Physical Disk sensor not showing all information




2196
7.8.183 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 2202 .

§ Dutch: SNMP HPE ProLiant Systeemstatus
§ French: HPE ProLiant état du système (SNMP)
§ German: SNMP HPE ProLiant Systemzustand
§ Portuguese: Funcionamento do sistema HPE ProLiant (SNMP)
2197
§ Russian: Рабо то сп о со бн о сть систем ы HPE ProLiant п о SNMP
§ Spanish: Salud de sistema HPE ProLiant (SNMP)
Remarks
sensor.
§ This sensor has predefined limits for temperatures and broken frames. You can change these limits
individually in the channel settings 3052 .
§ Redundant array of independent disks (RAID) controllers that have no hard disks assigned might
cause the Down status 186 . In this case, deactivate the respective controllers in the HPE ProLiant
BIOS to avoid sensor errors.
longer requires HPE system management tools.
for this sensor.
2198
Add Sensor

Setting Description
inherited 146 .
§ snmphpesystemhealthsensor
§ systemhealth
§ snmphpe
§ hpe
2199
Setting Description
sensor settings.
Sensor Display
Sensor Display
Setting Description

2200
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2201

Channel List
Channel Description
CPU Fan Status The CPU fan status

Disk Controller Status The disk controller status

§ Up status: OK
2202
Channel Description
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
Overall Status The overall status

§ Up status: OK
Power Consumption [#] The power consumption in watts (W)
Power Consumption [#] The power consumption in percent

(%)
Power Supply [#] The power supply condition

Condition
§ Up status: OK
§ 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
2203
Channel Description
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 error status after updating PRTG?


2204
7.8.184 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 2210 .

§ 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
§ This sensor requires the IBM Systems Director Platform Agent to be installed on the target device.
2205
§ See the Knowledge Base: What are the requirements to monitor IBM System x?
§ See the Knowledge Base: IBM System X sensors could not find any disk/data on this device
(PE187/PE188/PE194)
IBM Systems Director This sensor needs the IBM Systems Director Platform Agent to be
Platform Agent installed on the target IBM device to monitor it via SNMP.
For more information, see the Knowledge Base: What are the
requirements to monitor IBM System x?
Add Sensor
IBM System X Logical Disk Settings
Setting Description
right corner.

2206
Setting Description
inherited 146 .
§ snmpibmlogicaldisksensor
§ logicaldisk
§ snmpibm
§ ibm
sensor settings.
2207
Setting Description
Disk Shows the ID of the logical disk that this sensor monitors.
Sensor Display
Sensor Display
Setting Description

2208
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2209

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
2210
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)



2211
7.8.185 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 2217 .

§ 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)
§ Russian: Физический диск IBM System X п о SNMP
§ Spanish: Disco físico IBM System X (SNMP)
Remarks
2212
(PE187/PE188/PE194)
Add Sensor
IBM System X Physical Disk Settings
Setting Description
right corner.

2213
Setting Description
inherited 146 .
§ snmpibmphysicaldisksensor
§ physicaldisk
§ snmpibm
§ ibm
sensor settings.
2214
Setting Description
Sensor Display
Sensor Display
Setting Description

2215
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2216

Channel List
Channel Description


2217
More
Knowledge Base




2218
7.8.186 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 2225 .

§ 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)
§ Russian: Физическая п ам ять IBM System X п о SNMP
§ Spanish: Memoria física IBM System X (SNMP)
Remarks
2219
(PE187/PE188/PE194)
Add Sensor
IBM System X Physical Memory Settings
Setting Description
Modules Select the memory modules that you want to monitor. PRTG creates one
sensor for each memory module that you select.
right corner.

2220
Setting Description
inherited 146 .
§ snmpibmphysicalmemorysensor
§ memorycontroller
§ snmpibm
§ ibm
sensor settings.
2221
Setting Description
Name Shows the name of the memory module that this sensor monitors.
Caption Shows the caption of the memory module that this sensor monitors.
Serial Number Shows the serial number of the memory module that this sensor
monitors.
Size Shows the size of the memory module that this sensor monitors.
Sensor Display
Sensor Display
Setting Description
2222
Setting Description


Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2223
Maintenance Window.
Access Rights
Access Rights

2224
Channel List
Channel Description
Controller Condition. The condition of the memory controller


Power The power status

§ Up status: On
§ Down status: Off
More
Knowledge Base




2225
7.8.187 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 2232 .

§ Dutch: SNMP IBM System X System Health
§ French: IBM System X état du système (SNMP)
§ German: SNMP IBM System X Systemzustand
§ Portuguese: Funcionamento do sistema IBM System X (SNMP)
§ Russian: Рабо то сп о со бн о сть систем ы IBM System X п о SNMP
§ Spanish: Salud de sistema IBM System X (SNMP)
Remarks
§ This sensor can also run directly on an Integrated Management Module (IMM) network port and can
show the overall health of IMMs.
2226
§ 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 3053 .
(PE187/PE188/PE194)
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.
Add Sensor
IBM System X System Health Specific
Setting Description
2227
Setting Description

right corner.

Setting Description
inherited 146 .
§ snmpibmsystemhealthsensor
§ systemhealth
2228
Setting Description
sensor settings.
Setting Description
Source Shows the source of the measurement that this sensor monitors.

Sensor Display
Sensor Display
2229
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2230
Maintenance Window.
Access Rights
Access Rights

2231
Channel List
Channel Description
Ambient Temp The ambient temperature
CMOS Battery The CMOS battery voltage in millivolts (mV)
CPU [#] Temp The temperature of the CPU
Fan [#] Tach The fan revolutions per minute (RPM) or the percentage of the possible
maximum
Overall Status The overall system health

§ Up status 186 : Normal, System Level
SysBrd 3.3V The 3.3V-system board voltage in mV
SysBrd 5V The 5V-system board voltage in mV
SysBrd 12V The 12V-system board voltage in mV
More
Knowledge Base



2232
2233
7.8.188 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 2239 .

§ 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
§ 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.
2234
Add Sensor
InterSeptor Environment Specific
Setting Description
Measuring Point Select the measuring points that you want to monitor. PRTG creates one
sensor for each measuring point that you select.
right corner.

Setting Description
2235
Setting Description
inherited 146 .
§ interseptor
§ environment
sensor settings.
Setting Description
Name Shows the name of the measuring point that this sensor monitors.
Measuring Point Shows the measuring point that this sensor monitors.
2236
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2237
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2238
Channel List
Channel Description
Humidity The humidity in percent
Temperature The temperature
More
Knowledge Base



2239
7.8.189 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 2244 .

§ Dutch: SNMP Juniper NS systeemstatus
§ French: Juniper NS état du système (SNMP)
§ German: SNMP Juniper NS Systemzustand
§ Japanese: SNMP Juniper NS
§ Portuguese: Funcionamento do sistema Juniper NS (SNMP)
§ Russian: Рабо то сп о со бн о сть систем ы Juniper NS п о SNMP
§ Simplified Chinese: SNMP Juniper NS
§ Spanish: Salud de sistema Juniper NS (SNMP)
Remarks
2240
Add Sensor

Setting Description
inherited 146 .
§ snmpjuniper
2241
Setting Description
§ systemhealth
sensor settings.
Sensor Display
Sensor Display
Setting Description


2242
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2243

Channel List
Channel Description

Power Supply (Power) The status of the power supply

§ Up status 186 : Good
§ Down status: Fail
2244
Channel Description
Session Usage The session usage in percent
Temperature (System The system temperature

Temperature)
More
Knowledge Base



2245
7.8.190 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 2251 .

§ 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
2246
Add Sensor
LenovoEMC NAS Settings
Setting Description
right corner.

Setting Description
2247
Setting Description
inherited 146 .
§ snmplenovoemc
§ lenovoemc
§ physicaldisk
sensor settings.
Setting Description
2248
Setting Description
Name Shows the name of the physical disk that this sensor monitors.
Size Shows the size of the physical disk that this sensor monitors.
Sensor Display
Sensor Display
Setting Description

2249
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2250
Channel List
Channel Description
Disk Status The overall disk status

§ Warning status: Foreign, Unknown
§ Down status: Faulted, Missing
More
Knowledge Base


2251
7.8.191 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 2256 .

§ Dutch: SNMP LenovoEMC Systeem Status
§ French: LenovoEMC état du système (SNMP)
§ German: SNMP LenovoEMC Systemzustand
§ Japanese: SNMP LenovoEMC
§ Portuguese: Funcionamento do sistema LenovoEMC (SNMP)
§ Russian: Рабо то сп о со бн о сть систем ы LenovoEMC п о SNMP
§ Simplified Chinese: SNMP LenovoEMC
§ Spanish: Salud sistema LenovoEMC (SNMP)
2252
Remarks
Add Sensor

Setting Description
inherited 146 .
2253
Setting Description
§ snmplenovoemc
§ lenovoemc
§ systemhealth
sensor settings.
Sensor Display
Sensor Display
Setting Description

2254
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2255
Access Rights
Access Rights
Channel List
Channel Description
Fan "Internal Fan" The fan revolutions per minute (RPM)
RAID Status The status of the RAID

§ Warning status: Degraded, RebuildFS, Rebuilding, Unknown
§ Down status: Faulted
Temperature "CPU" The temperature of the CPU
Temperature "Drives" The temperature of the drives
Temperature "System" The temperature of the system
Voltage "System Voltage The system voltage (12V) in millivolts (mV)

(12V)"
Voltage "V1.1" The voltage of the 1.1V-battery in mV
Voltage "V3.3" The voltage of the 3.3V-battery in mV
2256
More
Knowledge Base


2257
7.8.192 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 2265 them into PRTG. PRTG also provides precompiled .oidlib files 2265 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

§ Dutch: SNMP Bibliotheek
§ French: Bibliothèque (SNMP)
§ German: SNMP-Bibliothek
2258
§ Japanese: SNMP
§ Portuguese: Biblioteca (SNMP)
§ Russian: Библио тека SNMP
§ Spanish: Biblioteca (SNMP)
Remarks
§ See the Knowledge Base: How do SNMP, MIBs and OIDs work?
§ See the Knowledge Base: How can I import my MIB files into PRTG?
§ See the Knowledge Base: Can't find a sensor for my device in PRTG but I believe it supports SNMP.
How to proceed?
To import MIB files into PRTG Hosted Monitor, see section Manage a PRTG Hosted Monitor
Subscription 81 .
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 3579 . It contains both the default PRTG library files and
your own library files.
List of SNMP Library Files
2259
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
2260
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 quotes.
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 Shows 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. Select one or more items by enabling or disabling
the check boxes in front of the respective line.
2261
Setting Description
Depending on the type of the selected entries, PRTG creates the following
sensors:
§ SNMP Custom Advanced sensor : For up to 10 channels for 10 OIDs
2042
each. For example, 22 selected single values result in 3 sensors: 2

sensors with 10 channels and 1 sensor with 2 channels.
§ SNMP Custom String sensor 2050 : For each selected entry that returns a
string value.
§ SNMP Custom Table sensor 2068 : 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 3093 from it and prepare it for distribution. For example, you
can refine the template with better name templates.

Setting Description
inherited 146 .
2262
Setting Description
§ snmplibrarysensor
sensor settings.
Sensor Specific
The available sensor settings depend on the sensor that the SNMP Library sensor creates. For details
about settings, see the sections of these sensors:
§ SNMP Custom Advanced sensor 2045
§ SNMP Custom String sensor 2052
§ SNMP Custom Table sensor 2072
Sensor Display
Sensor Display
Setting Description
2263
Setting Description


Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2264
Maintenance Window.
Access Rights
Access Rights
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 3579 .
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 3541 (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 186 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 3547 .
Subscription 81 .
Default .oidlib Files Overview

PRTG comes with the following .oidlib files.
2265
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.
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.
2266
.oidlib File Description
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.
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
2267
§ https://www.paessler.com/tools/mibimporter
2268
7.8.193 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 may be available for use because a part of this space may be reserved by the system, for
example, for redundancy purposes. For details, see the Knowledge Base: Why do SSH Disk Free and
SNMP Linux Disk Free show different values for my target Linux system?
List 2277 .

§ 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)
2269
§ Russian: Сво бо дн о е п ро стран ство диска в Linux п о SNMP
§ Simplified Chinese: SNMP Linux
§ Spanish: Espacio libre en disco Linux (SNMP)
Remarks
§ See the Knowledge Base: Why do SSH Disk Free and SNMP Linux Disk Free show different values
for my target Linux system?
§ See the Knowledge Base: Monitoring Linux problem - SNMP port not reachable
Add Sensor

Setting Description
inherited 146 .
2270
Setting Description
§ diskspacesensor
sensor settings.
Set Limits Checkes 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 186 , 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 3052 .
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.
2271
Setting Description
Percentage Limit Check Enable or disable a limit check for the free space in percentage channels
of all drives. By default, the sensor enables percentage limits with a lower
warning limit and a lower error limit. Choose between:
§ 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.
Upper Warning Limit This setting is only visible if you select Use the limits of both the sensor
Warning status. If the free disk space of one of your drives exceeds this
value, the sensor changes to the 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
and the channel settings above. Specify a lower limit in percent for the
Warning status. If the free disk space of one of your drives falls below this
the field empty.
2272
Setting Description
Lower Error Limit This setting is only visible if you select Use the limits of both the sensor
Down status. If the free disk space of one of your drives falls below this
the field empty.
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.
and the channel settings above. Specify an upper limit. Use the same unit
as shown by the free bytes channels of this sensor (by default this 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.
changes to the Warning status. Enter an integer or leave the field empty.
2273
Setting Description
and the channel settings above. Specify a lower limit. Use the same unit
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.
sensor changes to the Down status. Enter an integer or leave the field
empty.
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
2274
Setting Description


Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2275
Maintenance Window.
Access Rights
Access Rights

2276
Channel List
Channel Description
Free Bytes [Partition] The free space in bytes
Free INodes [Partition] The free index nodes in percent
Free Space [Partition] The free space in percent
Total The free total disk space in bytes
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




2277
7.8.194 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 2281 .

§ Dutch: SNMP Linux Gemiddelde belasting
§ French: Linux charge moyenne (SNMP)
§ German: SNMP Linux Durchschnittliche Last
§ Portuguese: Carga média Linux (SNMP)
§ Russian: Средн яя загрузка Linux п о SNMP
§ Spanish: Promedio de carga Linux (SNMP)
Remarks
2278
Add Sensor

Setting Description
inherited 146 .
§ snmploadsensor
2279
sensor settings.
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2280
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2281
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



2282
7.8.195 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 2287 .

§ 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)
2283
Remarks
Add Sensor

Setting Description
inherited 146 .
2284
Setting Description
§ snmpmeminfosensor
§ memorysensor
sensor settings.
Sensor Display
Sensor Display
Setting Description

2285
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2286
Access Rights
Access Rights

Channel List
Channel Description
2287
Channel Description
Free Physical Memory The free physical memory in bytes
Free Physical Memory % The free physical memory in percent

Free Swap Space The free swap memory in bytes
Free Swap Space % The free swap memory in percent
Total Free Memory The total free memory (physical memory plus swap) in bytes
Total Free Memory % The total free memory (physical memory plus swap) in percent
More
Knowledge Base



2288
7.8.196 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 2294 .

§ Dutch: SNMP Linux Fysieke Schijf
§ French: Linux disque physique (SNMP)
§ German: SNMP Linux Physikalischer Datenträger
§ Portuguese: Disco físico Linux (SNMP)
§ Russian: Физический диск Linux п о SNMP
§ Spanish: Disco físico Linux (SNMP)
Remarks
2289
Add Sensor
Physical Disk Settings
Setting Description
right corner.

Setting Description
2290
Setting Description
inherited 146 .
§ snmpphysicaldisksensor
§ physicaldisk
sensor settings.
Setting Description

BitMask Shows the bitmask that might be necessary for bug tracking purposes.
2291
Setting Description
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2292
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2293
Channel List
Channel Description
Bytes Read The bytes read per second

Bytes Written The bytes written per second
Load Average (1 Minute) The load average (1 minute) in percent
Load Average (5 Minute) The load average (5 minutes) in percent
Load Average (15 Minute) The load average (15 minutes) in percent
Read Accesses The number of read accesses per second
Write Accesses The number of write accesses per second
2294
More
Knowledge Base



2295
7.8.197 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 sensor 2283 .
SNMP Memory Sensor
List 2301 .

§ Dutch: SNMP Geheugen
§ French: Mémoire (SNMP)
§ German: SNMP Speicher
§ Japanese: SNMP
§ Portuguese: Memória (SNMP)
§ Russian: П ам ять п о SNMP
§ Spanish: Memoria (SNMP)
Remarks
2296
Add Sensor
Memory Settings
Setting Description
Memory Type Select the memory types that you want to monitor. PRTG creates one
sensor for each memory type that you select.
right corner.

Setting Description
2297
Setting Description
inherited 146 .
§ snmpmemorysensor
§ memory
§ memorysensor
§ snmp
sensor settings.
Memory Settings
Memory Settings
Setting Description
Memory Type Shows the type of memory that this sensor monitors.
2298
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2299
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2300
Channel List
Channel Description

Memory
Total Memory The total memory in bytes
More
Knowledge Base


2301
2302
7.8.198 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 2308 .

§ 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)
2303
Remarks
§ See the Knowledge Base: How can I monitor capacity and used disk space on a NetApp?
Add Sensor
NetApp Disk Free Settings
Setting Description
File System Select the disks that you want to monitor. PRTG creates one sensor for
right corner.

2304
Setting Description
inherited 146 .
§ snmpnetappdiskfreesensor
§ snmpnetapp
§ netapp
sensor settings.
2305
Setting Description
File System Shows the name of the disk that this sensor monitors.
Virtual Disk Shows the name of the virtual disk that this sensor monitors (if
applicable).
Sensor Display
Sensor Display
Setting Description


2306
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2307

Channel List
Channel Description
Deduplication Saved The deduplication saved space in bytes

Space
Deduplication Saved The deduplication saved space in percent

Space %
Deduplication Shared The deduplication shared space in bytes

Space
Deduplication Shared The deduplication shared space in percent

Space %
2308
Channel Description
§ Up status : Creating, Mounted, Mounting, Nofsinfo, Replayed,

186
Replaying, Unmounting
§ Down status: Destroying, Frozen, Unmounted
Files Free The free files in percent

INodes Free The free index nodes in percent
More
Knowledge Base
How can I monitor capacity and used disk space on a NetApp?



2309
7.8.199 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 2316 .

§ Dutch: SNMP NetApp Behuizing
§ French: NetApp boîtier (SNMP)
§ German: SNMP NetApp Enclosure
§ Portuguese: Gabinete NetApp (SNMP)
§ Russian: Ко рп ус NetApp п о SNMP
§ Spanish: Gabinete NetApp (SNMP)
2310
Remarks
§ This sensor only supports NetApp versions up to 8.2.
Add Sensor
NetApp Enclosure Settings
Setting Description
Enclosures Select the power supply and cooling measurements of the enclosures that
you want to monitor. PRTG creates one sensor for each
enclosure/measurement combination that you select.
right corner.

2311
Setting Description
inherited 146 .
§ snmpnetappenclosuresensor
§ snmpnetapp
§ netapp
sensor settings.
2312
Setting Description
Enclosure Shows 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 186 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 3052 of the affected
channels and select this file in section Lookup. For details, see section
Define Lookups 3541 .
2313
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2314
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2315
Channel List
Channel Description
Broken Electronic Parts The number of broken electronic parts
Broken Power Supplies The number of broken power supplies
Current [#] The current in milliampere (mA)
Fan [#] The fan revolutions per minute (RPM)
Fans Failed The number of failed fans
Voltage [#] The voltage in millivolts (mV)
More
Knowledge Base
2316


2317
7.8.200 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 2322 .

§ 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)
§ Russian: Вво д-вы во д NetApp п о SNMP
§ Simplified Chinese: SNMP NetApp I/O
2318
§ Spanish: E/S NetApp (SNMP)
Remarks
§ If you use NetApp cDOT 8.3 or NetApp ONTAP 9.0 or later, we recommend that you use the NetApp
I/O sensor 1450 instead.
Add Sensor

Setting Description
inherited 146 .
2319
Setting Description
§ snmpnetappiosensor
§ snmpnetapp
§ netapp
sensor settings.
Sensor Display
Sensor Display
Setting Description

2320
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2321
Access Rights
Access Rights

Channel List
Channel Description
CIFS Ops The number of Common Internet File System (CIFS) operations per
second
2322
Channel Description
FCP Ops The number of Fibre Channel Protocol (FCP) operations per second
FCP Read The FCP read speed in bytes per second

FCP Write The FCP write speed in bytes per second
HTTP Ops The number of HTTP operations per second
ISCSI Ops The number of Internet Small Computer System Interface (iSCSI)
operations per second
ISCSI Read The ISCSI read speed in bytes per second
ISCSI Write The ISCSI write speed in bytes per second
Network Received The number of bytes received per second
Network Sent The number of bytes sent per second
NFS Ops The network file system (NFS) operations per second
Tape Read The tape read speed in bytes per second
Tape Write The tape write speed in bytes per second
More
Knowledge Base



2323
7.8.201 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 2329 .

§ Dutch: SNMP NetApp licentie
§ French: NetApp Licence (SNMP)
§ German: SNMP NetApp Lizenz
§ Portuguese: Licença NetApp (SNMP)
§ Russian: Лицен зия NetApp п о SNMP
§ Spanish: Licencia NetApp (SNMP)
Remarks
2324
Add Sensor
NetApp License Settings
Setting Description
Licenses for Services Select the licenses for the services that you want to monitor. PRTG
creates one sensor for each license that you select.
right corner.

Setting Description
2325
Setting Description
inherited 146 .
§ snmpnetapplicensesensor
§ snmpnetapp
§ netapp
sensor settings.
Setting Description
License for Service Shows the name of the license whose service this sensor monitors.
2326
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2327
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2328
Channel List
Channel Description
Time Left The time until the license for a service expires
More
Knowledge Base



2329
7.8.202 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 2336 .

§ Dutch: SNMP NetApp Logical Unit
§ French: NetApp unité logique (SNMP)
§ German: SNMP NetApp Logische Einheit
§ Portuguese: Unidade lógica NetApp (SNMP)
§ Russian: Ло гический бло к NetApp п о SNMP
§ Spanish: Unidad lógica NetApp (SNMP)
2330
Remarks
LUN sensor 1471 instead.
Add Sensor
NetApp Logical Unit Settings
Setting Description
Logical Unit Select the logical units that you want to monitor. PRTG creates one
sensor for each logical unit that you select.
right corner.
Alignment Monitoring Select if the sensor checks the alignment of the logical unit:
§ Do not check alignment
§ Check alignment (if available)

2331
Setting Description
inherited 146 .
§ snmpnetappdiskfreesensor
§ snmpnetapp
§ netapp
sensor settings.
2332
Setting Description
Logical Unit Shows the name of the logical unit that this sensor monitors.
Alignment Monitoring Shows if the sensor checks the alignment of the logical unit.
Volume Shows the volume that this sensor monitors.

Comment Shows comments for the logical unit that this sensor monitors.
Sensor Display
Sensor Display
2333
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2334
Maintenance Window.
Access Rights
Access Rights

2335
Channel List
Channel Description
Errors The number of errors per second
Ops The total number of operations per second

Other Ops The number of other operations per second
Status The status of the logical unit

§ Down status: Offline
More
Knowledge Base



2336
7.8.203 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 2342 .

§ Dutch: SNMP NetApp Network Interface
§ French: NetApp interface réseau (SNMP)
§ German: SNMP NetApp Netzwerkschnittstelle
§ Portuguese: Interface de rede NetApp (SNMP)
§ Russian: Сетево й ин терф ейс NetApp п о SNMP
§ Spanish: Interfaz de red NetApp (SNMP)
Remarks
2337
NIC sensor 1482 instead.
Add Sensor
NetApp Network Interface Settings
Setting Description
Network Interface Select the network interfaces that you want to monitor. PRTG creates one
sensor for each interface that you select.
right corner.

Setting Description
2338
Setting Description
inherited 146 .
§ snmpnetappnetworkinterfacesensor
§ snmpnetapp
§ netapp
sensor settings.
NetApp Network Interface Settings
NetApp Netw ork Interface Settings
Setting Description
Network Interface Shows the name of the network interface that this sensor monitors.
2339
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2340
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2341
Channel List
Channel Description
Errors In The number of incoming errors per second
Errors Out The number of outgoing errors per second

More
Knowledge Base

2342

2343
7.8.204 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 2348 .

§ Dutch: SNMP NetApp Systeemstatus
§ French: NetApp intégrité du système (SNMP)
§ German: SNMP NetApp Systemzustand
§ Portuguese: Funcionamento do sistema NetApp (SNMP)
§ Russian: Рабо то сп о со бн о сть систем ы NetApp п о SNMP
2344
§ Spanish: Salud de sistema NetApp (SNMP)
Remarks
System Health sensor 1513 instead.
Add Sensor

Setting Description
inherited 146 .
2345
Setting Description
§ snmpnetappsystemhealthsensor
§ snmpnetapp
§ netapp
sensor settings.
Sensor Display
Sensor Display
Setting Description

2346
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2347
Access Rights
Access Rights

Channel List
Channel Description
CPU Load The CPU load in percent
Disks Active The number of active disks
2348
Channel Description
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
Disks Total The number of disks in total

Disks Verifying Parity The number of disks that are verifying parity
More
Knowledge Base



2349
7.8.205 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 2356 .

§ 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
§ Nutanix devices only support SNMP v3. Make sure that you select SNMP v3 in the credentials for
SNMP devices 548 settings of the parent device.
2350
Add Sensor
System Specific
Setting Description
Measurement Select the measurements that you want to monitor. PRTG creates one

right corner.

Setting Description
2351
Setting Description
inherited 146 .
§ snmpnutanixclusterhealthsensor
§ snmp
§ nutanix
sensor settings.
System Specific
System Specific
2352
Setting Description
sensor.
table.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
2353
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2354
Maintenance Window.
Access Rights
Access Rights

2355
Channel List
Channel Description
I/O Bandwidth The bandwidth of input/output (I/O) operations in bytes per second
I/O Latency The latency of I/O operations in milliseconds (ms)
I/O Operations The number of I/O operations per second
Status The status of the Nutanix cluster

§ Up status 186 : Started
§ Warning status: Starting, Stopping
§ Down status: Stopped, Unknown
More
Knowledge Base



2356
7.8.206 SNMP Nutanix Hypervisor Sensor
The SNMP Nutanix Hypervisor sensor monitors a Nutanix hypervisor via the Simple Network
SNMP Nutanix Hypervisor Sensor
List 2363 .

§ 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)
2357
Remarks
§ Nutanix devices only support SNMP v3. Make sure that you select SNMP v3 in the credentials for
SNMP devices 548 settings of the parent device.
Add Sensor
System Specific
Setting Description

right corner.

2358
Setting Description
inherited 146 .
§ snmpnutanixhypervisorsensor
§ snmp
§ nutanix
sensor settings.
System Specific
System Specific
2359
Setting Description
sensor.
table.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
2360
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2361
Maintenance Window.
Access Rights
Access Rights

2362
Channel List
Channel Description

I/O Bandwidth The bandwidth of input/output (I/O) operations in bytes per second
I/O Latency The latency of I/O operations in microseconds (µ s)
I/O Read The read speed of I/O operations per second
I/O Write The write speed of I/O operations per second
Package Drop In The number of dropped incoming packages per second
Package Drop Out The number of dropped outgoing packages per second
VM Count The number of virtual machines (VM)
More
Knowledge Base



2363
7.8.207 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 2369 .

§ 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
2364
Add Sensor
Poseidon Environment Specific
Setting Description
Measuring Point Select the measuring points that you want to monitor. PRTG creates one
sensor for each measuring point that you select.
right corner.

Setting Description
2365
Setting Description
inherited 146 .
§ apcups
sensor settings.
Setting Description
Name Shows the name of the measurement that this sensor monitors.
Unit Shows the unit of the value measurement that this sensor monitors.
2366
Setting Description
Measuring Point Shows the measuring points that this sensor monitors.
Sensor Display
Sensor Display
Setting Description

2367
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2368
Channel List
Channel Description
[Value] The humidity in percent or the temperature
More
Knowledge Base



2369
7.8.208 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 2374 .

§ Dutch: SNMP Printer
§ French: Imprimante (SNMP)
§ German: SNMP Drucker
§ Japanese: SNMP
§ Portuguese: Impressora (SNMP)
§ Russian: П рин тер п о SNMP
§ Spanish: Impresora (SNMP)
2370
Remarks
§ 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.
Add Sensor

Setting Description
inherited 146 .
2371
Setting Description
§ snmp
§ printer
sensor settings.
Sensor Display
Sensor Display
Setting Description

2372
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2373
Access Rights
Access Rights
Channel List
Channel Description
Black Cartridge [Printer] The fill level of the cartridge

§ Up status 186 : No Restriction, Not Empty, Ok
§ Warning status: Low
Cyan Cartridge [Printer] The fill level of the cartridge

§ Up status: No Restriction, Not Empty, Ok
Magenta Cartridge The fill level of the cartridge

[Printer]
Printer Cover The status of the printer cover
2374
Channel Description
§ 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 fill level of the cartridge

More
Knowledge Base


2375
7.8.209 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 2381 .

§ 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
2376
Add Sensor
QNAP NAS Settings
Setting Description
right corner.

Setting Description
2377
Setting Description
inherited 146 .
§ snmpqnap
§ qnap
§ logicaldisk
sensor settings.
QNAP NAS Settings
QNAP NAS Settings
Setting Description
Disk Shows the logical disk that this sensor monitors.

Description Shows the name of the disk that this sensor monitors.
2378
Setting Description
File System Shows the file system of the disk that this sensor monitors.
Sensor Display
Sensor Display
Setting Description

2379
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2380
Channel List
Channel Description

Volume Status The volume status

§ Up status 186 : Ready
§ Warning status: In Degraded Mode, Rebuilding, Synchronizing
§ Down status: Failure
More
Knowledge Base




2381
7.8.210 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 2387 .

§ Dutch: SNMP QNAP Fysieke Schijf
§ French: QNAP disque physique (SNMP)
§ German: SNMP QNAP Physikalischer Datenträger
§ Portuguese: Disco físico QNAP (SNMP)
§ Russian: Физический диск QNAP п о SNMP
§ Spanish: Disco físico QNAP (SNMP)
Remarks
2382
Add Sensor
QNAP NAS Settings
Setting Description
right corner.
Unit Select the unit of the temperature measurement:

§ Celsius
§ Fahrenheit

Setting Description
2383
Setting Description
inherited 146 .
§ snmpqnap
§ qnap
§ physicaldisk
sensor settings.
QNAP NAS Settings
QNAP NAS Settings
2384
Setting Description

Description Shows information about the physical disk that this sensor monitors.
Model Shows the model of the physical disk that this sensor monitors.
Capacity Shows the capacity of the physical disk that this sensor monitors.
Unit Shows the unit of the temperature measurement.

Sensor Display
Sensor Display
Setting Description
2385
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2386
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
HD Status The disk status

§ Up status 186 : Ready
§ Down status: Invalid, No Disk, RwError, Unknown
S.M.A.R.T. Status The Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.)

status of the disk
§ Up status: Good, Normal
§ Down status: Bad
2387
Channel Description

More
Knowledge Base




2388
7.8.211 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 2393 .

§ Dutch: SNMP QNAP Systeemstatus
§ French: QNAP état du système (SNMP)
§ German: SNMP QNAP Systemzustand
§ Portuguese: Funcionamento do sistema QNAP (SNMP)
§ Russian: Рабо то сп о со бн о сть систем ы QNAP п о SNMP
§ Spanish: Salud de sistema QNAP (SNMP)
Remarks
2389
Add Sensor
QNAP NAS Settings
Setting Description
Unit Select the unit of the temperature measurement:

§ Celsius
§ Fahrenheit

Setting Description
inherited 146 .
2390
Setting Description
§ snmpqnap
§ qnap
§ systemhealth
sensor settings.
QNAP NAS Settings
QNAP NAS Settings
Setting Description
Unit Shows the unit of temperature measurement that the sensor monitors.
Sensor Display
Sensor Display
2391
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2392
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
CPU Temperature The temperature of the CPU

Fan [#] (System FAN [#]) The fan revolutions per minute (RPM)
2393
Channel Description
System Temperature The system temperature
More
Knowledge Base




2394
7.8.212 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 2399 .

§ Dutch: SNMP Rittal CMC III Hardware Status
§ French: SNMP Rittal CMC III Hardware Status
§ German: SNMP Rittal CMC III Hardware Status
§ Japanese: SNMP Rittal CMC III Hardware Status
§ Portuguese: SNMP Rittal CMC III Hardware Status
§ Russian: SNMP Rittal CMC III Hardware Status
§ Simplified Chinese: SNMP Rittal CMC III Hardware Status
§ Spanish: SNMP Rittal CMC III Hardware Status
2395
Remarks
Add Sensor

Setting Description
inherited 146 .
2396
Setting Description
§ snmprittal
§ cmc3
Sensor Display
Sensor Display
Setting Setting


2397
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2398
Channel List
Channel Description
Overall Device Status The overall status of the device

§ Up status: OK, Update
§ Warning status: Warning, Detected, Changed
§ Down status: Alarm, Lost
[Status of attached The status of an attached external sensor

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

2399
7.8.213 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 2406 .

§ Dutch: SNMP RMON
§ French: RMON (SNMP)
§ German: SNMP RMON
§ Japanese: SNMP RMON
§ Portuguese: RMON (SNMP)
§ Russian: RMON п о SNMP
§ Simplified Chinese: SNMP RMON
2400
§ Spanish: RMON (SNMP)
Remarks
§ You can define the displayed sensor name with port name templates in the SNMP compatibility
options 571 of the parent device.
§ See the Knowledge Base: What value does the Transmitted channel of an RMON sensor show?
§ See the Knowledge Base: SNMP Traffic sensors when the device changes them
Add Sensor
RMON Specific
Setting Description
Ports Select the ports that you want to monitor. PRTG creates one sensor for
each port that you select.
right corner.
You can select interfaces and cancel the selection by clicking Select
all connected interfaces, Select all disconnected interfaces, and
Deselect all interfaces.

2401
Setting Description
inherited 146 .
§ snmprmon
sensor settings.
2402
RMON Specific
RMON Specific
Setting Description
Port Shows the number of the interface port that this sensor monitors.
Channel Mask Describes which channels are available and might be useful for the
Paessler support team.
Sensor Display
Sensor Display
Setting Description
2403
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2404
Maintenance Window.
Access Rights
Access Rights

2405
Channel List
Channel Description
Broadcast Packets The number of broadcast packets per second
Collisions The number of collisions per second
CRC Errors The number of cyclic redundancy check (CRC) errors per second
Drop Events The number of drop events per second
Fragments The number of fragments per second
Jabbers The number of jabbers per second
Multicast Packets The number of multicast packets per second
Oversize Packets The number of oversize packets per second
Packets The number of packets per second
Packets <= 64 Byte The number of packets with less than or equal to 64 bytes per second
Packets 65 - 127 Bytes The number of packets with 65 - 127 bytes per second
Packets 512 - 1023 The number of packets with 512 - 1023 bytes per second
Bytes
Packets 1024 - 1518 The number of packets with 1024 - 1518 bytes per second
Bytes
Transmitted The transmitted bytes per second

2406
Channel Description
Undersize Packets The number of undersize packets per second
More
Knowledge Base
What value does the Transmitted channel of an RMON sensor show?






2407
7.8.214 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 2412 .

§ Dutch: SNMP SonicWall Systeem Gezondheid
§ French: SonicWall état du système (SNMP)
§ German: SNMP SonicWall Systemzustand
§ Japanese: SNMP SonicWall
§ Portuguese: Funcionamento do sistema SonicWall (SNMP)
§ Russian: Рабо то сп о со бн о сть систем ы SonicWall п о SNMP
§ Simplified Chinese: SNMP SonicWall
§ Spanish: Salud de sistema SonicWall (SNMP)
Remarks
§ See the Knowledge Base: Why does PRTG write error messages into my SonicWall log?
2408
Add Sensor

Setting Description
inherited 146 .
§ snmpsonicwallsystemhealthsensor
§ systemhealth
2409
Setting Description
sensor settings.
Sensor Display
Sensor Display
Setting Description

2410
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2411

Channel List
Channel Description
Connection Cache Used The connection cache usage in percent

2412
More
Knowledge Base
Why does PRTG write error messages into my SonicWall log?



2413
7.8.215 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 2420 .

§ 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
2414
§ See the Knowledge Base: Why does PRTG write error messages into my SonicWall log?
Add Sensor
SonicWall VPN Specific
Setting Description
Connections Select the connections that you want to monitor. PRTG creates one
sensor for each connection that you select.
right corner.
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.
§ 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.

2415
Setting Description
inherited 146 .
§ snmpsonicwallvpntrafficsensor
§ traffic
sensor settings.
2416
Setting Description
Security Policy Shows the security policy of the connection that this sensor monitors.
Remote IP Address Shows the remote IP address of the connection that this sensor monitors.
Source IP Addresses Shows the source IP addresses of the connection that this sensor
monitors.
Destination IP Addresses Shows the destination IP addresses of the connection that this sensor
monitors.
Index Shows the index of the connection that this sensor monitors.
Identification Method Shows the identification method of the connection that this sensor
monitors.
2417
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2418
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2419
Channel List
Channel Description
Decrypted Packets The number of decrypted packets per second
Decrypted Transmissions The decrypted transmissions in bytes per second
Encrypted Packets The number of encrypted packets per second

Encrypted Transmissions The encrypted transmissions in bytes per second
Fragmented Packets In The number of incoming fragmented packets per second
Fragmented Packets Out The number of outgoing fragmented packets per second
2420
More
Knowledge Base
Why does PRTG write error messages into my SonicWall log?



2421
7.8.216 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 2426 .

§ 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
2422
Add Sensor
Synology NAS Settings
Setting Description
right corner.

Setting Description
2423
Setting Description
inherited 146 .
§ snmpsynology
§ synology
§ logicaldisk
sensor settings.
Setting Description

monitoring data.
2424
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2425
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2426
Channel Description
Volume Status The status of a volume
§ Up status : Converting SHR to Pool, Data Scrubbing, Deploying,

186
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


2427
7.8.217 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 2433 .

§ Dutch: SNMP-Synology Fysieke Schijf
§ French: Synology disque physique (SNMP)
§ German: SNMP Synology Physikalischer Datenträger
§ Portuguese: Disco físico Synology (SNMP)
§ Russian: Физический диск Synology п о SNMP
§ Spanish: Disco físico Synology (SNMP)
Remarks
2428
Add Sensor
Setting Description
right corner.

Setting Description
2429
Setting Description
inherited 146 .
§ snmpsynology
§ synology
§ physicaldisk
sensor settings.
Setting Description
Disk Name Shows the name of the disk that this sensor monitors.
2430
Setting Description
Model Shows the model of the physical disk that this sensor monitors.
Type Shows the type of the physical disk that this sensor monitors.
Sensor Display
Sensor Display
Setting Description

2431
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2432
Channel List
Channel Description

§ Up status 186 : Initialized, Normal
§ Warning status: NotInitialized
§ Down status: Crashed, SystemPartitionFailed

More
Knowledge Base


2433
7.8.218 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 2438 .

§ Dutch: SNMP-Synology Systeem Status
§ French: Synology état ?

du système (SNMP)
§ German: SNMP Synology Systemzustand
§ Portuguese: Funcionamento do sistema Synology (SNMP)
§ Russian: Рабо то сп о со бн о сть систем ы Synology п о SNMP
§ Spanish: Salud de sistema Synology (SNMP)
Remarks
2434
§ See the Knowledge Base: Why does my Synology System Health sensor show incorrect CPU and
memory values?
Add Sensor

Setting Description
inherited 146 .
2435
Setting Description
§ snmpsynology
§ synology
§ systemhealth
sensor settings.
Sensor Display
Sensor Display
Setting Description

2436
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2437
Access Rights
Access Rights
Channel List
Channel Description
CPU Fan Status The CPU fan status

CPU Load The CPU load in percent

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 in percent

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

2438
Channel Description
System Status The system status

More
Knowledge Base
Why does my Synology System Health sensor show incorrect CPU and memory values?



2439
7.8.219 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 2443 .

§ 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 sistema (SNMP)
Remarks
§ See the Knowledge Base: Why does the SNMP System Uptime sensor report wrong values?
2440
Add Sensor

Setting Description
inherited 146 .
§ snmpuptimesensor
2441
sensor settings.
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2442
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2443
Channel Description
System Uptime The system uptime
More
Knowledge Base
Why does the SNMP System Uptime sensor report wrong values?



2444
7.8.220 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 Traffic Sensor
List 2452 .

§ Dutch: SNMP Verkeer
§ French: Trafic (SNMP)
§ German: SNMP Datenverkehr
§ Japanese: SNMP
§ Portuguese: Tráfego (SNMP)
§ Russian: Траф ик п о SNMP
§ Spanish: Tráfico (SNMP)
Remarks
§ You can define the displayed sensor name with port name templates in the SNMP compatibility
options 571 of the parent device.
2445
§ We recommend that you select SNMP v2c (most common) or SNMP v3 in the credentials for SNMP
devices 548 of the parent device (if supported by the target device). SNMP v1 does not support 64-bit
counters, which may result in invalid data. For details, see the Knowledge Base: SNMP Traffic sensor
suddenly drops at 610Mbps
§ The auto-discovery always creates SNMP Traffic sensors for all interfaces whose SNMP traffic
269
counters are above 0. As a result, every interface that has had traffic since the last restart of the target
device is added, even if it is currently disconnected or disabled. For details, see the Knowledge Base:
§ See the Knowledge Base: SNMP Traffic sensors when the device changes them
Add Sensor
Traffic Specific
Setting Description
Interface Number Select the ports on SNMP devices with multiple interfaces that you want
to monitor. PRTG creates one sensor for each port that you select.

right corner.
You can see the connection status of an interface in the respective
table column.
You can select interfaces and cancel the selection by clicking Select
all connected interfaces, Select all disconnected interfaces, and
Deselect all interfaces.
Name for Traffic In For the standard channel Traffic In, enter the channel name here. The
Channel sensor shows it in graphs and tables. You can change this description
and the description of all other channels in the channel settings 3052 later.
Name for Traffic Out For the standard channel Traffic Out, enter the channel name here. The
and the description of all other channels in the channel settings later.
2446
Setting Description
Name for Traffic Total For the standard channel Traffic Total, enter the channel name here. The
and the description of all other channels in the channel settings later.

Setting Description
inherited 146 .
§ bandwidthsensor
§ snmptrafficsensor
2447
Setting Description
sensor settings.
Traffic Specific
Traffic Specific
2448
Setting Description
Interface Number Shows 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.
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.
§ 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 186 with the message
Channels not available, you can disable the affected channels to
remove the warning.
Connection Status Define how PRTG reacts when an interface is operational. An interface
Handling that is not operational is, for example, an Ethernet port on a switch with
no cable plugged in. This setting is valid for all selected interfaces.
Choose between:
§ 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 2449
in the Up status when the interface has been deactivated.
§ Ignore all disconnected states: 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).
Inherited Settings
2450
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2451
Channel List
Channel Description
Discards In The number of incoming discards per second
Discards Out The number of outgoing discards per second
Non-Unicast In The number of incoming non-unicast packets per second
Non-Unicast Out The number of outgoing non-unicast packets per second
Traffic Total The total traffic in bytes per second

2452
Channel Description
Unicast In The number of incoming unicast packets per second
Unit The number of outgoing unicast packets per second
Unknown Protocols In The number of incoming, unknown protocols per second
More
Knowledge Base




SNMP Traffic sensor suddenly drops at 610Mbps



2453
7.8.221 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 2463 .

§ 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
§ This sensor does not support SNMP v3 traps. Use SNMP v1 or v2c instead.
§ This sensor only supports the User Datagram Protocol (UDP).
2454
§ Add this sensor to the probe device to receive all messages of the remote probe system.
§ Add this sensor to a specific device to directly receive all messages from this device. This makes this
sensor faster than when you use source filters.
§ You can use specific placeholders in email notification templates 3182 to see the messages when you
receive an email notification. See section List of Placeholders for Notifications 3704 .
§ The sensor states of this sensor persist for one scanning interval only. After showing a Warning
186
status or a Down status, and if there is no warning or error message in the following scanning interval,
the sensor shows an Up status again. For a workaround, see the Knowledge Base: How can I
configure sensors using speed limits to keep the status for more than one interval?
§ With the available filter options, you can individually define which types of messages the sensor
considers for monitoring, and which messages it categorizes as warning or error messages.
Depending on the filters, received messages are counted in the respective channels.
§ If you do not add the sensor to a probe device but to a different device in PRTG, be careful with the
configuration: Ensure that the IP address or Domain Name System (DNS) name of the parent device
matches the proper sender. For example, if you want to receive messages from a storage area
network (SAN), you might need to add a device to PRTG using the IP address of a specific array
member that sends the messages. Providing a DNS name that points to the IP address of a whole
group might not work for SANs.
§ In PRTG Network Monitor, you can copy the Management Information Base (MIB) file for your traps
into the \MIB subfolder of the PRTG program directory 3579 to translate the object identifiers (OID) for
the traps into readable messages. For details, see the Knowledge Base: How can I show the name of
a received OID in PRTG?
§ See the Knowledge Base: How do I test an SNMP Trap Receiver sensor?
§ For a general introduction to the receiver's configuration, see section Monitoring Syslogs and SNMP
Traps 3390 .
Subscription 81 .
Add Sensor

2455
Setting Description
inherited 146 .
§ snmptrapsensor
SNMP Trap Specific
SNMP Trap Specific
2456
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.
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
2457
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 186 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
Setting Description
2458
Setting Description


Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2459
Maintenance Window.
Access Rights
Access Rights

2460
Debug Options
Debug Options
Setting Description
§ Store result: Store the last sensor result in the \Logs\debug subfolder of
the PRTG data directory 3579 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 3540 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 creates agent[10.0.0.1]
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"]
2461
Field Parameter Examples
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.
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,value,mode]in the specified OID. Separate the OID, the value, and the 2.31.1.0,error,exact]
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: This is the default mode that 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[number]Enter a number that specifies the generic trap type. gentrap[3], gentrap[2-6]
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[text]Enter a community string for an exact, case-sensitive community[public],

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 222 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 3172 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.
2462
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
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 2461 .
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 per second on the SNMP trap collector
port
Errors The number of messages categorized as "error" per second
Messages The overall number of received traps per second

Warnings The number of messages categorized as "warning" per second
More
Knowledge Base
2463
How can I show the name of a received OID in PRTG?
How do I test an SNMP Trap Receiver sensor?




2464
7.8.222 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 2469 .

§ 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
§ This sensor cannot distinguish the status "not installed" from "not running".
2465
Add Sensor
SNMP Windows Service Monitor
Setting Description
services Select the services that you want to monitor. PRTG creates one sensor
right corner.

Setting Description
2466
Setting Description
inherited 146 .
§ snmpservicesensor
§ servicesensor
sensor settings.
SNMP Windows Service Monitor
SNMP Window s Service Monitor
Setting Description
Service Shows the Windows service that this sensor monitors.

2467
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2468
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2469
Channel Description
Operating State The operating status of the target device
§ Up status 186 : Active

§ Down status: Continue-Pending, Pause-Pending, Paused
More
Knowledge Base



2470
7.8.223 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 2475 .

§ Dutch: SNTP
§ French: SNTP
§ German: SNTP
§ Japanese: SNTP
§ Portuguese: SNTP
§ Russian: SNTP
§ Simplified Chinese: SNTP
§ Spanish: SNTP
Remarks
2471
Add Sensor

Setting Description
inherited 146 .
§ sntpsensor
2472
sensor settings.
Sensor Specific
Sensor Specific
Setting Description
Sensor Display
Sensor Display
Setting Description

2473
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2474
Access Rights
Access Rights
Channel List
Channel Description
Difference The time difference in comparison to the local system time

More
Knowledge Base

2475
7.8.224 Soffico Orchestra Channel Health Sensor
The Soffico Orchestra Channel Health sensor monitors the state and the overall number of successful or
unsuccessful channel calls.
Soffico Orchestra Channel Health Sensor
List 2482 .

§ Dutch: Soffico Orchestra Channel Health
§ French: Soffico Orchestra Channel Health
§ German: Soffico Orchestra Channel Health
§ Japanese: Soffico Orchestra Channel Health
§ Portuguese: Soffico Orchestra Channel Health
§ Russian: Soffico Orchestra Channel Health
§ Simplified Chinese: Soffico Orchestra Channel Health
§ Spanish: Soffico Orchestra Channel Health
Remarks
§ This sensor requires a Soffico license and Orchestra 4.8.2.5 or later.
§ You can define credentials for Soffico Orchestra 565 in settings that are higher in the object

2476
Add Sensor
Orchestra Channel Specific
Setting Description
Channel Name Select the Orchestra channels that you want to monitor. PRTG creates
one sensor for each channel that you select.
right corner.

Setting Description
2477
Setting Description
inherited 146 .
§ orchestra
§ orchestrachannelhealth
§ soffico
sensor settings.
Setting Description
Channel Name Shows 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.
2478
Setting Description
Type Shows the type of the Orchestra channel that this sensor monitors.
The sensor supports inbound and outbound channels.
Sensor Display
Sensor Display
Setting Description

2479
Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
Scanning Interval
Scanning Interval
2480
objects' settings.
Maintenance Window.
Access Rights
Access Rights

2481
Channel List
Channel Description
Adapter State The adapter state

§ Up status 186 : Offline, Online
§ Warning status: Not Installed, Unknown
§ Down status: Online With Error
Error Count The number of errors per second
OK Count The number of OKs per second
More
Knowledge Base
2482
2483
7.8.225 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. The size of the reserved disk space can be defined with
tune2fs. For details, 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 2494 .

§ Dutch: SSH Disk vrij
§ French: Espace disponible du disque (SSH)
§ German: SSH Laufwerkskapazität
§ Japanese: SSH
§ Portuguese: Disco livre (SSH)
§ Russian: Сво бо дн о е п ро стран ство диска п о SSH
§ Simplified Chinese: SSH
§ Spanish: Espacio libre en disco (SSH)
2484
Remarks
the parent device.
Add Sensor
SSH Disk Free
Setting Description
Disk Select the disks that you want to monitor. PRTG creates two channels for
You can select up to 100 disks. If you select more disks, you cannot
create the sensor. Add the sensor multiple times to monitor more
than 100 disks with several sensors.
right corner.

2485
Setting Description
inherited 146 .
§ sshdiskfreesensor
§ diskfreesensor
sensor settings.
2486
SSH Specific
SSH Specific
Setting Description
(15 minutes).
2487
Setting Description
engine.
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 186 , 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 3052 .
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.
2488
Setting Description
the field empty.
the field empty.
2489
Setting Description
the field empty.
the field empty.
changes to the Down status. Enter an integer or leave the field empty.
2490
Setting Description
changes to the Warning status. Enter an integer or leave the field empty.
empty.
empty.

found.
2491
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2492
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2493
Channel List
Channel Description
Free Bytes [Mounted The free space in bytes

Partition]
Free Space [Mounted The free space in percent

Partition]
More
Knowledge Base
Why do SSH Disk Free and SNMP Linux Disk Free show different values for my target Linux system?

2494
How do I set up SSH sensors with my AWS Linux instances?

2495
7.8.226 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 2502 .

§ 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)
2496
Remarks
the parent device.
§ This sensor does not support ESX(i) hosts.
Add Sensor

Setting Description
inherited 146 .
2497
Setting Description
§ sshinodesfreesensor
sensor settings.
SSH Specific
SSH Specific
Setting Description
(15 minutes).
2498
Setting Description
engine.
2499
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

2500
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2501
Access Rights
Access Rights

Channel List
Channel Description
2502
Channel Description
Free INodes [Mount] The free index nodes in percent 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



2503
7.8.227 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 2510 .

§ 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
the parent device.
2504
Add Sensor

Setting Description
inherited 146 .
§ sshloadavgsensor
2505
Setting Description
sensor settings.
SSH Specific
SSH Specific
Setting Description
(15 minutes).
2506
Setting Description
engine.
2507
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2508
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2509
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
More
Knowledge Base


2510
2511
7.8.228 SSH Meminfo Sensor
The SSH Meminfo sensor monitors the memory usage of a Linux/Unix system using Secure Shell
(SSH).
SSH Meminfo Sensor
List 2518 .

§ Dutch: SSH Meminfo
§ French: Information mémoire (SSH)
§ German: SSH Speicherinfo
§ Japanese: SSH
§ Portuguese: Meminfo (SSH)
§ Russian: Meminfo п о SSH
§ Spanish: Meminfo (SSH)
Remarks
the parent device.
§ This sensor cannot support all Linux/Unix distributions.
§ This sensor does not support any macOS distributions.
2512
Add Sensor

Setting Description
inherited 146 .
§ sshmeminfosensor
§ memorysensor
2513
Setting Description
sensor settings.
SSH Specific
SSH Specific
Setting Description
(15 minutes).
2514
Setting Description
engine.
2515
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2516
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2517
Channel List
Channel Description

Memory
More
Knowledge Base


2518
2519
7.8.229 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 2526 .

§ 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
the parent device.
2520
Add Sensor

Setting Description
inherited 146 .
§ sshremotepingsensor
2521
Setting Description
§ pingsensor
§ remotepingsensor
sensor settings.
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.
2522
Setting Description
Do not use parameters that change the output format of the result to
ensure that it can still be parsed. You cannot enter an additional
command.
SSH Specific
SSH Specific
Setting Description
(15 minutes).
2523
Setting Description
engine.
master node.
2524
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2525
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2526
Channel Description
Avg Response The average response time measured from the remote device in
milliseconds (msec)
Max Response The maximum response time measured from the remote device in msec
Min Response The minimum response time measured from the remote device in msec
Packet Loss The packet loss in percent

More
Knowledge Base


2527
7.8.230 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 2535 .

§ 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
2528
the parent device.
§ This sensor does not support every SAN, even if it provides a CLI. The sensor only works with specific
devices, for example, the HPE P2000.
§ It might happen that the controller of your target device breaks down. Experience shows that this issue
strongly depends on the hardware model you monitor. Increase the scanning interval to discharge the
controller and try again.
§ After a firmware update of the target device, this sensor might show incorrect channel values. Add this
sensor anew in this case.
§ Sometimes the devices you monitor with this SSH SAN 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 on this issue, see the Knowledge Base: Why does my SSH SAN sensor show a
wrong status?
Add Sensor
SSH SAN Enclosure Settings
Setting Description
Storage Enclosure Select the storage enclosures that you want to monitor. PRTG creates
one sensor for each storage enclosure that you select.
right corner.

2529
Setting Description
inherited 146 .
§ sshsanenclosure
§ sshsan
§ enclosure
2530
Setting Description
Storage Enclosure Shows the identifier of the storage enclosure that this sensor monitors.
Durable ID Shows the durable identifier of the storage enclosure that this sensor
monitors.
Name Shows the name of the storage enclosure that this sensor monitors.
WWN Shows the World Wide Name (WWN) of the storage enclosure that this
sensor monitors.
2531
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.
2532
Setting Description
engine.
master node.
2533
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2534
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2535
Channel Description
Controller[#] The status of the controller

§ Up status: Ok
§ Down status: Fault, Not Available
Enclosure[#] The overall status of the enclosure

§ Up status: Ok
PSU[#] The status of the power supplies

§ Up status: Ok
More
Knowledge Base
Why does my SSH SAN sensor show a wrong status?

2536
7.8.231 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 2545 .

§ 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
the parent device.
2537
wrong status?
Add Sensor
SSH SAN Logical Disk Settings
Setting Description
right corner.

2538
Setting Description
inherited 146 .
§ sshsanlogicaldisk
§ sshsan
§ logicaldisk
sensor settings.
2539
SSH Specific
SSH Specific
Setting Description
2540
Setting Description
engine.
master node.
2541
Setting Description
Volume Shows the volume that this sensor monitors.

Size Shows 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 (recommended): 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
2542
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2543
Maintenance Window.
Access Rights
Access Rights

2544
Channel List
Channel Description
Health The health status of the disk

§ Up status: Ok
Total IOs The total number of input/output (I/O) operations per second
Transferred The data transferred per second
More
Knowledge Base


2545
7.8.232 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 2554 .

§ 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
the parent device.
2546
wrong status?
Add Sensor
SSH SAN Physical Disk Settings
Setting Description
right corner.

2547
Setting Description
inherited 146 .
§ sshsanphysicaldisk
§ sshsan
§ physicaldisk
sensor settings.
2548
SSH Specific
SSH Specific
Setting Description
2549
Setting Description
engine.
master node.
2550
Setting Description

Name Shows the name of the physical disk that this sensor monitors.
Size Shows 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 (recommended): 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:
2551
Setting Description
§ Request all historical data: Use this mode to possibly deliver better
data.
§ Request actual counters: Use this mode if the device does not support
Request all historical data. This mode might result in incorrect data and
spikes in graphs.
Sensor Display
Sensor Display
Setting Description

2552
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2553

Channel List
Channel Description
Health The health status of the disk

§ Up status: Ok
Total IOs The total number of input/output (I/O) operations per second
Transferred The data transferred per second
2554
More
Knowledge Base

2555
7.8.233 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 2564 .

§ Dutch: SSH SAN systeemstatus
§ French: SAN état du système (SSH)
§ German: SSH SAN Systemzustand
§ Portuguese: Funcionamento do sistema SAN (SSH)
§ Russian: Рабо то сп о со бн о сть систем ы SAN п о SSH
§ Spanish: Salud de sistema SAN (SSH)
2556
Remarks
the parent device.
wrong status?
Add Sensor
SSH SAN Specific
Setting Description
Metrics Select the metrics that you want to monitor. PRTG creates one sensor for
each metric that you select.
right corner.

2557
Setting Description
inherited 146 .
§ sshsansystemhealth
§ sshsan
§ systemhealth
sensor settings.
2558
SSH SAN Specific
SSH SAN Specific
Setting Description
Metric Shows 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.
2559
SSH Specific
SSH Specific
Setting Description
2560
Setting Description
engine.
master node.
2561
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2562
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2563
Channel List
Channel Description
Capacitor Cell [#] Voltage The capacitor cell voltage in volts (V)
[Controller]
Capacitor Cell [#] Voltage The capacitor cell voltage status

[Controller] Status
§ Up status 186 : Ok
§ Down status: Error, Unavailable, Unknown, Unrecoverable
§ Unknown status: Not Installed, Unsupported
Capacitor Pack Voltage The capacitor pack voltage in V

[Controller]
Capacitor Pack Voltage The capacitor pack voltage status

[Controller] Status
§ Up status: Ok
2564
Channel Description
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
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
2565
More
Knowledge Base

2566
7.8.234 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 2576 .

§ Dutch: SSH Script
§ French: Script (SSH)
§ German: SSH-Skript
§ Japanese: SSH
§ Portuguese: Script (SSH)
§ Russian: Скрип т SSH
§ Spanish: Script (SSH)
Remarks
§ For security reasons, you must 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).
2567
the parent device.
§ For details about the return value format, see section Custom Sensors 3498 .
Add Sensor
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/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 186 , 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 an example script, see the Knowledge Base: Is there a shell

script example for the SSH Script sensor?
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.
Channel Name Enter a name for the channel. Enter a string. This is for display purposes
only.
2568
Setting Description
sensor.

Setting Description
inherited 146 .
§ sshscript
2569
Setting Description
Sensor Settings
Sensor Settings
Setting Description
Script Shows the name of the script that the sensor executes with each
scanning interval.
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.
You must escape special characters and whitespaces in your
details.
2570
Setting Description
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.
sensor settings?
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.
Value Type Shows the expected type of the returned value.


2571
SSH Specific
SSH Specific
Setting Description
2572
Setting Description
engine.
master node.
Sensor Display
Sensor Display
2573
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2574
Maintenance Window.
Access Rights
Access Rights

2575




-name pub\"lic
-name "pu'b\"lic"
Channel List
Channel Description

[Value] The value that the script file returns in one channel
Sensors 3498 .
2576
More
Knowledge Base

Is there a shell script example for the SSH Script sensor?



2577
7.8.235 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 2586 .

§ Dutch: SSH Script Geavanceerd
§ French: Script (SSH) avancé
§ German: SSH-Skript (Erweitert)
§ Japanese: SSH
§ Portuguese: Script (avançado) (SSH)
§ Russian: Расш ирен н ы й скрип т SSH

§ Spanish: Script (avanzado) (SSH)
Remarks
§ For security reasons, you must store the script file in the /var/prtg/scriptsxml directory on the target
system. Make sure that the script has executable rights.
2578
the parent device.
§ For details about the return value format, see section Custom Sensors 3499 .
Add Sensor
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 186 , 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.

2579
Setting Description
inherited 146 .
§ sshscript
Sensor Settings
Sensor Settings
Setting Description
Script Shows the script that the sensor executes with each scanning interval.
2580
Setting Description
Parameters If your script file catches command-line parameters, you can define them
here. You can use also placeholders. Enter a string or leave the field
empty.
You must escape special characters and whitespaces in your
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.
sensor settings?
SSH Specific
SSH Specific
2581
Setting Description
engine.
2582
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

2583
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2584
Access Rights
Access Rights



2585


-name pub\"lic
-name "pu'b\"lic"
Channel List
Channel Description
[Value] The values that the script file returns in several channels
Sensors 3499 .
More
Knowledge Base



2586
2587
7.8.236 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 2595 .

§ Dutch: SSL Certificaat
§ French: SSL certificat
§ German: SSL-Zertifikat
§ Japanese: SSL
§ Portuguese: Certificado SSL
§ Russian: Сертиф икат SSL
§ Simplified Chinese: SSL
§ Spanish: Certificado SSL
2588
Remarks
§ Enter the Domain Name System (DNS) name in the settings of the parent device 535 exactly as it is
written in your certificate. You can also use wildcards 2595 .
§ 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?
This sensor supersedes the deprecated HTTP Certificate Expiry sensor.
Add Sensor

Setting Description
2589
Setting Description
inherited 146 .
§ sslcertificate
§ ssl
§ certificate
Timeout (Sec.) Enter a timeout in seconds for the TCP read request. Enter an integer.
The maximum timeout value is 300 seconds (5 minutes).
sensor settings.
SSL Certificate Specific
SSL Certificate Specific
2590
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 186 .
§ 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.
Connection Specific
Connection Specific
2591
Setting Description
SOCKS Proxy (v5 only) Define if the sensor uses a SOCKS proxy server for the sensor
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 username.
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.
Debug Options
Debug Options
Setting Description
2592
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 logfile 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

2593
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2594
Access Rights
Access Rights
Using Wildcards
You can use wildcards in the IP Address/DNS Name in the device settings 535 . 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
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
2595
Channel Description
Common Name Check If the common name or subject-alternative names match the host address
or Server Name Indication (SNI) (if certificate name validation is enabled)
§ 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
Public Key Length The public key length

§ Up status 186 :
ú RSA keys: For 2048-bit keys (good security) and longer (perfect
security)
ú Elliptic Curve Cryptography (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
2596
More
Knowledge Base
How can I configure the WinHTTP proxy settings for the SSL Certificate sensor?
2597
7.8.237 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 2603 .

§ 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
Remarks
§ This sensor only checks accepted protocols, it does not consider the used ciphers.
2598
§ See the Knowledge Base: How do you determine the protocol security ratings of the SSL Security
Check sensor?
Add Sensor

Setting Description
inherited 146 .
2599
Setting Description
§ sslsensor
sensor settings.
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).
2600
Connection Specific
Connection Specific
Setting Description
SOCKS Proxy (v5 only) Define if the sensor uses a SOCKS proxy server for the sensor
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 username.
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
2601
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2602
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Security Rating The security of the connection to the defined port

§ Up status 186 : Only Strong Protocols Available
§ Warning status: Weak Protocols Available
§ Down status: No Secure Protocol Available
SSL 2.0 (Deprecated) No longer available
2603
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

§ Up status: Accepted
§ Unknown status: Denied
More
Knowledge Base

How do you determine the protocol security ratings of the SSL Security Check sensor?
2604
7.8.238 Syslog Receiver Sensor
The Syslog Receiver sensor receives and analyzes Syslog messages.
Syslog Receiver Sensor
List 2614 .

§ Dutch: Syslog ontvanger
§ French: Récepteur Syslog
§ German: Syslog-Empfänger
§ Japanese: Syslog
§ Portuguese: Receptor de Syslog
§ Russian: П рием н ик Syslog
§ Spanish: Receptor de Syslog
Remarks
§ This sensor only supports the User Datagram Protocol (UDP).
2605
§ If you do not add the sensor to a probe device but to a different device in PRTG, be careful with the
configuration: Ensure that the IP address or Domain Name System (DNS) name of the parent device
matches the proper sender. For example, if you want to receive messages from a storage area
network (SAN), you might need to add a device to PRTG using the IP address of a specific array
member that sends the messages. Providing a DNS name that points to the IP address of a whole
group might not work for SANs.
§ With the available filter options, you can individually define which types of messages the sensor
considers for monitoring, and which messages it categorizes as warning or error messages.
Depending on the filters, received messages are counted in the respective channels.
§ Add this sensor to the probe device to receive all messages of the remote probe system.
§ Add this sensor to a specific device to directly receive all messages from this device. This makes this
sensor faster than when you use source filters.
§ For a general introduction to the receiver's configuration, see section Monitoring Syslogs and SNMP
Traps 3390 .
§ You can use specific placeholders in email notification templates 3182 to see the messages when you
receive an email notification. See section List of Placeholders for Notifications 3704 .
§ The sensor states 186 of this sensor persist for one scanning interval only. After showing a Warning
status or a Down status, and if there is no warning or error message in the following scanning interval,
the sensor shows an Up status again. For a workaround, see the Knowledge Base: How can I
configure sensors using speed limits to keep the status for more than one interval?
Add Sensor

2606
Setting Description
inherited 146 .
§ syslogsensor
sensor settings.
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.
2607
Setting Description
Purge Messages After Define how long PRTG stores received Syslog messages for analysis.
Select a period of time from the dropdown list.
Filter
Filter
2608
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
as the scanning interval is running, the sensor does not change its
status. By default, the sensor changes to the Warning status 186 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
2609
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2610
Maintenance Window.
Access Rights
Access Rights

2611
Debug Options
Debug Options
Setting Description
§ Store result: Store the last sensor result in the \Logs\debug subfolder of
the PRTG data directory 3579 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 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]
2612
Field Parameter Example
hostname[text] Enter any string that specifies the hostname of a device§ hostname[www.example.c
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 case
insensitive.)
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 222 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 3172 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.
2613
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 2612 .
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 per second on the syslog port
Errors The number of messages categorized as "error" per second
Messages The number of received Syslog messages per second

Warnings The number of messages categorized as "warning" per second
More
Knowledge Base

VIDEO TUTORIAL
SNMP Trap receiver and syslog receiver sensors

§ https://www.paessler.com/support/videos-and-webinars/videos/syslog-receiver
2614
7.8.239 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 2619 .

§ Dutch: System Status
§ French: État du système
§ German: Systemzustand
§ Japanese:
§ Portuguese: Funcionamento do sistema
§ Russian: Рабо то сп о со бн о сть систем ы
§ Spanish: Salud de sistema
2615
Remarks

Setting Description
inherited 146 .
§ systemhealthsensor
2616
sensor settings.
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2617
Scanning Interval
Scanning Interval
Access Rights
Access Rights

2618
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.
CPU Load The CPU load in percent on the probe system with a predefined upper
warning limit (50 %) and upper error limit (90 %). Extensive CPU load can
lead to false, incomplete, and incorrect monitoring results. This value
should usually stay below 50%.
Health The sum of the system status as a value between 100% (healthy) and 0%
More
Knowledge Base

2619
7.8.240 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 2625 .

§ Dutch: TFTP
§ French: TFTP
§ German: TFTP
§ Japanese: TFTP
§ Portuguese: TFTP
§ Russian: TFTP
§ Simplified Chinese: TFTP
§ Spanish: TFTP
Remarks
2620
Add Sensor

Setting Description
inherited 146 .
§ trivialftpsensor
2621
sensor settings.
Sensor Specific
Sensor Specific
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 186 . Enter a
string.
Sensor Display
Sensor Display
2622
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2623
Maintenance Window.
Access Rights
Access Rights

2624
Channel List
Channel Description
Available The response time in msec

More
Knowledge Base

2625
7.8.241 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 186 .
Traceroute Hop Count Sensor
List 2631 .

§ Dutch: Traceroute Hop Count
§ French: Compteur de Hop Traceroute
§ German: Traceroute Hop-Anzahl
§ Japanese: Traceroute
§ Portuguese: Contagem de hops em traceroute
§ Russian: Ко л-во п ерехо до в трассиро вки м арш рута
§ Spanish: Recuento de saltos traceroute
Remarks
2626
does PRTG require?
Add Sensor

Setting Description
2627
Setting Description
inherited 146 .
§ ptfsensor
Sensor Settings
Sensor Settings
Setting Description
If Route Changes Define what to do if the route has changed since the last check:
§ Ignore: Do not perform any action.
§ Set sensor to warning status: Show the Warning status 186 if the route
changes.
§ Set sensor to down status: Show the Down status if the route changes.
2628
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
2629
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2630
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Hops The number of hops

More
Knowledge Base
2631

2632
7.8.242 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 2638 .

§ Dutch: Veeam Backup Job Status
§ French: Veeam Backup Job Status
§ German: Veeam Backup Job Status
§ Japanese: Veeam Backup Job Status
§ Portuguese: Veeam Backup Job Status
§ Russian: Veeam Backup Job Status
§ Simplified Chinese: Veeam Backup Job Status
§ Spanish: Veeam Backup Job Status
Remarks
§ This sensor requires credentials for Veeam 569 in settings that are higher in the object hierarchy 140 , for
2633
§ This sensor requires an installation of the Veeam Backup Enterprise Manager 10 or 11 with the
Enterprise Plus license.
§ This sensor does not support the following backup job types: Tape, Sure Backup, NAS Backup Copy,
and Agent Backup Copy.
§ This sensor does not support Veeam Agent Backup Jobs if they are managed by a Veeam Agent.
§ This sensor only supports version 1.5 of the Representational State Transfer (REST) application
Add Sensor

Setting Description
inherited 146 .
2634
Setting Description
§ veeam
§ veeambackup
§ veeamenterprisemanager
sensor settings.
Sensor Display
Sensor Display
Setting Description
2635
Setting Description

Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
2636
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2637
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

The Job Runs Finished channel shows the total number of all job runs
in a warning state, successful job runs, and failed job runs.
Job Runs Running The number of running job runs
Job Runs Successful The number of successful job runs
2638
Channel Description
Job Runs Warning The number of job runs in a warning state
Jobs Scheduled The number of scheduled backup jobs
More
Knowledge Base

2639
7.8.243 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 2646 .

§ Dutch: Veeam Backup Job Status Advanced
§ French: Veeam Backup Job Status Advanced
§ German: Veeam Backup Job Status Advanced
§ Japanese: Veeam Backup Job Status Advanced
§ Portuguese: Veeam Backup Job Status Advanced
§ Russian: Veeam Backup Job Status Advanced
§ Simplified Chinese: Veeam Backup Job Status Advanced
§ Spanish: Veeam Backup Job Status Advanced
Remarks
§ This sensor requires credentials for Veeam 569 in settings that are higher in the object hierarchy 140 , for
2640
§ This sensor requires an installation of the Veeam Backup Enterprise Manager 10 or 11 with the
Enterprise Plus license.
§ This sensor does not support the following backup job types: Tape, Sure Backup, NAS Backup Copy,
and Agent Backup Copy.
§ This sensor does not support Veeam Agent Backup Jobs if they are managed by a Veeam Agent.
§ This sensor only supports version 1.5 of the Representational State Transfer (REST) application
§ See the Knowledge Base: How can I change the status of my Veeam sensors based on whether a job
is scheduled or not?
Add Sensor
Veeam Specific
Setting Description
Backup Jobs You see a list of all backup jobs that are available on the Veeam Backup
Enterprise Manager. The backup jobs are listed by job name, job type,
platform, and job description.

right corner.

2641
Setting Description
inherited 146 .
§ veeam
§ veeambackup
§ veeamenterprisemanager
2642
Veeam Specific
Veeam Specific
Setting Description
Job Name Shows the name of the backup job that this sensor monitors.
Job Type Shows the type of backup job that this sensor monitors.
Platform Shows the platform on which the backup job runs.
Job Description Shows the description of the backup job that this sensor monitors.
Sensor Display
Sensor Display
Setting Description
2643
Setting Description

Debug Options
Debug Options
Setting Description
master node.
Inherited Settings
2644
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2645
Channel List
Channel Description
Duration The duration of the backup job run in seconds
Job Scheduled If the backup job is scheduled

§ Up status: No, Yes. Which status the sensor actually shows depends
on the lookup file 3541 that you choose in the channel settings.
For more information, see the Knowledge Base: How can I change
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
2646
Channel Description
Last Result The status of the last backup job run

§ Up status: Successful
§ Unknown status: None
Status The overall status of the backup job run

§ Up status: Starting, Working, Stopped
§ 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?
2647
7.8.244 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 2654 .

§ 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
§ The parent device must be a VMware ESXi server version 5.2 or later or vCenter.
§ This sensor requires credentials for VMware/XenServer 547 in the settings of the parent device. Ensure
that you enter a user with sufficient access rights to obtain statistics (read-only usually works).
2648
§ See the Knowledge Base: I cannot add VMware sensors because of "wrong" password although it is
correct. What can I do?
§ See the Knowledge Base: Why are my VMware sensors not working after upgrading to VCSA 6.5 U1?
This sensor supersedes the outdated SSH VMWare ESX(i) Disk sensor. We recommend that you
use this new VMware Datastore (SOAP) sensor to monitor VMware datastores.
does PRTG require?
Settings on VMware Host System

If you set up this sensor on different probes (for example, when using remote probes 3557 or when running
a failover cluster 137 ), 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 details about this setting, see the Knowledge Base: How can I increase the connection limit on
VMware systems? PE121.
Add Sensor
2649
Datastore Settings
Setting Description
Datastores Select the datastores that you want to monitor. PRTG creates one sensor
for each datastore that you select.
right corner.

Setting Description
inherited 146 .
2650
Setting Description
§ vmwaredatastoreexternsensor
sensor settings.
Datastore Settings
Datastore Settings
Setting Description
Managed Object Identifier Shows the managed object identifier (MOID) of the datastore that this
(MOID) sensor monitors.
scanning interval.
master node.
2651
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2652
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2653
Channel List
Channel Description
Accessible The accessibility of the datastore

§ Up status: Yes
§ Down status: No
Available Capacity The available capacity in bytes (the physically or virtually available size of
the datastore)
Free Bytes The free space in bytes (the disk space that is not used by virtual
machines (VM). Used disk space can be either thick-provisioned or used
by thin-provisioned virtual disks)
Free Space The free space in percent (the disk space that is not used by VMs. Used
disk space can be either thick-provisioned or used by thin-provisioned
virtual disks)
2654
Channel Description
Total Provisioned The total provisioned disk space in percent (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?



Monitoring VMware ESXi 5.5 does not work. What can I do?
2655
7.8.245 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 2661 .

§ 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
§ This sensor requires that the CIM interface is enabled on the ESXi host. On ESXi 6.5 and later, you
2657
must manually enable CIM.

the parent device.
2656
§ The parent device must be a VMware ESXi server version 5.2 or later.
Enabled CIM Interface on To access the ESXi host and retrieve monitoring data via WBEM, the CIM
ESXi Host interface must be enabled on the ESXi host. On ESXi 6.5, CIM is disabled
by default, so you need to manually activate it.
For details, see the Knowledge Base: How do I enable the CIM
interface on VMware ESXi 6.5?
Add Sensor
ESXi Server Elements
Setting Description
Hardware Elements Select the hardware elements that you want to monitor. PRTG creates
one sensor for each element that you select.
right corner.

2657
Setting Description
inherited 146 .
§ esxshealthsensor
2658
Setting Description
Hardware Element Shows the hardware element that this sensor monitors.
Automatic Sensor Status Define if the sensor changes its status 186 depending on the health status
reading:
§ Set sensor to warning or down status: 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.
2659
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2660
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2661
Channel Description
Current The current in milliampere (mA)
Healthstate The health status

§ Up status 186 : OK Unknown
§ Warning status: Degraded, Minor
§ Down status: Critical, Major, Non Recoverable Error
Power The average host power usage in watts
Rotational Speed The fan revolutions per minute (RPM)
More
Knowledge Base
How do I enable the CIM interface on VMware ESXi 6.5?

2662
7.8.246 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 2669 .

§ 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)
§ Russian: Со сто ян ие ап п аратн ы х средств узла VMware (SOAP)

§ Spanish: Estado de hardware host VMware (SOAP)
Remarks
2663
§ The parent device must be a VMware ESXi server version 5.2 or later. 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.
§ This sensor only shows items that report an actual status, so you might see more "sensors" in your
vSphere client than the number of states available in the channels of this sensor
does PRTG require?

Add Sensor
VMware Host Settings
2664
Setting Description
Host Servers Select the host servers that you want to monitor. PRTG creates one
sensor for each host server that you select.
right corner.

Setting Description
inherited 146 .
2665
Setting Description
§ esxserverhosthealthsensor
sensor settings.
VMw are Host Settings
Setting Description
Managed Object Identifier Shows 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 186 .
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.
2666
Setting Description
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
2667
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2668
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Alert States The total number of items in the alert status as the vSphere client reports
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
2669
Channel Description
Warning States The total number of items in the warning status as the vSphere client
reports
More
Knowledge Base



2670
7.8.247 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 2677 .

§ Dutch: VMware Host Prestaties (SOAP)
§ French: VMware performances du serveur hôte (SOAP)
§ German: VMware Hostserver Leistung (SOAP)

§ Portuguese: Performance do host VMware (SOAP)
§ Russian: Рабо та узла VMware (SOAP)

§ Spanish: Rendimiento de host VMware (SOAP)
2671
Remarks
§ The parent device must be a VMware ESXi server version 5.2 or later. 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.
does PRTG require?

Add Sensor
2672
Setting Description
inherited 146 .
§ esxserverhostsensor
2673
VMw are Host Settings
Setting Description
Managed Object Identifier Shows the managed object identifier of the host that this sensor monitors.
(MOID)
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
2674
Setting Description


Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2675
Maintenance Window.
Access Rights
Access Rights

2676
Channel List
Channel Description
CPU Ready (Percent) The CPU readiness in percent

Datastore Total The datastore total read latency in milliseconds (msec)

ReadLatency
Datastore Total The datastore total write latency in msec

WriteLatency
Disk Usage The disk usage per second
Disk.DeviceLatency The disk device latency in msec
Disk.KernelLatency The disk kernel latency in msec
Memory Active The active memory in bytes
Memory Consumed The consumed memory in bytes
Memory Consumed The memory consumed in percent

(Percent)
Memory Swap Used The used memory swap
Network Received The received bytes per second
Network Transmitted The transmitted bytes per second
2677
Channel Description
Network Usage The total network usage in bytes per second
More
Knowledge Base



2678
7.8.248 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 2685 .

§ Dutch: VMware Virtuele Machine (SOAP)
§ French: VMware machine virtuelle (SOAP)
§ German: VMware Virtual Machine (SOAP)

§ Portuguese: Máquina virtual VMware (SOAP)
§ Russian: Виртуальн ая м аш ин а VMware (SOAP)

§ Spanish: Máquina virtual VMware (SOAP)
2679
Remarks
§ 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 version
5.2 or later.
§ For VMware virtual machines, disk usage channels are only available as of virtual hardware version 8.
does PRTG require?

Add Sensor
2680
PRTG requests a full list of all VMs configured on the target device. Because of this, it might take a
few seconds before the dialog appears.
VMware Virtual Machine Settings
Setting Description
Virtual Machines You see a list of all VMs available on the host server on this device,
including the ones that do not run. PRTG lists all VMs by name and the
operating system that they run on. Select the VMs that you want to
monitor. PRTG creates one sensor for each VM that you select.

Setting Description
inherited 146 .
2681
Setting Description
§ esxservervmsensor
VMware Virtual Machine Settings
VMw are Virtual Machine Settings
Setting Description
Managed Object Identifier Shows the managed object identifier (MOID) of the VM that this sensor
(MOID) monitors.
Powered-Off VM Handling Define how the sensor reacts to VMs that are powered off:
§ Alarm when VM is powered off (default): Change to the Down status 186
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.
2682
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

2683
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2684

Channel List
Channel Description
CPU Ready (Percent) The CPU readiness in percent

Datastore Total Read The datastore total read latency in milliseconds (msec)
Latency
Datastore Total Write The datastore total write latency in msec

Latency
2685
Channel Description
Disk Usage The disk usage per second
Memory Active The active memory in bytes
Memory Consumed The consumed memory in bytes
Memory Consumed The memory consumed in percent

(Percent)
Network Received The received bytes per second
Network Transmitted The transmitted bytes per second
Network Usage The total network usage in bytes per second
More
Knowledge Base



2686
2687
7.8.249 Windows CPU Load Sensor
The Windows CPU Load sensor monitors the CPU load on a computer via Windows Management
Window s CPU Load Sensor
List 2694 .

§ Dutch: Windows Processor Belasting
§ French: Windows charge CPU
§ German: Windows Prozessorlast
§ Japanese: Windows CPU
§ Portuguese: Carga de CPU Windows
§ Russian: Загрузка ЦП Windows
§ Simplified Chinese: Windows CPU
§ Spanish: Carga de CPU Windows
Remarks
2688
§ This sensor requires WoW64 (Windows 32-bit on Windows 64-bit) for target systems that run
Windows Server 2016.
query data.
still work.

2689
Add Sensor

Setting Description
inherited 146 .
2690
Setting Description
§ cpuloadsensor
§ wmicpuloadsensor
sensor settings.
Debug Options
Debug Options
Setting Description
master node.
Alternative WMI Query
2691
Setting Description
Query Method Select the method that the sensor uses to query via WMI:
§ Use the default WMI query method: 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

2692
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2693

Channel List
Channel Description
Processor [#] The CPU load of the processor in percent
Total The total CPU load in percent

More
Knowledge Base
2694
My Windows sensors do not work when using direct performance counter access. What can I do?
2695
7.8.250 Windows IIS 6.0 SMTP Received Sensor
The Windows IIS 6.0 SMTP Received sensor monitors the number of received emails for a Microsoft
Internet Information Services (IIS) 6.0 Simple Mail Transfer Protocol (SMTP) service (Exchange 2003) via
Windows Management Instrumentation (WMI) or Windows performance counters, as configured in the
Windows Compatibility Options 569 of the parent device.
List 2703 .

§ Dutch: Windows IIS 6.0 SMTP Ontvangen
§ French: Windows IIS 6.0 SMTP reçu
§ German: Windows IIS 6.0 SMTP Empfangen
§ Japanese: Windows IIS 6.0 SMTP
§ Portuguese: Recebido Windows IIS 6.0 SMTP
§ Russian: П о лучен о п акето в Windows IIS 6.0 SMTP
§ Simplified Chinese: Windows IIS 6.0 SMTP

§ Spanish: Recibidos Windows IIS 6.0 SMTP
Remarks
query data.
§ This service is not used by Exchange Server 2007 and higher. Exchange Server 2007 uses its own
SMTP stack implemented in the Microsoft Exchange Transport service.
2696
still work.

Add Sensor
2697
Setting Description
inherited 146 .
§ wmiiissmtpreceivedsensor
2698
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
2699
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2700
Setting Description
§ None
§ Saturdays
§ Sundays
§ Weekdays
§ Weekends

below.
past.
2701
Setting Description
can choose from:

object will depend.
an integer.
2702
Access Rights
Access Rights

Channel List
Channel Description
2703
Channel Description
Message Bytes Received The number of bytes in received messages
Messages Received The number of received messages

More
Knowledge Base

2704
7.8.251 Windows IIS 6.0 SMTP Sent Sensor
The Windows IIS 6.0 SMTP Sent sensor monitors the number of sent emails for a Microsoft Internet
Information Services (IIS) 6.0 Simple Mail Transfer Protocol (SMTP) service (Exchange 2003) via
List 2712 .

§ Dutch: Windows IIS 6.0 SMTP Verzonden
§ French: Windows IIS 6.0 SMTP envoyé
§ German: Windows IIS 6.0 SMTP Versendet
§ Japanese: Windows IIS 6.0 SMTP
§ Portuguese: Enviado Windows IIS 6.0 SMTP
§ Russian: О тп равлен о п акето в Windows IIS 6.0 SMTP
§ Simplified Chinese: Windows IIS 6.0 SMTP

§ Spanish: Enviados Windows IIS 6.0 SMTP
Remarks
query data.
§ This service is not used by Exchange Server 2007 and higher. Exchange Server 2007 uses its own
SMTP stack implemented in the Microsoft Exchange Transport service.
2705
still work.

Add Sensor
2706
Setting Description
inherited 146 .
§ wmiiissmtpsentsensor
2707
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
2708
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2709
Setting Description
§ None
§ Saturdays
§ Sundays
§ Weekdays
§ Weekends

below.
past.
2710
Setting Description
can choose from:

object will depend.
an integer.
2711
Access Rights
Access Rights

Channel List
Channel Description
2712
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
More
Knowledge Base

2713
7.8.252 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 2720 .

§ 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
2714
§ Spanish: Aplicación IIS Windows
Remarks
§ The sensor cannot return data for the channels Status, Uptime, and Total when using performance
counters. We recommend that you use WMI only (recommended) as Preferred Data Source in the
Add Sensor
Windows Internet Information Services
Setting Description
Instances Select the instances that you want to monitor. PRTG creates one sensor
for each instance that you select.

right corner.

2715
Setting Description
inherited 146 .
§ wmiiis
sensor settings.
2716
Windows Internet Information Services
Window s Internet Information Services
Setting Description
Instance Shows the unique instance name of the web service that this sensor
monitors.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
2717
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2718
Maintenance Window.
Access Rights
Access Rights

2719
Channel List
Channel Description
Anonymous Users The number of anonymous users per second

CGI Requests The number of Common Gateway Interface (CGI) requests per second
Files Received The number of files received per second
Files Sent The number of files sent per second
Get Requests The number of GET requests per second
Known Users The number of known users per second
Not Found Errors The number of not found errors per second
Post Requests The number of POST requests per second
Status The status of the web service

§ Up status 186 : Running
§ Down status: Stopped
Total The total in bytes per second
Uptime The uptime of the web service
More
Knowledge Base
2720
2721
7.8.253 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 2728 .

§ 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
§ This sensor requires that the Microsoft Message Queuing (MSMQ) service runs on both the probe
2723
system and the target system.

2722
§ See the Knowledge Base: How do I activate Message Queuing in my Windows installation?
does PRTG require?
correctly connect.
MSMQ service For this sensor to work, the MSMQ service must be started both on the
target system and on the probe system. Additionally, the MSMQ service
must also be started on the target computer.
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 details, see the Knowledge Base: How do I activate Message

Queuing in my Windows installation?
2723
Add Sensor
Sensor Settings
Setting Description
Message Queues Select the message queues that you want to monitor. PRTG creates one
sensor for each message queue that you select.
If no message queues are available, you see a corresponding
message.
This sensor cannot monitor subqueues.
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.

Setting Description
2724
Setting Description
inherited 146 .
§ ptfsensor
Sensor Settings
Sensor Settings
Setting Description
Message Queue Shows the name of the message queue that this sensor monitors.
Message Queue Type Shows the type of the message queue that this sensor monitors.
2725
Setting Description
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.

Debug Options
Debug Options
Setting Description
scanning interval.
master node.
2726
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2727
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2728
Channel Description
Messages The total number of messages in the queue

More
Knowledge Base
How do I activate Message Queuing in my Windows installation?



2729
7.8.254 Windows Network Card Sensor
The Windows Network Card sensor monitors the bandwidth usage and traffic of a network interface via
Window s Netw ork Card Sensor
List 2737 .

§ Dutch: Windows Netwerkkaart
§ French: Windows carte réseau
§ German: Windows Netzwerkadapter
§ Japanese: Windows
§ Portuguese: Adaptador de rede Windows
§ Russian: Сетево й адап тер Windows
§ Simplified Chinese: Windows
2730
§ Spanish: Tarjeta de red Windows
Remarks
§ This sensor requires 2731 Windows Server 2008 R2 or later on the probe system to work with Windows
performance counters.
§ This sensor requires that the Windows Remote Registry service runs on the target computer.
§ This sensor requires Windows Server 2008 R2 or later or Windows 7 or later 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.
query data.
§ This sensor supports teamed network adapters ("network interface card (NIC) teaming") on Windows
Server 2012.
still work.
2731

Add Sensor
Sensor Specific
Setting Description
Network Cards Select the network cards that you want to monitor. PRTG creates one
sensor for each network card that you select.
right corner.

2732
Setting Description
inherited 146 .
§ bandwidthsensor
§ wmibandwidthsensor
Sensor Specific
Sensor Specific
2733
Setting Description
Network Card Shows the name of the network card that this sensor monitors.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description
2734
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).
Inherited Settings
Scanning Interval
Scanning Interval
2735
objects' settings.
Maintenance Window.
Access Rights
Access Rights

2736
Channel List
Channel Description
Discards In The number of incoming discards per second
Discards Out The number of outgoing discards per second
Non-Unicast In The number of incoming non-unicast packets per second
Non-Unicast Out The number of outgoing non-unicast packets per second
Packets The number of packets in total
2737
Channel Description

Unicast In The number of incoming unicast packets per second
Unicast Out The number of outgoing unicast packets per second
Unknown Protocols In The number of unknown protocols per second
More
Knowledge Base

2738
7.8.255 Windows Pagefile Sensor
The Windows Pagefile sensor monitors the Windows pagefile usage via Windows Management
Window s Pagefile Sensor
List 2744 .

§ 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
2739
§ This sensor does not work with Windows 2000 because the respective WMI class does not exist on
this operating system.
query data.
still work.

2740
Add Sensor

Setting Description
inherited 146 .
2741
Setting Description
§ pagefilesensor
§ wmipagefilesensor
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
2742
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2743
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Total The total pagefile usage in percent

More
Knowledge Base

2744
2745
7.8.256 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 569 of the parent device.
Window s Physical Disk I/O Sensor
List 2753 .

§ 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
2746
§ Simplified Chinese: Windows I/O
§ Spanish: E/S de disco físico Windows
Remarks
query data.
still work.
2747

Add Sensor
Windows Physical Disk Specific
Setting Description
right corner.

2748
Setting Description
inherited 146 .
§ wmiphysicaldisksensor
Windows Physical Disk Specific
Window s Physical Disk Specific
2749
Setting Description

Debug Options
Debug Options
Setting Description
scanning interval.
PRTG only stores the result of this sensor if you select WMI only
(recommended) as Preferred Data Source in the Windows
Compatibility Options 569 of the parent device.
master node.
Sensor Display
Sensor Display
2750
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2751
Maintenance Window.
Access Rights
Access Rights

2752
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 in milliseconds (msec)
Avg Transfer Time The average transfer time in msec
Avg Write Queue The average number of items in the write queue
Avg Write Time The average write time in msec
Current Queue The current number of items in the queue
Disk IOs The number of disk input/output (I/O) operations per second
Disk Read IOs The number of disk read I/O operations per second
Disk Read Time % The disk read time in percent

Disk Time % The disk time in percent
Disk Transfer The disk transfer speed in bytes per second
Disk Write IOs The number of disk write I/O operations per second
2753
Channel Description
Disk Write Time % The disk write time in percent
Idle Time % The idle time in percent
Split IOs The number of split I/O operations per second
More
Knowledge Base

2754
7.8.257 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 2757 for available parameters.
Window s Print Queue Sensor
List 2764 .

§ 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
2755
Remarks
§ This sensor requires 2756 that the Print Spooler Windows service runs on the target device and the
probe system.
§ You can add a change trigger 3182 to this sensor to get a notification when the number of jobs in the
queue changes.
does PRTG require?
correctly connect.
Print Spooler Windows For this sensor to work, the Print Spooler Windows service must be
service started on the target computer and the probe system.
2756
Add Sensor
Sensor Settings
Setting Description
Print Queues 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.
right corner.

Setting Description
2757
Setting Description
inherited 146 .
§ ptfsensor
sensor settings.
Sensor Settings
Sensor Settings
Setting Description
Print Queue Shows the name of the task whose print queue this sensor monitors.
2758
Setting Description
Advanced Status Options You can optionally define specific sensor states 186 for several return
messages of the printer that this sensor monitors. Choose between:
§ Do not define sensor states for specific return messages: Do not define
sensor states for specific return messages.
§ 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 available if you select the Define sensor states for
specific return messages above. For each problem that the printer reports,
you can define the status that the sensor shows. Choose between:
§ Ignore: 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 available if you select the Define sensor states for
Needs User Intervention This setting is only available if you select the Define sensor states for
Offline This setting is only available if you select the Define sensor states for
2759
Setting Description
Out of Memory This setting is only available if you select the Define sensor states for
Out of Paper This setting is only available if you select the Define sensor states for
Paper Jammed This setting is only available if you select the Define sensor states for
Paper Problem This setting is only available if you select the Define sensor states for
Paused This setting is only available if you select the Define sensor states for
Printer Error This setting is only available if you select the Define sensor states for
2760
Setting Description
Printer Not Available This setting is only available if you select the Define sensor states for
Toner Low This setting is only available if you select the Define sensor states for
Toner Out This setting is only available if you select the Define sensor states for
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
2761
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

2762
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2763
Channel List
Channel Description
Jobs The number of jobs in the queue

More
Knowledge Base


2764
7.8.258 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 569 of the
parent device.
Window s Process Sensor
List 2771 .

§ Dutch: Windows Proces
§ French: Windows processus
§ German: Windows Prozess
§ Portuguese: Processo Windows
§ Russian: П ро цесс Windows
§ Spanish: Proceso Windows
2765
Remarks
§ The sensor cannot show values above 4 GB for 64-bit processes if you use performance counters.
query data.
still work.
2766
Add Sensor

Setting Description
inherited 146 .
2767
Setting Description
§ 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 186 if the process is not active on
the target device.
Debug Options
Debug Options
Setting Description
2768
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

2769
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2770

Channel List
Channel Description
CPU Usage (Average Per The average CPU usage (if multiple instances are running) in percent
Instance)
For the CPU Usage (average per instance) value, the summed up
CPU usage value is divided by the number of all instances. It shows
the average CPU usage of a single instance of the process on one CPU.
CPU Usage (Total) The total CPU usage in percent

For the CPU Usage (Total) 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.
2771
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 in bytes

More
Knowledge Base

2772
7.8.259 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 569 of the parent device.
Window s System Uptime Sensor
List 2778 .

§ Dutch: Windows Systeem Uptime
§ French: Windows disponibilité du système
§ German: Windows-Systemlaufzeit
§ Portuguese: Tempo de ativação do sistema Windows
§ Russian: Врем я бесп еребо йн о й рабо ты систем ы Windows
§ Spanish: Tiempo activo sistema Windows
Remarks
2773
query data.
§ This sensor has a high performance impact.
still work.

2774
Add Sensor

Setting Description
inherited 146 .
§ wmiuptimesensor
2775
Setting Description
sensor settings.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
2776
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2777
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
System Uptime The system uptime

More
Knowledge Base

2778
2779
7.8.260 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 2786 .

§ Dutch: Windows Updates Status (PowerShell)
§ French: Windows statut des mises à jour (PowerShell)
§ German: Windows Updates Status (PowerShell)
§ Japanese: Windows PowerShell

§ Portuguese: Status de atualizações Windows (PowerShell)
§ Russian: Статус о бн о влен ия Windows (PowerShell)
§ Simplified Chinese: Windows (PowerShell)
2780
§ Spanish: Estado de actualizaciones Windows (PowerShell)
Remarks
2781

§ We recommend that you set the scanning interval 2785 of this sensor to at least 12 hours to limit the
load on the server that is monitored.
§ In certain cases, it might take some time until the sensor receives data for the first time.
§ If the sensor cannot determine any values for the Time Since Last Update channel (for example,
because the list of updates is empty), it shows the value -1s and changes to the Warning status 186 .
§ 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.
does PRTG require?
2781
Add Sensor

Setting Description
inherited 146 .
§ windowsupdatesstatus
2782
sensor settings.
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. Choose between:
§ 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?
2783
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description
2784
Setting Description

Inherited Settings
Scanning Interval
The minimum scanning interval of this sensor is 1 hour.
Scanning Interval

objects' settings.
2785
Maintenance Window.
Access Rights
Access Rights
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
2786
Channel Description
Updates (Severity The number of installed updates with critical severity

Critical) Installed
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
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
2787





Facing issues with the Windows Updates Status (PowerShell) sensor - can you help me?
2788
7.8.261 WMI Battery Sensor
The WMI Battery sensor monitors the available capacity and the state of connected batteries of a
Windows-based device via Windows Management Instrumentation (WMI).
WMI Battery Sensor
List 2795 .

§ Dutch: WMI batterij
§ French: Batterie (WMI)
§ German: WMI Batterie
§ Japanese: WMI
§ Portuguese: Bateria (WMI)
§ Russian: Аккум улято р WMI
§ Simplified Chinese: WMI
§ Spanish: Batería (WMI)
Remarks
§ This sensor has a high performance impact. Try to stay below 200 WMI sensors in total per probe 133 .
Above this number, consider using multiple remote probes 3557 for load balancing.
2789
Add Sensor
WMI Battery Specific
Setting Description
Batteries Select the batteries or uninterruptible power supplies (UPSs) that you
want to monitor. PRTG creates one sensor for each battery or
uninterruptible power supply (UPS) that you select.
right corner.

2790
Setting Description
inherited 146 .
§ batterysensor
§ wmibatterysensor
Setting Description
Name Shows the name of the battery or the UPS that this sensor monitors.
2791
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
2792
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2793
Maintenance Window.
Access Rights
Access Rights

2794
Channel List
Channel Description
Battery Health The battery health in percent
Estimated Charge The estimated remaining charge in percent

Remaining
Status The status of the battery

§ Up status 186 : 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 in volts (V)
More
Knowledge Base


2795
7.8.262 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 sensor 2804 .
WMI Custom Sensor
List 2802 .

§ Dutch: WMI (Klant Specifiek)
§ French: WMI personnalisé
§ German: WMI (Benutzerdef.)
§ Japanese: WMI
§ Portuguese: WMI (customizado)
§ Russian: Н естан дартн ы й WMI
§ Spanish: WMI (personalizado)
Remarks
2796
the probe computer?
§ See the Knowledge Base: How do I create a WMI Custom sensor?
Add Sensor
Custom Query Specific
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.
You can change the name later in the sensor's channel settings 3052 .
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 3579
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 sensor 2804 in this case.

2797
Setting Description
inherited 146 .
§ wmicustomsensor
2798
Setting Description
Namespace Enter the WMI namespace for the query.
WQL File Shows the .wql file that this sensor executes with every scanning interval.
Your query must return an integer or float value. Strings are not
supported. Use the WMI Custom String sensor 2804 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.
the field empty.
the field empty.
2799
Setting Description

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
master node.
Sensor Display
Sensor Display
2800
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2801
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
[Value] The retrieved numeric value

More
Knowledge Base
How do I create a WMI Custom sensor?
2802

How do I properly configure a WMI custom sensor?

Which WQL queries are used by the PRTG WMI sensors?

2803
7.8.263 WMI Custom String Sensor
The WMI Custom String sensor performs a custom string query via Windows Management
Instrumentation (WMI).
The sensor can also show the retrieved string value in the sensor message.
If the WQL query returns numeric values, use the WMI Custom sensor 2796 .
WMI Custom String Sensor
List 2812 .

§ 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
2804
the probe computer?
§ See the Knowledge Base: How do I create a WMI Custom sensor?
Add Sensor
Setting Description
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 3579
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
sensor 2796 to not only show the returned value in the sensor
message, but to also monitor the value in a channel.

2805
Setting Description
inherited 146 .
§ wmicustomsensor
sensor settings.
2806
Setting Description
Namespace Enter the WMI namespace for the query.

.
WQL File Shows the .wql file that this sensor executes with every scanning interval.
2807
Setting Description
If the WQL query returns integers or floats, use the WMI Custom
sensor 2796 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.

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 3552 .
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.
Down status.
2808
Setting Description

§ 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
status. Enter an integer or leave the field empty.
Numeric Value Extraction Define if you want to filter out a numeric value from the string received from
Using Regular the WMI object. You can convert this into a float value to use it with
Expression channel limits 3053 .
§ Do not use extraction: 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 2812 .
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.

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
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
2809
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description

2810
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2811
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
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 details, see section
Regular Expressions 3552 .
Channel List
Channel Description

2812
More
Knowledge Base
How do I create a WMI Custom sensor?


2813
7.8.264 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 2820 .

§ 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
2814
§ This sensor supports Windows 8 or Windows Server 2012 or later on the target system.
Add Sensor
WMI Disk Health Specific
Setting Description
right corner.

2815
Setting Description
inherited 146 .
§ wmidiskhealthsensor
§ diskhealthsensor
sensor settings.
Setting Description
Friendly Name Shows a user-friendly name for the physical disk.
2816
Setting Description
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description
2817
Setting Description


Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2818
Maintenance Window.
Access Rights
Access Rights

2819
Channel List
Channel Description
Flush Latency Max The maximum flush latency in milliseconds (msec)

Operational Status The operational status

§ Up status: OK
§ Unknown status: Starting
Read Latency Max The maximum read latency in msec
Write Latency Max The maximum write latency in msec
More
Knowledge Base


2820
7.8.265 WMI Event Log Sensor
The WMI Event Log sensor monitors a Windows logfile 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 2830 .

§ 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
2821
§ See the Knowledge Base: My Event Log sensor ignores changes in the event log. What can I do?
§ See the Knowledge Base: How can I configure sensors using speed limits to keep the status for more
than one interval?
Add Sensor
WMI Event Log Monitor
Setting Description
Log Files Select the log files that you want to monitor. PRTG creates one sensor for
each log file that you select.
right corner.

2822
Setting Description
inherited 146 .
§ wmieventlogsensor
sensor settings.
Setting Description
Log File Shows the Windows log file that this sensor monitors.
2823
Setting Description
scanning interval.
master node.

For details 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?
2824
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.
2825
Setting Description
Filter by Source Filter all events for a certain event source:

§ Off: Do not filter by event source.
§ On: Filter by event source.

Filter Type This setting is only visible if you enable Filter by Source above. Select the
filter type:
Match String (Event This setting is only visible if you enable Filter by Source above. Enter an
Source) 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
Filter by ID Filter all events for a certain event ID:

§ Off: Do not filter by event ID.
§ On: Filter by event ID.

Filter Type This setting is only visible if ID filtering is On above. Select a filter type:
Match Values (Event ID) This setting is only visible if you enable Filter by ID 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 events for a certain event category:

§ Off: Do not filter by event category.
§ On: Filter by event category.

Filter Type This setting is only visible if you enable Filter by Category above. Select a
filter type:
2826
Setting Description
Match String (Event This setting is only visible if you enable Filter by Category above. Enter a
Category) 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
Filter by User Filter all received events for a certain event user:
§ Off: Do not filter by event user.
§ On: Filter by event user.

Filter Type This setting is only visible if you enable Filter by User above. Select a filter
type:
Match String (Event This setting is only visible if you enable Filter by User above. Enter a user
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 does not
process it (Exclude filter option). Enter a string.
Filter by Computer Filter all received events for a certain event computer:
§ Off: Do not filter by event computer.
§ On: Filter by event computer.

Filter Type This setting is only visible if you enable Filter by Computer above. Select a
filter type:
Match String (Event This setting is only visible if you enable Filter by Computer above. Enter a
Computer) 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
Filter by Message Filter all received events for a certain event message:
§ Off: Do not filter by event message.
2827
Setting Description
§ On: Filter by event message.

Filter Type This setting is only visible if you enable Filter by Message above. Select a
filter type:
Match String (Event This setting is only visible if message filtering is On above. Enter a
Message) 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 source that contains the string RAS.
Sensor Display
Sensor Display
Setting Description

2828
Setting Description
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
2829
Access Rights
Access Rights
Channel List
Channel Description
New Records The number of new records per second

More
Knowledge Base
My Event Log sensor ignores changes in the event log. What can I do?


2830
7.8.266 WMI Exchange Server Sensor
The WMI Exchange Server sensor monitors a Microsoft Exchange Server 2003 or later via Windows
WMI Exchange Server Sensor
List 2838 .

§ Dutch: WMI Exchange Server
§ French: Exchange serveur (WMI)
§ German: WMI Exchange-Server
§ Japanese: WMI Exchange
§ Portuguese: Servidor Exchange (WMI)
§ Russian: WMI Exchange Server
§ Simplified Chinese: WMI Exchange
§ Spanish: Servidor Exchange (WMI)
Remarks
2831
Former WMI Exchange Server 2003/2007 sensors from previous PRTG versions continue to monitor
your Exchange server in PRTG 9, but newly added Exchange server sensors are WMI Exchange
Server sensors that can monitor Exchange servers regardless of their version.
Add Sensor
Exchange Server Data Readings Accessible Using WMI
Setting Description
Performance Counters Select the performance counters of the Exchange server that you want to
monitor. PRTG creates one sensor for each performance counter that you
select.
right corner.
The available options depend on your Exchange server configuration.
PRTG shows all possible performance counters with the name and
instance description (if available).
You might be able to select 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.
2832
Setting Description
inherited 146 .
§ wmiexchangeserversensor
sensor settings.
2833
Setting Description
Display Name Shows the display name that the sensor uses to query data from the
target device.
Instance Shows the instance that the sensor uses to query data from the target
device.
WMI Class Shows the WMI class that the sensor uses to query data from the target
device.
Counter Shows the counter that the sensor uses to query data from the target
device.
Time Stamp Shows the time stamp that the sensor uses to query data from the target
device.
2834
Setting Description
Time Frequency Shows the time frequency that the sensor uses to query data from the
target device.
Counter Type Shows the counter type that the sensor uses to query data from the target
device.
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
2835
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2836
Maintenance Window.
Access Rights
Access Rights

2837
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 remote procedure call (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


2838
7.8.267 WMI Exchange Transport Queue Sensor
The WMI Exchange Transport Queue sensor monitors the length of transport queues of a Microsoft
Exchange Server 2003 or later via Windows Management Instrumentation (WMI). It shows the same
information as in Windows System Monitor perfmon.
WMI Exchange Transport Queue Sensor
For an explanation of transport queue types, see the Knowledge Base: What types of Exchange
transport queues are there?
List 2845 .

§ 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
2839
§ See the Knowledge Base: What types of Exchange transport queues are there?
Add Sensor
WMI Exchange Transport Queue Specific
Setting Description
Transport Queues Select the transport queues that you want to monitor. PRTG creates one
sensor for each transport queue that you select.
right corner.
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.

2840
Setting Description
inherited 146 .
§ wmiexchangeservertransportqueuesensor
sensor settings.
2841
Setting Description
target device.
device.
device.
device.
device.
target device.
device.
scanning interval.
2842
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2843
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

2844
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
2845
Channel Description
Items Completed Delivery The number of items with completed delivery per second
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
Items Queued For The number of items expired queued for delivery in total
Delivery Expired Total
Items Queued for Delivery The number of items queued for delivery per second
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 per second
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
2846
Channel Description
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 per second

Second
Messages Submitted The number of messages submitted in total

Total
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?


2847
2848
7.8.268 WMI File Sensor
The WMI File sensor monitors a file via Windows Management Instrumentation (WMI).
WMI File Sensor
List 2854 .

§ Dutch: WMI Bestand
§ French: Fichier (WMI)
§ German: WMI Datei
§ Japanese: WMI
§ Portuguese: Arquivo (WMI)
§ Russian: Файл WMI
§ Spanish: Archivo (WMI)
Remarks
2849
Add Sensor

Setting Description
inherited 146 .
§ wmifilesensor
2850
Setting Description
sensor settings.
WMI File Monitor
WMI File Monitor
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 when the time stamp of the file changes:
§ Ignore changes (default): Do not take action on change.

that the time stamp has changed. In combination with a change
whenever the time stamp changes.
Debug Options
Debug Options
2851
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


2852
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2853

Channel List
Channel Description
File Size The file size in bytes

Last Modified The time since the last modification of the file
More
Knowledge Base
2854

2855
7.8.269 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 2865 .

§ 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)
2856
Remarks
Add Sensor
Drive Selection
Setting Description
Drives Select the drives that you want to monitor from the dropdown list.
You can select All to monitor all available drives, or you can select one
specific drive letter to monitor a single drive only. The dropdown list might
also contain drive letters that do not exist on your device.
You cannot change the drive setting after sensor creation.

2857
Setting Description
inherited 146 .
§ diskspacesensor
§ wmidiskspacesensor
sensor settings.
Drive Selection
Drive Selection
Setting Description
Drives Shows the drives that this sensor monitors. This is either All or a specific
drive letter.
2858
Setting Description

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 186 , 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 3052 .
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
2859
Setting Description
the field empty.
the field empty.
the field empty.
the field empty.
2860
Setting Description
as shown by the free bytes channels of this sensor (by default this is
MB). If the free disk space of one of your drives exceeds this value, the
empty.
MB). If the free disk space of one of your drives exceeds this value, the
empty.
MB). If the free disk space of one of your drives falls below this value, the
empty.
MB). If the free disk space of one of your drives falls below this value, the
empty.
2861
Setting Description

found.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
2862
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2863
Maintenance Window.
Access Rights
Access Rights

2864
Channel List
Channel Description
Free Bytes C: The free space in bytes
Free Bytes D: The free space in bytes
Free Space C: The free space in percent
Free Space D: The free space in percent
Total The disk space in total
More
Knowledge Base


2865
7.8.270 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 2872 .

§ Dutch: WMI HDD Status
§ French: État du disque dur (WMI)
§ German: WMI Laufwerkszustand
§ Japanese: WMI HDD
§ Portuguese: Funcionamento do HDD (WMI)
§ Russian: Рабо то сп о со бн о сть жестко го диска WMI
2866
§ Spanish: Salud HDD (WMI)
Remarks
§ This sensor requires Windows 7 or later on the target machine that holds the hard disk drives you want
to monitor. The sensor might not work reliably if the target machine 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.
§ 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 for more information.
§ For a general introduction to the technology behind WMI, see section Monitoring via WMI 3360 .
Add Sensor
S.M.A.R.T. Specific
Setting Description
IDE Devices Select the IDE target device. PRTG creates one sensor for each IDE
device that you select.
right corner.
The items in the list are specific to the parent device.

2867
Setting Description
inherited 146 .
§ smartsensor
sensor settings.
2868
S.M.A.R.T. Specific
S.M.A.R.T. Specific
Setting Description
Serial Number Shows the serial number of the disk that this sensor monitors.
Size (GB) Shows the size of the disk that this sensor monitors.
Name Shows the name of the disk that this sensor monitors.
Debug Options
Debug Options
2869
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


2870
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2871
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 186 . 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 3541 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
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
2872
Channel Description
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
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 unused reserved block count total

Count Total
Used Reserved Block The used reserved block count total

Count Total
Temperature Celsius The temperature
Total LBAs Read The total LBAs read
2873
Channel Description
Total LBAs Written The total LBAs written
Wear Range Delta The wear range delta
More
Knowledge Base


2874
7.8.271 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 2881 .

§ 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)
2875
§ Russian: Вво д-вы во д ло гическо го диска WMI
§ Simplified Chinese: WMI I/O

§ Spanish: E/S de disco lógico (WMI)
Remarks
§ This sensor supports Windows Server 2008 R2 or later. It does not work on previous Windows versions
(Windows Server 2008 or earlier).
Add Sensor
WMI Logical Disk I/O Specific
Setting Description
right corner.

2876
Setting Description
inherited 146 .
§ wmilogicalsensor
sensor settings.
2877
Setting Description
Disk Shows the logical disk or mount point that this sensor monitors.
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
2878
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2879
Maintenance Window.
Access Rights
Access Rights

2880
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 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 in milliseconds (msec)
Avg Transfer Time The average transfer time in msec
Avg Write Queue The average number of items in the write queue
Avg Write Time The average write time in msec
Current Queue The current number of items in the queue
Disk IOs The number of disk input/output (I/O) operations per second
Disk Read IOs The number of disk read I/O operations per second
Disk Read Time % The disk read time in percent
Disk Time % The disk time in percent
Disk Transfer The disk transfer speed in bytes per second
Disk Write IOs The number of disk write I/O operations per second
Disk Write Time % The disk write time in percent
2881
Channel Description

Idle Time % The idle time in percent
Split IOs The number of split I/O operations per second
More
Knowledge Base


2882
7.8.272 WMI Memory Sensor
The WMI Memory sensor monitors available (free) system memory on Windows systems via Windows
WMI Memory Sensor
List 2888 .

§ Dutch: WMI Geheugen
§ French: Mémoire (WMI)
§ German: WMI Arbeitsspeicher
§ Japanese: WMI
§ Portuguese: Memória (WMI)
§ Russian: П ам ять WMI
§ Spanish: Memoria (WMI)
Remarks
2883
Add Sensor

Setting Description
inherited 146 .
§ memorysensor
§ wmimemorysensor
2884
Setting Description
sensor settings.
Debug Options
Debug Options
Setting Description
master node.
Setting Description
Query Method Select the method that the sensor uses to query via WMI:
2885
Setting Description
§ Use the default WMI query method: 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

2886
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2887

Channel List
Channel Description

More
Knowledge Base
2888

2889
7.8.273 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 2896 .
2890
§ 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
§ You can only add this sensor to a device (computer) running a Microsoft SQL database.
Add Sensor
SQL Server Settings
Setting Description
Server Instances Select the instances that you want to monitor. PRTG creates one sensor

right corner.
Display name and service name are provided as returned by the SQL
server.
2891
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. Choose from:
§ 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).
§ 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.

2892
Setting Description
inherited 146 .
§ wmisqlserversensor
SQL Server Settings
SQL Server Settings
Setting Description
Service Shows the service that this sensor monitors.
2893
Setting Description
Name Shows the name of the server instance that this sensor monitors.
Naming Method Select whether PRTG automatically selects the name of the WMI class
used for monitoring:
§ Automatically determine the WMI class name: 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.
Setting Description
Performance Counters Shows the performance counter that this sensor monitors.
2894
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2895
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2896
Channel Description
Average Wait Time The average amount of wait time for each lock request that resulted in a
wait
Batch Requests The number of Transact-SQL command batches received per second. This
statistic is affected by all constraints (such as input/output (I/O), 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.
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
Deadlocks The number of lock requests per second that resulted in a deadlock
Full Scans The number of unrestricted full scans per second. These can be either
base-table or full-index scans.
Lock Requests The number of new locks and lock conversions per second requested from
the lock manager
Logins The total number of logins started per second
Logouts The total number of logout operations started per second
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 The number of page splits per second that occur as the result of
overflowing index pages
SQL Cache Memory (KB) The total amount of dynamic memory the server is using for the dynamic
SQL cache
2897
Channel Description
SQL Compilations 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 Re-Compilations 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)
Table Lock Escalations The number of times that locks on a table were escalated
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?


2898
7.8.274 WMI Microsoft SQL Server 2008 Sensor
List 2905 .

Remarks
2899
Add Sensor
SQL Server Settings
Setting Description

right corner.
server.
Setting Description
second.
second).
pages.
2900
Setting Description

channels.

Setting Description
inherited 146 .
2901
Setting Description
§ wmisqlserversensor2008
sensor settings.
SQL Server Settings
SQL Server Settings
Setting Description

2902
Setting Description
automatic mode.
scanning interval.
master node.
Setting Description
2903
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2904
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2905
Channel Description
wait
SQL Server.
connections
the lock manager
optimization
SQL cache
2906
Channel Description
a steady state.
procedure cache)
(KB)
(KB)
More
Knowledge Base


2907
List 2914 .

Remarks
2908
Add Sensor
SQL Server Settings
Setting Description

right corner.
server.
Setting Description
second.
second).
pages.
2909
Setting Description

channels.

Setting Description
inherited 146 .
2910
Setting Description
sensor settings.
SQL Server Settings
SQL Server Settings
Setting Description

2911
Setting Description
automatic mode.
scanning interval.
master node.
Setting Description
2912
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2913
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2914
Channel Description
wait
SQL Server.
connections
the lock manager
optimization
SQL cache
2915
Channel Description
a steady state.
procedure cache)
(KB)
(KB)
More
Knowledge Base


2916
List 2923 .

Remarks
2917
Add Sensor
SQL Server Settings
Setting Description

right corner.
server.
Setting Description
second.
second).
pages.
2918
Setting Description

channels.

Setting Description
inherited 146 .
2919
Setting Description
sensor settings.
SQL Server Settings
SQL Server Settings
Setting Description

2920
Setting Description
automatic mode.
scanning interval.
master node.
Setting Description
2921
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2922
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2923
Channel Description
wait
SQL Server.
connections
the lock manager
optimization
SQL cache
2924
Channel Description
a steady state.
procedure cache)
(KB)
(KB)
More
Knowledge Base


2925
List 2932 .

Remarks
2926
Add Sensor
SQL Server Settings
Setting Description

right corner.
server.
Setting Description
second.
second).
pages.
2927
Setting Description

channels.

Setting Description
inherited 146 .
2928
Setting Description
sensor settings.
SQL Server Settings
SQL Server Settings
Setting Description

2929
Setting Description
automatic mode.
scanning interval.
master node.
Setting Description
2930
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2931
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2932
Channel Description
wait
SQL Server.
connections
the lock manager
optimization
SQL cache
2933
Channel Description
a steady state.
procedure cache)
(KB)
(KB)
More
Knowledge Base


2934
List 2941 .

Remarks
2935
Add Sensor
SQL Server Settings
Setting Description

right corner.
server.
Setting Description
second.
second).
pages.
2936
Setting Description

channels.

Setting Description
inherited 146 .
2937
Setting Description
sensor settings.
SQL Server Settings
SQL Server Settings
Setting Description

2938
Setting Description
automatic mode.
scanning interval.
master node.
Setting Description
2939
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2940
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2941
Channel Description
wait
SQL Server.
connections
the lock manager
optimization
SQL cache
2942
Channel Description
a steady state.
procedure cache)
(KB)
(KB)
More
Knowledge Base


2943
List 2950 .

Remarks
2944
Add Sensor
SQL Server Settings
Setting Description

right corner.
server.
Setting Description
second.
second).
pages.
2945
Setting Description

channels.

Setting Description
inherited 146 .
2946
Setting Description
sensor settings.
SQL Server Settings
SQL Server Settings
Setting Description

2947
Setting Description
automatic mode.
scanning interval.
master node.
Setting Description
2948
Sensor Display
Sensor Display
Setting Description

Inherited Settings
2949
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
2950
Channel Description
wait
SQL Server.
connections
the lock manager
optimization
SQL cache
2951
Channel Description
a steady state.
procedure cache)
(KB)
(KB)
More
Knowledge Base


2952
7.8.280 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 2958 .

§ 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
2953
Add Sensor

Setting Description
inherited 146 .
§ pingsensor
§ wmisensor
2954
Setting Description
§ wmipingsensor
§ remotepingsensor
sensor settings.
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.
integer. The maximum timeout value is 300 seconds (5 minutes)..
2955
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description
2956
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2957
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Ping Time The Ping time from the remote device to the target device in milliseconds
(msec)
More
Knowledge Base

2958
2959
7.8.281 WMI Security Center Sensor
The WMI Security Center sensor monitors the security status of a Windows client computer 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 2965 .

§ 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
§ This sensor requires Windows Vista or later on the target computer.
2960
§ 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.
Add Sensor
WMI Security Center Specific
Setting Description
Security Center Products 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.

2961
Setting Description
inherited 146 .
§ WMISecurityCenter
sensor settings.
Setting Description
Display Name Shows the display name of the security center product that this sensor
monitors.
2962
Setting Description
Type Shows the type of the security center product that this sensor monitors.
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
2963
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2964
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Status The status code of the monitored security product

§ Up status 186 : 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)
2965
More
Knowledge Base

2966
7.8.282 WMI Service Sensor
The WMI Service sensor monitors a Windows service via Windows Management Instrumentation (WMI).
WMI Service Sensor
List 2973 .

§ Dutch: WMI Service
§ French: Service (WMI)
§ German: WMI Dienst
§ Japanese: WMI
§ Portuguese: Serviço (WMI)
§ Russian: Служба WMI
§ Spanish: Servicio (WMI)
Remarks
2967
Add Sensor
WMI Service Monitor
Setting Description
services Select the services that you want to monitor. PRTG creates one sensor
right corner.
The name and description appear in the language of the device's
Windows installation.
After creation, the sensor shows the Down status 186 if the service
does not run.

2968
Setting Description
inherited 146 .
§ wmiservicesensor
§ servicesensor
sensor settings.
WMI Service Monitor
WMI Service Monitor
2969
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: PRTG tries to start the service if it is not running
when the device is scanned. In combination with a change trigger 3182 ,
you can use this mechanism to trigger a notification 3063 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 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 above. Define
what to do if PRTG restarts the service:
§ Ignore changes: No action is taken on change.
§ Trigger 'change' notification: The sensor sends an internal message

indicating that its value has changed. In combination with a change
trigger, you can use this mechanism to trigger a notification whenever
the sensor value changes.
Extended Monitoring Select whether you want to monitor CPU usage and other performance
counters:
§ Only check if the service is running: 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 Shows the Windows service that this sensor monitors.

Description Shows the description of the Windows service that this sensor monitors.
2970
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description


2971
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2972
Channel List
Channel Description

Enable Monitor other performance counters in the sensor settings to
show this parameter.
Handles The number of handles

Pagefile Usage The pagefile usage in bytes

Sensor Execution Time The execution time of the monitoring request

Threads The number of threads

Working Set The working set in bytes

More
Knowledge Base


2973
7.8.283 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 186 for different share status messages.
WMI Share Sensor
List 2982 .

§ Dutch: WMI Share
§ French: Partage (WMI)
§ German: WMI Freigabe
§ Japanese: WMI
§ Portuguese: Compartilhamento (WMI)
§ Russian: Ресурс WMI
§ Spanish: Recurso compartido (WMI)
Remarks
2974
Add Sensor
WMI Shared Resource
Setting Description
Shares Select the shares that you want to monitor. PRTG creates one sensor for
each share that you select.
right corner.
To provide any shares, the LanmanServer "Server" Windows service
must run on the target computer. If it does not run, there are no
shares and you see a No Share available message.

Setting Description
2975
Setting Description
inherited 146 .
§ wmisharesensor
sensor settings.
WMI Shared Resource
WMI Shared Resource
Setting Description
Shared Resource Shows information about the shared resource that this sensor monitors.
2976
Setting Description
Description Shows the description of the shared resource that this sensor monitors.
Type Shows the type of the shared resource that this sensor monitors.
TypeID Shows 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 186 . 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.
2977
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.
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.
2978
Condition Description
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
Setting Description
2979
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description

2980
Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
2981
Channel List
Channel Description
Available The availability of the share in milliseconds (msec)

More
Knowledge Base


2982
7.8.284 WMI SharePoint Process Sensor
The WMI SharePoint Process sensor monitors a Microsoft SharePoint server via Windows Management
WMI SharePoint Process Sensor
List 2989 .

§ 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
2983
Add Sensor
WMI Process Monitor
Setting Description
SharePoint Processes Select the SharePoint processes that you want to monitor. PRTG creates
one sensor for each process that you select.
right corner.

2984
Setting Description
inherited 146 .
§ wmiprocesssensor
§ wmisharepointprocesssensor
WMI Process Monitor
WMI Process Monitor
Setting Description
SharePoint Process Shows the name of the SharePoint process that this sensor monitors.
2985
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description
2986
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2987
Maintenance Window.
Access Rights
Access Rights

2988
Channel List
Channel Description
Active Threads The number of active threads
Current Page Requests The number of current page requests

Executing SQL Queries The number of Structured Query Language (SQL) queries being executed
Global Heap Size The global heap size in bytes
Object Cache Always The object cache always live size in bytes
Live Size
Template Cache Size The template cache size in bytes
More
Knowledge Base


2989
7.8.285 WMI Storage Pool Sensor
The WMI Storage Pool sensor monitors a storage pool via Windows Management Instrumentation (WMI).
WMI Storage Pool Sensor
List 2996 .

§ 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
2990
§ This sensor supports Windows 8 or Windows Server 2012 or later on the target system.
Add Sensor
WMI Storage Pool Specific
Setting Description
Storage Pools Select the storage pools that you want to monitor. PRTG creates one
sensor for each storage pool that you select.
right corner.

2991
Setting Description
inherited 146 .
§ wmistoragepoolsensor
§ storagepoolsensor
sensor settings.
Setting Description
Friendly Name Shows a user-friendly name for the storage pool.
2992
Setting Description
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description
2993
Setting Description


Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
2994
Maintenance Window.
Access Rights
Access Rights

2995
Channel List
Channel Description

Operational Status The operational status

§ Up status: OK
§ Unknown status: Starting
More
Knowledge Base


2996
7.8.286 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 3001 .

§ 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
2997
§ 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.
Add Sensor

Setting Description
inherited 146 .
2998
Setting Description
§ wmiterminalservicessensor
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
Sensor Display
Sensor Display
2999
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
3000
Maintenance Window.
Access Rights
Access Rights
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
3001
More
Knowledge Base

3002
7.8.287 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 3007 .

§ 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
3003
§ 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.
Add Sensor

Setting Description
inherited 146 .
3004
Setting Description
§ wmiterminalservicessensor
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
3005
Sensor Display
Sensor Display
Setting Description

Inherited Settings
3006
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights
Channel List
3007
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
More
Knowledge Base


3008
7.8.288 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 3013 .

§ 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
3009
Add Sensor

Setting Description
inherited 146 .
§ wmiutctimesensor
3010
Setting Description
Debug Options
Debug Options
Setting Description
master node.
Sensor Display
Sensor Display
Setting Description
3011
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
3012
Maintenance Window.
Access Rights
Access Rights
Channel List
Channel Description
Difference The time difference between the PRTG core server system time and the
target device in seconds
UTC Time The UTC time of the target device

More
Knowledge Base
3013

3014
7.8.289 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 3022 .

§ 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
3015
Add Sensor
Vital System Data Readings Accessible Using WMI
Setting Description
Performance Counters 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

3016
Setting Description
inherited 146 .
§ wmivitalsystemdatasensor
sensor settings.
3017
Setting Description
target device.
device.
device.
device.
device.
3018
Setting Description
target device.
device.
scanning interval.
master node.
Sensor Display
Sensor Display
Setting Description
3019
Setting Description

Inherited Settings
Scanning Interval
Scanning Interval

objects' settings.
3020
Maintenance Window.
Access Rights
Access Rights

3021
Channel List
Channel Description
Bytes In All Heaps The common language runtime (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
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 in percent
More
Knowledge Base


3022
7.8.290 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 3029 .

§ Dutch: WMI Volume
§ French: Espace disponible du disque (WMI)
§ German: WMI Datenträger
§ Japanese: WMI
§ Portuguese: Volume (WMI)
§ Russian: То м WMI
§ Spanish: Volumen (WMI)
3023
Remarks
§ This sensor does not support Windows XP and earlier.
Add Sensor
WMI Volume Specific
Setting Description
Volumes Select the volumes (drives, logical volumes, mount points) that you want
to monitor. PRTG creates one sensor for each volume that you select.
right corner.

3024
Setting Description
inherited 146 .
§ wmivolumesensor
§ diskspacesensor
sensor settings.
WMI Volume Specific
WMI Volume Specific
3025
Setting Description
DeviceID Shows the unique identifier of the volume that this sensor monitors.
Drive Type Shows the type of disk drive that this sensor monitors.
ID Selection Define how the sensor identifies the volume:

§ Use system device ID (recommended): 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
Setting Description
master node.
3026
Sensor Display
Sensor Display
Setting Description

Inherited Settings
3027
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

3028
Channel List
Channel Description

More
Knowledge Base


3029
7.8.291 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 3036 .

§ Dutch: WSUS Statistieken
§ French: WSUS statistiques
§ German: WSUS-Statistiken
§ Japanese: WSUS
§ Portuguese: Estatísticas WSUS
§ Russian: Статистика WSUS
§ Simplified Chinese: WSUS
3030
§ Spanish: Estadísticas WSUS
Remarks
§ This sensor requires 3031 the Microsoft WSUS 3.0 Administration Console on the probe system.
§ See the Knowledge Base: Can I encrypt connections to my WSUS server?
does PRTG require?
correctly connect.
WSUS 3.0 For this sensor to work, the Microsoft WSUS 3.0 Administration Console
Administration Console must be installed on the probe system. In a cluster, it must be installed
on every cluster node.
Add Sensor
3031
Setting Description
inherited 146 .
§ ptfsensor
sensor settings.
3032
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
If you want to use SSL/TLS, you must configure the WSUS server
accordingly. For details, see the Knowledge Base: Can I encrypt
connections to my WSUS server?
Debug Options
Debug Options
Setting Description
scanning interval.
master node.
3033
Sensor Display
Sensor Display
Setting Description

Inherited Settings
3034
Scanning Interval
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

3035
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
Computers Up To Date The number of computers that are up to date
Declined Updates The number of updates that were declined
3036
Channel Description
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
Can I encrypt connections to my WSUS server?



3037
7.8.292 Zoom Service Status Sensor
The Zoom Service Status sensor monitors the global status of all Zoom services.
Zoom Service Status Sensor
List 3043 .

§ Dutch: Zoom Service Status
§ French: Zoom Service Status
§ German: Zoom Service Status
§ Japanese: Zoom Service Status
§ Portuguese: Zoom Service Status
§ Russian: Zoom Service Status
§ Simplified Chinese: Zoom Service Status
§ Spanish: Zoom Service Status
3038
Remarks
§ This sensor only supports the global status of Zoom services.
device templates?
Add Sensor

Setting Description
inherited 146 .
3039
Setting Description
§ zoom
§ zoomsensor
Sensor Display
Sensor Display
Setting Description

3040
Setting Description
Debug Options
Debug Options
Setting Description
Inherited Settings
Scanning Interval
3041
Scanning Interval

objects' settings.
Maintenance Window.
Access Rights
Access Rights

3042
Channel List
Channel Description
Cloud Recording The status of Cloud Recording

§ Up status 186 : Operational
§ Warning status: Degraded Performance, Under Maintenance
§ Down status: Major Outage, Partial Outage
Downloading Center The status of Downloading Center

§ Up status: Operational
Live Streaming The status of Live Streaming

3043
Channel Description
Marketplace The status of Marketplace

Meeting Telephony The status of Meeting Telephony Services

Services
REST API The status of REST API

Web Client The status of Web Client

Web Portal The status of Web Portal

Web SDK The status of Web SDK

Webhooks The status of Webhooks

3044
Channel Description
Zoom Chat The status of Zoom Chat

Zoom Cloud Room The status of Zoom Cloud Room Connector

Connector
Zoom Connector for The status of Zoom Connector for Cisco

Cisco
Zoom Connector for The status of Zoom Connector for Polycom

Polycom
Zoom Dashboard & The status of Zoom Dashboard & Reporting

Reporting
Zoom Meetings The status of Zoom Meetings

Zoom Phone The status of Zoom Phone

3045
Channel Description
Zoom Video Webinars The status of Zoom Video Webinars
More
Knowledge Base

3046
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 or .dll 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 3496 ,
which contains details about the necessary return format for these sensors. WMI Custom sensors allow
you to execute WQL requests.
§ EXE/Script sensor 941
§ EXE/Script Advanced sensor 951
§ Python Script Advanced sensor 1749
§ REST Custom sensor 1819
§ SSH Script sensor 2567
§ SSH Script Advanced sensor 2578
§ WMI Custom sensor 2796
§ WMI Custom String sensor 2804
Additionally, some types of SQL sensors execute script files with SQL queries:
The HL7 sensor 1017 sends messages that are stored in extra files on the probe system.
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 3579 , 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.
3047
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 Dll - Returns a random integer.dll
§ Demo EXE - Returns a random integer.exe
§ Demo EXE - Returns number of files in folder (parameter).exe
§ Demo EXE - Returns user of process.exe
§ Demo Powershell Script - Available MB via WMI.ps1
§ Demo Powershell Script - InterruptsPerSec via WMI.ps1
§ Demo Powershell Script - Powershell Version.ps1
§ Demo Powershell Script - Returns a fixed integer.ps1
§ Demo Powershell Script - Returns a random integer.ps1
§ Demo Powershell Script - Returns Random Integer and Warnings.ps1
§ Demo VBScript - InterruptsPerSec via WMI.vbs
§ Demo VBScript - Multiplies two integers(2 parameters).vbs
§ Demo VBScript - Returns a fixed float value.vbs
§ Demo VBScript - Returns a fixed integer.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

PRT G Manual

Uploaded by

Document Information

Original Title

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: August 2022 in Nuremberg

Part 1 Welcome to PRTG ......................................................................................................... 13

1.1 About this Document ..................................................................................................... 16

2.1 Step 1: Download, Installation, and First Login ................................................................. 44

3.1 Create a PRTG Hosted Monitor Instance ......................................................................... 56

4.1 Download PRTG ............................................................................................................ 96

5.1 Architecture and User Interfaces ................................................................................... 133

6.1 Login .......................................................................................................................... 161

7.1 Auto-Discovery ............................................................................................................ 269

8.1 Toplists ..................................................................................................................... 3077

Part 10 PRTG Apps for Mobile Network Monitoring .................................................................... 3340

Part 11 Desktop Notifications .................................................................................................. 3343

Part 12 Sensor Technologies ................................................................................................... 3346

14.1 Active Directory Integration ......................................................................................... 3446

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 43 .

Monitoring w ith PRTG

PRTG can monitor:

§ Uptimes, downtimes, and slow servers

§ System health of hardware devices

§ Network devices and bandwidth

§ service level agreement (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

PRTG Key Features

§ 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?

We provide three release channels for PRTG Network Monitor:

Release notes for the "stable" release channel

PRTG version history

§ Monitors an unlimited number of sensors.

§ Supports all available sensors.

§ Free for personal and commercial use.

§ Monitors up to 100 sensors.

§ Supports all available sensors.

The Freeware Edition is not available in PRTG Hosted Monitor.

§ Monitors a maximum number of sensors (consider our recommendations 28 ).

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 26

ú Large PRTG Installations 27

§ Detailed System Requirements 27

ú Hardware and Network Size Requirements for Remote Probes 29

ú Performance Impact Considerations Based on Sensor Types 29