advertisement
Part 6: Ajax Web Interface—Device and Sensor Setup | 8 Sensor Settings
39 HTTP Transaction Sensor
6.8.39 HTTP Transaction Sensor
The HTTP Transaction sensor monitors an interactive website, such as a web shop, by performing a transaction using a set of Hypertext Transfer Protocol (HTTP) URLs. The sensor monitors whether logins or shopping carts work properly. It returns the loading time.
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually
220
. It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later.
Sensor Settings
On the sensor's details page, click on the Set t ings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Set t ings
Sensor Name
Tags
Priority
Enter a meaningful name to identify the sensor. The name will be shown by default in the device tree and in all alarms.
Enter one or more tags, separated by space or comma. You can use tags to group sensors and use tag-filtered views later on. Tags are not case sensitive. We recommend using the default value. You can add additional tags to it, if you like. Other tags are
89
from objects further up in the device tree. Those are not visible here.
Select a priority for the sensor. This setting determines where the sensor will be placed in sensor lists. Top priority will be at the top of a list. You can choose from one star (low priority) to five stars
(top priority).
HTTP Specific
Timeout (Sec.) Enter a timeout in seconds for all HTTP requests. If the complete transaction takes longer than this value the request is aborted and an error message is triggered. The maximum value is 900 seconds
(15 minutes).
562
28.05.2014
28.05.2014
Part 6: Ajax Web Interface—Device and Sensor Setup | 8 Sensor Settings
39 HTTP Transaction Sensor
HTTP Specific
Single URL Timeout
(Sec.)
Enter a timeout in seconds for one single HTTP request. If the reply of any single request takes longer than this value the transaction is aborted and an error message is triggered. The maximum value is
900 seconds (15 minutes).
HTTP Engine
Monitoring Engine If you encounter unexpected errors with the standard method that is used to monitor an URL, try to use the compatibility mode which is based on .Net
(introduced in PRTG v13.x.7). Choose between:
§ Default /High Performance (recommended): This is the default monitoring method for this sensor type.
§ Alt ernat e/Compat ibilit y Mode: Try this method as an alternative for websites that do not work with the default approach. Using the compatibility mode, this sensor will execute an external exe . Thus, this method will need more resources, but it can be helpful in particular cases. Note: If you select the compatibility mode, the options for the SSL method will be slightly different. You can also check for trusted certificates.
Please see below.
Note: When using the Compatibility Mode, Smart URL
Replacement will not work, i.e., this sensor does not use the IP
Address/DNS value of the parent device automatically then.
SSL Specific
SSL Method This setting is relevant only when using https in the URL field. We recommend using the default value. If you experience connection problems, please select another SSL method from the list. Choose between:
§ SSL V2
§ SSL V2 or V3: This is the default setting.
§ SSL V3
§ TLS V1
Note: Other TLS versions are not supported.
563
Part 6: Ajax Web Interface—Device and Sensor Setup | 8 Sensor Settings
39 HTTP Transaction Sensor
564
SSL Specific (when using Compat ibilit y Mode)
SSL Method
When using the compatibility mode, the SSL specific settings are a bit different to the default SSL settings. SSL V2 is not available. You can choose between:
§ SSL V3
§ TLS V1
§ SSL V3 or TLS V1: This is the default setting.
Check SSL Certificates Specify if the certificate of the monitored URL will be checked.
Choose between:
§ Do not check used cert ificat es: This the default setting.
§ Check if t he used cert ificat es are t rust ed: If the certificate of the server is not trusted, the sensor will go into a Down status and display a corresponding message.
Note: This sensor type implicitly supports Server Name Identification (SNI), an extension to the
TLS protocol.
Advanced Sensor Dat a
Limit Download (kb)
Cookie Management
Result Handling
Enter a maximum amount of data that will be transferred per every single request. If you set content checks below, please be aware that only the content downloaded within this limit can be checked for certain search expressions.
Select if cookies will be used for the transaction. Choose between:
·
Use cookies (recommended): Allow cookies to be set and read during the transaction cycle.
·
Ignore cookies: Do not allow cookies. Use this option if you want to test the transaction without the use of cookies.
We recommend using the default value.
Define what will be done with the web page loaded at the given
URL. Choose between:
·
Discard HTML result : Do not store the requested web page.
·
St ore lat est HTML result : Store the last result of the requested web page to the "Logs (Sensors)" directory (on the Master node, if in a cluster). This is for debugging purposes, especially in combination with content checks. The file will be overridden with each scanning interval. For information on how to find the folder
2074
section.
28.05.2014
28.05.2014
Part 6: Ajax Web Interface—Device and Sensor Setup | 8 Sensor Settings
39 HTTP Transaction Sensor
Aut hent icat ion
Authentication Define if the web page at the configured URL need authentication.
Choose between:
§ No aut hent icat ion needed
§ Web page needs aut hent icat ion
User
Password
This field is only visible if authentication is enabled above. Enter a username. Please enter a string.
This field is only visible if authentication is enabled above. Enter a password. Please enter a string.
Authentication Method This field is only visible if authentication is enabled above. Please select the authentication method the given URL is protected with.
Choose between:
·
Basic access aut hent icat ion (HTTP): Use simple HTTP authentication. This is the default setting and suitable for most cases. Note: This authentication method will transmit credentials as plain text!
·
Windows NT LAN Manager (NTLM): Use the Microsoft NTLM protocol for authentication. This is sometimes used in Intranets for single sign-on.
We recommend using the default value.
Transact ion URL
You can define up to 10 different transaction URLs which will all be called in a row. Only if the complete transaction can be completed, the sensor will be in an Up
121
. Using this mechanism you can set up an extended monitoring with multiple URLs. Please enter settings for at least one transaction URL. You can use as many steps as needed and disable the other steps.
Transaction Step # x This setting is available for URL #2 through #10. Define if you want to use this step for your transaction check. Choose between:
§ Disable st ep #x: Do not use this step. Choose this option if you do not need all 10 steps for your transaction check.
§ Enable st ep #x: Enable this step. Further options will be viewed, as described below.
565
Part 6: Ajax Web Interface—Device and Sensor Setup | 8 Sensor Settings
39 HTTP Transaction Sensor
566
Transact ion URL
URL
Request Method
Please enter the URL the sensor will connect to. It has to be URL encoded ! If you enter an absolute URL, this address will be independent from the IP address/DNS name setting of the device this sensor is created on. PRTG uses a smart URL replacement which allows you to use the parent device's IP address/DNS name setting as part of the URL. For more information, please see section Smart URL Replacement below.
The request method determines how the given URL is requested.
·
GET: Request the website directly, like browsing the web. We recommend using this setting for a simple check of a web page.
·
POST: Send post form data to the URL. If this setting is chosen, you must enter the data that will be sent in the Post dat a field below.
·
HEAD: Only request the HTTP header from the server; without the actual web page. Although this saves bandwidth since less data is transferred, it is not recommended because the measured request time is not the one experienced by your users and you might not be notified for slow results or timeouts.
Postdata This field is only active when POST is selected in the Request
Met hod setting above. Please enter the data part for the post request here. Note: No XML is allowed here!
Check For Existing Key
Words (Positive)
Define whether the result at the configured URL will be checked for keywords. Choose between:
§ Disable: Do not search for keywords.
§ Enable key word check (posit ive): In the result returned at the
URL, check if a key word exists.
Note: The content check is only intended for html websites and might not work with other target URLs.
Response Must Include Define which string must be part of the web at the given URL. If the data does not include this string, the sensor will be set to an error state. Please enter a string. Note: Only simple text search is available here. The characters * and ?
work here as placeholder, whereas * stands for no or any number of characters and ?
stands for exactly one character (as known from Windows search). This behavior cannot be disabled, so the literal search for these characters is not possible.
Check For Existing Key
Words (Negative)
Define whether the the result at the configured URL will be checked for keywords. Choose between:
§ Disable: Do not search for keywords.
28.05.2014
Part 6: Ajax Web Interface—Device and Sensor Setup | 8 Sensor Settings
39 HTTP Transaction Sensor
28.05.2014
Transact ion URL
Response Must Not
Include
§ Enable key word check (negat ive): In the result returned at the
URL, check if a key word does not exist.
Note: The content check is only intended for html websites and might not work with other target URLs.
Define which string must not be part of the web at the given URL. If the data does include this string, the sensor will be set to an error state. Please enter a string. Note: Only simple text search is available here. The characters * and ?
work here as placeholder, whereas * stands for no or any number of characters and ?
stands for exactly one character (as known from Windows search). This behavior cannot be disabled, so the literal search for these characters is not possible.
Inherited Settings
By default, all following settings are inherited from objects higher in the hierarchy and should be changed there, if necessary. Often, best practice is to change them centrally in the
224
group's settings. To change a setting for this object, disable inheritance by clicking on the check mark symbol in front of the respective setting name. You will then see the options described below.
Proxy Set t ings for HTTP Sensors
HTTP Proxy Settings The proxy settings determine how a sensor connects to a given
URL. You can enter data for a proxy server that will be used when connecting via HTTP or HTTPS. Note: This setting is valid for the monitoring only and determines the behavior of sensors. In order to change proxy settings for the core server, please see
Administ rat ion—Core & Probes
1849
.
Name Enter the IP address or DNS name of the proxy server to use. If you leave this field empty, no proxy will be used.
Port
User
Password
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
If the proxy requires authentication, enter the username for the proxy login. Note: Only basic authentication is available! Please enter a string or leave the field empty.
If the proxy requires authentication, enter the password for the proxy login. Note: Only basic authentication is available! Please enter a string or leave the field empty.
567
Part 6: Ajax Web Interface—Device and Sensor Setup | 8 Sensor Settings
39 HTTP Transaction Sensor
Scanning Int erval
Scanning Interval The scanning interval determines the time the sensor waits between two scans. Select a scanning interval (seconds, minutes, or hours) from the list. You can change the available intervals in
1839
.
Schedules, Dependencies, and Maint enance Window
Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings.
Schedule
Maintenance Window
Select a schedule from the list. Schedules can be used to monitor for a certain time span (days, hours) throughout the week. With the period list option it is also possible to pause monitoring for a specific time span. You can create new schedules and edit existing ones in the
1817
. Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active.
Specify if you want to set-up a one-time maintenance window.
During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between:
§ Not set (monit or cont inuously ): No maintenance window will be set.
§ Set up a one-t ime maint enance window: Pause monitoring within a maintenance window.
Maintenance Begins At This field is only visible if maintenance window is enabled above.
Use the date time picker to enter the start date and time of the maintenance window.
Maintenance End At
Dependency Type
This field is only visible if maintenance window is enabled above.
Use the date time picker to enter the end date and time of the maintenance window.
Define a dependency type. Dependencies can be used to pause monitoring for an object depending on the status of another. You can choose between:
§ Use parent : Pause the current sensor if the device it is created on is in a Down status, or if it is paused by another dependency.
568
28.05.2014
28.05.2014
Part 6: Ajax Web Interface—Device and Sensor Setup | 8 Sensor Settings
39 HTTP Transaction Sensor
Schedules, Dependencies, and Maint enance Window
Dependency
Delay (Seconds)
§ Select object : Pause the current sensor if the device it is created on is in an Down status, or if it is paused by another dependency. Additionally, pause the current sensor if a specific other object in the device tree is in a Down status, or if it is paused by another dependency. Select below.
§ Mast er object for parent : Make this sensor the master object for its parent device. The sensor will influence the behavior of the device it is created on: If the sensor is in a Down status, the device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor will be paused if the parent group of its parent device is in a Down status, or if it is paused by another dependency.
Note: Testing your dependencies is easy! Simply choose Simulat e
Error St at us from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused.
This field is only visible if the select object option is enabled above.
Click on the reading-glass symbol and use the
159 to choose an object on which the current sensor will be dependent on.
Define a time span. After the master object for this dependency comes back to an Up status, monitoring of the depending objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds. Note: This setting is not available if you choose this sensor to be the Mast er object for parent . In this case, please define delays in the parent
272
or the
253
.
569
Part 6: Ajax Web Interface—Device and Sensor Setup | 8 Sensor Settings
39 HTTP Transaction Sensor
570
Access Right s
User Group Access Define which user group(s) will have access to the object you're editing. A table with user groups and right is shown; it contains all user groups from your setup. For each user group you can choose from the following access rights:
§ Inherit ed: Use the settings of the parent object.
§ None: Users in this group cannot see or edit the object. The object does not show up in lists and in the device tree.
Exception: If a child object is visible to the user, the object is visible in the device tree, though not accessible.
§ Read: Users in this group can see the object and review its monitoring results.
§ Writ e: Users in this group can see the object, review its monitoring results, and edit the object's settings. They cannot edit access rights settings.
§ Full: Users in this group can see the object, review its monitoring results, edit the object's settings, and edit access rights settings.
You can create new user groups in the
1861
settings. To automatically set all objects further down in the hierarchy to inherit this object's access rights, set a check mark for the Revert children's access right s t o inherit ed option.
For more details about access rights, please see section
94
.
Smart URL Replacement
Instead of entering a complete address in the URL field of an HTTP sensor, you can merely enter the protocol followed by colon and three slashes (that means you can enter either http:/// or https:/// or even a simple slash / as equivalent for http:/// ). PRTG will then fill in the parent device's IP address or DNS name in front of the third slash automatically. Whether this results in a valid URL or not, depends on the IP address or DNS name of the device where this
HTTP sensor is created on. In combination with cloning devices, the smart URL replacement makes it easy to create many like devices.
For example, if you create a device with DNS name www.example.com
and you put an HTTP sensor on it, you can provide values the following ways:
§ Providing the value https:/// in the URL field, PRTG will automatically create the URL https:// www.example.com/ from that.
§ Using the value /help in the URL field, PRTG will automatically create and monitor the URL http://www.example.com/help
§ It is also possible to provide a port number in the URL field which will be taken over by the device's DNS name and internally added, for example, http://:8080/
28.05.2014
28.05.2014
Part 6: Ajax Web Interface—Device and Sensor Setup | 8 Sensor Settings
39 HTTP Transaction Sensor
Note: Smart URL replacement does not work for sensors running on the "Probe Device".
More
Knowledge Base: Configuration Tips for HTTP Transaction Sensors needed
§ http://kb.paessler.com/en/topic/443
Edit Sensor Channels
In order to change display settings, spike filter, and limits, please switch to the sensor's
Overview tab and click on the gear icon of a specific channel. For detailed information, please see
1709
section.
Notifications
Click on the Not ificat ions tab to change notification triggers. For detailed information, please see
Sensor Not ificat ions Set t ings
1716
section.
Others
For more general information about settings, please see
142
section.
571
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 14 Welcome to PRTG Network Monitor
- 15 About this Document
- 16 Key Features
- 18 New in This Version
- 19 Available Licenses
- 21 System Requirements
- 23 Detailed System Requirements
- 32 Quick Start Guide
- 33 ONE—Download, Installation, and First Login
- 36 TWO—Using the Configuration Guru
- 44 Installing the Software
- 45 Download PRTG
- 47 Update From Previous Versions
- 51 Install a PRTG Core Server
- 56 Install a PRTG Cluster
- 57 Enter a License Key
- 60 Activate the Product
- 62 Install a PRTG Remote Probe
- 67 Install the Enterprise Console
- 71 Uninstall PRTG Products
- 76 Understanding Basic Concepts
- 77 Architecture and User Interfaces
- 81 Clustering
- 83 Object Hierarchy
- 87 Inheritance of Settings
- 89 Tags
- 90 Dependencies
- 91 Scheduling
- 92 Notifying
- 93 Data Reporting
- 94 User Access Rights
- 97 IPv6
- 100 Ajax Web Interface—Basic Procedures
- 102 Login
- 105 SSL Certificate Warning
- 108 General Layout
- 121 Sensor States
- 124 Review Monitoring Data
- 130 Compare Sensors
- 133 Historic Data Reports
- 138 Similar Sensors
- 142 Object Settings
- 144 Alarms
- 147 Logs
- 149 Tickets
- 156 Working with Table Lists
- 159 Object Selector
- 160 Priority and Favorites
- 162 Pause
- 163 Context Menus
- 174 Hover Popup
- 175 Main Menu Structure
- 188 Ajax Web Interface—Device and Sensor Setup
- 190 Auto-Discovery
- 204 Create Objects Manually
- 205 Add a Group
- 211 Add a Device
- 220 Add a Sensor
- 222 Manage Device Tree
- 224 Root Group Settings
- 238 Probe Settings
- 253 Group Settings
- 272 Device Settings
- 290 Sensor Settings
- 291 List of Available Sensor Types
- 309 Active Directory Replication Errors Sensor
- 316 ADO SQL Sensor
- 323 Amazon CloudWatch Sensor
- 331 AVM FRITZ!Box WAN Interface Sensor
- 337 Cisco IP SLA Sensor
- 343 Citrix XenServer Host Sensor
- 349 Citrix XenServer Virtual Machine Sensor
- 355 Cluster Probe Health Sensor
- 359 Core Health Sensor
- 363 Dell PowerVault MDi Sensor
- 369 DHCP Sensor
- 376 DNS Sensor
- 382 Enterprise Virtual Array Sensor
- 389 Event Log (Windows API) Sensor
- 397 Exchange Backup (Powershell) Sensor
- 404 Exchange Database (Powershell) Sensor
- 411 Exchange Mailbox (Powershell) Sensor
- 418 Exchange Mail Queue (Powershell) Sensor
- 424 Exchange Public Folder (Powershell) Sensor
- 431 EXE/Script Sensor
- 440 EXE/Script Advanced Sensor
- 449 File Sensor
- 455 File Content Sensor
- 461 Folder Sensor
- 467 FTP Sensor
- 473 FTP Server File Count Sensor
- 479 Google Analytics Sensor
- 486 HTTP Sensor
- 493 HTTP Advanced Sensor
- 505 HTTP Apache ModStatus PerfStats Sensor
- 512 HTTP Apache ModStatus Totals Sensor
- 519 HTTP Content Sensor
- 528 HTTP Full Web Page Sensor
- 536 HTTP Push Count Sensor
- 542 HTTP Push Data Sensor
- 549 HTTP Push Data Advanced Sensor
- 556 HTTP SSL Certificate Expiry Sensor
- 562 HTTP Transaction Sensor
- 572 HTTP XML/REST Value Sensor
- 583 Hyper-V Cluster Shared Volume Disk Free Sensor
- 590 Hyper-V Host Server Sensor
- 596 Hyper-V Virtual Machine Sensor
- 604 Hyper-V Virtual Network Adapter Sensor
- 611 Hyper-V Virtual Storage Device Sensor
- 618 IMAP Sensor
- 629 INI File Content Check Sensor
- 635 IP on DNS Blacklist Sensor
- 641 IPFIX Sensor
- 649 IPFIX (Custom) Sensor
- 657 IPMI System Health Sensor
- 664 jFlow V5 Sensor
- 672 jFlow V5 (Custom) Sensor
- 680 LDAP Sensor
- 685 Microsoft SQL Sensor
- 693 MySQL Sensor
- 700 NetFlow V5 Sensor
- 708 NetFlow V5 (Custom) Sensor
- 716 NetFlow V9 Sensor
- 724 NetFlow V9 (Custom) Sensor
- 732 Oracle SQL Sensor
- 740 Packet Sniffer Sensor
- 748 Packet Sniffer (Custom) Sensor
- 755 Passive Application Performance Sensor
- 761 PerfCounter Custom Sensor
- 768 PerfCounter IIS Application Pool Sensor
- 775 Ping Sensor
- 781 Ping Jitter Sensor
- 786 Pingdom Sensor
- 792 POP3 Sensor
- 798 POP3 Email Count Sensor
- 804 Port Sensor
- 811 Port Range Sensor
- 816 Probe Health Sensor
- 820 QoS (Quality of Service) One Way Sensor
- 826 QoS (Quality of Service) Round Trip Sensor
- 832 RADIUS Sensor
- 837 RDP (Remote Desktop) Sensor
- 842 SCVMM Host Sensor
- 849 SCVMM Virtual Machine Sensor
- 856 Sensor Factory Sensor
- 871 sFlow Sensor
- 879 sFlow (Custom) Sensor
- 887 SFTP Secure File Transfer Protocol Sensor
- 893 Share Disk Free Sensor
- 899 SIP Options Ping Sensor
- 905 SMTP Sensor
- 911 SMTP&IMAP Round Trip Sensor
- 919 SMTP&POP3 Round Trip Sensor
- 927 SNMP APC Hardware Sensor
- 933 SNMP Cisco ADSL Sensor
- 938 SNMP Cisco ASA VPN Connections Sensor
- 943 SNMP Cisco ASA VPN Traffic Sensor
- 948 SNMP Cisco ASA VPN Users Sensor
- 953 SNMP Cisco CBQoS Sensor
- 958 SNMP Cisco System Health Sensor
- 964 SNMP Cisco UCS Chassis Sensor
- 970 SNMP Cisco UCS Physical Disk Sensor
- 976 SNMP Cisco UCS System Health Sensor
- 982 SNMP CPU Load Sensor
- 987 SNMP Custom Sensor
- 994 SNMP Custom String Sensor
- 1002 SNMP Dell Hardware Sensor
- 1008 SNMP Dell PowerEdge Physical Disk Sensor
- 1014 SNMP Dell PowerEdge System Health Sensor
- 1020 SNMP Disk Free Sensor
- 1026 SNMP GSA System Health Sensor
- 1031 SNMP Hardware Status Sensor
- 1036 SNMP HP LaserJet Hardware Sensor
- 1042 SNMP HP ProLiant Logical Disk Sensor
- 1048 SNMP HP ProLiant Memory Controller Sensor
- 1054 SNMP HP ProLiant Network Interface Sensor
- 1060 SNMP HP ProLiant Physical Disk Sensor
- 1066 SNMP HP ProLiant System Health Sensor
- 1072 SNMP IBM System X Logical Disk Sensor
- 1078 SNMP IBM System X Physical Disk Sensor
- 1084 SNMP IBM System X Physical Memory Sensor
- 1090 SNMP IBM System X System Health Sensor
- 1096 SNMP interSeptor Pro Environment Sensor
- 1102 SNMP LenovoEMC Physical Disk Sensor
- 1108 SNMP LenovoEMC System Health Sensor
- 1113 SNMP Library Sensor
- 1122 SNMP Linux Disk Free Sensor
- 1130 SNMP Linux Load Average Sensor
- 1135 SNMP Linux Meminfo Sensor
- 1140 SNMP Linux Physical Disk Sensor
- 1148 SNMP Memory Sensor
- 1154 SNMP NetApp Disk Free Sensor
- 1160 SNMP NetApp Enclosure Sensor
- 1166 SNMP NetApp I/O Sensor
- 1172 SNMP NetApp License Sensor
- 1178 SNMP NetApp Logical Unit Sensor
- 1184 SNMP NetApp Network Interface Sensor
- 1190 SNMP NetApp System Health Sensor
- 1196 SNMP Poseidon Environment Sensor
- 1201 SNMP Printer Sensor
- 1206 SNMP QNAP Logical Disk Sensor
- 1211 SNMP QNAP Physical Disk Sensor
- 1217 SNMP QNAP System Health Sensor
- 1222 SNMP RMON Sensor
- 1228 SNMP SonicWALL System Health Sensor
- 1233 SNMP SonicWALL VPN Traffic Sensor
- 1239 SNMP Synology Logical Disk Sensor
- 1244 SNMP Synology Physical Disk Sensor
- 1249 SNMP Synology System Health Sensor
- 1254 SNMP System Uptime Sensor
- 1259 SNMP Traffic Sensor
- 1267 SNMP Trap Receiver Sensor
- 1276 SNMP Windows Service Sensor
- 1281 SNTP Sensor
- 1286 SSH Disk Free Sensor
- 1295 SSH INodes Free Sensor
- 1301 SSH Load Average Sensor
- 1307 SSH Meminfo Sensor
- 1313 SSH Remote Ping Sensor
- 1320 SSH SAN Logical Disk Sensor
- 1327 SSH SAN Physical Disk Sensor
- 1334 SSH SAN System Health Sensor
- 1341 SSH Script Sensor
- 1350 SSH Script Advanced Sensor
- 1358 SSH VMWare ESX(i) Disk Sensor
- 1364 Syslog Receiver Sensor
- 1373 System Health Sensor
- 1377 TFTP Sensor
- 1383 Traceroute Hop Count Sensor
- 1389 Virtuozzo Container Disk Sensor
- 1395 Virtuozzo Container Network Sensor
- 1401 VMware Host Hardware (WBEM) Sensor
- 1407 VMware Host Hardware Status (SOAP) Sensor
- 1413 VMware Host Performance (SOAP) Sensor
- 1419 VMware Virtual Machine (SOAP) Sensor
- 1426 WBEM Custom Sensor
- 1432 Windows CPU Load Sensor
- 1438 Windows IIS 6.0 SMTP Received Sensor
- 1444 Windows IIS 6.0 SMTP Sent Sensor
- 1450 Windows IIS Application Sensor
- 1457 Windows Last Update Sensor
- 1463 Windows Logged In Users Sensor
- 1469 Windows MSMQ Queue Length Sensor
- 1476 Windows Network Card Sensor
- 1483 Windows Pagefile Sensor
- 1489 Windows Physical Disk Sensor
- 1496 Windows Print Queue Sensor
- 1502 Windows Registry Sensor
- 1510 Windows Scheduled Task Sensor
- 1517 Windows System Uptime Sensor
- 1523 Windows Updates Status (Powershell) Sensor
- 1529 WMI Custom Sensor
- 1536 WMI Custom String Sensor
- 1545 WMI Event Log Sensor
- 1553 WMI Exchange Server Sensor
- 1560 WMI Exchange Transport Queue Sensor
- 1567 WMI File Sensor
- 1573 WMI Free Disk Space (Multi Drive) Sensor
- 1581 WMI HDD Health Sensor
- 1587 WMI Logical Disk Sensor
- 1593 WMI Memory Sensor
- 1598 WMI Microsoft SQL Server 2005 Sensor (Deprecated)
- 1607 WMI Microsoft SQL Server 2008 Sensor
- 1615 WMI Microsoft SQL Server 2012 Sensor
- 1623 WMI Process Sensor
- 1629 WMI Remote Ping Sensor
- 1634 WMI Security Center Sensor
- 1640 WMI Service Sensor
- 1646 WMI Share Sensor
- 1653 WMI SharePoint Process Sensor
- 1659 WMI Terminal Services (Windows 2008) Sensor
- 1664 WMI Terminal Services (Windows XP/Vista/2003) Sensor
- 1669 WMI UTC Time Sensor
- 1674 WMI Vital System Data (V2) Sensor
- 1680 WMI Volume Sensor
- 1686 WMI Volume Fragmentation Sensor
- 1693 WMI Windows Version Sensor
- 1699 WSUS Statistics Sensor
- 1706 Additional Sensor Types (Custom Sensors)
- 1709 Sensor Channels Settings
- 1716 Sensor Notifications Settings
- 1726 Ajax Web Interface—Advanced Procedures
- 1728 Toplists
- 1733 Arrange Objects
- 1734 Clone Object
- 1736 Multi-Edit
- 1741 Create Device Template
- 1744 Geo Maps
- 1749 Notifications
- 1751 Setting Up Notifications Based on Sensor Limits: Example
- 1759 Libraries
- 1762 Libraries Step By Step
- 1766 Management
- 1768 Libraries and Node Settings
- 1774 Context Menus
- 1775 Reports
- 1778 Reports Step By Step
- 1781 View and Run Reports
- 1784 Reports Settings
- 1794 Maps
- 1797 Maps Step By Step
- 1800 Maps Designer
- 1806 Maps Settings
- 1810 Setup
- 1812 Account Settings—My Account
- 1817 Account Settings—Notifications
- 1827 Account Settings—Schedules
- 1831 System Administration—User Interface
- 1839 System Administration—Monitoring
- 1843 System Administration—Notification Delivery
- 1849 System Administration—Core & Probes
- 1855 System Administration—Cluster
- 1856 System Administration—User Accounts
- 1861 System Administration—User Groups
- 1865 System Administration—Administrative Tools
- 1869 PRTG Status—System Status
- 1878 PRTG Status—Auto-Update
- 1883 PRTG Status—Cluster Status
- 1884 PRTG Status—Activation Status
- 1885 Optional Downloads and Add-Ons
- 1887 Chrome Desktop Notifications
- 1889 Support—Contact Support
- 1894 Enterprise Console
- 1897 First Start
- 1898 General Layout
- 1902 Menu Tabs and Page Content
- 1903 Devices
- 1910 Libraries
- 1912 Sensors
- 1914 Alarms
- 1916 Maps
- 1918 Reports
- 1920 Logs
- 1922 Tickets
- 1924 Setup
- 1926 Search Results
- 1927 PRTG Servers
- 1930 Options
- 1936 Windows Menu Structure
- 1941 Context Menus
- 1942 Shortcuts Overview
- 1946 Other User Interfaces
- 1947 Mobile Web GUI
- 1950 Smartphone Apps
- 1954 Sensor Technologies
- 1955 Monitoring via SNMP
- 1959 Monitoring via WMI
- 1962 Monitoring via SSH
- 1964 Monitoring Bandwidth via Packet Sniffing
- 1966 Monitoring Bandwidth via Flows
- 1969 Bandwidth Monitoring Comparison
- 1971 Monitoring Quality of Service and VoIP
- 1975 Monitoring Email Round Trip
- 1977 Monitoring Backups
- 1978 Monitoring Virtual Environments
- 1987 Monitoring Databases
- 1989 Monitoring Syslogs and SNMP Traps
- 1998 System Administration Tools
- 1999 PRTG Server Administrator
- 2016 PRTG Probe Administrator
- 2028 Advanced Topics
- 2029 Active Directory Integration
- 2031 Application Programming Interface (API) Definition
- 2032 Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors
- 2036 Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors
- 2038 Define IP Ranges
- 2039 Define Lookups
- 2048 Regular Expressions
- 2049 Add Remote Probe
- 2050 Remote Probes and Multiple Probes
- 2053 Remote Probe Quick Setup
- 2059 Remote Probe Setup Using Installer
- 2064 Failover Cluster Configuration
- 2067 Failover Cluster Step by Step
- 2074 Data Storage
- 2076 Using Your Own SSL Certificate with PRTG's Web Server
- 2078 Calculating Percentiles
- 2080 Appendix
- 2081 Glossary
- 2085 List of Abbreviations
- 2088 Support and Troubleshooting
- 2089 Legal Notices