Almost 2 years ago, we first announced the start of our new NetEye 4 product. With NetEye 4 we started to build our monitoring solution on top of the popular Icinga2 and Icingaweb2 framework.
Having been in the position of implementing some of the first projects based on NetEye 4, I recognized the need for providing additional default configurations and to automate the setup of this new world. After those first experiences, I found myself with a collection of configurations and scripts to automate specific steps during a setup.
The obvious next step was to share that information with my colleagues, leading me to ask myself – why should we keep this information just inside our group when there are so many people and organizations out there using Icinga2 who could benefit from this information?
This was the moment in late 2018 when I initiated the first commit on my github account, founding the repository neteye4. In the early days, it consisted of just a few scripts to automate the deployment of the Icinga2 Agent, making use of the PowerShell framework to configure the Agent using Director’s self-service API.
Thanks to the contributions of colleagues and brainstorming with them, the content grew and grew, and today the repository provides scripts to automate the setup of a web-based neteyeshare, including the Agents along with some additional configuration templates.
Some of the contents provided within neteyeshare
A second repository, the icinga2-monitoring-templates, now provides a collection of monitoring-related content, directly importable via scripts into Icinga Director. A short Readme guides even new users or explorers of NetEye 4 through the steps of configuring a fresh installation of NetEye 4 and importing those templates.
The number of objects provided in the various categories
Growing with Community Contributions
Projects on GitHub are public for a good reason: everyone may access the data and everyone may contribute to it. Over the course of this year, I had the occasion to collaborate with colleagues and business partners, who helped me to review and enrich the content provided in these two repositories. It has been impressive to see the number of commits and contributions over the last year!
We’ve now arrived at the end of the year, a period of holidays and good times. And so it’s also time for me to thank everyone who spent some of their own time contributing to the content of this community project! Let’s continue and grow in 2020 ,)
After my graduation in Applied Computer Science at the Free University of Bolzano I decided to start my professional career outside the province. With a bit of good timing and good luck I went into the booming IT-Dept. of Geox in the shoe district of Montebelluna, where I realized how a big IT infrastructure has to grow and adapt to quickly changing requirements. During this experience I had also the nice possibility to travel the world, while setting up the various production and retail areas of this company. Arrived at Würth Phoenix I started developing on our monitoring solution NetEye. Today, in my position as Consulting an Project Manager I am continuously heading to implement our solutions to meet the expectation of your enterprise customers.
Author
Patrick Zambelli
After my graduation in Applied Computer Science at the Free University of Bolzano I decided to start my professional career outside the province. With a bit of good timing and good luck I went into the booming IT-Dept. of Geox in the shoe district of Montebelluna, where I realized how a big IT infrastructure has to grow and adapt to quickly changing requirements. During this experience I had also the nice possibility to travel the world, while setting up the various production and retail areas of this company. Arrived at Würth Phoenix I started developing on our monitoring solution NetEye. Today, in my position as Consulting an Project Manager I am continuously heading to implement our solutions to meet the expectation of your enterprise customers.
In our previous post we discussed how to handle RD users using CMDO, focusing on the scripts needed to obtain a unique identifier for each users in the RD Farm. In this post I want to focus on how to Read More
ScenarioIn a Microsoft Remote Desktop environment, it’s a common need to force the logoff of a hanged user session. The NetEye Command Orchestrator (CMDO) can help us perform this task by executing remote commands through the Icinga2 agent API. There’s Read More
In recent months many enterprise customers have asked me for a solution to create services on their monitored Icinga hosts automatically. They want a single point of insertion (like a list) for all services on the host as well as Read More
During migrations from NetEye 3 to NetEye 4, I often run into really outdated monitoring checks in the Windows world, where the last update was more than 10 years ago... and whose logic is therefore now completely obsolete! The time Read More
We fixed wrong permissions on spool directory, which were preventing send sms-notification. For NetEye 4.18 we updated the following packages: smstools-neteye-config to version 1.5.1-1icinga2, icinga2-autosetup, icinga2-bin, icinga2-common, icinga2-debuginfo, icinga2-doc, icinga2-ido-mysql, icinga2-ido-pgsql, icinga2-neteye-config, icinga2-resources, icinga2-selinux to version 2.11.6_neteye1.33.1-1