# Same filter which is working for 2.x in Elk not working for 6.1.3

**URL:** <https://discuss.elastic.co/t/same-filter-which-is-working-for-2-x-in-elk-not-working-for-6-1-3/123176>\
**Category:** Logstash\
**Created:** [March 9, 2018, 2:26am UTC](https://discuss.elastic.co/t/same-filter-which-is-working-for-2-x-in-elk-not-working-for-6-1-3/123176 "2018-03-09T02:26:04Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![ashish\_khulbe](https://avatars.discourse-cdn.com/v4/letter/a/ea5d25/32.png) [@ashish\_khulbe](https://discuss.elastic.co/u/ashish_khulbe)\
**Post date:** [March 9, 2018, 2:26am UTC](https://discuss.elastic.co/t/same-filter-which-is-working-for-2-x-in-elk-not-working-for-6-1-3/123176/1 "2018-03-09T02:26:04Z")

</div>

Hi,

I have 2 queries :-

1. I configured Elk 2.x with Kibana 4.x a week back and everything working fine.  
Now I am working with 6.1.3 of Elk and file beat but I can see whole message but not filters.

2. Is there any difference in SSL authentication in 2.x Elk and 6.1.3.

Thanks  
Ashish

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [March 11, 2018, 7:54pm UTC](https://discuss.elastic.co/t/same-filter-which-is-working-for-2-x-in-elk-not-working-for-6-1-3/123176/2 "2018-03-11T19:54:03Z")

</div>

> Now I am working with 6.1.3 of Elk and file beat but I can see whole message but not filters.

Please show an example of what you mean.

---

<div class="post-metadata">

**Author:** ![ashish\_khulbe](https://avatars.discourse-cdn.com/v4/letter/a/ea5d25/32.png) [@ashish\_khulbe](https://discuss.elastic.co/u/ashish_khulbe)\
**Post date:** [March 12, 2018, 6:00am UTC](https://discuss.elastic.co/t/same-filter-which-is-working-for-2-x-in-elk-not-working-for-6-1-3/123176/3 "2018-03-12T06:00:58Z")

</div>

Hi Magnus,

Below found the exact code used below:

1. I am using filter, also verified same using online grox filter ([http://grokdebug.herokuapp.com/](http://grokdebug.herokuapp.com/))

LOGS: [DEBUG]:[gur3144]:[lab]:[Feb 14 07:56:23]:[h5vnkdksvmij1aitnbpk0u4]:[INTER]:[Event.Post\_deploymentevent\_check\_started]:[com.onset.openstackdeploy.Deploy{1}:68]

It is working perfectly file with ELK 2.X, with Kibana 4.x.  
Also, in windows also, i am using similar logs and filetr and it is working perfectly fine with 6.1.3 but without filebeat.

1. SSL Error:  
I have configured the SSL on both ELK machine and filebeat (as shown in website)  
when SSL set to false at logstash and SSL line commented on filebeat.yml it is also working file.

Error Received:  
javax.net.ssl.SSLHandshakeException: error:100000f7:SSL routines:OPENSSL\_internal:WRONG\_VERSION\_NUMBER

Regards,  
Ashish Khulbe

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [March 12, 2018, 6:59am UTC](https://discuss.elastic.co/t/same-filter-which-is-working-for-2-x-in-elk-not-working-for-6-1-3/123176/4 "2018-03-12T06:59:43Z")

</div>

> It is working perfectly file with ELK 2.X, with Kibana 4.x.  
> Also, in windows also, i am using similar logs and filetr and it is working perfectly fine with 6.1.3 but without filebeat.

And under what circumstances is it _not_ working?

> Error Received:  
> javax.net.ssl.SSLHandshakeException: error:100000f7:SSL routines:OPENSSL\_internal:WRONG\_VERSION\_NUMBER

Judging by [Unable to get ssl working between Filebeat and Logstash · Issue #293 · logstash-plugins/logstash-input-beats · GitHub](https://github.com/logstash-plugins/logstash-input-beats/issues/293) the problem might be that you have enabled SSL in Logstash but not in Filebeat. What does your Filebeat configuration look like? **Make sure you post it as preformatted text using the `</>` toolbar button.**

---

<div class="post-metadata">

**Author:** ![ashish\_khulbe](https://avatars.discourse-cdn.com/v4/letter/a/ea5d25/32.png) [@ashish\_khulbe](https://discuss.elastic.co/u/ashish_khulbe)\
**Post date:** [March 13, 2018, 6:58am UTC](https://discuss.elastic.co/t/same-filter-which-is-working-for-2-x-in-elk-not-working-for-6-1-3/123176/5 "2018-03-13T06:58:41Z")

</div>

Hi Magnus,

1. I am not able identify that thing which creates trouble.

--\> I already configured with same filters Elasticsearch 2.2.x, Logstash 2.2.x, and Kibana 4.5.x. using Filebeat 1.1.x. (Working perfectly fine i can see the newly created fields in kibana)  
--\> I already configured with same filters ELK 6.1.3 without Filebeat (Working perfectly fine i can see the newly created fields in kibana) on Windows.  
--\> Not able to see newly fields in the kibana for ELK6.1.3 using Filebeat 6.1.3 on Ubuntu with the same configuration.

==\> For logstash : I have modified logstash.yml and /etc/logstash/conf.d/logstash-syslog.conf  
==\> For Filebeat : I have modified filebeat.yml  
Please let me know incase any other file need to be modified.

1. SSL on both logstash and filebeat is set to disabled or commented. Then only i can proceed.

e.g.  
**case 1-\> Working fine without SSL**

## a) filebeat.yml=\>

## #ssl.certificate\_authorities: ["/etc/pki/tls/certs/logstash-forwarder.crt"]

## b) logstash.yml =\>

## input { beats { port =\> 5044 ssl =\> false ssl\_certificate =\> "/etc/pki/tls/certs/logstash-forwarder.crt" ssl\_key =\> "/etc/pki/tls/private/logstash-forwarder.key" } }

## **2) Case 2 -\> Error received with SSL** Whereas, when comment is removed at filebeat.yml and SSL set to True at logstash config, I have even verified the chksum on both filbeat and logstash path.

## Error Received: javax.net.ssl.SSLHandshakeException: error:100000f7:SSL routines:OPENSSL\_internal:WRONG\_VERSION\_NUMBER

Regards,  
Ashish Khulbe

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [March 13, 2018, 7:05am UTC](https://discuss.elastic.co/t/same-filter-which-is-working-for-2-x-in-elk-not-working-for-6-1-3/123176/6 "2018-03-13T07:05:07Z")

</div>

> --\> Not able to see newly fields in the kibana for ELK6.1.3 using Filebeat 6.1.3 on Ubuntu with the same configuration.

Do you get any events at all? What do they look like? What does your Logstash configuration look like?

> Whereas, when comment is removed at filebeat.yml and SSL set to True at logstash config,

Show the complete Filebeat configuration when you think you have enabled SSL. **Format it as requested earlier. I will not ask again.**

---

<div class="post-metadata">

**Author:** ![ashish\_khulbe](https://avatars.discourse-cdn.com/v4/letter/a/ea5d25/32.png) [@ashish\_khulbe](https://discuss.elastic.co/u/ashish_khulbe)\
**Post date:** [March 13, 2018, 9:26am UTC](https://discuss.elastic.co/t/same-filter-which-is-working-for-2-x-in-elk-not-working-for-6-1-3/123176/7 "2018-03-13T09:26:58Z")

</div>

Thanks Magnus,

1. Logstash Configuration:

* * *

root@elk-log:~# cat /etc/logstash/logstash.yml

# Settings file in YAML

# 

# Settings can be specified either in hierarchical form, e.g.:

# 

# pipeline:

# batch:

# size: 125

# delay: 5

# 

# Or as flat keys:

# 

# pipeline.batch.size: 125

# pipeline.batch.delay: 5

# 

# ------------ Node identity ------------

# 

# Use a descriptive name for the node:

# 

# node.name: test

# 

# ------------ Data path ------------------

# 

# 

#path.data: /var/lib/logstash

# 

# ------------ Pipeline Settings --------------

# 

# Set the number of workers that will, in parallel, execute the filters+outputs

# stage of the pipeline.

# 

# This defaults to the number of the host's CPU cores.

# 

# pipeline.workers: 2

# 

# How many workers should be used per output plugin instance

# 

# pipeline.output.workers: 1

# 

# How many events to retrieve from inputs before sending to filters+workers

# 

# pipeline.batch.size: 125

# 

# How long to wait before dispatching an undersized batch to filters+workers

# Value is in milliseconds.

# 

# pipeline.batch.delay: 5

# 

# Force Logstash to exit during shutdown even if there are still inflight

# events in memory. By default, logstash will refuse to quit until all

# received events have been pushed to the outputs.

# 

# WARNING: enabling this can lead to data loss during shutdown

# 

# pipeline.unsafe\_shutdown: false

# 

# ------------ Pipeline Configuration Settings --------------

# 

# Where to fetch the pipeline configuration for the main pipeline

# 

#path.config: /etc/logstash/conf.d/\*.conf  
**path.config: /etc/logstash/conf.d/logstash-syslog.conf**

# 

# Pipeline configuration string for the main pipeline

# 

# config.string:

# 

# config.test\_and\_exit: false

# 

# config.reload.automatic: false

# 

# config.reload.interval: 3s

# 

# config.debug: false

# 

# When enabled, process escaped characters such as \n and " in strings in the

# pipeline configuration files.

# 

# config.support\_escapes: false

# 

# ------------ Module Settings ---------------

# Define modules here. Modules definitions must be defined as an array.

# The simple way to see this is to prepend each `name` with a `-`, and keep

# all associated variables under the `name` they are associated with, and

# above the next, like this:

# 

# modules:

# - name: MODULE\_NAME

# var.PLUGINTYPE1.PLUGINNAME1.KEY1: VALUE

# var.PLUGINTYPE1.PLUGINNAME1.KEY2: VALUE

# var.PLUGINTYPE2.PLUGINNAME1.KEY1: VALUE

# var.PLUGINTYPE3.PLUGINNAME3.KEY1: VALUE

# 

# Module variable names must be in the format of

# 

# var.PLUGIN\_TYPE.PLUGIN\_NAME.KEY

# 

# modules:

# 

# ------------ Cloud Settings ---------------

# Define Elastic Cloud settings here.

# Format of cloud.id is a base64 value e.g. dXMtZWFzdC0xLmF3cy5mb3VuZC5pbyRub3RhcmVhbCRpZGVudGlmaWVy

# and it may have an label prefix e.g. staging:dXMtZ...

# This will overwrite 'var.elasticsearch.hosts' and 'var.kibana.host'

# cloud.id:

# 

# Format of cloud.auth is: :

# This is optional

# If supplied this will overwrite 'var.elasticsearch.username' and 'var.elasticsearch.password'

# If supplied this will overwrite 'var.kibana.username' and 'var.kibana.password'

# cloud.auth: elastic:

# 

# ------------ Queuing Settings --------------

# 

# queue.type: memory

# 

# If using queue.type: persisted, the directory path where the data files will be stored.

# Default is path.data/queue

# 

# path.queue:

# 

# If using queue.type: persisted, the page data files size. The queue data consists of

# append-only data files separated into pages. Default is 250mb

# 

# queue.page\_capacity: 250mb

# 

# If using queue.type: persisted, the maximum number of unread events in the queue.

# Default is 0 (unlimited)

# 

# queue.max\_events: 0

# 

# Default is 1024mb or 1gb

# queue.max\_bytes: 1024mb

# 

# If using queue.type: persisted, the maximum number of acked events before forcing a checkpoint

# Default is 1024, 0 for unlimited

# 

# queue.checkpoint.acks: 1024

# 

# Default is 1024, 0 for unlimited

# 

# queue.checkpoint.writes: 1024

# 

# If using queue.type: persisted, the interval in milliseconds when a checkpoint is forced on the head page

# Default is 1000, 0 for no periodic checkpoint.

# 

# queue.checkpoint.interval: 1000

# 

# ------------ Dead-Letter Queue Settings --------------

# Flag to turn on dead-letter queue.

# 

# dead\_letter\_queue.enable: false

# Default is 1024mb

# dead\_letter\_queue.max\_bytes: 1024mb

# If using dead\_letter\_queue.enable: true, the directory path where the data files will be stored.

# Default is path.data/dead\_letter\_queue

# 

# path.dead\_letter\_queue:

# 

# ------------ Metrics Settings --------------

# 

# Bind address for the metrics REST endpoint

# 

# http.host: "127.0.0.1"

# 

# Bind port for the metrics REST endpoint, this option also accept a range

# (9600-9700) and logstash will pick up the first available ports.

# 

# http.port: 9600-9700

# 

# ------------ Debugging Settings --------------

# 

# Options for log.level:

# \* fatal

# \* error

# \* warn

# \* info (default)

# \* debug

# \* trace

# 

# log.level: info

**path.logs: /var/log/logstash**

# 

# ------------ Other Settings --------------

# 

# Where to find custom plugins

# path.plugins: []

* * *

root@elk-log:~#  
root@elk-log:~#

## root@elk-log:~# cat /etc/logstash/conf.d/logstash-syslog.conf

## input { beats { port =\> 5044 ssl =\> false ssl\_certificate =\> "/etc/pki/tls/certs/logstash-forwarder.crt" ssl\_key =\> "/etc/pki/tls/private/logstash-forwarder.key" } } filter { if [type] == "syslog" { grok { match =\> { "message" =\> "%{SYSLOGTIMESTAMP:syslog\_timestamp} %{SYSLOGHOST:syslog\_hostname} %{DATA:syslog\_program}(?:[%{POSINT:syslog\_pid}])?: %{GREEDYDATA:syslog\_message}" } add\_field =\> ["received\_at", "%{@timestamp}"] add\_field =\> ["received\_from", "%{host}"] add\_field =\> ["received\_program", "%{syslog\_program}"] add\_field =\> ["received\_pid", "%{syslog\_pid}"] } syslog\_pri { } date { match =\> ["syslog\_timestamp", "MMM dd HH:mm:ss", "MMM dd HH:mm:ss"] } } } output { elasticsearch { hosts =\> ["localhost:9200"] sniffing =\> true manage\_template =\> false **index =\> "check\_ELK-%{+YYYY.MM.dd}"** document\_type =\> "%{[@metadata][type]}" } }

Regards,  
Ashish Khulbe

---

<div class="post-metadata">

**Author:** ![ashish\_khulbe](https://avatars.discourse-cdn.com/v4/letter/a/ea5d25/32.png) [@ashish\_khulbe](https://discuss.elastic.co/u/ashish_khulbe)\
**Post date:** [March 13, 2018, 9:29am UTC](https://discuss.elastic.co/t/same-filter-which-is-working-for-2-x-in-elk-not-working-for-6-1-3/123176/8 "2018-03-13T09:29:24Z")

</div>

Hi Magnus,

Filebeat Configuration:

* * *

root@filebeat:~# cat /etc/filebeat/filebeat.yml  
##:q#################### Filebeat Configuration Example #########################

# This file is an example configuration file highlighting only the most common

# options. The filebeat.reference.yml file from the same directory contains all the

# supported options with more comments. You can use it as a reference.

# 

# You can find the full configuration reference here:

# [https://www.elastic.co/guide/en/beats/filebeat/index.html](https://www.elastic.co/guide/en/beats/filebeat/index.html)

# For more available modules and options, please see the filebeat.reference.yml sample

# configuration file.

#=========================== Filebeat prospectors =============================

filebeat.prospectors:

# Each - is a prospector. Most options can be set at the prospector level, so

# you can use different prospectors for various configurations.

# Below are the prospector specific configurations.

- type: log

#============================= Filebeat modules ===============================

filebeat.config.modules:

# Glob pattern for configuration loading

path: /etc/filebeat/modules.d/\*.yml

# Set to true to enable config reloading

reload.enabled: false

# Period on which files under path should be checked for changes

#reload.period: 10s

#==================== Elasticsearch template setting ==========================

setup.template.settings:  
index.number\_of\_shards: 3  
#index.codec: best\_compression  
#\_source.enabled: false

#================================ General =====================================

# The name of the shipper that publishes the network data. It can be used to group

# all the transactions sent by a single shipper in the web interface.

#name:

# The tags of the shipper are included in their own field with each

# transaction published.

#tags: ["service-X", "web-tier"]

# Optional fields that you can specify to add additional information to the

# output.

#fields:

# env: staging

#============================== Dashboards =====================================

# These settings control loading the sample dashboards to the Kibana index. Loading

# the dashboards is disabled by default and can be enabled either by setting the

# options here, or by using the `-setup` CLI flag or the `setup` command.

#setup.dashboards.enabled: false

# The URL from where to download the dashboards archive. By default this URL

# has a value which is computed based on the Beat name and version. For released

# versions, this URL points to the dashboard archive on the [artifacts.elastic.co](http://artifacts.elastic.co)

# website.

#setup.dashboards.url:

#============================== Kibana =====================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.

# This requires a Kibana endpoint configuration.

#setup.kibana:

# Kibana Host

# Scheme and port can be left out and will be set to the default (http and 5601)

# In case you specify and additional path, the scheme is required: [http://localhost:5601/path](http://localhost:5601/path)

# IPv6 addresses should always be defined as: https://[2001:db8::1]:5601

#host: "localhost:5601"

#============================= Elastic Cloud ==================================

# These settings simplify using filebeat with the Elastic Cloud ([https://cloud.elastic.co/](https://cloud.elastic.co/)).

# The cloud.id setting overwrites the `output.elasticsearch.hosts` and

# `setup.kibana.host` options.

# You can find the `cloud.id` in the Elastic Cloud web UI.

#cloud.id:

#================================ Outputs =====================================

# Configure what output to use when sending the data collected by the beat.

#-------------------------- Elasticsearch output ------------------------------  
#output.elasticsearch:

# Array of hosts to connect to.

# hosts: ["localhost:9200"]

# Optional protocol and basic auth credentials.

#protocol: "https"  
#username: "elastic"  
#password: "changeme"

#----------------------------- Logstash output --------------------------------  
output.logstash:

# The Logstash hosts

hosts: ["20.20.20.251:5044"]

# Optional SSL. By default is off.

# List of root certificates for HTTPS server verifications

#ssl.certificate\_authorities: ["/etc/pki/root/ca.pem"]  
#ssl.certificate\_authorities: ["/etc/pki/tls/certs/logstash-forwarder.crt"]

# Certificate for SSL client authentication

#ssl.certificate: "/etc/pki/client/cert.pem"

# Client Certificate Key

#ssl.key: "/etc/pki/client/cert.key"

#================================ Logging =====================================

# Sets log level. The default log level is info.

# Available log levels are: critical, error, warning, info, debug

logging.level: debug

# To enable all selectors use ["\*"]. Examples of other selectors are "beat",

# "publish", "service".

## #logging.selectors: ["\*"] root@filebeat:~#

Regards,  
Ashish Khulbe

---

<div class="post-metadata">

**Author:** ![ashish\_khulbe](https://avatars.discourse-cdn.com/v4/letter/a/ea5d25/32.png) [@ashish\_khulbe](https://discuss.elastic.co/u/ashish_khulbe)\
**Post date:** [March 14, 2018, 1:03pm UTC](https://discuss.elastic.co/t/same-filter-which-is-working-for-2-x-in-elk-not-working-for-6-1-3/123176/9 "2018-03-14T13:03:53Z")

</div>

Hi Magnus,

Only Fields populated in elasticsearch and kibana are :  
@timestamp  
t @version  
t \_id  
t \_index

# \_score

t \_type  
t beat.hostname  
t beat.name  
t beat.version  
t host  
t message

# offset

t prospector.type  
t source

whereas the filter i used has :

filter {  
if [type] == "tantem.log" {  
grok  
{  
match =\> { "message" =\> "[%{LOGLEVEL:Severity}]:[%{SYSLOGHOST:Host\_Name}]:[%{DATA:User\_Name}]:[%{SYSLOGTIMESTAMP:timestamp}]:[%{DATA:Session\_ID}]:[%{DATA:Function\_Name}]:[%{DATA:Event}]:[%{GREEDYDATA:message}]" }  
}  
syslog\_pri { }  
date  
{  
match =\> ["syslog\_timestamp", "MMM dd HH:mm:ss", "MMM dd HH:mm:ss"]  
}  
}

Regards,  
Ashish Khulbe

---

<div class="post-metadata">

**Author:** ![ashish\_khulbe](https://avatars.discourse-cdn.com/v4/letter/a/ea5d25/32.png) [@ashish\_khulbe](https://discuss.elastic.co/u/ashish_khulbe)\
**Post date:** [March 14, 2018, 1:07pm UTC](https://discuss.elastic.co/t/same-filter-which-is-working-for-2-x-in-elk-not-working-for-6-1-3/123176/10 "2018-03-14T13:07:43Z")

</div>

I have not found, but just a question, Is there any field or option defined enabling the custom fields in index pattern for 6.1.3. please help i am blocked.

I am using same grok filters even for Windows machine and it is running perfectly fine.

---

<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:** [April 11, 2018, 1:07pm UTC](https://discuss.elastic.co/t/same-filter-which-is-working-for-2-x-in-elk-not-working-for-6-1-3/123176/11 "2018-04-11T13:07:53Z")

</div>

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