Operations | Monitoring | ITSM | DevOps | Cloud

Icinga

A Short Overview: GitLab Tokens

During my recent work on extending our GitLab packaging capabilities, I came across various types of tokens that can be used to authenticate users, services, and pipelines while using GitLab CI/CD. Each token has its unique features and use cases that can help ensure the security and integrity of your GitLab environment. By understanding the features and use cases of each token, you can leverage them to enhance your GitLab CI/CD workflows and ensure the security of your GitLab environment.

How German drugstore chain Müller thrives with Icinga

We are 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.

Feedback Week Results

For the third time, we initiated the Icinga Feedback Week. Why? Because your opinion matters to us, a lot. Even though, we do get feedback throughout the year, our yearly Feedback Week is a chance for us, to ask you specific questions to certain topics. By understanding your thoughts and feelings towards Icinga, we aim to develop the most effective monitoring tool for you. But that wasn’t all: as a good tradition, we asked you to choose your Community Heroes and we have found five!

How Tenacta Group uses Icinga

Tenacta Group is an Italian company with a portfolio of worldwide leading brands that share the same mission: to develop designs and technological innovations that will improve people’s quality of life. We have been using Icinga since its early days, specifically version 1 after the fork from Nagios. We have continued using Icinga because we like its direction for future improvements and appreciate the support of the Icinga community.

Why is Icinga called Icinga?

It’s the year 2009, a nice weekend in late spring and a small group of monitoring enthusiasts comes together to discuss how to move forward with the idea of forking Nagios. The Icinga team in 2009, just to set the mood. Plans were made to make it faster, easier, more scalable, and simply better. Of course, such a project has a lot of hurdles to take – the most important one was of course: the name.