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 IT Italy, 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 IT Italy, 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.
With Elastic Observability we can create alerts on all data we collect, such as logs, metrics, application services and synthetic monitoring. However, NetEye represents the main operational console from which to monitor the entire infrastructure. By sending alarms from Elastic Read More
Node export in the Tornado Processing Tree was broken on Firefox The bug was caused by a divergence between Firefox and Chrome in blob handling with CSP. Issue resolved, behavior is now consistent across both browsers. List of updated packages Read More
Processing Tree Rendering Issue We shipped a fix for a rendering bug in the Tornado UI Processing Tree. Under specific conditions, navigating back to the dashboard after expanding tree nodes caused the tree to render incorrectly nodes would appear collapsed, Read More
Role Search Now Works in Access Control We've fixed the search functionality in the Roles view under Configuration - Access Control, so you can now find roles instantly without any errors. List of updated packages To solve the issues mentioned Read More
Hi everyone! Today I'd like to share with you an investigation we undertook related to ingesting Open Telemetry data in Elasticsearch, while maintaining tenant segregation from start to end. The Scenario Let's imagine we have multiple customers, where in this Read More