Icinga

Not all monitoring work happens remotely. Some of it means packing a bag, taking the ICE across three countries, and sitting down with the customer's team. Our trainee Oleksandr Barbashyn accompanied one of our partners' consultants and spent a week on site near Basel: consolidating monitoring onto newer infrastructure, moving the customer onto Icinga DB, rolling out the Ansible plugins across both servers, then spending a full day verifying that everything reported correctly. Coordinating a migration, checking assumptions, and catching the small things is quicker when you can talk to the team directly and see the systems in front of you. His field report is here: https://lnkd.in/e7tRNuHt

Running OpenCloud and want security posture in the same dashboard as everything else? There's a new check for that. sowoi published the OpenCloud Security Check plugin: it scans OpenCloud instances and returns a security rating you can amonitor alongside your regular checks. The plugin exchange runs on community submissions. If you've written a check that solves a problem for your environment, you can add it yourself and anyone with the same use case can discover it. https://lnkd.in/ebTMwc_i

Our full webinar on automating Icinga with Ansible is on YouTube. Matthias from NETWAYS covers installation, configuration, distributed setups, and managing agents. Here is one detail from it that is easy to miss: icinga2_objects in the Ansible Collection for Icinga can be a dictionary. Matthias uses that to stick object config into host variables and still deploy it somewhere else, like the master. Small thing, but it keeps your inventory readable once you have more than a handful of hosts. The snippet below is a short piece of it. Get yourself a coffee and watch the rest: https://lnkd.in/dJUDaaRe

This one isn't about monitoring. It's about a LinkedIn setting that decides whether you see our posts at all. So new releases, roadmap updates, webinars and blog posts can pass you by without you ever noticing they existed. LinkedIn shows you a fraction of what the pages you follow publish, not everything. You can change that per page: switch to "All Posts" on our page and you get what we actually publish. The video shows how. Under ten seconds. And yes, this post also needs likes to reach anyone. Feel free 😉

Thanks for the mention, Telekom MMS. The strongest part of this post is the one that has nothing to do with tooling: the tool is not the point, transparency, stability and resilience are. That is close to how Martin Schurz, IT Architect and Member of Technology Board at Telekom MMS, put it in their customer story: "No one wants a tool that says: 'This is how you do monitoring.' We needed something that blends into our workflows, not breaks them." Behind that sentence sits a setup of 35+ fully isolated Icinga clusters on the Open Telekom Cloud, up to 2,000 servers each, one isolated instance per customer, provisioned end-to-end with Ansible. Read their full article (in German): https://lnkd.in/ergss4-u

Icinga 2 v2.16.5 and v2.15.6 are now available. Both releases contain security enhancements that fix a couple of minor vulnerabilities. v2.16.5 also contains a bugfix for a regression in the IcingaDB feature that was introduced in v2.16.0. Read the full release notes: https://lnkd.in/e65YpW9E

FrOSCon was an absolute blast for the three of us behind the Icinga booth. We had chats spanning a wide range of topics and complexity, from explaining the use case and concepts of monitoring to discussing what makes an open-source project successful and what kind of merchandise we should bring next year. Many people really appreciated the idea of writing configurations in files, doing things manually, and putting effort into software. We were surprised to meet more people using Icinga on BSD than Icinga Director. It was refreshing to hear so many positive things about Icinga and to receive thanks for our work on Free Open Source software. Usually, we only see issues pop up in our repos, so receiving praise for our work was a welcome change. All in all, it was a great success, and we'd love to come back again next year! #opensource I FrOSCon e.V.

OSMC turns 20 this year, and we're back as a Gold Sponsor. Twenty years of a conference dedicated to open-source monitoring is not a given. Three days, more than 30 talks, three workshops, and the part most people actually come back for: the hallway conversations with other people who work with monitoring everyday. We're sponsoring the anniversary edition alongside ilert, B1 Systems, NETWAYS Web Services, Thomas-Krenn and Elastic. Tickets are still available. ICINGA20@OSMC_2026 gets you 20% off. And we have something planned for the lunch break on day one. More on that closer to the event. 📅November 17-19, 2026 in Nuremberg. 🎟️Get your ticket: osmc.de

Telemetry data is scattered across more tools than ever - metrics here, traces there, logs somewhere else, each with its own exporter and its own format. OpenTelemetry exists to fix exactly that: one open standard for collecting and exporting observability data, instead of a different format for every backend. We recorded a full webinar on how this connects to Icinga 2 and its native OpenTelemetry export. Here you see Blerim's opening explanation of what OTel is and why it's relevant. Watch the full recording here: https://lnkd.in/eKr_Bw3W

Icinga Director's health check --check sync used to report on every sync rule at once, even if you'd only touched one and wanted to confirm just that one is healthy. That's fixed in v1.11.6. The --name option narrows a health check to a single sync rule, import source, or job: icingacli director health check --check sync --name ldap-hosts-sync The same release also adds delete to importsource and syncrule, so removing one (during a migration cleanup, or from a script) no longer means switching to the web UI. Ravi, the lead on this Director release, wrote up both, with examples: https://lnkd.in/eWThnRa7 ‎