ERROR Index management Winlogbeat 7.9.0

zombietek · September 19, 2020, 11:59pm

Hi,

I saw this old thread(Error index management Filebeat to Logstash) though it was for filebeat and my issue is for winlogbeat, I'll give it a try.

I have winlogbeat version 7.9.0 and configured it to send output to logstash. When I issued the command winlogbeat.exe setup -e, I am getting an error on Index management but when I issued the same command without "setup" the error is not showing up.

Thanks!

warkolm · September 20, 2020, 9:24pm

Welcome to our community!

Can you please edit your post and remove the formatting, it's very difficult to follow your question as it looks now.

zombietek · September 20, 2020, 9:40pm

Hi Mark,

I just edited my post and hope it looks good now.

Thanks!

warkolm · September 20, 2020, 9:40pm

Can you share the error please?

zombietek · September 20, 2020, 9:43pm

PS C:\Program Files\Winlogbeat> .\winlogbeat.exe setup -e
2020-09-20T17:42:33.811-0400 INFO instance/beat.go:640 Home path: [C:\Program Files\Winlogbeat] Config path: [C:\Program Files\Winlogbeat] Data path: [C:\Program Files\Winlogbeat\data] Logs path: [C:\Program Files\Winlogbeat\logs]
2020-09-20T17:42:33.818-0400 INFO instance/beat.go:648 Beat ID: c22e087e-398f-4888-b610-aa3ed3f5ec11
2020-09-20T17:42:33.846-0400 INFO [beat] instance/beat.go:976 Beat info {"system_info": {"beat": {"path": {"config": "C:\Program Files\Winlogbeat", "data": "C:\Program Files\Winlogbeat\data", "home": "C:\Program Files\Winlogbeat", "logs": "C:\Program Files\Winlogbeat\logs"}, "type": "winlogbeat", "uuid": "c22e087e-398f-4888-b610-aa3ed3f5ec11"}}}
2020-09-20T17:42:33.846-0400 INFO [beat] instance/beat.go:985 Build info {"system_info": {"build": {"commit": "ad823eca4cc74439d1a44351c596c12ab51054f5", "libbeat": "7.9.1", "time": "2020-09-01T20:10:59.000Z", "version": "7.9.1"}}}
2020-09-20T17:42:33.850-0400 INFO [beat] instance/beat.go:988 Go runtime info {"system_info": {"go": {"os":"windows","arch":"amd64","max_procs":2,"version":"go1.14.7"}}}
2020-09-20T17:42:33.865-0400 INFO [beat] instance/beat.go:992 Host info {"system_info": {"host": {"architecture":"x86_64","boot_time":"2020-09-18T19:02:33.17-04:00","name":"DESKTOP-PTFFRML","ip":["169.254.124.106/16","192.168.163.132/24","fe80::4537:c6b:5b57:29d/64","169.254.2.157/16","::1/128","127.0.0.1/8"],"kernel_version":"10.0.19041.508 (WinBuild.160101.0800)","mac":["00:0c:29:61:6a:69","00:0c:29:61:6a:5f","00:26:83:17:e2:c1"],"os":{"family":"windows","platform":"windows","name":"Windows 10 Pro","version":"10.0","major":10,"minor":0,"patch":0,"build":"19041.508"},"timezone":"EDT","timezone_offset_sec":-14400,"id":"9ae6ad27-bda1-4ffe-b40c-3252934f7957"}}}
2020-09-20T17:42:33.866-0400 INFO [beat] instance/beat.go:1021 Process info {"system_info": {"process": {"cwd": "C:\Program Files\Winlogbeat", "exe": "C:\Program Files\Winlogbeat\winlogbeat.exe", "name": "winlogbeat.exe", "pid": 7904, "ppid": 3328, "start_time": "2020-09-20T17:42:33.633-0400"}}}
2020-09-20T17:42:33.866-0400 INFO instance/beat.go:299 Setup Beat: winlogbeat; Version: 7.9.1
2020-09-20T17:42:33.868-0400 INFO [publisher] pipeline/module.go:113 Beat name: DESKTOP-PTFFRML
2020-09-20T17:42:33.868-0400 INFO beater/winlogbeat.go:69 State will be read from and persisted to C:\Program Files\Winlogbeat\data.winlogbeat.yml
2020-09-20T17:42:33.923-0400 WARN [cfgwarn] registered_domain/registered_domain.go:60 BETA: The registered_domain processor is beta.
2020-09-20T17:42:34.023-0400 WARN [cfgwarn] registered_domain/registered_domain.go:60 BETA: The registered_domain processor is beta.
2020-09-20T17:42:34.046-0400 ERROR instance/beat.go:951 Exiting: Index management requested but the Elasticsearch output is not configured/enabled
Exiting: Index management requested but the Elasticsearch output is not configured/enabled

