Skip to content
Branch: master
Go to file

Latest commit


Failed to load latest commit information.
Latest commit message
Commit time

Apache Exporter for Prometheus Build Status

GitHub release GitHub Downloads Docker Repository on Quay Docker Pulls

Exports apache mod_status statistics via HTTP for Prometheus consumption.

With working golang environment it can be built with go get. There is a good article with build HOWTO and usage example.

Help on flags:

  -h, --help
                          Address on which to expose metrics.
                          Path under which to expose metrics.
                          URI to apache stub status page.
      --host_override=""  Override for HTTP Host header; empty string for no override.
      --insecure          Ignore server certificate if using https.
      --log.level="info"  Only log messages with the given severity or above. Valid levels: [debug, info, warn, error, fatal]
                          Set the log target and format. Example: "logger:syslog?appname=bob&local=7" or "logger:stdout?json=true"
      --version           Show application version.

Tested on Apache 2.2 and Apache 2.4.

If your server-status page is secured by http auth, add the credentials to the scrape URL following this example:


Override host name by runnning


Using Docker

Build the compatible binary

To make sure that exporter binary created by build job is suitable to run on busybox environment, generate the binary using Makefile definition. Inside project directory run:


Please be aware that binary generated using go get or go build with defaults may not work in busybox/alpine base images.

Another option is to use a docker go container to generate the binary.

Pick an appropriate go image from Inside the project directory run:

docker run --rm -v <project home>:/usr/local/go/src/ -w /usr/local/go/src/ <go docker image name> make

Build image

Run the following commands from the project root directory.

docker build -t apache_exporter .


docker run -d -p 9117:9117 apache_exporter \


Apache metrics:

# HELP apache_accesses_total Current total apache accesses (*)
# TYPE apache_accesses_total counter
# HELP apache_scoreboard Apache scoreboard statuses
# TYPE apache_scoreboard gauge
# HELP apache_sent_kilobytes_total Current total kbytes sent (*)
# TYPE apache_sent_kilobytes_total counter
# HELP apache_cpu_load CPU Load (*)
# TYPE apache_cpu_load gauge
# HELP apache_up Could the apache server be reached
# TYPE apache_up gauge
# HELP apache_uptime_seconds_total Current uptime in seconds (*)
# TYPE apache_uptime_seconds_total counter
# HELP apache_workers Apache worker statuses
# TYPE apache_workers gauge
# HELP apache_version Apache server version
# TYPE apache_version gauge
# HELP apache_duration_total Total duration of all registered requests
# TYPE apache_duration_total gauge

Metrics marked '(*)' are only available if ExtendedStatus is On in apache webserver configuration. In version 2.3.6, loading mod_status will toggle ExtendedStatus On by default.


Q. Is there a Grafana dashboard for this exporter?

A. There's a 3rd party dashboard here which seems to work.

Q. Can you add additional metrics such as reqpersec, bytespersec and bytesperreq?

A. In line with the best practices, the exporter only provides the totals and you should derive rates using PromQL.

Like that:

  • ReqPerSec : rate(apache_accesses_total[5m])
  • BytesPerSec: rate(apache_sent_kilobytes_total[5m])
  • BytesPerReq: BytesPerSec / ReqPerSec

Q. Can I monitor multiple Apache instances?

A. In line with the best practices, the answer is no. Each process being monitored should be accompanied by one exporter.

We suggest automating configuration and deployment using your favorite tools, e.g. Ansible/Chef/Kubernetes.

Q. Its not working! Apache_up shows as 0

A. When apache_up reports 0 it means the exporter is running however it is not able to connect to Apache.

Do you have this (or similar) configuration uncommented in your Apache instance?

<Location "/server-status">
    SetHandler server-status
    Require host

As documented at

Are you able to see the stats, if you run this from the Apache instance?

curl localhost/server-status?auto

If you run the exporter manually, do you see any errors?


Please include all this information if you still have issues when creating an issue.

Q. There seem to be missing metrics! I can only see apache_up and apache_cpuload.

A. Make sure that you add ?auto at the end of the scrape_uri.


The exporter was originally created by neezgee.

You can’t perform that action at this time.