【问题标题】:Logstash - Storing RabbitMQ Logs - MultilineLogstash - 存储 RabbitMQ 日志 - 多行
【发布时间】:2018-04-04 07:27:45
【问题描述】:

我已经使用 ELK 大约六个月了,到目前为止效果很好。我在logstash 6.2.3版上。 RabbitMQ 构成了我的分布式系统的核心(RabbitMQ 本身就是分布式的),因此跟踪 RabbitMQ 的日志非常重要。 这个论坛上的大多数其他对话似乎都使用 RabbitMQ 作为输入/输出阶段,但我只想监控日志。 我发现的唯一问题是 RabbitMQ 具有多行日志记录,如下所示:

=WARNING REPORT==== 19-Nov-2017::06:53:14 ===
closing AMQP connection <0.27161.0> (...:32799 -> ...:5672, vhost: '/', user: 'worker'):
client unexpectedly closed TCP connection

=WARNING REPORT==== 19-Nov-2017::06:53:18 ===
closing AMQP connection <0.22410.0> (...:36656 -> ...:5672, vhost: '/', user: 'worker'):
client unexpectedly closed TCP connection

=WARNING REPORT==== 19-Nov-2017::06:53:19 ===
closing AMQP connection <0.26045.0> (...:55427 -> ...:5672, vhost: '/', user: 'worker'):
client unexpectedly closed TCP connection

=WARNING REPORT==== 19-Nov-2017::06:53:20 ===
closing AMQP connection <0.5484.0> (...:47740 -> ...:5672, vhost: '/', user: 'worker'):
client unexpectedly closed TCP connection

我找到了一个出色的代码示例here,我将其剥离到过滤器阶段,如下所示:

filter {
    if [type] == "rabbitmq" {
        codec => multiline {
            pattern => "^="
            negate => true
            what => "previous"
        }
        grok {
            type => "rabbit"
            patterns_dir => "patterns"
            pattern => "^=%{WORD:report_type} REPORT=+ %{RABBIT_TIME:time_text} ===.*$"
        }
        date {
            type => "rabbit"
            time_text => "dd-MMM-yyyy::HH:mm:ss"
        }
        mutate {
            type => "rabbit"
            add_field => [ 
                "message", 
                "%{@message}" 
            ]
        }
        mutate {
            gsub => [
                "message", "^=[A-Za-z0-9: =-]+=\n", "",
                # interpret message header text as "severity"
                "report_type", "INFO", "1",
                "report_type", "WARNING", "3",
                "report_type", "ERROR", "4",
                "report_type", "CRASH", "5",
                "report_type", "SUPERVISOR", "5"
            ]
        }
    }
}

但是当我将它保存到一个 conf 文件并重新启动 logstash 时,我收到以下错误:

[2018-04-04T07:01:57,308][INFO ][logstash.modules.scaffold] Initializing module {:module_name=>"fb_apache", :directory=>"/usr/share/logstash/modules/fb_apache/configuration"}
[2018-04-04T07:01:57,316][INFO ][logstash.modules.scaffold] Initializing module {:module_name=>"netflow", :directory=>"/usr/share/logstash/modules/netflow/configuration"}
[2018-04-04T07:01:57,841][INFO ][logstash.runner          ] Starting Logstash {"logstash.version"=>"6.2.3"}
[2018-04-04T07:01:57,973][INFO ][logstash.agent           ] Successfully started Logstash API endpoint {:port=>9600}
[2018-04-04T07:01:58,037][ERROR][logstash.agent           ] Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:main, :exception=>"LogStash::ConfigurationError", :message=>"Expected one of #, { at line 3, column 15 (byte 54) after filter {\n    if [type] == \"rabbitmq\" {\n        codec ", :backtrace=>["/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:42:in `compile_imperative'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:50:in `compile_graph'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:12:in `block in compile_sources'", "org/jruby/RubyArray.java:2486:in `map'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:11:in `compile_sources'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:51:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:169:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:40:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:315:in `block in converge_state'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:141:in `with_pipelines'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:312:in `block in converge_state'", "org/jruby/RubyArray.java:1734:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:299:in `converge_state'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:166:in `block in converge_state_and_update'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:141:in `with_pipelines'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:164:in `converge_state_and_update'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:90:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:348:in `block in execute'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/stud-0.0.23/lib/stud/task.rb:24:in `block in initialize'"]}

任何想法可能是什么问题?

谢谢,

【问题讨论】:

    标签: rabbitmq logstash multiline logstash-configuration


    【解决方案1】:

    如果您使用 filebeat 将日志从 rabbitMQ 服务器发送到 logstash,您应该在那里配置 multiline

    【讨论】:

      【解决方案2】:

      答案确实是multiline。目标是将以日期以外的其他内容开头的行与以日期开头的上一行合并。就是这样:

      multiline.pattern: '^\d{4}-\d{2}-\d{2}'
      multiline.negate: true
      multiline.match: after
      

      注意:我之前尝试合并任何以空格字符 ^\s+ 开头的行,但这不起作用,因为并非所有警告或错误消息都以空格开头。

      完整的filebeat输入(7.5.2格式)

      filebeat:
        inputs:
        - exclude_lines:
          - 'Failed to publish events caused by: EOF'
          fields:
            type: rabbitmq
          fields_under_root: true
          paths:
          - /var/log/rabbitmq/*.log
          tail_files: false
          timeout: 60s
          type: log
          multiline.pattern: '^\d{4}-\d{2}-\d{2}'
          multiline.negate: true
          multiline.match: after
      

      Logstash 模式

      # RabbitMQ
      RABBITMQDATE %{MONTHDAY}-%{MONTH}-%{YEAR}::%{HOUR}:%{MINUTE}:%{SECOND}
      RABBITMQLINE (?m)=%{DATA:severity} %{DATA}==== %{RABBITMQDATE:timestamp} ===\n%{GREEDYDATA:message}
      

      我相信他们有充分的理由在 RMQ 3.7.x 中以这种奇怪的方式登录,但在不认识他们的情况下,这确实让我们的生活变得艰难。

      【讨论】:

        【解决方案3】:

        您不能将编解码器用作过滤器插件。编解码器只能用于输入或输出插件(请参阅the doc),带有编解码器配置选项。

        您必须将多行编解码器放入生成 rabbitmq 日志的输入插件中。

        【讨论】:

          猜你喜欢
          • 1970-01-01
          • 1970-01-01
          • 1970-01-01
          • 1970-01-01
          • 1970-01-01
          • 2016-06-09
          • 2021-05-08
          • 1970-01-01
          • 1970-01-01
          相关资源
          最近更新 更多