This Ansible role installs and configures the atop performance monitoring tool on Debian systems, matching how we deploy it in production baselines.
The Ansible Role is written and actively maintained by Blunix GmbH. It is used in the Blunix Linux Managed Hosting Stack. Its usage is documented at our Linux Managed Hosting Documentation.
- Installs the
atoppackage on Debian. - Manages
/etc/default/atopvia a template to control logging behaviour. - Configures log directory, log retention and sampling interval via role variables.
- Ansible: >= 2.20.0
- Managed operating systems:
- Debian trixie
Production playbooks include the role without overrides. The example is split into files under example/:
example/inventory/group_vars/all/atop.yml— sampling interval, log retention, and log dir.example/play.yml— minimal play applying the role to all hosts.
/etc/default/atop(controls interval, log dir, log file name)
- Provision: use
dev-tools/main.tfwith the atop role enabled to create a test host. - Playbook:
example/play.ymlapplies the role and configures atop/log rotation defaults. - Tests in
example/tests/:cus-dev-prod-web-1/test_default.py: checks atop is installed, service is active, and basic defaults are in place.
The directory test/ contains an example play.yml as well as inventory/group_vars/, if applicable to the role. the script example/run-tests.sh creates a IONOS cloud instance with terraform, uses the example inventory and playbook to run the role and then run pytest tests located in example/tests/. Destroy the terraform using ./run-tests.sh -d.
Blunix GmbH Berlin
root@Linux:~# Support | Consulting | Hosting | Training
Blunix GmbH provides 24/7/365 Linux emergency support and consulting, Service Level Agreements for Debian Linux managed hosting using Ansible Configuration Management as well as Linux trainings and workshops.
Learn more at https://www.blunix.com.
Click here to see our Contact Information.
For bug reports and feature requests, please open an issue in this repository’s GitHub issue tracker.
Apache-2.0
Please refer to the LICENSE file in the root of this repository.