warkolm · September 20, 2020, 9:45pm

Thanks. Can you post your filebeat.yml?

Please format your code/logs/config using the </> button, or markdown style back ticks. It helps to make things easy to read which helps us help you

zombietek · September 20, 2020, 9:53pm

I only use winlogbeat and not filebeat in my setup. Do you want the winlogbeat.yml?


PS C:\Program Files\Winlogbeat> .\winlogbeat.exe setup -e
2020-09-20T17:42:33.811-0400    INFO    instance/beat.go:640    Home path: [C:\Program Files\Winlogbeat] Config path: [C:\Program Files\Winlogbeat] Data path: [C:\Program Files\Winlogbeat\data] Logs path: [C:\Program Files\Winlogbeat\logs]
2020-09-20T17:42:33.818-0400    INFO    instance/beat.go:648    Beat ID: c22e087e-398f-4888-b610-aa3ed3f5ec11
2020-09-20T17:42:33.846-0400    INFO    [beat]  instance/beat.go:976    Beat info       {"system_info": {"beat": {"path": {"config": "C:\\Program Files\\Winlogbeat", "data": "C:\\Program Files\\Winlogbeat\\data", "home": "C:\\Program Files\\Winlogbeat", "logs": "C:\\Program Files\\Winlogbeat\\logs"}, "type": "winlogbeat", "uuid": "c22e087e-398f-4888-b610-aa3ed3f5ec11"}}}
2020-09-20T17:42:33.846-0400    INFO    [beat]  instance/beat.go:985    Build info      {"system_info": {"build": {"commit": "ad823eca4cc74439d1a44351c596c12ab51054f5", "libbeat": "7.9.1", "time": "2020-09-01T20:10:59.000Z", "version": "7.9.1"}}}
2020-09-20T17:42:33.850-0400    INFO    [beat]  instance/beat.go:988    Go runtime info {"system_info": {"go": {"os":"windows","arch":"amd64","max_procs":2,"version":"go1.14.7"}}}
2020-09-20T17:42:33.865-0400    INFO    [beat]  instance/beat.go:992    Host info       {"system_info": {"host": {"architecture":"x86_64","boot_time":"2020-09-18T19:02:33.17-04:00","name":"DESKTOP-PTFFRML","ip":["169.254.124.106/16","192.168.163.132/24","fe80::4537:c6b:5b57:29d/64","169.254.2.157/16","::1/128","127.0.0.1/8"],"kernel_version":"10.0.19041.508 (WinBuild.160101.0800)","mac":["00:0c:29:61:6a:69","00:0c:29:61:6a:5f","00:26:83:17:e2:c1"],"os":{"family":"windows","platform":"windows","name":"Windows 10 Pro","version":"10.0","major":10,"minor":0,"patch":0,"build":"19041.508"},"timezone":"EDT","timezone_offset_sec":-14400,"id":"9ae6ad27-bda1-4ffe-b40c-3252934f7957"}}}
2020-09-20T17:42:33.866-0400    INFO    [beat]  instance/beat.go:1021   Process info    {"system_info": {"process": {"cwd": "C:\\Program Files\\Winlogbeat", "exe": "C:\\Program Files\\Winlogbeat\\winlogbeat.exe", "name": "winlogbeat.exe", "pid": 7904, "ppid": 3328, "start_time": "2020-09-20T17:42:33.633-0400"}}}
2020-09-20T17:42:33.866-0400    INFO    instance/beat.go:299    Setup Beat: winlogbeat; Version: 7.9.1
2020-09-20T17:42:33.868-0400    INFO    [publisher]     pipeline/module.go:113  Beat name: DESKTOP-PTFFRML
2020-09-20T17:42:33.868-0400    INFO    beater/winlogbeat.go:69 State will be read from and persisted to C:\Program Files\Winlogbeat\data\.winlogbeat.yml
2020-09-20T17:42:33.923-0400    WARN    [cfgwarn]       registered_domain/registered_domain.go:60       BETA: The registered_domain processor is beta.
2020-09-20T17:42:34.023-0400    WARN    [cfgwarn]       registered_domain/registered_domain.go:60       BETA: The registered_domain processor is beta.
2020-09-20T17:42:34.046-0400    ERROR   instance/beat.go:951    Exiting: Index management requested but the Elasticsearch output is not configured/enabled
Exiting: Index management requested but the Elasticsearch output is not configured/enabled

