# Filebeat log not in elastic when matching parser

**URL:** <https://discuss.elastic.co/t/filebeat-log-not-in-elastic-when-matching-parser/326609>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 27, 2023, 3:16pm UTC](https://discuss.elastic.co/t/filebeat-log-not-in-elastic-when-matching-parser/326609 "2023-02-27T15:16:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![NL-kk](https://avatars.discourse-cdn.com/v4/letter/n/f1d935/32.png) [@NL-kk](https://discuss.elastic.co/u/NL-kk)\
**Post date:** [February 27, 2023, 3:16pm UTC](https://discuss.elastic.co/t/filebeat-log-not-in-elastic-when-matching-parser/326609/1 "2023-02-27T15:16:24Z")

</div>

I just setup a multiline parser because of the multiline error logs of nginx.  
Before the logs were visible in kibana as seperate log enteries, now they are not visible at all.  
The single line logs are being logged correctly but the multiline are not coming through.

This is the config of filebeat:

> filebeat.inputs:
> 
> - type: log  
> paths:
> - "/var/log/nginx/error.log"  
> fields\_under\_root: true  
> fields:  
> document\_type: nginx-error  
> parsers:
> 
> - multiline:  
> type: pattern  
> pattern: '^\d{4}/(0?[1-9]|1[012])/(0?[1-9]|[12][0-9]|3[01])'  
> negate: true  
> match: after

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 27, 2023, 5:16pm UTC](https://discuss.elastic.co/t/filebeat-log-not-in-elastic-when-matching-parser/326609/2 "2023-03-27T17:16:42Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.