Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Server & Application Monitor (SAM). Hybrid Cloud Observability and SAM are built on the self-hosted SolarWinds Platform.

Apache (Windows) template

This SAM application monitor template retrieves Apache server statistics from the built-in Apache server-status web page using a PowerShell script.


Configure Apache to allow access to the server-status page:

  1. Log in to the target Apache Windows server.
  2. Locate the Apache configuration file, typically named httpd.conf.
  3. Append the following lines to httpd.conf to allow access to the Apache server-status page for your domain. Replace APM_host with the IP address or hostname of the SolarWinds Platform server.
    <Location /server-status>
    SetHandler server-status
    Order Deny,Allow
    Deny from all
    Allow from APM_host
    ExtendedStatus On
  4. Ensure the following line is uncommented and present in the httpd.conf file:
    LoadModule status_module modules/
  5. Restart the Apache server.


Administrator rights on the SolarWinds Platform server. All monitors run locally.

Before assigning this template to a node, set up the following argument in component monitors:


  • server: The hostname or IP address of the target Apache server. Set this argument to ${IP} to automatically replace it with the target host IP address.
  • server_port: The Apache port under which the site is running. By default, it is set to port 80.

For example, set the Scripts Arguments field to ${IP},8080

If you receive a "Cannot connect to local host" error, see this article.

Component monitors

Server Uptime

The time, in seconds, that the server has been up.

Idle Workers

The number of free workers ready to handle client connections. This value should be as high as possible. If you have no idle workers, or very few, Apache may be using all processes it is allowed and new, incoming requests must wait for older requests to finish. If so, increasing the maximum number of allowed processes in your configuration file might help with performance.

Total Accesses

The total number of accesses.

Total Traffic

The total number of kilobytes this server has served.

Server Requests Per Second

The average rate of all requests per second. The result is calculated as the total number of requests throughout the life of the server (count) and divided by the total uptime in seconds (up_time).

Server kB Per Second

The average rate of kilobytes served per second.

Server kB Per Request

The average number of kilobytes per request.

Busy Workers

The number of busy workers serving requests. This counter should be as low as possible.