"The execution of checks occurs at fixed intervals in
status-based monitoring.
Checkmk uses one minute as its standard. Every check is therefore
performed
once per minute. This can be altered in the configuration:
To a longer interval in order to save CPU resources on the
server and target systems
To a shorter interval in order to receive alerts more quickly
and to collect performance data at a higher resolution."
The first one is what we want to do (save resources on target
servers). And specially we want to increas check interval on
services like apt-get updates, Yum updates, NTP time and so on.
For that, we try to use WATO >> Host & Service
Monitoring Configuration and rules “Normal check
interval for service checks” and “Retry check interval …”.
We are up-to-date in Check-MK server (RAW 1.5.0p16) but that
don’t work.
I think we don’t understand waht rules are doing effectively ?
Please, where are we wrong ?
(NB: We don’t want to increase notification interval)
Thanks in Advance,
Best regards,
···
-- Université de Bordeaux Didier CAPDEVIELLE
Ingénieur. Service Intégration des Applications / Bureau Déploiement des Services Numériques, ____________________________________________________________________________________________
Direction des systèmes d'information
The first one is what we want to do (save resources on target servers).
And specially we want to increas check interval on services like apt-get
updates, Yum updates, NTP time and so on.
This are all checks that are based on agent data. Check_MK queries the
agent in the interval of the "Check_MK" service check which is usually
every minute. You cannot set another interval for these checks.
Both updates checks come from data that is generated by agent plugins.
These plugins can be configured to run in a different interval on the
host therefor updating their data not as often.
The first one is what we want to do (save resources on target servers).
And specially we want to increas check interval on services like apt-get
updates, Yum updates, NTP time and so on.
This are all checks that are based on agent data. Check_MK queries the
agent in the interval of the "Check_MK" service check which is usually
every minute. You cannot set another interval for these checks.
OK. We was deceived by the name of the rules. (What do they do exactly ?)
Both updates checks come from data that is generated by agent plugins.
These plugins can be configured to run in a different interval on the
host therefor updating their data not as often.
Didier CAPDEVIELLE
Ingénieur. Service Intégration des Applications / Bureau Déploiement des Services Numériques,
____________________________________________________________________________________________
Direction des systèmes d'information
This are all checks that are based on agent data. Check_MK queries the
agent in the interval of the "Check_MK" service check which is usually
every minute. You cannot set another interval for these checks.
OK. We was deceived by the name of the rules. (What do they do exactly ?)
Please make yourself familiar with the difference between active and
passive checks in a Nagios monitoring system.
You can only set a check interval on active checks.
Regards
--
Robert Sander
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin
Tel: 030 / 405051-43
Fax: 030 / 405051-19
Amtsgericht Berlin-Charlottenburg - HRB 93818 B
Geschäftsführer: Peer Heinlein - Sitz: Berlin
This are all checks that are based on agent data. Check_MK queries the
agent in the interval of the "Check_MK" service check which is usually
every minute. You cannot set another interval for these checks.
OK. We was deceived by the name of the rules. (What do they do exactly ?)
Please make yourself familiar with the difference between active and
passive checks in a Nagios monitoring system.
You can only set a check interval on active checks.
Sorry, just a last question.
On a test, i move mk_apt to /usr/lib/check_mk_agent/plugins/3600
Didier CAPDEVIELLE
Ingénieur. Service Intégration des Applications / Bureau Déploiement des Services Numériques,
____________________________________________________________________________________________
Direction des systèmes d'information
Yes, that is normal because the agent will send the data every 60
seconds. It will only refresh the plugin output every hour and use
cached data in between.
Regards
···
On 17.05.19 14:15, Didier Capdevielle wrote:
Column CHECKED never exceeds 60 s. Is it normal ?
--
Robert Sander
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin
Tel: 030 / 405051-43
Fax: 030 / 405051-19
Amtsgericht Berlin-Charlottenburg - HRB 93818 B
Geschäftsführer: Peer Heinlein - Sitz: Berlin
Yes, that is normal because the agent will send the data every 60
seconds. It will only refresh the plugin output every hour and use
cached data in between.
Didier CAPDEVIELLE
Ingénieur. Service Intégration des Applications / Bureau Déploiement des Services Numériques,
____________________________________________________________________________________________
Direction des systèmes d'information
