Learn how to - Monitor Apache Web Server with Prometheus and Grafana in 5 minutes

Learn how to – Monitor Apache Web Server with Prometheus and Grafana in 5 minutes.

Welcome to our guide on how to Monitor Apache Web Server with Prometheus and Grafana in less than 5 minutes. This setup should work for any version of Apache web server running on any flavor of Linux. We have other Prometheus Monitoring tutorials:

If you are following this guide, I expect that you have Prometheus server installed and running, you can refer to our guide for a fresh installation of Prometheus server on Ubuntu or CentOS server.

Install Prometheus Server on CentOS / Debian / Ubuntu

Follow these setup steps to have your Apache Web Server metrics stored on Prometheus and visualized using Grafana.

Step 1: Install Apache Prometheus exporter

Install curl utility if not already present in your machine.

### Ubuntu / Debian ###
sudo apt update && sudo apt install wget curl

### CentOS / RHEL / Fedora ###
sudo yum -y install curl wget

Check the latest release of Apache Prometheus exporter.

curl -s https://api.github.com/repos/Lusitaniae/apache_exporter/releases/latest|grep browser_download_url|grep linux-amd64|cut -d '"' -f 4|wget -qi -

Extract downloaded archive:

tar xvf apache_exporter-*.linux-amd64.tar.gz
sudo cp apache_exporter-*.linux-amd64/apache_exporter /usr/local/bin
sudo chmod +x /usr/local/bin/apache_exporter

Make sure apache_exporter is executable from your current SHELL:

$ apache_exporter --version
apache_exporter, version 0.11.0 (branch: HEAD, revision: c64b4496c4658d72c58fbda905a70c06a4b7f0c7)
  build user:       root@2ec369d6fc9a
  build date:       20210729-10:04:27
  go version:       go1.16.6
  platform:         linux/amd64

Step 2: Create Apache exporter service

First, add prometheus user which will run the service:

sudo groupadd --system prometheus
sudo useradd -s /sbin/nologin --system -g prometheus prometheus

Then proceed to create a systemd service unit file:

sudo vim /etc/systemd/system/apache_exporter.service

Add below content:

[Unit]
Description=Prometheus
Documentation=https://github.com/Lusitaniae/apache_exporter
Wants=network-online.target
After=network-online.target

[Service]
Type=simple
User=prometheus
Group=prometheus
ExecReload=/bin/kill -HUP $MAINPID
ExecStart=/usr/local/bin/apache_exporter 
  --insecure 
  --scrape_uri=http://localhost/server-status/?auto 
  --telemetry.address=0.0.0.0:9117 
  --telemetry.endpoint=/metrics

SyslogIdentifier=apache_exporter
Restart=always

[Install]
WantedBy=multi-user.target

The service will listen on port 9117, and metrics exposed on /metrics URI. If Apache metrics are not on http://localhost/server-status/?auto you’ll need to change the URL.

With Init System

For Init system like CentOS 6.x, create an init script under /etc/init.d/

sudo vim /etc/init.d/apache_exporter

Add:

#!/bin/bash
# Author: Josphat Mutai, kiplangatmtai@gmail.com , https://github.com/jmutai
# apache_exporter     This shell script takes care of starting and stopping Prometheus apache exporter 
#
# chkconfig: 2345 80 80
# description: Prometheus apache exporter  start script
# processname: apache_exporter
# pidfile: /var/run/apache_exporter.pid

# Source function library.
. /etc/rc.d/init.d/functions

RETVAL=0
PROGNAME=apache_exporter
PROG=/usr/local/bin/${PROGNAME}
RUNAS=prometheus
LOCKFILE=/var/lock/subsys/${PROGNAME}
PIDFILE=/var/run/${PROGNAME}.pid
LOGFILE=/var/log/${PROGNAME}.log
DAEMON_SYSCONFIG=/etc/sysconfig/${PROGNAME}

# GO CPU core Limit

#GOMAXPROCS=$(grep -c ^processor /proc/cpuinfo)
GOMAXPROCS=1

# Source config

. ${DAEMON_SYSCONFIG}

start() {
    if [[ -f $PIDFILE ]] > /dev/null; then
        echo "apache_exporter  is already running"
        exit 0
    fi

    echo -n "Starting apache_exporter  service…"
    daemonize -u ${USER} -p ${PIDFILE} -l ${LOCKFILE} -a -e ${LOGFILE} -o ${LOGFILE} ${PROG} ${ARGS}
    RETVAL=$?
    echo ""
    return $RETVAL
}

stop() {
    if [ ! -f "$PIDFILE" ] || ! kill -0 $(cat "$PIDFILE"); then
        echo "Service not running"
        return 1
    fi
    echo 'Stopping service…'
    #kill -15 $(cat "$PIDFILE") && rm -f "$PIDFILE"
    killproc -p ${PIDFILE} -d 10 ${PROG}
    RETVAL=$?
    echo
    [ $RETVAL = 0 ] && rm -f ${LOCKFILE} ${PIDFILE}
    return $RETVAL
}

status() {
    if [ -f "$PIDFILE" ] || kill -0 $(cat "$PIDFILE"); then
      echo "apache exporter  service running..."
      echo "Service PID: `cat $PIDFILE`"
    else
      echo "Service not running"
    fi
     RETVAL=$?
     return $RETVAL
}

