Prometheus Metrics exporter for HTTP daemons (Apache, nginx, ...) based on access log file scraping.
current(Dockerfile) - latest (unstable) imagev1.0.0-rc3(Dockerfile) - Release Candidate
httpd-exporter is in Beta phase. It is running stable in a commercial Kubernetes environment. However, it cannot be regarded as mature because the project was initiated for and tested in that very specific environment only.
Main documentation is available here.
- Configuration File
httpd-exporter requires a configuration file describing the log files to scrape and the metrics to be produced. You need to copy/mount your configuration in directory /etc/httpd-exporter or provide the location via environment variable HTTPD_EXPORTER_CONFIG_FILE. See the Configuration page for more details.
- HTTPD Log Files
httpd-exporter scrapes log files. The configuration file must list all the locations where these log files are available. Make sure you mount your log files to be analyzed into the container at the right place. Please notice that - due to a Docker limitation - httpd-exporter requires to run as user root in order to have access to Docker container log files.
- Metrics File
httpd-exporter does not serve the metrics itself but requires an additional HTTP server, such as nginx, Apache, Tomcat, et al. The metrics are written to the location as given in the configuration file, preferrably at /var/www/html/metrics. Therefore, it is required that httpd-exporter has this directory mounted and it is writable. The HTTP server must expose the metrics at this URL: http://<your-server-name>:9386/metrics. This is the reserved port for httpd-exporter.
Prometheus requires the following configuration to scrape the metrics:
TBD
The Prometheus Operator YAML for Kubernetes is available here. It will automatically configure httpd-exporter for your cluster and provide an nginx container for serving the metrics. Install it via:
kubectl apply -f https://github.com/technicalguru/httpd-exporter/master/contrib/kubernetes/exporter.yaml
The httpd-exporter exposes the following metrics:
# TYPE http_requests_total counter
# HELP http_requests_total Counts the requests that were logged by HTTP daemon
http_requests_total{method="GET",status="2xx"} 5432 1512397393000
http_requests_total{method="GET",status="4xx"} 32 1512397393000
http_requests_total{method="GET",status="5xx"} 5 1512397393000
# TYPE http_sent_bytes counter
# HELP http_sent_bytes Number of bytes transferred as logged by HTTP daemon
http_sent_bytes{method="GET",status="2xx"} 235432 1512397393000
http_sent_bytes{method="GET",status="4xx"} 3782 1512397393000
http_sent_bytes{method="GET",status="5xx"} 4375 1512397393000
Metrics are attributed with appropriate labels as defined by the configuration file. You might require the following Prometheus expressions to query your HTTPD status:
increase(http_requests_total{status!="200"}[5m]) - returns number of requests in the last 5 minutes for each label combination that were not successful
sum(increase(http_requests_total{status!="200"}[5m])) - returns the total count of requests in the last 5 minutes that failed