From a9c5fd17f2bb3131b7821997badd0ed201153a0f Mon Sep 17 00:00:00 2001 From: frayber Date: Tue, 19 Feb 2019 11:19:46 +0100 Subject: [PATCH] nrpe.cfg.in thresholds for check_load Please refer to https://github.com/NagiosEnterprises/nrpe/issues/171 Even if it's not simple set general cpu_load thresholds for every system, I suggest to increase these values because are too low. Generally, 1 for core is considered the bottleneck, so I suggest these new values. --- sample-config/nrpe.cfg.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sample-config/nrpe.cfg.in b/sample-config/nrpe.cfg.in index 1d503c9..c96655a 100644 --- a/sample-config/nrpe.cfg.in +++ b/sample-config/nrpe.cfg.in @@ -296,7 +296,7 @@ connection_timeout=300 # This is by far the most secure method of using NRPE command[check_users]=@pluginsdir@/check_users -w 5 -c 10 -command[check_load]=@pluginsdir@/check_load -r -w .15,.10,.05 -c .30,.25,.20 +command[check_load]=@pluginsdir@/check_load -r -w .9,.8,.7 -c 1,.9,.8 command[check_hda1]=@pluginsdir@/check_disk -w 20% -c 10% -p /dev/hda1 command[check_zombie_procs]=@pluginsdir@/check_procs -w 5 -c 10 -s Z command[check_total_procs]=@pluginsdir@/check_procs -w 150 -c 200