# Call function
case "$1" in
    start)
        start
        ;;
    stop)
        stop
        ;;
    restart)
        stop
        start
        ;;
    status)
        status
        ;;
    *)
        echo "Usage: $0 {start|stop|restart}"
        exit 2
esac

Install daemonize package:

sudo yum -y install daemonize

Create Arguments configuration file:

sudo vim /etc/sysconfig/apache_exporter

Add:

ARGS="--insecure --scrape_uri=http://localhost/server-status/?auto --telemetry.address=0.0.0.0:9117 --telemetry.endpoint=/metrics"

Test the script:

$ sudo /etc/init.d/apache_exporter
Usage: /etc/init.d/apache_exporter {start|stop|restart}

Step 3: Start Apache exporter service

For Systemd:

sudo systemctl daemon-reload
sudo systemctl start apache_exporter.service
sudo systemctl enable apache_exporter.service

For Init systems without Systemd.

sudo /etc/init.d/apache_exporter start
sudo chkconfig apache_exporter on

You can verify service status using:

### Systemd ###
$ systemctl status apache_exporter.service
● apache_exporter.service - Prometheus
     Loaded: loaded (/etc/systemd/system/apache_exporter.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2021-09-01 10:12:33 UTC; 9s ago
       Docs: https://github.com/Lusitaniae/apache_exporter
   Main PID: 14652 (apache_exporter)
      Tasks: 6 (limit: 2340)
     Memory: 2.6M
        CPU: 5ms
     CGroup: /system.slice/apache_exporter.service
             └─14652 /usr/local/bin/apache_exporter --insecure --scrape_uri=http://localhost/server-status/?auto --telemetry.address=0.0.0.0:9117 --telemetry.endpoint=/metrics

Sep 01 10:12:33 debian-bullseye-01 systemd[1]: Started Prometheus.
Sep 01 10:12:33 debian-bullseye-01 apache_exporter[14652]: time="2021-09-01T10:12:33Z" level=info msg="Starting apache_exporter (version=0.10.0, branch=HEAD, revision=c64b4496c4658d72c58fbda905a70c>
Sep 01 10:12:33 debian-bullseye-01 apache_exporter[14652]: time="2021-09-01T10:12:33Z" level=info msg="Build context (go=go1.16.6, user=root@2ec369d6fc9a, date=20210729-10:04:27)" source="apache_ex>
Sep 01 10:12:33 debian-bullseye-01 apache_exporter[14652]: time="2021-09-01T10:12:33Z" level=info msg="Starting Server: 0.0.0.0:9117" source="apache_exporter.go:596"
Sep 01 10:12:33 debian-bullseye-01 apache_exporter[14652]: time="2021-09-01T10:12:33Z" level=info msg="Collect from: http://localhost/server-status/?auto" source="apache_exporter.go:597"
Sep 01 10:12:33 debian-bullseye-01 apache_exporter[14652]: time="2021-09-01T10:12:33Z" level=info msg="listening and wait for graceful stop" source="apache_exporter.go:601"

### Init System ###
$ sudo /etc/init.d/apache_exporter status
apache exporter  service running...
Service PID: 1970

Check service status:

$ sudo chkconfig --list | grep apache_exporter
apache_exporter 0:off   1:off   2:on    3:on    4:on    5:on    6:off

Confirm the port is listening for requests.

$ sudo ss -tunelp | grep 9117
tcp    LISTEN     0      128                   :::9117                 :::*      users:(("apache_exporter",1970,6)) ino:1823474168 sk:ffff880341cd7800

Step 4: Add exporter job to Prometheus

Add a job to the Prometheus server for scraping metrics. Edit /etc/prometheus/prometheus.yml

# Apache Servers
  - job_name: apache1
    static_configs:
      - targets: ['10.1.10.15:9117']
        labels:
          alias: server1-apache

  - job_name: apache2
    static_configs:
      - targets: ['10.1.10.16:9117']
        labels:
          alias: server2-apache

Restart prometheus service for scraping to start

sudo systemctl restart prometheus

Test access to port 9117 from Prometheus server

$ telnet 10.1.10.15 9117
Trying 10.1.10.15...
Connected to 10.1.10.15.
Escape character is '^]'.
^]

Step 5: Add Dashboard to Grafana

The final step is to create your own Dashboard for visualizing Apache metrics. For this demo, we’ll use Grafana Dashboards by Ricardo F. The dashboard ID is 3894. You should have Prometheus Data source already added to Grafana, or use the link Add Prometheus data source to add one.

Once the data source has been added, Import Apache Grafana Dashboard by navigating to Dashboard > Import. Use 3894 for Grafana Dashboard ID.

Monitor Apache Web Server with Prometheus and Grafana in 5 minutes 1

Give it a descriptive name and select Prometheus data source added earlier.

Monitor Apache Web Server with Prometheus and Grafana in 5 minutes 2

Click “Import” button to start using the dashboard. After a few minutes, the metrics should start showing.

Monitor Apache Web Server with Prometheus and Grafana in 5 minutes 3

Select a different host to show metrics for using the drop-down menu at the top of the metrics dashboard. In my next Apache monitoring guide, I’ll cover the use of InfluxDB and Grafana to monitor Apache Web server.

Other monitoring articles available in our website are:

Cart

Learn how to – Monitor Apache Web Server with Prometheus and Grafana in 5 minutes