warkolm · September 20, 2020, 10:06pm

Yes, sorry that's what I meant.

zombietek · September 20, 2020, 10:13pm

###################### Winlogbeat Configuration Example ########################

# This file is an example configuration file highlighting only the most common
# options. The winlogbeat.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/winlogbeat/index.html

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

# event_logs specifies a list of event logs to monitor as well as any
# accompanying options. The YAML data type of event_logs is a list of
# dictionaries.
#
# The supported keys are name (required), tags, fields, fields_under_root,
# forwarded, ignore_older, level, event_id, provider, and include_xml. Please
# visit the documentation for the complete details of each option.
# https://go.es.io/WinlogbeatConfig

winlogbeat.event_logs:
  - name: Application
   
  - name: System

  - name: Security
      
  - name: Microsoft-Windows-Sysmon/Operational
    processors:
      - script:
          lang: javascript
          id: sysmon
          file: ${path.home}/module/sysmon/config/winlogbeat-sysmon.js

  - name: Windows PowerShell
    event_id: 400, 403, 600, 800
    processors:
      - script:
          lang: javascript
          id: powershell
          file: ${path.home}/module/powershell/config/winlogbeat-powershell.js

  - name: Microsoft-Windows-PowerShell/Operational
    event_id: 4103, 4104, 4105, 4106
    processors:
      - script:
          lang: javascript
          id: powershell
          file: ${path.home}/module/powershell/config/winlogbeat-powershell.js

  - name: ForwardedEvents
    tags: [forwarded]
    processors:
      - script:
          when.equals.winlog.channel: Security
          lang: javascript
          id: security
          file: ${path.home}/module/security/config/winlogbeat-security.js
      - script:
          when.equals.winlog.channel: Microsoft-Windows-Sysmon/Operational
          lang: javascript
          id: sysmon
          file: ${path.home}/module/sysmon/config/winlogbeat-sysmon.js
      - script:
          when.equals.winlog.channel: Windows PowerShell
          lang: javascript
          id: powershell
          file: ${path.home}/module/powershell/config/winlogbeat-powershell.js
      - script:
          when.equals.winlog.channel: Microsoft-Windows-PowerShell/Operational
          lang: javascript
          id: powershell
          file: ${path.home}/module/powershell/config/winlogbeat-powershell.js

# ====================== 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: "localhost: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: ["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: ["192.168.163.150: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"

# ================================= 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",
# "publish", "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

zombietek · September 23, 2020, 4:10pm

Hi,

I just wanted to follow up if there's news on this.

Thanks!

system · October 21, 2020, 6:10pm

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