1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Main Configuration File Options</title>
<STYLE type="text/css">
<!--
.Default { font-family: verdana,arial,serif; font-size: 8pt; }
.PageTitle { font-family: verdana,arial,serif; font-size: 12pt; font-weight: bold; }
-->
</STYLE>
</head>
<body bgcolor="#FFFFFF" text="black" class="Default">
<p>
<div align="center">
<h2 class="PageTitle">Main Configuration File Options</h2>
</div>
</p>
<hr>
<p>
<strong><u>Notes</u></strong>
</p>
<p>
When creating and/or editing configuration files, keep the following in mind:
</p>
<p>
<ol>
<li>Lines that start with a '#' character are taken to be comments and are not processed
<li>Variables names must begin at the start of the line - no white space is allowed before the name
<li>Variable names are case-sensitive
</ol>
</p>
<p>
<strong><u>Sample Configuration</u></strong>
</p>
<p>
A sample main configuration file is created in the base directory of the Nagios distribution when you run the configure script. The default name of the main configuration file is <b>nagios.cfg</b> - its usually placed in the <b>etc/</b> subdirectory of you Nagios installation (i.e. <i>/usr/local/nagios/etc/</i>).
</p>
<p>
<strong><u>Index</u></strong>
</p>
<p>
<a href="#log_file">Log file</a><br>
<a href="#cfg_file">Object configuration file</a><br>
<a href="#cfg_dir">Object configuration directory</a><br>
<a href="#object_cache_file">Object cache file</a><br>
<a href="#resource_file">Resource file</a><br>
<a href="#temp_file">Temp file</a><br>
<br>
<a href="#status_file">Status file</a><br>
<a href="#aggregate_status_updates">Aggregated status updates option</a><br>
<a href="#status_update_interval">Aggregated status data update interval</a><br>
<br>
<a href="#nagios_user">Nagios user</a><br>
<a href="#nagios_group">Nagios group</a><br>
<br>
<a href="#enable_notifications">Notifications option</a><br>
<a href="#execute_service_checks">Service check execution option</a><br>
<a href="#accept_passive_service_checks">Passive service check acceptance option</a><br>
<a href="#execute_host_checks">Host check execution option</a><br>
<a href="#accept_passive_host_checks">Passive host check acceptance option</a><br>
<a href="#enable_event_handlers">Event handler option</a><br>
<br>
<a href="#log_rotation_method">Log rotation method</a><br>
<a href="#log_archive_path">Log archive path</a><br>
<br>
<a href="#check_external_commands">External command check option</a><br>
<a href="#command_check_interval">External command check interval</a><br>
<a href="#command_file">External command file</a><br>
<br>
<a href="#comment_file">Comment file</a><br>
<a href="#downtime_file">Downtime file</a><br>
<a href="#lock_file">Lock file</a><br>
<br>
<a href="#retain_state_information">State retention option</a><br>
<a href="#state_retention_file">State retention file</a><br>
<a href="#retention_update_interval">Automatic state retention update interval</a><br>
<a href="#use_retained_program_state">Use retained program state option</a><br>
<a href="#use_retained_scheduling_info">Use retained scheduling info option</a><br>
<br>
<a href="#use_syslog">Syslog logging option</a><br>
<a href="#log_notifications">Notification logging option</a><br>
<a href="#log_service_retries">Service check retry logging option</a><br>
<a href="#log_host_retries">Host retry logging option</a><br>
<a href="#log_event_handlers">Event handler logging option</a><br>
<a href="#log_initial_states">Initial state logging option</a><br>
<a href="#log_external_commands">External command logging option</a><br>
<a href="#log_passive_checks">Passive check logging option</a><br>
<br>
<a href="#global_host_event_handler">Global host event handler</a><br>
<a href="#global_service_event_handler">Global service event handler</a><br>
<br>
<a href="#sleep_time">Inter-check sleep time</a><br>
<a href="#service_inter_check_delay_method">Service inter-check delay method</a><br>
<a href="#max_service_check_spread">Maximum service check spread</a><br>
<a href="#service_interleave_factor">Service interleave factor</a><br>
<a href="#max_concurrent_checks">Maximum concurrent service checks</a><br>
<a href="#service_reaper_frequency">Service reaper frequency</a><br>
<a href="#host_inter_check_delay_method">Host inter-check delay method</a><br>
<a href="#max_host_check_spread">Maximum host check spread</a><br>
<a href="#interval_length">Timing interval length</a><br>
<a href="#auto_reschedule_checks">Auto-rescheduling option</a><br>
<a href="#auto_rescheduling_interval">Auto-rescheduling interval</a><br>
<a href="#auto_rescheduling_window">Auto-rescheduling window</a><br>
<br>
<a href="#use_aggressive_host_checking">Aggressive host checking option</a><br>
<br>
<a href="#enable_flap_detection">Flap detection option</a><br>
<a href="#low_service_flap_threshold">Low service flap threshold</a><br>
<a href="#high_service_flap_threshold">High service flap threshold</a><br>
<a href="#low_host_flap_threshold">Low host flap threshold</a><br>
<a href="#high_host_flap_threshold">High host flap threshold</a><br>
<br>
<a href="#soft_service_dependencies">Soft service dependencies option</a><br>
<br>
<a href="#service_check_timeout">Service check timeout</a><br>
<a href="#host_check_timeout">Host check timeout</a><br>
<a href="#event_handler_timeout">Event handler timeout</a><br>
<a href="#notification_timeout">Notification timeout</a><br>
<a href="#ocsp_timeout">Obsessive compulsive service processor timeout</a><br>
<a href="#ochp_timeout">Obsessive compulsive host processor timeout</a><br>
<a href="#perfdata_timeout">Performance data processor command timeout</a><br>
<br>
<a href="#obsess_over_services">Obsess over services option</a><br>
<a href="#ocsp_command">Obsessive compulsive service processor command</a><br>
<a href="#obsess_over_hosts">Obsess over hosts option</a><br>
<a href="#ochp_command">Obsessive compulsive host processor command</a><br>
<br>
<a href="#process_performance_data">Performance data processing option</a><br>
<a href="#host_perfdata_command">Host performance data processing command</a><br>
<a href="#service_perfdata_command">Service performance data processing command</a><br>
<a href="#host_perfdata_file">Host performance data file</a><br>
<a href="#service_perfdata_file">Service performance data file</a><br>
<a href="#host_perfdata_file_template">Host performance data file template</a><br>
<a href="#service_perfdata_file_template">Service performance data file template</a><br>
<a href="#host_perfdata_file_mode">Host performance data file mode</a><br>
<a href="#service_perfdata_file_mode">Service performance data file mode</a><br>
<a href="#host_perfdata_file_processing_interval">Host performance data file processing interval</a><br>
<a href="#service_perfdata_file_processing_interval">Service performance data file processing interval</a><br>
<a href="#host_perfdata_file_processing_command">Host performance data file processing command</a><br>
<a href="#service_perfdata_file_processing_command">Service performance data file processing command</a><br>
<br>
<a href="#check_for_orphaned_services">Orphaned service check option</a><br>
<br>
<a href="#check_service_freshness">Service freshness checking option</a><br>
<a href="#service_freshness_check_interval">Service freshness check interval</a><br>
<a href="#check_host_freshness">Host freshness checking option</a><br>
<a href="#host_freshness_check_interval">Host freshness check interval</a><br>
<br>
<a href="#date_format">Date format</a><br>
<br>
<a href="#illegal_object_name_chars">Illegal object name characters</a><br>
<a href="#illegal_macro_output_chars">Illegal macro output characters</a><br>
<br>
<a href="#use_regexp_matching">Regular expression matching option</a><br>
<a href="#use_true_regexp_matching">True regular expression matching option</a><br>
<br>
<a href="#admin_email">Administrator email address</a><br>
<a href="#admin_pager">Administrator pager</a><br>
</p>
<p>
<a name="log_file"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Log File</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>log_file=<file_name></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>log_file=/usr/local/nagios/var/nagios.log</strong></font></td>
</tr>
</table>
</p>
<p>
This variable specifies where Nagios should create its main log file. This should be the first
variable that you define in your configuration file, as Nagios will try to write errors that it
finds in the rest of your configuration data to this file. If you have <a href="#log_rotation_method">log rotation</a> enabled, this file will automatically be rotated every hour, day, week, or month.
</p>
<p>
<a name="cfg_file"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Object Configuration File</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>cfg_file=<file_name></strong></td>
</tr>
<tr>
<td>Example:</td>
<td>
<font color="red"><strong>cfg_file=/usr/local/nagios/etc/hosts.cfg</strong></font><br>
<font color="red"><strong>cfg_file=/usr/local/nagios/etc/services.cfg</strong></font><br>
<font color="red"><strong>cfg_file=/usr/local/nagios/etc/commands.cfg</strong></font>
</td>
</tr>
</table>
</p>
<p>
This directive is used to specify an <a href="configobject.html">object configuration file</a> containing object definitions that Nagios should use for monitoring. Object configuration files contain definitions for hosts, host groups, contacts, contact groups, services, commands, etc. You can seperate your configuration information into several files and specify multiple <b>cfg_file=</b> statements to have each of them processed.
</p>
<p>
<a name="cfg_dir"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Object Configuration Directory</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>cfg_dir=<directory_name></strong></td>
</tr>
<tr>
<td>Example:</td>
<td>
<font color="red"><strong>cfg_dir=/usr/local/nagios/etc/commands</strong></font><br>
<font color="red"><strong>cfg_dir=/usr/local/nagios/etc/services</strong></font><br>
<font color="red"><strong>cfg_dir=/usr/local/nagios/etc/hosts</strong></font>
</td>
</tr>
</table>
</p>
<p>
This directive is used to specify a directory which contains <a href="configobject.html">object configuration files</a> that Nagios should use for monitoring. All files in the directory with a <b>.cfg</b> extension are processed as object config files. Additionally, Nagios will recursively process all config files in subdirectories of the directory you specify here. You can seperate your configuration files into different directories and specify multiple <b>cfg_dir=</b> statements to have all config files in each directory processed.
</p>
<a name="object_cache_file"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Object Cache File</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>object_cache_file=<file_name></strong></td>
</tr>
<tr>
<td>Example:</td>
<td>
<font color="red"><strong>object_cache_file_file=/usr/local/nagios/var/objects.cache</strong></font>
</td>
</tr>
</table>
</p>
<p>
This directive is used to specify a file in which a cached copy of <a href="configobject.html">object definitions</a> should be stored. The cache file is (re)created every time Nagios is (re)started and is used by the CGIs. It is intended to speed up config file caching in the CGIs and allow you to edit the source <a href="#cfg_file">object config files</a> while Nagios is running without affecting the output displayed in the CGIs.
</p>
<p>
<a name="resource_file"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Resource File</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>resource_file=<file_name></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>resource_file=/usr/local/nagios/etc/resource.cfg</strong></font></td>
</tr>
</table>
</p>
<p>
This is used to specify an optional resource file that can contain $USERn$ <a href="macros.html">macro</a> definitions. $USERn$ macros are useful for storing usernames, passwords, and items commonly used in command definitions (like directory paths). The CGIs will <i>not</i> attempt to read resource files, so you can set restrictive permissions (600 or 660) on them to protect sensitive information. You can include multiple resource files by adding multiple resource_file statements to the main config file - Nagios will process them all. See the sample resource.cfg file in the base of the Nagios directory for an example of how to define $USERn$ macros.
</p>
<p>
<a name="temp_file"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Temp File</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>temp_file=<file_name></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>temp_file=/usr/local/nagios/var/nagios.tmp</strong></font></td>
</tr>
</table>
</p>
<p>
This is a temporary file that Nagios periodically creates to use when updating comment data, status data, etc. The file is deleted when it is no longer needed.
</p>
<p>
<a name="status_file"></a>
<a name="status_log"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Status File</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>status_file=<file_name></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>status_file=/usr/local/nagios/var/status.dat</strong></font></td>
</tr>
</table>
</p>
<p>
This is the file that Nagios uses to store the current status of all monitored services. The status of all hosts associated with the service you monitor are also recorded here. This file is used by the CGIs so that current monitoring status can be reported via a web interface. The CGIs must have read access to this file in order to function properly. This file is deleted every time Nagios stops and recreated when it starts.
</p>
<p>
<a name="aggregate_status_updates"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Aggregated Status Updates Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>aggregate_status_updates=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>aggregate_status_updates=1</strong></font></td>
</tr>
</table>
</p>
<p>
This option determines whether or not Nagios will aggregate updates of host, service, and program status data. If you do not enable this option, status data is updated every time a host or service checks occurs. This can result in high CPU loads and file I/O if you are monitoring a lot of services. If you want Nagios to only update status data (in the <a href="#status_file">status file</a>) every few seconds (as determined by the <a href="#status_update_interval">status_update_interval</a> option), enable this option. If you want immediate updates, disable it. I would highly recommend using aggregated updates (even at short intervals) unless you have good reason not to. Values are as follows:
</p>
<p>
<ul>
<li>0 = Disable aggregated updates
<li>1 = Enabled aggregated updates (default)
</ul>
</p>
<p>
<a name="status_update_interval"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Aggregated Status Update Interval</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>status_update_interval=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>status_update_interval=15</strong></font></td>
</tr>
</table>
</p>
<p>
This setting determines how often (in seconds) that Nagios will update status data in the <a href="#status_file">status file</a>. The minimum update interval is five seconds. If you have disabled aggregated status updates (with the <a href="#aggregate_status_updates">aggregate_status_updates</a> option), this option has no effect.
</p>
<p>
<a name="nagios_user"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Nagios User</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>nagios_user=<username/UID></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>nagios_user=nagios</strong></font></td>
</tr>
</table>
</p>
<p>
This is used to set the effective user that the Nagios process should run as. After initial program startup and before starting to monitor anything, Nagios will drop its effective privileges and run as this user. You may specify either a username or a UID.
</p>
<p>
<a name="nagios_group"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Nagios Group</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>nagios_group=<groupname/GID></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>nagios_group=nagios</strong></font></td>
</tr>
</table>
</p>
<p>
This is used to set the effective group that the Nagios process should run as. After initial program startup and before starting to monitor anything, Nagios will drop its effective privileges and run as this group. You may specify either a groupname or a GID.
</p>
<p>
<a name="enable_notifications"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Notifications Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>enable_notifications=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>enable_notifications=1</strong></font></td>
</tr>
</table>
</p>
<p>
This option determines whether or not Nagios will send out <a href="notifications.html">notifications</a> when it initially (re)starts. If this option is disabled, Nagios will not send out notifications for any host or service. Note: If you have <a href="#retain_state_information">state retention</a> enabled, Nagios will ignore this setting when it (re)starts and use the last known setting for this option (as stored in the <a href="#state_retention_file">state retention file</a>), <i>unless</i> you disable the <a href="#use_retained_program_state">use_retained_program_state</a> option. If you want to change this option when state retention is active (and the <a href="#use_retained_program_state">use_retained_program_state</a> is enabled), you'll have to use the appropriate <a href="extcommands.html">external command</a> or change it via the web interface. Values are as follows:
</p>
<p>
<ul>
<li>0 = Disable notifications
<li>1 = Enable notifications (default)
</ul>
</p>
<p>
<a name="execute_service_checks"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Service Check Execution Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>execute_service_checks=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>execute_service_checks=1</strong></font></td>
</tr>
</table>
</p>
<p>
This option determines whether or not Nagios will execute service checks when it initially (re)starts. If this option is disabled, Nagios will not actively execute any service checks and will remain in a sort of "sleep" mode (it can still accept <a href="passivechecks.html">passive checks</a> unless you've <a href="#accept_passive_service_checks">disabled them</a>). This option is most often used when configuring backup monitoring servers, as described in the documentation on <a href="redundancy.html">redundancy</a>, or when setting up a <a href="distributed.html">distributed</a> monitoring environment. Note: If you have <a href="#retain_state_information">state retention</a> enabled, Nagios will ignore this setting when it (re)starts and use the last known setting for this option (as stored in the <a href="#state_retention_file">state retention file</a>), <i>unless</i> you disable the <a href="#use_retained_program_state">use_retained_program_state</a> option. If you want to change this option when state retention is active (and the <a href="#use_retained_program_state">use_retained_program_state</a> is enabled), you'll have to use the appropriate <a href="extcommands.html">external command</a> or change it via the web interface. Values are as follows:
</p>
<p>
<ul>
<li>0 = Don't execute service checks
<li>1 = Execute service checks (default)
</ul>
</p>
<p>
<a name="accept_passive_service_checks"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Passive Service Check Acceptance Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>accept_passive_service_checks=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>accept_passive_service_checks=1</strong></font></td>
</tr>
</table>
</p>
<p>
This option determines whether or not Nagios will accept <a href="passivechecks.html">passive service checks</a> when it initially (re)starts. If this option is disabled, Nagios will not accept any passive service checks. Note: If you have <a href="#retain_state_information">state retention</a> enabled, Nagios will ignore this setting when it (re)starts and use the last known setting for this option (as stored in the <a href="#state_retention_file">state retention file</a>), <i>unless</i> you disable the <a href="#use_retained_program_state">use_retained_program_state</a> option. If you want to change this option when state retention is active (and the <a href="#use_retained_program_state">use_retained_program_state</a> is enabled), you'll have to use the appropriate <a href="extcommands.html">external command</a> or change it via the web interface. Values are as follows:
</p>
<p>
<ul>
<li>0 = Don't accept passive service checks
<li>1 = Accept passive service checks (default)
</ul>
</p>
<p>
<a name="execute_host_checks"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Host Check Execution Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>execute_host_checks=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>execute_host_checks=1</strong></font></td>
</tr>
</table>
</p>
<p>
This option determines whether or not Nagios will execute on-demand and regularly scheduled host checks when it initially (re)starts. If this option is disabled, Nagios will not actively execute any host checks, although it can still accept <a href="passivechecks.html">passive host checks</a> unless you've <a href="#accept_passive_host_checks">disabled them</a>). This option is most often used when configuring backup monitoring servers, as described in the documentation on <a href="redundancy.html">redundancy</a>, or when setting up a <a href="distributed.html">distributed</a> monitoring environment. Note: If you have <a href="#retain_state_information">state retention</a> enabled, Nagios will ignore this setting when it (re)starts and use the last known setting for this option (as stored in the <a href="#state_retention_file">state retention file</a>), <i>unless</i> you disable the <a href="#use_retained_program_state">use_retained_program_state</a> option. If you want to change this option when state retention is active (and the <a href="#use_retained_program_state">use_retained_program_state</a> is enabled), you'll have to use the appropriate <a href="extcommands.html">external command</a> or change it via the web interface. Values are as follows:
</p>
<p>
<ul>
<li>0 = Don't execute host checks
<li>1 = Execute host checks (default)
</ul>
</p>
<p>
<a name="accept_passive_host_checks"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Passive Host Check Acceptance Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>accept_passive_host_checks=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>accept_passive_host_checks=1</strong></font></td>
</tr>
</table>
</p>
<p>
This option determines whether or not Nagios will accept <a href="passivechecks.html">passive host checks</a> when it initially (re)starts. If this option is disabled, Nagios will not accept any passive host checks. Note: If you have <a href="#retain_state_information">state retention</a> enabled, Nagios will ignore this setting when it (re)starts and use the last known setting for this option (as stored in the <a href="#state_retention_file">state retention file</a>), <i>unless</i> you disable the <a href="#use_retained_program_state">use_retained_program_state</a> option. If you want to change this option when state retention is active (and the <a href="#use_retained_program_state">use_retained_program_state</a> is enabled), you'll have to use the appropriate <a href="extcommands.html">external command</a> or change it via the web interface. Values are as follows:
</p>
<p>
<ul>
<li>0 = Don't accept passive host checks
<li>1 = Accept passive host checks (default)
</ul>
</p>
<p>
<a name="enable_event_handlers"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Event Handler Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>enable_event_handlers=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>enable_event_handlers=1</strong></font></td>
</tr>
</table>
</p>
<p>
This option determines whether or not Nagios will run <a href="eventhandlers.html">event handlers</a> when it initially (re)starts. If this option is disabled, Nagios will not run any host or service event handlers. Note: If you have <a href="#retain_state_information">state retention</a> enabled, Nagios will ignore this setting when it (re)starts and use the last known setting for this option (as stored in the <a href="#state_retention_file">state retention file</a>), <i>unless</i> you disable the <a href="#use_retained_program_state">use_retained_program_state</a> option. If you want to change this option when state retention is active (and the <a href="#use_retained_program_state">use_retained_program_state</a> is enabled), you'll have to use the appropriate <a href="extcommands.html">external command</a> or change it via the web interface. Values are as follows:
</p>
<p>
<ul>
<li>0 = Disable event handlers
<li>1 = Enable event handlers (default)
</ul>
</p>
<p>
<a name="log_rotation_method"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Log Rotation Method</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>log_rotation_method=<n/h/d/w/m></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>log_rotation_method=d</strong></font></td>
</tr>
</table>
</p>
<p>
This is the rotation method that you would like Nagios to use for your log file. Values are as follows:
</p>
<p>
<ul>
<li>n = None (don't rotate the log - this is the default)
<li>h = Hourly (rotate the log at the top of each hour)
<li>d = Daily (rotate the log at midnight each day)
<li>w = Weekly (rotate the log at midnight on Saturday)
<li>m = Monthly (rotate the log at midnight on the last day of the month)
</ul>
</p>
<p>
<a name="log_archive_path"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Log Archive Path</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>log_archive_path=<path></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>log_archive_path=/usr/local/nagios/var/archives/</strong></font></td>
</tr>
</table>
</p>
<p>
This is the directory where Nagios should place log files that have been rotated. This option is ignored if you choose to not use the <a href="#log_rotation_method">log rotation</a> functionality.
</p>
<p>
<a name="check_external_commands"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>External Command Check Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>check_external_commands=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>check_external_commands=1</strong></font></td>
</tr>
</table>
</p>
<p>
This option determines whether or not Nagios will check the <a href="#command_file">command file</a> for commands that should be executed. This option must be enabled if you plan on using the <a href="cgis.html#command_cgi">command CGI</a> to issue commands via the web interface. Third party programs can also issue commands to Nagios by writing to the command file, provided proper rights to the file have been granted as outlined in <a href="faqs.html#command_file_permissions">this FAQ</a>. More information on external commands can be found <a href="extcommands.html">here</a>.
</p>
<p>
<ul>
<li>0 = Don't check external commands (default)
<li>1 = Check external commands
</ul>
</p>
<p>
<a name="command_check_interval"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>External Command Check Interval</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>command_check_interval=<xxx>[s]</strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>command_check_interval=1</strong></font></td>
</tr>
</table>
</p>
<p>
If you specify a number with an "s" appended to it (i.e. 30s), this is the number of <i>seconds</i> to wait between external command checks. If you leave off the "s", this is the number of "time units" to wait between external command checks. Unless you've changed the <a href="#interval_length">interval_length</a> value (as defined below) from the default value of 60, this number will mean minutes.
</p>
<p>
Note: By setting this value to <b>-1</b>, Nagios will check for external commands as often as possible. Each time Nagios checks for external commands it will read and process all commands present in the <a href="#command_file">command file</a> before continuing on with its other duties. More information on external commands can be found <a href="extcommands.html">here</a>.
</p>
<p>
<a name="command_file"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>External Command File</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>command_file=<file_name></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>command_file=/usr/local/nagios/var/rw/nagios.cmd</strong></font></td>
</tr>
</table>
</p>
<p>
This is the file that Nagios will check for external commands to process. The <a href="cgis.html#cmd_cgi">command CGI</a> writes commands to this file. Other third party programs can write to this file if proper file permissions have been granted as outline in <a href="commandfile.html">here</a>. The external command file is implemented as a named pipe (FIFO), which is created when Nagios starts and removed when it shuts down. If the file exists when Nagios starts, the Nagios process will terminate with an error message. More information on external commands can be found <a href="extcommands.html">here</a>.
</p>
<p>
<a name="downtime_file"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Downtime File</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>downtime_file=<file_name></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>downtime_file=/usr/local/nagios/var/downtime.dat</strong></font></td>
</tr>
</table>
</p>
<p>
This is the file that Nagios will use for storing scheduled host and service <a href="downtime.html">downtime</a> information. Comments can be viewed and added for both hosts and services through the <a href="cgis.html#extinfo_cgi">extended information CGI</a>.
</p>
<p>
<a name="comment_file"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Comment File</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>comment_file=<file_name></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>comment_file=/usr/local/nagios/var/comment.dat</strong></font></td>
</tr>
</table>
</p>
<p>
This is the file that Nagios will use for storing service and host comments. Comments can be viewed and added for both hosts and services through the <a href="cgis.html#extinfo_cgi">extended information CGI</a>.
</p>
<p>
<a name="lock_file"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Lock File</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>lock_file=<file_name></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>lock_file=/tmp/nagios.lock</strong></font></td>
</tr>
</table>
</p>
<p>
This option specifies the location of the lock file that Nagios should create when it runs as a daemon (when started with the -d command line argument). This file contains the process id (PID) number of the running Nagios process.
</p>
<p>
<a name="retain_state_information"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>State Retention Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>retain_state_information=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>retain_state_information=1</strong></font></td>
</tr>
</table>
</p>
<p>
This option determines whether or not Nagios will retain state information for hosts and services between program restarts. If you enable this option, you should supply a value for the <a href="#state_retention_file">state_retention_file</a> variable. When enabled, Nagios will save all state information for hosts and service before it shuts down (or restarts) and will read in previously saved state information when it starts up again.
</p>
<p>
<ul>
<li>0 = Don't retain state information
<li>1 = Retain state information (default)
</ul>
</p>
<p>
<a name="state_retention_file"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>State Retention File</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>state_retention_file=<file_name></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>state_retention_file=/usr/local/nagios/var/retention.dat</strong></font></td>
</tr>
</table>
</p>
<p>
This is the file that Nagios will use for storing service and host state information before it shuts down. When Nagios is restarted it will use the information stored in this file for setting the initial states of services and hosts before it starts monitoring anything. This file is deleted after Nagios reads in initial state information when it (re)starts. In order to make Nagios retain state information between program restarts, you must enable the <a href="#retain_state_information">retain_state_information</a> option.
</p>
<p>
<a name="retention_update_interval"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Automatic State Retention Update Interval</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>retention_update_interval=<minutes></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>retention_update_interval=60</strong></font></td>
</tr>
</table>
</p>
<p>
This setting determines how often (in minutes) that Nagios will automatically save retention data during normal operation. If you set this value to 0, Nagios will not save retention data at regular intervals, but it will still save retention data before shutting down or restarting. If you have disabled state retention (with the <a href="#retain_state_information">retain_state_information</a> option), this option has no effect.
</p>
<p>
<a name="use_retained_program_state"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Use Retained Program State Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>use_retained_program_state=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>use_retained_program_state=1</strong></font></td>
</tr>
</table>
</p>
<p>
This setting determines whether or not Nagios will set various program-wide state variables based on the values saved in the retention file. Some of these program-wide state variables that are normally saved across program restarts if state retention is enabled include the <a href="#enable_notifications">enable_notifications</a>, <a href="#enable_flap_detection">enable_flap_detection</a>, <a href="#enable_event_handlers">enable_event_handlers</a>, <a href="#execute_service_checks">execute_service_checks</a>, and <a href="#accept_passive_service_checks">accept_passive_service_checks</a> options. If you do not have <a href="#retain_state_information">state retention</a> enabled, this option has no effect.
</p>
<p>
<ul>
<li>0 = Don't use retained program state
<li>1 = Use retained program state (default)
</ul>
</p>
<p>
<a name="use_retained_scheduling_info"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Use Retained Scheduling Info Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>use_retained_scheduling_info=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>use_retained_scheduling_info=1</strong></font></td>
</tr>
</table>
</p>
<p>
This setting determines whether or not Nagios will retain scheduling info (next check times) for hosts and services when it restarts. If you are adding a large number (or percentage) of hosts and services, I would recommend disabling this option when you first restart Nagios, as it can adversely skew the spread of initial checks. Otherwise you will probably want to leave it enabled.
</p>
<p>
<ul>
<li>0 = Don't use retained scheduling info
<li>1 = Use retained scheduling info (default)
</ul>
</p>
<p>
<a name="use_syslog"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Syslog Logging Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>use_syslog=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>use_syslog=1</strong></font></td>
</tr>
</table>
</p>
<p>
This variable determines whether messages are logged to the syslog facility on your local host. Values
are as follows:
</p>
<p>
<ul>
<li>0 = Don't use syslog facility
<li>1 = Use syslog facility
</ul>
</p>
<p>
<a name="log_notifications"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Notification Logging Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>log_notifications=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>log_notifications=1</strong></font></td>
</tr>
</table>
</p>
<p>
This variable determines whether or not notification messages are logged. If you have a lot of contacts
or regular service failures your log file will grow relatively quickly. Use this option to keep contact
notifications from being logged.
</p>
<p>
<ul>
<li>0 = Don't log notifications
<li>1 = Log notifications
</ul>
</p>
<p>
<a name="log_service_retries"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Service Check Retry Logging Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>log_service_retries=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>log_service_retries=1</strong></font></td>
</tr>
</table>
</p>
<p>
This variable determines whether or not service check retries are logged. Service check retries occur when a
service check results in a non-OK state, but you have configured Nagios to retry the service more than once before
responding to the error. Services in this situation are considered to be in "soft" states. Logging service check retries
is mostly useful when attempting to debug Nagios or test out service <a href="eventhandlers.html">event handlers</a>.
</p>
<p>
<ul>
<li>0 = Don't log service check retries
<li>1 = Log service check retries
</ul>
</p>
<p>
<a name="log_host_retries"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Host Check Retry Logging Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>log_host_retries=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>log_host_retries=1</strong></font></td>
</tr>
</table>
</p>
<p>
This variable determines whether or not host check retries are logged. Logging host check retries
is mostly useful when attempting to debug Nagios or test out host <a href="eventhandlers.html">event handlers</a>.
</p>
<p>
<ul>
<li>0 = Don't log host check retries
<li>1 = Log host check retries
</ul>
</p>
<p>
<a name="log_event_handlers"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Event Handler Logging Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>log_event_handlers=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>log_event_handlers=1</strong></font></td>
</tr>
</table>
</p>
<p>
This variable determines whether or not service and host <a href="eventhandlers.html">event handlers</a> are logged.
Event handlers are optional commands that can be run whenever a service or hosts changes state. Logging event handlers
is most useful when debugging Nagios or first trying out your event handler scripts.
</p>
<p>
<ul>
<li>0 = Don't log event handlers
<li>1 = Log event handlers
</ul>
</p>
<p>
<a name="log_initial_states"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Initial States Logging Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>log_initial_states=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>log_initial_states=1</strong></font></td>
</tr>
</table>
</p>
<p>
This variable determines whether or not Nagios will force all initial host and service states to be logged, even if they result in an OK state. Initial service and host states are normally only logged when there is a problem on the first check. Enabling this option is useful if you are using an application that scans the log file to determine long-term state statistics for services and hosts.
</p>
<p>
<ul>
<li>0 = Don't log initial states (default)
<li>1 = Log initial states
</ul>
</p>
<p>
<a name="log_external_commands"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>External Command Logging Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>log_external_commands=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>log_external_commands=1</strong></font></td>
</tr>
</table>
</p>
<p>
This variable determines whether or not Nagios will log <a href="extcommands.html">external commands</a> that it receives from the <a href="#command_file">external command file</a>. Note: This option does not control whether or not <a href="passivechecks.html">passive service checks</a> (which are a type of external command) get logged. To enable or disable logging of passive checks, use the <a href="#log_passive_service_checks">log_passive_service_checks</a> option.
</p>
<p>
<ul>
<li>0 = Don't log external commands
<li>1 = Log external commands (default)
</ul>
</p>
<p>
<a name="log_passive_checks"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Passive Check Logging Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>log_passive_checks=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>log_passive_checks=1</strong></font></td>
</tr>
</table>
</p>
<p>
This variable determines whether or not Nagios will log <a href="passivechecks.html">passive host and service checks</a> that it receives from the <a href="#command_file">external command file</a>. If you are setting up a <a href="distributed.html">distributed monitoring environment</a> or plan on handling a large number of passive checks on a regular basis, you may wish to disable this option so your log file doesn't get too large.
</p>
<p>
<ul>
<li>0 = Don't log passive checks
<li>1 = Log passive checks (default)
</ul>
</p>
<p>
<a name="global_host_event_handler"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Global Host Event Handler Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>global_host_event_handler=<command></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>global_host_event_handler=log-host-event-to-db</strong></font></td>
</tr>
</table>
</p>
<p>
This option allows you to specify a host event handler command that is to be run for every host state change. The global event handler is executed immediately prior to the event handler that you have optionally specified in each host definition. The <i>command</i> argument is the short name of a command that you define in your <a href="configobject.html">object configuration file</a>. The maximum amount of time that this command can run is controlled by the <a href="#event_handler_timeout">event_handler_timeout</a> option. More information on event handlers can be found <a href="eventhandlers.html">here</a>.
</p>
<p>
<a name="global_service_event_handler"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Global Service Event Handler Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>global_service_event_handler=<command></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>global_service_event_handler=log-service-event-to-db</strong></font></td>
</tr>
</table>
</p>
<p>
This option allows you to specify a service event handler command that is to be run for every service state change. The global event handler is executed immediately prior to the event handler that you have optionally specified in each service definition. The <i>command</i> argument is the short name of a command that you define in your <a href="configobject.html">object configuration file</a>. The maximum amount of time that this command can run is controlled by the <a href="#event_handler_timeout">event_handler_timeout</a> option. More information on event handlers can be found <a href="eventhandlers.html">here</a>.
</p>
<p>
<a name="sleep_time"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Inter-Check Sleep Time</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>sleep_time=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>sleep_time=1</strong></font></td>
</tr>
</table>
</p>
This is the number of seconds that Nagios will sleep before checking to see if the next service or host check in the scheduling queue should be executed. Note that Nagios will only sleep after it "catches up" with queued service checks that have fallen behind.
</p>
<p>
<a name="service_inter_check_delay_method"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Service Inter-Check Delay Method</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>service_inter_check_delay_method=<n/d/s/x.xx></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>service_inter_check_delay_method=s</strong></font></td>
</tr>
</table>
</p>
This option allows you to control how service checks are initially "spread out" in the event queue. Using a "smart" delay calculation (the default) will cause Nagios to calculate an average check interval and spread initial checks of all services out over that interval, thereby helping to eliminate CPU load spikes. Using no delay is generally <i>not</i> recommended unless you are testing the <a href="parallelization.html">service check parallelization</a> functionality. Using no delay will cause all service checks to be scheduled for execution at the same time. This means that you will generally have large CPU spikes when the services are all executed in parallel. More information on how to estimate how the inter-check delay affects service check scheduling can be found <a href="checkscheduling.html#service_inter_check_delay">here</a>. Values are as follows:
</p>
<p>
<ul>
<li>n = Don't use any delay - schedule all service checks to run immediately (i.e. at the same time!)
<li>d = Use a "dumb" delay of 1 second between service checks
<li>s = Use a "smart" delay calculation to spread service checks out evenly (default)
<li>x.xx = Use a user-supplied inter-check delay of x.xx seconds
</ul>
</p>
<p>
<a name="max_service_check_spread"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Maximum Service Check Spread</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>max_service_check_spread=<minutes></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>max_service_check_spread=30</strong></font></td>
</tr>
</table>
</p>
This option determines the maximum number of minutes from when Nagios starts that all services (that are scheduled to be regularly checked) are checked. This option will automatically adjust the <a href="#service_inter_check_delay">service inter-check delay</a> (if necessary) to ensure that the initial checks of all services occur within the timeframe you specify. In general, this option will not have an affect on service check scheduling if scheduling information is being retained using the <a href="#use_retained_scheduling_info">use_retained_scheduling_info</a> option. Default value is <b>30</b> (minutes).
</p>
<p>
<a name="service_interleave_factor"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Service Interleave Factor</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>service_interleave_factor=<s|<i>x</i>></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>service_interleave_factor=s</strong></font></td>
</tr>
</table>
</p>
</p>
This variable determines how service checks are interleaved. Interleaving allows for a more even distribution of service checks, reduced load on <i>remote</i> hosts, and faster overall detection of host problems. With the introduction of service check <a href="parallelization.html">parallelization</a>, remote hosts could get bombarded with checks if interleaving was not implemented. This could cause the service checks to fail or return incorrect results if the remote host was overloaded with processing other service check requests. Setting this value to 1 is equivalent to not interleaving the service checks (this is how versions of Nagios previous to 0.0.5 worked). Set this value to <b>s</b> (smart) for automatic calculation of the interleave factor unless you have a specific reason to change it. The best way to understand how interleaving works is to watch the <a href="cgis.html#status_cgi">status CGI</a> (detailed view) when Nagios is just starting. You should see that the service check results are spread out as they begin to appear. More information on how interleaving works can be found <a href="checkscheduling.html#service_interleaving">here</a>.
<ul>
<li><i>x</i> = A number greater than or equal to 1 that specifies the interleave factor to use. An interleave factor of 1 is equivalent to not interleaving the service checks.
<li>s = Use a "smart" interleave factor calculation (default)
</ul>
</p>
<p>
<a name="max_concurrent_checks"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Maximum Concurrent Service Checks</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>max_concurrent_checks=<max_checks></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>max_concurrent_checks=20</strong></font></td>
</tr>
</table>
</p>
</p>
This option allows you to specify the maximum number of service checks that can be run in <a href="parallelization.html">parallel</a> at any given time. Specifying a value of 1 for this variable essentially prevents any service checks from being parallelized. Specifying a value of 0 (the default) does not place any restrictions on the number of concurrent checks. You'll have to modify this value based on the system resources you have available on the machine that runs Nagios, as it directly affects the maximum load that will be imposed on the system (processor utilization, memory, etc.). More information on how to estimate how many concurrent checks you should allow can be found <a href="checkscheduling.html#max_concurrent_checks">here</a>.
</p>
<p>
<a name="service_reaper_frequency"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Service Reaper Frequency</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>service_reaper_frequency=<frequency_in_seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>service_reaper_frequency=10</strong></font></td>
</tr>
</table>
</p>
This option allows you to control the frequency <i>in seconds</i> of service "reaper" events. "Reaper" events process the results from <a href="parallelization.html">parallelized service checks</a> that have finished executing. These events consitute the core of the monitoring logic in Nagios.
</p>
<p>
<a name="host_inter_check_delay_method"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Host Inter-Check Delay Method</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>host_inter_check_delay_method=<n/d/s/x.xx></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>host_inter_check_delay_method=s</strong></font></td>
</tr>
</table>
</p>
This option allows you to control how host checks <i>that are scheduled to be checked on a regular basis</i> are initially "spread out" in the event queue. Using a "smart" delay calculation (the default) will cause Nagios to calculate an average check interval and spread initial checks of all hosts out over that interval, thereby helping to eliminate CPU load spikes. Using no delay is generally <i>not</i> recommended. Using no delay will cause all host checks to be scheduled for execution at the same time. More information on how to estimate how the inter-check delay affects host check scheduling can be found <a href="checkscheduling.html#host_inter_check_delay">here</a>.Values are as follows:
</p>
<p>
<ul>
<li>n = Don't use any delay - schedule all host checks to run immediately (i.e. at the same time!)
<li>d = Use a "dumb" delay of 1 second between host checks
<li>s = Use a "smart" delay calculation to spread host checks out evenly (default)
<li>x.xx = Use a user-supplied inter-check delay of x.xx seconds
</ul>
</p>
<p>
<a name="max_host_check_spread"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Maximum Host Check Spread</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>max_host_check_spread=<minutes></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>max_host_check_spread=30</strong></font></td>
</tr>
</table>
</p>
This option determines the maximum number of minutes from when Nagios starts that all hosts (that are scheduled to be regularly checked) are checked. This option will automatically adjust the <a href="#host_inter_check_delay">host inter-check delay</a> (if necessary) to ensure that the initial checks of all hosts occur within the timeframe you specify. In general, this option will not have an affect on host check scheduling if scheduling information is being retained using the <a href="#use_retained_scheduling_info">use_retained_scheduling_info</a> option. Default value is <b>30</b> (minutes).
</p>
<p>
<a name="interval_length"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Timing Interval Length</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>interval_length=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>interval_length=60</strong></font></td>
</tr>
</table>
</p>
This is the number of seconds per "unit interval" used for timing in the scheduling queue, re-notifications, etc. "Units intervals" are used in the object configuration file to determine how often to run a service check, how often of re-notify a contact, etc.
</p>
<p>
<strong>Important:</strong> The default value for this is set to 60, which means that a "unit value" of 1 in the object configuration file will mean 60 seconds (1 minute). I have not really tested other values for this variable, so proceed at your own risk if you decide to do so!
</p>
<p>
<a name="auto_reschedule_checks"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Auto-Rescheduling Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>auto_reschedule_checks=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>auto_reschedule_checks=1</strong></font></td>
</tr>
</table>
</p>
This option determines whether or not Nagios will attempt to automatically reschedule active host and service checks to
"smooth" them out over time. This can help to balance the load on the monitoring server, as it will attempt to keep the time between consecutive checks consistent, at the expense of executing checks on a more rigid schedule.
</p>
<p>
<strong>WARNING:</strong> THIS IS AN EXPERIMENTAL FEATURE AND MAY BE REMOVED IN FUTURE VERSIONS. ENABLING THIS OPTION CAN DEGRADE PERFORMANCE - RATHER THAN INCREASE IT - IF USED IMPROPERLY!
</p>
<p>
<a name="auto_rescheduling_interval"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Auto-Rescheduling Interval</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>auto_rescheduling_interval=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>auto_rescheduling_interval=30</strong></font></td>
</tr>
</table>
</p>
This option determines how often (in seconds) Nagios will attempt to automatically reschedule checks. This option only has an effect if the <a href="#auto_reschedule_checks">auto_reschedule_checks</a> option is enabled. Default is 30 seconds.
</p>
<p>
<strong>WARNING:</strong> THIS IS AN EXPERIMENTAL FEATURE AND MAY BE REMOVED IN FUTURE VERSIONS. ENABLING THE AUTO-RESCHEDULING OPTION CAN DEGRADE PERFORMANCE - RATHER THAN INCREASE IT - IF USED IMPROPERLY!
</p>
<p>
<a name="auto_rescheduling_window"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Auto-Rescheduling Window</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>auto_rescheduling_window=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>auto_rescheduling_window=180</strong></font></td>
</tr>
</table>
</p>
This option determines the "window" of time (in seconds) that Nagios will look at when automatically rescheduling checks. Only host and service checks that occur in the next X seconds (determined by this variable) will be rescheduled. This option only has an effect if the <a href="#auto_reschedule_checks">auto_reschedule_checks</a> option is enabled. Default is 180 seconds (3 minutes).
</p>
<p>
<strong>WARNING:</strong> THIS IS AN EXPERIMENTAL FEATURE AND MAY BE REMOVED IN FUTURE VERSIONS. ENABLING THE AUTO-RESCHEDULING OPTION CAN DEGRADE PERFORMANCE - RATHER THAN INCREASE IT - IF USED IMPROPERLY!
</p>
<p>
<a name="use_agressive_host_checking"></a>
<a name="use_aggressive_host_checking"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Aggressive Host Checking Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>use_aggressive_host_checking=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>use_aggressive_host_checking=0</strong></font></td>
</tr>
</table>
</p>
Nagios tries to be smart about how and when it checks the status of hosts. In general, disabling this option will allow Nagios to make some smarter decisions and check hosts a bit faster. Enabling this option will increase the amount of time required to check hosts, but may improve reliability a bit. Unless you have problems with Nagios not recognizing that a host recovered, I would suggest <b>not</b> enabling this option.
</p>
<p>
<ul>
<li>0 = Don't use aggressive host checking (default)
<li>1 = Use aggressive host checking
</ul>
</p>
<p>
<a name="enable_flap_detection"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Flap Detection Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>enable_flap_detection=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>enable_flap_detection=0</strong></font></td>
</tr>
</table>
</p>
This option determines whether or not Nagios will try and detect hosts and services that are "flapping". Flapping occurs when a host or service changes between states too frequently, resulting in a barrage of notifications being sent out. When Nagios detects that a host or service is flapping, it will temporarily suppress notifications for that host/service until it stops flapping. Flap detection is very experimental at this point, so use this feature with caution! More information on how flap detection and handling works can be found <a href="flapping.html">here</a>. Note: If you have <a href="#retain_state_information">state retention</a> enabled, Nagios will ignore this setting when it (re)starts and use the last known setting for this option (as stored in the <a href="#state_retention_file">state retention file</a>), <i>unless</i> you disable the <a href="#use_retained_program_state">use_retained_program_state</a> option. If you want to change this option when state retention is active (and the <a href="#use_retained_program_state">use_retained_program_state</a> is enabled), you'll have to use the appropriate <a href="extcommands.html">external command</a> or change it via the web interface.
</p>
<p>
<ul>
<li>0 = Don't enable flap detection (default)
<li>1 = Enable flap detection
</ul>
</p>
<p>
<a name="low_service_flap_threshold"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Low Service Flap Threshold</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>low_service_flap_threshold=<percent></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>low_service_flap_threshold=25.0</strong></font></td>
</tr>
</table>
</p>
This option is used to set the low threshold for detection of service flapping. For more information on how flap detection and handling works (and how this option affects things) read <a href="flapping.html">this</a>.
</p>
<p>
<a name="high_service_flap_threshold"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>High Service Flap Threshold</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>high_service_flap_threshold=<percent></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>high_service_flap_threshold=50.0</strong></font></td>
</tr>
</table>
</p>
This option is used to set the low threshold for detection of service flapping. For more information on how flap detection and handling works (and how this option affects things) read <a href="flapping.html">this</a>.
</p>
<p>
<a name="low_host_flap_threshold"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Low Host Flap Threshold</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>low_host_flap_threshold=<percent></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>low_host_flap_threshold=25.0</strong></font></td>
</tr>
</table>
</p>
This option is used to set the low threshold for detection of host flapping. For more information on how flap detection and handling works (and how this option affects things) read <a href="flapping.html">this</a>.
</p>
<p>
<a name="high_host_flap_threshold"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>High Host Flap Threshold</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>high_host_flap_threshold=<percent></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>high_host_flap_threshold=50.0</strong></font></td>
</tr>
</table>
</p>
This option is used to set the low threshold for detection of host flapping. For more information on how flap detection and handling works (and how this option affects things) read <a href="flapping.html">this</a>.
</p>
<p>
<a name="soft_service_dependencies"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Soft Service Dependencies Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>soft_state_dependencies=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>soft_state_dependencies=0</strong></font></td>
</tr>
</table>
</p>
This option determines whether or not Nagios will use soft service state information when checking <a href="dependencies.html">service dependencies</a>. Normally Nagios will only use the latest hard service state when checking dependencies. If you want it to use the latest state (regardless of whether its a soft or hard <a href="statetypes.html">state type</a>), enable this option.
</p>
<p>
<ul>
<li>0 = Don't use soft service state dependencies (default)
<li>1 = Use soft service state dependencies
</ul>
</p>
<p>
<a name="service_check_timeout"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Service Check Timeout</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>service_check_timeout=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>service_check_timeout=60</strong></font></td>
</tr>
</table>
</p>
This is the maximum number of seconds that Nagios will allow service checks to run. If checks exceed this limit, they are killed and a CRITICAL state is returned. A timeout error will also be logged.
</p>
<p>
There is often widespread confusion as to what this option really does. It is meant to be used as a last ditch mechanism to kill off plugins which are misbehaving and not exiting in a timely manner. It should be set to something high (like 60 seconds or more), so that each service check normally finishes executing within this time limit. If a service check runs longer than this limit, Nagios will kill it off thinking it is a runaway processes.
</p>
<p>
<a name="host_check_timeout"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Host Check Timeout</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>host_check_timeout=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>host_check_timeout=60</strong></font></td>
</tr>
</table>
</p>
This is the maximum number of seconds that Nagios will allow host checks to run. If checks exceed this limit, they are killed and a CRITICAL state is returned and the host will be assumed to be DOWN. A timeout error will also be logged.
</p>
<p>
There is often widespread confusion as to what this option really does. It is meant to be used as a last ditch mechanism to kill off plugins which are misbehaving and not exiting in a timely manner. It should be set to something high (like 60 seconds or more), so that each host check normally finishes executing within this time limit. If a host check runs longer than this limit, Nagios will kill it off thinking it is a runaway processes.
</p>
<p>
<a name="event_handler_timeout"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Event Handler Timeout</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>event_handler_timeout=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>event_handler_timeout=60</strong></font></td>
</tr>
</table>
</p>
This is the maximum number of seconds that Nagios will allow <a href="eventhandlers.html">event handlers</a> to be run. If an event handler exceeds this time limit it will be killed and a warning will be logged.
</p>
<p>
There is often widespread confusion as to what this option really does. It is meant to be used as a last ditch mechanism to kill off commands which are misbehaving and not exiting in a timely manner. It should be set to something high (like 60 seconds or more), so that each event handler command normally finishes executing within this time limit. If an event handler runs longer than this limit, Nagios will kill it off thinking it is a runaway processes.
</p>
<p>
<a name="notification_timeout"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Notification Timeout</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>notification_timeout=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>notification_timeout=60</strong></font></td>
</tr>
</table>
</p>
This is the maximum number of seconds that Nagios will allow notification commands to be run. If a notification command exceeds this time limit it will be killed and a warning will be logged.
</p>
<p>
There is often widespread confusion as to what this option really does. It is meant to be used as a last ditch mechanism to kill off commands which are misbehaving and not exiting in a timely manner. It should be set to something high (like 60 seconds or more), so that each notification command finishes executing within this time limit. If a notification command runs longer than this limit, Nagios will kill it off thinking it is a runaway processes.
</p>
<p>
<a name="ocsp_timeout"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Obsessive Compulsive Service Processor Timeout</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>ocsp_timeout=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>ocsp_timeout=5</strong></font></td>
</tr>
</table>
</p>
This is the maximum number of seconds that Nagios will allow an <a href="#ocsp_command">obsessive compulsive service processor command</a> to be run. If a command exceeds this time limit it will be killed and a warning will be logged.
</p>
<p>
<a name="ochp_timeout"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Obsessive Compulsive Host Processor Timeout</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>ochp_timeout=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>ochp_timeout=5</strong></font></td>
</tr>
</table>
</p>
This is the maximum number of seconds that Nagios will allow an <a href="#ochp_command">obsessive compulsive host processor command</a> to be run. If a command exceeds this time limit it will be killed and a warning will be logged.
</p>
<p>
<a name="perfdata_timeout"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Performance Data Processor Command Timeout</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>perfdata_timeout=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>perfdata_timeout=5</strong></font></td>
</tr>
</table>
</p>
This is the maximum number of seconds that Nagios will allow a <a href="#host_perfdata_command">host performance data processor command</a> or <a href="#service_perfdata_command">service performance data processor command</a> to be run. If a command exceeds this time limit it will be killed and a warning will be logged.
</p>
<p>
<a name="obsess_over_services"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Obsess Over Services Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>obsess_over_services=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>obsess_over_services=1</strong></font></td>
</tr>
</table>
</p>
This value determines whether or not Nagios will "obsess" over service checks results and run the <a href="#ocsp_command">obsessive compulsive service processor command</a> you define. I know - funny name, but it was all I could think of. This option is useful for performing <a href="distributed.html">distributed monitoring</a>. If you're not doing distributed monitoring, don't enable this option.
</p>
<p>
<ul>
<li>0 = Don't obsess over services (default)
<li>1 = Obsess over services
</ul>
</p>
<p>
<a name="ocsp_command"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Obsessive Compulsive Service Processor Command</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>ocsp_command=<command></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>ocsp_command=obsessive_service_handler</strong></font></td>
</tr>
</table>
</p>
<p>
This option allows you to specify a command to be run after <i>every</i> service check, which can be useful in <a href="distributed.html">distributed monitoring</a>. This command is executed after any <a href="eventhandlers.html">event handler</a> or <a href="notifications.html">notification</a> commands. The <i>command</i> argument is the short name of a <a href="configobject.html#command">command definition</a> that you define in your object configuration file. The maximum amount of time that this command can run is controlled by the <a href="#ocsp_timeout">ocsp_timeout</a> option. More information on distributed monitoring can be found <a href="distributed.html">here</a>. This command is only executed if the <a href="#obsess_over_services">obsess_over_services</a> option is enabled globally and if the <i>obsess_over_service</i> directive in the <a href="xodtemplate.html#service">service definition</a> is enabled.
</p>
<p>
<a name="obsess_over_hosts"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Obsess Over Hosts Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>obsess_over_hosts=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>obsess_over_hosts=1</strong></font></td>
</tr>
</table>
</p>
This value determines whether or not Nagios will "obsess" over host checks results and run the <a href="#ochp_command">obsessive compulsive host processor command</a> you define. I know - funny name, but it was all I could think of. This option is useful for performing <a href="distributed.html">distributed monitoring</a>. If you're not doing distributed monitoring, don't enable this option.
</p>
<p>
<ul>
<li>0 = Don't obsess over hosts (default)
<li>1 = Obsess over hosts
</ul>
</p>
<p>
<a name="ochp_command"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Obsessive Compulsive Host Processor Command</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>ochp_command=<command></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>ochp_command=obsessive_host_handler</strong></font></td>
</tr>
</table>
</p>
<p>
This option allows you to specify a command to be run after <i>every</i> host check, which can be useful in <a href="distributed.html">distributed monitoring</a>. This command is executed after any <a href="eventhandlers.html">event handler</a> or <a href="notifications.html">notification</a> commands. The <i>command</i> argument is the short name of a <a href="xodtemplate.html#command">command definition</a> that you define in your object configuration file. The maximum amount of time that this command can run is controlled by the <a href="#ochp_timeout">ochp_timeout</a> option. More information on distributed monitoring can be found <a href="distributed.html">here</a>. This command is only executed if the <a href="#obsess_over_hosts">obsess_over_hosts</a> option is enabled globally and if the <i>obsess_over_host</i> directive in the <a href="xodtemplate.html#host">host definition</a> is enabled.
</p>
<p>
<a name="process_performance_data"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Performance Data Processing Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>process_performance_data=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>process_performance_data=1</strong></font></td>
</tr>
</table>
</p>
This value determines whether or not Nagios will process host and service check <a href="perfdata.html">performance data</a>.
</p>
<p>
<ul>
<li>0 = Don't process performance data (default)
<li>1 = Process performance data
</ul>
</p>
<p>
<a name="host_perfdata_command"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Host Performance Data Processing Command</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>host_perfdata_command=<command></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>host_perfdata_command=process-host-perfdata</strong></font></td>
</tr>
</table>
</p>
This option allows you to specify a command to be run after <i>every</i> host check to process host <a href="perfdata.html">performance data</a> that may be returned from the check. The <i>command</i> argument is the short name of a <a href="xodtemplate.html#command">command definition</a> that you define in your object configuration file. This command is only executed if the <a href="#process_performance_data">process_performance_data</a> option is enabled globally and if the <i>process_perf_data</i> directive in the <a href="xodtemplate.html#host">host definition</a> is enabled.
</p>
<p>
<a name="service_perfdata_command"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Service Performance Data Processing Command</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>service_perfdata_command=<command></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>service_perfdata_command=process-service-perfdata</strong></font></td>
</tr>
</table>
</p>
This option allows you to specify a command to be run after <i>every</i> service check to process service <a href="perdata.html">performance data</a> that may be returned from the check. The <i>command</i> argument is the short name of a <a href="xodtemplate.html#command">command definition</a> that you define in your object configuration file. This command is only executed if the <a href="#process_performance_data">process_performance_data</a> option is enabled globally and if the <i>process_perf_data</i> directive in the <a href="xodtemplate.html#service">service definition</a> is enabled.
</p>
<p>
<a name="host_perfdata_file"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Host Performance Data File</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>host_perfdata_file=<file_name></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>host_perfdata_file=/usr/local/nagios/var/host-perfdata.dat</strong></font></td>
</tr>
</table>
</p>
This option allows you to specify a file to which host <a href="perdata.html">performance data</a> will be written after every host check. Data will be written to the performance file as specified by the <a href="#host_perfdata_file_template">host_perfdata_file_template</a> option. Performance data is only written to this file if the <a href="#process_performance_data">process_performance_data</a> option is enabled globally and if the <i>process_perf_data</i> directive in the <a href="xodtemplate.html#host">host definition</a> is enabled.
</p>
<p>
<a name="service_perfdata_file"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Service Performance Data File</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>service_perfdata_file=<file_name></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>service_perfdata_file=/usr/local/nagios/var/service-perfdata.dat</strong></font></td>
</tr>
</table>
</p>
This option allows you to specify a file to which service <a href="perdata.html">performance data</a> will be written after every service check. Data will be written to the performance file as specified by the <a href="#service_perfdata_file_template">service_perfdata_file_template</a> option. Performance data is only written to this file if the <a href="#process_performance_data">process_performance_data</a> option is enabled globally and if the <i>process_perf_data</i> directive in the <a href="xodtemplate.html#service">service definition</a> is enabled.
</p>
<p>
<a name="host_perfdata_file_template"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Host Performance Data File Template</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>host_perfdata_file_template=<template></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$</strong></font></td>
</tr>
</table>
</p>
This option determines what (and how) data is written to the <a href="#host_perfdata_file">host performance data file</a>. The template may contain <a href="macros.html">macros</a>, special characters (\t for tab, \r for carriage return, \n for newline) and plain text. A newline is automatically added after each write to the performance data file.
</p>
<p>
<a name="service_perfdata_file_template"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Service Performance Data File Template</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>service_perfdata_file_template=<template></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$</strong></font></td>
</tr>
</table>
</p>
This option determines what (and how) data is written to the <a href="#service_perfdata_file">service performance data file</a>. The template may contain <a href="macros.html">macros</a>, special characters (\t for tab, \r for carriage return, \n for newline) and plain text. A newline is automatically added after each write to the performance data file.
</p>
<p>
<a name="host_perfdata_file_mode"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Host Performance Data File Mode</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>host_perfdata_file_mode=<mode></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>host_perfdata_file_mode=a</strong></font></td>
</tr>
</table>
</p>
This option determines whether the <a href="#host_perfdata_file">host performance data file</a> is opened in write or append mode. Unless the file is a named pipe, you will probably want to use the default mode of append.
</p>
<p>
<ul>
<li>a = Open file in append mode (default)
<li>w = Open file in write mode
</ul>
</p>
<p>
<a name="service_perfdata_file_mode"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Service Performance Data File Mode</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>service_perfdata_file_mode=<mode></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>service_perfdata_file_mode=a</strong></font></td>
</tr>
</table>
</p>
This option determines whether the <a href="#service_perfdata_file">service performance data file</a> is opened in write or append mode. Unless the file is a named pipe, you will probably want to use the default mode of append.
</p>
<p>
<ul>
<li>a = Open file in append mode (default)
<li>w = Open file in write mode
</ul>
</p>
<p>
<a name="host_perfdata_file_processing_interval"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Host Performance Data File Processing Interval</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>host_perfdata_file_processing_interval=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>host_perfdata_file_processing_interval=0</strong></font></td>
</tr>
</table>
</p>
This option allows you to specify the interval (in seconds) at which the <a href="#host_perfdata_file">host performance data file</a> is processed using the <a href="#host_perfdata_file_processing_command">host performance data file processing command</a>. A value of 0 indicates that the performance data file should not be processed at regular intervals.
</p>
<p>
<a name="service_perfdata_file_processing_interval"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Service Performance Data File Processing Interval</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>service_perfdata_file_processing_interval=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>service_perfdata_file_processing_interval=0</strong></font></td>
</tr>
</table>
</p>
This option allows you to specify the interval (in seconds) at which the <a href="#service_perfdata_file">service performance data file</a> is processed using the <a href="#service_perfdata_file_processing_command">service performance data file processing command</a>. A value of 0 indicates that the performance data file should not be processed at regular intervals.
</p>
<p>
<a name="host_perfdata_file_processing_command"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Host Performance Data File Processing Command</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>host_perfdata_file_processing_command=<command></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>host_perfdata_file_processing_command=process-host-perfdata-file</strong></font></td>
</tr>
</table>
</p>
This option allows you to specify the command that should be executed to process the <a href="#host_perfdata_file">host performance data file</a>. The <i>command</i> argument is the short name of a <a href="xodtemplate.html#command">command definition</a> that you define in your object configuration file. The interval at which this command is executed is determined by the <a href="#host_perfdata_file_processing_interval">host_perfdata_file_processing_interval</a> directive.
</p>
<p>
<a name="service_perfdata_file_processing_command"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Service Performance Data File Processing Command</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>service_perfdata_file_processing_command=<command></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>service_perfdata_file_processing_command=process-service-perfdata-file</strong></font></td>
</tr>
</table>
</p>
This option allows you to specify the command that should be executed to process the <a href="#service_perfdata_file">service performance data file</a>. The <i>command</i> argument is the short name of a <a href="xodtemplate.html#command">command definition</a> that you define in your object configuration file. The interval at which this command is executed is determined by the <a href="#service_perfdata_file_processing_interval">service_perfdata_file_processing_interval</a> directive.
</p>
<p>
<a name="check_for_orphaned_services"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Orphaned Service Check Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>check_for_orphaned_services=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>check_for_orphaned_services=1</strong></font></td>
</tr>
</table>
</p>
<p>
This option allows you to enable or disable checks for orphaned service checks. Orphaned service checks are checks which have been executed and have been removed from the event queue, but have not had any results reported in a long time. Since no results have come back in for the service, it is not rescheduled in the event queue. This can cause service checks to stop being executed. Normally it is very rare for this to happen - it might happen if an external user or process killed off the process that was being used to execute a service check. If this option is enabled and Nagios finds that results for a particular service check have not come back, it will log an error message and reschedule the service check. If you start seeing service checks that never seem to get rescheduled, enable this option and see if you notice any log messages about orphaned services.
</p>
<p>
<ul>
<li>0 = Don't check for orphaned service checks
<li>1 = Check for orphaned service checks (default)
</ul>
</p>
<p>
<a name="check_service_freshness"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Service Freshness Checking Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>check_service_freshness=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>check_service_freshness=0</strong></font></td>
</tr>
</table>
</p>
<p>
This option determines whether or not Nagios will periodically check the "freshness" of service checks. Enabling this option is useful for helping to ensure that <a href="passivechecks.html">passive service checks</a> are received in a timely manner. More information on freshness checking can be found <a href="freshness.html">here</a>.
</p>
<p>
<ul>
<li>0 = Don't check service freshness
<li>1 = Check service freshness (default)
</ul>
</p>
<p>
<a name="service_freshness_check_interval"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Service Freshness Check Interval</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>service_freshness_check_interval=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>service_freshness_check_interval=60</strong></font></td>
</tr>
</table>
</p>
<p>
This setting determines how often (in seconds) Nagios will periodically check the "freshness" of service check results. If you have disabled service freshness checking (with the <a href="#check_service_freshness">check_service_freshness<a> option), this option has no effect. More information on freshness checking can be found <a href="freshness.html">here</a>.
</p>
<p>
<a name="check_host_freshness"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Host Freshness Checking Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>check_host_freshness=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>check_host_freshness=0</strong></font></td>
</tr>
</table>
</p>
<p>
This option determines whether or not Nagios will periodically check the "freshness" of host checks. Enabling this option is useful for helping to ensure that <a href="passivechecks.html">passive host checks</a> are received in a timely manner. More information on freshness checking can be found <a href="freshness.html">here</a>.
</p>
<p>
<ul>
<li>0 = Don't check host freshness
<li>1 = Check host freshness (default)
</ul>
</p>
<p>
<a name="host_freshness_check_interval"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Host Freshness Check Interval</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>host_freshness_check_interval=<seconds></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>host_freshness_check_interval=60</strong></font></td>
</tr>
</table>
</p>
<p>
This setting determines how often (in seconds) Nagios will periodically check the "freshness" of host check results. If you have disabled host freshness checking (with the <a href="#check_h_freshostness">check_host_freshness<a> option), this option has no effect. More information on freshness checking can be found <a href="freshness.html">here</a>.
</p>
<p>
<a name="date_format"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Date Format</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>date_format=<option></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>date_format=us</strong></font></td>
</tr>
</table>
</p>
<p>
This option allows you to specify what kind of date/time format Nagios should use in the web interface and date/time <a href="macros.html">macros</a>. Possible options (along with example output) include:
</p>
<p>
<table border="1" class="Default">
<tr><th>Option</th><th>Output Format</th><th>Sample Output</th></tr>
<tr><td>us</td><td>MM/DD/YYYY HH:MM:SS</td><td>06/30/2002 03:15:00</td></tr>
<tr><td>euro</td><td>DD/MM/YYYY HH:MM:SS</td><td>30/06/2002 03:15:00</td></tr>
<tr><td>iso8601</td><td>YYYY-MM-DD HH:MM:SS</td><td>2002-06-30 03:15:00</td></tr>
<tr><td>strict-iso8601</td><td>YYYY-MM-DDTHH:MM:SS</td><td>2002-06-30T03:15:00</td></tr>
</table>
</p>
<p>
<a name="illegal_object_name_chars"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Illegal Object Name Characters</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>illegal_object_name_chars=<chars...></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>illegal_object_name_chars=`~!$%^&*"|'<>?,()=</strong></font></td>
</tr>
</table>
</p>
<p>
This option allows you to specify illegal characters that cannot be used in host names, service descriptions, or names of other object types. Nagios will allow you to use most characters in object definitions, but I recommend not using the characters shown in the example above. Doing may give you problems in the web interface, notification commands, etc.
</p>
<p>
<a name="illegal_macro_output_chars"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Illegal Macro Output Characters</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>illegal_macro_output_chars=<chars...></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>illegal_macro_output_chars=`~$^&"|'<></strong></font></td>
</tr>
</table>
</p>
<p>
This option allows you to specify illegal characters that should be stripped from <a href="macros.html">macros</a> before being used in notifications, event handlers, and other commands. This DOES NOT affect macros used in service or host check commands. You can choose to not strip out the characters shown in the example above, but I recommend you do not do this. Some of these characters are interpreted by the shell (i.e. the backtick) and can lead to security problems. The following macros are stripped of the characters you specify:
</p>
<p>
<b>$HOSTOUTPUT$</b>, <b>$HOSTPERFDATA$</b>, <b>$HOSTACKAUTHOR$</b>, <b>$HOSTACKCOMMENT$</b>, <b>$SERVICEOUTPUT$</b>, <b>$SERVICEPERFDATA$</b>, <b>$SERVICEACKAUTHOR$</b>, and <b>$SERVICEACKCOMMENT$</b>
</p>
<p>
<a name="use_regexp_matching"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Regular Expression Matching Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>use_regexp_matching=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>use_regexp_matching=0</strong></font></td>
</tr>
</table>
</p>
<p>
This option determines whether or not various directives in your <a href="configobject.html">object definitions</a> will be processed as regular expressions. More information on how this works can be found <a href="templatetricks.html">here</a>.
</p>
<p>
<ul>
<li>0 = Don't use regular expression matching (default)
<li>1 = Use regular expression matching
</ul>
</p>
<p>
<a name="use_true_regexp_matching"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>True Regular Expression Matching Option</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>use_true_regexp_matching=<0/1></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>use_true_regexp_matching=0</strong></font></td>
</tr>
</table>
</p>
<p>
If you've enabled regular expression matching of various object directives using the <a href="#use_regexp_matching">use_regexp_matching</a> option, this option will determine when object directives are treated as regular expressions. If this option is disabled (the default), directives will only be treated as regular expressions if the contain a <b>*</b> or <b>?</b> wildcard character. If this option is enabled, all appropriate directives will be treated as regular expression - be careful when enabling this! More information on how this works can be found <a href="templatetricks.html">here</a>.
</p>
<p>
<ul>
<li>0 = Don't use true regular expression matching (default)
<li>1 = Use true regular expression matching
</ul>
</p>
<p>
<a name="admin_email"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Administrator Email Address</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>admin_email=<email_address></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>admin_email=root@localhost.localdomain</strong></font></td>
</tr>
</table>
</p>
This is the email address for the administrator of the local machine (i.e. the one that Nagios is running on).
This value can be used in notification commands by using the <b>$ADMINEMAIL$</b> <a href="macros.html">macro</a>.
</p>
<p>
<a name="admin_pager"></a>
<table border="0" width="100%" class="Default">
<tr>
<td bgcolor="#cbcbcb"><strong>Administrator Pager</strong></td>
</tr>
</table>
</p>
<p>
<table border="0" class="Default">
<tr>
<td>Format:</td>
<td><strong>admin_pager=<pager_number_or_pager_email_gateway></strong></td>
</tr>
<tr>
<td>Example:</td>
<td><font color="red"><strong>admin_pager=pageroot@localhost.localdomain</strong></font></td>
</tr>
</table>
</p>
This is the pager number (or pager email gateway) for the administrator of the local machine (i.e. the one that Nagios is running on). The pager number/address can be used in notification commands by using the <b>$ADMINPAGER$</b> <a href="macros.html">macro</a>.
</p>
<hr>
</body>
</html>
|
