forked from elastic/built-docs
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathconfiguring-logstash.html
431 lines (410 loc) · 22 KB
/
configuring-logstash.html
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
<!DOCTYPE html>
<html lang="en-us">
<head>
<meta charset="UTF-8">
<title>Configuring Monitoring for Logstash Nodes | Logstash Reference [6.8] | Elastic</title>
<meta class="elastic" name="content" content="Configuring Monitoring for Logstash Nodes | Logstash Reference [6.8]">
<link rel="home" href="index.html" title="Logstash Reference [6.8]"/>
<link rel="up" href="configuration.html" title="Configuring Logstash"/>
<link rel="prev" href="configuring-centralized-pipelines.html" title="Configuring Centralized Pipeline Management"/>
<link rel="next" href="ls-security.html" title="Configuring Security in Logstash"/>
<meta class="elastic" name="product_version" content="6.8"/>
<meta class="elastic" name="product_name" content="Logstash"/>
<meta class="elastic" name="website_area" content="documentation"/>
<meta name="DC.type" content="Learn/Docs/Logstash/Reference/6.8"/>
<meta name="DC.subject" content="Logstash"/>
<meta name="DC.identifier" content="6.8"/>
<meta name="robots" content="noindex,nofollow"/>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<script src="https://cdn.optimizely.com/js/18132920325.js"></script>
<link rel="apple-touch-icon" sizes="57x57" href="/apple-icon-57x57.png">
<link rel="apple-touch-icon" sizes="60x60" href="/apple-icon-60x60.png">
<link rel="apple-touch-icon" sizes="72x72" href="/apple-icon-72x72.png">
<link rel="apple-touch-icon" sizes="76x76" href="/apple-icon-76x76.png">
<link rel="apple-touch-icon" sizes="114x114" href="/apple-icon-114x114.png">
<link rel="apple-touch-icon" sizes="120x120" href="/apple-icon-120x120.png">
<link rel="apple-touch-icon" sizes="144x144" href="/apple-icon-144x144.png">
<link rel="apple-touch-icon" sizes="152x152" href="/apple-icon-152x152.png">
<link rel="apple-touch-icon" sizes="180x180" href="/apple-icon-180x180.png">
<link rel="icon" type="image/png" href="/favicon-32x32.png" sizes="32x32">
<link rel="icon" type="image/png" href="/android-chrome-192x192.png" sizes="192x192">
<link rel="icon" type="image/png" href="/favicon-96x96.png" sizes="96x96">
<link rel="icon" type="image/png" href="/favicon-16x16.png" sizes="16x16">
<link rel="manifest" href="/manifest.json">
<meta name="apple-mobile-web-app-title" content="Elastic">
<meta name="application-name" content="Elastic">
<meta name="msapplication-TileColor" content="#ffffff">
<meta name="msapplication-TileImage" content="/mstile-144x144.png">
<meta name="theme-color" content="#ffffff">
<meta name="naver-site-verification" content="936882c1853b701b3cef3721758d80535413dbfd" />
<meta name="yandex-verification" content="d8a47e95d0972434" />
<meta name="localized" content="true" />
<meta name="st:robots" content="follow,index" />
<meta property="og:image" content="https://static-www.elastic.co/v3/assets/bltefdd0b53724fa2ce/blt280217a63b82a734/6202d3378b1f312528798412/elastic-logo.svg" />
<meta property="og:image:width" content="500" />
<meta property="og:image:height" content="172" />
<link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
<link rel="icon" href="/favicon.ico" type="image/x-icon">
<link rel="apple-touch-icon-precomposed" sizes="64x64" href="/favicon_64x64_16bit.png">
<link rel="apple-touch-icon-precomposed" sizes="32x32" href="/favicon_32x32.png">
<link rel="apple-touch-icon-precomposed" sizes="16x16" href="/favicon_16x16.png">
<!-- Give IE8 a fighting chance -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
<![endif]-->
<link rel="stylesheet" type="text/css" href="/guide/static/styles.css" />
</head>
<!--© 2015-2022 Elasticsearch B.V. -->
<!-- All Elastic documentation is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. -->
<!-- http://creativecommons.org/licenses/by-nc-nd/4.0/ -->
<body>
<!-- Google Tag Manager -->
<script>dataLayer = [];</script><noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-58RLH5" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= '//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-58RLH5');</script>
<!-- End Google Tag Manager -->
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-12395217-16"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-12395217-16');
</script>
<!-- Google Tag Manager for GA4 -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);})(window,document,'script','dataLayer','GTM-KNJMG2M');</script>
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-KNJMG2M" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<!-- End Google Tag Manager for GA4-->
<div id='elastic-nav' style="display:none;"></div>
<script src='https://www.elastic.co/elastic-nav.js'></script>
<div class="main-container">
<section id="content" >
<div class="content-wrapper">
<section id="guide" lang="en">
<div class="container-fluid">
<div class="row pb-3">
<div class="col-12 order-2 col-md-4 order-md-1 col-lg-3 h-almost-full-md sticky-top-md" id="left_col">
<!-- The TOC is appended here -->
</div>
<div class="col-12 order-1 col-md-8 order-md-2 col-lg-7 order-lg-2 guide-section" id="middle_col">
<!-- start body -->
<div class="page_header">
<strong>IMPORTANT</strong>: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
<a href="../current/index.html">current release documentation</a>.
</div>
<div id="content">
<div class="breadcrumbs">
<span class="breadcrumb-link"><a href="/guide/">Elastic Docs</a></span>
<span class="chevron-right">›</span><span class="breadcrumb-link"><a href="index.html">Logstash Reference [6.8]</a></span>
<span class="chevron-right">›</span><span class="breadcrumb-link"><a href="configuration.html">Configuring Logstash</a></span>
</div>
<div class="navheader">
<span class="prev">
<a href="configuring-centralized-pipelines.html">« Configuring Centralized Pipeline Management</a>
</span>
<span class="next">
<a href="ls-security.html">Configuring Security in Logstash »</a>
</span>
</div>
<div class="section xpack">
<div class="titlepage"><div><div>
<h2 class="title"><a id="configuring-logstash"></a>Configuring Monitoring for Logstash Nodes<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/6.8/docs/static/monitoring/configuring-logstash.asciidoc">edit</a><a class="xpack_tag" href="/subscriptions"></a></h2>
</div></div></div>
<p>To monitor Logstash nodes:</p>
<div class="olist orderedlist">
<ol class="orderedlist">
<li class="listitem">
<p>Identify where to send monitoring data. This cluster is often referred to as
the <em>production cluster</em>. For examples of typical monitoring architectures, see
<a href="/guide/en/elasticsearch/reference/6.8/how-monitoring-works.html" class="ulink" target="_top">How monitoring works</a>.</p>
<div class="important admon">
<div class="icon"></div>
<div class="admon_content">
<p>To visualize Logstash as part of the Elastic Stack (as shown in Step
6), send metrics to your <em>production</em> cluster. Sending metrics to a dedicated
monitoring cluster will show the Logstash metrics under the <em>monitoring</em> cluster.</p>
</div>
</div>
</li>
<li class="listitem">
Verify that the <code class="literal">xpack.monitoring.collection.enabled</code> setting is <code class="literal">true</code> on the
production cluster. If that setting is <code class="literal">false</code>, the collection of monitoring data
is disabled in Elasticsearch and data is ignored from all other sources.
</li>
<li class="listitem">
<p>Configure your Logstash nodes to send metrics by setting the
<code class="literal">xpack.monitoring.elasticsearch.hosts</code> in <code class="literal">logstash.yml</code>. If X-Pack security is enabled,
you also need to specify the credentials for the
<a href="/guide/en/elasticsearch/reference/6.8/built-in-users.html" class="ulink" target="_top">built-in <code class="literal">logstash_system</code> user</a>. For more information about these settings, see <a class="xref" href="configuring-logstash.html#monitoring-settings" title="Monitoring Settings in Logstash">Monitoring Settings</a>.</p>
<div class="pre_wrapper lang-yaml">
<pre class="programlisting prettyprint lang-yaml">xpack.monitoring.elasticsearch.hosts: ["http://es-prod-node-1:9200", "http://es-prod-node-2:9200"] <a id="CO3-1"></a><i class="conum" data-value="1"></i>
xpack.monitoring.elasticsearch.username: "logstash_system" <a id="CO3-2"></a><i class="conum" data-value="2"></i>
xpack.monitoring.elasticsearch.password: "changeme"</pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO3-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>If SSL/TLS is enabled on the production cluster, you must connect through
HTTPS. As of v5.2.1, you can specify multiple Elasticsearch hosts as an array as well as
specifying a single host as a string. If multiple URLs are specified, Logstash
can round-robin requests to these production nodes.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO3-2"><i class="conum" data-value="2"></i></a></p>
</td>
<td align="left" valign="top">
<p>If X-Pack security is disabled on the production cluster, you can omit these
<code class="literal">username</code> and <code class="literal">password</code> settings.</p>
</td>
</tr>
</table>
</div>
</li>
<li class="listitem">
<p>If SSL/TLS is enabled on the production Elasticsearch cluster, specify the trusted
CA certificates that will be used to verify the identity of the nodes
in the cluster.</p>
<p>To add a CA certificate to a Logstash node’s trusted certificates, you
can specify the location of the PEM encoded certificate with the
<code class="literal">certificate_authority</code> setting:</p>
<div class="pre_wrapper lang-yaml">
<pre class="programlisting prettyprint lang-yaml">xpack.monitoring.elasticsearch.ssl.certificate_authority: /path/to/ca.crt</pre>
</div>
<p>Alternatively, you can configure trusted certificates using a truststore
(a Java Keystore file that contains the certificates):</p>
<div class="pre_wrapper lang-yaml">
<pre class="programlisting prettyprint lang-yaml">xpack.monitoring.elasticsearch.ssl.truststore.path: /path/to/file
xpack.monitoring.elasticsearch.ssl.truststore.password: password</pre>
</div>
<p>Also, optionally, you can set up client certificate using a keystore
(a Java Keystore file that contains the certificate):</p>
<div class="pre_wrapper lang-yaml">
<pre class="programlisting prettyprint lang-yaml">xpack.monitoring.elasticsearch.ssl.keystore.path: /path/to/file
xpack.monitoring.elasticsearch.ssl.keystore.password: password</pre>
</div>
<p>Set sniffing to <code class="literal">true</code> to enable discovery of other nodes of the
elasticsearch cluster. Defaults to <code class="literal">false</code>.</p>
<div class="pre_wrapper lang-yaml">
<pre class="programlisting prettyprint lang-yaml">xpack.monitoring.elasticsearch.sniffing: false</pre>
</div>
</li>
<li class="listitem">
Restart your Logstash nodes.
</li>
<li class="listitem">
<p>To verify your X-Pack monitoring configuration, point your web browser at your Kibana
host, and select <span class="strong strong"><strong>Monitoring</strong></span> from the side navigation. Metrics reported from
your Logstash nodes should be visible in the Logstash section. When security is
enabled, to view the monitoring dashboards you must log in to Kibana as a user
who has the <code class="literal">kibana_user</code> and <code class="literal">monitoring_user</code> roles.</p>
<p><span class="image"><a class="image" href="monitoring/images/monitoring-ui.png"><img src="static/monitoring/images/monitoring-ui.png" alt="Monitoring"></a></span></p>
</li>
</ol>
</div>
<h4><a id="monitoring-upgraded-logstash"></a>Re-enabling Logstash Monitoring After Upgrading<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/6.8/docs/static/monitoring/configuring-logstash.asciidoc">edit</a></h4>
<p>When upgrading from older versions of X-Pack, the built-in <code class="literal">logstash_system</code>
user is disabled for security reasons. To resume monitoring,
<a class="xref" href="monitoring-troubleshooting.html" title="Troubleshooting X-Pack monitoring in Logstash">change the password and re-enable the logstash_system user</a>.</p>
<div class="section xpack">
<div class="titlepage"><div><div>
<h3 class="title"><a id="monitoring-settings"></a>Monitoring Settings in Logstash<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/6.8/docs/static/monitoring/configuring-logstash.asciidoc">edit</a><a class="xpack_tag" href="/subscriptions"></a></h3>
</div></div></div>
<p>You can set the following <code class="literal">xpack.monitoring</code> settings in <code class="literal">logstash.yml</code> to
control how monitoring data is collected from your Logstash nodes. However, the
defaults work best in most circumstances. For more information about configuring
Logstash, see <a class="xref" href="logstash-settings-file.html" title="logstash.yml">logstash.yml</a>.</p>
<h5><a id="monitoring-general-settings"></a>General Monitoring Settings<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/6.8/docs/static/monitoring/configuring-logstash.asciidoc">edit</a></h5>
<div class="variablelist">
<dl class="variablelist">
<dt>
<span class="term">
<code class="literal">xpack.monitoring.enabled</code>
</span>
</dt>
<dd>
Monitoring is disabled by default. Set to <code class="literal">true</code> to enable X-Pack monitoring.
</dd>
<dt>
<span class="term">
<code class="literal">xpack.monitoring.elasticsearch.hosts</code>
</span>
</dt>
<dd>
The Elasticsearch instances that you want to ship your Logstash metrics to. This might be
the same Elasticsearch instance specified in the <code class="literal">outputs</code> section in your Logstash
configuration, or a different one. This is <span class="strong strong"><strong>not</strong></span> the URL of your dedicated
monitoring cluster. Even if you are using a dedicated monitoring cluster, the
Logstash metrics must be routed through your production cluster. You can specify
a single host as a string, or specify multiple hosts as an array. Defaults to
<code class="literal">http://localhost:9200</code>.
</dd>
</dl>
</div>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>If your Elasticsearch cluster is configured with dedicated master-eliglble
nodes, Logstash metrics should <em>not</em> be routed to these nodes, as doing so can
create resource contention and impact the stability of the Elasticsearch
cluster. Therefore, do not include such nodes in
<code class="literal">xpack.monitoring.elasticsearch.hosts</code>.</p>
</div>
</div>
<div class="variablelist">
<dl class="variablelist">
<dt>
<span class="term">
<code class="literal">xpack.monitoring.elasticsearch.username</code> and <code class="literal">xpack.monitoring.elasticsearch.password</code>
</span>
</dt>
<dd>
If your Elasticsearch is protected with basic authentication, these settings provide the
username and password that the Logstash instance uses to authenticate for
shipping monitoring data.
</dd>
</dl>
</div>
<h4><a id="monitoring-collection-settings"></a>Monitoring Collection Settings<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/6.8/docs/static/monitoring/configuring-logstash.asciidoc">edit</a></h4>
<div class="variablelist">
<dl class="variablelist">
<dt>
<span class="term">
<code class="literal">xpack.monitoring.collection.interval</code>
</span>
</dt>
<dd>
Controls how often data samples are collected and shipped on the Logstash side.
Defaults to <code class="literal">10s</code>. If you modify the collection interval, set the
<code class="literal">xpack.monitoring.min_interval_seconds</code> option in <code class="literal">kibana.yml</code> to the same value.
</dd>
</dl>
</div>
<h5><a id="monitoring-ssl-settings"></a>X-Pack monitoring TLS/SSL Settings<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/6.8/docs/static/monitoring/configuring-logstash.asciidoc">edit</a></h5>
<p>You can configure the following Transport Layer Security (TLS) or
Secure Sockets Layer (SSL) settings. For more information, see
<a class="xref" href="ls-security.html#ls-monitoring-user" title="Configuring Credentials for Logstash Monitoring">Configuring Credentials for Logstash Monitoring</a>.</p>
<div class="variablelist">
<dl class="variablelist">
<dt>
<span class="term">
<code class="literal">xpack.monitoring.elasticsearch.ssl.certificate_authority</code>
</span>
</dt>
<dd>
Optional setting that enables you to specify a path to the <code class="literal">.pem</code> file for the
certificate authority for your Elasticsearch instance.
</dd>
<dt>
<span class="term">
<code class="literal">xpack.monitoring.elasticsearch.ssl.truststore.path</code>
</span>
</dt>
<dd>
Optional settings that provide the paths to the Java keystore (JKS) to validate
the server’s certificate.
</dd>
<dt>
<span class="term">
<code class="literal">xpack.monitoring.elasticsearch.ssl.truststore.password</code>
</span>
</dt>
<dd>
Optional settings that provide the password to the truststore.
</dd>
<dt>
<span class="term">
<code class="literal">xpack.monitoring.elasticsearch.ssl.keystore.path</code>
</span>
</dt>
<dd>
Optional settings that provide the paths to the Java keystore (JKS) to validate
the client’s certificate.
</dd>
<dt>
<span class="term">
<code class="literal">xpack.monitoring.elasticsearch.ssl.keystore.password</code>
</span>
</dt>
<dd>
Optional settings that provide the password to the keystore.
</dd>
<dt>
<span class="term">
<code class="literal">xpack.monitoring.elasticsearch.ssl.verification_mode</code>
</span>
</dt>
<dd>
Option to validate the server’s certificate. Defaults to <code class="literal">certificate</code>. To disable, set to <code class="literal">none</code>. Disabling this severely compromises security.
</dd>
</dl>
</div>
</div>
</div>
<div class="navfooter">
<span class="prev">
<a href="configuring-centralized-pipelines.html">« Configuring Centralized Pipeline Management</a>
</span>
<span class="next">
<a href="ls-security.html">Configuring Security in Logstash »</a>
</span>
</div>
</div>
<!-- end body -->
</div>
<div class="col-12 order-3 col-lg-2 order-lg-3 h-almost-full-lg sticky-top-lg" id="right_col">
<div id="sticky_content">
<!-- The OTP is appended here -->
<div class="row">
<div class="col-0 col-md-4 col-lg-0" id="bottom_left_col"></div>
<div class="col-12 col-md-8 col-lg-12">
<div id="rtpcontainer">
<div class="mktg-promo" id="most-popular">
<p class="aside-heading">Most Popular</p>
<div class="pb-2">
<p class="media-type">Video</p>
<a href="https://www.elastic.co/webinars/getting-started-elasticsearch?baymax=default&elektra=docs&storm=top-video">
<p class="mb-0">Get Started with Elasticsearch</p>
</a>
</div>
<div class="pb-2">
<p class="media-type">Video</p>
<a href="https://www.elastic.co/webinars/getting-started-kibana?baymax=default&elektra=docs&storm=top-video">
<p class="mb-0">Intro to Kibana</p>
</a>
</div>
<div class="pb-2">
<p class="media-type">Video</p>
<a href="https://www.elastic.co/webinars/introduction-elk-stack?baymax=default&elektra=docs&storm=top-video">
<p class="mb-0">ELK for Logs & Metrics</p>
</a>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
</div>
<div id='elastic-footer'></div>
<script src='https://www.elastic.co/elastic-footer.js'></script>
<!-- Footer Section end-->
</section>
</div>
<script src="/guide/static/jquery.js"></script>
<script type="text/javascript" src="/guide/static/docs.js"></script>
<script type="text/javascript">
window.initial_state = {}</script>
</body>
</html>