Lost data in kibana but show in syslog logstash

Elastic Stack Logstash
1

I have conf file in logstash like this

input {
  beats {
    host => "0.0.0.0"
    port => 5044
    ssl => false
  }
}

filter {
  
    if [fileset][name] == "auth" {
      grok {
    	match => { "message" => "%{SYSLOGTIMESTAMP:[system][auth][timestamp]} %{SYSLOGHOST:[system][auth][hostname]} sshd(?:\[%{POSINT:[system][auth][pid]}\])?: %{DATA:[system][auth][ssh][event]} for %{DATA:[system][auth][user]} from %{IPORHOST:[system][auth][ssh][ip]} port %{NUMBER:[system][auth][ssh][port]} ssh2" }

	add_field => [ "activity","SSH Logins" ]

    	add_tag => "linux_auth"

      }
      if "_grokparsefailure" in [tags] { drop {} }

      date {
        match => [ "[system][auth][timestamp]", "MMM  d HH:mm:ss", "MMM dd HH:mm:ss" ]
      }

    }
    else if [fileset][name] == "syslog" {
      grok {
      	match => { "message" => "%{SYSLOGTIMESTAMP:syslog_timestamp} %{SYSLOGHOST:syslog_hostname} %{DATA:syslog_program}(?:\[%{POSINT:syslog_pid}\])?: %{GREEDYDATA:syslog_message}" }
	add_tag => "linux_syslog"
    }
      
    }
  
}

output {
  elasticsearch {
    hosts => ["192.168.186.157:9200"]
    manage_template => false
    index => "%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}"
  }
  stdout { codec => rubydebug }
}

Then I send auth.log and syslog to logstash.
Here is some auth.log for you to check

Jul 16 06:58:59 kali sshd[5806]: Failed password for kali from 192.168.186.149 port 54760 ssh2
Jul 16 06:58:59 kali sshd[5812]: Failed password for kali from 192.168.186.149 port 54774 ssh2
Jul 16 06:58:59 kali sshd[5807]: Failed password for kali from 192.168.186.149 port 54762 ssh2
Jul 16 06:58:59 kali sshd[5809]: Failed password for kali from 192.168.186.149 port 54766 ssh2
Jul 16 06:58:59 kali sshd[5808]: Failed password for kali from 192.168.186.149 port 54764 ssh2
Jul 16 06:58:59 kali sshd[5811]: Failed password for kali from 192.168.186.149 port 54772 ssh2
Jul 16 06:59:00 kali sshd[5802]: Connection closed by authenticating user kali 192.168.186.149 port 54752 [preauth]
Jul 16 06:59:00 kali sshd[5802]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 16 06:59:00 kali sshd[5802]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 16 06:59:00 kali sshd[5801]: Connection closed by authenticating user kali 192.168.186.149 port 54750 [preauth]
Jul 16 06:59:00 kali sshd[5801]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 16 06:59:00 kali sshd[5801]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 16 06:59:00 kali sshd[5799]: Connection closed by authenticating user kali 192.168.186.149 port 54746 [preauth]
Jul 16 06:59:00 kali sshd[5799]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 16 06:59:00 kali sshd[5799]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 16 06:59:00 kali sshd[5800]: error: maximum authentication attempts exceeded for kali from 192.168.186.149 port 54748 ssh2 [preauth]
Jul 16 06:59:00 kali sshd[5800]: Disconnecting authenticating user kali 192.168.186.149 port 54748: Too many authentication failures [preauth]
Jul 16 06:59:00 kali sshd[5800]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 16 06:59:00 kali sshd[5800]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 16 06:59:00 kali sshd[5803]: Connection closed by authenticating user kali 192.168.186.149 port 54754 [preauth]
Jul 16 06:59:00 kali sshd[5803]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 16 06:59:00 kali sshd[5803]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 16 06:59:00 kali sshd[5804]: Connection closed by authenticating user kali 192.168.186.149 port 54756 [preauth]
Jul 16 06:59:00 kali sshd[5804]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 16 06:59:00 kali sshd[5804]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 16 06:59:00 kali sshd[5798]: Connection closed by authenticating user kali 192.168.186.149 port 54744 [preauth]
Jul 16 06:59:00 kali sshd[5798]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 16 06:59:00 kali sshd[5798]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 16 06:59:00 kali sshd[5805]: Connection closed by authenticating user kali 192.168.186.149 port 54758 [preauth]
Jul 16 06:59:00 kali sshd[5805]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 16 06:59:00 kali sshd[5805]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 16 06:59:00 kali sshd[5806]: Connection closed by authenticating user kali 192.168.186.149 port 54760 [preauth]
Jul 16 06:59:00 kali sshd[5806]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 16 06:59:00 kali sshd[5806]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 16 06:59:00 kali sshd[5812]: Connection closed by authenticating user kali 192.168.186.149 port 54774 [preauth]
Jul 16 06:59:00 kali sshd[5812]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali

I have shown my syslog where logstash install and it's in there

