Skip to main content
Availability8.6.9 or later

What Is Monitored

Requests, clients, failures

How It Works

Log monitor and parser

Deploy

Two wizards on one Engine

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.

Every Request, Searchable

Method, path, query string, status, response size, client address and user for each request.

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.

All Web Servers Together

Compare traffic and failures between IHS servers in front of the same application.

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

Analytics, Alerts and Automation

AI Analysis

Ask AI Explore questions such as “Which IHS URLs failed most this week?” and get the answer without building a report. Outlier detection flags unusual spikes or drops in request volume and failures.

Dashboards and Reports

Build dashboards and reports 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

IBM HTTP Server Overview Dashboard - GermainUX

Analysis

Click a value on the dashboard to open it in the Analysis 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

Aggregate Analysis of IHS Response Time - GermainUX

SLAs and Alerts

Set SLAs on the failure rate or request volume, and get an alert 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 IHS requests with browser sessions and with the systems behind IHS, such as IBM WebSphere MQ, to follow a failed request to its cause.

How It Works

access_logLog Directory MonitorAccess Log ParserKPIsAlerts
You deploy two components to the GermainUX Engine that can read the IHS log directory: 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 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.
  • 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:
httpd.conf
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:Finish the wizard.
Parser Deployment wizard with IHS Access Log Parser selected as the Component Type

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:Finish the wizard. GermainUX starts reading the access log.
Directory Monitor Deployment wizard with IHS Log Directory Monitor selected as the Component Type

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:
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

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

KPIs

GermainUX uses this shared KPI for other web servers too. It has no IHS-specific default SLA. Add the thresholds you need. See KPIs and SLAs.

IBM WebSphere MQ

Queues and messaging behind IHS

File and Log Monitoring

How GermainUX reads log files

Automation

More Automation Features

Get Help

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

Contact GermainUX Support

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.

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.