forked from elastic/built-docs
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdeploying-and-scaling.html
453 lines (435 loc) · 28.2 KB
/
deploying-and-scaling.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
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
<!DOCTYPE html>
<html lang="en-us">
<head>
<meta charset="UTF-8">
<title>Deploying and Scaling Logstash | Logstash Reference [7.3] | Elastic</title>
<meta class="elastic" name="content" content="Deploying and Scaling Logstash | Logstash Reference [7.3]">
<link rel="home" href="index.html" title="Logstash Reference [7.3]"/>
<link rel="up" href="index.html" title="Logstash Reference [7.3]"/>
<link rel="prev" href="lookup-enrichment.html" title="Enriching Data with Lookups"/>
<link rel="next" href="performance-tuning.html" title="Performance Tuning"/>
<meta class="elastic" name="product_version" content="7.3"/>
<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/7.3"/>
<meta name="DC.subject" content="Logstash"/>
<meta name="DC.identifier" content="7.3"/>
<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 [7.3]</a></span>
</div>
<div class="navheader">
<span class="prev">
<a href="lookup-enrichment.html">« Enriching Data with Lookups</a>
</span>
<span class="next">
<a href="performance-tuning.html">Performance Tuning »</a>
</span>
</div>
<div class="chapter">
<div class="titlepage"><div><div>
<h1 class="title"><a id="deploying-and-scaling"></a>Deploying and Scaling 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/7.3/docs/static/deploying.asciidoc">edit</a></h1>
</div></div></div>
<p>The Elastic Stack is used for tons of use cases, from operational log and
metrics analytics, to enterprise and application search. Making sure your data
gets scalably, durably, and securely transported to Elasticsearch is extremely
important, especially for mission critical environments.</p>
<p>The goal of this document is to highlight the most common architecture patterns
for Logstash and how to effectively scale as your deployment grows. The focus
will be around the operational log, metrics, and security analytics use cases
because they tend to require larger scale deployments. The deploying and scaling
recommendations provided here may vary based on your own requirements.</p>
<h3><a id="deploying-getting-started"></a>Getting Started<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h3>
<p>For first time users, if you simply want to tail a log file to grasp the power
of the Elastic Stack, we recommend trying
<a href="/guide/en/beats/filebeat/7.3/filebeat-modules-overview.html" class="ulink" target="_top">Filebeat Modules</a>. Filebeat Modules
enable you to quickly collect, parse, and index popular log types and view
pre-built Kibana dashboards within minutes.
<a href="/guide/en/beats/metricbeat/7.3/metricbeat-modules.html" class="ulink" target="_top">Metricbeat Modules</a> provide a similar
experience, but with metrics data. In this context, Beats will ship data
directly to Elasticsearch where <a href="/guide/en/elasticsearch/reference/7.3/ingest.html" class="ulink" target="_top">Ingest Nodes</a> will process
and index your data.</p>
<div class="imageblock">
<div class="content">
<img src="static/images/deploy1.png" alt="deploy1">
</div>
</div>
<h4><a id="_introducing_logstash"></a>Introducing 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/7.3/docs/static/deploying.asciidoc">edit</a></h4>
<p>What are the main benefits for integrating Logstash into your architecture?</p>
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
Scale through ingestion spikes - Logstash has an adaptive disk-based
buffering system that will absorb incoming throughput, therefore mitigating
backpressure
</li>
<li class="listitem">
Ingest from other data sources like databases, S3, or messaging queues
</li>
<li class="listitem">
Emit data to multiple destinations like S3, HDFS, or write to a file
</li>
<li class="listitem">
Compose more sophisticated processing pipelines with conditional dataflow logic
</li>
</ul>
</div>
<h3><a id="scaling-ingest"></a>Scaling Ingest<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h3>
<p>Beats and Logstash make ingest awesome. Together, they provide a comprehensive
solution that is scalable and resilient. What can you expect?</p>
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
Horizontal scalability, high availability, and variable load handling
</li>
<li class="listitem">
Message durability with at-least-once delivery guarantees
</li>
<li class="listitem">
End-to-end secure transport with authentication and wire encryption
</li>
</ul>
</div>
<h4><a id="_beats_and_logstash"></a>Beats and 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/7.3/docs/static/deploying.asciidoc">edit</a></h4>
<p>Beats run across thousands of edge host servers, collecting, tailing, and
shipping logs to Logstash. Logstash serves as the centralized streaming
engine for data unification and enrichment. The
<a class="xref" href="plugins-inputs-beats.html" title="Beats input plugin">Beats input plugin</a> exposes a secure,
acknowledgement-based endpoint for Beats to send data to Logstash.</p>
<div class="imageblock">
<div class="content">
<img src="static/images/deploy2.png" alt="deploy2">
</div>
</div>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>Enabling persistent queues is strongly recommended, and these
architecture characteristics assume that they are enabled. We encourage you to
review the <a class="xref" href="persistent-queues.html" title="Persistent Queues">Persistent Queues</a> documentation for feature benefits and more
details on resiliency.</p>
</div>
</div>
<h4><a id="_scalability"></a>Scalability<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h4>
<p>Logstash is horizontally scalable and can form groups of nodes running the same
pipeline. Logstash’s adaptive buffering capabilities will facilitate smooth
streaming even through variable throughput loads. If the Logstash layer becomes
an ingestion bottleneck, simply add more nodes to scale out. Here are a few
general recommendations:</p>
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
Beats should <a href="/guide/en/beats/filebeat/7.3/load-balancing.html" class="ulink" target="_top">load balance</a> across a group of
Logstash nodes.
</li>
<li class="listitem">
A minimum of two Logstash nodes are recommended for high availability.
</li>
<li class="listitem">
It’s common to deploy just one Beats input per Logstash node, but multiple
Beats inputs can also be deployed per Logstash node to expose independent
endpoints for different data sources.
</li>
</ul>
</div>
<h4><a id="_resiliency"></a>Resiliency<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h4>
<p>When using <a href="/products/beats/filebeat" class="ulink" target="_top">Filebeat</a> or
<a href="/products/beats/winlogbeat" class="ulink" target="_top">Winlogbeat</a> for log collection
within this ingest flow, <span class="strong strong"><strong>at-least-once delivery</strong></span> is guaranteed. Both the
communication protocols, from Filebeat or Winlogbeat to Logstash, and from
Logstash to Elasticsearch, are synchronous and support acknowledgements. The
other Beats don’t yet have support for acknowledgements.</p>
<p>Logstash persistent queues provide protection across node failures. For
disk-level resiliency in Logstash, it’s important to ensure disk redundancy.
For on-premise deployments, it’s recommended that you configure RAID. When
running in the cloud or a containerized environment, it’s recommended that you
use persistent disks with replication strategies that reflect your data SLAs.</p>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>Make sure <code class="literal">queue.checkpoint.writes: 1</code> is set for at-least-once
guarantees. For more details, see the
<a class="xref" href="persistent-queues.html#durability-persistent-queues" title="Controlling Durability">persistent queue durability</a> documentation.</p>
</div>
</div>
<h4><a id="_processing"></a>Processing<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h4>
<p>Logstash will commonly extract fields with <a class="xref" href="plugins-filters-grok.html" title="Grok filter plugin">grok</a> or
<a class="xref" href="plugins-filters-dissect.html" title="Dissect filter plugin">dissect</a>, augment
<a class="xref" href="plugins-filters-geoip.html" title="Geoip filter plugin">geographical</a> info, and can further enrich events with
<a class="xref" href="plugins-filters-translate.html" title="Translate filter plugin">file</a>, <a class="xref" href="plugins-filters-jdbc_streaming.html" title="Jdbc_streaming filter plugin">database</a>,
or <a class="xref" href="plugins-filters-elasticsearch.html" title="Elasticsearch filter plugin">Elasticsearch</a> lookup datasets. Be aware
that processing complexity can affect overall throughput and CPU utilization.
Make sure to check out the other <a class="xref" href="filter-plugins.html" title="Filter plugins">available filter plugins</a>.</p>
<h4><a id="_secure_transport"></a>Secure Transport<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h4>
<p>Enterprise-grade security is available across the entire delivery chain.</p>
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
Wire encryption is recommended for both the transport from
<a href="/guide/en/beats/filebeat/7.3/configuring-ssl-logstash.html" class="ulink" target="_top">Beats to Logstash</a> and from
<a href="/guide/en/logstash/7.3/ls-security.html" class="ulink" target="_top">Logstash to Elasticsearch</a>.
</li>
<li class="listitem">
There’s a wealth of security options when communicating with Elasticsearch
including basic authentication, TLS, PKI, LDAP, AD, and other custom realms.
To enable Elasticsearch security, see
<a href="/guide/en/elasticsearch/reference/7.3/secure-cluster.html" class="ulink" target="_top">Secure a cluster</a>.
</li>
</ul>
</div>
<h4><a id="_monitoring"></a>Monitoring<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h4>
<p>When running Logstash 5.2 or greater,
the <a href="/products/x-pack/monitoring" class="ulink" target="_top">Monitoring UI</a> provides
deep visibility into your deployment metrics, helping observe performance and
alleviate bottlenecks as you scale. Monitoring is an X-Pack feature under the
Basic License and is therefore <span class="strong strong"><strong>free to use</strong></span>. To get started, see
<a href="/guide/en/logstash/7.3/monitoring-logstash.html" class="ulink" target="_top">Monitoring Logstash</a>.</p>
<p>If external monitoring is preferred, there are <a class="xref" href="monitoring-logstash.html#monitoring" title="APIs for monitoring Logstash">Monitoring APIs</a>
that return point-in-time metrics snapshots.</p>
<h3><a id="adding-other-sources"></a>Adding Other Popular Sources<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h3>
<p>Users may have other mechanisms of collecting logging data, and it’s easy to
integrate and centralize them into the Elastic Stack. Let’s walk through a few
scenarios:</p>
<div class="imageblock">
<div class="content">
<img src="static/images/deploy3.png" alt="deploy3">
</div>
</div>
<h4><a id="_tcp_udp_and_http_protocols"></a>TCP, UDP, and HTTP Protocols<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h4>
<p>The TCP, UDP, and HTTP protocols are common ways to feed data into Logstash.
Logstash can expose endpoint listeners with the respective
<a class="xref" href="plugins-inputs-tcp.html" title="Tcp input plugin">TCP</a>, <a class="xref" href="plugins-inputs-udp.html" title="Udp input plugin">UDP</a>, and
<a class="xref" href="plugins-inputs-http.html" title="Http input plugin">HTTP</a> input plugins. The data sources enumerated below
are typically ingested through one of these three protocols.</p>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>The TCP protocol does not support application-level acknowledgements, so
connectivity issues may result in data loss.</p>
</div>
</div>
<p>For high availability scenarios, a third-party hardware or software load
balancer, like HAProxy, should be added to fan out traffic to a group of
Logstash nodes.</p>
<h4><a id="_network_and_security_data"></a>Network and Security Data<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h4>
<p>Although Beats may already satisfy your data ingest use case, network and
security datasets come in a variety of forms. Let’s touch on a few other
ingestion points.</p>
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
Network wire data - collect and analyze network traffic with
<a href="/products/beats/packetbeat" class="ulink" target="_top">Packetbeat</a>.
</li>
<li class="listitem">
Netflow v5/v9/v10 - Logstash understands data from Netflow/IPFIX exporters
with the <a class="xref" href="plugins-codecs-netflow.html" title="Netflow codec plugin">Netflow codec</a>.
</li>
<li class="listitem">
Nmap - Logstash accepts and parses Nmap XML data with the
<a class="xref" href="plugins-codecs-nmap.html" title="Nmap codec plugin">Nmap codec</a>.
</li>
<li class="listitem">
SNMP trap - Logstash has a native <a class="xref" href="plugins-inputs-snmptrap.html" title="Snmptrap input plugin">SNMP trap input</a>.
</li>
<li class="listitem">
CEF - Logstash accepts and parses CEF data from systems like Arcsight
SmartConnectors with the <a class="xref" href="plugins-codecs-cef.html" title="Cef codec plugin">CEF codec</a>. See this
<a href="/blog/integrating-elastic-stack-with-arcsight-siem-part-1" class="ulink" target="_top">blog series</a>
for more details.
</li>
</ul>
</div>
<h4><a id="_centralized_syslog_servers"></a>Centralized Syslog Servers<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h4>
<p>Existing syslog server technologies like rsyslog and syslog-ng generally send
syslog over to Logstash TCP or UDP endpoints for extraction, processing, and
persistence. If the data format conforms to RFC3164, it can be fed directly
to the <a class="xref" href="plugins-inputs-syslog.html" title="Syslog input plugin">Logstash syslog input</a>.</p>
<h4><a id="_infrastructure_application_data_and_iot"></a>Infrastructure & Application Data and IoT<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h4>
<p>Infrastructure and application metrics can be collected with
<a href="/products/beats/metricbeat" class="ulink" target="_top">Metricbeat</a>, but applications
can also send webhooks to a Logstash HTTP input or have metrics polled from an
HTTP endpoint with the <a class="xref" href="plugins-inputs-http_poller.html" title="Http_poller input plugin">HTTP poller input plugin</a>.</p>
<p>For applications that log with log4j2, it’s recommended to use the
SocketAppender to send JSON to the Logstash TCP input. Alternatively, log4j2
can also log to a file for collection with FIlebeat. Usage of the log4j1
SocketAppender is not recommended.</p>
<p>IoT devices like Raspberry Pis, smartphones, and connected vehicles often send
telemetry data through one of these protocols.</p>
<h3><a id="integrating-with-messaging-queues"></a>Integrating with Messaging Queues<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h3>
<p>If you are leveraging message queuing technologies as part of your existing
infrastructure, getting that data into the Elastic Stack is easy. For existing
users who are utilizing an external queuing layer like Redis or RabbitMQ just
for data buffering with Logstash, it’s recommended to use Logstash persistent
queues instead of an external queuing layer. This will help with overall ease
of management by removing an unnecessary layer of complexity in your ingest
architecture.</p>
<p>For users who want to integrate data from existing Kafka deployments or require
the underlying usage of ephemeral storage, Kafka can serve as a data hub where
Beats can persist to and Logstash nodes can consume from.</p>
<div class="imageblock">
<div class="content">
<img src="static/images/deploy4.png" alt="deploy4">
</div>
</div>
<p>The other TCP, UDP, and HTTP sources can persist to Kafka with Logstash as a
conduit to achieve high availability in lieu of a load balancer. A group of
Logstash nodes can then consume from topics with the
<a class="xref" href="plugins-inputs-kafka.html" title="Kafka input plugin">Kafka input</a> to further transform and enrich the data in
transit.</p>
<h4><a id="_resiliency_and_recovery"></a>Resiliency and Recovery<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h4>
<p>When Logstash consumes from Kafka, persistent queues should be enabled and will
add transport resiliency to mitigate the need for reprocessing during Logstash
node failures. In this context, it’s recommended to use the default persistent
queue disk allocation size <code class="literal">queue.max_bytes: 1GB</code>.</p>
<p>If Kafka is configured to retain data for an extended period of time, data can
be reprocessed from Kafka in the case of disaster recovery and reconciliation.</p>
<h4><a id="_other_messaging_queue_integrations"></a>Other Messaging Queue Integrations<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/logstash/edit/7.3/docs/static/deploying.asciidoc">edit</a></h4>
<p>Although an additional queuing layer is not required, Logstash can consume from
a myriad of other message queuing technologies like
<a class="xref" href="plugins-inputs-rabbitmq.html" title="Rabbitmq input plugin">RabbitMQ</a> and <a class="xref" href="plugins-inputs-redis.html" title="Redis input plugin">Redis</a>. It also
supports ingestion from hosted queuing services like
<a class="xref" href="plugins-inputs-google_pubsub.html" title="Google_pubsub input plugin">Pub/Sub</a>, <a class="xref" href="plugins-inputs-kinesis.html" title="Kinesis input plugin">Kinesis</a>, and
<a class="xref" href="plugins-inputs-sqs.html" title="Sqs input plugin">SQS</a>.</p>
</div>
<div class="navfooter">
<span class="prev">
<a href="lookup-enrichment.html">« Enriching Data with Lookups</a>
</span>
<span class="next">
<a href="performance-tuning.html">Performance Tuning »</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>