Today we are happy to announce that after many delays, re-writes, pushbacks and restructuring Icinga for Windows v1.11.0 is finally released! First, we would like to thank everyone for contributing feedback over the past month to track down issues and testing new integrations.
We recently announced the general availability of Icinga 2.14, which most of you might have noticed, and with that in mind, I’d like to show you how you can easily troubleshoot and eliminate some of the dependencies headaches known as the dependency cycle.
We are happy to announce the release of Icinga 2.14.0 and 2.13.8 today. Especially the 2.14.0 release comes with a lot of fixes and improvements and this blog post will highlight the most important ones. There are some breaking changes in 2.14.0, so please make sure to read the corresponding section before upgrading.
Before attending Icinga Berlin in May this year, Daniel Bodky and Markus Opolka from our partner NETWAYS developed the very first Icinga Kubernetes Helm Charts and released it in an alpha version. If you have ever wanted to deploy an entire Icinga stack in your Kubernetes cluster, now is your chance. I also want to highlight Daniel’s talk again on how Icinga can run on Kubernetes and the challenges involved.
It was a nice sunny morning, the weather really with us, for our Icinga Camp Berlin this year. When I peeked outside after helping with the setup, people were already mingling, getting ready to check in and get their first coffee to prepare for the day ahead. Bernd took the stage, welcoming everyone with genuine enthusiasm, setting the tone for what promised to be an engaging event. Surrounded by our community, I felt right at home – ready to dive into the talks and connect with new friends.
In my last blogpost I explained how our ipl-html lib works and how to use it. With the help of ipl-html it is possible to add forms. Usually we want to validate the data of the form before submitting it and display messages if the validation fails. For this purpose, we have introduced the ipl-validator. The ipl-validator includes many useful validators, and today I want to explain how you can easily use them.
Nowadays businesses rely heavily on robust and resilient infrastructure to deliver uninterrupted services to their customers. This includes things like servers, databases, and cloud-based systems. It’s important to monitor the health and performance of this infrastructure, and that’s where monitoring metrics come in.
When setting up new monitoring software or migrating, it’s important to have a strong backbone in place for the systems, so you can cover as many services with as little manual burden as possible. Of course, defining the resources – like HTTP, SSH, etc. services or entire host systems – is one of the first things that comes to mind.
I remember as if it was yesterday. I participated at the OSMC 2014 and watched Bernd’s talk “Current state of Icinga”. In the live demo Bernd has showed some of the new things we’ve built. One of them he introduced somewhat hesitantly IMHO.
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.
