在Logstash中解析JSON事件

Question

我的登录格式如下，它是一个带有嵌套字段的普通json。

{
    "level": "info",
    "message": {
        "req": {
            "headers": {
                "host": "localhost:8080",
                "connection": "keep-alive",
                "x-forwarded-for": "192.168.1.1, 1.1.1.1",
                "x-forwarded-proto": "http"
            },
            "url": "/products?userId=493d0aec-a9a7-42a3",
            "method": "GET",
            "originalUrl": "/products?userId=493d0aec-a9a7-42a3",
            "params": {
                "0": "/products"
            },
            "query": {
                "userId": "493d0aec-a9a7-42a3"
            },
            "body": ""
        },
        "res": {
            "headers": {
                "traceid": "ac586e4e924048",
                "x-correlation-id": "57d7920d-b623-48f8",
                "content-type": "application/json;charset=UTF-8",
                "content-length": "2",
                "date": "Fri, 08 Mar 2019 09:55:45 GMT",
                "connection": "close"
            },
            "statusCode": 200,
            "body": "[]"
        },
        "gateway": "internal"
    },
    "correlationId": "57d7920d-b623-48f8",
    "timestamp": "2019-03-08T09:55:45.833Z"
}

如何使用Filebeat和Logstash正确地解析它，以将Kibana中的所有json字段视为单独的（已解析的）字段？我在“message”字段中遇到了一个问题，它嵌套了json字段。我解析一个在“message”中有字符串的事件没有问题，但不是JSON。

我的尝试：

filebeat.inputs:
- type: stdin
  json.keys_under_root: true
  json.add_error_key: true

{
    "req" => {
        "originalUrl" => "/offers", "params" => {
            "0" => "/offers"
        }, "query" => {}, "body" => "", "headers" => {
            "accept-encoding" => "gzip", "user-agent" => "okhttp/3.8.1", "x-consumer-id" => "f2a6e4cd-2224-4535

json {   
    source => "message"    
    target => "message_json"    
} 

[2019-03-08T09:55:47,084][WARN][logstash.outputs.ElasticSearch]无法将事件索引到ElasticSearch。{:status=>400,:action=>[“index”,{:_id=>nil,:_index=>“filebeat-6.5.0-2019.03.08-sdx”,:_type=>“doc”,:routing=>nil},#],:response=>{“index”=>{“_index”=>“filebeat-6.5.0-2019.03.08-sdx”,“_type”=>“doc”,“id”=>“ERS6xGKBGE-US7A6MVT”,“status”=>400,“error”=>{“type”=>“[json.message]类型[keyword]”,“caused_by”=>{“type”=>“illegal_state_exception”,“reason”=>“无法在1:461获取START_OBJECT上的文本”}}}}[2019-03-08t09:55:47,085][WARN][logstash.outputs.elasticsearch]无法将事件索引到elasticsearch。{:status=>400,:action=>[“index”,{:_id=>nil,:_index=>“filebeat-6.5.0-2019.03.08-sdx”,:_type=>“doc”,:routing=>nil},#],:response=>{“index”=>{“_index”=>“filebeat-6.5.0-2019.03.08-sdx”,“_type”=>“doc”,“id”=>“ehs6xgkbge-us7a6mvt”,“status”=>400,“error”=>{“type”=>“[json.message]类型[keyword]”,“caused_by”=>{“type”=>“illegal_state_exception”,“reason”=>“无法在1:461获取START_OBJECT上的文本”}}}}

如果“message”字段是字符串（不是json)，这个过滤器对我来说很好。

你知道如何解析“消息域”中的嵌套json吗？

Answer 1

我有问题要通过logstash来解析json。

我在这个问题上挣扎了一段时间。并未能解入logstash。

但幸运的是，我们已经在elasticsearch中吸收了node。

{
    "description": "Parse JSON log",
    "processors": [
      {
        "json": {
          "field": "message",
          "target_field": "message-json"
        }
      },
      {
        "remove": {
          "field": "message"
        }
      },
      {
        "append": {
          "field": "tags",
          "value": [
            "isjsonlog"
          ]
        }
      }
    ],
    "on_failure": [
      {
        "append": {
          "field": "tags",
          "value": [
            "nonjsonlog"
          ]
        }
      }
    ]
  }

elasticsearch {
    hosts => [ localhost ]
    index => "filebeat-%{+YYYY.MM.dd}"
    manage_template => false
    pipeline => "your_pipeline_name"
  }

 output.elasticsearch:
    ....
    pipelines:
       - pipeline: "your pipeline name"
          when:
            contains:
               message: "{"