Jul 17 19:02:33 ubuntu logstash[3645]:       "@version" => "1",
Jul 17 19:02:33 ubuntu logstash[3645]:           "host" => {
Jul 17 19:02:33 ubuntu logstash[3645]:                    "os" => {
Jul 17 19:02:33 ubuntu logstash[3645]:             "platform" => "kali",
Jul 17 19:02:33 ubuntu logstash[3645]:              "version" => "2020.3",
Jul 17 19:02:33 ubuntu logstash[3645]:               "kernel" => "5.7.0-kali1-amd64",
Jul 17 19:02:33 ubuntu logstash[3645]:                 "type" => "linux",
Jul 17 19:02:33 ubuntu logstash[3645]:                 "name" => "Kali GNU/Linux",
Jul 17 19:02:33 ubuntu logstash[3645]:               "family" => "",
Jul 17 19:02:33 ubuntu logstash[3645]:             "codename" => "kali-rolling"
Jul 17 19:02:33 ubuntu logstash[3645]:         },
Jul 17 19:02:33 ubuntu logstash[3645]:                    "ip" => [
Jul 17 19:02:33 ubuntu logstash[3645]:             [0] "192.168.186.151",
Jul 17 19:02:33 ubuntu logstash[3645]:             [1] "fe80::20c:29ff:fed0:4beb"
Jul 17 19:02:33 ubuntu logstash[3645]:         ],
Jul 17 19:02:33 ubuntu logstash[3645]:                  "name" => "kali",
Jul 17 19:02:33 ubuntu logstash[3645]:              "hostname" => "kali",
Jul 17 19:02:33 ubuntu logstash[3645]:          "architecture" => "x86_64",
Jul 17 19:02:33 ubuntu logstash[3645]:                   "mac" => [
Jul 17 19:02:33 ubuntu logstash[3645]:             [0] "00:0c:29:d0:4b:eb"
Jul 17 19:02:33 ubuntu logstash[3645]:         ],
Jul 17 19:02:33 ubuntu logstash[3645]:                    "id" => "0c42c6c017eb4a808d334aedb1e3f72f",
Jul 17 19:02:33 ubuntu logstash[3645]:         "containerized" => false
Jul 17 19:02:33 ubuntu logstash[3645]:     },
Jul 17 19:02:33 ubuntu logstash[3645]:        "message" => "Jul 17 08:02:30 kali sshd[1195]: Failed password for kali from 192.168.186.149 port 60216 ssh2"
Jul 17 19:02:33 ubuntu logstash[3645]: }
Jul 17 19:02:33 ubuntu logstash[3645]: {
Jul 17 19:02:33 ubuntu logstash[3645]:        "fileset" => {
Jul 17 19:02:33 ubuntu logstash[3645]:         "name" => "auth"
Jul 17 19:02:33 ubuntu logstash[3645]:     },
Jul 17 19:02:33 ubuntu logstash[3645]:        "service" => {
Jul 17 19:02:33 ubuntu logstash[3645]:         "type" => "system"
Jul 17 19:02:33 ubuntu logstash[3645]:     },
Jul 17 19:02:33 ubuntu logstash[3645]:          "event" => {
Jul 17 19:02:33 ubuntu logstash[3645]:         "timezone" => "-04:00",
Jul 17 19:02:33 ubuntu logstash[3645]:          "dataset" => "system.auth",
Jul 17 19:02:33 ubuntu logstash[3645]:           "module" => "system"
Jul 17 19:02:33 ubuntu logstash[3645]:     },
Jul 17 19:02:33 ubuntu logstash[3645]:           "tags" => [
Jul 17 19:02:33 ubuntu logstash[3645]:         [0] "beats_input_codec_plain_applied",
Jul 17 19:02:33 ubuntu logstash[3645]:         [1] "linux_auth"
Jul 17 19:02:33 ubuntu logstash[3645]:     ],
Jul 17 19:02:33 ubuntu logstash[3645]:     "@timestamp" => 2021-07-17T01:02:30.000Z,
Jul 17 19:02:33 ubuntu logstash[3645]:         "system" => {
Jul 17 19:02:33 ubuntu logstash[3645]:         "auth" => {
Jul 17 19:02:33 ubuntu logstash[3645]:                   "ssh" => {
Jul 17 19:02:33 ubuntu logstash[3645]:                 "event" => "Failed password",
Jul 17 19:02:33 ubuntu logstash[3645]:                    "ip" => "192.168.186.149",
Jul 17 19:02:33 ubuntu logstash[3645]:                  "port" => "60194"
Jul 17 19:02:33 ubuntu logstash[3645]:             },
Jul 17 19:02:33 ubuntu logstash[3645]:             "timestamp" => "Jul 17 08:02:30",
Jul 17 19:02:33 ubuntu logstash[3645]:                   "pid" => "1189",
Jul 17 19:02:33 ubuntu logstash[3645]:                  "user" => "kali",
Jul 17 19:02:33 ubuntu logstash[3645]:              "hostname" => "kali"
Jul 17 19:02:33 ubuntu logstash[3645]:         }
Jul 17 19:02:33 ubuntu logstash[3645]:     },
Jul 17 19:02:33 ubuntu logstash[3645]:       "activity" => "SSH Logins",
Jul 17 19:02:33 ubuntu logstash[3645]:            "log" => {
Jul 17 19:02:33 ubuntu logstash[3645]:           "file" => {
Jul 17 19:02:33 ubuntu logstash[3645]:             "path" => "/var/log/auth.log"
Jul 17 19:02:33 ubuntu logstash[3645]:         },
Jul 17 19:02:33 ubuntu logstash[3645]:         "offset" => 330238
Jul 17 19:02:33 ubuntu logstash[3645]:     },
Jul 17 19:02:33 ubuntu logstash[3645]:          "input" => {
Jul 17 19:02:33 ubuntu logstash[3645]:         "type" => "log"
Jul 17 19:02:33 ubuntu logstash[3645]:     },
Jul 17 19:02:33 ubuntu logstash[3645]:          "agent" => {
Jul 17 19:02:33 ubuntu logstash[3645]:         "ephemeral_id" => "2cc4e8df-1218-48c4-9b41-aa77c62a356e",
Jul 17 19:02:33 ubuntu logstash[3645]:                 "type" => "filebeat",
Jul 17 19:02:33 ubuntu logstash[3645]:              "version" => "7.13.1",
Jul 17 19:02:33 ubuntu logstash[3645]:                 "name" => "kali",
Jul 17 19:02:33 ubuntu logstash[3645]:             "hostname" => "kali",
Jul 17 19:02:33 ubuntu logstash[3645]:                   "id" => "f152b60c-88cf-41a2-9a23-0f0119532b35"
Jul 17 19:02:33 ubuntu logstash[3645]:     },
Jul 17 19:02:33 ubuntu logstash[3645]:            "ecs" => {
Jul 17 19:02:33 ubuntu logstash[3645]:         "version" => "1.9.0"
Jul 17 19:02:33 ubuntu logstash[3645]:     },
Jul 17 19:02:35 ubuntu logstash[3645]: [2021-07-17T19:02:35,582][DEBUG][logstash.outputs.elasticsearch][main][b139133fa702504a3c994dbba5834e0ddce2f41e64742a611bb9239ae1df99f4] Sending final bulk request for batch. {:action_count=>4, :payload_size=>5192, :content_length=>5192, :batch_offset=>0}
Jul 17 19:02:35 ubuntu logstash[3645]: {
Jul 17 19:02:35 ubuntu logstash[3645]:        "fileset" => {

It got the log, but why my Kibana didn't show that? It just shows syslog but not any auth.log.

Does anyone know how to fix this? I really need your help!

2

Your grok looks good AFAICT.

Hmmm I suspect that fileset.name may not be correct for your auth what does your filebeat.yml input section look like?

3

My filebeat.yml

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

#filebeat.inputs:

# Each - is an input. Most options can be set at the input level, so
# you can use different inputs for various configurations.
# Below are the input specific configurations.

#- type: log

  # Change to true to enable this input configuration.
  #enabled: true

  # Paths that should be crawled and fetched. Glob based paths.
  #paths:
    #- /var/log/*.log
    #- 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

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

# filestream is an experimental input. It is going to replace log input in the future.
#- type: filestream

  # Change to true to enable this input configuration.
  #enabled: false

  # Paths that should be crawled and fetched. Glob based paths.
  #paths:
    #- /var/log/*.log
    #- 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.
  #prospector.scanner.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

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

filebeat.config.modules:
  # Glob pattern for configuration loading
  path: ${path.config}/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: 1
  #index.codec: best_compression
  #_source.enabled: false
setup.ilm.overwrite: true

# ================================== 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` 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: "192.168.186.147:5601"

  # Kibana Space ID
  # ID of the Kibana Space into which the dashboards should be loaded. By default,
  # the Default Space will be used.
  #space.id:

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

# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
#cloud.auth:

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

  # Protocol - either `http` (default) or `https`.
  #protocol: "https"

  # Authentication credentials - either API key or username/password.
  #api_key: "id:api_key"
  #username: "elastic"
  #password: "changeme"

# ------------------------------ Logstash Output -------------------------------
output.logstash:
  # The Logstash hosts
  hosts: ["192.168.186.157:5044"]
  index: "filebeat-192.168.186.146"
  bulk_max_size: 1024
  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

  # Certificate for SSL client authentication
  #ssl.certificate: "/etc/pki/client/cert.pem"

  # Client Certificate Key
  #ssl.key: "/etc/pki/client/cert.key"

# ================================= Processors =================================
processors:
  - add_host_metadata:
      when.not.contains.tags: forwarded
  - add_cloud_metadata: ~
  - add_docker_metadata: ~
  - add_kubernetes_metadata: ~

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

# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
#logging.level: debug

# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publisher", "service".
#logging.selectors: ["*"]

# ============================= X-Pack Monitoring ==============================
# Filebeat can export internal metrics to a central Elasticsearch monitoring
# cluster.  This requires xpack monitoring to be enabled in Elasticsearch.  The
# reporting is disabled by default.

# Set to true to enable the monitoring reporter.
#monitoring.enabled: false

# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
# Filebeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
#monitoring.cluster_uuid:

# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:

# ============================== Instrumentation ===============================

# Instrumentation support for the filebeat.
#instrumentation:
    # Set to true to enable instrumentation of filebeat.
    #enabled: false

    # Environment in which filebeat is running on (eg: staging, production, etc.)
    #environment: ""

    # APM Server hosts to report instrumentation results to.
    #hosts:
    #  - http://localhost:8200

    # API Key for the APM Server(s).
    # If api_key is set then secret_token will be ignored.
    #api_key:

    # Secret token for the APM Server(s).
    #secret_token:


# ================================= Migration ==================================

# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true

My modules.d/system.yml

# Module: system
# Docs: https://www.elastic.co/guide/en/beats/filebeat/7.x/filebeat-module-system.html

- module: system
  # Syslog
  syslog:
    enabled: true

    # Set custom paths for the log files. If left empty,
    # Filebeat will choose the paths depending on your OS.
    #var.paths:

  # Authorization logs
  auth:
    enabled: true

    # Set custom paths for the log files. If left empty,
    # Filebeat will choose the paths depending on your OS.
    #var.paths:

But maybe it doesn't relate to filebeat 'cause syslog in logstash host have log after filter (I posted in top), and it has fileset.name

The only problem is kibana don't show the log in auth.log after logstash filter it.

4

Perhaps your auth logs are not in the default location?

Why don't you try explicitly defining the path.

If you don't filter in logstash do you see the auth logs? In other words are you sure they're getting to logstash?

5

I've tested when didn't have filter in logstash, it received all the log well. So I don't think the path is necessary.

And I am pretty sure that logstash received the log and filter it. I read in a blog https://kifarunix.com/how-to-debug-logstash-grok-filters/ and it has a command to test grok is /usr/share/logstash/bin/logstash -f /etc/logstash/conf.d/ssh-authentication.conf --path.settings /etc/logstash/. When I get log from filebeat like

Jul 17 13:56:06 kali sshd[1585]: Failed password for kali from 192.168.186.149 port 33604 ssh2
Jul 17 13:56:06 kali sshd[1587]: Failed password for kali from 192.168.186.149 port 33608 ssh2
Jul 17 13:56:06 kali sshd[1586]: Failed password for kali from 192.168.186.149 port 33602 ssh2
Jul 17 13:56:06 kali sshd[1588]: Failed password for kali from 192.168.186.149 port 33610 ssh2
Jul 17 13:56:06 kali sshd[1594]: Failed password for kali from 192.168.186.149 port 33622 ssh2

after stop logstash and run that command and it's show

[2021-07-18T00:56:13,815][DEBUG][logstash.outputs.elasticsearch][main][b139133fa702504a3c994dbba5834e0ddce2f41e64742a611bb9239ae1df99f4] Sending final bulk request for batch. {:action_count=>8, :payload_size=>10176, :content_length=>10176, :batch_offset=>0}
{
          "tags" => [
        [0] "beats_input_codec_plain_applied",
        [1] "linux_auth"
    ],
         "event" => {
         "dataset" => "system.auth",
        "timezone" => "-04:00",
          "module" => "system"
    },
       "service" => {
        "type" => "system"
    },
           "log" => {
        "offset" => 325463,
          "file" => {
            "path" => "/var/log/auth.log"
        }
    },
         "input" => {
        "type" => "log"
    },
           "ecs" => {
        "version" => "1.9.0"
    },
        "system" => {
        "auth" => {
                  "pid" => "1591",
                  "ssh" => {
                   "ip" => "192.168.186.149",
                "event" => "Failed password",
                 "port" => "33618"
            },
                 "user" => "kali",
            "timestamp" => "Jul 17 13:56:10",
             "hostname" => "kali"
        }
    },
    "@timestamp" => 2021-07-17T06:56:10.000Z,
       "message" => "Jul 17 13:56:10 kali sshd[1591]: Failed password for kali from 192.168.186.149 port 33618 ssh2",
      "@version" => "1",
          "host" => {
                   "id" => "0c42c6c017eb4a808d334aedb1e3f72f",
        "containerized" => false,
                  "mac" => [
            [0] "00:0c:29:88:f6:b8"
        ],
                   "ip" => [
            [0] "192.168.186.146",
            [1] "fe80::20c:29ff:fe88:f6b8"
        ],
                 "name" => "kali",
         "architecture" => "x86_64",
                   "os" => {
             "version" => "2020.3",
              "kernel" => "5.7.0-kali1-amd64",
            "platform" => "kali",
              "family" => "",
                "name" => "Kali GNU/Linux",
            "codename" => "kali-rolling",
                "type" => "linux"
        },
             "hostname" => "kali"
    },
         "agent" => {
             "version" => "7.13.1",
                  "id" => "f152b60c-88cf-41a2-9a23-0f0119532b35",
        "ephemeral_id" => "ff70babe-99ee-43f0-98e0-eaa15daa3dba",
                "name" => "kali",
                "type" => "filebeat",
            "hostname" => "kali"
    },
       "fileset" => {
        "name" => "auth"
    },
      "activity" => "SSH Logins"
}
{
          "tags" => [
        [0] "beats_input_codec_plain_applied",
        [1] "linux_auth"
    ],
         "event" => {
         "dataset" => "system.auth",
        "timezone" => "-04:00",
          "module" => "system"
    },
       "service" => {
        "type" => "system"
    },
           "log" => {
        "offset" => 325558,
          "file" => {
            "path" => "/var/log/auth.log"
        }
    },
         "input" => {
        "type" => "log"
    },
           "ecs" => {
        "version" => "1.9.0"
    },
        "system" => {
        "auth" => {
                  "pid" => "1595",
                  "ssh" => {
                   "ip" => "192.168.186.149",
                "event" => "Failed password",
                 "port" => "33624"
            },
                 "user" => "kali",
            "timestamp" => "Jul 17 13:56:10",
             "hostname" => "kali"
        }
    },
    "@timestamp" => 2021-07-17T06:56:10.000Z,
       "message" => "Jul 17 13:56:10 kali sshd[1595]: Failed password for kali from 192.168.186.149 port 33624 ssh2",
      "@version" => "1",
          "host" => {
                   "id" => "0c42c6c017eb4a808d334aedb1e3f72f",
        "containerized" => false,
                  "mac" => [
            [0] "00:0c:29:88:f6:b8"
        ],
                   "ip" => [
            [0] "192.168.186.146",
            [1] "fe80::20c:29ff:fe88:f6b8"
        ],
                 "name" => "kali",
         "architecture" => "x86_64",
                   "os" => {
             "version" => "2020.3",
              "kernel" => "5.7.0-kali1-amd64",
            "platform" => "kali",
              "family" => "",
                "name" => "Kali GNU/Linux",
            "codename" => "kali-rolling",
                "type" => "linux"
        },
             "hostname" => "kali"
    },
         "agent" => {
             "version" => "7.13.1",
                  "id" => "f152b60c-88cf-41a2-9a23-0f0119532b35",
        "ephemeral_id" => "ff70babe-99ee-43f0-98e0-eaa15daa3dba",
                "name" => "kali",
                "type" => "filebeat",
            "hostname" => "kali"
    },
       "fileset" => {
        "name" => "auth"
    },
      "activity" => "SSH Logins"
}
{
          "tags" => [
        [0] "beats_input_codec_plain_applied",
        [1] "linux_auth"
    ],
         "event" => {
         "dataset" => "system.auth",
        "timezone" => "-04:00",
          "module" => "system"
    },
       "service" => {
        "type" => "system"
    },
           "log" => {
        "offset" => 325653,
          "file" => {
            "path" => "/var/log/auth.log"
        }
    },
         "input" => {
        "type" => "log"
    },
           "ecs" => {
        "version" => "1.9.0"
    },
        "system" => {
        "auth" => {
                  "pid" => "1592",
                  "ssh" => {
                   "ip" => "192.168.186.149",
                "event" => "Failed password",
                 "port" => "33616"
            },
                 "user" => "kali",
            "timestamp" => "Jul 17 13:56:10",
             "hostname" => "kali"
        }
    },
    "@timestamp" => 2021-07-17T06:56:10.000Z,
       "message" => "Jul 17 13:56:10 kali sshd[1592]: Failed password for kali from 192.168.186.149 port 33616 ssh2",
      "@version" => "1",
          "host" => {
                   "id" => "0c42c6c017eb4a808d334aedb1e3f72f",
        "containerized" => false,
                  "mac" => [
            [0] "00:0c:29:88:f6:b8"
        ],
                   "ip" => [
            [0] "192.168.186.146",
            [1] "fe80::20c:29ff:fe88:f6b8"
        ],
                 "name" => "kali",
         "architecture" => "x86_64",
                   "os" => {
             "version" => "2020.3",
              "kernel" => "5.7.0-kali1-amd64",
            "platform" => "kali",
              "family" => "",
                "name" => "Kali GNU/Linux",
            "codename" => "kali-rolling",
                "type" => "linux"
        },
             "hostname" => "kali"
    },
         "agent" => {
             "version" => "7.13.1",
                  "id" => "f152b60c-88cf-41a2-9a23-0f0119532b35",
        "ephemeral_id" => "ff70babe-99ee-43f0-98e0-eaa15daa3dba",
                "name" => "kali",
                "type" => "filebeat",
            "hostname" => "kali"
    },
       "fileset" => {
        "name" => "auth"
    },
      "activity" => "SSH Logins"
}
{
          "tags" => [
        [0] "beats_input_codec_plain_applied",
        [1] "linux_auth"
    ],
         "event" => {
         "dataset" => "system.auth",
        "timezone" => "-04:00",
          "module" => "system"
    },
       "service" => {
        "type" => "system"
    },
           "log" => {
        "offset" => 325748,
          "file" => {
            "path" => "/var/log/auth.log"
        }
    },
         "input" => {
        "type" => "log"
    },
           "ecs" => {
        "version" => "1.9.0"
    },
        "system" => {
        "auth" => {
                  "pid" => "1590",
                  "ssh" => {
                   "ip" => "192.168.186.149",
                "event" => "Failed password",
                 "port" => "33614"
            },
                 "user" => "kali",
            "timestamp" => "Jul 17 13:56:10",
             "hostname" => "kali"
        }
    },
    "@timestamp" => 2021-07-17T06:56:10.000Z,
       "message" => "Jul 17 13:56:10 kali sshd[1590]: Failed password for kali from 192.168.186.149 port 33614 ssh2",
      "@version" => "1",
          "host" => {
                   "id" => "0c42c6c017eb4a808d334aedb1e3f72f",
        "containerized" => false,
                  "mac" => [
            [0] "00:0c:29:88:f6:b8"
        ],
                   "ip" => [
            [0] "192.168.186.146",
            [1] "fe80::20c:29ff:fe88:f6b8"
        ],
                 "name" => "kali",
         "architecture" => "x86_64",
                   "os" => {
             "version" => "2020.3",
              "kernel" => "5.7.0-kali1-amd64",
            "platform" => "kali",
                "name" => "Kali GNU/Linux",
              "family" => "",
            "codename" => "kali-rolling",
                "type" => "linux"
        },
             "hostname" => "kali"
    },
         "agent" => {
             "version" => "7.13.1",
                  "id" => "f152b60c-88cf-41a2-9a23-0f0119532b35",
                "name" => "kali",
        "ephemeral_id" => "ff70babe-99ee-43f0-98e0-eaa15daa3dba",
                "type" => "filebeat",
            "hostname" => "kali"
    },
       "fileset" => {
        "name" => "auth"
    },
      "activity" => "SSH Logins"
}

in terminal. That is the result when filter.

6

Ok I am a bit confused I just ran your Logstash and Filebeat setup and it worked fine with the filter and everything.

Here is my output, the only change I made is to make the auth log point at where I put your sample data.

Filebeat keeps track of what it has already read... are there new entries?

Sample output from logstash stdout


{
           "log" => {
        "offset" => 190,
          "file" => {
            "path" => "/Users/sbrown/workspace/sample-data/discuss/auth-log/auth.log"
        }
    },
      "activity" => "SSH Logins",
           "ecs" => {
        "version" => "1.9.0"
    },
        "system" => {
        "auth" => {
                  "pid" => "5807",
            "timestamp" => "Jul 16 06:58:59",
                 "user" => "kali",
                  "ssh" => {
                   "ip" => "192.168.186.149",
                "event" => "Failed password",
                 "port" => "54762"
            },
             "hostname" => "kali"
        }
    },
         "input" => {
        "type" => "log"
    },
          "tags" => [
        [0] "beats_input_codec_plain_applied",
        [1] "linux_auth"
    ],
          "host" => {
                  "ip" => [
            [0] "fe80::1090:9944:3e59:e5ee",
            [1] "192.168.2.107",
            [2] "fe80::a008:5fb6:591d:c4b4",
            [3] "fe80::ed7c:f1d5:aff:72d9",
            [4] "fe80::aede:48ff:fe00:1122"
        ],
        "architecture" => "x86_64",
                "name" => "ceres",
                  "id" => "CB562E90-69DE-5D41-AC64-4EEDC79D5CB0",
            "hostname" => "ceres",
                 "mac" => [
            [ 0] "8c:85:90:ae:b0:b2",
            [ 1] "82:de:c3:e6:d4:05",
            [ 2] "82:de:c3:e6:d4:04",
            [ 3] "82:de:c3:e6:d4:01",
            [ 4] "82:de:c3:e6:d4:00",
            [ 5] "a0:ce:c8:51:95:38",
            [ 6] "82:de:c3:e6:d4:01",
            [ 7] "0e:85:90:ae:b0:b2",
            [ 8] "6e:85:b5:ef:88:6d",
            [ 9] "6e:85:b5:ef:88:6d",
            [10] "ac:de:48:00:11:22"
        ],
                  "os" => {
               "build" => "20F71",
              "kernel" => "20.5.0",
                "type" => "macos",
             "version" => "10.16",
            "platform" => "darwin",
              "family" => "darwin",
                "name" => "Mac OS X"
        }
    },
         "agent" => {
                "type" => "filebeat",
                  "id" => "1d5a1f47-65b3-4d65-bcaf-ad2f378e846c",
            "hostname" => "ceres",
        "ephemeral_id" => "9545f7c9-aed6-4d94-909e-52a81cbfd089",
             "version" => "7.13.2",
                "name" => "ceres"
    },
      "@version" => "1",
       "service" => {
        "type" => "system"
    },
    "@timestamp" => 2021-07-16T13:58:59.000Z,
       "fileset" => {
        "name" => "auth"
    },
         "event" => {
          "module" => "system",
         "dataset" => "system.auth",
        "timezone" => "-07:00"
    },
       "message" => "Jul 16 06:58:59 kali sshd[5807]: Failed password for kali from 192.168.186.149 port 54762 ssh2",
     "container" => {
        "id" => "discuss"
    }
}

and here it is in elasticsearch

GET filebeat-7.13.2-2021.07.16/_search
{
  "took" : 28,
  "timed_out" : false,
  "_shards" : {
    "total" : 1,
    "successful" : 1,
    "skipped" : 0,
    "failed" : 0
  },
    "hits" : [
      {
        "_index" : "filebeat-7.13.2-2021.07.16",
        "_type" : "_doc",
        "_id" : "sSautXoBE2_dRnuqPwTG",
        "_score" : 1.0,
        "_source" : {
          "log" : {
            "offset" : 475,
            "file" : {
              "path" : "/Users/sbrown/workspace/sample-data/discuss/auth-log/auth.log"
            }
          },
          "activity" : "SSH Logins",
          "ecs" : {
            "version" : "1.9.0"
          },
          "system" : {
            "auth" : {
              "pid" : "5811",
              "timestamp" : "Jul 16 06:58:59",
              "user" : "kali",
              "ssh" : {
                "ip" : "192.168.186.149",
                "event" : "Failed password",
                "port" : "54772"
              },
              "hostname" : "kali"
            }
          },
          "input" : {
            "type" : "log"
          },
          "tags" : [
            "beats_input_codec_plain_applied",
            "linux_auth"
          ],
          "agent" : {
            "type" : "filebeat",
            "id" : "1bfe4001-7815-4438-ac45-3984ad8189e6",
            "hostname" : "ceres",
            "ephemeral_id" : "000057bb-4688-40df-a7e2-e00f0760856b",
            "version" : "7.13.2",
            "name" : "ceres"
          },
          "host" : {
            "architecture" : "x86_64",
            "name" : "ceres",
            "ip" : [
              "fe80::1090:9944:3e59:e5ee",
              "192.168.2.107",
              "fe80::a008:5fb6:591d:c4b4",
              "fe80::ed7c:f1d5:aff:72d9",
              "fe80::aede:48ff:fe00:1122"
            ],
            "id" : "CB562E90-69DE-5D41-AC64-4EEDC79D5CB0",
            "hostname" : "ceres",
            "mac" : [
              "8c:85:90:ae:b0:b2",
              "82:de:c3:e6:d4:05",
              "82:de:c3:e6:d4:04",
              "82:de:c3:e6:d4:01",
              "82:de:c3:e6:d4:00",
              "a0:ce:c8:51:95:38",
              "82:de:c3:e6:d4:01",
              "0e:85:90:ae:b0:b2",
              "6e:85:b5:ef:88:6d",
              "6e:85:b5:ef:88:6d",
              "ac:de:48:00:11:22"
            ],
            "os" : {
              "build" : "20F71",
              "type" : "macos",
              "kernel" : "20.5.0",
              "version" : "10.16",
              "platform" : "darwin",
              "family" : "darwin",
              "name" : "Mac OS X"
            }
          },
          "@version" : "1",
          "service" : {
            "type" : "system"
          },
          "@timestamp" : "2021-07-16T13:58:59.000Z",
          "fileset" : {
            "name" : "auth"
          },
          "event" : {
            "module" : "system",
            "dataset" : "system.auth",
            "timezone" : "-07:00"
          },
          "message" : "Jul 16 06:58:59 kali sshd[5811]: Failed password for kali from 192.168.186.149 port 54772 ssh2",
          "container" : {
            "id" : "discuss"
          }
        }
      },
7

I was confused too. Can't understand why.
I run

curl -X GET "192.168.186.157:9200/filebeat-192.168.186.146-7.13.1-2021.07.17/_search?pretty" -H 'Content-Type: application/json' -d' { "query": { "match": { "tag": "linux_auth" } } } '
{
  "took" : 0,
  "timed_out" : false,
  "_shards" : {
    "total" : 1,
    "successful" : 1,
    "skipped" : 0,
    "failed" : 0
  },
  "hits" : {
    "total" : {
      "value" : 0,
      "relation" : "eq"
    },
    "max_score" : null,
    "hits" : [ ]
  }
}

I'm going crazy with this soon.

Some new auth.log you need, but it is not very different.

Jul 17 14:37:36 kali sshd[2436]: Failed password for kali from 192.168.186.149 port 33654 ssh2
Jul 17 14:37:36 kali sshd[2442]: Failed password for kali from 192.168.186.149 port 33666 ssh2
Jul 17 14:37:36 kali sshd[2438]: Failed password for kali from 192.168.186.149 port 33658 ssh2
Jul 17 14:37:37 kali sshd[2437]: Connection closed by authenticating user kali 192.168.186.149 port 33656 [preauth]
Jul 17 14:37:37 kali sshd[2437]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:37:37 kali sshd[2437]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 17 14:37:37 kali sshd[2433]: Connection closed by authenticating user kali 192.168.186.149 port 33648 [preauth]
Jul 17 14:37:37 kali sshd[2433]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:37:37 kali sshd[2433]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 17 14:37:37 kali sshd[2435]: Connection closed by authenticating user kali 192.168.186.149 port 33652 [preauth]
Jul 17 14:37:37 kali sshd[2435]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:37:37 kali sshd[2435]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 17 14:37:37 kali sshd[2436]: Connection closed by authenticating user kali 192.168.186.149 port 33654 [preauth]
Jul 17 14:37:37 kali sshd[2436]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:37:37 kali sshd[2436]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 17 14:37:37 kali sshd[2442]: Connection closed by authenticating user kali 192.168.186.149 port 33666 [preauth]
Jul 17 14:37:37 kali sshd[2442]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:37:37 kali sshd[2442]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 17 14:37:37 kali sshd[2438]: Connection closed by authenticating user kali 192.168.186.149 port 33658 [preauth]
Jul 17 14:37:37 kali sshd[2438]: PAM 4 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:37:37 kali sshd[2438]: PAM service(sshd) ignoring max retries; 5 > 3
Jul 17 14:38:04 kali sshd[1582]: exited MaxStartups throttling after 00:00:45, 4 connections dropped
Jul 17 14:38:04 kali sshd[2466]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:38:06 kali sshd[2466]: Failed password for kali from 192.168.186.149 port 33688 ssh2
Jul 17 14:38:06 kali sshd[2466]: Connection closed by authenticating user kali 192.168.186.149 port 33688 [preauth]
Jul 17 14:39:01 kali CRON[2469]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul 17 14:39:01 kali CRON[2469]: pam_unix(cron:session): session closed for user root
Jul 17 14:45:01 kali CRON[2522]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul 17 14:45:01 kali CRON[2522]: pam_unix(cron:session): session closed for user root
Jul 17 14:46:12 kali sshd[2526]: Received disconnect from 192.168.186.149 port 33690:11: Bye Bye [preauth]
Jul 17 14:46:12 kali sshd[2526]: Disconnected from authenticating user kali 192.168.186.149 port 33690 [preauth]
Jul 17 14:46:12 kali sshd[1582]: error: beginning MaxStartups throttling
Jul 17 14:46:12 kali sshd[1582]: drop connection #12 from [192.168.186.149]:33716 on [192.168.186.146]:22 past MaxStartups
Jul 17 14:46:12 kali sshd[2531]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2532]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2528]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2533]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2537]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2538]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2543]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2540]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2535]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2530]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2534]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2529]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2536]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2539]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2542]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:12 kali sshd[2544]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.186.149  user=kali
Jul 17 14:46:14 kali sshd[2532]: Failed password for kali from 192.168.186.149 port 33700 ssh2
Jul 17 14:46:14 kali sshd[2531]: Failed password for kali from 192.168.186.149 port 33698 ssh2
Jul 17 14:46:14 kali sshd[2533]: Failed password for kali from 192.168.186.149 port 33702 ssh2
Jul 17 14:46:14 kali sshd[2528]: Failed password for kali from 192.168.186.149 port 33692 ssh2
Jul 17 14:46:14 kali sshd[2534]: Failed password for kali from 192.168.186.149 port 33704 ssh2
Jul 17 14:46:14 kali sshd[2530]: Failed password for kali from 192.168.186.149 port 33696 ssh2
Jul 17 14:46:14 kali sshd[2529]: Failed password for kali from 192.168.186.149 port 33694 ssh2
Jul 17 14:46:14 kali sshd[2535]: Failed password for kali from 192.168.186.149 port 33706 ssh2
Jul 17 14:46:14 kali sshd[2543]: Failed password for kali from 192.168.186.149 port 33730 ssh2
Jul 17 14:46:14 kali sshd[2537]: Failed password for kali from 192.168.186.149 port 33710 ssh2
Jul 17 14:46:14 kali sshd[2538]: Failed password for kali from 192.168.186.149 port 33712 ssh2
8

Well, by some magic that I don't know, it's worked.

I just change the timeline in all filebeat hosts to my location and restart all of that.

Anyway, thanks for helping me! I'm appreciated for your help :smiling_face_with_three_hearts:

9

2 Things

you have
"match": { "tag": "linux_auth" } }
should be
"match": { "tags": "linux_auth" } }. <! -- tags with an "s"

That is why the query is failing.

Also

Why do you have the IP address in the index name is that on purpose, that is not what your logstash conf shows


filebeat-192.168.186.146-7.13.1-2021.07.17
10

Yup tag is wrong, but that not the reason why it don't have anything.

192.168.186.146 is the ip of filebeat host, I put in the index in filebeat.yml to separate every single host. I want to see log in single host, insead of combine all log in one day in one.

By the way, I fix the timeline and all thing just work perfect.

11

Understand on the index naming, Not sure if that's just for testing but that will most likely cause issues at scale as you will have many many indexes which isn't always efficient.

12

I know that. But now I need to test so it'll easier for me to config like that. Of course I will change index back later, when I finish my test.

1 Like
13

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