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

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

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.

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/)

    match => { "message" => "[%{LOGLEVEL:Severity}]:[%{SYSLOGHOST:Host_Name}]:[%{DATA:User_Name}]:[%{SYSLOGTIMESTAMP:timestamp}]:[%{DATA:Session_ID}]:[%{DATA:Function_Name}]:[%{DATA:Event}]:[%{GREEDYDATA:message}]" }

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

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 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.

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

--> 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.

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

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

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

    Change to true to enable this prospector configuration.

    enabled: true

    Paths that should be crawled and fetched. Glob based paths.

    paths:
    #- /var/log/tantem/tantem.log

    • /var/log/syslog
      #- c:\programdata\elasticsearch\logs*

    Exclude lines. A list of regular expressions to match. It drops the lines that are

    matching any regular expression from the list.

    #exclude_lines: ['^DBG']

    Include lines. A list of regular expressions to match. It exports the lines that are

    matching any regular expression from the list.

    #include_lines: ['^ERR', '^WARN']

    Exclude files. A list of regular expressions to match. Filebeat drops the files that

    are matching any regular expression from the list. By default, no files are dropped.

    #exclude_files: ['.gz$']

    Optional additional fields. These fields can be freely picked

    to add additional information to the crawled log files for filtering

    #fields:

    level: debug

    review: 1

    Multiline options

    Mutiline can be used for log messages spanning multiple lines. This is common

    for Java Stack Traces or C-Line Continuation

    The regexp Pattern that has to be matched. The example pattern matches all lines starting with [

    #multiline.pattern: ^[

    Defines if the pattern set under pattern should be negated or not. Default is false.

    #multiline.negate: false

    Match can be set to "after" or "before". It is used to define if lines should be append to a pattern

    that was (not) matched before or after or as long as a pattern is not matched based on negate.

    Note: After is the equivalent to previous and before is the equivalent to to next in Logstash

    #multiline.match: after

#============================= 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

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

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/).

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

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

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.

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