This platform is made with love for community discussions on Icinga open source monitoring, metrics, integrations and anything related to the #monitoringlove :heart: culture. We have grown as international community and have decided on English as the forums language to allow everyone to join the conversation.

  1. Questions and Answers
    1.1 Before you ask your question
    1.2 Format topics with Markdown
    1.3 Details you should always include
    1.4 Steps to reproduce or understand the question
    1.5 Add the things you’ve tried already
    1.6 Pick a solution
  2. Community Code of Conduct
    2.1 Improve the Conversation
    2.2 Keep it friendly and relaxed
    2.3 Learn from others
    2.4 Be Agreeable, Even When You Disagree
    2.5 Your Participation Counts
    2.6 If You See a Problem, Flag It
    2.7 Keep It Tidy
    2.8 Post Only Your Own Stuff
    2.9 Powered by You
    2.10 Terms of Service

Questions and Answers

Before you ask your question

  • Use your preferred search engine such as Google and the search here. Maybe a similar topic already covers your problem.
  • Does the documentation provide a troubleshooting guide already? Try that first and add your findings here. Example: Icinga 2
  • If you think you’ve hit a bug, look into the upstream GitHub project if it already exists and link it in your post. Example:

Please make sure to include every little detail in your question. This helps community members to analyse your problem. They do not need to ask again to find out more about your issue.

Sometimes a screenshot or a handcrafted overview picture help even more to understand what you mean.

Format topics with Markdown

Please format configuration snippets, source code, logs, shell output with Markdown (three backticks or 4 space indent). This makes your questions far more readable and others can identify things faster.

More tips on Markdown and general writing can be found in this guide.

