About Ramiro Ferrão
Ramiro has been working with Nagios (both Core and XI) for almost 10 years, starting in 2016. Since then, he has been tasked with managing the solution by performing:
– backup, optimization, and configuration of the platform and its monitoring objects
– migration and/or database offloading between servers
– plugin/wizard/script development, for various monitoring and integration purposes
– broker modules implementation and development, such as mod_gearman and retention_dr (customer project)
– bug/vulnerability reports and troubleshooting for both PHP and C codebases
…and many other assignments. Lately, as cybersecurity has been gaining momentum, he has been working with Nagios to try and leverage it as a SOAR of sorts; so, upon coming across the proposal of a stalking_notify feature, he saw an opportunity to enhance the passive checks being received from SIEM solutions — and notify only unique events, for each corresponding category.
Sessions
Stalking Notify Feature Implementation
Regarding the Stalking Notify feature proposed by Jake Omann, I have implemented a functionality where a check will notify regardless of the Notification Interval when a host and/or service—”stalking_notify” and “stalking_options” enabled and already in a PROBLEM state—will have its (HOST/SERVICE) OUTPUT changed at the next cycle of checks. The core logic as well as the motivation behind this development will be dived into to present it as an opportunity for opening up Nagios for more integrations between systems and platforms.
See You In September!
Connect with IT professionals from around the world, gain hands-on experience, and explore the latest innovations in IT monitoring.