There is no grok expression that can parse 100% of the following log information

hello
logtfile

12Jul20 10:18:09.561645: hello IT00S451.uaes.com (port 57276)
12Jul20 10:18:09.561645: info request for enable_MULTI_v7 from IT00S451.uaes.com (port 57276)
12Jul20 10:18:09.561645: exit  IT00S451.uaes.com (port 57276)
12Jul20 11:20:22.752214: hello 174.34.74.54 (port 63825)
12Jul20 11:20:22.752214: license request from hongbin.zhang@174.34.74.54 (display 54.74.34.174:5, port 63825)
12Jul20 11:20:22.752214: recorded user: hongbin.zhang
12Jul20 11:20:22.752214: new enable_MULTI_v7 (1 of 1) for hongbin.zhang@174.34.74.54 (display 54.74.34.174:5, port 63825)
12Jul20 11:20:22.752214: granted enable_MULTI_v7 (1 of 1) to hongbin.zhang@174.34.74.54 (display 54.74.34.174:5, port 63825)
12Jul20 11:20:22.752214: license request from hongbin.zhang@174.34.74.54 (display 54.74.34.174:5, port 63825)
12Jul20 11:20:22.752214: new multi (1 of 1) for hongbin.zhang@174.34.74.54 (display 54.74.34.174:5, port 63825)
12Jul20 11:20:22.752214: granted multi (1 of 1) to hongbin.zhang@174.34.74.54 (display 54.74.34.174:5, port 63825)
12Jul20 11:22:00.868378: hello 174.34.74.54 (port 63848)
12Jul20 11:22:00.883985: license request from hongbin.zhang@174.34.74.54 (display 54.74.34.174:5, port 63848)
12Jul20 11:22:00.883985:   (hongbin.zhang@174.34.74.54 (display 54.74.34.174:5, port 63848)) license denied: not configured for 11023
12Jul20 11:22:00.883985: exit  hongbin.zhang@174.34.74.54 (display 54.74.34.174:5, port 63848)
12Jul20 12:31:48.929833: hello 174.34.74.54 (port 64327)
12Jul20 12:31:48.945488: version request from 174.34.74.54 (port 64327)
12Jul20 12:31:48.945488: exit  174.34.74.54 (port 64327)

Ask for help.

Correct. You would need to write multiple grok statements for this one if you want to parse it all out. One grok statement for message format.

hi
I'm using FileBeat and I don't see a way for a pipeline to configure multiple groks, the pipeline and FileBeat configurations I currently use are as follows

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:

- type: log

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

  # Paths that should be crawled and fetched. Glob based paths.
  paths:
    - D:\git\ii.log

  fields:
    type: "hightec"

  index: "indexcx-%{[agent.version]}-%{[fields.type]:other}-%{+yyyy.MM.dd}"
  pipeline: "ne_user_lookup"    

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

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

  # Paths that should be crawled and fetched. Glob based paths.
  paths:
    - D:\git\ll.log
  multiline.pattern: 'hello'
  multiline.negate: true
  multiline.match: after

  fields:
    type: "ghs"


  index: "indexcx-%{[agent.version]}-%{[fields.type]:other}-%{+yyyy.MM.dd}"
  pipeline: "ghs-log-cs"  


# ============================== 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.ilm.enabled: false

setup.template.settings:
  index.number_of_shards: 1
  #index.codec: best_compression
  #_source.enabled: false
# setup.template.enabled: false
setup.template.name: "indexcx-%{[agent.version]}"
setup.template.pattern: "indexcx-%{[agent.version]}-*"

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

  host: "174.34.93.62: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:

# 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: ["174.34.93.62:9200"]
  # pipeline: "xxx-log"
  # pipeline: "discuss-timestamp"
  

# ------------------------------ Logstash Output -------------------------------
#output.logstash:
  # The Logstash hosts
  #hosts: ["localhost:5044"]

  # 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",
# "publish", "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

pipeline


  {
    "grok": {
      "field": "message",
      "patterns": [
        "%{MY_DATE:timestamp_cx}: license request from %{USERNAME:username}@%{GREEDYDATA:computername}"
      ],
      "pattern_definitions": {
        "MY_MONTH": "(?:[Jj]an(?:uary|uar)?|[Ff]eb(?:ruary|ruar)?|[Mm](?:a|ä)?r(?:ch|z)?|[Aa]pr(?:il)?|[Mm]a(?:y|i)?|[Jj]un(?:e|i)?|[Jj]ul(?:y|i)?|[Aa]ug(?:ust)?|[Ss]ep(?:tember)?|[Oo](?:c|k)?t(?:ober)?|[Nn]ov(?:ember)?|[Dd]e(?:c|z)(?:ember)?)",
        "MY_DATE": "%{MONTHDAY}%{MY_MONTH}%{YEAR} %{TIME}"
      },
      "ignore_failure": true
    }
  },
  {
    "date": {
      "field": "timestamp_cx",
      "formats": [
        "ddMMMyy HH:mm:ss.SSSSSS"
      ],
      "target_field": "@timestamp-tyz"
    }
  }

hi
Can the FileBeat configuration customize a time field?

There is a new processor for timestamps in filebeat but is still in beta and limited. I would use the Date Processor.

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