In one of my last projects, I had to implement a job scheduler to the IT environment of one of our NetEye customers, whereby a central requirement was that it had to be possible to launch jobs directly from NetEye. The customer had chosen the job scheduler solution from SOS Berlin, which had to be installed on a Linux environment.
Before explaining you how I did the integration, I will shortly explain how the customer is working.
IT-Orchestration with NetEye
To follow the ITIL best practices, the company’s Help Desk is using NetEye for the identification of problems on the IT infrastructure and the orchestration of the detected problems. If the Help Desk in case of a problem gets an alert, the help desk employees to relaunch certain processes use the so-called ActionLaunchpad module of NetEye. Therefore, for the employees the NetEye GUI is the “single” point of contact to the IT infrastructure: not only for monitoring, but also for restarting processes.
Job Scheduler required
At a certain moment, the customer had the necessity to implement a job scheduler to trigger a sequence of jobs on different systems like Unix, Windows etc. They have chosen the SOS Berlin JobScheduler, for which we, by the way, are also offering consultancy.
NetEye remains single point of contact
One of the main requirements the customer explained to me was that the NetEye GUI had to remain the only GUI, which the Help Desk employees should use. This was because the customer wished to avoid confusing his employees by implementing a new interface for restarting or monitoring scheduled jobs.
For this reason, I implemented different interfaces between the job scheduler and NetEye. This allows that each job scheduled on the job scheduler that failed will create an alert on the NetEye interface. In this way, the Help Desk is able to see the problem and to restart the failed jobs by using the NetEye ActionLaunchpad with which they are already familiar. Hence, for the Help Desk people there is no need to learn in detail the job schedulers’ GUI and configuration possibilities.
I started my professional career as a system administrator.
Over the years, my area of responsibility changed from administrative work to the architectural planning of systems.
During my activities at Würth Phoenix, the focus of my area of responsibility changed to the installation and consulting of the IT system management solution WÜRTHPHOENIX NetEye.
In the meantime, I take care of the implementation and planning of customer projects in the area of our unified monitoring solution.
Author
Tobias Goller
I started my professional career as a system administrator.
Over the years, my area of responsibility changed from administrative work to the architectural planning of systems.
During my activities at Würth Phoenix, the focus of my area of responsibility changed to the installation and consulting of the IT system management solution WÜRTHPHOENIX NetEye.
In the meantime, I take care of the implementation and planning of customer projects in the area of our unified monitoring solution.
When using Kibana in environments that require a proxy to reach external services, you might encounter issues with unrecognized SSL certificates. Specifically, if the proxy is exposed with its own certificate and acts as an SSL terminator, requests made by Read More
In a previous post we went through the configuration of Elastic Universal Profiling in NetEye, seeing how we can profile applications written in programming languages that do not compile to native code (for example Python, PHP, Perl, etc.) But what Read More
Elastic 8.16, which comes with NetEye 4.39, made Elastic Universal Profiling generally available for self-hosted installations. This means that NetEye SIEM installations will now be able to take advantage of the continuous profiling solution by Elastic. In this blog post Read More
In the first part of this series, we explored how Jira Service Management (JSM) helps streamline Incident Management, aligning with ITIL v4 best practices. Incident Management aims to restore normal service operation as quickly as possible after a disruption, ensuring Read More
Hello everyone! Today, I'd like to briefly discuss an improvement to the update and upgrade procedures that we've started to adopt with NetEye 4.39! What we wanted to improve One aspect that made quite an impact was that whenever the Read More