Currently, deploying an Icinga 2 Agent on a Linux system can be intricate, given the substantial variations in the process across different releases or OS families.
For instance:
The repository definition differs for each OS version and family
User and group specifications vary between Debian and RedHat
The environmental path for the Icinga installation also could differ
Fortunately, there’s no need to develop and maintain a custom script to manage these diverse scenarios. We can leverage the readily available Ansible Plugins for this purpose.
Given that our objectives are clearly defined, I developed a role that encompasses all the necessary steps. This allows you to effortlessly integrate it into your playbooks.
You can consult these links to better understand the topic:
Essentially, the role is structured around the following stages:
Gathering NetEye Information: Retrieving essential data from NetEye, including node role, NetEye version, and Icinga2 zone
Collecting Target Information: Gathering details about the target system, such as Linux version and hostname
Verifying Icinga Certificates: Checking for the existence of Icinga certificates on target systems
Token Generation: Creating a token either through the command-line interface (CLI) or by utilizing the API
Installing Icinga Repository and Agent: Setting up the Icinga repository and installing the agent on the designated target
Establishing Icinga Connection: Linking the Icinga agent to the master or satellite
Icinga 2 Restart: Initiating a restart of the Icinga 2 service
NB: When executing this role on a NetEye master or satellite node, there’s no requirement to input specific variables. All necessary data will be automatically collected and utilized.
The playbook will look something like this:
- hosts: all
remote_user: root
roles:
- icinga2-wp
As anticipated, the role can be executed from an external system, such as an Ansible server. In such cases, the following information needs to be provided:
For more information you can request the access to the bitbucket role
Conclusion
Deploying Icinga using Ansible greatly improves on manual deployment due to the efficiency, accuracy, and consistency of automation. Ansible eliminates human error, ensures uniformity across deployments, and adapts to various systems, reducing complexity. Centralized management and scalability enhances efficiency. In sum, Ansible accelerates deployment, minimizes mistakes, and boosts system reliability.
These Solutions are Engineered by Humans
Did you find this article interesting? Are you an “under the hood” kind of person? We’re really big on automation and we’re always looking for people in a similar vein to fill roles like this one as well as other roles here at Würth Phoenix.
Scenario NetEye 4 is a comprehensive monitoring platform which natively supports Business Processes. A Business Process is an abstract view of a customer’s business from the Application point of view. Usually, it’s a collection of Icinga 2 checks aggregated by Read More
On February 3rd and 4th, 2024, we attended FOSDEM, a major event where thousands of free and open-source software developers from around the world gather to exchange ideas and collaborate. This year I dedicated much of the second day to Read More
Introduction: Unveiling Elastic APM in Containerized Environments In today's dynamic digital landscape, where every interaction matters, understanding the intricacies of application performance has become paramount. Elastic APM is a powerful toolset within the Elastic Stack included in the NetEye SIEM Read More
In this article, we’ll explore how to configure the “Agent Binary Download” setting and set up your own artifact registry for binary downloads within a NetEye cluster. Prerequisites Before we begin, ensure you have the following prerequisites in place: Your Elastic Agents Read More
We fixed the following issues in the integration between NetEye and Alyvix. Test Case file selection dropdown We fixed an issue in the Test Cases view for which, when switching between the Test Cases of different nodes, the wrong Test Read More