Icinga

Roles, permissions and filter-based restrictions decide what a user sees in Icinga Web once they are past the login form. They are one of the five topics in our webinar on September 23. The others: password policies in Icinga Web 2.14, TOTP two-factor authentication with Icinga TOTP Web 1.0.0, OpenID Connect single sign-on with Icinga Web SSO 1.0.0, and the new Content Security Policy settings page.

Everything is shown as configuration, in the web interface and in the files behind it. There is an interactive Q&A at the end.

Date: September 23, 2026
Time: 3 PM CEST

Register here: https://icinga.com/webinars/security-in-icinga-web/

Software Freedom Day happens every third Saturday of September, and this year that's today!

It's the day we celebrate software freedom: the right to run, inspect, share, and change the tools you depend on.

We don't have to reach far to make that concrete. Icinga has no investors and no shareholders - the roadmap is shaped by maintainers and the community, not a board.

If you've been meaning to open an issue, try a plugin, or just read the source, this could be your sign to do it!

Find the source on github.com/Icinga

OSMC is celebrating 20 years in 2026, and Icinga is a Gold Sponsor again this year.

The Open Source Monitoring Conference, organised by NETWAYS, runs November 17-19 in Nuremberg. Bernd Erk and Blerim Sheqa give the "Current State of Icinga" talk on November 18, and Christian Stein runs a full-day Icinga for Windows workshop on the 17th.

Two decades of open source monitoring people meeting in one room is worth marking.

Learn more about the conference at osmc.de
And come see us there!

OSMC 2026 - The Open Source Monitoring Conference OSMC is the annual meeting of international monitoring experts, where future trends and objectives are set.

We're in Erfurt today for the Bitkom Forum Open Source, this year under the motto "Open Source - Open Values".

Two topics keep coming up across the agenda: what open development looks like once generating code is the cheap part and review and maintenance are the expensive part, and what the Cyber Resilience Act actually means in practice for the people who maintain and ship open-source software.

Both hit close to home. Icinga is built in the open by a German company with no investors and no shareholders, so compliance, supply chain and long-term maintenance questions land on our own desk too.

Blerim Sheqa is representing Icinga today. If you want to talk monitoring, CRA, or anything in between, find him at the Parksaal.

If you connect Icinga Web 2 to a ticket system for incident handling, there's a good chance the GenericTTS module is already in your stack.

The module has a new home now. Maintenance has moved from the Icinga GitHub organization to Linuxfabrik, who a lot of you will already know from the Linuxfabrik Monitoring Plugins Collection.

If you're running it, you should update your remotes, the new repository can be found here:
Repository: https://github.com/Linuxfabrik/icingaweb2-module-generictts

Screenshots on a product page only tell you so much. At some point you want to click around a tool yourself and see how it behaves.

That's what demo.icinga.com is for. It's set up to resemble a real company's IT environment - with servers, network devices, services, and alerts - instead of a curated slideshow.

If you're not sure where to start, the demotour module gives you a guided walk through Icinga Web's core screens before you go exploring on your own - just look out for the "Start Demo Tour" button in the bottom right (the demotour is only available on desktop).

Check it out: demo.icinga.com

On September 23, we are running a webinar on the authentication and authorization features Icinga Web ships today, shown as configuration in the web interface and in the files behind it.

What we'll cover:

- Password policies in Icinga Web 2.14, including the built-in Common policy and registering your own rules through the PasswordPolicyHook

- Two-factor authentication with Icinga TOTP Web 1.0.0: database resource, issuer name, clock drift, and user enrollment via QR code

- Single sign-on with Icinga Web SSO 1.0.0: one or more OpenID Connect providers, the claim a username is derived from, and provider group mapping

- Roles, permissions and filter-based restrictions, so a team only sees the hosts and services that belong to it

- The new Content Security Policy settings page

Date: September 23, 2026

Time: 3 PM CEST

Register here: https://icinga.com/webinars/security-in-icinga-web/

A 24-hour reporting deadline, filed through a portal nobody has seen yet. Welcome to the CRA, starting tomorrow.

11 September 2026: the Cyber Resilience Act's Article 14 starts to apply. Actively exploited vulnerability or severe incident in a product you ship, including products already on the market, means

- early warning within 24 hours

- full notification within 72 hours

- final report within 14 days

Open-source stewards get until 11 December 2027, when the rest of the CRA applies. Manufacturers start tomorrow.

The Single Reporting Platform goes live tomorrow too. No public URL until launch, no API, no way to rehearse a submission. For a deadline measured in hours, that is not how we would treat a production dependency.

We are ready for this phase regardless: the process is defined, the people are named, the CSIRT is known. The remaining obligations land in December 2027, and we keep working on them now rather than in November 2027.

There's more than one way to get a rootless Podman container write access to a bind-mounted host directory for Icinga 2, and they're not equally good.

You could chown the mount to Icinga's mapped high UID on the host. You could run Icinga 2 as root inside the container, which is safe here since that "root" is just your unprivileged host user in its own namespace. Or you could tell Podman to map your host user straight to UID 5665 with `--userns=keep-id:uid=5665,gid=5665` - no ownership changes, no environment variable overrides, and the process stays unprivileged.

Johannes" new blog post walks through all three, plus systemd and compose setups for running it long-term.

Read the full blog post here:

https://icinga.com/blog/icinga-2-rootless-podman/

When people hear you're a developer on a monitoring tool, they tend to assume you're also a systems integrator who can walk into any setup and make it work.



Jan, who completed his apprenticeship with us in 2025, has a more nuanced answer than a flat no. The better you know the entire codebase, the better you can judge how the tool behaves. But that takes a long time to build, and in massive environments the necessary hands-on experience is sometimes simply missing, compared to consultants who see new setups almost every day. Two different kinds of expertise, and it helps to know which one you are asking for.



Jan started here in 2022, after a few different degree programs that mostly served to confirm that IT was where he belonged. When he went looking for an apprenticeship as an application developer, he deliberately picked a company covering a broad range of topics. Monitoring stood out for exactly that reason: you work with a wide variety of technologies and build a broad foundation, rather than investing years into a proprietary DSL whose value ends with the job.



That has stayed true since. He has no single area he maintains entirely on his own and works project by project instead: Icinga Kubernetes, Icinga Web, several web modules, and Icinga Notifications, where most of his experience has gone so far.