Hey there, I am not sure if I understand the question - in the part you linked Johannes is talking about "fake" Hosts / Services and not a specific feature or module. Can you explain what you mean, so I can make sure I answer correctly? :) ~Feu
@@T4nqino I just asked Johannes about it, and he meant to say "learned" not "launched", there was a talk about the topic the day before - I'll see if I can find it... It's very easy to mishear (I also understood "launched"). So there you go, sorry for the confusion! :)
For our team and many of our customers eventhandlers are very important. Unfortunately some customers use quite stupid and instable software that can not run and live withou being continously restarted when certain errors occur. In those case we use some self written eventhandlers. Like when a specific error occurs or port is down which we all monitor, an eventhandler kicks the server or the software and restarts it. We also use them to acknowledge a host or a service automatically based on certain service states or outputs. We migrated most of them from icinga1 to icinga2 so I might have grown historically. But at least until now we do not know of an alternative way to solve these problems.
Hi, nice tutorial! I would like to do development in Python. Maybe I can create a PHP wrapper and call Python Flask/Django? :) I am not very familiar with PHP.
Not sure if that would work all that well, but feel free to give it a shot. This might also be a nice chance to learn something new - like PHP! Markus also shows off a lot of ways to do things in the other videos in the series. Let us know if it helped you get some insights! :)
is this still up-to-date? when i check elasticsearch integration with icinga i get the info that i shouldn't "attempt to use" the module, yet it's referenced on your website.. What's this?
A event handler tab like the one for notifications would be nice but to be honest, every time I used a event handler it was a ugly fix for a bad problem and most of them got retired. The only one still in production is trying once to restart a possibly stuck queue via a SOAP request. One needs to be very careful not to make matters worse by trying to auto heal systems in the monitoring! Right now I plan on using event handlers to sync host and service states form one icinga2 instance to another via the REST API. And no, I don't want to cluster the two environments. I don't know it this would be practical and useful to see in a event handler tab of the service. From memory I don't know if a failed event handler is visible in icingaweb2, this could be useful.
Looks nice but I don't get it, why use this and not Ansible? Looks like a lot more work then adding a new host to the inventory and running the playbook.
As not everyone is using Ansible or Puppet we require a generic approach which works in general on every single Windows machine. For the Icinga for Windows automation, you have everything on your disposal then and are free to integrate this later into SCCM, Ansible, Puppet, Chef or any other configuration management solution. In addition we want to make sure that the "basic" user has an easy and quick way to manage everything, not requiring additional tools to get everything started. Long term short, we try to provide a solution appealing to everyone and being usable/integrate able into every environment
@@icinga Is this then, extending the icinga2.exe parameters plus some config management and a alternative for the GUI setup on headless Windows Servers? Well if it makes for a cleaner Ansible role adn easier handling of edge cases, I'm all for it - I know, nobody requested my approval ;) I noticed the menu points that will help a new user in debugging and think it's a nice touch. BTW, I just had a edge case, where I needed to do the setup by hand for a agent in the DMZ that will never have a connection back to the master and the last thing I got was the firewall rule for master -> agent - maybe to special for this tool but this would be a hard nut to crack for a "basic" user.
I'm not sure if it can be used that way, but a try would be great. In general the idea was to make everything way more easier. The scenario you described on where the agent communicates never with the master is doable by the new menu.
Thanks for the Icinga Intro. I'm trying to move from Nagios to Icinga2, however your tutorial doesn't look anything like the Icinga2 I have installed.. It looks like a completely unique application. Nagios however has stayed the same, therefore I'm still using it.
Definitely liked watching this video... I want to say a BIG Thanks for making this video. It helps sum up a lot of what goes on behind the scenes and has given me a new perspective on Icinga and its developers. Please continue doing what you do and making the product even better. You've come a long way! Thanks again.
Hello and please excuse the late response. You can do so by adding a new dashboard with te following content: Overdue Host Checks: monitoring/list/hosts?host_next_update<now Overdue Service Checks: monitoring/list/services?service_next_update<now Acknowledgement older 3 days: monitoring/list/comments?comment_type=Ack&comment_timestamp<-3 days&sort=comment_timestamp&dir=asc Downtimes older 3 days: monitoring/list/downtimes?downtime_is_in_effect=1&downtime_scheduled_start<-3%20days&sort=downtime_start&dir=asc I hope this helps and sorry again for the late response! /cs
thanks for this wonderful video Please is it possible to have the full version of this tutorial in PDF? and on which forum to subscribe for help with the installation and configuration of icinga 2
@DNSmichi - Where is the code that you said will share; regarding aws auto create object and delete.. can you please share the sample code, i am working on similar thing with Oracle VM Manager API's
Beach Samurai Aussie may be more accurate. Most English speakers, and multilingual Europeans with their ear for diverse language rhythms, should be able to understand the presenter; I'd expect so anyway. I would agree that the volume is a little low -- like she's whispering. I'd recommend a redo just for that, unfortunately, as it'd be so much better with more voice.
