volker.raschek/prometheus-fail2ban-exporter
1
0
Fork 0
Code Issues Pull Requests 2 Packages Projects Releases Wiki Activity
98d376ac60
prometheus-fail2ban-exporter/docker/run.sh

21 lines
636 B
Bash
Raw Normal View History

build: add project dockerfile (#2) Add a project Dockerfile to allow deploying the application in a docker container. Add a `run.sh` script to start the application in the container. Add Makefile commands to build the docker image based on the Dockerfile. Fix possible nil reference error in the `db` package.
2021-02-07 13:04:24 +00:00
#/bin/sh
# Print version to logs for debugging purposes
/app/fail2ban-prometheus-exporter -version
feat: support reading fail2ban socket in docker Update the docker container to support mounting the fail2ban server socket and pointing the exporter at it. This allows the exporter to interact with the socket from within the container. The entire `/var/run` folder is mounted instead of just the socket file to correctly handle fail2ban restarts (where the file will be deleted).
2021-08-29 17:36:27 +00:00
socket_path=/var/run/fail2ban/fail2ban.sock
feat: support for textfile metrics (#13) Add support for collecting arbitrary metrics from a textfile as well as metrics collected from fail2ban. This allows other data to be exported along with the fail2ban metrics (e.g. instance metadata). Update the docker image to allow mounting a folder with a collection of metric files to be exported. Only files ending in `.prom` with be read. Update project README with the new functionality.
2021-10-12 20:38:26 +00:00
textfile_dir=/app/textfile/
textfile_enabled=false
feat: support reading fail2ban socket in docker Update the docker container to support mounting the fail2ban server socket and pointing the exporter at it. This allows the exporter to interact with the socket from within the container. The entire `/var/run` folder is mounted instead of just the socket file to correctly handle fail2ban restarts (where the file will be deleted).
2021-08-29 17:36:27 +00:00
remove: database-based metrics Remove all database-based metrics from the metrics endpoint. Remove all code related to pulling metrics from the fail2ban database. Remove all configuration variables related to the fail2ban database. The CLI parameter for the database path was not removed to avoid breaking compatibility. Update docker entrypoint to remove references to the fail2ban database. Remove all references to the old database metrics from the README.
2021-10-15 18:02:26 +00:00
# Enable textfile metrics if the folder exists (i.e. was mounted by docker)
feat: support for textfile metrics (#13) Add support for collecting arbitrary metrics from a textfile as well as metrics collected from fail2ban. This allows other data to be exported along with the fail2ban metrics (e.g. instance metadata). Update the docker image to allow mounting a folder with a collection of metric files to be exported. Only files ending in `.prom` with be read. Update project README with the new functionality.
2021-10-12 20:38:26 +00:00
if [ -d $textfile_dir ]; then
textfile_enabled=true
fi
feat: support reading fail2ban socket in docker Update the docker container to support mounting the fail2ban server socket and pointing the exporter at it. This allows the exporter to interact with the socket from within the container. The entire `/var/run` folder is mounted instead of just the socket file to correctly handle fail2ban restarts (where the file will be deleted).
2021-08-29 17:36:27 +00:00
build: add project dockerfile (#2) Add a project Dockerfile to allow deploying the application in a docker container. Add a `run.sh` script to start the application in the container. Add Makefile commands to build the docker image based on the Dockerfile. Fix possible nil reference error in the `db` package.
2021-02-07 13:04:24 +00:00
# Start the exporter (use exec to support graceful shutdown)
# Inspired by: https://akomljen.com/stopping-docker-containers-gracefully/
exec /app/fail2ban-prometheus-exporter \
feat: configure tool using environment variables (#17) Replace CLI parsing functionality with the `kingpin` library to better support configuring the tool with environment variables. Add new environment variables to configure the tool. BREAKING CHANGE: CLI params now require two dashes instead of one (e.g. `--socket`)
2022-01-30 21:32:48 +00:00
--socket "$socket_path" \
--collector.textfile=$textfile_enabled \
--collector.textfile.directory="$textfile_dir"
Reference in New Issue Copy Permalink