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
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Example Configurations</title>
<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.0.2 Documentation">
<link rel="up" href="ch11.html" title="Chapter 11. IDOUtils">
<link rel="prev" href="db_components.html" title="Components">
<link rel="next" href="db_model.html" title="IDOUtils Database Model">
</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">Example Configurations</th></tr>
<tr>
<td width="20%" align="left">
<a accesskey="p" href="db_components.html">Prev</a> </td>
<th width="60%" align="center">Chapter 11. IDOUtils</th>
<td width="20%" align="right"> <a accesskey="n" href="db_model.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
<div class="section" title="Example Configurations">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="db_example-configs"></a>Example Configurations</h2></div></div></div>
<div class="section" title="Single Server, Single Instance Setup">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2011546"></a>Single Server, Single Instance Setup</h3></div></div></div>
<p>The easiest configuration occurs when you have a single Icinga instance running on your network. In this case, installing
and configuring the various components of the IDOUtils addon is fairly straightforward.</p>
<p>The following diagram illustrates how the various components can fit together in a single server, single Icinga instance
setup...</p>
<div class="figure">
<a name="id2011564"></a><p class="title"><b>Figure 11.11. Single Server, Single Instance Setup</b></p>
<div class="figure-contents">
<div class="mediaobject"><img src="../images/fig11.png" alt="Single Server, Single Instance Setup"></div>
</div>
</div>
<br class="figure-break">
<p>Here's a description of what's happening at each point in the diagram:</p>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
<p>The IDOMOD module is configured with an instance name of "default" since there is only one instance of Icinga that is
running on the network.</p>
</li>
<li class="listitem">
<p>While the Icinga daemon is running and performing its usual business of monitoring the network, the IDOMOD module is
sending configuration data and event information to the TCP or Unix domain socket that was created by the IDO2DB daemon.</p>
</li>
<li class="listitem">
<p>The IDO2DB daemon reads data that is coming into the socket from the IDOMOD module.</p>
</li>
<li class="listitem">
<p>The IDO2DB daemon processes and transforms data that has been received from the IDOMOD module.</p>
</li>
<li class="listitem">
<p>The processed data is stored in a database for later retrieval and processing.</p>
</li>
</ol></div>
<p>This example assumes that:</p>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
<p>Icinga is configured to load the IDOMOD module at startup.</p>
</li>
<li class="listitem">
<p>The IDO2DB daemon (which is a separate process from the Icinga daemon) is running.</p>
</li>
</ol></div>
</div>
<div class="section" title="Single Server, Multiple Instance Setup">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2011651"></a>Single Server, Multiple Instance Setup</h3></div></div></div>
<p>Another simple configuration can be used when you have multiple Icinga instances running on a single server. Installing and
configuring the various components of the IDOUtils addon is similiar as to what was shown in the previous example.</p>
<p>The following diagram illustrates how the various components can fit together in a single server, multiple Icinga instance
setup...</p>
<div class="figure">
<a name="id2011674"></a><p class="title"><b>Figure 11.12. Single Server, Multiple Instance Setup</b></p>
<div class="figure-contents">
<div class="mediaobject"><img src="../images/fig12.png" alt="Single Server, Multiple Instance Setup"></div>
</div>
</div>
<br class="figure-break">
<p>You'll notice that the diagram above is similiar to the one for the single-server, single instance configuration. The main
difference is that there are now three (3) different Icinga daemons instead of just one.</p>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
<p>Each Icinga daemon loads the IDOMOD module at startup with a unique instance name. In this example the instances are
simply named "Icinga1", "Icinga2" and "Icinga3".</p>
</li>
<li class="listitem">
<p>Each IDOMOD module sends configuration data and event information for its specific instance of the Icinga daemon to the
TCP or Unix domain socket that was created by the IDO2DB daemon.</p>
</li>
<li class="listitem">
<p>The IDO2DB daemon reads data that is coming into the socket from the three IDOMOD modules.</p>
</li>
<li class="listitem">
<p>The IDO2DB daemon processes and transforms data that has been received from the IDOMOD modules.</p>
</li>
<li class="listitem">
<p>The processed data is stored in a database for later retrieval and processing. Data from each instance of Icinga is
kept separate (using the instance names as unique identifiers) in the database.</p>
</li>
</ol></div>
</div>
<div class="section" title="Single Server, Single Instance Log File Import">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2011746"></a>Single Server, Single Instance Log File Import</h3></div></div></div>
<p>There are two reasons you'll probably want to import your Icinga log files into the same database that Icinga
configuration and event data is stored in:</p>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
<p>Historical log file data isn't imported into the database by default and having a record of events that occurred before you
implemented the IDOUtils addon is probably desireable.</p>
</li>
<li class="listitem">
<p>The IDOMOD module is not able to process realtime log entries from the time right after the Icinga daemon starts to the
time that the IDOMOD module is loaded by the Icinga daemon. This "blackout period" is unavoidable and causing log entries
such as "Icinga 1.0 starting..." to be missed by the IDOMOD module. Thus, importing day-old Icinga log files on a
daily basis (via a cron job) is recommended.</p>
</li>
</ol></div>
<div class="figure">
<a name="id2011775"></a><p class="title"><b>Figure 11.13. Single Server, Single Instance Log File Import</b></p>
<div class="figure-contents">
<div class="mediaobject"><img src="../images/fig13.png" alt="Single Server, Single Instance Log File Import"></div>
</div>
</div>
<br class="figure-break">
<p>Here's a description of what's happening at each point in the diagram:</p>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
<p>Historical Icinga log files are read by the LOG2IDO utility.</p>
</li>
<li class="listitem">
<p>The LOG2IDO utility processes the contents of the log files and tags them with an instance name of "default". This instance
name must match the same instance name used by the IDOMOD module in the Icinga daemon.</p>
</li>
<li class="listitem">
<p>Historical log file data is sent to the TCP or Unix domain socket in a format that the IDO2DB daemon can understand.</p>
</li>
<li class="listitem">
<p>The IDO2DB daemon reads the log file data from the Unix domain socket.</p>
</li>
<li class="listitem">
<p>The IDO2DB daemon processes the log file data.</p>
</li>
<li class="listitem">
<p>Historical log file data is stored in a database for later retrieval and processing. The IDO2DB daemon will perform some
checks to make sure it doesn't re-import duplicate historical log entries, so running the LOG2IDO utility on the same historical log
file multiple times shouldn't have any negative side effects.</p>
</li>
</ol></div>
<p>That's it! Pretty simple.</p>
</div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="db_components.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href="ch11.html">Up</a></td>
<td width="40%" align="right"> <a accesskey="n" href="db_model.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Components </td>
<td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td>
<td width="40%" align="right" valign="top"> IDOUtils Database Model</td>
</tr>
</table>
</div>
<P class="copyright">© 2009-2010 Icinga Development Team, http://www.icinga.org</P>
</body>
</html>
|
