Icinga

The Icinga forum is meant to be humans helping humans. And keeping it that way is important to us, it's what makes the forum actually useful.

After several community members reached out about posts that felt AI-generated, we added a section to the forum guidelines.�

Have a read, and if you haven't already, there's a community badge waiting for you: https://community.icinga.com/faq

If your monitoring config and your infrastructure documentation live in separate places, they will drift. It's just a matter of time.
NetBox knows what devices you have, how they are connected, and which contacts are responsible for what. Icinga knows what's healthy and what isn't. Keeping both in sync manually doesn't scale.

We published a guide that walks through how to connect the two: turning NetBox into a live configuration engine for Icinga Director. Import sources, sync rules, Apply Rules driven by NetBox roles and platforms, zone assignments from IP ranges, notification contacts pulled straight from NetBox.

It was co-created with NetBox Labs and Sol1, the team behind the NetBox Import Source Module.

If this is a problem you are already living with, the guide is worth reading.

Download here: https://icinga.com/guides/

Our Senior UX Designer Flo wrote a dev-diary like post where he ran a design system experiment with the Figma MCP and Claude Code and documented his findings.

What worked: Claude built a solid static HTML documentation project, pushed components to Figma in real time, and set up color and spacing variables with consistent naming.

What didn't: icons showed up as rectangles, fonts didn't apply, and tokens burned faster than it's worth.

If you're planning to automate design work with AI tools, this post is worth reading before you start: https://icinga.com/blog/design-system-with-figma-and-claude

If you're running Icinga alongside Prometheus or Grafana, your check performance data and your metrics dashboards have probably been living in separate worlds. We think that gap is worth closing.

The OTLPMetricsWriter in Icinga 2 v2.16 is how we do it. It exports Icinga check performance data as OpenTelemetry Gauge metrics via OTLP HTTP - so your monitoring data can flow directly into Prometheus, Grafana Mimir, Datadog, VictoriaMetrics, Elasticsearch, and any other OTLP-compatible backend you're already using.

On June 30, we're running a hands-on session with our devs: configuring the writer, integration paths for common backends, threshold metrics, resource attributes, and HA zone behavior. Live demo and Q&A included.

📅June 30 | 3 PM - 4 PM CEST

Register here: https://icinga.com/webinars/icinga-opentelemetry-metrics/

The recording of last week's Terraform webinar is now on YouTube.
Bram Vogelaar, who has been running Icinga in production since before Icinga 2 existed and has been working with Terraform for years, walked through the full workflow for managing Icinga 2 monitoring config as code using the Terraform Icinga 2 Provider.

From provider setup and API authentication to hosts, host groups, services, check commands, users, and notifications - all declared in Terraform config files, versioned in your repo, and reviewed in your pull requests.

If you're already using Terraform for provisioning and your Icinga config is still managed separately, this is the session that shows you how to close that gap.

Watch the recording on YouTube:

Infrastructure as Code for Icinga with Terraform Webinar Declarative Icinga Monitoring Configuration with TerraformIn this ...

Every last Thursday of the month, the Icinga Newsletter lands in your inbox.

What's in it: the latest releases, active discussions from the community forum, new blog posts, and a broader look at what's happening in the Icinga ecosystem.

If you're working with Icinga and want to stay on top of what's shipping and what the community is talking about, this is the most direct way to do it.

If you register now, you'll still get the newsletter we sent out two days ago!
Sign up here: https://icinga.com/company/newsletter/

Content planning in a heat wave: Simona and I sat down Monday to map out this week's posts. Nuremberg is currently doing its best to become a Mediterranean city, and our brains were noticeably cooperative for maybe the first half hour. This post is a testament to that

Bernd redeemed the week yesterday with Spaghetti Eis for the whole org. 10/10 management decision.

~ Feu

Our Partner Manager Angelika attended the Stockholm Tech Show this week - and met up with Binero right there on-site.

Binero is our dedicated partner for the Nordics. They bring local presence and hands-on Icinga experience to teams across the region. If you're running Icinga in Scandinavia or looking to get started, Binero is worth talking to!

Building multi-value form inputs in ipl-web? Then the TermInput is worth knowing.

Our Web Developer Bastian published a step-by-step guide covering the full feature set: per-term validation, label enrichment, multipart updates so enriched terms survive auto-submit, and search suggestions via SearchSuggestions.

The walkthrough uses a weekday picker as the running example, which keeps it concrete and easy to follow.

Read the full blog post here:

IPL: How to Use the ipl-web TermInput Learn how to use the ipl-web TermInput to handle multi-value form inputs in Icinga modules with validation, term enrichment, and live suggestions.