I am currently in the process of setting up Icinga 2 to monitor a multi-node environment, and I’m looking for some guidance on best practices for this kind of setup. My environment consists of a mix of Linux and Windows servers spread across different locations. I’ve managed to get Icinga 2 up and running on a single node for basic monitoring, but I’m now looking to scale this to cover multiple nodes and would like to ensure I’m following the right steps.
Specifically, I had like to know:
How to effectively set up distributed monitoring in Icinga 2 for multiple nodes—are there any tips or common pitfalls to avoid?
What’s the best way to handle configuration files for different server types? Should I be using templates or a different approach?
Is there a recommended method for managing notifications and alerts for such a diverse environment? I’m concerned about alert fatigue, so any advice on refining this would be really helpful.
Icinga is a blank monitoring canvas/framework with a lot of flexibility and resulting edge cases and paper cuts - it’s the Lego of monitoring.
In broad strokes, you have 3 major ways to get going.
get a consultant or Icinga GmbH to help you set it up Icinga » Partners and train you
Do it your self by experimenting, using the documentation and asking here about your specific sticking points
Use a configuration tool like Ansible with the LFOPS Roles that has the best practices for the setup build in, to get going fast but you still need to learn how to use the resulting system.
A mix of the above is also possible and maybe the right approach for you.
