Michael Medin released NSClient++ 0.5.0 this week. We’re of course considering to update the bundled NSClient++ installer inside the Windows package.
First things first – the NSClient++ 0.5.0 Changelog mentions breaking changes, so we’ll need to test the ITL CheckCommands still working prior to the next Icinga 2 release (follow #12733). In case you want to help test yourself – you can safely upgrade the NSClient++ application in Windows yourself and fire your Icinga 2 checks against it (just install the new 0.5.0 package).
One cool thing to note about NSClient++ 0.5.0 – it comes with its own web server which also provides a REST API. That could introduce a solution for querying metrics via REST API which require rate calculation (CPU) from a running nscp service. This could be easily integrated into a native Icinga 2 client check plugin then. Let’s just try this out on my Windows 10 VM! :-)
You can build simple Icinga 2 setups where everything is checked and notified 24×7. If you are planning with bigger setups and multiple user groups being notified on problems, you’ll certainly get the task to filter specific time ranges or notification types. Or you’ll consider partial check times e.g. when a service is definitely not available and you don’t want your SLA reporting faked with downtimes.
One common thing is to limit the notifications sent to users to “9 to 5”. The configuration requires the following addition:
- TimePeriod object named “9to5” (available in the example configuration in timeperiods.conf)
- Referenced as “period” attribute in your Notification object or apply rule
Human beings don’t work 5 days a week and 52 weeks over the whole year. Vacation is needed, finding some rest without any work. And you obviously don’t want to get notified about Icinga problems during that period of time. In addition to that there are several days or hours where no-one wants to get notified except for the 24×7 support (new year’s eve, christmas, etc.).
We keep working together as an open source community. We’re here to listen what you say – keep it polite and encourage/motivate us to solve your problem with you as best as we can. Lean back and think how others would react if you click “send”, frustrated with an issue tab opened in your browser. Sometimes it doesn’t hurt to just close the tab or rephrase. The person on the other end (dev and/or user) will appreciate it. In the end we all are human beings with emotions, language & culture differences and offline needs (friends, family, hobbies, etc.). What we have in common – we all want to build a great Icinga monitoring product together :)
Bernd did a great ignite on that topic with “Working in and with Open Source Communities” at DevOpsDays Amsterdam (video starts at 17:35).
We’ve come a long way with our new release Icinga 2 v2.5. After the 2.4 release in November we’ve focussed on fixing many of the remaining bugs. 2.5 isn’t just a feature release – it includes all the bugfixes from the past months. (more…)
What really drives us making Icinga a great monitoring solution is community feedback and appreciation.
One thing which is really really cool – when someone sends you an email and says “Look. Icinga 2 works fine. Awesome work.” – attaching a screenshot with a hell of CPU cores and RAM. I cannot tell you this time which company he’s working for (only that the company is a NETWAYS customer we’ve been working with). This is JUST AWESOME. (more…)