Metricbeat(至 logz.io)抛出 "Failed to connect to backoff: x509: certificate signed by unknown authority"

Metricbeat (To logz.io) throws "Failed to connect to backoff: x509: certificate signed by unknown authority"

当 运行 metricbeat 反对 logz.io 时,metricbeat 抛出以下错误:

ERROR   [publisher_pipeline_output]     pipeline/output.go:154  Failed to connect to backoff(async(tcp://listener-eu.logz.io:5015)): x509: certificate signed by unknown authority

设置如下:

# Standard config, I changed nothing here
metricbeat.config.modules:
  path: ${path.config}/modules.d/*.yml
  reload.enabled: false

# Standard config, I changed nothing here
setup.template.settings:
  index.number_of_shards: 1
  index.codec: best_compression

# "MyToken" is the correct token for metrics in logz.io, of course
fields:
  logzio_codec: json
  token: "MyToken"
fields_under_root: true

# Standard config, I changed nothing here
setup.kibana:
  host: "localhost:5601"

# listener is correct, we use EU access, certificate is in the folder (Download as in the description)
output.logstash:
  # The Logstash hosts
  hosts: ["listener-eu.logz.io:5015"]

  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  ssl.certificate_authorities: ['/etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt']

# Standard config, I changed nothing here
processors:
  - add_host_metadata: ~
  - add_cloud_metadata: ~
  - add_docker_metadata: ~
  - add_kubernetes_metadata: ~

到目前为止我尝试了什么/我已经检查了什么:

我注意到的一些奇怪的事情是有时不是 X509 错误发生,而是超时错误(一旦我在日志中再次得到它,我将 post 它在这里)。

是否有明显的配置遗漏或我可以在服务器上检查的其他内容?

logz.io documentation 使用更新的证书。 更新后的证书可用 here

请注意文档中的通知:“2021 年 3 月之后创建的 Metrics 帐户使用 Prometheus 而不是 ElasticSearch。”

免责声明:我在 logz.io

工作