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.
Fixing Misplaced Plugin Output in Icinga Web Interface When plugin output contained HTML content (like links), it was incorrectly displayed near the service name instead of in the Plugin Output section. The plugin output section now correctly renders all content. Read More
Icinga Director Now Responsive During Configuration Deployments Previously, users were unable to interact with Icinga Director while configuration deployments were running. Any attempt to access the interface or API would be blocked until the deployment completed, causing unnecessary delays in Read More
Bug Fix We updated the version of GLPI in order to fix some relevant vulnerabilities. List of updated packages The following packages have been updated for NetEye 4.45: glpi, glpi-autosetup, glpi-configurator, glpi-neteye-config to version 10.0.22_neteye1.17.5-1.
Bug Fix in Tornado Module We solved an issue in Tornado's rule configuration where the action_name field in director actions was being cleared after saving and deploying. When users created a rule with a director action and filled in both Read More
Today we continue our journey into monitoring automation in NetEye. In my previous post we discussed the possibility of automating Business Processes. As you may remember, for those of us working on NetEye Cloud monitoring dozens of clients, it's important Read More