Skip to content

Releases

v2.3.1

Choose a tag to compare

@github-actions github-actions released this 08 Nov 17:31
5b2e915

Docs and CI only, no changes to the stack itself. Found by running the install docs on a machine with leftovers: busy ports, an old Grafana volume, an upgrade over existing data, Compose and Ansible on one host. Write-up: https://dev.to/airat71/i-installed-my-stack-on-a-machine-with-leftovers-three-green-signals-stayed-green-5211

Changed

  • Quick Start, README and Installation Guide verify the stack with scripts/smoke-check.sh instead of docker compose ps, list the ports that must be free, and say to use either Option A or Option B on a host.
  • docs/UPGRADE.md: upgrade steps for the Docker Compose path.
  • docs/TROUBLESHOOTING.md: port conflicts, the Grafana password after the first start, dashboards after the v2.2.0 to v2.3.0 upgrade, Ansible on a host that already runs a stack or a Node Exporter.

Added

  • scripts/upgrade-check.sh and an upgrade job in the smoke test: starts the latest release with data, upgrades to the commit under test on the same volumes, and checks that the smoke check passes, the Grafana folder and Prometheus data survive and every dashboard file is provisioned without errors.

Known, not fixed

  • Upgrading from v2.2.0 to v2.3.0 over an existing Grafana volume leaves three new dashboards unapplied (nginx, postgresql, redis). docker compose up -d still exits 0. The workaround that was verified is in docs/TROUBLESHOOTING.md.
  • The Prometheus healthcheck runs inside the container and cannot detect a port taken by another process. The Ansible playbook does not check targets after it starts.

Full list: CHANGELOG.md.

v2.3.0

Choose a tag to compare

@github-actions github-actions released this 26 Oct 20:37
8f3afa1

Fixes and a weekly clean-VM test since v2.2.0. I followed my own README on a clean VM and fixed what failed. Write-up: https://dev.to/airat71/i-tested-my-own-docs-like-a-stranger-they-failed-24-times-1ekf

Added

  • Smoke test in CI: starts the stack with Docker Compose and with the Ansible playbook on ubuntu-24.04, checks readiness, loaded alert rules and that all scrape targets are up, then runs the playbook again and expects changed=0. Runs weekly.
  • Fail2ban dashboard: 7 panels, including "Attacks last 24 h" and "Total attacks blocked".
  • Alert Fail2banSocketDown (f2b_up == 0).
  • Pull request and issue templates.

Fixed

  • Prometheus config was invalid YAML when monitored_nodes was not empty.
  • node_exporter_install_method from the inventory now takes effect.
  • Prometheus, Alertmanager and Blackbox restart when their config files change.
  • Backup script runs with umask 077 and also copies blackbox.yml and .env.
  • FilesystemReadonly no longer fires on the read-only ramfs mount on Ubuntu 22.04.

Full list: CHANGELOG.md.

v2.2.0

Choose a tag to compare

@github-actions github-actions released this 04 Oct 10:50
08e5855

What's Changed

  • fix: remove PRO/Open Core references from LICENSE and CONTRIBUTING by @Airat71 in #5
  • ci: TruffleHog, auto-release, dependabot, paths-ignore by @Airat71 in #7
  • docs: add dashboard source attribution by @Airat71 in #6
  • docs: CHANGELOG v2.1.0, CI pipeline docs, Security badge by @Airat71 in #10
  • fix: correct Grafana port 3000 → 3001 in quickstart docs by @Airat71 in #11
  • fix: one runnable stack, current image tags by @Airat71 in #12

Full Changelog: v2.0.0...v2.2.0

Monitoring Stack v2.0.0 — Full Open Source

Choose a tag to compare

@Airat71 Airat71 released this 30 Sep 20:16
5737011

Full Open Source Release

Everything that was previously paid (PRO) is now free and open source.

What's new

  • Ansible automation — one-command deployment to any number of servers
  • 7 pre-built Grafana dashboards — Node Exporter, Prometheus, Blackbox, Nginx, PostgreSQL, Redis, RabbitMQ
  • 20 production-ready alert rules — host down, CPU/memory/disk thresholds, HTTP probes, fail2ban events
  • fail2ban integration — ban events visible in Grafana
  • Multi-server support — monitor N servers from one Grafana instance
  • Automated backup script with optional cron
  • 20 guides — deployment, security, operations, multi-server, runbook, troubleshooting

CI improvements

  • Concurrency groups (cancel duplicate runs)
  • YAML validation for Ansible configs and alert rules
  • ShellCheck for all scripts

Quick Start

git clone https://github.com/Airat71/monitoring-stack.git
cd monitoring-stack/prometheus-grafana
cp .env.example .env
docker compose up -d
# Grafana → http://localhost:3000

Full deploy with Ansible: see INSTALLATION_GUIDE.md


CHANGELOG · Documentation · Roadmap

Enterprise Monitoring Stack v1.0.2 — Open Core Launch

Choose a tag to compare

@Airat71 Airat71 released this 26 Feb 14:36

🎉 First Public Release — Open Core Model

Production-ready monitoring stack with Prometheus, Grafana, Alertmanager and fail2ban security integration.

FREE Version includes

  • ✅ Prometheus + Grafana + Node Exporter (Docker Compose)
  • ✅ 2 Grafana dashboards (System Metrics, Prometheus Overview)
  • ✅ 5 basic alert rules
  • ✅ Multipass quick demo script (2-minute setup)
  • ✅ Complete documentation (README, QUICK_START, DEMO)

PRO Version ($40) includes

  • 6 containers (+ Alertmanager, fail2ban Exporter, Blackbox Exporter)
  • 8 professional dashboards (fail2ban, Nginx, PostgreSQL, RabbitMQ, Redis...)
  • 21 production alert rules
  • Ansible one-command deployment (multi-server)
  • Telegram + Email notifications
  • 20 comprehensive guides
  • Lifetime updates + email support

👉 Get PRO Version

Quick Start

git clone https://github.com/Airat71/monitoring-stack.git
cd monitoring-stack/prometheus-grafana
cp .env.example .env
docker compose up -d

Stats

  • 321,060 attacks blocked in production
  • Tested on Ubuntu 22.04 / 24.04
  • 2000+ lines of Ansible/YAML/Scripts