Operations | Monitoring | ITSM | DevOps | Cloud

Latest Posts

Embedding Git Commit Information in Go Binaries

It is always helpful to know which version you are running of some software, even more so when running development versions. So it’s good if software is able to tell you its version, for example by calling it with --version. For release versions, maintaining this information by hand is feasible, but in order for development versions to show exact revision information, you need some automation, otherwise updating it will be forgotten, leaving you with wrong information.

Icinga integration cases: OpsBridge and ServiceNow

The health of your systems and applications is fundamental for your organization’s infrastructure. Monitoring them indicates if there are any issues that need to be handled before they become serious and affect your customers. This is why companies often use a plethora of monitoring tools that can spot any irregularities as early as possible. Icinga allows you to monitor a lot of different metrics throughout your ecosystem, with various plugins that are ready-to-use.

Deutsche Telekom Security trusts in Icinga monitoring

We´re proud of our many customers and users around the globe that trust Icinga for critical IT infrastructure monitoring. That´s why we´re now showcasing some of these enterprises with their Success stories. It´s stories from companies or organizations just like yours, of any size and different kinds of industries. Some of them are our long-standing customers, others have just recently profited from migrating from another solution to Icinga.

Why Icinga?

We have decided to make some short educational videos about Icinga, and today we will be releasing the first one: Why Icinga? In these videos we want to explain the Whys and Whats and Hows around Icinga in a way that is accessible to anyone who is interested. So Why do you want to use Icinga? Monitoring is the foundation you want to build your infrastrastructure on.

Introduction of the ansible-collection-icinga

Ansible is a commonly known tool to easily automate deployments in infrastructures, its configuration is based on YAML and is able to scale in big environments. Icinga 2 provides its own secure agent to monitor hosts, high available satellite zones and monitoring configuration. To manage this monitoring environment we introduce you to the ansible-collection-icinga, this collection can install Icinga 2 server, configure monitoring and deploy Icinga 2 agents in your infrastructure.

How to use path wildcards in Graphite Module

The Graphite module of Icingaweb2 is a great tool for rendering graphs from performance data. The latest version 1.2.0 introduces some bug fixes and new features like dark and light mode support, a lot of new templates, support for path wildcard, etc. The support for wildcard * was already available in the previous version. We have extended this support and added all the wildcards that graphite offers.

Parameterizing GitLab CI/CD?

While doing packaging for Icinga, I noticed we have a lot of YAML files describing GitLab pipelines doing very similar jobs. The same build job across different operating systems. That’s wasteful behaviour, which leads to a bigger workload when it comes to modifying these jobs. Tasks like adding new versions and especially adding new operating systems become tedious. What I’m looking for is a way to have interchangeable values for our building jobs.