In NetEye environments we use Tornado to collect events, elaborate on them, and send notifications based on them from a lot of sources (syslog, email, SNMP traps and so on). In this article I’d like to suggest a different use case: how to use Tornado to monitor your cron jobs. In our example we want to use NetEye to track the status of a sequence of dependent scripts.
Suppose you need to weekly runa script composed of three commands: the first two extract data from different sources, while the third one merges the previously extracted data. For each script we want to keep track of the results in NetEye. We also want to be notified when any script is not executed.
Here the three scripts :
extract-info-source1
extract-info-source2
merge-sources
Host and Service Creation
We begin by creating a dummy host:
then creating (if it’s not already present) a service template with a check interval:
and next a service template with an auto-reset delay of one week:
Finally, create the three services (here’s the first one):
Deploy the configuration in Director and we’ll now have our host/services ready to be used:
That’s it for today. In my next article we’ll create the Tornado configuration to send the script status on NetEye and monitor your scheduled jobs.
These Solutions are Engineered by Humans
Did you find this article interesting? Are you an “under the hood” kind of person? We’re really big on automation and we’re always looking for people in a similar vein to fill roles like this one as well as other roles here at Würth Phoenix.
In NetEye, 'business processes' is a module used to model and monitor the business process hierarchy to obtain a high-level view of the status of critical applications. In short, they allow monitoring controls of individual components to be aggregated into Read More
If you've worked with Elastic APM, you're probably familiar with the APM Server: a component that collects telemetry data from APM Agents deployed across your infrastructure. But what happens when you need to segregate that data by tenant, especially in Read More
In the first part we created hosts and services to monitor a sequence of script using Tornado. The Tornado Rule Now let's continue with the creation of a Tornado rule: open the NetEye web interface and select Tornado dashboard, then Read More
Some time ago, my colleague Giuseppe Di Garbo published this article on the NetEye Blog, where he explained how to integrate NetEye notifications with Telegram. It was a great starting point, and in fact many of us used it to Read More
In the latest update to NetEye 4.42, we're excited to announce the introduction of support for the Content-Security-Policy (CSP) header within the Icinga Web 2 interface. This enhancement plays a crucial role in strengthening your system's defenses against cross-site scripting Read More