Icinga

28/08/2026

Atlassian stops supporting Opsgenie on April 5, 2027. Data left in the platform after that date gets deleted.

New sales ended in June 2025, so most of the two-year window has already passed. The official path is Jira Service Management, and it covers alerting and on-call. A few things don't come along: Opsgenie phone numbers stay behind (the documented workaround is transferring them to Twilio), bidirectional integrations need Premium or Enterprise, and the Opsgenie-to-Opsgenie setup that MSPs used for sub-accounts is gone.

The self-hosted field got thinner at the same time. Grafana OnCall OSS was archived on March 24, 2026, and the repository is read-only.

In our blog post, you will get insights about the dates, the gaps, and what the options look like if you want the alerting layer to stay open-source and self-hosted.

Read the full blog post here: https://icinga.com/blog/opsgenie-end-of-life-open-source-alerting/

27/08/2026

On September 29, 2026, Icinga's lead developer is holding an Q&A call with a handful of community members. This is not going to be a webinar, it will be a closed conversation about what's working in Icinga, what isn't, and where we should focus next.

We'll pick the group based on the most interesting topics submitted. Send us your question - a monitoring gap, missing functionality, or something you built yourself to patch a shortcoming - along with your name and email.

The call gets recorded so we can write a follow-up blog post. The recording stays internal; only anonymized quotes might be used.

Time: September 29, 3 PM CEST

Submit your topic via Formbricks:

Please complete this survey.

26/08/2026

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://icinga.com/blog/icinga-on-site-consulting-basel/

25/08/2026

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://icinga.com/plugin-vendor/opencloud/

24/08/2026

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://youtu.be/LhRKcSe6zGw

19/08/2026

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://icinga.com/blog/releasing-icinga-2-v2-16-5-and-v2-15-6/

18/08/2026

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!

17/08/2026

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

13/08/2026

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://youtu.be/N1odI4XKVJg

12/08/2026

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://icinga.com/blog/director-cli-commands-1-11-6/ ‎