Operations | Monitoring | ITSM | DevOps | Cloud

This is a guest blogpost by Adam Sweet from the Icinga Partner Transitiv Technologies. Since this is a longer post, we added a tl;dr at the end. For many, host and application monitoring is an afterthought at the end of a project. Some people don’t think about monitoring at all until a few failures go unnoticed and a customer or end-user calls to ask why something isn’t working.

Modern applications are often built using microservices: Small, independent components that work together. This makes systems more flexible and scalable, but also harder to monitor. In this guide, we’ll explain what microservice monitoring is, why it’s different from traditional approaches, and how to do it effectively. Whether you’re starting from scratch or improving an existing setup, this article will help you monitor microservices with confidence.

The raw data imported from the external sources (CSV, SQL, REST API, LDAP, etc.) is usually not in the right format. Hence, they have to be processed or converted before they are used to modify objects using synchronization rules. To do this, Icinga Director provides different property modifiers. There are many property modifiers provided by Icinga Director.

There are many ways to interact with the data that Icinga 2 collects, processes, and produces. The most common is probably Icinga Web, which displays checks in all the colors of a traffic light. Icinga 2 also comes with several metrics or performance data writers. But that is not all. Icinga 2 has open interfaces to integrate all kinds of third-party tools if one is not afraid to write a little glue code.