If you are using our Asset Management module integrated into NetEye, you probably already know about the potential of OCS Inventory and GLPI. However, often users are not aware of all the functionalities available in Life Cycle Asset Management. So let’s highlight some of the most important features to manage the entire life cycle of your assets:
All about the Open Source based IT System Management with integrated Asset, Inventory and Traffic Monitoring features.
Experiences and sample applications on the Network Traffic monitoring tool identifying network usage in real time.
EriZone & OTRS
Learn more about the leading Open Source Service Desk and Ticketing System available in 32 languages and adopted by over 110,000 organizations worldwide.
Developers, SysAdmins, Community members, Nagios experts and Open Source enthusiasts. See who´s writing.
NetEye & EriZone User Group
Challenges and opportunities in the IT Management 4.0
Connectbay, Mantova, October 19, 11:00 – 17:00
We are glad to invite you to attend the NetEye & EriZone User Group. The yearly event for our customers will offer you the possibility to discover the innovations in the IT Service Management field, to identify modern approaches for the Performance Monitoring and to participate in the definition of our solution roadmap.
Machine learning and anomaly detection are being mentioned with increasing frequency in performance monitoring. But what are they and why is interest in them rising so quickly?
From Statistics to Machine Learning
There have been several attempts to explicitly differentiate between machine learning and statistics. It is not so easy to draw a line between them, though.
For instance, different experts have said:
- “There is no difference between Machine Learning and Statistics” (in terms of maths, books, teaching, and so on)
- “Machine Learning is completely different from Statistics.” (and the only future of both)
- “Statistics is the true and only one” (Machine Learning is a different name used for part of statistics by people who do not understand the real concepts of what they are doing)
In short we will not answer this question here. But for monitoring people it is still relevant that the machine learning and statistics communities currently focus on different directions and that it might be convenient to use methods from both fields. The statistics community focuses on inference (they want to infer the process by which data were generated) while the machine learning community puts emphasis on the prediction of what future data are expected to look like. Obviously the two interests are not independent. Knowledge about the generating model could be used for creating an even better predictor or anomaly detection algorithm.
Every so often I get asked whether it is possible to integrate Active Directory Users and Groups with NetEye. Until now my answer has always been that it is possible to use AD via its LDAP functionality as an authentication backend, and that you may manually add each AD user one-by-one to NetEye.
I was never very satisfied with this answer and so I tried to find a solution. Here’s what needs to be done:
Usually, during a new EriZone implementation, we are not just implementing “simple” Incident Management, but also defining processes to standardize existing procedures within the company.
Investing time now in the implementation of a standardized process will pay dividends later, especially in the case of multilevel authorizations or other workflows where the ticket needs to follow a predefined path.
Thanks to EriZone’s “process bundle”, tickets that have a given service and category automatically trigger a predefined process flow. Thus a new ticket automatically enters the appropriate pipeline defined in the standardization process.
Service desk systems are of great importance to most IT departments. They are used to manage not only incidents and service requests, but also for authorizations and the management of internal projects. Moreover, data obtained from an ITSM system can be used for time accounting, invoicing and cost estimates. Finally, yet importantly, tickets and their metadata build a structured and searchable request history and knowledge base.
In the event a ticketing system needs to be merged with another system or has to be completely shut down, it is important that this precious data be preserved.
Whether you are responsible for your company’s Network Operations Center (NOC), or you are just generally interested in the topic of infrastructure monitoring, this article will be of interest to you.
We built the Action Launchpad module for NetEye to simplify the execution of remote commands (proactive actions). When resolving some anomaly you find yourself needing to execute a well-defined sequence of steps, you can automate this using the Action Launchpad. The Launchpad works by exposing a web interface to execute predefined commands on certain servers.
If you don’t work in the field of IT service management, you might suppose that a service desk, and especially an IT service desk, is something quite standard… having similar services and a similarly structured support staff structures across all companies.
However, despite having (apparently) a very similar goal and trying to follow a common terminology and guidelines such as the ITIL standard for IT service management, each company has its own specific demands and processes put into practice for providing service to both their internal and external customers. These processes differ on the type of service given, the number of service requests, their distribution among services, the complexity of requests, etc. In addition, the level of expertise of the support staff members, the internal organization of the (IT-)department, and the concepts and architecture of the supporting tools have a decisive influence on the service processes being implemented.
“Is there any way to speed up opening new tickets?”
This is a typical question new EriZone customers ask during project implementation. The reason is quite obvious: If you have a large Service Desk team that is opening several hundred tickets each day, every second counts. Especially in situations where the resolution time is critical, a shortcut for quickly selecting service, category, and potentially other fields may be of great advantage.
Thanks to an additional configuration which will be available starting with EriZone 5.2, you will be able to add the menu item “Ticket Template”. This new option will allow you to add and configure this item within the webpage itself. Once a template has been created, the agent will be able to use that template to create a new ticket. The form that appears will contain the predefined content inside the corresponding fields. Then the agent just has to fill in the remaining fields in order to create the new ticket.
Depending on the groups an agent belongs to, he will see a different set of templates. For example, agents in the group “ServiceDesk_Template_G” will see templates different from those available for members of the group “Network”.
Below you can see an example of a ticket regarding a malfunction of the email service.
Icinga Web 2 is a powerful PHP framework for web applications in a clean, minimal design. It’s fast, responsive, accessible and easily extensible with modules. It can be installed quickly and easily from packages found in the official package repositories (see the resource links at the bottom of this blog post).
Besides the global configuration settings, each user has individual configuration options like the interface’s language, the current time zone, and the preferred theme. My aim here is to explain how you can easily create a new customized theme to make your Icinga interface the one you’ve always dreamed of.
Doing my work as monitoring consultant, I often have to monitor Nutanix systems on customer site. Nutanix is a integrated systems vendor that produces a hyper-converged storage system called “Virtual Computing Platform”.
It is quiet easy to monitor the Nutanix system and with NetEye you will be able to get the best results and visualization possibilities.
You will monitor the Nutanix system by using the SNMP protocol:
After a long test phase today we released a new version of our NetEye base OS packages, which is CentOS 6.9. It provides various bug fixes and improvements.
For a change log see CentOS 6.9 Release Notes.
There are no problems for customers continuing using CentOS 6.8.
Network traffic keeps becoming more and more heterogeneous. In many cases, it is not enough to monitor a system as we have done in the past. Here I will present the key ingredients according to Würth Phoenix for successful state of the art performance monitoring and proactive analysis of those applications that are critical for your business.
Combining User Experience and Performance Metrics for new Insights
User experience is a very important factor. If your measurements seem in the right range, BUT end users complain about slow applications, you need to act. For this reason, user experience combined with an overview of all the servers being put under monitoring is the right place to start. In our opinion it is of vital importance to know when critical business applications begin to slow down before your users start to complain. You can achieve this by running continuous checks via Alyvix – our active user experience monitoring solution. Test cases can be written specifically for the most vital parts of your applications, and the functionality and speed of those very parts can be checked as often as needed. The outcome in terms of performance of each individual user interaction tested is then saved into the same central time series data base as the performance metrics registered from all original sources of interest (such as Perfmon data, ESX performance data, etc.) It is then possible to perform a multiserver zoom and with a single click to navigate to the most interesting servers during time periods where Alyvix detected problems.
The NetEye APIs offer a simple way to automate and script common processes on NetEye. They expose more than 150 objects written in Perl, which can be easily used and extended. The NetEye APIs allow you to perform several actions: add/modify/remove a host, service or business process from Nagios, as well as compute the availability of these objects over a given period of time. The APIs are open source, and you can find the Perl code installed at /var/lib/neteye/API. However, if you modify your code locally, your changes will be overwritten at the next API update. In this article I will show you how to do make your changes to the NetEye APIs persist across updates.
Keeping an offline copy of your logs does not only provide better visibility from the system management point of view, but also turns out to be extremely precious in case of a security incident during which your local copies have been affected.
As many of you might know, the Log Management module of NetEye offers a complete solution to manage logs, in line with the obligations intended by the data protection authority. Moreover, it provides a handy way to centrally manage logs from various sources. (see also on our blog: “What to do with all those logs?” and “NetEye Log Management on the official Elastic blog” ).
Architecture of the Log Management module:
- Log auditing and data collection system, based on rsyslog
- Agent (Safed) for sending logs over the syslog protocol (RFC 3164 – configured by default to send over TCP on port 514 to guarantee the correct receiving of the sent logs)
It is crucial that the communication between the Safed agents and NetEye on the TCP port 514 is always guaranteed.
During one of my latest customer projects, I was asked to implement a possibility for collecting logs from remote systems in the cloud. The main challenge was that accessing the systems was possible just via SSH.
Now I will show you how I resolved this problem by using a reverse SSH tunnel and a Safed agent on a Linux/Unix machine.