Details you should always include

  • Which documentation source did you use (URL, short quote).
  • Distribution name and its version (/etc/os-release or /etc/*-release or /etc/*-version) of any involved host.
  • Software versions (<applicationname> --version or web application - About).
  • Additional dependencies (php -v, ruby -v, python -V, etc.).
  • Installation method and download source (packages, or source, and if Git, git show -1).


yum info icinga2
apt-cache showpkg icinga2
zypper info icinga2

Steps to reproduce or understand the question

  • Configuration files you’ve edited - their content formatted with code tags, their location on disk.
  • Cluster and HA related configuration details (e.g. Zone/Endpoint configuration in zones.conf in Icinga 2, my.cnf for MySQL replication, etc.).
  • Order of things, e.g. notification was triggered, corresponding debug log entries, your analysis.
  • Which steps are needed to reproduce the problem standalone in a local environment, e.g. Docker or a (Vagrant) VM?


Keep your private details safe. Remove passwords, credentials, etc. and obfuscate host names from your company environment.

Add the things you’ve tried already

  • Configuration changes which did not work - they help explain your idea.
  • Docs and howto URLs you’ve found, maybe they do not match 100%.
  • If it could be a bug, did you try a snapshot package or attempted to fix it already?


Do your homework and describe your thoughts in detail. Don’t throw something short and ask for a ready-to-use solution.

Pick a solution

If someone posts an answer to your question, mark it as the solution!


That makes it easier for others to
a) figure out the solution for their own problems
b) know which topics still need answering

The solutions author will also receive a shiny badge for their profile!

Sometimes the solution would be your own answer!
So feel free to just pop that solution on yourself :slight_smile:

Other times the way to solving an issue is a very iterative process…
Having a dedicated solution helps others, with similar issues, resolve the problem quickly.
It would be totally awesome, if you could write a quick summary in this case.
Maybe the repetition also helps you understand the process better? :innocent:

Community Code of Conduct

Icinga contributors and maintainers want this place to be a harassment-free experience for everyone, regardless of age, body size, ability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

Please read the community code of conduct carefully. By registering and using this forum, you have agreed to follow these guidelines.

Improve the Conversation

Treat this place like you would walk into a public park. Treat everyone with respect, even if someone disagrees with your opinion. Listen to what others suggest and learn from their experience.

Create a new topic for your question with your own details. Older topics might not necessarily fit, and also requires others to scroll and read history to fully understand if your issue is the same.

Help us make this a great place for discussion by always working to improve the discussion in some way, however small. If you are not sure your post adds to the conversation, think over what you want to say and try again later.

The topics discussed here matter to us, and we want you to act as if they matter to you, too. Be respectful of the topics and the people discussing them, even if you disagree with some of what is being said.

One way to improve the discussion is by discovering ones that are already happening. Spend time browsing the topics here before replying or starting your own, and you’ll have a better chance of meeting others who share your interests.

Keep it friendly and relaxed

Please hide frustration when asking a question here. A message which has a negative tone feels different to a clear-cut problem description. Think about the other side and their feelings about your tone.


Please don’t stress it if answers take their time. We are human beings with our day job, and try to help you for free. Don’t be impolite and force one with a personal message, keep it public and wait for an answer.

If you need faster professional support from an enterprise partner, look for a local support partner.

Things to keep in mind:

  • Be civil. Don’t post anything that a reasonable person would consider offensive, abusive, or hate speech.
  • Keep it clean. Don’t post anything obscene or sexually explicit.
  • Respect each other. Don’t harass or grief anyone, impersonate people, or expose their private information.
  • Respect our forum. Don’t post spam or otherwise vandalize the forum.
  • Choose the right category. A question for Icinga Web 2 does not fit into Automation & Infrastructure necessarily.

This is a public platform, and search engines index these discussions. Keep the language, links, and images safe for family and friends.

Learn from others

Community members want to help you to learn about all the tools we use and love. Please understand that you won’t get copy-paste solutions all the time. The more you are willing to invest into your learning curve, the more you will benefit later on :heart_eyes:

Helping others and learning new things is a good feeling. If you think the same, come back here on a regular basis and add your help and opinion. This is what matters most in our community. Others will honor this, making you the Icinga monitoring expert.

Be Agreeable, Even When You Disagree

You may wish to respond to something by disagreeing with it. That’s fine. But remember to criticize ideas, not people. Please avoid:

  • Name-calling
  • Ad hominem attacks
  • Responding to a post’s tone instead of its actual content
  • Knee-jerk contradiction

Instead, provide reasoned counter-arguments that improve the conversation.

Your Participation Counts

The conversations we have here set the tone for every new arrival. Help us influence the future of this community by choosing to engage in discussions that make this forum an interesting place to be — and avoiding those that do not.

Discourse provides tools that enable the community to collectively identify the best (and worst) contributions: bookmarks, likes, flags, replies, edits, and so forth. Use these tools to improve your own experience, and everyone else’s, too.

Let’s leave our community better than we found it.

If You See a Problem, Flag It

Moderators have special authority; they are responsible for this forum. But so are you. With your help, moderators can be community facilitators, not just janitors or police.

When you see bad behavior, don’t reply. It encourages the bad behavior by acknowledging it, consumes your energy, and wastes everyone’s time. Just flag it. If enough flags accrue, action will be taken, either automatically or by moderator intervention.

If you experience abuse, harassment, discrimination, or feel unsafe, let a moderator know as soon as possible.

In order to maintain our community, moderators reserve the right to remove any content and any user account for any reason at any time. Moderators do not preview new posts; the moderators and site operators take no responsibility for any content posted by the community.

Keep It Tidy

Make the effort to put things in the right place, so that we can spend more time discussing and less cleaning up. So:

  • Don’t start a topic in the wrong category.
  • Don’t cross-post the same thing in multiple topics.
  • Don’t post no-content replies.
  • Don’t divert a topic by changing it midstream.
  • Don’t sign your posts — every post has your profile information attached to it.

Rather than posting “+1” or “Agreed”, use the Like button. Rather than taking an existing topic in a radically different direction, use Reply as a Linked Topic.

Post Only Your Own Stuff

You may not post anything digital that belongs to someone else without permission. You may not post descriptions of, links to, or methods for stealing someone’s intellectual property (software, video, audio, images), or for breaking any other law.

Powered by You

This site is operated by your friendly local staff and you, the community. If you have any further questions about how things should work here, open a new topic in the meta category and let’s discuss! If there’s a critical or urgent issue that can’t be handled by a meta topic or flag, contact us via the staff page.

Terms of Service

Yes, legalese is boring, but we must protect ourselves – and by extension, you and your data – against unfriendly folks. We have a Terms of Service describing your (and our) behavior and rights related to content, privacy, and laws. To use this service, you must agree to abide by our TOS.