使用grok in logstash过滤原木

使用grok in logstash过滤原木,logstash,elastic-stack,logstash-grok,Logstash,Elastic Stack,Logstash Grok,我试图过滤掉在grok帮助下收到的日志。下面是示例日志 INFO | jvm 1 | main | 2013/04/05 01:08:47.048 | [m[32mINFO [TaskExecutor-master-2443-ProcessTask [31111111112]] [b2cConfirmationAction] CRON JOB ID : 101AA1C, ACTION : ConfirmationAction , CUSTOMER ID : 0000011111

我试图过滤掉在grok帮助下收到的日志。下面是示例日志

INFO   | jvm 1    | main    | 2013/04/05 01:08:47.048 | [m[32mINFO  [TaskExecutor-master-2443-ProcessTask [31111111112]] [b2cConfirmationAction] CRON JOB ID : 101AA1C, ACTION : ConfirmationAction , CUSTOMER ID : 000001111111 , EMAIL ADDRESS : abc@gmail.com , SCHEDULE : Every 1 week  , MESSAGE : Execution started for action ConfirmationAction
我正在使用grok debugger()在更新logstash conf文件之前进行测试。 下面是我的筛选代码:

%{LOGLEVEL:level}%{GREEDYDATA:greedydata}%{SPACE}%{YEAR}[/-]%{MONTHNUM}[/-]%{MONTHDAY}%{SPACE}%{HOUR}:%{MINUTE}:%{SECOND}%{GREEDYDATA:gd} \[(?:%{WORD:action})\]%{GREEDYDATA:cronjobresult}
在这里,我得到了输出作为

"level": [ [ "INFO" ] ], "greedydata": [ [ " | jvm 1 | main | 20" ] ], "SPACE": [ [ "", " " ] ], "YEAR": [ [ "13" ] ], "MONTHNUM": [ [ "04" ] ], "MONTHDAY": [ [ "05" ] ], "HOUR": [ [ "01" ] ], "MINUTE": [ [ "08" ] ], "SECOND": [ [ "47.048" ] ], "gd": [ [ " | \u001b[m\u001b[32mINFO [TaskExecutor-master-2443-ProcessTask [31111111112]]" ] ], "action": [ [ "b2cConfirmationAction" ] ], "cronjobresult": [ [ " CRON JOB ID : 101AA4A , ACTION : ConfirmationAction , CUSTOMER ID : 000001111111 , EMAIL ADDRESS : abc@gmail.com , SCHEDULE : Every 1 week , MESSAGE : Execution started for action ConfirmationAction" ] ] }

我的要求是在cronjobresult下获取值,比如cron job iD customer iD和不同的独立字段,以便我可以在kibana中使用这些值。现在我无法得到它。另外,我已经使用了两次greedyData,对于这个日志来说,更好的方法是值得注意的

您只需进一步扩展过滤器并显式匹配即可。例如,为了匹配cron作业id,您可以在过滤器中写入
cron作业id:%{BASE16NUM:cron\u job\u id}

如果您不需要日志中的任何数据,则只需编写
*
而不是
GREEDYDATA
,它将被跳过

这是日志的完整过滤器

%{LOGLEVEL:level}%{GREEDYDATA:greedydata}%{SPACE}%{YEAR}[/-]%{MONTHNUM}[/-]%{MONTHDAY}%{SPACE}%{HOUR}:%{MINUTE}:%{SECOND}%{GREEDYDATA:gd} \[(?:%{WORD:action})\] CRON JOB ID : %{BASE16NUM:Cron_job_id},.*CUSTOMER ID : %{NUMBER:Customer_id}.*EMAIL ADDRESS : %{EMAILADDRESS}.*SCHEDULE : %{GREEDYDATA:schedule}.*, MESSAGE : %{GREEDYDATA:Message}
输出:

{
  "level": [
    [
      "INFO"
    ]
  ],
  "greedydata": [
    [
      "   | jvm 1    | main    | 20"
    ]
  ],
  "SPACE": [
    [
      "",
      " "
    ]
  ],
  "YEAR": [
    [
      "13"
    ]
  ],
  "MONTHNUM": [
    [
      "04"
    ]
  ],
  "MONTHDAY": [
    [
      "05"
    ]
  ],
  "HOUR": [
    [
      "01"
    ]
  ],
  "MINUTE": [
    [
      "08"
    ]
  ],
  "SECOND": [
    [
      "47.048"
    ]
  ],
  "gd": [
    [
      " | [m[32mINFO  [TaskExecutor-master-2443-ProcessTask [31111111112]]"
    ]
  ],
  "action": [
    [
      "b2cConfirmationAction"
    ]
  ],
  "Cron_job_id": [
    [
      "101AA1C"
    ]
  ],
  "Customer_id": [
    [
      "000001111111"
    ]
  ],
  "BASE10NUM": [
    [
      "000001111111"
    ]
  ],
  "EMAILADDRESS": [
    [
      "abc@gmail.com"
    ]
  ],
  "local": [
    [
      "abc"
    ]
  ],
  "remote": [
    [
      "gmail.com"
    ]
  ],
  "schedule": [
    [
      "Every 1 week  "
    ]
  ],
  "Message": [
    [
      "Execution started for action"
    ]
  ]
}
请注意,我使用了来自

如果你想测试它,你需要添加

EMAILADDRESSPART [a-zA-Z0-9_.+-=:]+
EMAILADDRESS %{EMAILADDRESSPART:local}@%{EMAILADDRESSPART:remote}
通过检查
添加自定义模式