Installation of Apache Exporter for Prometheus in production environment consists from following high level steps:
-
Install exporter;
-
Configure authentication;
-
Configure firewall;
-
Configure service for autostart and restart;
-
Check access to exporter from I&B monitoring platform.
1. Install Prometheus apache exporter.
-
Check latest version, available platforms on apache_exporter GitHub page and make necessary changes in variables on next step.
-
Prepare environment variables to simplify installation and configuration process.
export EXPORTER_VERSION=1.0.10
export EXPORTER_PLATFORM=linux-amd64
-
Download exporter.
wget https://github.com/Lusitaniae/apache_exporter/releases/download/v$EXPORTER_VERSION/apache_exporter-$EXPORTER_VERSION.$EXPORTER_PLATFORM.tar.gz
-
Create directory /usr/local/bin/apache_exporter and untar exporter into it.
sudo mkdir -p /usr/local/bin/apache_exporter
sudo tar xvfz apache_exporter-$EXPORTER_VERSION.$EXPORTER_PLATFORM.tar.gz -C /usr/local/bin/apache_exporter --strip-components=1
-
Create prometheus user. If it already exist - go to step 6.
Fedora (RHEL, CentOS)
sudo useradd -M -s /sbin/nologin prometheus
-
-M(or--no-create-home): This option prevents the creation of a home directory for the new user; -
-s /sbin/nologin: This option sets the user's login shell to/sbin/nologin. This effectively prevents the user from interactively logging into the system. While the user won't have a password set, this further ensures they cannot log in.
Debian (Ubuntu)
sudo useradd -s /sbin/nologin prometheus --no-create-home
-
Make prometheus user owner of apache_exporter directory.
sudo chown -hR prometheus:prometheus /usr/local/bin/apache_exporter
2. Configure firewall
Configure firewall on resource
-
apache exporter uses default port 9117, so allow it in firewall on resource.
Fedora (RHEL, CentOS)
sudo firewall-cmd --zone=public --add-port=9117/tcp --permanent
sudo systemctl reload firewalld
Check firewall configuration
sudo firewall-cmd --list-all
You should see in output:
ports: 9117/tcp
Debian (Ubuntu)
sudo ufw allow 9117
You should see in output:
Rules updated
Rules updated (v6)
Check firewall configuration
sudo ufw status
You should see in output:
To Action From
-- ------ ----
9117 ALLOW Anywhere
its good
3. Configure authentication for exporter
Do the steps described in Exporters configuration → Authentication section.
4. Check configuration
-
Run apache_exporter in key
--scrape_uri="https://your.server.com/server-status?auto"you set ip or domain name of monitoring apache
/usr/local/bin/apache_exporter/apache_exporter --web.config.file=/usr/local/bin/apache_exporter/web-config.yml --scrape_uri="https://your.server.com/server-status?auto"
In output you should see:
... msg="TLS is enabled." ...
Check with browser if it is accessible at:
https://resource-hostname-or-ip:9117/metrics
After entering exporter’s user name and password you should see page like this:
# HELP apache_exporter_build_info A metric with a constant '1' value labeled by version, revision, branch, goversion from which apache_exporter was built, and the goos and goarch for the build.
# TYPE apache_exporter_build_info gauge
apache_exporter_build_info{branch="HEAD",goarch="amd64",goos="linux",goversion="go1.22.12",revision="c4206b529038d79f20f2eeba98a9780c8cb4a2c2",tags="netgo",version="1.0.10"} 1
...
Stop apache exporter with Ctrl-c in terminal where you run it.
Make apache_exporter service for autostart and restart.
Create file with your preferred text editor, for example nano …
sudo nano /etc/systemd/system/apache_exporter.service
… and paste following text into it.
[Unit]
Description=apache Exporter
[Service]
User=prometheus
ExecStart=/usr/local/bin/apache_exporter/apache_exporter --web.config.file=/usr/local/bin/apache_exporter/web-config.yml --scrape_uri="https://your.server.com/server-status?auto"
[Install]
WantedBy=multi-user.target
Save file and exit editor.
Start service …
sudo systemctl daemon-reload
sudo systemctl start apache_exporter
sudo systemctl enable apache_exporter
… and check
sudo systemctl status apache_exporter
You should see following output similar to:
In case of any problem, you should view log entries for service:
journalctl -u apache_exporter.service -e
Now apache exporter is ready to accept data and then expose it to Prometheus.