1#####################################################################
2# NDO2DB DAEMON CONFIG FILE
3#
4# Last Modified: 01-02-2009
5#####################################################################
6
7
8
9# LOCK FILE
10# This is the lockfile that NDO2DB will use to store its PID number
11# in when it is running in daemon mode.
12
13lock_file=@localstatedir@/ndo2db.pid
14
15
16
17# USER/GROUP PRIVILEGES
18# These options determine the user/group that the daemon should run as.
19# You can specify a number (uid/gid) or a name for either option.
20
21ndo2db_user=@ndo2db_user@
22ndo2db_group=@ndo2db_group@
23
24
25
26# SOCKET TYPE
27# This option determines what type of socket the daemon will create
28# an accept connections from.
29# Value:
30#   unix = Unix domain socket (default)
31#   tcp  = TCP socket
32
33socket_type=unix
34#socket_type=tcp
35
36
37
38# SOCKET NAME
39# This option determines the name and path of the UNIX domain
40# socket that the daemon will create and accept connections from.
41# This option is only valid if the socket type specified above
42# is "unix".
43
44socket_name=@localstatedir@/ndo.sock
45
46
47
48# TCP PORT
49# This option determines what port the daemon will listen for
50# connections on.  This option is only vlaid if the socket type
51# specified above is "tcp".
52
53tcp_port=@ndo2db_port@
54
55
56
57# ENCRYPTION
58# This option determines if the ndo2db daemon will accept SSL to encrypt the
59# network traffic between module and ndo2db daemon.
60# Both sides have to enable this feature which depends on SSL Libraries
61# like openssl or kerberos
62# This option is only valid if the output type
63# option specified above is "tcpsocket".
64#
65# A value of '1' will enable this feature
66
67use_ssl=0
68
69
70
71# DATABASE SERVER TYPE
72# This option determines what type of DB server the daemon should connect to.
73# Values:
74#   mysql = MySQL
75
76db_servertype=mysql
77
78
79
80# DATABASE HOST
81# This option specifies what host the DB server is running on.
82
83db_host=localhost
84
85
86
87# DATABASE PORT
88# This option specifies the port that the DB server is running on.
89# Values:
90#  3306 = Default MySQL port
91
92db_port=3306
93
94
95
96# DATABASE SOCKET
97# This option specifies the path to the socket to use for local DB connections.
98#
99# MySQL's default location is /tmp/mysql.sock, but /var/lib/mysql/mysql.sock
100# is common for RPM distributions, and /var/run/mysqld/mysqld.sock is seen on
101# Ubuntu...
102#
103# You normally do not need to set this option unless you experience connection
104# problems with messages in NDO2DB's log like:
105#   "Can't connect to local MySQL server through socket ..."
106
107#db_socket=/var/lib/mysql/mysql.sock
108
109
110
111# DATABASE NAME
112# This option specifies the name of the database that should be used.
113
114db_name=nagios
115
116
117
118# DATABASE TABLE PREFIX
119# Determines the prefix (if any) that should be prepended to table names.
120# If you modify the table prefix, you'll need to modify the SQL script for
121# creating the database!
122
123db_prefix=nagios_
124
125
126
127# DATABASE USERNAME/PASSWORD
128# This is the username/password that will be used to authenticate to the DB.
129# The user needs at least SELECT, INSERT, UPDATE, and DELETE privileges on
130# the database.
131
132db_user=ndouser
133db_pass=ndopassword
134
135
136
137## TABLE TRIMMING OPTIONS
138# Several database tables containing Nagios event data can become quite large
139# over time.  Most admins will want to trim these tables and keep only a
140# certain amount of data in them.  The options below are used to specify the
141# age (in MINUTES) that data should be allowd to remain in various tables
142# before it is deleted.  Using a value of zero (0) for any value means that
143# that particular table should NOT be automatically trimmed.
144
145# Keep timed events for 24 hours
146max_timedevents_age=1440
147
148# Keep system commands for 1 week
149max_systemcommands_age=10080
150
151# Keep service checks for 1 week
152max_servicechecks_age=10080
153
154# Keep host checks for 1 week
155max_hostchecks_age=10080
156
157# Keep event handlers for 31 days
158max_eventhandlers_age=44640
159
160# Keep external commands for 31 days
161max_externalcommands_age=44640
162
163# Keep notifications for 31 days
164max_notifications_age=44640
165
166# Keep contactnotifications for 31 days
167max_contactnotifications_age=44640
168
169# Keep contactnotificationmethods for 31 days
170max_contactnotificationmethods_age=44640
171
172# Keep logentries for 90 days
173max_logentries_age=129600
174
175# Keep acknowledgements for 31 days
176max_acknowledgements_age=44640
177
178
179
180# DEBUG LEVEL
181# This option determines how much (if any) debugging information will
182# be written to the debug file.  OR values together to log multiple
183# types of information.
184# Values: -1 = Everything
185#          0 = Nothing
186#          1 = Process info
187#	   2 = SQL queries
188
189debug_level=0
190
191
192
193# DEBUG VERBOSITY
194# This option determines how verbose the debug log out will be.
195# Values: 0 = Brief output
196#         1 = More detailed
197#         2 = Very detailed
198
199debug_verbosity=1
200
201
202
203# DEBUG FILE
204# This option determines where the daemon should write debugging information.
205
206debug_file=@localstatedir@/ndo2db.debug
207
208
209
210# MAX DEBUG FILE SIZE
211# This option determines the maximum size (in bytes) of the debug file.  If
212# the file grows larger than this size, it will be renamed with a .old
213# extension.  If a file already exists with a .old extension it will
214# automatically be deleted.  This helps ensure your disk space usage doesn't
215# get out of control when debugging.
216
217max_debug_file_size=1000000
218
219
220# MAX OUTPUT BUFFER SIZE
221# This option determines the maximum size (in bytes) of the output buffer.
222# NDO2DB will start truncating characters after this value.
223# If you have very large long output and you're not seeing it all in the database,
224# try increasing this number.
225# IMPORTANT NOTE: The 'long_output' fields in the database are set to TEXT fields, and the maximum
226# size of a TEXT field is 64KB, so if you really want to make use of this field, you'll need to set
227# the long_output fields to MEDIUMTEXT OR LONGTEXT.
228# the long_output column exists in the following tables:
229#  _eventhandlers, _hostchecks, _hoststatus, _notifications, _servicechecks, _servicestatus, _statehistory, _systemcommands
230# An example sql alter statement might look like this:
231# ALTER TABLE nagios_hoststatus MODIFY COLUMN long_output LONGTEXT NOT NULL DEFAULT '';
232max_output_buffer_size=65536
233