Content Previous Next

PRTG Manual: HTTP Apache ModStatus PerfStats Sensor

<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: 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

For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Sensor in Other Languages

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

This sensor does not support Secure Remote Password (SRP) ciphers.
This sensor supports smart URL replacement.
This sensor supports the IPv6 protocol.

This sensor has a low performance impact.

See the Knowledge Base: Which HTTP status code leads to which HTTP sensor status?

Add Sensor

The Add Sensor 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.

Basic Sensor Settings

Click the Settings tab of a sensor to change its settings.

Basic Sensor Settings

Setting	Description
Sensor Name	Enter a name to identify the sensor.
Parent Tags	Shows tags that the sensor inherits from its parent device, parent group, and parent probe. This setting is for your information only. You cannot change it.
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. 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. The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor: httpsensor httpapachemodstatusperfstatssensor apache
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 for details. For some sensors, you can explicitly define the monitoring target in the sensor settings.

HTTP Specific

Setting	Description
Timeout (Sec.)	Enter a timeout in seconds for the request. Enter an integer. The maximum timeout value is 900 seconds (15 minutes). If the reply takes longer than this value, the sensor cancels the request and shows a corresponding error message.
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. 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.

Setting

Description

Timeout (Sec.)

Enter a timeout in seconds for the request. Enter an integer. The maximum timeout value is 900 seconds (15 minutes).

If the reply takes longer than this value, the sensor cancels the request and shows a corresponding error message.

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.

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.

This sensor implicitly supports SNI, an extension to the Transport Layer Security (TLS) protocol.

Authentication

Setting	Description
Authentication	Define if authentication is necessary on the web page: Web page does not need authentication Web page needs authentication
User Name	If the proxy requires authentication, enter the user name for the proxy 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.

Sensor Display

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).
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.

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).

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

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 if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.

For more information, see section Inheritance of Settings.

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.

Proxy Settings for HTTP Sensors

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

Scanning Interval

For more information, see section Root Group Settings, section Scanning Interval.

Schedules, Dependencies, and Maintenance Window

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.

Schedules, Dependencies, and Maintenance Window

For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.

Access Rights

For more information, see section Root Group Settings, section 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:

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

Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.

Channel	Description
BusyWorkers	The number of busy worker threads
BytesPerReq	The number of bytes per request
CPULoad	The CPU load This channel is the primary channel by default.
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.
IdleWorkers	The number of idle worker threads
ReqPerSec	The number of requests per second
Uptime	The server uptime

Knowledge Base

Which HTTP status code leads to which HTTP sensor status?

https://kb.paessler.com/en/topic/65731

What security features does PRTG include?

https://kb.paessler.com/en/topic/61108

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

https://kb.paessler.com/en/topic/85284