Exiting: error connecting to Kibana: fail to get the Kibana version: HTTP GET request to http://X.X.X.X:5601/api/status fails: fail to execute the HTTP GET request: Get "http://X.X.X.X:5601/api/status": context deadline exceeded. Response:

Elastic Stack Beats
1

Hello,

I'm having errors loading --dashboards from filebeats to kibana. But when running the command below, it returns me the following message:

[rcmag.kta@XXXXXXXX ~]$ sudo filebeat setup --dashboards
Loading dashboards (Kibana must be running and reachable)
Exiting: error connecting to Kibana: fail to get the Kibana version: HTTP GET request to http://X.X.X.X:5601/api/status fails: fail to execute the HTTP GET request: Get "http://X.X.X.X:5601/api/status": context deadline exceeded. Response:

To add:

filebeats is on another server, separate with kibana and others.

2

Does the non-redacted IP point to your Kibana instance?

3

yes, it's my Kibana IP...

4

Pretty simple. Just curl that exact URL and see if you get a response. I suspect you're not going to.

In kibana.yml what did you set

server.host

server.host
This setting specifies the host of the back end server. To allow remote users to connect, set the value to the IP address or DNS name of the Kibana server. Use 0.0.0.0 to make Kibana listen on all IPs (public and private). Default: "localhost

5

I put the server IP

server.host: "10.25.678.56"

6

Did the curl work?

I would try "0.0.0.0"

Also is this running on the OS or in a Container?

7

operational system Red Hat 8

8

Curl to which address ?

I changed the server.host: "0.0.0.0" does not work

9

The one in the error message...

You've got a network connectivity problem most likely.

That or Kibana is not actually running. Are you sure it's running?

Do you have authentication username and password configured?

Perhaps we should back up is elasticsearch and Kibana running. Can you log into them through the browser??

10 
[rcmag.kta@LSVQA ~]$ sudo filebeat setup --dashboards
[sudo] password for rcmag.kta:
Loading dashboards (Kibana must be running and reachable)
Exiting: error connecting to Kibana: fail to get the Kibana version: HTTP GET request to http://10.25.155.45:5601/api/status fails: fail to execute the HTTP GET request: Get "http://10.25.155.45:5601/api/status": context deadline exceeded. Response:

The Kibana is run in browser
I'm not using authentication

11

That seems to indicate That where you have file beat running, it cannot reach Kibana.

If from the file beat box, you cannot curl that same URL and API. Then there is a network connectivity issue typically

12

image
image1896×744 66.6 KB

13

Is that Kibana Browser from the filebeat host?

Or from a different host.

Please share your entire filebeat.yml we're just guessing at this point.

14

Kibana and filebeat are on different servers...

###################### Filebeat Configuration Example #########################

# This file is an example configuration file highlighting only the most common
# options. The filebeat.reference.yml file from the same directory contains all the
# supported options with more comments. You can use it as a reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/filebeat/index.html

# For more available modules and options, please see the filebeat.reference.yml sample
# configuration file.

# ============================== Filebeat inputs ===============================

filebeat.inputs:

# Each - is an input. Most options can be set at the input level, so
# you can use different inputs for various configurations.
# Below are the input specific configurations.

