· 9 years ago · Aug 05, 2017, 09:50 PM
1#####################################################################
2# IDO2DB DAEMON CONFIG FILE
3#####################################################################
4
5
6
7# LOCK FILE
8# This is the lockfile that IDO2DB will use to store its PID number
9# in when it is running in daemon mode.
10
11lock_file=/usr/local/icinga/var/ido2db.lock
12
13
14
15# USER/GROUP PRIVILIGES
16# These options determine the user/group that the daemon should run as.
17# You can specify a number (uid/gid) or a name for either option.
18
19ido2db_user=icinga
20ido2db_group=icinga
21
22
23
24# SOCKET TYPE
25# This option determines what type of socket the daemon will create
26# an accept connections from.
27# Value:
28# unix = Unix domain socket (default)
29# tcp = TCP socket
30
31#socket_type=unix
32socket_type=tcp
33
34
35
36# SOCKET NAME
37# This option determines the name and path of the UNIX domain
38# socket that the daemon will create and accept connections from.
39# This option is only valid if the socket type specified above
40# is "unix".
41
42socket_name=/usr/local/icinga/var/ido.sock
43
44
45
46# TCP PORT
47# This option determines what port the daemon will listen for
48# connections on. This option is only vlaid if the socket type
49# specified above is "tcp".
50
51tcp_port=5668
52
53
54
55# ENCRYPTION
56# This option determines if the ido2db daemon will accept SSL to encrypt the
57# network traffic between module and ido2db daemon.
58# Both sides have to enable this feature which depends on SSL Libraries
59# like openssl or kerberos
60# This option is only valid if the output type
61# option specified above is "tcpsocket".
62#
63# A value of '1' will enable this feature
64
65use_ssl=1
66
67
68
69# DATABASE SERVER TYPE
70# This option determines what type of DB server the daemon should
71# connect to.
72# Values:
73# mysql = MySQL
74# pgsql = PostgreSQL
75# db2 = DB2
76# firebird = Firebird
77# freetds = FreeTDS
78# ingres = Ingres
79# msql = MSSQL
80# oracle = Oracle
81# sqlite = SQLite
82# sqlite3 = SQLite3
83# Currently supported:
84# libdbi: mysql, pgsql
85# ocilib: oracle
86
87
88db_servertype=mysql
89
90
91
92# DATABASE HOST
93# This option specifies what host the DB server is running on.
94# Note: Oracle will ignore this setting
95
96db_host=localhost
97
98
99
100# DATABASE PORT
101# This option specifies the port that the DB server is running on.
102# Values:
103# 3306 = Default MySQL port
104# 5432 = Default PostgreSQL port
105# 1521 = Default Oracle port
106
107db_port=3306
108
109
110
111# DATABASE NAME
112# This option specifies the name of the database that should be used.
113# Note: Oracle needs //DBSERVER/DBNAME
114
115db_name=icinga
116
117
118
119# DATABASE TABLE PREFIX
120# Determines the prefix (if any) that should be prepended to table names.
121# If you modify the table prefix, you'll need to modify the SQL script for
122# creating the database!
123# Note: Oracle will ignore this prefix since the tablename length will exceed 30 characters.
124
125db_prefix=icinga_
126
127
128
129# DATABASE USERNAME/PASSWORD
130# This is the username/password that will be used to authenticate to the DB.
131# The user needs at least SELECT, INSERT, UPDATE, and DELETE privileges on
132# the database.
133
134db_user=icinga
135db_pass=icinga
136
137
138
139## TABLE TRIMMING OPTIONS
140# Several database tables containing Icinga event data can become quite large
141# over time. Most admins will want to trim these tables and keep only a
142# certain amount of data in them. The options below are used to specify the
143# age (in MINUTES) that data should be allowd to remain in various tables
144# before it is deleted. Using a value of zero (0) for any value means that
145# that particular table should NOT be automatically trimmed.
146#
147# Remember: There are no optimized settings, it depends on your rdbm install,
148# number/checkinterval of host/service-checks and your desired time of data
149# savings - historical vs live-data. Please keep in mind that low delete
150# intervals may interfere with insert/update data from Icinga.
151
152# ***DEFAULT***
153
154# Keep timed events for 1 hour
155max_timedevents_age=60
156
157# Keep system commands for 1 day
158max_systemcommands_age=1440
159
160# Keep service checks for 1 day
161max_servicechecks_age=1440
162
163# Keep host checks for 1 day
164max_hostchecks_age=1440
165
166# Keep event handlers for 1 week
167max_eventhandlers_age=10080
168
169# Keep external commands for 1 week
170max_externalcommands_age=10080
171
172# Keep logentries for 31 days
173max_logentries_age=44640
174
175# Keep acknowledgements for 31 days
176max_acknowledgements_age=44640
177
178
179## CLEAN REALTIME TABLES AT CORE STARTUP
180# If you don't want to clean all those tables, set this option to 0.
181# This can be useful if the deletes slow down the normal data
182# processing.
183# Values: 0 - don't clean
184# 1 - clean (default)
185
186clean_realtime_tables_on_core_startup=1
187
188
189## CLEAN CONFIG TABLES AT CORE STARTUP
190# If you don't want to clean all those tables, set this option to 0.
191# This can be useful if the deletes slow down the normal data
192# processing.
193# Furthermore if you need to keep e.g. the state of customvariables
194# or any other tables not directly linked to the objects table.
195# Values: 0 - don't clean
196# 1 - clean (default)
197
198clean_config_tables_on_core_startup=1
199
200
201# ***EXPERIMENTAL*** DB TRIMMING INTERVAL
202# ido2db default db trimming interval is set to 60 SECONDS.
203# Some environments will require higher or lower values. This setting is
204# highly experimental!!!
205# Modify at your own risk to set the interval DB trimming interval
206# to an appropriate value. If left blank, it defaults to 60 seconds.
207
208trim_db_interval=60
209
210
211# DB TRIMMING THREAD DELAY ON STARTUP
212# ido2db spawns a thread for parallel db trimming. This option can be
213# modified to extend/minimize the initial wait delay at startup.
214# Default is set to 60 seconds in order to allow startup routines.
215
216housekeeping_thread_startup_delay=60
217
218
219
220# DEBUG LEVEL
221# This option determines how much (if any) debugging information will
222# be written to the debug file. OR values together to log multiple
223# types of information.
224# Values: -1 = Everything
225# 0 = Nothing
226# 1 = Process info
227# 2 = SQL queries
228
229debug_level=0
230
231
232
233# DEBUG VERBOSITY
234# This option determines how verbose the debug log out will be.
235# Values: 0 = Brief output
236# 1 = More detailed
237# 2 = Very detailed
238
239debug_verbosity=1
240
241
242
243# DEBUG FILE
244# This option determines where the daemon should write debugging information.
245
246debug_file=/usr/local/icinga/var/ido2db.debug
247
248
249
250# MAX DEBUG FILE SIZE
251# This option determines the maximum size (in bytes) of the debug file. If
252# the file grows larger than this size, it will be renamed with a .old
253# extension. If a file already exists with a .old extension it will
254# automatically be deleted. This helps ensure your disk space usage doesn't
255# get out of control when debugging.
256
257max_debug_file_size=1000000
258
259
260
261# OCI ERRORS TO SYSLOG
262# ido2db registers an error handler in ocilib which spits all msg
263# into debug and syslog by default. Setting this option to 0,
264# syslog output will be disabled, only debug log will be used (if
265# appropriate debug_level is set).
266
267oci_errors_to_syslog=1