> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# IBM HTTP Server Monitoring

> See which URLs on your IBM HTTP Server fail or spike in traffic, by client and status, across every web server in one place.

Components
[`Engine`](https://docs.germainux.com/deploy/germain-ux-engine)
[`JS Profiler`](https://docs.germainux.com/deploy/germain-ux-js-profiler)
[`RPA Bot Recorder`](https://docs.germainux.com/deploy/germain-ux-rpa-bot-recorder)
[`RUM JS`](https://docs.germainux.com/deploy/germain-ux-rum-js)
[`RUM Extension`](https://docs.germainux.com/deploy/germain-ux-rum-extension)

Availability
8.6.9 or later

> [card] [What Is Monitored](#what-is-monitored)
>
> Requests, clients, failures

> [card] [How It Works](#how-it-works)
>
> Log monitor and parser

> [card] [Deploy](#deploy)
>
> Two wizards on one Engine

> [card] [KPIs](#kpis)
>
> Inbound HTTP Request

## Overview

GermainUX turns every line of your IBM HTTP Server (IHS) access log into a request you can filter by URL, status, client and user. You see which URLs fail, how traffic moves through the day, and which clients hit an error, across all your IHS servers at once. Failed requests stand out from the normal traffic, and an SLA alerts you when they rise. Your team stops reading `access_log` files server by server to find out what went wrong.

> [card] Every Request, Searchable
>
> Method, path, query string, status, response size, client address and user for each request.

> [card] Failures at a Glance
>
> Requests with status `400` or higher count as failed, so error spikes on a URL or a server show up right away.

> [card] All Web Servers Together
>
> Compare traffic and failures between IHS servers in front of the same application.

> [card] Links to the Rest of the Stack
>
> Put IHS requests next to browser sessions, application logs and messaging data in the same KPIs and dashboards.

### Questions It Answers

* Which URLs return 5xx errors right now, and since when?
* Is one IHS server failing more requests than the others?
* Is traffic dropping or spiking compared with a normal day?
* Which clients or users get the failing responses?
* Which pages and resources are requested most?
* Is every IHS server still writing an access log that GermainUX receives?

## What Is Monitored

| Area | What GermainUX monitors |
| - | - |
| **Requests** | Every access-log entry: HTTP method, path, query string, status code and response size. A request with status `400` or higher counts as failed. |
| **Clients** | Client address and the authenticated user name, when the request has one |
| **Availability** | Up/down status and response time of the URLs IHS serves, checked on a schedule with [synthetic HTTP checks](https://docs.germainux.com/automation/synthetic-http-execution.md) |
| **Host** | CPU, memory, disk and network of the IHS server, and whether the server process is running. See [Linux monitoring](https://docs.germainux.com/integrations/linux-redhat-suse-monitoring.md) or [Windows monitoring](https://docs.germainux.com/integrations/windows-monitoring.md). |
| **User experience** | Real-user page performance, JavaScript errors and Session Replay for the applications IHS serves, with [RUM JS](https://docs.germainux.com/deploy/germain-ux-rum-js.md) or the [RUM Extension](https://docs.germainux.com/deploy/germain-ux-rum-extension.md) |

## Analytics, Alerts and Automation

### AI Analysis

Ask [AI Explore](https://docs.germainux.com/analytics/ai-driven-insights.md) questions such as "Which IHS URLs failed most this week?" and get the answer without building a report. [Outlier detection](https://docs.germainux.com/analytics/outlier-detection.md) flags unusual spikes or drops in request volume and failures.

### Dashboards and Reports

Build [dashboards and reports](https://docs.germainux.com/dashboards/dashboard-and-report.md) on IHS requests: volume and failure rate by server or URL, status-code distribution, and the busiest clients.

GermainUX ships the **IBM HTTP Server Overview** dashboard as a starting point. In the left menu, go to **Dashboards > All**, and then open **IBM HTTP Server Overview** in the **IBM WebSphere** folder. It has four charts:

* **Requests by Server**: the number of requests each IHS server handled
* **Failed Requests by Server (%)**: the share of requests with status `400` or higher, per server
* **Response Time**: the average and 95th-percentile request time
* **Requests by Status Code**: the number of requests per HTTP status

Each chart compares the selected period with the previous one, shown as a dashed line. **Response Time** shows data only when IHS also logs the request time: add `%D` to the end of the `LogFormat` line of the access log. Click a chart to open the **Inbound HTTP Request** KPI behind it.

![IBM HTTP Server Overview dashboard showing requests and failed requests for servers ihs-01 and ihs-02, a response-time peak and requests by status code over six hours, with the previous period as a dashed line](https://mintcdn.com/germain-ux/qPioGmu274bi5Ska/images/main/ibm-http-server-monitoring/ibm-http-server-overview-dashboard.png?fit=max\&auto=format\&n=qPioGmu274bi5Ska\&q=85\&s=b13a1f7bfad8912327aff9d119f68440)

IBM HTTP Server Overview Dashboard - GermainUX

### Analysis

Click a value on the dashboard to open it in the [Analysis](https://docs.germainux.com/dashboards/analytics-dashboard/4-analysis-dashboard.md) screen. The top row compares the selected period with the previous days and the last quarter, and shows the hourly trend. The relationships chart shows the KPI over a longer time range, with the selected period highlighted. The segmentation breakdown lists the applications, servers and URLs that changed most, and labels each one as a spike, an outlier or degraded.

In the example below, the average response time more than doubled while an application server behind IHS was down. The breakdown points to the **ihs-02** server and the `/orders/` URLs.

![Analysis screen for the Inbound HTTP Request KPI, with the average duration compared with the previous days, a response-time peak in the relationships chart, and leading factors ihs-02, Order Management and the /orders/ URLs marked as spikes](https://mintcdn.com/germain-ux/qPioGmu274bi5Ska/images/main/ibm-http-server-monitoring/ihs-inbound-http-request-analysis.png?fit=max\&auto=format\&n=qPioGmu274bi5Ska\&q=85\&s=219da7a4fd30871b3c4ad41ea57d5599)

Aggregate Analysis of IHS Response Time - GermainUX

### SLAs and Alerts

Set [SLAs](https://docs.germainux.com/analytics/slas.md) on the failure rate or request volume, and get an [alert](https://docs.germainux.com/automation/notifications.md) by email, SMS, Slack or Teams when one is breached. An SLA on request volume tells you when a server stops sending data.

### Correlation with Other Technologies

[Correlate](https://docs.germainux.com/analytics/correlation-and-tracing.md) IHS requests with browser sessions and with the systems behind IHS, such as [IBM WebSphere MQ](https://docs.germainux.com/integrations/websphere-mq-monitoring.md), to follow a failed request to its cause.

## How It Works

access\_log
Log Directory Monitor
Access Log Parser
KPIs
Alerts

You deploy two components to the GermainUX Engine that can read the IHS log directory:

| Component | What it does |
| - | - |
| **IHS Log Directory Monitor** | Watches the IHS log directory and sends new lines of the file named `access_log` to the access log parser |
| **IHS Access Log Parser** | Reads each access-log line and stores it as an **Inbound HTTP Request** transaction, with the request, client, status and size |

The Engine reads the log files directly, so it runs on the IHS host or on a server that can read the log directory. See [File and Log Monitoring](https://docs.germainux.com/integrations/file-log-monitoring.md) for how GermainUX reads log files.

## Before You Start

* A GermainUX Engine is deployed on the IHS host, or on a server that can read its log directory. See [GermainUX Engine](https://docs.germainux.com/deploy/germain-ux-engine.md).
* The Engine's account can read the IHS log directory, for example `/opt/IBM/HTTPServer/logs`.
* IHS writes its access log to a file named `access_log` in the `common` log format, as the default IHS configuration does.

## Deploy

**1. Check the access log format**

In the IHS `httpd.conf`, check that the access log uses the `common` format:

```apache httpd.conf theme={null}
LogFormat "%h %l %u %t \"%r\" %>s %b" common
CustomLog logs/access_log common
```

If you changed these lines, restart IHS.

**2. Deploy the access log parser**

In the left menu, go to **Settings > Wizards**. On the **Parser Deployment** card, click **Add**, and fill in the fields:

| Field | Value |
| - | - |
| **Component Type** | `IHS Access Log Parser` |
| **Monitored Application** | The application the IHS data belongs to |
| **Monitor Name** | A name you recognize, for example `IHS Access Log Parser - web-01` |
| **Monitoring Node** | The Monitoring Node and Engine that can read the IHS log directory |

Finish the wizard.

![Parser Deployment wizard with IHS Access Log Parser selected as the Component Type](https://mintcdn.com/germain-ux/qPioGmu274bi5Ska/images/main/ibm-http-server-monitoring/parser-deployment-ihs-access-log-parser.png?fit=max\&auto=format\&n=qPioGmu274bi5Ska\&q=85\&s=1e30ba960052413a86c878821cc94f9e)

Parser Deployment Wizard with the IHS Access Log Parser - GermainUX

**3. Deploy the log directory monitor**

On the **Directory Monitor Deployment** card, click **Add**, and fill in the fields:

| Field | Value |
| - | - |
| **Component Type** | `IHS Log Directory Monitor` |
| **Directory** | The IHS log directory, for example `/opt/IBM/HTTPServer/logs` |
| **Monitor Name** | For example `IHS Log Directory Monitor - web-01` |
| **Monitoring Node** | The same Monitoring Node and Engine as the parser |

Finish the wizard. GermainUX starts reading the access log.

![Directory Monitor Deployment wizard with IHS Log Directory Monitor selected as the Component Type](https://mintcdn.com/germain-ux/qPioGmu274bi5Ska/images/main/ibm-http-server-monitoring/directory-monitor-deployment-ihs.png?fit=max\&auto=format\&n=qPioGmu274bi5Ska\&q=85\&s=504127d2f7fe0f7543a58cd39c26fefb)

Directory Monitor Deployment Wizard for IHS Logs - GermainUX

Repeat both steps for each IHS server.

## Validate

**1. Send a test request**

From any machine that can reach the IHS server, request a page and a path that doesn't exist:

```bash theme={null}
curl -s -o /dev/null -w "%{http_code}\n" http://IHS_HOST/
curl -s -o /dev/null -w "%{http_code}\n" http://IHS_HOST/germainux-test-missing
```

Replace `IHS_HOST` with the host name of the IHS server.

**2. Find the requests in GermainUX**

In GermainUX Workspace, open the **Inbound HTTP Request** KPI and look for the requests to `/` and `/germainux-test-missing`. Check that each one shows its status, and that the `404` request counts as failed.

## Troubleshooting

> [accordion] No IHS requests appear
>
> Check that both components run on the same Engine, that the Engine's account can read the log directory, and that the access log file is named `access_log`. A log written to another file name, such as `access.log` or `ssl_access_log`, isn't picked up.

> [accordion] Some access-log lines are missing
>
> GermainUX skips lines that don't match the `common` format. This happens when a `CustomLog` line uses another format, such as `combined`. Use the `common` format for the access log in the monitored directory.

## Security and Privacy

IBM HTTP Server monitoring data includes personal data:

* **Identity data**: the client address and the authenticated user name of each request
* **URLs**: the request path and query string. Query strings can contain email addresses, IDs or tokens, so treat them as possibly containing personal or customer data.

To mask, anonymize or exclude this data, see [Data Privacy](https://docs.germainux.com/management/compliance-privacy-and-security/data-privacy.md).

## KPIs

| KPI | What it holds | Data model |
| - | - | - |
| **Inbound HTTP Request** | One transaction per access-log line, with the request, client, status and size | `InboundHttpRequest` |

GermainUX uses this shared KPI for other web servers too. It has no IHS-specific default SLA. Add the thresholds you need. See [KPIs](https://docs.germainux.com/analytics/kpis.md) and [SLAs](https://docs.germainux.com/analytics/slas.md).

## Related Documentation

> [card] [IBM WebSphere MQ](https://docs.germainux.com/integrations/websphere-mq-monitoring.md)
>
> Queues and messaging behind IHS

> [card] [File and Log Monitoring](https://docs.germainux.com/integrations/file-log-monitoring.md)
>
> How GermainUX reads log files

> [card] [Automation](https://docs.germainux.com/automation.md)
>
> More Automation Features

## Get Help

The GermainUX team can help you monitor IHS servers that use a custom log format or file name.

> [card] [Contact GermainUX Support](https://docs.germainux.com/getting-started/support.md)
>
> The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

> [card] Can't Find What You Need?
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.