Logstash monitoring problem

Elastic Stack Logstash
1

Hi all. We are trying to use stack monitoring feature. But after we enabled internal monitoring we see only Elasticsearch and Kibana instances.
Entering SETUP mode show Logstash and Beats with empty values and drops error HTTP 503

[exception] Security must be explicitly enabled when using a [basic] license. Enable security by setting [xpack.security.enabled] to [true] in the elasticsearch.yml file and restart the node.: Check the Elasticsearch Monitoring cluster network connection or the load level of the nodes.

After enabling this feature in elasticsearch.yml Kibana shows "Kibana server is not ready yet" and i guess its a security issue, because all services up and running.
Besides that we can successfuly query logstash by

curl -XGET 'localhost:9600/_node/pipelines?pretty'

The question is, do we really need to enable xpack.security for logstash api monitoring? if we dont need any authentication and security features at all.

2

@dennys_84

You don't need security to see logstash monitoring data. Your experience is an existing bug here -> https://github.com/elastic/kibana/issues/53129

For logstash, do you have any configured pipelines? Can you share your logstash and pipeline configuration?

3

Thank you for reply!
Logstash has default settings
Pipeline looks like this:

input {
  beats {
    port => 5044
  }
}

filter {
  if [message] {
    mutate {
      copy => { "message" => "message_head" }
    }
  }
  mutate {
    split => ["message_head", "
"]}

  mutate {
    replace => { "message_head" => "%{[message_head][0]}" }
    add_tag => ["logstash_output_tag"]
  }
 
 if [winlog][event_data][MemberName] {
    mutate { copy => { "[winlog][event_data][MemberName]" => "dc_member" } }

    mutate {
      split => ["dc_member", ","]
    }
    mutate {
      add_field => {
        "dc_member_cn" => "%{[dc_member][0]}"
        "dc_member_ou" => "%{[dc_member][2]}"
      }
      remove_field => "dc_member"
    }
    mutate { split => ["dc_member_cn", "="]
    }
    mutate {
      replace => { "dc_member_cn" => "%{[dc_member_cn][1]}" }
    }
    mutate {
      split => ["dc_member_ou", "="]
    }
    mutate {
      replace => { "dc_member_ou" => "%{[dc_member_ou][1]}" }
    }
  }
  
  # Drop event providers
  if [event][provider] in  ["ESENT", "Microsoft-Windows-Security-SPP"] {
    drop { }
  }
# Drop Application events
  if [event][code] in  [6000, 9027, 17550] and [winlog][channel] == "Application" {
    drop { }
  }
# Drop System events
  if [event][code] in [6013, 7001, 7002, 7036, 7040]  and [winlog][channel] == "System" {
    drop { }
  }
# Other filters
  if [event][code] == 4624 and [winlog][event_data][LogonType] not in ["7", "10"] {
    drop { }
  }

}

output {
   elasticsearch {
     hosts => ["http://localhost:9200"]
     index => "logstash-000001"
  }
}
4

Great, thanks.

Let's see what indices you have in ES.

Can you run GET _cat/indices and return the result?

5 
green open .monitoring-es-7-2020.01.15     -CelSdPSR32uvCfEB6amsw 1 0  42926  27115  18.2mb  18.2mb
green open .monitoring-es-7-2020.01.17     OZDpuAxmQJyfgayz_LfWtA 1 0 129998  85998  57.7mb  57.7mb
green open .monitoring-es-7-2020.01.16     jVFiD2lVTbOI5i8IXRma7g 1 0  54433  33731  22.6mb  22.6mb
green open .monitoring-es-7-2020.01.22     5vp0cgm9Qdi0A3c5MdQBrw 1 0 151123 120720  97.5mb  97.5mb
green open .monitoring-kibana-7-2020.01.22 AYPQcu7WQ4Gga9WpBamm8A 1 0   6030      0   1.4mb   1.4mb
green open .monitoring-es-7-2020.01.21     0araWbpgR-yYajAaV2FBYw 1 0 198808 155430 111.5mb 111.5mb
green open .monitoring-kibana-7-2020.01.21 T5IhjGEFQKq5mIQ9zOhSPA 1 0   8630      0     2mb     2mb
green open .monitoring-kibana-7-2020.01.20 SpQSuImHR2KZG38JBYPiuA 1 0   8612      0     2mb     2mb
green open .apm-agent-configuration        _XVK8h4ZTtGKTULirbHkpA 1 0      0      0    283b    283b
green open .monitoring-kibana-7-2020.01.15 UpWXU_daSze2l5-AauaqZA 1 0   3602      0 852.2kb 852.2kb
green open .monitoring-es-7-2020.01.20     Qzy6fA-QQpufZrxhSevueg 1 0 181804 137872 103.7mb 103.7mb
green open .monitoring-kibana-7-2020.01.19 wxNLKyHCR0Wf6TtpGI4dBg 1 0    663      0 268.3kb 268.3kb
green open .kibana_1                       Y1nSz76CSM6YUzkrKXcrxQ 1 0     95      8 126.3kb 126.3kb
green open .monitoring-kibana-7-2020.01.18 evxJZrscRSaTfqEA6lzLnA 1 0   6849      0   1.4mb   1.4mb
green open .monitoring-kibana-7-2020.01.17 iBbdxhAvTcqoiB6QZM35RA 1 0   8628      0   1.9mb   1.9mb
green open .monitoring-kibana-7-2020.01.16 FT-dXecXT3ODFjzYqbTbRQ 1 0   3916      0 876.7kb 876.7kb
green open logstash-000001                 XEEpK1amTA6GG5HUbfUb0A 1 0   7763      0  12.1mb  12.1mb
green open .kibana_task_manager_1          JI5gswJsSN-nMCY-J7HzrQ 1 0      2      2  54.2kb  54.2kb
green open .monitoring-es-7-2020.01.19     ety22M8gQ92Ewegd52mebw 1 0  12895   8948   8.1mb   8.1mb
green open .monitoring-es-7-2020.01.18     OOmaFl71QJ612W8G42Safg 1 0 125545     24  47.8mb  47.8mb
6

Hmm. I'm not seeing any .monitoring-logstash-7-* indices.

Can you share your logstash config?

7 
# Settings file in YAML
#
# Settings can be specified either in hierarchical form, e.g.:
#
#   pipeline:
#     batch:
#       size: 125
#       delay: 5
#
# Or as flat keys:
#
#   pipeline.batch.size: 125
#   pipeline.batch.delay: 5
#
# ------------  Node identity ------------
#
# Use a descriptive name for the node:
#
 node.name: elk-server
#
# If omitted the node name will default to the machine's host name
#
# ------------ Data path ------------------
#
# Which directory should be used by logstash and its plugins
# for any persistent needs. Defaults to LOGSTASH_HOME/data
#
path.data: /var/lib/logstash
#
# ------------ Pipeline Settings --------------
#
# The ID of the pipeline.
#
# pipeline.id: main
#
# Set the number of workers that will, in parallel, execute the filters+outputs
# stage of the pipeline.
#
# This defaults to the number of the host's CPU cores.
#
# pipeline.workers: 2
#
# How many events to retrieve from inputs before sending to filters+workers
#
# pipeline.batch.size: 125
#
# How long to wait in milliseconds while polling for the next event
# before dispatching an undersized batch to filters+outputs
#
# pipeline.batch.delay: 50
#
# Force Logstash to exit during shutdown even if there are still inflight
# events in memory. By default, logstash will refuse to quit until all
# received events have been pushed to the outputs.
#
# WARNING: enabling this can lead to data loss during shutdown
#
# pipeline.unsafe_shutdown: false
#
# ------------ Pipeline Configuration Settings --------------
#
# Where to fetch the pipeline configuration for the main pipeline
#
# path.config:
#
# Pipeline configuration string for the main pipeline
#
# config.string:
#
# At startup, test if the configuration is valid and exit (dry run)
#
# config.test_and_exit: false
#
# Periodically check if the configuration has changed and reload the pipeline
# This can also be triggered manually through the SIGHUP signal
#
# config.reload.automatic: false
#
# How often to check if the pipeline configuration has changed (in seconds)
#
# config.reload.interval: 3s
#
# Show fully compiled configuration as debug log message
# NOTE: --log.level must be 'debug'
#
# config.debug: false
#
# When enabled, process escaped characters such as \n and \" in strings in the
# pipeline configuration files.
#
# config.support_escapes: false
#
# ------------ Module Settings ---------------
# Define modules here.  Modules definitions must be defined as an array.
# The simple way to see this is to prepend each `name` with a `-`, and keep
# all associated variables under the `name` they are associated with, and
# above the next, like this:
#
# modules:
#   - name: MODULE_NAME
#     var.PLUGINTYPE1.PLUGINNAME1.KEY1: VALUE
#     var.PLUGINTYPE1.PLUGINNAME1.KEY2: VALUE
#     var.PLUGINTYPE2.PLUGINNAME1.KEY1: VALUE
#     var.PLUGINTYPE3.PLUGINNAME3.KEY1: VALUE
#
# Module variable names must be in the format of
#
# var.PLUGIN_TYPE.PLUGIN_NAME.KEY
#
# modules:
#
# ------------ Cloud Settings ---------------
# Define Elastic Cloud settings here.
# Format of cloud.id is a base64 value e.g. dXMtZWFzdC0xLmF3cy5mb3VuZC5pbyRub3RhcmVhbCRpZGVudGlmaWVy
# and it may have an label prefix e.g. staging:dXMtZ...
# This will overwrite 'var.elasticsearch.hosts' and 'var.kibana.host'
# cloud.id: <identifier>
#
# Format of cloud.auth is: <user>:<pass>
# This is optional
# If supplied this will overwrite 'var.elasticsearch.username' and 'var.elasticsearch.password'
# If supplied this will overwrite 'var.kibana.username' and 'var.kibana.password'
# cloud.auth: elastic:<password>
#
# ------------ Queuing Settings --------------
#
# Internal queuing model, "memory" for legacy in-memory based queuing and
# "persisted" for disk-based acked queueing. Defaults is memory
#
# queue.type: memory
#
# If using queue.type: persisted, the directory path where the data files will be stored.
# Default is path.data/queue
#
# path.queue:
#
# If using queue.type: persisted, the page data files size. The queue data consists of
# append-only data files separated into pages. Default is 64mb
#
# queue.page_capacity: 64mb
#
# If using queue.type: persisted, the maximum number of unread events in the queue.
# Default is 0 (unlimited)
#
# queue.max_events: 0
#
# If using queue.type: persisted, the total capacity of the queue in number of bytes.
# If you would like more unacked events to be buffered in Logstash, you can increase the
# capacity using this setting. Please make sure your disk drive has capacity greater than
# the size specified here. If both max_bytes and max_events are specified, Logstash will pick
# whichever criteria is reached first
# Default is 1024mb or 1gb
#
# queue.max_bytes: 1024mb
#
# If using queue.type: persisted, the maximum number of acked events before forcing a checkpoint
# Default is 1024, 0 for unlimited
#
# queue.checkpoint.acks: 1024
#
# If using queue.type: persisted, the maximum number of written events before forcing a checkpoint
# Default is 1024, 0 for unlimited
#
# queue.checkpoint.writes: 1024
#
# If using queue.type: persisted, the interval in milliseconds when a checkpoint is forced on the head page
# Default is 1000, 0 for no periodic checkpoint.
#
# queue.checkpoint.interval: 1000
#
# ------------ Dead-Letter Queue Settings --------------
# Flag to turn on dead-letter queue.
#
# dead_letter_queue.enable: false

# If using dead_letter_queue.enable: true, the maximum size of each dead letter queue. Entries
# will be dropped if they would increase the size of the dead letter queue beyond this setting.
# Default is 1024mb
# dead_letter_queue.max_bytes: 1024mb

# If using dead_letter_queue.enable: true, the directory path where the data files will be stored.
# Default is path.data/dead_letter_queue
#
# path.dead_letter_queue:
#
# ------------ Metrics Settings --------------
#
# Bind address for the metrics REST endpoint
#
# http.host: "127.0.0.1"
#
# Bind port for the metrics REST endpoint, this option also accept a range
# (9600-9700) and logstash will pick up the first available ports.
#
# http.port: 9600-9700
#
# ------------ Debugging Settings --------------
#
# Options for log.level:
#   * fatal
#   * error
#   * warn
#   * info (default)
#   * debug
#   * trace
#
# log.level: info
path.logs: /var/log/logstash
#
# ------------ Other Settings --------------
#
# Where to find custom plugins
# path.plugins: []
#
# Flag to output log lines of each pipeline in its separate log file. Each log filename contains the pipeline.name
# Default is false
# pipeline.separate_logs: false
#
# ------------ X-Pack Settings (not applicable for OSS build)--------------
#
# X-Pack Monitoring
# https://www.elastic.co/guide/en/logstash/current/monitoring-logstash.html
xpack.monitoring.enabled: true
#xpack.monitoring.elasticsearch.username: logstash_system
#xpack.monitoring.elasticsearch.password: password
xpack.monitoring.elasticsearch.hosts: ["http://localhost:9200"]
#xpack.monitoring.elasticsearch.ssl.certificate_authority: [ "/path/to/ca.crt" ]
#xpack.monitoring.elasticsearch.ssl.truststore.path: path/to/file
#xpack.monitoring.elasticsearch.ssl.truststore.password: password
#xpack.monitoring.elasticsearch.ssl.keystore.path: /path/to/file
#xpack.monitoring.elasticsearch.ssl.keystore.password: password
#xpack.monitoring.elasticsearch.ssl.verification_mode: certificate
#xpack.monitoring.elasticsearch.sniffing: false
#xpack.monitoring.collection.interval: 10s
xpack.monitoring.collection.pipeline.details.enabled: true
#
# X-Pack Management
# https://www.elastic.co/guide/en/logstash/current/logstash-centralized-pipeline-management.html
#xpack.management.enabled: false
#xpack.management.pipeline.id: ["main", "apache_logs"]
#xpack.management.elasticsearch.username: logstash_admin_user
#xpack.management.elasticsearch.password: password
#xpack.management.elasticsearch.hosts: ["https://es1:9200", "https://es2:9200"]
#xpack.management.elasticsearch.ssl.certificate_authority: [ "/path/to/ca.crt" ]
#xpack.management.elasticsearch.ssl.truststore.path: /path/to/file
#xpack.management.elasticsearch.ssl.truststore.password: password
#xpack.management.elasticsearch.ssl.keystore.path: /path/to/file
#xpack.management.elasticsearch.ssl.keystore.password: password
#xpack.management.elasticsearch.ssl.verification_mode: certificate
#xpack.management.elasticsearch.sniffing: false
#xpack.management.logstash.poll_interval: 5s
8

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