-
Notifications
You must be signed in to change notification settings - Fork 70
/
Copy pathobservability-integrations.html
461 lines (440 loc) · 24.2 KB
/
observability-integrations.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
454
455
456
457
458
459
460
461
<!DOCTYPE html>
<html lang="en-us">
<head>
<meta charset="UTF-8">
<title>Observability integrations | APM Overview [7.5] | Elastic</title>
<meta class="elastic" name="content" content="Observability integrations | APM Overview [7.5]">
<link rel="home" href="index.html" title="APM Overview [7.5]"/>
<link rel="up" href="index.html" title="APM Overview [7.5]"/>
<link rel="prev" href="opentracing.html" title="OpenTracing bridge"/>
<link rel="next" href="agent-server-compatibility.html" title="Agent and Server compatibility"/>
<meta class="elastic" name="product_version" content="7.5"/>
<meta class="elastic" name="product_name" content="APM"/>
<meta class="elastic" name="website_area" content="documentation"/>
<meta name="DC.type" content="Learn/Docs/APM Server/Reference/7.5"/>
<meta name="DC.subject" content="APM"/>
<meta name="DC.identifier" content="7.5"/>
<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-v1.css" />
</head>
<!--© 2015-2025 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">
A newer version is available. For the latest information, see the
<a href="../current/index.html">current release documentation</a>.
</div>
<div class="navheader">
<span class="prev">
<a href="opentracing.html">« OpenTracing bridge</a>
</span>
<span class="next">
<a href="agent-server-compatibility.html">Agent and Server compatibility »</a>
</span>
</div>
<div class="book" lang="en">
<div class="titlepage">
<div class="breadcrumbs">
<span class="breadcrumb-link"><a href="/guide/">Elastic Docs</a></span>
<span class="chevron-right">›</span><span class="breadcrumb-link">
<div id="related-products" class="dropdown">
<div class="related-products-title">APM:</div>
<div class="dropdown-anchor" tabindex="0">Overview<span class="dropdown-icon"></span></div>
<div class="dropdown-content">
<ul>
<li class="dropdown-category">APM</li>
<ul>
<li><a href="/guide/en/observability/current/apm.html">Observability › APM</a></li>
</ul>
<li class="dropdown-category">APM agents</li>
<ul>
<li><a href="/guide/en/apm/agent/android/current/intro.html">Android Agent Reference</a></li>
<li><a href="/guide/en/apm/agent/go/current/introduction.html">Go Agent Reference</a></li>
<li><a href="/guide/en/apm/agent/swift/current/intro.html">iOS Agent Reference</a></li>
<li><a href="/guide/en/apm/agent/java/current/intro.html">Java Agent Reference</a></li>
<li><a href="/guide/en/apm/agent/dotnet/current/intro.html">.NET Agent Reference</a></li>
<li><a href="/guide/en/apm/agent/nodejs/current/intro.html">Node.js Agent Reference</a></li>
<li><a href="/guide/en/apm/agent/php/current/intro.html">PHP Agent Reference</a></li>
<li><a href="/guide/en/apm/agent/python/current/getting-started.html">Python Agent Reference</a></li>
<li><a href="/guide/en/apm/agent/ruby/current/introduction.html">Ruby Agent Reference</a></li>
<li><a href="/guide/en/apm/agent/rum-js/current/intro.html">Real User Monitoring JavaScript Agent Reference</a></li>
</ul>
<li class="dropdown-category">APM extensions</li>
<ul>
<li><a href="/guide/en/apm/lambda/current/aws-lambda-arch.html">AWS Lambda extension</a></li>
<li><a href="/guide/en/apm/attacher/current/apm-attacher.html">Attacher</a></li>
</ul>
</ul>
</div>
</div>
</div>
<div>
<div><h1 class="title"><a id="id-1"></a>Observability integrations</h1><a class="edit_me" rel="nofollow" title="Edit this page on GitHub" href="https://github.com/elastic/apm-server/edit/7.5/docs/guide/obs-integrations.asciidoc">edit</a></div>
</div>
<!--EXTRA-->
</div>
<div id="content">
<div id="url-to-v3" class="version-warning">
<strong>IMPORTANT</strong>: This documentation is no longer updated. Refer to <a href="https://www.elastic.co/support/eol">Elastic's version policy</a> and the <a href="https://www.elastic.co/docs">latest documentation</a>.
</div>
<div class="chapter">
<div class="titlepage"><div><div>
<div class="position-relative"><h2 class="title"><a id="observability-integrations"></a>Observability integrations</h2><a class="edit_me" rel="nofollow" title="Edit this page on GitHub" href="https://github.com/elastic/apm-server/edit/7.5/docs/guide/obs-integrations.asciidoc">edit</a></div>
</div></div></div>
<p>Elastic APM supports integrations with other observability solutions.</p>
<div class="position-relative"><h3><a id="apm-logging-integration"></a>Logging integration</h3><a class="edit_me" rel="nofollow" title="Edit this page on GitHub" href="https://github.com/elastic/apm-server/edit/7.5/docs/guide/obs-integrations.asciidoc">edit</a></div>
<p>Many applications use logging frameworks to help record, format, and append an application’s logs.
Elastic APM now offers a way to make your application logs even more useful,
by integrating with the most popular logging frameworks in their respective languages.
This means you can easily inject trace information into your logs,
allowing you to explore logs in the <a href="/guide/en/kibana/7.5/xpack-logs.html" class="ulink" target="_top">Logs app</a>,
then jump straight into the corresponding APM traces — all while preserving the trace context.</p>
<p>To get started:</p>
<div class="olist orderedlist">
<ol class="orderedlist">
<li class="listitem">
Enable log correlation
</li>
<li class="listitem">
Add APM identifiers to your logs
</li>
<li class="listitem">
Ingest your logs into Elasticsearch
</li>
</ol>
</div>
<div class="position-relative"><h4><a id="_enable_log_correlation"></a>Enable Log correlation</h4><a class="edit_me" rel="nofollow" title="Edit this page on GitHub" href="https://github.com/elastic/apm-server/edit/7.5/docs/guide/obs-integrations.asciidoc">edit</a></div>
<p>Some Agents require you to first enable log correlation in the Agent.
This is done with a configuration variable, and is different for each Agent.
See the relevant <a href="/guide/en/apm/agent/index.html" class="ulink" target="_top">Agent documentation</a> for further information.</p>
<div class="position-relative"><h4><a id="_add_apm_identifiers_to_your_logs"></a>Add APM identifiers to your logs</h4><a class="edit_me" rel="nofollow" title="Edit this page on GitHub" href="https://github.com/elastic/apm-server/edit/7.5/docs/guide/obs-integrations.asciidoc">edit</a></div>
<p>Once log correlation is enabled,
you must ensure your logs contain APM identifiers.
In some supported frameworks, this is already done for you.
In other scenarios, like for unstructured logs,
you’ll need to add APM identifiers to your logs in any easy to parse manner.</p>
<p>The identifiers we’re interested in are: <a href="/guide/en/ecs/1.1/ecs-tracing.html" class="ulink" target="_top"><code class="literal">trace.id</code></a> and
<a href="/guide/en/ecs/1.1/ecs-tracing.html" class="ulink" target="_top"><code class="literal">transaction.id</code></a>. Certain Agents also support the <code class="literal">span.id</code> field.</p>
<p>This process for adding these fields will differ based the Agent you’re using, the logging framework,
and the type and structure of your logs.</p>
<p>See the relevant <a href="/guide/en/apm/agent/index.html" class="ulink" target="_top">Agent documentation</a> to learn more.</p>
<div class="position-relative"><h4><a id="_ingest_your_logs_into_elasticsearch"></a>Ingest your logs into Elasticsearch</h4><a class="edit_me" rel="nofollow" title="Edit this page on GitHub" href="https://github.com/elastic/apm-server/edit/7.5/docs/guide/obs-integrations.asciidoc">edit</a></div>
<p>Once your logs contain the appropriate identifiers (fields), you need to ingest them into Elasticsearch.
Luckily, we’ve got a tool for that — Filebeat is Elastic’s log shipper.
The <a href="/guide/en/beats/filebeat/7.5/filebeat-getting-started.html" class="ulink" target="_top">Filebeat getting started</a>
guide will walk you through the setup process.</p>
<p>Because logging frameworks and formats vary greatly between different programming languages,
there is no one-size-fits-all approach for ingesting your logs into Elasticsearch.
The following tips should hopefully get you going in the right direction:</p>
<p><span class="strong strong"><strong>Download Filebeat</strong></span></p>
<p>There are many ways to download and get started with Filebeat.
Read the <a href="/guide/en/beats/filebeat/7.5/filebeat-installation.html" class="ulink" target="_top">Filebeat Installation</a> guide to determine which is best for you.</p>
<p><span class="strong strong"><strong>Configure Filebeat</strong></span></p>
<p>Modify the <a href="/guide/en/beats/filebeat/7.5/filebeat-configuration.html" class="ulink" target="_top"><code class="literal">filebeat.yml</code></a> configuration file to your needs.
Here are some recommendations:</p>
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
Set <code class="literal">filebeat.inputs</code> to point to the source of your logs
</li>
<li class="listitem">
Point Filebeat to the same Elastic Stack that is receiving your APM data
</li>
<li class="listitem">
If you’re using Elastic cloud, set <code class="literal">cloud.id</code> and <code class="literal">cloud.auth</code>.
</li>
<li class="listitem">
If your using a manual setup, use <code class="literal">output.elasticsearch.hosts</code>.
</li>
</ul>
</div>
<div class="pre_wrapper lang-yml">
<div class="console_code_copy" title="Copy to clipboard"></div>
<pre class="programlisting prettyprint lang-yml">filebeat.inputs:
- type: log <a id="CO1-1"></a><i class="conum" data-value="1"></i>
paths: <a id="CO1-2"></a><i class="conum" data-value="2"></i>
- /var/log/*.log
cloud.id: "staging:dXMtZWFzdC0xLmF3cy5mb3VuZC5pbyRjZWMNjN2Q3YTllOTYyNTc0Mw==" <a id="CO1-3"></a><i class="conum" data-value="3"></i>
cloud.auth: "elastic:YOUR_PASSWORD" <a id="CO1-4"></a><i class="conum" data-value="4"></i></pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO1-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>Configures the <code class="literal">log</code> input</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO1-2"><i class="conum" data-value="2"></i></a></p>
</td>
<td align="left" valign="top">
<p>Path(s) that must be crawled to fetch the log lines</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO1-3"><i class="conum" data-value="3"></i></a></p>
</td>
<td align="left" valign="top">
<p>Used to resolve the Elasticsearch and Kibana URLs for Elastic Cloud</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO1-4"><i class="conum" data-value="4"></i></a></p>
</td>
<td align="left" valign="top">
<p>Authorization token for Elastic Cloud</p>
</td>
</tr>
</table>
</div>
<p><span class="strong strong"><strong>JSON logs</strong></span></p>
<p>For JSON logs you can use the <a href="/guide/en/beats/filebeat/7.5/filebeat-input-log.html" class="ulink" target="_top"><code class="literal">log</code> input</a> to read lines from log files.
Here’s what a sample configuration might look like:</p>
<div class="pre_wrapper lang-yml">
<div class="console_code_copy" title="Copy to clipboard"></div>
<pre class="programlisting prettyprint lang-yml">filebeat.inputs:
json.keys_under_root: true <a id="CO2-1"></a><i class="conum" data-value="1"></i>
json.add_error_key: true <a id="CO2-2"></a><i class="conum" data-value="2"></i>
json.message_key: message <a id="CO2-3"></a><i class="conum" data-value="3"></i></pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO2-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p><code class="literal">true</code> copies JSON keys to the top level in the output document</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO2-2"><i class="conum" data-value="2"></i></a></p>
</td>
<td align="left" valign="top">
<p>Tells Filebeat to add an <code class="literal">error.message</code> and <code class="literal">error.type: json</code> key in case of JSON unmarshalling errors</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO2-3"><i class="conum" data-value="3"></i></a></p>
</td>
<td align="left" valign="top">
<p>Specifies the JSON key on which to apply line filtering and multiline settings</p>
</td>
</tr>
</table>
</div>
<p><span class="strong strong"><strong>Parsing unstructured logs</strong></span></p>
<p>Consider the following log that is decorated with the <code class="literal">transaction.id</code> and <code class="literal">trace.id</code> fields:</p>
<div class="pre_wrapper lang-log">
<div class="console_code_copy" title="Copy to clipboard"></div>
<pre class="programlisting prettyprint lang-log">2019-09-18 21:29:49,525 - django.server - ERROR - "GET / HTTP/1.1" 500 27 | elasticapm transaction.id=fcfbbe447b9b6b5a trace.id=f965f4cc5b59bdc62ae349004eece70c span.id=None</pre>
</div>
<p>All that’s needed now is an <a href="/guide/en/beats/filebeat/7.5/configuring-ingest-node.html" class="ulink" target="_top">ingest node processor</a> to pre-process your logs and
extract these structured fields before they are indexed in Elasticsearch.
To do this, you’d need to create a pipeline that uses Elasticsearch’s <a href="/guide/en/elasticsearch/reference/7.5/grok-processor.html" class="ulink" target="_top">Grok Processor</a>.
Here’s an example:</p>
<div class="pre_wrapper lang-json">
<div class="console_code_copy" title="Copy to clipboard"></div>
<pre class="programlisting prettyprint lang-json">PUT _ingest/pipeline/log-correlation
{
"description": "Parses the log correlation IDs out of the raw plain-text log",
"processors": [
{
"grok": {
"field": "message", <a id="CO3-1"></a><i class="conum" data-value="1"></i>
"patterns": ["%{GREEDYDATA:message} | elasticapm transaction.id=%{DATA:transaction.id} trace.id=%{DATA:trace.id} span.id=%{DATA:span.id}"] <a id="CO3-2"></a><i class="conum" data-value="2"></i>
}
}
]
}</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>The field to use for grok expression parsing</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>An ordered list of grok expression to match and extract named captures with:
<code class="literal">%{DATA:transaction.id}</code> captures the value of <code class="literal">transaction.id</code>,
<code class="literal">%{DATA:trace.id}</code> captures the value or <code class="literal">trace.id</code>, and
<code class="literal">%{DATA:span.id}</code> captures the value of <code class="literal">span.id</code>.</p>
</td>
</tr>
</table>
</div>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>Depending on how you’ve added APM data to your logs,
you may need to tweak this grok pattern in order to work for your setup.
In addition, it’s possible to extract more structure out of your logs.
Make sure to follow the <a href="/guide/en/ecs/1.1/ecs-field-reference.html" class="ulink" target="_top">Elastic Common Schema</a>
when defining which fields you are storing in Elasticsearch.</p>
</div>
</div>
<p>Then, configure Filebeat to use the processor in <code class="literal">filebeat.yml</code>:</p>
<div class="pre_wrapper lang-json">
<div class="console_code_copy" title="Copy to clipboard"></div>
<pre class="programlisting prettyprint lang-json">output.elasticsearch:
pipeline: "log-correlation"</pre>
</div>
<p>If your logs contain messages that span multiple lines of text (common in Java stack traces),
you’ll also need to configure <a href="/guide/en/beats/filebeat/7.5/multiline-examples.html" class="ulink" target="_top">multiline settings</a>.</p>
<p>The following example shows how to configure Filebeat to handle a multiline message where the first line of the message begins with a bracket ([).</p>
<div class="pre_wrapper lang-yml">
<div class="console_code_copy" title="Copy to clipboard"></div>
<pre class="programlisting prettyprint lang-yml">multiline.pattern: '^\['
multiline.negate: true
multiline.match: after</pre>
</div>
</div>
</div>
</div><div class="navfooter">
<span class="prev">
<a href="opentracing.html">« OpenTracing bridge</a>
</span>
<span class="next">
<a href="agent-server-compatibility.html">Agent and Server compatibility »</a>
</span>
</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?page=docs&placement=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?page=docs&placement=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?page=docs&placement=top-video">
<p class="mb-0">ELK for Logs & Metrics</p>
</a>
</div>
</div>
</div>
<!-- Feedback widget -->
<div id="feedbackWidgetContainer"></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>
<!-- Feedback modal -->
<div id="feedbackModalContainer"></div>
<script src="/guide/static/jquery.js"></script>
<script type="text/javascript" src="/guide/static/docs-v1.js"></script>
<script type="text/javascript">
window.initial_state = {}</script>
</body>
</html>