23. 12. 2024
APM, Development, Log-SIEM, NetEye
In case of passive checks as for example SNMP traps or notifications via email from external checking systems, it is not always possible to know if these controls are correctly performed.
This is the reason that made us decide to look for a solution able to ensure that the passive checks are being regularly provided by external applications. To reach our target we opted for the freshness check of Nagios, that as the word itself is suggesting is a check that verifies the freshness of the results provided.
Nagios, in fact, supports freshness checks on host and service passive check results. The freshness check aims to ensure that host and service checks are being passively provided by external applications on a regular basis. In particular, it will be guaranteed that the passive checks are registered in the expected time period. For example, if you have a daily check at 8 a.m., the freshness check will verify that the results are received exactly in that configured time frame.
How does it work?
Nagios performs periodic checks to verify the passive check results for all those hosts and services that have the freshness check enabled.
- A “freshness” threshold is calculated for each host or service
- For each host/service, the age of its last check result is compared with the freshness threshold.
- If last check result is received on a time above the freshness threshold, the check result is considered “stale”.
How is the Freshness Check enabled?
Here the procedure to follow to enable the freshness check:
- Use the check_service_freshness and check_host_freshness directives, that are already enabled by default in NetEye
- Use service_freshness_check_interval and host_freshness_check_interval options to tell Nagios how often it should check the freshness of service and host results – configuration already enabled by default in NetEye
- Enable freshness checking on a host- and service-specific basis by setting the check_freshness option and activating the checkbox near the same option in Monarch
- Configure freshness thresholds by setting the freshness_threshold option in your host and service definitions
- Configure the check_command option in your host or service definitions to reflect a valid command that should be used to actively check the host or service when it is detected as “stale”
- The check_period option in your host and service definitions is used when Nagios determines when a host or service can be checked for freshness, so make sure it is set to a valid timeperiod
Juergen Vigna
NetEye Solution Architect at Würth Phoenix
I have over 20 years of experience in the IT branch. After first experiences in the field of software development for public transport companies, I finally decided to join the young and growing team of Würth Phoenix. Initially, I was responsible for the internal Linux/Unix infrastructure and the management of CVS software. Afterwards, my main challenge was to establish the meanwhile well-known IT System Management Solution WÜRTHPHOENIX NetEye. As a Product Manager I started building NetEye from scratch, analyzing existing open source models, extending and finally joining them into one single powerful solution. After that, my job turned into a passion: Constant developments, customer installations and support became a matter of personal. Today I use my knowledge as a NetEye Senior Consultant as well as NetEye Solution Architect at Würth Phoenix.
Author
Latest posts by Juergen Vigna
30. 08. 2024
Log-SIEM, NetEye, Unified Monitoring
Monitor your Elasticsearch Shards Count
02. 07. 2024
NetEye
Monitor the Tasks in the Windows Task Scheduler
23. 02. 2024
Log-SIEM, NetEye, Unified Monitoring
Monitoring Logs in Elasticsearch: A Practical Example