Logs don't show up when trying to use logstash

Elastic Stack Logstash
1

when trying to execute winlogbeat.exe from powershell i receive this kind of errors in logs

{"log.level":"error","@timestamp":"xxx","log.logger":"publisher_pipeline_output","log.origin":{"file.name":"pipeline/client_worker.go","file.line":150},"message":"Failed to connect to backoff(async(tcp://logstash_host:5044)): read tcp 192.168.10.44:52607->logstash_host:5044: wsarecv: "An existing connection must have been closed by the remote host","service.name":"winlogbeat","ecs.version":"1.6.0"}

if i try with .\winlogbeat.exe setup -e it says

Exiting: index management requested but the Elasticsearch output is not configured/enabled
2

Please share your winlogbeat.yml, you probably have options enabled that only works if your output is elasticsearch.

Set setup.template.enabled and setup.ilm.enabled to false for example.

3

this is mi winlogbeat.yml

# ======================== Winlogbeat specific options =========================

winlogbeat.event_logs:
  - name: Application
    ignore_older: 72h

  - name: System

  - name: Security
    level: critical, error, warning

  - name: Microsoft-Windows-Sysmon/Operational

  - name: Windows PowerShell
    event_id: 400, 403, 600, 800

  - name: Microsoft-Windows-PowerShell/Operational
    event_id: 4103, 4104, 4105, 4106

  - name: ForwardedEvents
    tags: [forwarded]

winlogbeat.registry_file: C:/ProgramData/winlogbeat/winlogbeat.yml

# ====================== Elasticsearch template settings =======================

#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: "http://kibana: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 Winlogbeat 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: ["https://elasticsearch:9200"]
##
##  # Protocol - either `http` (default) or `https`.
##  #protocol: "https"
##
##  # Authentication credentials - either API key or username/password.
##  #api_key: "id:api_key"
#  username: "xxxx"
#  password: "${ES_PWD}"
#  ssl:
#    certificate_authorities: ['C:/Program Files/Winlogbeat/new_ca.pem']
#    certificate: "C:/Program Files/Winlogbeat/es01_cert.pem"
#    key: "C:/Program Files/Winlogbeat/es01.key"

  ## Pipeline to route events to security, sysmon, or powershell pipelines.
  #pipeline: "winlogbeat-%{[agent.version]}-routing"

# ------------------------------ Logstash Output -------------------------------
output.logstash:
  # The Logstash hosts
  enabled: true
  hosts: ["logstash:5044"]
  ssl:
    enabled: true
    certificate_authorities: ['C:/Program Files/Winlogbeat/new_ca.pem']
    certificate: "C:/Program Files/Winlogbeat/es01_cert.pem"
    key: "C:/Program Files/Winlogbeat/es01.key"
  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
 # output.file:
 #   path: "C:\Users\d.mammone\Desktop\Winlogbeat\tmp"
 #   filename: winlogbeat

  
 

# ================================= Processors =================================
processors:
  - add_host_metadata:
      when.not.contains.tags: forwarded
  - add_cloud_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 ==============================
# Winlogbeat 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
# Winlogbeat 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 winlogbeat.
#instrumentation:
    # Set to true to enable instrumentation of winlogbeat.
    #enabled: false

    # Environment in which winlogbeat 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
4

i tryed to set

and

to false but I still receive this : Exiting: index management requested but the Elasticsearch output is not configured/enabled

5

This need setup.kibana and output.elasticsearch to import ingestion pipeline and templates. Try to set and run without Logstash setup.
Winlogbeat works fine without Logstash.

6

yes I already did this without logstash, isn't it better if I use it though?

7

No need. Elasticsearch has own ingestion pipeline, Winlogbeat has out-of-box module and Kibana dashboard, I don't see the point for additional server.

8

all right, thanks

9

Logstash is needed when you need complex data transformations. I don't know what is a situation in your case, if you don't want to remove fields, transform data, then you don't need.
Whenever is the clean situation with log formats, and they are supported by Filebeat, I would stick to Filebeat. Faster approach, easier to maintain, and upgrade is supported.

10

by transform data, you mean that I can modify logs in order to see only things that I want of them? removing all unnecessary stuff?

11

Yes,something like that, remove fields, conversions, if then...

12

that would be helpful, but until logstash does not work there is nothing I can do

13

I see nothing in the winlogbeat.yml that would make it try to talk with elasticsearch.

Which version are you using?

14

8.3.2

15

now I have upgraded to 8.4.1 but nothing has changed, do you have a solution?

16

Unfortunately no.

If you did not set setup.template.enabled and setup.ilm.enabled or set both to false, then winlogbeat should not try to talk to elasticsearch.

My recomendation is to double check your config file to make sure that those two options are commented, as well the output.elasticsearch, after you confirm this, if it still not work, maybe try to open an issue in Github.

17

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.