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
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4938
4939
4940
4941
4942
4943
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4955
4956
4957
4958
4959
4960
4961
4962
4963
4964
4965
4966
4967
4968
4969
4970
4971
4972
4973
4974
4975
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
4986
4987
4988
4989
4990
4991
4992
4993
4994
4995
4996
4997
4998
4999
5000
5001
5002
5003
5004
5005
5006
5007
5008
5009
5010
5011
5012
5013
5014
5015
5016
5017
5018
5019
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5033
5034
5035
5036
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047
5048
5049
5050
5051
5052
5053
5054
5055
5056
5057
5058
5059
5060
5061
5062
5063
5064
5065
5066
5067
5068
5069
5070
5071
5072
5073
5074
5075
5076
5077
5078
5079
5080
5081
5082
5083
5084
5085
5086
5087
5088
5089
5090
5091
5092
5093
5094
5095
5096
5097
5098
5099
5100
5101
5102
5103
5104
5105
5106
5107
5108
5109
5110
5111
5112
5113
5114
5115
5116
5117
5118
5119
5120
5121
5122
5123
5124
5125
5126
5127
5128
5129
5130
5131
5132
5133
5134
5135
5136
5137
5138
5139
5140
5141
5142
5143
5144
5145
5146
5147
5148
5149
5150
5151
5152
5153
5154
5155
5156
5157
5158
5159
5160
5161
5162
5163
5164
5165
5166
5167
5168
5169
5170
5171
5172
5173
5174
5175
5176
5177
5178
5179
5180
5181
5182
5183
5184
5185
5186
5187
5188
5189
5190
5191
5192
5193
5194
5195
5196
5197
5198
5199
5200
5201
5202
5203
5204
5205
5206
5207
5208
5209
5210
5211
5212
5213
5214
5215
5216
5217
5218
5219
5220
5221
5222
5223
5224
5225
5226
5227
5228
5229
5230
5231
5232
5233
5234
5235
5236
5237
5238
5239
5240
5241
5242
5243
5244
5245
5246
5247
5248
5249
5250
5251
5252
5253
5254
5255
5256
5257
5258
5259
5260
5261
5262
5263
5264
5265
5266
5267
5268
5269
5270
5271
5272
5273
5274
5275
5276
5277
5278
5279
5280
5281
5282
5283
5284
5285
5286
5287
5288
5289
5290
5291
5292
5293
5294
5295
5296
5297
5298
5299
5300
5301
5302
5303
5304
5305
5306
5307
5308
5309
5310
5311
5312
5313
5314
5315
5316
5317
5318
5319
5320
5321
5322
5323
5324
5325
5326
5327
5328
5329
5330
5331
5332
5333
5334
5335
5336
5337
5338
5339
5340
5341
5342
5343
5344
5345
5346
5347
5348
5349
5350
5351
5352
5353
5354
5355
5356
5357
5358
5359
5360
5361
5362
5363
5364
5365
5366
5367
5368
5369
5370
5371
5372
5373
5374
5375
5376
5377
5378
5379
5380
5381
5382
5383
5384
5385
5386
5387
5388
5389
5390
5391
5392
5393
5394
5395
5396
5397
5398
5399
5400
5401
5402
5403
5404
5405
5406
5407
5408
5409
5410
5411
5412
5413
5414
5415
5416
5417
5418
5419
5420
5421
5422
5423
5424
5425
5426
5427
5428
5429
5430
5431
5432
5433
5434
5435
5436
5437
5438
5439
5440
5441
5442
5443
5444
5445
5446
5447
5448
5449
5450
5451
5452
5453
5454
5455
5456
5457
5458
5459
5460
5461
5462
5463
5464
5465
5466
5467
5468
5469
5470
5471
5472
5473
5474
5475
5476
5477
5478
5479
5480
5481
5482
5483
5484
5485
5486
5487
5488
5489
5490
5491
5492
5493
5494
5495
5496
5497
5498
5499
5500
5501
5502
5503
5504
5505
5506
5507
5508
5509
5510
5511
5512
5513
5514
5515
5516
5517
5518
5519
5520
5521
5522
5523
5524
5525
5526
5527
5528
5529
5530
5531
5532
5533
5534
5535
5536
5537
5538
5539
5540
5541
5542
5543
5544
5545
5546
5547
5548
5549
5550
5551
5552
5553
5554
5555
5556
5557
5558
5559
5560
5561
5562
5563
5564
5565
5566
5567
5568
5569
5570
5571
5572
5573
5574
5575
5576
5577
5578
5579
5580
5581
5582
5583
5584
5585
5586
5587
5588
5589
5590
5591
5592
5593
5594
5595
5596
5597
5598
5599
5600
5601
5602
5603
5604
5605
5606
5607
5608
5609
5610
5611
5612
5613
5614
5615
5616
5617
5618
5619
5620
5621
5622
5623
5624
5625
5626
5627
5628
5629
5630
5631
5632
5633
5634
5635
5636
5637
5638
5639
5640
5641
5642
5643
5644
5645
5646
5647
5648
5649
5650
5651
5652
5653
5654
5655
5656
5657
5658
5659
5660
5661
5662
5663
5664
5665
5666
5667
5668
5669
5670
5671
5672
5673
5674
5675
5676
5677
5678
5679
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>3.2. Main Configuration File Options</title>
<link rel="stylesheet" href="../stylesheets/icinga-docs.css" type="text/css">
<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
<meta name="keywords" content="Supervision, Icinga, Nagios, Linux">
<link rel="home" href="index.html" title="Icinga Version 1.13 Documentation">
<link rel="up" href="ch03.html" title="Chapter 3. Configuring Icinga">
<link rel="prev" href="config.html" title="3.1. Configuration Overview">
<link rel="next" href="configobject.html" title="3.3. Object Configuration Overview">
<script src="../js/jquery-min.js" type="text/javascript"></script><script src="../js/icinga-docs.js" type="text/javascript"></script>
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<CENTER><IMG src="../images/logofullsize.png" border="0" alt="Icinga" title="Icinga"></CENTER>
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr><th colspan="3" align="center">3.2. Main Configuration File Options</th></tr>
<tr>
<td width="20%" align="left">
<a accesskey="p" href="config.html">Prev</a> </td>
<th width="60%" align="center">Chapter 3. Configuring Icinga</th>
<td width="20%" align="right"> <a accesskey="n" href="configobject.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
<div class="section" title="3.2. Main Configuration File Options">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="configmain"></a>3.2. <a name="config_main"></a>Main Configuration File Options</h2></div></div></div>
<p><span class="bold"><strong>Notes</strong></span></p>
<p>When creating and/or editing configuration files, keep the following in mind:</p>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
<p>Lines that start with a '#' character are taken to be comments and are not processed</p>
</li>
<li class="listitem">
<p>Variables names must begin at the start of the line - no white space is allowed before the name</p>
</li>
<li class="listitem">
<p>Variable names are case-sensitive</p>
</li>
</ol></div>
<p><span class="bold"><strong>Sample Configuration File</strong></span></p>
<div class="tip" title="Tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="../images/tip.png"></td>
<th align="left">Tip</th>
</tr>
<tr><td align="left" valign="top">
<p>A sample main configuration file (<span class="emphasis"><em>/usr/local/icinga/etc/icinga.cfg</em></span>) is installed for you when you follow the <a class="link" href="quickstart.html" title="2.3. Quickstart Installation Guides">quickstart installation guide</a>.</p>
</td></tr>
</table></div>
<p><span class="bold"><strong>Config File Location</strong></span></p>
<p>The main configuration file is usually named <span class="emphasis"><em>icinga.cfg</em></span> and located in the
<span class="emphasis"><em>/usr/local/icinga/etc/</em></span> directory.</p>
<p><span class="bold"><strong>Configuration File Variables</strong></span></p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-log_file">Log file</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-cfg_file">Object configuration file</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-cfg_dir">Object configuration directory</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-object_cache_file">Object cache file</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-precached_object_file">Precached object file</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-resource_file">Resource file</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-temp_file">Temp file</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-temp_path">Temp path</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-status_file">Status file</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-status_update_interval">Status file update interval</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-icinga_user">Icinga user</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-icinga_group">Icinga group</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-enable_notifications">Notifications option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-execute_service_checks">Service check execution option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-accept_passive_service_checks">Passive service check acceptance option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-execute_host_checks">Host check execution option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-accept_passive_host_checks">Passive host check acceptance option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-enable_event_handlers">Event handler option</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-log_rotation_method">Log rotation method</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-log_archive_path">Log archive path</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-use_daemon_log">Logging options for daemon</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-check_external_commands">External command check option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-command_check_interval">External command check interval</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-command_file">External command file</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-external_command_buffer_slots">External command buffer slots option</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
<p><a class="link" href="configmain.html#configmain-lock_file">Lock file</a></p>
</li></ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-retain_state_information">State retention option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-state_retention_file">State retention file</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-sync_retention_file">Sync retention file</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-retention_update_interval">Automatic state retention update interval</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-use_retained_program_state">Use retained program state option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-dump_retained_host_service_states_to_neb">Dump retained host service states to neb</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-use_retained_scheduling_info">Use retained scheduling info option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-retained_host_attribute_mask">Retained host/service attribute masks</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-retained_process_host_attribute_mask">Retained process attribute masks</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-retained_contact_host_attribute_mask">Retained contact attribute masks</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-use_syslog">Syslog logging option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-use_syslog_local_facility">Syslog local facility logging option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-syslog_local_facility">Syslog local facility logging value</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-log_notifications">Notification logging option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-log_service_retries">Service check retry logging option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-log_host_retries">Host retry logging option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-log_event_handlers">Event handler logging option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-log_initial_states">Initial state logging option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-log_external_commands">External command logging option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-log_external_commands_user">External commands user logging option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-log_passive_checks">Passive check logging option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-log_current_states">Current state logging option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-log_long_plugin_output">Long plugin output logging option</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-global_host_event_handler">Global host event handler</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-global_service_event_handler">Global service event handler</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-stalking_event_handlers_for_hosts">Stalking event handlers for hosts</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-stalking_event_handlers_for_services">Stalking event handlers for services</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-stalking_notifications_for_hosts">Notifications for stalked hosts</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-stalking_notifications_for_services">Notifications for stalked services</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-sleep_time">Inter-check sleep time</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-service_inter_check_delay_method">Service inter-check delay method</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-max_service_check_spread">Maximum service check spread</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-service_interleave_factor">Service interleave factor</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-max_concurrent_checks">Maximum concurrent service checks</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-check_result_reaper_frequency">Check result reaper frequency</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-max_check_result_reaper_time">Maximum check result reaper time</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-check_result_path">Check result path</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-max_check_result_file_age">Maximum check result file age</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-host_inter_check_delay_method">Host inter-check delay method</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-max_host_check_spread">Maximum host check spread</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-interval_length">Timing interval length</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-auto_reschedule_checks">Auto-rescheduling option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-auto_rescheduling_interval">Auto-rescheduling interval</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-auto_rescheduling_window">Auto-rescheduling window</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-use_aggressive_host_checking">Aggressive host checking option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-translate_passive_host_checks">Translate passive host checks option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-passive_host_checks_are_soft">Passive host checks are SOFT option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-enable_predictive_host_dependency_checks">Predictive host dependency checks option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-enable_predictive_service_dependency_checks">Predictive service dependency checks option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-cached_host_check_horizon">Cached host check horizon</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-cached_service_check_horizon">Cached service check horizon</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
<p><a class="link" href="configmain.html#configmain-use_large_installation_tweaks">Large installation tweaks option</a></p>
</li></ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-enable_flap_detection">Flap detection option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-low_service_flap_threshold">Low service flap threshold</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-high_service_flap_threshold">High service flap threshold</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-low_host_flap_threshold">Low host flap threshold</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-high_host_flap_threshold">High host flap threshold</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
<p><a class="link" href="configmain.html#configmain-soft_state_dependencies">Soft state dependencies option</a></p>
</li></ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
<p><a class="link" href="configmain.html#configmain-time_change_threshold">Time change threshold option</a></p>
</li></ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-service_check_timeout">Service check timeout</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-service_check_timeout_state">Service check timeout state</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-host_check_timeout">Host check timeout</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-event_handler_timeout">Event handler timeout</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-notification_timeout">Notification timeout</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-ocsp_timeout">Obsessive compulsive service processor timeout</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-ochp_timeout">Obsessive compulsive host processor timeout</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-perfdata_timeout">Performance data processor command timeout</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-obsess_over_services">Obsess over services option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-ocsp_command">Obsessive compulsive service processor command</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-obsess_over_hosts">Obsess over hosts option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-ochp_command">Obsessive compulsive host processor command</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-process_performance_data">Performance data processing option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-host_perfdata_command">Host performance data processing command</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-service_perfdata_command">Service performance data processing command</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-host_perfdata_file">Host performance data file</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-service_perfdata_file">Service performance data file</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-host_perfdata_file_template">Host performance data file template</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-service_perfdata_file_template">Service performance data file template</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-host_perfdata_file_mode">Host performance data file mode</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-service_perfdata_file_mode">Service performance data file mode</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-host_perfdata_file_processing_interval">Host performance data file processing interval</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-service_perfdata_file_processing_interval">Service performance data file processing
interval</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-host_perfdata_file_processing_command">Host performance data file processing command</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-service_perfdata_file_processing_command">Service performance data file processing
command</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-check_for_orphaned_services">Orphaned service check option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-check_for_orphaned_hosts">Orphaned host check option</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-check_service_freshness">Service freshness checking option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-service_freshness_check_interval">Service freshness check interval</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-check_host_freshness">Host freshness checking option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-host_freshness_check_interval">Host freshness check interval</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-p1_file_location">P1.PL File Location</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-enable_embedded_perl">Embedded Perl interpreter option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-use_embedded_perl_implicitly">Embedded Perl implicit use option</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
<p><a class="link" href="configmain.html#configmain-date_format">Date format</a></p>
</li></ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-illegal_object_name_chars">Illegal object name characters</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-illegal_macro_output_chars">Illegal macro output characters</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
<p><a class="link" href="configmain.html#configmain-keep_unknown_macros">Keep unknown macros</a></p>
</li></ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-use_regexp_matching">Regular expression matching option</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-use_true_regexp_matching">True regular expression matching option</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-admin_email">Administrator email address</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-admin_pager">Administrator pager</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
<p><a class="link" href="configmain.html#configmain-daemon_dumps_core">Daemon Core Dumps</a></p>
</li></ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-debug_file">Debug file</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-debug_level">Debug level</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-debug_verbosity">Debug verbosity</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-max_debug_file_size">Maximum debug file size option</a></p>
</li>
</ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
<p><a class="link" href="configmain.html#configmain-event_profiling">Event profiling</a></p>
</li></ul></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-allow_empty_hostgroup_assignment">Allow empty hostgroup assignment</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-process_empty_results">Process empty host performance results</a></p>
</li>
<li class="listitem">
<p><a class="link" href="configmain.html#configmain-process_empty_results">Process empty service performance results</a></p>
</li>
</ul></div>
<p>Below you will find descriptions of each main Icinga configuration file option...</p>
<p><a name="configmain-log_file"></a> <span class="bold"><strong>Log File</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>log_file=<file_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>log_file=/usr/local/icinga/var/icinga.log</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This variable specifies where Icinga should create its main log file. This should be the first variable that you define in
your configuration file, as Icinga will try to write errors that it finds in the rest of your configuration data to this file. If
you have <a class="link" href="configmain.html#configmain-log_rotation_method">log rotation</a> enabled, this file will automatically be rotated every hour,
day, week, or month.</p>
<p><a name="configmain-cfg_file"></a> <span class="bold"><strong>Object Configuration File</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>cfg_file=<file_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td>
<p><span class="color"><font color="red"><span class="bold"><strong>cfg_file=/usr/local/icinga/etc/conf.d/hosts.cfg</strong></span></font></span></p>
<p><span class="color"><font color="red"><span class="bold"><strong>cfg_file=/usr/local/icinga/etc/conf.d/services.cfg</strong></span></font></span></p>
<p><span class="color"><font color="red"><span class="bold"><strong>cfg_file=/usr/local/icinga/etc/conf.d/commands.cfg</strong></span>
</font></span></p>
</td>
</tr>
</tbody>
</table>
</div>
<p>This directive is used to specify an <a class="link" href="configobject.html" title="3.3. Object Configuration Overview">object configuration file</a> containing object definitions
that Icinga should use for monitoring. Object configuration files contain definitions for hosts, host groups, contacts, contact
groups, services, commands, etc. You can separate your configuration information into several files and specify multiple
<span class="emphasis"><em>cfg_file=</em></span> statements to have each of them processed.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>Using <code class="filename">cfg_file=.../foo/bar.cfg</code> for a file in the same directory which is specified in a
<code class="filename">cfg_dir=.../foo</code> directive will result in the file being processed twice and lead to config verification
errors.</p>
</td></tr>
</table></div>
<p><a name="configmain-cfg_dir"></a> <span class="bold"><strong>Object Configuration Directory</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>cfg_dir=<directory_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>cfg_dir=/usr/local/icinga/etc/conf.d</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This directive is used to specify a directory which contains <a class="link" href="configobject.html" title="3.3. Object Configuration Overview">object configuration files</a> that
Icinga should use for monitoring. All files in the directory with a <span class="emphasis"><em>.cfg</em></span> extension are processed as object
config files. Additionally, Icinga will recursively process all config files in subdirectories of the directory you specify here.
You can separate your configuration files into different directories and specify multiple <span class="emphasis"><em>cfg_dir=</em></span> statements to have
all config files in each directory processed.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>Using <code class="filename">cfg_file=.../foo/bar.cfg</code> for a file in the same directory which is specified in a
<code class="filename">cfg_dir=.../foo</code> directive will result in the file being processed twice and lead to config verification
errors.</p>
</td></tr>
</table></div>
<p><a name="configmain-object_cache_file"></a> <span class="bold"><strong>Object Cache File</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>object_cache_file=<file_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>object_cache_file=/usr/local/icinga/var/objects.cache</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This directive is used to specify a file in which a cached copy of <a class="link" href="configobject.html" title="3.3. Object Configuration Overview">object definitions</a> should be
stored. The cache file is (re)created every time Icinga 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 class="link" href="configmain.html#configmain-cfg_file">object config files</a> while
Icinga is running without affecting the output displayed in the CGIs.</p>
<p><a name="configmain-precached_object_file"></a> <span class="bold"><strong>Precached Object File</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>precached_object_file=<file_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>precached_object_file=/usr/local/icinga/var/objects.precache</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This directive is used to specify a file in which a pre-processed, pre-cached copy of <a class="link" href="configobject.html" title="3.3. Object Configuration Overview">object
definitions</a> should be stored. This file can be used to drastically improve startup times in large/complex Icinga
installations. Read more information on how to speed up start times <a class="link" href="faststartup.html" title="8.4. Fast Startup Options">here</a>.</p>
<p><a name="configmain-resource_file"></a> <span class="bold"><strong>Resource File</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>resource_file=<file_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>resource_file=/usr/local/icinga/etc/resource.cfg</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This is used to specify an optional resource file that can contain $USERn$ <a class="link" href="macros.html" title="5.2. Understanding Macros and How They Work">macro</a> definitions. $USERn$
macros are useful for storing usernames, passwords, and items commonly used in command definitions (like directory paths). The CGIs will
<span class="emphasis"><em>not</em></span> 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 - Icinga
will process them all. See the sample resource.cfg file in the <span class="emphasis"><em>sample-config/</em></span> subdirectory of the Icinga
distribution for an example of how to define $USERn$ macros.</p>
<p><a name="configmain-temp_file"></a> <span class="bold"><strong>Temp File</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>temp_file=<file_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>temp_file=/usr/local/icinga/var/icinga.tmp</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This is a temporary file that Icinga 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="configmain-temp_path"></a> <span class="bold"><strong>Temp Path</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>temp_path=<dir_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>temp_path=/tmp</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This is a directory that Icinga can use as scratch space for creating temporary files used during the monitoring process. You
should run <span class="emphasis"><em>tmpwatch</em></span>, or a similiar utility, on this directory occassionally to delete files older than 24
hours.</p>
<p><a name="configmain-status_file"></a> <span class="bold"><strong>Status File</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>status_file=<file_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>status_file=/usr/local/icinga/var/status.dat</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the file that Icinga uses to store the current status, comment, and downtime information. 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 Icinga stops and recreated when it starts.</p>
<p><a name="configmain-status_update_interval"></a> <span class="bold"><strong>Status File Update Interval</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>status_update_interval=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>status_update_interval=15</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This setting determines how often (in seconds) that Icinga will update status data in the <a class="link" href="configmain.html#configmain-status_file">status file</a>. The minimum update interval is 1 second.</p>
<p><a name="configmain-icinga_user"></a> <span class="bold"><strong>Icinga User</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>icinga_user=<username/UID></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>icinga_user=icinga</strong></span></font></span> </p></td>
</tr>
</tbody>
</table>
</div>
<p>This is used to set the effective user that the Icinga process should run as. After initial program startup and before
starting to monitor anything, Icinga will drop its effective privileges and run as this user. You may specify either a username or
a UID.</p>
<p><a name="configmain-icinga_group"></a> <span class="bold"><strong>Icinga Group</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>icinga_group=<groupname/GID></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>icinga_group=icinga</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This is used to set the effective group that the Icinga process should run as. After initial program startup and before
starting to monitor anything, Icinga will drop its effective privileges and run as this group. You may specify either a groupname
or a GID.</p>
<p><a name="configmain-enable_notifications"></a> <span class="bold"><strong>Notifications Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>enable_notifications=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>enable_notifications=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will send out <a class="link" href="notifications.html" title="5.11. Notifications">notifications</a> when it
initially (re)starts. If this option is disabled, Icinga will not send out notifications for any host or service.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>If you have <a class="link" href="configmain.html#configmain-retain_state_information">state retention</a> enabled, Icinga will ignore this
setting when it (re)starts and use the last known setting for this option (as stored in the <a class="link" href="configmain.html#configmain-state_retention_file">state retention file</a>), <span class="emphasis"><em>unless</em></span> you disable the <a class="link" href="configmain.html#configmain-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 class="link" href="configmain.html#configmain-use_retained_program_state">use_retained_program_state</a> is enabled), you'll
have to use the appropriate <a class="link" href="extcommands.html" title="7.1. External Commands">external command</a> or change it via the web interface.</p>
</td></tr>
</table></div>
<p>Values are as follows:</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Disable notifications</p>
</li>
<li class="listitem">
<p>1 = Enable notifications (default)</p>
</li>
</ul></div>
<p><a name="configmain-execute_service_checks"></a> <span class="bold"><strong>Service Check Execution Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>execute_service_checks=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>execute_service_checks=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will execute service checks when it initially (re)starts. If this option is
disabled, Icinga will not actively execute any service checks and will remain in a sort of "sleep" mode (it can still accept <a class="link" href="passivechecks.html" title="5.7. Passive Checks">passive checks</a> unless you've <a class="link" href="configmain.html#configmain-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 class="link" href="redundancy.html" title="7.7. Redundant and Failover Network Monitoring">redundancy</a>, or when setting up a <a class="link" href="distributed.html" title="7.6. Distributed Monitoring">distributed</a> monitoring environment.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>If you have <a class="link" href="configmain.html#configmain-retain_state_information">state retention</a> enabled, Icinga will ignore this
setting when it (re)starts and use the last known setting for this option (as stored in the <a class="link" href="configmain.html#configmain-state_retention_file">state retention file</a>), <span class="emphasis"><em>unless</em></span> you disable the <a class="link" href="configmain.html#configmain-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 class="link" href="configmain.html#configmain-use_retained_program_state">use_retained_program_state</a> is enabled), you'll
have to use the appropriate <a class="link" href="extcommands.html" title="7.1. External Commands">external command</a> or change it via the web interface.</p>
</td></tr>
</table></div>
<p>Values are as follows:</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't execute service checks</p>
</li>
<li class="listitem">
<p>1 = Execute service checks (default)</p>
</li>
</ul></div>
<p><a name="configmain-accept_passive_service_checks"></a> <span class="bold"><strong>Passive Service Check Acceptance
Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>accept_passive_service_checks=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>accept_passive_service_checks=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will accept <a class="link" href="passivechecks.html" title="5.7. Passive Checks">passive service checks</a> when it
initially (re)starts. If this option is disabled, Icinga will not accept any passive service checks.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>If you have <a class="link" href="configmain.html#configmain-retain_state_information">state retention</a> enabled, Icinga will ignore this
setting when it (re)starts and use the last known setting for this option (as stored in the <a class="link" href="configmain.html#configmain-state_retention_file">state retention file</a>), <span class="emphasis"><em>unless</em></span> you disable the <a class="link" href="configmain.html#configmain-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 class="link" href="configmain.html#configmain-use_retained_program_state">use_retained_program_state</a> is enabled), you'll
have to use the appropriate <a class="link" href="extcommands.html" title="7.1. External Commands">external command</a> or change it via the web interface.</p>
</td></tr>
</table></div>
<p>Values are as follows:</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't accept passive service checks</p>
</li>
<li class="listitem">
<p>1 = Accept passive service checks (default)</p>
</li>
</ul></div>
<p><a name="configmain-execute_host_checks"></a> <span class="bold"><strong>Host Check Execution Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>execute_host_checks=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>execute_host_checks=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will execute on-demand and regularly scheduled host checks when it initially
(re)starts. If this option is disabled, Icinga will not actively execute any host checks, although it can still accept <a class="link" href="passivechecks.html" title="5.7. Passive Checks">passive host checks</a> unless you've <a class="link" href="configmain.html#configmain-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 class="link" href="redundancy.html" title="7.7. Redundant and Failover Network Monitoring">redundancy</a>, or when setting up a <a class="link" href="distributed.html" title="7.6. Distributed Monitoring">distributed</a> monitoring environment.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>If you have <a class="link" href="configmain.html#configmain-retain_state_information">state retention</a> enabled, Icinga will ignore this
setting when it (re)starts and use the last known setting for this option (as stored in the <a class="link" href="configmain.html#configmain-state_retention_file">state retention file</a>), <span class="emphasis"><em>unless</em></span> you disable the <a class="link" href="configmain.html#configmain-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 class="link" href="configmain.html#configmain-use_retained_program_state">use_retained_program_state</a> is enabled), you'll
have to use the appropriate <a class="link" href="extcommands.html" title="7.1. External Commands">external command</a> or change it via the web interface.</p>
</td></tr>
</table></div>
<p>Values are as follows:</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't execute host checks</p>
</li>
<li class="listitem">
<p>1 = Execute host checks (default)</p>
</li>
</ul></div>
<p><a name="configmain-accept_passive_host_checks"></a> <span class="bold"><strong>Passive Host Check Acceptance
Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>accept_passive_host_checks=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>accept_passive_host_checks=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will accept <a class="link" href="passivechecks.html" title="5.7. Passive Checks">passive host checks</a> when it
initially (re)starts. If this option is disabled, Icinga will not accept any passive host checks.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>If you have <a class="link" href="configmain.html#configmain-retain_state_information">state retention</a> enabled, Icinga will ignore this
setting when it (re)starts and use the last known setting for this option (as stored in the <a class="link" href="configmain.html#configmain-state_retention_file">state retention file</a>), <span class="emphasis"><em>unless</em></span> you disable the <a class="link" href="configmain.html#configmain-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 class="link" href="configmain.html#configmain-use_retained_program_state">use_retained_program_state</a> is enabled), you'll
have to use the appropriate <a class="link" href="extcommands.html" title="7.1. External Commands">external command</a> or change it via the web interface.</p>
</td></tr>
</table></div>
<p>Values are as follows:</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't accept passive host checks</p>
</li>
<li class="listitem">
<p>1 = Accept passive host checks (default)</p>
</li>
</ul></div>
<p><a name="configmain-enable_event_handlers"></a> <span class="bold"><strong>Event Handler Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>enable_event_handlers=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>enable_event_handlers=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will run <a class="link" href="eventhandlers.html" title="7.3. Event Handlers">event handlers</a> when it initially
(re)starts. If this option is disabled, Icinga will not run any host or service event handlers.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>If you have <a class="link" href="configmain.html#configmain-retain_state_information">state retention</a> enabled, Icinga will ignore this
setting when it (re)starts and use the last known setting for this option (as stored in the <a class="link" href="configmain.html#configmain-state_retention_file">state retention file</a>), <span class="emphasis"><em>unless</em></span> you disable the <a class="link" href="configmain.html#configmain-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 class="link" href="configmain.html#configmain-use_retained_program_state">use_retained_program_state</a> is enabled), you'll
have to use the appropriate <a class="link" href="extcommands.html" title="7.1. External Commands">external command</a> or change it via the web interface.</p>
</td></tr>
</table></div>
<p>Values are as follows:</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Disable event handlers</p>
</li>
<li class="listitem">
<p>1 = Enable event handlers (default)</p>
</li>
</ul></div>
<p><a name="configmain-log_rotation_method"></a> <span class="bold"><strong>Log Rotation Method</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>log_rotation_method=<n/h/d/w/m></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>log_rotation_method=d</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the rotation method that you would like Icinga to use for your log file. Values are as follows:</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>n = None (don't rotate the log - this is the default)</p>
</li>
<li class="listitem">
<p>h = Hourly (rotate the log at the top of each hour)</p>
</li>
<li class="listitem">
<p>d = Daily (rotate the log at midnight each day)</p>
</li>
<li class="listitem">
<p>w = Weekly (rotate the log at midnight on Saturday)</p>
</li>
<li class="listitem">
<p>m = Monthly (rotate the log at midnight on the last day of the month)</p>
</li>
</ul></div>
<p><a name="configmain-log_archive_path"></a> <span class="bold"><strong>Log Archive Path</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>log_archive_path=<path></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>log_archive_path=/usr/local/icinga/var/archives/</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the directory where Icinga should place log files that have been rotated. This option is ignored if you choose to not
use the <a class="link" href="configmain.html#configmain-log_rotation_method">log rotation</a> functionality.</p>
<p><a name="configmain-use_daemon_log"></a><span class="bold"><strong>Logging Options for Daemon</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>use_daemon_log=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>use_daemon_log=1</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines if the log daemon writes to the log file (usually icinga.log).</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = logging disabled</p>
</li>
<li class="listitem">
<p>1 = logging enabled (default)</p>
</li>
</ul></div>
<p><a name="configmain-check_external_commands"></a> <span class="bold"><strong>External Command Check Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>check_external_commands=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>check_external_commands=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will check the <a class="link" href="configmain.html#configmain-command_file">command file</a> for
commands that should be executed. This option must be enabled if you plan on using the <a class="link" href="cgis.html#cgis-cmd_cgi">command CGI</a> to
issue commands via the web interface. Icinga Web and other addons like NagVis, Nagios Checker, Nagstamon and NagiosQL also
use this file to issue commands to Icinga. More information on external commands can be found <a class="link" href="extcommands.html" title="7.1. External Commands">here</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't check external commands</p>
</li>
<li class="listitem">
<p>1 = Check external commands (default)</p>
</li>
</ul></div>
<p><a name="configmain-command_check_interval"></a> <span class="bold"><strong>External Command Check Interval</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>command_check_interval=<xxx>[s]</strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>command_check_interval=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>If you specify a number with an "s" appended to it (i.e. 30s), this is the number of <span class="emphasis"><em>seconds</em></span> 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 class="link" href="configmain.html#configmain-interval_length">interval_length</a> value (as defined below) from the default value of
60, this number will mean minutes.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>Icinga will also check for external commands after event handlers are executed.</p>
</td></tr>
</table></div>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>By setting this value to <span class="bold"><strong>-1</strong></span>, Icinga will check for external commands as often as possible.
Each time Icinga checks for external commands it will read and process all commands present in the <a class="link" href="configmain.html#configmain-command_file">command file</a> before continuing on with its other duties. More information on external commands
can be found <a class="link" href="extcommands.html" title="7.1. External Commands">here</a>.</p>
</td></tr>
</table></div>
<p><a name="configmain-command_file"></a> <span class="bold"><strong>External Command File</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>command_file=<file_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>command_file=/usr/local/icinga/var/rw/icinga.cmd</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the file that Icinga will check for external commands to process. The <a class="link" href="cgis.html#cgis-cmd_cgi">command
CGI</a>, Icinga Web and other addons write commands to this file. The external command file is implemented as a named pipe (FIFO),
which is created when Icinga starts and removed when it shuts down. If the file exists when Icinga starts, the Icinga
process will terminate with an error message. More information on external commands can be found <a class="link" href="extcommands.html" title="7.1. External Commands">here</a>.</p>
<p><a name="configmain-external_command_buffer_slots"></a> <span class="bold"><strong>External Command Buffer Slots</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>external_command_buffer_slots=<#></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>external_command_buffer_slots=512</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>This is an advanced feature. This option determines how many buffer slots Icinga will reserve for caching external commands
that have been read from the external command file by a worker thread, but have not yet been processed by the main thread of the
Icinga daemon. Each slot can hold one external command, so this option essentially determines how many commands can be buffered.
For installations where you process a large number of passive checks (e.g. <a class="link" href="distributed.html" title="7.6. Distributed Monitoring">distributed setups</a>), you
may need to increase this number. You should consider using PNP4Nagios to graph Icinga's usage of external command buffers. You
can read more on how to configure graphing <a class="link" href="perfgraphs.html" title="8.7. Graphing Performance Info With PNP4Nagios">here</a>.</p>
</td></tr>
</table></div>
<p><a name="configmain-lock_file"></a> <span class="bold"><strong>Lock File</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>lock_file=<file_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>lock_file=/tmp/icinga.lock</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option specifies the location of the lock file that Icinga 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 Icinga process.</p>
<p><a name="configmain-retain_state_information"></a> <span class="bold"><strong>State Retention Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>retain_state_information=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>retain_state_information=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will retain state information for hosts and services between program restarts.
If you enable this option, you should supply a value for the <a class="link" href="configmain.html#configmain-state_retention_file">state_retention_file</a>
variable. When enabled, Icinga 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>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't retain state information</p>
</li>
<li class="listitem">
<p>1 = Retain state information (default)</p>
</li>
</ul></div>
<p><a name="configmain-state_retention_file"></a> <span class="bold"><strong>State Retention File</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>state_retention_file=<file_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>state_retention_file=/usr/local/icinga/var/retention.dat</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the file that Icinga will use for storing status, downtime, and comment information before it shuts down. When
Icinga 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. In order to make Icinga retain state information between program restarts, you must enable the <a class="link" href="configmain.html#configmain-retain_state_information">retain_state_information</a> option.</p>
<p><a name="configmain-sync_retention_file"></a> <span class="bold"><strong>Sync Retention File</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>sync_retention_file=<file_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>sync_retention_file=/usr/local/icinga/var/sync.dat</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This is an advanced option which works like the state_retention_file so that you can load a subset of retention information such as
status , acknowledgements, downtimes, and comments (you will have to create the contents of this file outside of Icinga). When
Icinga is restarted, it reads the information in the sync_retention_file and will update the host or service specified <span class="emphasis"><em>if
the last_update time in the sync file is newer</em></span> than in the state_retention_file, otherwise information will be discarded for
that host or service. After the sync file has been read, it will be removed. To disable, comment out the option.</p>
<p><a name="configmain-retention_update_interval"></a> <span class="bold"><strong>Automatic State Retention Update
Interval</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>retention_update_interval=<minutes></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>retention_update_interval=60</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This setting determines how often (in minutes) that Icinga will automatically save retention data during normal operation. If
you set this value to 0, Icinga 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 class="link" href="configmain.html#configmain-retain_state_information">retain_state_information</a> option), this option has no effect.</p>
<p><a name="configmain-use_retained_program_state"></a> <span class="bold"><strong>Use Retained Program State Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>use_retained_program_state=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>use_retained_program_state=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This setting determines whether or not Icinga 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 class="link" href="configmain.html#configmain-enable_notifications">enable_notifications</a>, <a class="link" href="configmain.html#configmain-enable_flap_detection">enable_flap_detection</a>, <a class="link" href="configmain.html#configmain-enable_event_handlers">enable_event_handlers</a>, <a class="link" href="configmain.html#configmain-execute_service_checks">execute_service_checks</a>, and <a class="link" href="configmain.html#configmain-accept_passive_service_checks">accept_passive_service_checks</a> options. If you do not have <a class="link" href="configmain.html#configmain-retain_state_information">state retention</a> enabled, this option has no effect.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't use retained program state</p>
</li>
<li class="listitem">
<p>1 = Use retained program state (default)</p>
</li>
</ul></div>
<p><a name="configmain-dump_retained_host_service_states_to_neb"></a><span class="bold"><strong>Dump Retained Host Service States To
Neb</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>dump_retained_host_service_states_to_neb=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>dump_retained_host_service_states_to_neb=0</strong></span>
</font></span> </p></td>
</tr>
</tbody>
</table>
</div>
<p>This setting determines whether or not Icinga will dump host and service states based on the values saved in the <a class="link" href="configmain.html#configmain-state_retention_file">retention file</a> to the neb modules. If you don't want that, use at your own risk and
disable it.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't dump status informations to neb (default in 1.10+)</p>
</li>
<li class="listitem">
<p>1 = Dump status informations to neb</p>
</li>
</ul></div>
<p><a name="configmain-use_retained_scheduling_info"></a> <span class="bold"><strong>Use Retained Scheduling Info
Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>use_retained_scheduling_info=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>use_retained_scheduling_info=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This setting determines whether or not Icinga 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, we would recommend disabling this option when you first
restart Icinga, as it can adversely skew the spread of initial checks. Otherwise you will probably want to leave it enabled.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't use retained scheduling info</p>
</li>
<li class="listitem">
<p>1 = Use retained scheduling info (default)</p>
</li>
</ul></div>
<p><a name="configmain-retained_host_attribute_mask"></a></p>
<p><a name="configmain-retained_service_attribute_mask"></a> <span class="bold"><strong>Retained Host and Service Attribute
Masks</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td>
<p>
<span class="bold"><strong>retained_host_attribute_mask=<number></strong></span>
</p> <p>
<span class="bold"><strong>retained_service_attribute_mask=<number></strong></span>
</p>
</td>
</tr>
<tr>
<td><p>Example:</p></td>
<td>
<p>
<span class="color"><font color="red">
<span class="bold"><strong>retained_host_attribute_mask=0</strong></span>
</font></span>
</p> <p>
<span class="color"><font color="red">
<span class="bold"><strong>retained_service_attribute_mask=0</strong></span>
</font></span>
</p>
</td>
</tr>
</tbody>
</table>
</div>
<p>WARNING: This is an advanced feature. You'll need to read the Icinga source code to use this option effectively.</p>
<p>These options determine which host or service attributes are NOT retained across program restarts. The values for these options are
a bitwise AND of values specified by the "MODATTR_" definitions in the include/common.h source code file. By default, all host and service
attributes are retained.</p>
<p><a name="configmain-retained_process_host_attribute_mask"></a></p>
<p><a name="configmain-retained_process_service_attribute_mask"></a> <span class="bold"><strong>Retained Process Attribute
Masks</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td>
<p>
<span class="bold"><strong>retained_process_host_attribute_mask=<number></strong></span>
</p> <p>
<span class="bold"><strong>retained_process_service_attribute_mask=<number></strong></span>
</p>
</td>
</tr>
<tr>
<td><p>Example:</p></td>
<td>
<p>
<span class="color"><font color="red">
<span class="bold"><strong>retained_process_host_attribute_mask=0</strong></span>
</font></span>
</p> <p>
<span class="color"><font color="red">
<span class="bold"><strong>retained_process_service_attribute_mask=0</strong></span>
</font></span>
</p>
</td>
</tr>
</tbody>
</table>
</div>
<p>WARNING: This is an advanced feature. You'll need to read the Icinga source code to use this option effectively.</p>
<p>These options determine which process attributes are NOT retained across program restarts. There are two masks because there are
often separate host and service process attributes that can be changed. For example, host checks can be disabled at the program level,
while service checks are still enabled. The values for these options are a bitwise AND of values specified by the "MODATTR_" definitions
in the include/common.h source code file. By default, all process attributes are retained.</p>
<p><a name="configmain-retained_contact_host_attribute_mask"></a></p>
<p><a name="configmain-retained_contact_service_attribute_mask"></a> <span class="bold"><strong>Retained Contact Attribute
Masks</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td>
<p>
<span class="bold"><strong>retained_contact_host_attribute_mask=<number></strong></span>
</p> <p>
<span class="bold"><strong>retained_contact_service_attribute_mask=<number></strong></span>
</p>
</td>
</tr>
<tr>
<td><p>Example:</p></td>
<td>
<p>
<span class="color"><font color="red">
<span class="bold"><strong>retained_contact_host_attribute_mask=0</strong></span>
</font></span>
</p> <p>
<span class="color"><font color="red">
<span class="bold"><strong>retained_contact_service_attribute_mask=0</strong></span>
</font></span>
</p>
</td>
</tr>
</tbody>
</table>
</div>
<p>WARNING: This is an advanced feature. You'll need to read the Icinga source code to use this option effectively.</p>
<p>These options determine which contact attributes are NOT retained across program restarts. There are two masks because there are
often separate host and service contact attributes that can be changed. The values for these options are a bitwise AND of values specified
by the "MODATTR_" definitions in the include/common.h source code file. By default, all process attributes are retained.</p>
<p><a name="configmain-use_syslog"></a> <span class="bold"><strong>Syslog Logging Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>use_syslog=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>use_syslog=1</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This variable determines whether messages are logged to the syslog facility on your local host. Values are as follows:</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't use syslog facility</p>
</li>
<li class="listitem">
<p>1 = Use syslog facility</p>
</li>
</ul></div>
<p><a name="configmain-use_syslog_local_facility"></a> <span class="bold"><strong>Local Syslog Facility Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>use_syslog_local_facility=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>use_syslog_local_facility=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>If you enabled use_syslog you can set Icinga to use a local facility instead of the default. Values are as follows:</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't use syslog local facility</p>
</li>
<li class="listitem">
<p>1 = Use syslog local facility</p>
</li>
</ul></div>
<p><a name="configmain-syslog_local_facility"></a> <span class="bold"><strong>Syslog Local Facility Value</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>syslog_local_facility=<0|1|2|3|4|5|6|7></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>syslog_local_facility=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>If you enabled use_syslog_local_facility you can choose which local facility to use. Valid values are from 0 to 7.</p>
<p><a name="configmain-log_notifications"></a> <span class="bold"><strong>Notification Logging Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>log_notifications=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>log_notifications=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<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>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't log notifications</p>
</li>
<li class="listitem">
<p>1 = Log notifications</p>
</li>
</ul></div>
<p><a name="configmain-log_service_retries"></a> <span class="bold"><strong>Service Check Retry Logging Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>log_service_retries=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>log_service_retries=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<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 Icinga 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
Icinga or test out service <a class="link" href="eventhandlers.html" title="7.3. Event Handlers">event handlers</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't log service check retries</p>
</li>
<li class="listitem">
<p>1 = Log service check retries</p>
</li>
</ul></div>
<p><a name="configmain-log_host_retries"></a> <span class="bold"><strong>Host Check Retry Logging Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>log_host_retries=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>log_host_retries=1</strong></span></font></span> </p></td>
</tr>
</tbody>
</table>
</div>
<p>This variable determines whether or not host check retries are logged. Logging host check retries is mostly useful when attempting
to debug Icinga or test out host <a class="link" href="eventhandlers.html" title="7.3. Event Handlers">event handlers</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't log host check retries</p>
</li>
<li class="listitem">
<p>1 = Log host check retries</p>
</li>
</ul></div>
<p><a name="configmain-log_event_handlers"></a> <span class="bold"><strong>Event Handler Logging Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>log_event_handlers=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>log_event_handlers=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This variable determines whether or not service and host <a class="link" href="eventhandlers.html" title="7.3. Event Handlers">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 Icinga or first trying out your event handler scripts.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't log event handlers</p>
</li>
<li class="listitem">
<p>1 = Log event handlers</p>
</li>
</ul></div>
<p><a name="configmain-log_initial_states"></a> <span class="bold"><strong>Initial States Logging Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>log_initial_states=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>log_initial_states=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This variable determines whether or not Icinga 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>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't log initial states (default)</p>
</li>
<li class="listitem">
<p>1 = Log initial states</p>
</li>
</ul></div>
<p><a name="configmain-log_external_commands"></a> <span class="bold"><strong>External Command Logging Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>log_external_commands=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>log_external_commands=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This variable determines whether or not Icinga will log <a class="link" href="extcommands.html" title="7.1. External Commands">external commands</a> that it receives
from the <a class="link" href="configmain.html#configmain-command_file">external command file</a>.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>This option does not control whether or not <a class="link" href="passivechecks.html" title="5.7. Passive Checks">passive service checks</a> (which are a type of
external command) get logged. To enable or disable logging of passive checks, use the <a class="link" href="configmain.html#configmain-log_passive_checks">log_passive_checks</a> option.</p>
</td></tr>
</table></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't log external commands</p>
</li>
<li class="listitem">
<p>1 = Log external commands (default)</p>
</li>
</ul></div>
<p><a name="configmain-log_external_commands_user"></a> <span class="bold"><strong>External Commands User Logging
Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>log_external_commands_user=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>log_external_commands_user=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to enable the logging of the current user of external commands. The syntax will be CMD;username;cmdargs
instead of CMD;cmdargs written to the logs, if the external application sends that correctly. Since this will break compatibility with
existing log parsers, it is intentionally disabled by default.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>This option is deprecated starting with Icinga 1.4 because you can use the directive <a class="link" href="configcgi.html#configcgi-use_logging">use_logging</a> to enable logging of CGI commands.</p>
</td></tr>
</table></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't log user name using external commands (default)</p>
</li>
<li class="listitem">
<p>1 = Log user name using external commands</p>
</li>
</ul></div>
<p><a name="configmain-log_passive_checks"></a> <span class="bold"><strong>Passive Check Logging Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>log_passive_checks=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>log_passive_checks=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This variable determines whether or not Icinga will log <a class="link" href="passivechecks.html" title="5.7. Passive Checks">passive host and service checks</a>
that it receives from the <a class="link" href="configmain.html#configmain-command_file">external command file</a>. If you are setting up a <a class="link" href="distributed.html" title="7.6. Distributed Monitoring">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>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't log passive checks</p>
</li>
<li class="listitem">
<p>1 = Log passive checks (default)</p>
</li>
</ul></div>
<p><a name="configmain-log_current_states"></a> <span class="bold"><strong>Current State Logging Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>log_current_states=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>log_current_states=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This variable determines whether or not Icinga will log the current states of hosts and services after a log rotation. If you
set the value of log_current_states to 0 the current states will not be written to the main log file after a log rotation.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't log current host and service states</p>
</li>
<li class="listitem">
<p>1 = Log current host and service states (default)</p>
</li>
</ul></div>
<p><a name="configmain-log_long_plugin_output"></a> <span class="bold"><strong>Long Plugin Output Logging Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>log_long_plugin_output=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>log_long_plugin_output=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This variable determines whether or not Icinga will log the complete output of a plugin (not only the first line). If you set
the value of log_long_plugin_output to 1 the complete plugin output will be logged.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Only log the first line of plugin output (default)</p>
</li>
<li class="listitem">
<p>1 = Log complete plugin output</p>
</li>
</ul></div>
<p><a name="configmain-global_host_event_handler"></a> <span class="bold"><strong>Global Host Event Handler Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>global_host_event_handler=<command></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>global_host_event_handler=log-host-event-to-db</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<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
<span class="emphasis"><em>command</em></span> argument is the short name of a command that you define in your <a class="link" href="configobject.html" title="3.3. Object Configuration Overview">object
configuration file</a>. The maximum amount of time that this command can run is controlled by the <a class="link" href="configmain.html#configmain-event_handler_timeout">event_handler_timeout</a> option. More information on event handlers can be found <a class="link" href="eventhandlers.html" title="7.3. Event Handlers">here</a>.</p>
<p><a name="configmain-global_service_event_handler"></a> <span class="bold"><strong>Global Service Event Handler
Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>global_service_event_handler=<command></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>global_service_event_handler=log-service-event-to-db</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<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
<span class="emphasis"><em>command</em></span> argument is the short name of a command that you define in your <a class="link" href="configobject.html" title="3.3. Object Configuration Overview">object
configuration file</a>. The maximum amount of time that this command can run is controlled by the <a class="link" href="configmain.html#configmain-event_handler_timeout">event_handler_timeout</a> option. More information on event handlers can be found <a class="link" href="eventhandlers.html" title="7.3. Event Handlers">here</a>.</p>
<p><a name="configmain-stalking_event_handlers_for_hosts"></a> <span class="bold"><strong> Event handlers for stalked
hosts</strong></span></p>
<p><a name="configmain-stalking_event_handlers_for_services"></a> <span class="bold"><strong> Event handlers for stalked
services</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td>
<p>
<span class="bold"><strong>stalking_event_handlers_for_hosts=<0|1></strong></span>
</p> <p>
<span class="bold"><strong>stalking_event_handlers_for_services=<0|1></strong></span>
</p>
</td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>stalking_event_handlers_for_hosts=1</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>These options allow you to specify whether or not Icinga executes event handlers for stalked hosts or services, respectively.
This way it is possible to forward status information changes to external systems.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Event handler disabled (default)</p>
</li>
<li class="listitem">
<p>1 = Event handler enabled</p>
</li>
</ul></div>
<p><a name="configmain-stalking_notifications_for_hosts"></a> <span class="bold"><strong>Notifications for stalked
hosts</strong></span></p>
<p><a name="configmain-stalking_notifications_for_services"></a> <span class="bold"><strong>Notifications for stalked
services</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td>
<p>
<span class="bold"><strong>stalking_notification_for_hosts=<0|1></strong></span>
</p> <p>
<span class="bold"><strong>stalking_notifications_for_services=<0|1></strong></span>
</p>
</td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>stalking_notifications_for_hosts=1</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>These options specify globally for all contacts whether or not Icinga sends notifications for stalked hosts/services.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>Unless there are no stalking_options defined on a host/service, the global definitions above won't affect anything.</p>
</td></tr>
</table></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Notifications disabled (default)</p>
</li>
<li class="listitem">
<p>1 = Notifications enabled</p>
</li>
</ul></div>
<p><a name="configmain-sleep_time"></a> <span class="bold"><strong>Inter-Check Sleep Time</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>sleep_time=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>sleep_time=1</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the number of seconds that Icinga will sleep before checking to see if the next service or host check in the
scheduling queue should be executed. Note that Icinga will only sleep after it "catches up" with queued service checks that have
fallen behind.</p>
<p><a name="configmain-service_inter_check_delay_method"></a> <span class="bold"><strong>Service Inter-Check Delay
Method</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>service_inter_check_delay_method=<n/d/s/x.xx></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>service_inter_check_delay_method=s</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<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 Icinga 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 <span class="emphasis"><em>not</em></span> recommended, as it
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 class="link" href="checkscheduling.html#serviceintercheckdelay" title="7.23.4. Inter-Check Delay">here</a>. Values are as follows:</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>n = Don't use any delay - schedule all service checks to run immediately (i.e. at the same time!)</p>
</li>
<li class="listitem">
<p>d = Use a "dumb" delay of 1 second between service checks</p>
</li>
<li class="listitem">
<p>s = Use a "smart" delay calculation to spread service checks out evenly (default)</p>
</li>
<li class="listitem">
<p>x.xx = Use a user-supplied inter-check delay of x.xx seconds</p>
</li>
</ul></div>
<p><a name="configmain-max_service_check_spread"></a> <span class="bold"><strong>Maximum Service Check Spread</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>max_service_check_spread=<minutes></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>max_service_check_spread=30</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines the maximum number of minutes from when Icinga starts that all services (that are scheduled to be
regularly checked) are checked. This option will automatically adjust the <a class="link" href="configmain.html#configmain-service_inter_check_delay_method">service inter-check delay method</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 class="link" href="configmain.html#configmain-use_retained_scheduling_info">use_retained_scheduling_info</a> option. Default value is <span class="bold"><strong>30</strong></span> (minutes).</p>
<p><a name="configmain-service_interleave_factor"></a> <span class="bold"><strong>Service Interleave Factor</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>service_interleave_factor=<s|x></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>service_interleave_factor=s</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This variable determines how service checks are interleaved. Interleaving allows for a more even distribution of service checks,
reduced load on remote hosts, and faster overall detection of host problems. Setting this value to 1 is equivalent to not interleaving the
service checks (this is how versions of Icinga previous to 0.0.5 worked). Set this value to <span class="bold"><strong>s</strong></span>
(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 class="link" href="cgis.html#cgis-status_cgi">status CGI</a> (detailed view) when Icinga 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 class="link" href="checkscheduling.html#serviceinterleaving" title="7.23.5. Service Interleaving">here</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p><span class="emphasis"><em>x</em></span> = 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.</p>
</li>
<li class="listitem">
<p>s = Use a "smart" interleave factor calculation (default)</p>
</li>
</ul></div>
<p><a name="configmain-max_concurrent_checks"></a> <span class="bold"><strong>Maximum Concurrent Service Checks</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>max_concurrent_checks=<max_checks></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>max_concurrent_checks=20</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to specify the maximum number of service checks that can be run in parallel at any given time. Specifying a
value of 1 for this variable essentially prevents any service checks from being run in parallel. 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 Icinga, 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 class="link" href="checkscheduling.html#maxconcurrentchecks" title="7.23.6. Maximum Concurrent Service Checks">here</a>.</p>
<p><a name="configmain-check_result_reaper_frequency"></a> <span class="bold"><strong>Check Result Reaper Frequency</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>check_result_reaper_frequency=<frequency_in_seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>check_result_reaper_frequency=5</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to control the frequency <span class="emphasis"><em>in seconds</em></span> of check result "reaper" events. "Reaper" events
process the results from host and service checks that have finished executing. These events consitute the core of the monitoring logic in
Icinga.</p>
<p><a name="configmain-max_check_result_reaper_time"></a> <span class="bold"><strong>Maximum Check Result Reaper Time</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>max_check_result_reaper_time=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>max_check_result_reaper_time=30</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to control the maximum amount of time <span class="emphasis"><em>in seconds</em></span> that host and service check result
"reaper" events are allowed to run. "Reaper" events process the results from host and service checks that have finished executing. If
there are a lot of results to process, reaper events may take a long time to finish, which might delay timely execution of new host and
service checks. This variable allows you to limit the amount of time that an individual reaper event will run before it hands control back
over to Icinga for other portions of the monitoring logic.</p>
<p><a name="configmain-check_result_path"></a> <span class="bold"><strong>Check Result Path</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>check_result_path=<path></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>check_result_path=/var/spool/icinga/checkresults</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This options determines which directory Icinga will use to temporarily store host and service check results before they are
processed. This directory should not be used to store any other files, as Icinga will periodically clean this directory of old file
(see the <a class="link" href="configmain.html#configmain-max_check_result_file_age">max_check_result_file_age</a> option for more information).</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>Make sure that only a single instance of Icinga has access to the check result path. If multiple instances of Icinga
have their check result path set to the same directory, you will run into problems with check results being processed (incorrectly) by
the wrong instance of Icinga!</p>
</td></tr>
</table></div>
<p><a name="configmain-max_check_result_file_age"></a> <span class="bold"><strong>Max Check Result File Age</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>max_check_result_file_age=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>max_check_result_file_age=3600</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This options determines the maximum age in seconds that Icinga will consider check result files found in the <a class="link" href="configmain.html#configmain-check_result_path">check_result_path</a> directory to be valid. Check result files that are older that this
threshold will be deleted by Icinga and the check results they contain will not be processed. By using a value of zero (0) with
this option, Icinga will process all check result files - even if they're older than your hardware :-).</p>
<p><a name="configmain-host_inter_check_delay_method"></a> <span class="bold"><strong>Host Inter-Check Delay Method</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>host_inter_check_delay_method=<n/d/s/x.xx></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>host_inter_check_delay_method=s</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to control how host checks <span class="emphasis"><em>that are scheduled to be checked on a regular basis</em></span> are
initially "spread out" in the event queue. Using a "smart" delay calculation (the default) will cause Icinga 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 <span class="emphasis"><em>not</em></span> 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 class="link" href="checkscheduling.html#hostintercheckdelay">here</a>. Values are as follows:</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>n = Don't use any delay - schedule all host checks to run immediately (i.e. at the same time!)</p>
</li>
<li class="listitem">
<p>d = Use a "dumb" delay of 1 second between host checks</p>
</li>
<li class="listitem">
<p>s = Use a "smart" delay calculation to spread host checks out evenly (default)</p>
</li>
<li class="listitem">
<p>x.xx = Use a user-supplied inter-check delay of x.xx seconds</p>
</li>
</ul></div>
<p><a name="configmain-max_host_check_spread"></a> <span class="bold"><strong>Maximum Host Check Spread</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>max_host_check_spread=<minutes></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>max_host_check_spread=30</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines the maximum number of minutes from when Icinga starts that all hosts (that are scheduled to be
regularly checked) are checked. This option will automatically adjust the <a class="link" href="configmain.html#configmain-host_inter_check_delay_method">host
inter-check delay method</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 class="link" href="configmain.html#configmain-use_retained_scheduling_info">use_retained_scheduling_info</a> option. Default value is <span class="bold"><strong>30</strong></span> (minutes).</p>
<p><a name="configmain-interval_length"></a> <span class="bold"><strong>Timing Interval Length</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>interval_length=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>interval_length=60</strong></span></font></span> </p></td>
</tr>
</tbody>
</table>
</div>
<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 to re-notify a contact, etc.</p>
<p><span class="bold"><strong>Important:</strong></span> 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). We 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="configmain-auto_reschedule_checks"></a> <span class="bold"><strong>Auto-Rescheduling Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>auto_reschedule_checks=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>auto_reschedule_checks=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga 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><span class="bold"><strong>WARNING:</strong></span> 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="configmain-auto_rescheduling_interval"></a> <span class="bold"><strong>Auto-Rescheduling Interval</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>auto_rescheduling_interval=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>auto_rescheduling_interval=30</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines how often (in seconds) Icinga will attempt to automatically reschedule checks. This option only has an
effect if the <a class="link" href="configmain.html#configmain-auto_reschedule_checks">auto_reschedule_checks</a> option is enabled. Default is 30
seconds.</p>
<p><span class="bold"><strong>WARNING:</strong></span> 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="configmain-auto_rescheduling_window"></a> <span class="bold"><strong>Auto-Rescheduling Window</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>auto_rescheduling_window=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>auto_rescheduling_window=180</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines the "window" of time (in seconds) that Icinga 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 class="link" href="configmain.html#configmain-auto_reschedule_checks">auto_reschedule_checks</a> option is enabled. Default is 180 seconds (3
minutes).</p>
<p><span class="bold"><strong>WARNING:</strong></span> 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="configmain-use_agressive_host_checking"></a></p>
<p><a name="configmain-use_aggressive_host_checking"></a> <span class="bold"><strong>Aggressive Host Checking Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>use_aggressive_host_checking=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>use_aggressive_host_checking=0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>Icinga tries to be smart about how and when it checks the status of hosts. In general, disabling this option will allow
Icinga 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 Icinga not recognizing that a host recovered, we
would suggest <span class="bold"><strong>not</strong></span> enabling this option.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't use aggressive host checking (default)</p>
</li>
<li class="listitem">
<p>1 = Use aggressive host checking</p>
</li>
</ul></div>
<p><a name="configmain-translate_passive_host_checks"></a> <span class="bold"><strong>Translate Passive Host Checks
Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>translate_passive_host_checks=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>translate_passive_host_checks=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will translate DOWN/UNREACHABLE passive host check results to their "correct"
state from the viewpoint of the local Icinga instance. This can be very useful in distributed and failover monitoring
installations. More information on passive check state translation can be found <a class="link" href="passivestatetranslation.html" title="7.22. Passive Host State Translation">here</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Disable check translation (default)</p>
</li>
<li class="listitem">
<p>1 = Enable check translation</p>
</li>
</ul></div>
<p><a name="configmain-passive_host_checks_are_soft"></a> <span class="bold"><strong>Passive Host Checks Are SOFT
Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>passive_host_checks_are_soft=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>passive_host_checks_are_soft=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will treat <a class="link" href="passivechecks.html" title="5.7. Passive Checks">passive host checks</a> as HARD
states or SOFT states. By default, a passive host check result will put a host into a <a class="link" href="statetypes.html" title="5.8. State Types">HARD state type</a>.
You can change this behavior by enabling this option.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Passive host checks are HARD (default)</p>
</li>
<li class="listitem">
<p>1 = Passive host checks are SOFT</p>
</li>
</ul></div>
<p><a name="configmain-enable_predictive_host_dependency_checks"></a> <span class="bold"><strong>Predictive Host Dependency Checks
Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>enable_predictive_host_dependency_checks=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>enable_predictive_host_dependency_checks=1</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will execute predictive checks of hosts that are being depended upon (as defined
in <a class="link" href="objectdefinitions.html#objectdefinitions-hostdependency">host dependencies</a>) for a particular host when it changes state. Predictive
checks help ensure that the dependency logic is as accurate as possible. More information on how predictive checks work can be found <a class="link" href="dependencychecks.html" title="7.20. Predictive Dependency Checks">here</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Disable predictive checks</p>
</li>
<li class="listitem">
<p>1 = Enable predictive checks (default)</p>
</li>
</ul></div>
<p><a name="configmain-enable_predictive_service_dependency_checks"></a> <span class="bold"><strong>Predictive Service Dependency Checks
Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>enable_predictive_service_dependency_checks=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>enable_predictive_service_dependency_checks=1</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will execute predictive checks of services that are being depended upon (as
defined in <a class="link" href="objectdefinitions.html#objectdefinitions-servicedependency">service dependencies</a>) for a particular service when it changes
state. Predictive checks help ensure that the dependency logic is as accurate as possible. More information on how predictive checks work
can be found <a class="link" href="dependencychecks.html" title="7.20. Predictive Dependency Checks">here</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Disable predictive checks</p>
</li>
<li class="listitem">
<p>1 = Enable predictive checks (default)</p>
</li>
</ul></div>
<p><a name="configmain-cached_host_check_horizon"></a> <span class="bold"><strong>Cached Host Check Horizon</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>cached_host_check_horizon=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>cached_host_check_horizon=15</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines the maximum amount of time (in seconds) that the state of a previous host check is considered current. Cached
host states (from host checks that were performed more recently than the time specified by this value) can improve host check performance
immensely. Too high of a value for this option may result in (temporarily) inaccurate host states, while a low value may result in a
performance hit for host checks. Use a value of 0 if you want to disable host check caching. More information on cached checks can be
found <a class="link" href="cachedchecks.html" title="7.21. Cached Checks">here</a>.</p>
<p><a name="configmain-cached_service_check_horizon"></a> <span class="bold"><strong>Cached Service Check Horizon</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>cached_service_check_horizon=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>cached_service_check_horizon=15</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines the maximum amount of time (in seconds) that the state of a previous service check is considered current.
Cached service states (from service checks that were performed more recently than the time specified by this value) can improve service
check performance when a lot of <a class="link" href="objectdefinitions.html#objectdefinitions-servicedependency">service dependencies</a> are used. Too high of a
value for this option may result in inaccuracies in the service dependency logic. Use a value of 0 if you want to disable service check
caching. More information on cached checks can be found <a class="link" href="cachedchecks.html" title="7.21. Cached Checks">here</a>.</p>
<p><a name="configmain-use_large_installation_tweaks"></a> <span class="bold"><strong>Large Installation Tweaks Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>use_large_installation_tweaks=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>use_large_installation_tweaks=0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not the Icinga daemon will take several shortcuts to improve performance. These shortcuts
result in the loss of a few features, but larger installations will likely see a lot of benefit from doing so. More information on what
optimizations are taken when you enable this option can be found <a class="link" href="largeinstalltweaks.html" title="8.5. Large Installation Tweaks">here</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't use tweaks (default)</p>
</li>
<li class="listitem">
<p>1 = Use tweaks</p>
</li>
</ul></div>
<p><a name="configmain-free_child_process_memory"></a> <span class="bold"><strong>Child Process Memory Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>free_child_process_memory=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>free_child_process_memory=0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will free memory in child processes when they are fork()ed off from the main
process. By default, Icinga frees memory. However, if the <a class="link" href="configmain.html#configmain-use_large_installation_tweaks">use_large_installation_tweaks</a> option is enabled, it will not. By defining this
option in your configuration file, you are able to override things to get the behavior you want.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't free memory</p>
</li>
<li class="listitem">
<p>1 = Free memory</p>
</li>
</ul></div>
<p><a name="configmain-child_processes_fork_twice"></a> <span class="bold"><strong>Child Processes Fork Twice</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>child_processes_fork_twice=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>child_processes_fork_twice=0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will fork() child processes twice when it executes host and service checks. By
default, Icinga fork()s twice. However, if the <a class="link" href="configmain.html#configmain-use_large_installation_tweaks">use_large_installation_tweaks</a> option is enabled, it will only fork() once. By
defining this option in your configuration file, you are able to override things to get the behavior you want.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Fork() just once</p>
</li>
<li class="listitem">
<p>1 = Fork() twice</p>
</li>
</ul></div>
<p><a name="configmain-enable_environment_macros"></a> <span class="bold"><strong>Environment Macros Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>enable_environment_macros=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>enable_environment_macros=0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not the Icinga daemon will make all standard <a class="link" href="macrolist.html" title="5.3. Standard Macros in Icinga">macros</a>
available as environment variables to your check, notification, event hander, etc. commands. In large Icinga installations this can
be problematic because it takes additional memory and (more importantly) CPU to compute the values of all macros and make them available
to the environment.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't make macros available as environment variables (default)</p>
</li>
<li class="listitem">
<p>1 = Make macros available as environment variables</p>
</li>
</ul></div>
<p><a name="configmain-enable_flap_detection"></a> <span class="bold"><strong>Flap Detection Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>enable_flap_detection=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>enable_flap_detection=0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga 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 Icinga
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 class="link" href="flapping.html" title="7.8. Detection and Handling of State Flapping">here</a>.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>If you have <a class="link" href="configmain.html#configmain-retain_state_information">state retention</a> enabled, Icinga will ignore this
setting when it (re)starts and use the last known setting for this option (as stored in the <a class="link" href="configmain.html#configmain-state_retention_file">state retention file</a>), <span class="emphasis"><em>unless</em></span> you disable the <a class="link" href="configmain.html#configmain-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 class="link" href="configmain.html#configmain-use_retained_program_state">use_retained_program_state</a> is enabled), you'll
have to use the appropriate <a class="link" href="extcommands.html" title="7.1. External Commands">external command</a> or change it via the web interface.</p>
</td></tr>
</table></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't enable flap detection (default)</p>
</li>
<li class="listitem">
<p>1 = Enable flap detection</p>
</li>
</ul></div>
<p><a name="configmain-low_service_flap_threshold"></a> <span class="bold"><strong>Low Service Flap Threshold</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>low_service_flap_threshold=<percent></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>low_service_flap_threshold=25.0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<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 class="link" href="flapping.html" title="7.8. Detection and Handling of State Flapping">this</a>.</p>
<p><a name="configmain-high_service_flap_threshold"></a> <span class="bold"><strong>High Service Flap Threshold</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>high_service_flap_threshold=<percent></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>high_service_flap_threshold=50.0</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option is used to set the high threshold for detection of service flapping. For more information on how flap detection and
handling works (and how this option affects things) read <a class="link" href="flapping.html" title="7.8. Detection and Handling of State Flapping">this</a>.</p>
<p><a name="configmain-low_host_flap_threshold"></a> <span class="bold"><strong>Low Host Flap Threshold</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>low_host_flap_threshold=<percent></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>low_host_flap_threshold=25.0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<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 class="link" href="flapping.html" title="7.8. Detection and Handling of State Flapping">this</a>.</p>
<p><a name="configmain-high_host_flap_threshold"></a> <span class="bold"><strong>High Host Flap Threshold</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>high_host_flap_threshold=<percent></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>high_host_flap_threshold=50.0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option is used to set the high threshold for detection of host flapping. For more information on how flap detection and
handling works (and how this option affects things) read <a class="link" href="flapping.html" title="7.8. Detection and Handling of State Flapping">this</a>.</p>
<p><a name="configmain-soft_state_dependencies"></a> <span class="bold"><strong>Soft State Dependencies Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>soft_state_dependencies=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>soft_state_dependencies=0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will use soft state information when checking <a class="link" href="dependencies.html" title="7.13. Host and Service Dependencies">host
and service dependencies</a>. Normally Icinga will only use the latest hard host or service state when checking dependencies. If
you want it to use the latest state (regardless of whether its a soft or hard <a class="link" href="statetypes.html" title="5.8. State Types">state type</a>), enable this
option.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't use soft state dependencies (default)</p>
</li>
<li class="listitem">
<p>1 = Use soft state dependencies</p>
</li>
</ul></div>
<p><a name="configmain-time_change_threshold"></a><span class="bold"><strong>Time Change Threshold </strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>time_change_threshold=(seconds)</strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>time_change_threshold=900</strong></span> </font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>These option determines when Icinga will react to detected changes in system time (just forward).</p>
<p><a name="configmain-service_check_timeout"></a> <span class="bold"><strong>Service Check Timeout</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>service_check_timeout=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>service_check_timeout=60</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the maximum number of seconds that Icinga 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, Icinga will
kill it off thinking it is a runaway processes.</p>
<p><a name="configmain-service_check_timeout_state"></a> <span class="bold"><strong>Service Check Timeout State</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>service_check_timeout_state=<c/u/w/o></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>service_check_timeout_state=u</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This setting determines the state Icinga will report when a service check times out - that is does not respond within
service_check_timeout seconds. This can be useful if a machine is running at too high a load and you do not want to consider a failed
service check to be critical. The default was changed to service_check_timeout_state=u in Icinga1.0.1</p>
<p><a name="configmain-host_check_timeout"></a> <span class="bold"><strong>Host Check Timeout</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>host_check_timeout=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>host_check_timeout=60</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the maximum number of seconds that Icinga 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, Icinga will kill
it off thinking it is a runaway processes.</p>
<p><a name="configmain-event_handler_timeout"></a> <span class="bold"><strong>Event Handler Timeout</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>event_handler_timeout=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>event_handler_timeout=60</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the maximum number of seconds that Icinga will allow <a class="link" href="eventhandlers.html" title="7.3. Event Handlers">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,
Icinga will kill it off thinking it is a runaway processes.</p>
<p><a name="configmain-notification_timeout"></a> <span class="bold"><strong>Notification Timeout</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>notification_timeout=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>notification_timeout=60</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the maximum number of seconds that Icinga 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, Icinga
will kill it off thinking it is a runaway processes.</p>
<p><a name="configmain-ocsp_timeout"></a> <span class="bold"><strong>Obsessive Compulsive Service Processor Timeout</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>ocsp_timeout=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>ocsp_timeout=5</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the maximum number of seconds that Icinga will allow an <a class="link" href="configmain.html#configmain-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="configmain-ochp_timeout"></a> <span class="bold"><strong>Obsessive Compulsive Host Processor Timeout</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>ochp_timeout=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>ochp_timeout=5</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the maximum number of seconds that Icinga will allow an <a class="link" href="configmain.html#configmain-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="configmain-perfdata_timeout"></a> <span class="bold"><strong>Performance Data Processor Command Timeout</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>perfdata_timeout=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>perfdata_timeout=5</strong></span></font></span> </p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the maximum number of seconds that Icinga will allow a <a class="link" href="configmain.html#configmain-host_perfdata_command">host
performance data processor command</a> or <a class="link" href="configmain.html#configmain-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="configmain-obsess_over_services"></a> <span class="bold"><strong>Obsess Over Services Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>obsess_over_services=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>obsess_over_services=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This value determines whether or not Icinga will "obsess" over service checks results and run the <a class="link" href="configmain.html#configmain-ocsp_command">obsessive compulsive service processor command</a> you define. We know - funny name, but it was all
Ethan could think of. This option is useful for performing <a class="link" href="distributed.html" title="7.6. Distributed Monitoring">distributed monitoring</a>. If you're not doing
distributed monitoring, don't enable this option.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't obsess over services (default)</p>
</li>
<li class="listitem">
<p>1 = Obsess over services</p>
</li>
</ul></div>
<p><a name="configmain-ocsp_command"></a> <span class="bold"><strong>Obsessive Compulsive Service Processor Command</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>ocsp_command=<command></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>ocsp_command=obsessive_service_handler</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to specify a command to be run after <span class="emphasis"><em>every</em></span> service check, which can be useful in <a class="link" href="distributed.html" title="7.6. Distributed Monitoring">distributed monitoring</a>. This command is executed after any <a class="link" href="eventhandlers.html" title="7.3. Event Handlers">event handler</a>
or <a class="link" href="notifications.html" title="5.11. Notifications">notification</a> commands. The <span class="emphasis"><em>command</em></span> argument is the short name of a <a class="link" href="objectdefinitions.html#objectdefinitions-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 class="link" href="configmain.html#configmain-ocsp_timeout">ocsp_timeout</a> option. More information
on distributed monitoring can be found <a class="link" href="distributed.html" title="7.6. Distributed Monitoring">here</a>. This command is only executed if the <a class="link" href="configmain.html#configmain-obsess_over_services">obsess_over_services</a> option is enabled globally and if the
<span class="emphasis"><em>obsess_over_service</em></span> directive in the <a class="link" href="objectdefinitions.html#objectdefinitions-service">service definition</a> is
enabled.</p>
<p><a name="configmain-obsess_over_hosts"></a> <span class="bold"><strong>Obsess Over Hosts Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>obsess_over_hosts=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>obsess_over_hosts=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This value determines whether or not Icinga will "obsess" over host checks results and run the <a class="link" href="configmain.html#configmain-ochp_command">obsessive compulsive host processor command</a> you define. We know - funny name, but it was all
Ethan could think of. This option is useful for performing <a class="link" href="distributed.html" title="7.6. Distributed Monitoring">distributed monitoring</a>. If you're not doing
distributed monitoring, don't enable this option.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't obsess over hosts (default)</p>
</li>
<li class="listitem">
<p>1 = Obsess over hosts</p>
</li>
</ul></div>
<p><a name="configmain-ochp_command"></a> <span class="bold"><strong>Obsessive Compulsive Host Processor Command</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>ochp_command=<command></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>ochp_command=obsessive_host_handler</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to specify a command to be run after <span class="emphasis"><em>every</em></span> host check, which can be useful in <a class="link" href="distributed.html" title="7.6. Distributed Monitoring">distributed monitoring</a>. This command is executed after any <a class="link" href="eventhandlers.html" title="7.3. Event Handlers">event handler</a>
or <a class="link" href="notifications.html" title="5.11. Notifications">notification</a> commands. The <span class="emphasis"><em>command</em></span> argument is the short name of a <a class="link" href="objectdefinitions.html#objectdefinitions-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 class="link" href="configmain.html#configmain-ochp_timeout">ochp_timeout</a> option. More information
on distributed monitoring can be found <a class="link" href="distributed.html" title="7.6. Distributed Monitoring">here</a>. This command is only executed if the <a class="link" href="configmain.html#configmain-obsess_over_hosts">obsess_over_hosts</a> option is enabled globally and if the
<span class="emphasis"><em>obsess_over_host</em></span> directive in the <a class="link" href="objectdefinitions.html#objectdefinitions-host">host definition</a> is enabled.</p>
<p><a name="configmain-process_performance_data"></a> <span class="bold"><strong>Performance Data Processing Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>process_performance_data=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>process_performance_data=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This value determines whether or not Icinga will process host and service check <a class="link" href="perfdata.html" title="7.15. Performance Data">performance
data</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't process performance data (default)</p>
</li>
<li class="listitem">
<p>1 = Process performance data</p>
</li>
</ul></div>
<p><a name="configmain-host_perfdata_command"></a> <span class="bold"><strong>Host Performance Data Processing Command</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>host_perfdata_command=<command></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>host_perfdata_command=process-host-perfdata</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to specify a command to be run after <span class="emphasis"><em>every</em></span> host check to process host <a class="link" href="perfdata.html" title="7.15. Performance Data">performance data</a> that may be returned from the check. The <span class="emphasis"><em>command</em></span> argument is the short
name of a <a class="link" href="objectdefinitions.html#objectdefinitions-command">command definition</a> that you define in your object configuration file. This
command is only executed if the <a class="link" href="configmain.html#configmain-process_performance_data">process_performance_data</a> option is enabled
globally and if the <span class="emphasis"><em>process_perf_data</em></span> directive in the <a class="link" href="objectdefinitions.html#objectdefinitions-host">host definition</a>
is enabled.</p>
<p><a name="configmain-service_perfdata_command"></a> <span class="bold"><strong>Service Performance Data Processing
Command</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>service_perfdata_command=<command></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>service_perfdata_command=process-service-perfdata</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to specify a command to be run after <span class="emphasis"><em>every</em></span> service check to process service <a class="link" href="perfdata.html" title="7.15. Performance Data">performance data</a> that may be returned from the check. The <span class="emphasis"><em>command</em></span> argument is the short
name of a <a class="link" href="objectdefinitions.html#objectdefinitions-command">command definition</a> that you define in your object configuration file. This
command is only executed if the <a class="link" href="configmain.html#configmain-process_performance_data">process_performance_data</a> option is enabled
globally and if the <span class="emphasis"><em>process_perf_data</em></span> directive in the <a class="link" href="objectdefinitions.html#objectdefinitions-service">service
definition</a> is enabled.</p>
<p><a name="configmain-host_perfdata_file"></a> <span class="bold"><strong>Host Performance Data File</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>host_perfdata_file=<file_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>host_perfdata_file=/usr/local/icinga/var/host-perfdata.dat</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to specify a file to which host <a class="link" href="perfdata.html" title="7.15. Performance Data">performance data</a> will be written after every
host check. Data will be written to the performance file as specified by the <a class="link" href="configmain.html#configmain-host_perfdata_file_template">host_perfdata_file_template</a> option. Performance data is only written to this file
if the <a class="link" href="configmain.html#configmain-process_performance_data">process_performance_data</a> option is enabled globally and if the
<span class="emphasis"><em>process_perf_data</em></span> directive in the <a class="link" href="objectdefinitions.html#objectdefinitions-host">host definition</a> is enabled.</p>
<p><a name="configmain-service_perfdata_file"></a> <span class="bold"><strong>Service Performance Data File</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>service_perfdata_file=<file_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>service_perfdata_file=/usr/local/icinga/var/service-perfdata.dat</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to specify a file to which service <a class="link" href="perfdata.html" title="7.15. Performance Data">performance data</a> will be written after
every service check. Data will be written to the performance file as specified by the <a class="link" href="configmain.html#configmain-service_perfdata_file_template">service_perfdata_file_template</a> option. Performance data is only written to this
file if the <a class="link" href="configmain.html#configmain-process_performance_data">process_performance_data</a> option is enabled globally and if the
<span class="emphasis"><em>process_perf_data</em></span> directive in the <a class="link" href="objectdefinitions.html#objectdefinitions-service">service definition</a> is
enabled.</p>
<p><a name="configmain-host_perfdata_file_template"></a> <span class="bold"><strong>Host Performance Data File
Template</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>host_perfdata_file_template=<template></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$ \
\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines what (and how) data is written to the <a class="link" href="configmain.html#configmain-host_perfdata_file">host performance data
file</a>. The template may contain <a class="link" href="macros.html" title="5.2. Understanding Macros and How They Work">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="configmain-service_perfdata_file_template"></a> <span class="bold"><strong>Service Performance Data File
Template</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>service_perfdata_file_template=<template></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$ \
\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$ \ \t$SERVICEOUTPUT$\t$SERVICEPERFDATA$</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines what (and how) data is written to the <a class="link" href="configmain.html#configmain-service_perfdata_file">service performance
data file</a>. The template may contain <a class="link" href="macros.html" title="5.2. Understanding Macros and How They Work">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="configmain-host_perfdata_file_mode"></a> <span class="bold"><strong>Host Performance Data File Mode</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>host_perfdata_file_mode=<mode></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>host_perfdata_file_mode=a</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines how the <a class="link" href="configmain.html#configmain-host_perfdata_file">host performance data file</a> is opened. Unless the
file is a named pipe you'll probably want to use the default mode of append.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>a = Open file in append mode (default)</p>
</li>
<li class="listitem">
<p>w = Open file in write mode</p>
</li>
<li class="listitem">
<p>p = Open in non-blocking read/write mode (useful when writing to pipes)</p>
</li>
</ul></div>
<p><a name="configmain-service_perfdata_file_mode"></a> <span class="bold"><strong>Service Performance Data File Mode</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>service_perfdata_file_mode=<mode></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>service_perfdata_file_mode=a</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines how the <a class="link" href="configmain.html#configmain-service_perfdata_file">service performance data file</a> is opened.
Unless the file is a named pipe you'll probably want to use the default mode of append.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>a = Open file in append mode (default)</p>
</li>
<li class="listitem">
<p>w = Open file in write mode</p>
</li>
<li class="listitem">
<p>p = Open in non-blocking read/write mode (useful when writing to pipes)</p>
</li>
</ul></div>
<p><a name="configmain-host_perfdata_file_processing_interval"></a> <span class="bold"><strong>Host Performance Data File Processing
Interval</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>host_perfdata_file_processing_interval=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>host_perfdata_file_processing_interval=0</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to specify the interval (in seconds) at which the <a class="link" href="configmain.html#configmain-host_perfdata_file">host
performance data file</a> is processed using the <a class="link" href="configmain.html#configmain-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="configmain-service_perfdata_file_processing_interval"></a> <span class="bold"><strong>Service Performance Data File
Processing Interval</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>service_perfdata_file_processing_interval=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>service_perfdata_file_processing_interval=0</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to specify the interval (in seconds) at which the <a class="link" href="configmain.html#configmain-service_perfdata_file">service
performance data file</a> is processed using the <a class="link" href="configmain.html#configmain-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="configmain-host_perfdata_file_processing_command"></a> <span class="bold"><strong>Host Performance Data File Processing
Command</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>host_perfdata_file_processing_command=<command></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>host_perfdata_file_processing_command=process-host-perfdata-file</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to specify the command that should be executed to process the <a class="link" href="configmain.html#configmain-host_perfdata_file">host performance data file</a>. The <span class="emphasis"><em>command</em></span> argument is the short name of
a <a class="link" href="objectdefinitions.html#objectdefinitions-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 class="link" href="configmain.html#configmain-host_perfdata_file_processing_interval">host_perfdata_file_processing_interval</a> directive.</p>
<p><a name="configmain-service_perfdata_file_processing_command"></a> <span class="bold"><strong>Service Performance Data File
Processing Command</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>service_perfdata_file_processing_command=<command></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>service_perfdata_file_processing_command=process-service-perfdata-file</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to specify the command that should be executed to process the <a class="link" href="configmain.html#configmain-service_perfdata_file">service performance data file</a>. The <span class="emphasis"><em>command</em></span> argument is the short
name of a <a class="link" href="objectdefinitions.html#objectdefinitions-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 class="link" href="configmain.html#configmain-service_perfdata_file_processing_interval">service_perfdata_file_processing_interval</a> directive.</p>
<p><a name="configmain-check_for_orphaned_services"></a> <span class="bold"><strong>Orphaned Service Check Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>check_for_orphaned_services=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>check_for_orphaned_services=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<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 Icinga 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>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't check for orphaned service checks</p>
</li>
<li class="listitem">
<p>1 = Check for orphaned service checks (default)</p>
</li>
</ul></div>
<p><a name="configmain-check_for_orphaned_hosts"></a> <span class="bold"><strong>Orphaned Host Check Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>check_for_orphaned_hosts=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>check_for_orphaned_hosts=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to enable or disable checks for orphaned hoste checks. Orphaned host 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 host, it is not rescheduled in the event queue. This can cause host 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 host check. If
this option is enabled and Icinga finds that results for a particular host check have not come back, it will log an error message
and reschedule the host check. If you start seeing host checks that never seem to get rescheduled, enable this option and see if you
notice any log messages about orphaned hosts.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't check for orphaned host checks</p>
</li>
<li class="listitem">
<p>1 = Check for orphaned host checks (default)</p>
</li>
</ul></div>
<p><a name="configmain-check_service_freshness"></a> <span class="bold"><strong>Service Freshness Checking Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>check_service_freshness=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>check_service_freshness=0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will periodically check the "freshness" of service checks. Enabling this option
is useful for helping to ensure that <a class="link" href="passivechecks.html" title="5.7. Passive Checks">passive service checks</a> are received in a timely manner. More
information on freshness checking can be found <a class="link" href="freshness.html" title="7.5. Service and Host Freshness Checks">here</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't check service freshness</p>
</li>
<li class="listitem">
<p>1 = Check service freshness (default)</p>
</li>
</ul></div>
<p><a name="configmain-service_freshness_check_interval"></a> <span class="bold"><strong>Service Freshness Check
Interval</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>service_freshness_check_interval=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>service_freshness_check_interval=60</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This setting determines how often (in seconds) Icinga will periodically check the "freshness" of service check results. If
you have disabled service freshness checking (with the <a class="link" href="configmain.html#configmain-check_service_freshness">check_service_freshness</a>
option), this option has no effect. More information on freshness checking can be found <a class="link" href="freshness.html" title="7.5. Service and Host Freshness Checks">here</a>.</p>
<p><a name="configmain-check_host_freshness"></a> <span class="bold"><strong>Host Freshness Checking Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>check_host_freshness=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>check_host_freshness=0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga will periodically check the "freshness" of host checks. Enabling this option is
useful for helping to ensure that <a class="link" href="passivechecks.html" title="5.7. Passive Checks">passive host checks</a> are received in a timely manner. More
information on freshness checking can be found <a class="link" href="freshness.html" title="7.5. Service and Host Freshness Checks">here</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't check host freshness (default)</p>
</li>
<li class="listitem">
<p>1 = Check host freshness</p>
</li>
</ul></div>
<p><a name="configmain-host_freshness_check_interval"></a> <span class="bold"><strong>Host Freshness Check Interval</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>host_freshness_check_interval=<seconds></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>host_freshness_check_interval=60</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This setting determines how often (in seconds) Icinga will periodically check the "freshness" of host check results. If you
have disabled host freshness checking (with the <a class="link" href="configmain.html#configmain-check_host_freshness">check_host_freshness</a> option), this
option has no effect. More information on freshness checking can be found <a class="link" href="freshness.html" title="7.5. Service and Host Freshness Checks">here</a>.</p>
<p><a name="configmain-additional_freshness_latency"></a> <span class="bold"><strong>Additional Freshness Threshold Latency
Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>additional_freshness_latency=<#></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>additional_freshness_latency=15</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines the number of seconds Icinga will add to any host or services freshness threshold it automatically
calculates (e.g. those not specified explicity by the user). More information on freshness checking can be found <a class="link" href="freshness.html" title="7.5. Service and Host Freshness Checks">here</a>.</p>
<p><a name="configmain-p1_file_location"></a><span class="bold"><strong>P1.PL File Location</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody><tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>p1_file=@P1FILELOC@/p1.pl</strong></span></p></td>
</tr></tbody>
</table>
</div>
<p>This value determines where the p1.pl perl script (used by the embedded Perl interpreter) is located. If you didn't compile
Icinga with embedded Perl support, this option has no effect.</p>
<p><a name="configmain-enable_embedded_perl"></a> <span class="bold"><strong>Embedded Perl Interpreter Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>enable_embedded_perl=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>enable_embedded_perl=0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This setting determines whether or not the embedded Perl interpreter is enabled on a program-wide basis. Icinga must be
compiled with support for embedded Perl for this option to have an effect. More information on the embedded Perl interpreter can be found
<a class="link" href="embeddedperl.html" title="7.18. Using The Embedded Perl Interpreter">here</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = disabled (default)</p>
</li>
<li class="listitem">
<p>1 = enabled</p>
</li>
</ul></div>
<p><a name="configmain-use_embedded_perl_implicitly"></a> <span class="bold"><strong>Embedded Perl Implicit Use Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>use_embedded_perl_implicitly=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>use_embedded_perl_implicitly=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This setting determines whether or not the embedded Perl interpreter should be used for Perl plugins/scripts that do not explicitly
enable/disable it. Icinga must be compiled with support for embedded Perl for this option to have an effect. More information on
the embedded Perl interpreter and the effect of this setting can be found <a class="link" href="embeddedperl.html" title="7.18. Using The Embedded Perl Interpreter">here</a>.</p>
<p><a name="configmain-date_format"></a> <span class="bold"><strong>Date Format</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>date_format=<option></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>date_format=us</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to specify what kind of date/time format Icinga should use in the web interface and date/time <a class="link" href="macros.html" title="5.2. Understanding Macros and How They Work">macros</a>. Possible options (along with example output) include:</p>
<div class="informaltable">
<table border="1">
<colgroup>
<col>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p><span class="bold"><strong>Option</strong></span></p></td>
<td><p><span class="bold"><strong>Output Format</strong></span></p></td>
<td><p><span class="bold"><strong>Sample Output</strong></span></p></td>
</tr>
<tr>
<td><p>us</p></td>
<td><p>MM-DD-YYYY HH:MM:SS</p></td>
<td><p>06-30-2002 03:15:00</p></td>
</tr>
<tr>
<td><p>euro</p></td>
<td><p>DD-MM-YYYY HH:MM:SS</p></td>
<td><p>30-06-2002 03:15:00</p></td>
</tr>
<tr>
<td><p>iso8601</p></td>
<td><p>YYYY-MM-DD HH:MM:SS</p></td>
<td><p>2002-06-30 03:15:00</p></td>
</tr>
<tr>
<td><p>strict-iso8601</p></td>
<td><p>YYYY-MM-DDTHH:MM:SS</p></td>
<td><p>2002-06-30T03:15:00</p></td>
</tr>
</tbody>
</table>
</div>
<p><a name="configmain-use_timezone"></a> <span class="bold"><strong>Timezone Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>use_timezone=<tz></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>use_timezone=US/Mountain</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to override the default timezone that this instance of Icinga runs in. Useful if you have multiple
instances of Icinga that need to run from the same server, but have different local times associated with them. If not specified,
Icinga will use the system configured timezone.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>If you use this option to specify a custom timezone, you will also need to alter the Apache configuration directives for the CGIs
to specify the timezone you want. Example:</p>
</td></tr>
</table></div>
<p><Directory "/usr/local/icinga/sbin/"></p>
<p>SetEnv TZ "US/Mountain"</p>
<p>...</p>
<p></Directory></p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>Depending on your OS it might be necessary to add a colon before the timezone to work as expected</p>
<p><code class="literal">use_timezone=:US/Mountain</code></p>
</td></tr>
</table></div>
<p><a name="configmain-illegal_object_name_chars"></a> <span class="bold"><strong>Illegal Object Name Characters</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>illegal_object_name_chars=<chars...></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>illegal_object_name_chars=`~!$%^&*"|'<>?,()=</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p> This option allows you to specify illegal characters that cannot be used in host names, service descriptions, or names
of other object types. Icinga will allow you to use most characters in object definitions, but we 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="configmain-illegal_macro_output_chars"></a> <span class="bold"><strong>Illegal Macro Output Characters</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>illegal_macro_output_chars=<chars...></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>illegal_macro_output_chars=`~$&"|'<></strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option allows you to specify illegal characters that should be stripped from <a class="link" href="macros.html" title="5.2. Understanding Macros and How They Work">macros</a> before being
used in notifications, event handlers, and other commands. This ALSO affects macros used in service or host check commands. You can choose
to not strip out the characters shown in the example above, but we 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><span class="bold"><strong>$HOSTOUTPUT$</strong></span>, <span class="bold"><strong>$HOSTPERFDATA$</strong></span>, <span class="bold"><strong>$HOSTACKAUTHOR$</strong></span>, <span class="bold"><strong>$HOSTACKCOMMENT$</strong></span>, <span class="bold"><strong>$SERVICEOUTPUT$</strong></span>, <span class="bold"><strong>$SERVICEPERFDATA$</strong></span>, <span class="bold"><strong>$SERVICEACKAUTHOR$</strong></span>, and <span class="bold"><strong>$SERVICEACKCOMMENT$</strong></span></p>
<p><a name="configmain-keep_unknown_macros"></a> <span class="bold"><strong>Keep Unknown Marcos Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>keep_unknown_macros=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>keep_unknown_macros=0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option can be used to keep unknown macros within the output, e.g. check_proc -C $foo$ will remain on the commandline. This was
the default in versions older than Icinga 1.8, but now the default is to remove those macros from the output, causing the shell to
interpret $foo and leaving a single $ there. See <a class="link" href="https://dev.icinga.org/issues/2291" target="_top">#2291</a>for further
information. Make sure to escape single dollar signs with another '$', as the docs describe. Other than that, enable this setting to
revert to the old behaviour.</p>
<p><a name="configmain-use_regexp_matching"></a> <span class="bold"><strong>Regular Expression Matching Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>use_regexp_matching=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>use_regexp_matching=0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not various directives in your <a class="link" href="configobject.html" title="3.3. Object Configuration Overview">object definitions</a> will be
processed as regular expressions. More information on how this works can be found <a class="link" href="objecttricks.html" title="7.27. Time-Saving Tricks For Object Definitions">here</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't use regular expression matching (default)</p>
</li>
<li class="listitem">
<p>1 = Use regular expression matching</p>
</li>
</ul></div>
<p><a name="configmain-use_true_regexp_matching"></a> <span class="bold"><strong>True Regular Expression Matching
Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>use_true_regexp_matching=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>use_true_regexp_matching=0</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>If you've enabled regular expression matching of various object directives using the <a class="link" href="configmain.html#configmain-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 they contain
<span class="bold"><strong>*</strong></span>, <span class="bold"><strong>?</strong></span>, <span class="bold"><strong>$</strong></span>, <span class="bold"><strong>+</strong></span>, or <span class="bold"><strong>\. </strong></span>(POSIX ERE). 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 class="link" href="objecttricks.html" title="7.27. Time-Saving Tricks For Object Definitions">here</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't use true regular expression matching (default)</p>
</li>
<li class="listitem">
<p>1 = Use true regular expression matching</p>
</li>
</ul></div>
<p><a name="configmain-admin_email"></a> <span class="bold"><strong>Administrator Email Address</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>admin_email=<email_address></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>admin_email=root@localhost.localdomain</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the email address for the administrator of the local machine (i.e. the one that Icinga is running on). This value can
be used in notification commands by using the <span class="bold"><strong>$ADMINEMAIL$</strong></span> <a class="link" href="macros.html" title="5.2. Understanding Macros and How They Work">macro</a>.</p>
<p><a name="configmain-admin_pager"></a> <span class="bold"><strong>Administrator Pager</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>admin_pager=<pager_number_or_pager_email_gateway></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>admin_pager=pageroot@localhost.localdomain</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This is the pager number (or pager email gateway) for the administrator of the local machine (i.e. the one that Icinga is
running on). The pager number/address can be used in notification commands by using the <span class="bold"><strong>$ADMINPAGER$</strong></span>
<a class="link" href="macros.html" title="5.2. Understanding Macros and How They Work">macro</a>.</p>
<p><a name="configmain-daemon_dumps_core"></a> <span class="bold"><strong>Daemon Core Dump Option</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>daemon_dumps_core=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>daemon_dumps_core=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines whether or not Icinga is allowed to create a core dump when it runs as a daemon. Note that it is generally
considered bad form to allow this, but it may be useful for debugging purposes. Enabling this option doesn't guarantee that a core file
will be produced, but that's just life.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Don't allow core dumps (default)</p>
</li>
<li class="listitem">
<p>1 = Allow core dumps</p>
</li>
</ul></div>
<p><a name="configmain-event_broker_options"></a> <span class="bold"><strong>Event Broker Options</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>event_broker_options=<#></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>event_broker_options=-1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option controls what (if any) data gets sent to the event broker and, in turn, to any loaded event broker modules. This is an
advanced option. When in doubt, either broker nothing (if not using event broker modules) or broker everything (if using event broker
modules). Possible values are shown below.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Broker nothing</p>
</li>
<li class="listitem">
<p>-1 = Broker everything</p>
</li>
<li class="listitem">
<p># = See BROKER_* definitions in source code (include/broker.h) for other values that can be OR'ed together</p>
</li>
</ul></div>
<p><a name="configmain-broker_module"></a> <span class="bold"><strong>Event Broker Modules</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>broker_module=<modulepath> [moduleargs]</strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>broker_module=/usr/local/icinga/lib/idomod.so \
cfg_file=/usr/local/icinga/etc/idomod.cfg</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This directive is used to specify an event broker module that should by loaded by Icinga at startup. Use multiple directives
if you want to load more than one module. Arguments that should be passed to the module at startup are separated from the module path by a
space.</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>This option is deprecated starting with Icinga 1.13 because you must use the <a class="link" href="objectdefinitions.html#objectdefinitions-module">module object definition</a> instead.</p>
</td></tr>
</table></div>
<p><a name="configmain-debug_file"></a> <span class="bold"><strong>Debug File</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>debug_file=<file_name></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>debug_file=/usr/local/icinga/var/icinga.debug</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines where Icinga should write debugging information. What (if any) information is written is determined by
the <a class="link" href="configmain.html#configmain-debug_level">debug_level</a> and <a class="link" href="configmain.html#configmain-debug_verbosity">debug_verbosity</a>
options. You can have Icinga automaticaly rotate the debug file when it reaches a certain size by using the <a class="link" href="configmain.html#configmain-max_debug_file_size">max_debug_file_size</a> option.</p>
<p><a name="configmain-debug_level"></a> <span class="bold"><strong>Debug Level</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>debug_level=<#></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>debug_level=24</strong></span></font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines what type of information Icinga should write to the <a class="link" href="configmain.html#configmain-debug_file">debug_file</a>. This value is a logical OR of the values below.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>-1 = Log everything</p>
</li>
<li class="listitem">
<p>0 = Log nothing (default)</p>
</li>
<li class="listitem">
<p>1 = Function enter/exit information</p>
</li>
<li class="listitem">
<p>2 = Config information</p>
</li>
<li class="listitem">
<p>4 = Process information</p>
</li>
<li class="listitem">
<p>8 = Scheduled event information</p>
</li>
<li class="listitem">
<p>16 = Host/service check information</p>
</li>
<li class="listitem">
<p>32 = Notification information</p>
</li>
<li class="listitem">
<p>64 = Event broker information</p>
</li>
<li class="listitem">
<p>128 = External commands</p>
</li>
<li class="listitem">
<p>256 = Commands</p>
</li>
<li class="listitem">
<p>512 = Scheduled downtime</p>
</li>
<li class="listitem">
<p>1024 = Comments</p>
</li>
<li class="listitem">
<p>2048 = Macros</p>
</li>
</ul></div>
<p><a name="configmain-debug_verbosity"></a> <span class="bold"><strong>Debug Verbosity</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>debug_verbosity=<#></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>debug_verbosity=1</strong></span></font></span> </p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines how much debugging information Icinga should write to the <a class="link" href="configmain.html#configmain-debug_file">debug_file</a>.</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = Basic information</p>
</li>
<li class="listitem">
<p>1 = More detailed information (default)</p>
</li>
<li class="listitem">
<p>2 = Highly detailed information</p>
</li>
</ul></div>
<p><a name="configmain-max_debug_file_size"></a> <span class="bold"><strong>Maximum Debug File Size</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>max_debug_file_size=<#></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>max_debug_file_size=1000000</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option determines the maximum size (in bytes) of the <a class="link" href="configmain.html#configmain-debug_file">debug file</a>. If the file grows
larger than this size, it will be renamed with a .old extension. If a file already exists with a .old extension it will automatically be
deleted. This helps ensure your disk space usage doesn't get out of control when debugging Icinga.</p>
<p><a name="configmain-event_profiling"></a> <span class="bold"><strong>Event Profiling</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>event_profiling_enabled=<0/1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>event_profiling_enabled=1</strong></span></font></span>
</p></td>
</tr>
</tbody>
</table>
</div>
<p>This option enables or disables event profiling for stats of event counts and time taken for events. This option can't be used on
Solaris with gcc3.</p>
<p><a name="configmain-allow_empty_hostgroup_assignment"></a> <span class="bold"><strong>Allow Empty Hostgroup
Assignment</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p><span class="bold"><strong>allow_empty_hostgroup_assignment=<0|1></strong></span></p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p><span class="color"><font color="red"><span class="bold"><strong>allow_empty_hostgroup_assignment=1</strong></span>
</font></span></p></td>
</tr>
</tbody>
</table>
</div>
<p>This boolean option determines whether services, service dependencies, or host dependencies assigned to empty host groups (host
groups with no host members) will cause Icinga to exit with error on startup (or during a configuration check) or not. The default
behaviour if the option is not present (or set to "0") in the main configuration file is for Icinga to exit with error if any of
these objects are associated with host groups whose hostgroup definitions have no host_members associated with them.</p>
<p>Enabling this option can be useful when:</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>Configuration files or pre-cached object files are distributed across many Icinga pollers.</p>
</li>
<li class="listitem">
<p>Automation is used to generate an Icinga configuration file tree.</p>
</li>
<li class="listitem">
<p>There is one set of services, service dependencies, or host dependencies maintained by administrators for which users may add
hosts through host group membership for convenience (e.g. a suite of checks associated with a remote monitoring agent) but for which
there is no guarantee that users will use the services associated with the host group or that the hosts will exists (e.g. a remote
agent that is being deprecated over time or hosts that are being decommissioned).</p>
</li>
</ul></div>
<p><a name="configmain-process_empty_results"></a> <span class="bold"><strong>Process empty performance results</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td>
<p>
<span class="bold"><strong>host_perfdata_process_empty_results=<0|1></strong></span>
</p> <p>
<span class="bold"><strong>service_perfdata_process_empty_results=<0|1></strong></span>
</p>
</td>
</tr>
<tr>
<td><p>Example:</p></td>
<td>
<p>
<span class="color"><font color="red">
<span class="bold"><strong>host_perfdata_process_empty_results=1</strong></span>
</font></span>
</p> <p>
<span class="color"><font color="red">
<span class="bold"><strong>service_perfdata_process_empty_results=1</strong></span>
</font></span>
</p>
</td>
</tr>
</tbody>
</table>
</div>
<p>These options determine whether the core will process empty perfdata results or not. This is needed for distributed monitoring, and
intentionally turned on by default. If you don't require empty perfdata - saving some cpu cycles on unwanted macro calculation - you can
turn that off. Be careful!</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem">
<p>0 = disable</p>
</li>
<li class="listitem">
<p>1 = enable</p>
</li>
</ul></div>
<p><a name="configmain-max_check_result_list_items"></a><span class="bold"><strong>Limit number of items in check result
list</strong></span></p>
<div class="informaltable">
<table border="0">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td><p>Format:</p></td>
<td><p> <span class="bold"><strong>max_check_result_list_items=<n></strong></span> </p></td>
</tr>
<tr>
<td><p>Example:</p></td>
<td><p> <span class="color"><font color="red"> <span class="bold"><strong>max_check_result_list_items=1024</strong></span>
</font></span> </p></td>
</tr>
</tbody>
</table>
</div>
<p>This <span class="bold"><strong>experimental</strong></span> option allows you to set the max number of items the checkresult reaper will put
onto the checkresult list for further processing by the core. If there are too many, the reaping will be terminated early, allowing the
core to process the results sooner. On larger setups, that list might grow too much, and decrease performance on processing. You might
experiment with that value, the inner core default is set to 0, disabling that feature. Values: 0 = Disable max check result list items
number = set max check result list items</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top">
<p>These options are available starting with Icinga 1.8</p>
</td></tr>
</table></div>
<a class="indexterm" name="idm214401250448"></a>
<a class="indexterm" name="idm214401249280"></a>
<a class="indexterm" name="idm214401247760"></a>
<a class="indexterm" name="idm214401246000"></a>
<a class="indexterm" name="idm214401244512"></a>
<a class="indexterm" name="idm214401242912"></a>
<a class="indexterm" name="idm214401241280"></a>
<a class="indexterm" name="idm214401239648"></a>
<a class="indexterm" name="idm214401237888"></a>
<a class="indexterm" name="idm214401236368"></a>
<a class="indexterm" name="idm214401234608"></a>
<a class="indexterm" name="idm214401233120"></a>
<a class="indexterm" name="idm214401231392"></a>
<a class="indexterm" name="idm214401229872"></a>
<a class="indexterm" name="idm214401228176"></a>
<a class="indexterm" name="idm214401226656"></a>
<a class="indexterm" name="idm214401289984"></a>
<a class="indexterm" name="idm214401223728"></a>
<a class="indexterm" name="idm214401222336"></a>
<a class="indexterm" name="idm214401220592"></a>
<a class="indexterm" name="idm214401218992"></a>
<a class="indexterm" name="idm214401217360"></a>
<a class="indexterm" name="idm214401215728"></a>
<a class="indexterm" name="idm214401214096"></a>
<a class="indexterm" name="idm214401212448"></a>
<a class="indexterm" name="idm214401210688"></a>
<a class="indexterm" name="idm214401209136"></a>
<a class="indexterm" name="idm214401207552"></a>
<a class="indexterm" name="idm214401205920"></a>
<a class="indexterm" name="idm214401204272"></a>
<a class="indexterm" name="idm214401202640"></a>
<a class="indexterm" name="idm214401200976"></a>
<a class="indexterm" name="idm214401199216"></a>
<a class="indexterm" name="idm214401197648"></a>
<a class="indexterm" name="idm214401195952"></a>
<a class="indexterm" name="idm214401194256"></a>
<a class="indexterm" name="idm214401192480"></a>
<a class="indexterm" name="idm214401190928"></a>
<a class="indexterm" name="idm214401189200"></a>
<a class="indexterm" name="idm214401187536"></a>
<a class="indexterm" name="idm214401185872"></a>
<a class="indexterm" name="idm214401184192"></a>
<a class="indexterm" name="idm214401182528"></a>
<a class="indexterm" name="idm214401180880"></a>
<a class="indexterm" name="idm214401179232"></a>
<a class="indexterm" name="idm214401177584"></a>
<a class="indexterm" name="idm214401175936"></a>
<a class="indexterm" name="idm214401174288"></a>
<a class="indexterm" name="idm214401172640"></a>
<a class="indexterm" name="idm214401170992"></a>
<a class="indexterm" name="idm214401169344"></a>
<a class="indexterm" name="idm214401167664"></a>
<a class="indexterm" name="idm214401165904"></a>
<a class="indexterm" name="idm214401164352"></a>
<a class="indexterm" name="idm214401162656"></a>
<a class="indexterm" name="idm214401160960"></a>
<a class="indexterm" name="idm214401159296"></a>
<a class="indexterm" name="idm214401157600"></a>
<a class="indexterm" name="idm214401155936"></a>
<a class="indexterm" name="idm214401154240"></a>
<a class="indexterm" name="idm214401152544"></a>
<a class="indexterm" name="idm214401150784"></a>
<a class="indexterm" name="idm214401149168"></a>
<a class="indexterm" name="idm214401147552"></a>
<a class="indexterm" name="idm214401145872"></a>
<a class="indexterm" name="idm214401144160"></a>
<a class="indexterm" name="idm214401142592"></a>
<a class="indexterm" name="idm214401140864"></a>
<a class="indexterm" name="idm214401139200"></a>
<a class="indexterm" name="idm214401137664"></a>
<a class="indexterm" name="idm214401136032"></a>
<a class="indexterm" name="idm214401134368"></a>
<a class="indexterm" name="idm214401132704"></a>
<a class="indexterm" name="idm214401130912"></a>
<a class="indexterm" name="idm214401129280"></a>
<a class="indexterm" name="idm214401127568"></a>
<a class="indexterm" name="idm214401125824"></a>
<a class="indexterm" name="idm214401124240"></a>
<a class="indexterm" name="idm214401122624"></a>
<a class="indexterm" name="idm214401120864"></a>
<a class="indexterm" name="idm214401119280"></a>
<a class="indexterm" name="idm214401117648"></a>
<a class="indexterm" name="idm214401115936"></a>
<a class="indexterm" name="idm214401114320"></a>
<a class="indexterm" name="idm214401112688"></a>
<a class="indexterm" name="idm214401111056"></a>
<a class="indexterm" name="idm214401109392"></a>
<a class="indexterm" name="idm214401107760"></a>
<a class="indexterm" name="idm214401106096"></a>
<a class="indexterm" name="idm214401104432"></a>
<a class="indexterm" name="idm214401102704"></a>
<a class="indexterm" name="idm214401101072"></a>
<a class="indexterm" name="idm214401099488"></a>
<a class="indexterm" name="idm214401097856"></a>
<a class="indexterm" name="idm214401096224"></a>
<a class="indexterm" name="idm214401094464"></a>
<a class="indexterm" name="idm214401092976"></a>
<a class="indexterm" name="idm214401091248"></a>
<a class="indexterm" name="idm214401089680"></a>
<a class="indexterm" name="idm214401088128"></a>
<a class="indexterm" name="idm214401086480"></a>
<a class="indexterm" name="idm214401084848"></a>
<a class="indexterm" name="idm214401083200"></a>
<a class="indexterm" name="idm214401081520"></a>
<a class="indexterm" name="idm214401079872"></a>
<a class="indexterm" name="idm214401078192"></a>
<a class="indexterm" name="idm214401076544"></a>
<a class="indexterm" name="idm214401074896"></a>
<a class="indexterm" name="idm214401073200"></a>
<a class="indexterm" name="idm214401071536"></a>
<a class="indexterm" name="idm214401069872"></a>
<a class="indexterm" name="idm214401068112"></a>
<a class="indexterm" name="idm214401066560"></a>
<a class="indexterm" name="idm214401064864"></a>
<a class="indexterm" name="idm214401063168"></a>
<a class="indexterm" name="idm214401061424"></a>
<a class="indexterm" name="idm214401059776"></a>
<a class="indexterm" name="idm214401058096"></a>
<a class="indexterm" name="idm214401056336"></a>
<a class="indexterm" name="idm214401054768"></a>
<a class="indexterm" name="idm214401053136"></a>
<a class="indexterm" name="idm214401051456"></a>
<a class="indexterm" name="idm214401049792"></a>
<a class="indexterm" name="idm214401048144"></a>
<a class="indexterm" name="idm214401046496"></a>
<a class="indexterm" name="idm214401044832"></a>
<a class="indexterm" name="idm214401043072"></a>
<a class="indexterm" name="idm214401041584"></a>
<a class="indexterm" name="idm214401039936"></a>
<a class="indexterm" name="idm214401038288"></a>
<a class="indexterm" name="idm214401036656"></a>
<a class="indexterm" name="idm214401035008"></a>
<a class="indexterm" name="idm214401033344"></a>
<a class="indexterm" name="idm214401031712"></a>
<a class="indexterm" name="idm214401030080"></a>
<a class="indexterm" name="idm214401028448"></a>
<a class="indexterm" name="idm214401026688"></a>
<a class="indexterm" name="idm214401025168"></a>
<a class="indexterm" name="idm214401023584"></a>
<a class="indexterm" name="idm214401021952"></a>
<a class="indexterm" name="idm214401020320"></a>
<a class="indexterm" name="idm214401018640"></a>
<a class="indexterm" name="idm214401016848"></a>
<a class="indexterm" name="idm214401015168"></a>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="config.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href="ch03.html">Up</a></td>
<td width="40%" align="right"> <a accesskey="n" href="configobject.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">3.1. Configuration Overview </td>
<td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td>
<td width="40%" align="right" valign="top"> 3.3. Object Configuration Overview</td>
</tr>
</table>
</div>
<P class="copyright">© 1999-2009 Ethan Galstad, 2009-2015 Icinga Development Team, http://www.icinga.org</P>
</body>
</html>
|