# filestream is an input for collecting log messages from files.
- type: filestream

  # Unique ID among all inputs, an ID is required.
  id: my-filestream-id

  # Change to true to enable this input configuration.
  enabled: false

  # Paths that should be crawled and fetched. Glob based paths.
  paths:
    - /var/log/*.log
    #- c:\programdata\elasticsearch\logs\*

  # Exclude lines. A list of regular expressions to match. It drops the lines that are
  # matching any regular expression from the list.
  # Line filtering happens after the parsers pipeline. If you would like to filter lines
  # before parsers, use include_message parser.
  #exclude_lines: ['^DBG']

  # Include lines. A list of regular expressions to match. It exports the lines that are
  # matching any regular expression from the list.
  # Line filtering happens after the parsers pipeline. If you would like to filter lines
  # before parsers, use include_message parser.
  #include_lines: ['^ERR', '^WARN']

  # Exclude files. A list of regular expressions to match. Filebeat drops the files that
  # are matching any regular expression from the list. By default, no files are dropped.
  #prospector.scanner.exclude_files: ['.gz$']

  # Optional additional fields. These fields can be freely picked
  # to add additional information to the crawled log files for filtering
  #fields:
  #  level: debug
  #  review: 1

# ============================== Filebeat modules ==============================

filebeat.config.modules:
  # Glob pattern for configuration loading
  path: ${path.config}/modules.d/*.yml

  # Set to true to enable config reloading
  reload.enabled: false

  # Period on which files under path should be checked for changes
  #reload.period: 10s

# ======================= Elasticsearch template setting =======================

setup.template.settings:
  index.number_of_shards: 1
  #index.codec: best_compression
  #_source.enabled: false


# ================================== General ===================================

# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:

# The tags of the shipper are included in their own field with each
# transaction published.
#tags: ["service-X", "web-tier"]

# Optional fields that you can specify to add additional information to the
# output.
#fields:
#  env: staging

# ================================= Dashboards =================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here or by using the `setup` command.
#setup.dashboards.enabled: false

# The URL from where to download the dashboards archive. By default this URL
# has a value which is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:

# =================================== Kibana ===================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

  # Kibana Host
  # Scheme and port can be left out and will be set to the default (http and 5601)
  # In case you specify and additional path, the scheme is required: http://localhost:5601/path
  # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
  host: "10.25.193.X:5601"

  # Kibana Space ID
  # ID of the Kibana Space into which the dashboards should be loaded. By default,
  # the Default Space will be used.
  #space.id:

# =============================== Elastic Cloud ================================

# These settings simplify using Filebeat with the Elastic Cloud (https://cloud.elastic.co/).

# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
# `setup.kibana.host` options.
# You can find the `cloud.id` in the Elastic Cloud web UI.
#cloud.id:

# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
#cloud.auth:

# ================================== Outputs ===================================

# Configure what output to use when sending the data collected by the beat.

# ---------------------------- Elasticsearch Output ----------------------------
#output.elasticsearch:
  # Array of hosts to connect to.
 #hosts: ["localhost:9200"]

  # Protocol - either `http` (default) or `https`.
  #protocol: "https"

  # Authentication credentials - either API key or username/password.
  #api_key: "id:api_key"
  #username: "elastic"
  #password: "changeme"

# ------------------------------ Logstash Output -------------------------------
output.logstash:
  # The Logstash hosts
  hosts: ["https://10.25.193.X:5044"]


  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

  # Certificate for SSL client authentication
  #ssl.certificate: "/etc/pki/client/cert.pem"

  # Client Certificate Key
  #ssl.key: "/etc/pki/client/cert.key"
  ssl.verification_mode: none

# ================================= Processors =================================
processors:
  - add_host_metadata:
      when.not.contains.tags: forwarded
  - add_cloud_metadata: ~
  - add_docker_metadata: ~
  - add_kubernetes_metadata: ~

# ================================== Logging ===================================

# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
#logging.level: debug

# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publisher", "service".
#logging.selectors: ["*"]

# ============================= X-Pack Monitoring ==============================
# Filebeat can export internal metrics to a central Elasticsearch monitoring
# cluster.  This requires xpack monitoring to be enabled in Elasticsearch.  The
# reporting is disabled by default.

# Set to true to enable the monitoring reporter.
#monitoring.enabled: false

# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
# Filebeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
#monitoring.cluster_uuid:

# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:

# ============================== Instrumentation ===============================

# Instrumentation support for the filebeat.
#instrumentation:
    # Set to true to enable instrumentation of filebeat.
    #enabled: false

    # Environment in which filebeat is running on (eg: staging, production, etc.)
    #environment: ""

    # APM Server hosts to report instrumentation results to.
    #hosts:
    #  - http://localhost:8200

    # API Key for the APM Server(s).
    # If api_key is set then secret_token will be ignored.
    #api_key:

    # Secret token for the APM Server(s).
    #secret_token:


# ================================= Migration ==================================

# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true
15

I also take the opportunity to leave the logstash configuration

input {
  beats {
    port => 5044
  }
}
filter {
  if [type] == "syslog" {
     grok {
        match => { "message" => "%{SYSLOGLINE}" }
  }
     date {
        match => [ "timestamp", "MMM  d HH:mm:ss", "MMM dd HH:mm:ss" ]
     }
  }
}
output {
  elasticsearch {
    hosts => ["https://10.25.193.X:9200"]
    index => "%{[@metadata][beat]}-%{+YYYY.MM.dd}"
  }
}
16

Thanks

Again, if you cannot curl from the filebeat server to the Kibana server, then you have a some sort of network connectivity issue. And setup will not work.

Oh, Also if you want to use filebeats you should run full setup, not just the dashboard... Only loading the dashboards will not provide what you are looking for.

filebeat setup -e

That way the templates and all the other filebeat related assets get set up as well.

To do that you need to have filebeat pointing at Elasticsearch output, Not logstash. You only need to run this setup once per beat version.

Then after filebeat setup has been successfully run. Then you point the output back to logstash And then you can run filebeat normal

17

Are you saying that I should point the filebeats first in Elasticsearch, and run filebeats ... and then go back point the file beat in logstash and run again, is that what you want me to do?

18

There's two separate items here.

First is if you want to set up dashboards and you should set up the rest of the assets you need connectivity between filebeat and both elasticsearch and Kibana. It seems like you're having problems with that.

Second, in order to take full advantage of file beat, you need to run the full filebeat setup while Filebeat is pointing at Kibana and Elasticsearch.
filebeat setup -e

Then after you finished successfully setting up filebeat, you can then point filebeat at logstash... To actually run filebeat through logstash. I've written about this a number of times.

Generally, I tell people to first have file beat directly ingest into elasticsearch And then only after they have all that working then involve logstash.

These are just my suggestions.

In the end, none of this matters if you don't have the connectivity issue solved.

It's late here. I'll check in tomorrow

Looks like we finally documented this

19

I will test and give feedback

20

I made the changes as requested. That is, I configured filebeat to speak directly to elasticsearch, but when I run the command sudo filebeat setup -e, I am getting the error below:


{"log.level":"error","@timestamp":"2022-11-01T23:22:24.538+0100","log.logger":"esclientleg","log.origin":{"file.name":"transport/logging.go","file.line":38},"message":"Error dialing tls: first record does not look like a TLS handshake","service.name":"filebeat","network":"tcp","address":"10.25.193.195:9200","ecs.version":"1.6.0"}
{"log.level":"error","@timestamp":"2022-11-01T23:22:24.538+0100","log.logger":"esclientleg","log.origin":{"file.name":"eslegclient/connection.go","file.line":235},"message":"error connecting to Elasticsearch at https://10.25.193.195:9200: Get \"https://10.25.193.195:9200\": http: server gave HTTP response to HTTPS client","service.name":"filebeat","ecs.version":"1.6.0"}
{"log.level":"error","@timestamp":"2022-11-01T23:22:24.538+0100","log.origin":{"file.name":"instance/beat.go","file.line":1056},"message":"Exiting: couldn't connect to any of the configured Elasticsearch hosts. Errors: [error connecting to Elasticsearch at https://10.25.193.19:9200: Get \"https://10.25.193.19:9200\": http: server gave HTTP response to HTTPS client]","service.name":"filebeat","ecs.version":"1.6.0"}
Exiting: couldn't connect to any of the configured Elasticsearch hosts. Errors: [error connecting to Elasticsearch at https://10.25.193.19:9200: Get "https://10.25.193.19:9200": http: server gave HTTP response to HTTPS client]