Community

Get with the monitorin’ crowd

Icinga is not just software, it’s a whole community of users and developers who do monitoring and want to do it right.

Talk Icinga, troubleshoot and bounce ideas online on one of the many channels below or in person at an Icinga event near you. Welcome to the Icinga community.

Stay in touch

Icinga is coming closer – join an Icinga camp or conference near you, follow our blog and newsletter updates.

Events

Icinga Camps, conferences, …

Blog

Releases, technical reviews, etc.

Newsletter

Subscribe to the latest news.

Get social

Get social with Icinga, follow our community updates and release announcements.

Get help & share your knowledge

We all come across problems at some time, here are good places to ask for advice from other users and give some in return.

Monitoring Portal Forum

Talk all things Icinga with an international monitoring community.

Icinga-Users Mailing List

Discuss with community members (subscription details).

Official docs

Documentation to get you started within minutes.

Icinga Exchange

Plugin & Addon Repository

Contribute to Icinga

Icinga is an open source project and lives from your ideas, bug reports, features requests and patch contributions. Make yourself proud and help improve Icinga.

The Icinga code is hosted at GitHub – fork/clone the repositories and start your work.

Contribute a patch

Icinga 2 is written in C++. Icinga Web 2 and the modules require PHP and JS knowledge. Integrations might require additional know-how (Puppet, Ansible, Vagrant, etc.).

Get familiar with the inline coding style. Apply your changes, add test cases and prepare your contribution.

Learn your Git foo and commit a clean patch with your real name/email address as author.

ITL: Add new CheckCommand 'radius'

Short description if necessary.

refs #TICKETNUMBER

Create a new Git patch (git format-patch -1) or send a pull request on Github.

The developers will review your patch and request updates in case. Don’t worry – such reviews ensure that we all produce the best maintainable code and docs there is :) Thank you for your contribution!

Documentation & Templates

The documentation for Icinga 2 and Icinga Web 2 is written using Markdown. Edit the files in the doc/ directory with your preferred editor and review your changes (online in the GitHub repository, dillinger.io, etc.).

The Icinga Template Library (ITL) provides many community contributed CheckCommand definitions for monitoring plugins. This helps starting with Icinga 2 configuration far more easy. Edit/add files in the itl/ directory and follow best practices from given examples.

Proceed with contributing a patch – thanks for your contribution making the live of many others more easy! :)

Icinga Sponsors

We thank the following organisations for granting us free open source project licenses to use their great software and amazing hardware to develop and test Icinga.

Individual contributers

We’d also like to give much credit to the individuals who have contributed to Icinga:

  • The Monitoring-Portal.org community and team that keeps the forum running, for helping all Icinga users who seek advice there
  • Jannis Moßhammer for developing Icinga Web, creating Icinga Mobile and kicking off Icinga Web 2
  • Michael Lübben for co-founding Icinga and his early developmental work on Icinga Web and Reporting
  • Christian Döbler for helping in Icinga´s development of the API
  • Karolina Hein for creating Icinga website, graphics and kick-starting community activities
  • Hiren Patel for his contribution to the Icinga Core team
  • Christoph Maser for his help in creating RPMs on RepoForge and Icinga Virtual Appliance
  • Mike Becker for his work on NRPE for Icinga
  • Scott Evans for Q&A help, blogging and tweeting to create awareness for Icinga on social media
  • Erez Zarum for his contribution to Icinga quality and testing
  • Norbert Klein for his ideas regarding idoutils and PostgreSQL
  • Marco Berdelsmann for converting the xml-Doku into a handy .pdf format
  • Vitali Voroth for a huge improvement for Icinga core: escalation conditions
  • Bill McGonigle for a great patch “changing the default state from CRITICAL to UNKNOWN”
  • Edgar Salazar for getting Spanish translations underway
  • Matthias Flacke for his community support and advice
  • Ronny Fauth, Massimo Forni and James Michael Dupont for being a part of the Icinga Team