Beats

filebeat采集日志是cpu使用率为260%，不知道怎么给客户解释

贡献

yushun 回复了问题 • 6 人关注 • 5 个回复 • 7706 次浏览 • 2017-11-28 17:24 • 来自相关话题

filebeat nginx module配置问题

贡献

medcl 回复了问题 • 2 人关注 • 1 个回复 • 4161 次浏览 • 2017-10-18 14:34 • 来自相关话题

filebeat每次有新事件会将上一次的事件重新发送，该如何避免？

贡献

zdy 回复了问题 • 6 人关注 • 4 个回复 • 11495 次浏览 • 2018-01-23 00:44 • 来自相关话题

filebeat配置从文件末尾读

贡献

elastic5215 回复了问题 • 4 人关注 • 3 个回复 • 7544 次浏览 • 2018-03-07 16:51 • 来自相关话题

filebeat 5.6 如何定义多个index

贡献

kkgace 回复了问题 • 3 人关注 • 4 个回复 • 11086 次浏览 • 2017-12-08 10:13 • 来自相关话题

Filebeat cpu 使用率偏高

贡献

linjikun 回复了问题 • 2 人关注 • 1 个回复 • 8321 次浏览 • 2019-07-05 11:19 • 来自相关话题

filebeat采集文件的时区问题

贡献

novia 回复了问题 • 2 人关注 • 1 个回复 • 7209 次浏览 • 2017-09-18 09:26 • 来自相关话题

安裝 metricbeat 無法傳送訊息 Logstash

贡献

wy993322 回复了问题 • 2 人关注 • 2 个回复 • 4165 次浏览 • 2018-07-25 11:13 • 来自相关话题

Filebeat 配置「SSL」證書加密出現錯誤 ... ERR Failed to publish events

cddisk2017 发表了文章 • 3 个评论 • 11698 次浏览 • 2017-09-08 14:22 • 来自相关话题

各位朋友大家好:

進行配置「Filebeat」證書加密出現錯誤如下，有哪位朋友遇過此問題可以幫幫忙!

ERR Failed to publish events caused by: read tcp 192.168.1.57:56182->192.168.1.249:5043: wsarecv: An existing connection was forcibly closed by the remote host.

使用過「telnet IP Port」測試「ELK」服務器，確認通訊協議 OK !

Filebeat 配置如檔如下: (Windows 環境)

filebeat.prospectors:

- input_type: log                      #輸入 type「log」

  paths:

    - D:\Wireshark_Log\*               #指定推送日誌「Log」文件

    

output.logstash:

  hosts: ["192.168.1.249:5043"]         #指定接收Logstash

  tls:

      certificate_authorities:

      - C:\filebeat-5.5.0-windows-x86_64\ssl\logstash\192.168.1.249.crt

      ssl.certificate:

      - C:\filebeat-5.5.0-windows-x86_64\ssl\filebeat\192.168.1.57.crt

      ssl.certificate:

      - C:\filebeat-5.5.0-windows-x86_64\ssl\filebeat\192.168.1.57.key

以下是「FileBeat」錯誤日誌

2017-09-08T14:14:57+08:00 ERR Failed to publish events caused by: read tcp 192.168.1.57:56202->192.168.1.249:5043: wsarecv: An existing connection was forcibly closed by the remote host.

2017-09-08T14:14:57+08:00 INFO Error publishing events (retrying): read tcp 192.168.1.57:56202->192.168.1.249:5043: wsarecv: An existing connection was forcibly closed by the remote host.

2017-09-08T14:15:19+08:00 INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1 libbeat.logstash.call_count.PublishEvents=1 libbeat.logstash.publish.read_errors=1 libbeat.logstash.publish.write_bytes=323 libbeat.logstash.published_but_not_acked_events=5

2017-09-08T14:15:49+08:00 INFO No non-zero metrics in the last 30s

2017.09.08 感謝 medcl 兄弟幫忙，再次修改如下:

filebeat.prospectors:

- input_type: log                      #輸入 type「log」

  paths:

    - D:\Wireshark_Log\*               #指定推送日誌「Log」文件

    

output.logstash:

  hosts: ["192.168.1.249:5043"]         #指定接收Logstash

  ssl:     # <=== 新版本貌似要改成「SSL」

      certificate_authorities:

      - C:\filebeat-5.5.0-windows-x86_64\ssl\logstash\192.168.1.249.crt

      ssl.certificate:

      - C:\filebeat-5.5.0-windows-x86_64\ssl\filebeat\192.168.1.57.crt

      ssl.key: # <===  修正為「ssl.key」      

      - C:\filebeat-5.5.0-windows-x86_64\ssl\filebeat\192.168.1.57.key

以下是「FileBeat」錯誤日誌

2017-09-08T15:40:23+08:00 INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 libbeat.logstash.publish.read_bytes=5120 libbeat.logstash.publish.write_bytes=660 libbeat.publisher.published_events=20

2017-09-08T15:40:29+08:00 ERR Connecting error publishing events (retrying): x509: certificate is valid for 192.168.1.57, not 192.168.1.249

2017-09-08T15:40:53+08:00 INFO Non-zero metrics in the last 30s: libbeat.logstash.publish.read_bytes=1024 libbeat.logstash.publish.write_bytes=132

2017-09-08T15:41:01+08:00 ERR Connecting error publishing events (retrying): x509: certificate is valid for 192.168.1.57, not 192.168.1.249

2017-09-08T15:41:23+08:00 INFO Non-zero metrics in the last 30s: libbeat.logstash.publish.read_bytes=1024 libbeat.logstash.publish.write_bytes=132

2017-09-08T15:41:53+08:00 INFO No non-zero metrics in the last 30s

意思是說
证书对 192.168.1.57 有效，而不是192.168.1.249 。這裡有些不明白...