All Integrations
StandardsTigerOps agent + mod_status

Apache HTTP Server Integration

Worker thread metrics, request throughput, and scoreboard status monitoring for Apache HTTP Server. Detect worker saturation before it impacts users with AI-powered predictive alerting.

Setup

How It Works

01

Enable mod_status

Enable mod_status in your Apache configuration and expose the /server-status endpoint with ExtendedStatus On. Restrict access to localhost or the TigerOps agent IP.

02

Install TigerOps Agent

Install the TigerOps agent on your Apache host. It auto-discovers the mod_status endpoint and begins collecting worker, request, and connection metrics every 10 seconds.

03

Configure Log Ingestion

Point Apache access logs to TigerOps log ingestion for request-level latency, status code distribution, and upstream error tracking. Use the combined or JSON log format.

04

Set Worker Saturation Alerts

Configure alerts for worker thread saturation (idle workers below threshold), request queue depth, and response time percentiles. TigerOps correlates saturation with traffic spikes.

Capabilities

What You Get Out of the Box

Scoreboard Status Parsing

Parse the Apache scoreboard characters (_SRWKDCLGI) to track exact worker states: idle, sending reply, reading request, keepalive, DNS lookup, closing, logging, gracefully finishing, and idle cleanup.

Worker Thread Saturation Detection

Monitor idle vs. busy worker ratios in real time. TigerOps alerts before worker pools saturate using predictive thresholds that account for traffic time-of-day patterns.

Request Throughput & Bandwidth

Track requests per second, bytes per second, bytes per request, and total accesses from mod_status. Correlate throughput drops with deployment events or upstream failures.

Virtual Host Metrics

Segment request metrics by virtual host using Apache access log parsing. TigerOps tracks per-vhost request rates, error rates, and p99 latency for multi-tenant Apache deployments.

MPM-Aware Monitoring

Support for prefork, worker, and event MPMs. TigerOps adapts scoreboard interpretation and worker capacity calculations based on your detected MPM configuration.

SSL/TLS Certificate Expiry Tracking

Monitor SSL certificate expiry dates for all virtual hosts. TigerOps alerts 30 and 7 days before expiry, including certificates managed by mod_ssl and mod_md.

Configuration

Apache mod_status Configuration

Enable mod_status with ExtendedStatus and configure the TigerOps agent to scrape it.

apache-tigerops.conf
# /etc/apache2/conf-available/mod-status.conf
# Enable extended status (required for full scoreboard data)
ExtendedStatus On

<Location "/server-status">
  SetHandler server-status
  # Restrict to localhost only
  Require local
  # Or allow TigerOps agent IP:
  # Require ip 10.0.1.50
</Location>

# Access log with latency and virtual host fields
LogFormat "%v %h %l %u %t \"%r\" %>s %b %D \"%{Referer}i\" \"%{User-Agent}i\"" combined_vhost
CustomLog /var/log/apache2/access.log combined_vhost

# --- TigerOps Agent Configuration ---
# /etc/tigerops-agent/conf.d/apache.yaml
# integrations:
#   apache:
#     status_url: http://127.0.0.1/server-status?auto
#     scrape_interval: 10s
#     log_files:
#       - /var/log/apache2/access.log
#       - /var/log/apache2/error.log
#     log_format: combined_vhost
FAQ

Common Questions

Does TigerOps require mod_status to be internet-accessible?

No. The TigerOps agent runs locally on your Apache host and reads mod_status from 127.0.0.1. You can restrict the /server-status endpoint to localhost only, which is the recommended security configuration.

Which Apache MPMs does TigerOps support?

TigerOps supports all three Apache MPMs: prefork (process-based), worker (hybrid thread/process), and event (async). The agent detects your MPM and adjusts worker capacity metrics accordingly.

Can TigerOps monitor multiple Apache virtual hosts separately?

Yes. Configure Apache access logs with the %v (virtual host) field in your LogFormat. TigerOps parses per-vhost request rates, status code distributions, and response times from access logs.

How does TigerOps collect Apache request latency?

Add %D (request time in microseconds) to your Apache LogFormat. TigerOps parses this field to compute p50, p95, and p99 request latency histograms per virtual host and URL pattern.

Can I monitor Apache on Windows with TigerOps?

Yes. The TigerOps agent runs on Windows and collects mod_status metrics from Apache on Windows (XAMPP, manual installs). The agent also reads Windows Event Log entries for Apache service events.

Get Started

Stop Guessing When Apache Workers Will Saturate

Predictive worker saturation alerts, scoreboard visibility, and request latency tracking. Install in 5 minutes.