Metric beat module list empty

Hello Team,

I am using ELK6.4.0 and beat 6.4.0. Today i have installed the metricbeat6.4.0 over my 3 ubuntu16.04 servers. When i installed them all things were working properly except disk data was not avaialble on dashboard. But after some time i want to disable some module then i face issue. When i check the module list its showing empty for both enabled as well disabled. Please find the output:

root@xyz:~# metricbeat modules list
Enabled:

Disabled:

When i tried enable or disable module then its showing module doesn't exist. Please refer the below output:

root@xyz:~# metricbeat modules disable system
Module system doesn't exist!
root@xyz:~# metricbeat modules enable nginx
Module nginx doesn't exist!

Please find the metricbeat.yml config:

###################### Metricbeat Configuration Example #######################

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

#==========================  Modules configuration ============================

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

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

  # 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` CLI flag or 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: "xyz:5601"

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

# These settings simplify using metricbeat 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"]

  # Optional protocol and basic auth credentials.
  #protocol: "https"
  #username: "elastic"
  #password: "changeme"

#----------------------------- Logstash output --------------------------------
output.logstash:
  # The Logstash hosts
  hosts: ["xyz:5044"]

  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
  ssl.certificate_authorities: ["/etc/pki/tls/ca.crt"]
  ssl.certificate: "/etc/pki/tls/client.crt"
  ssl.key: "/etc/pki/tls/client.key"
  ssl.key_passphrase: "ky9D=h=w2z2uUCjRqqWF"


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

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

#================================ 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: ["*"]

I have all the module .yml file inside the modules.d directory. Please refer the below output:

root@xyz:/usr/share/metricbeat/modules.d# ls
aerospike.yml.disabled  dropwizard.yml.disabled     graphite.yml.disabled  kibana.yml.disabled      mongodb.yml.disabled  postgresql.yml.disabled  traefik.yml.disabled
apache.yml.disabled     elasticsearch.yml.disabled  haproxy.yml.disabled   kubernetes.yml.disabled  munin.yml.disabled    prometheus.yml.disabled  uwsgi.yml.disabled
ceph.yml.disabled       envoyproxy.yml.disabled     http.yml.disabled      kvm.yml.disabled         mysql.yml.disabled    rabbitmq.yml.disabled    vsphere.yml.disabled
couchbase.yml.disabled  etcd.yml.disabled           jolokia.yml.disabled   logstash.yml.disabled    nginx.yml.disabled    redis.yml.disabled       windows.yml.disabled
docker.yml.disabled     golang.yml.disabled         kafka.yml.disabled     memcached.yml.disabled   php_fpm.yml.disabled  system.yml               zookeeper.yml.disabled

Please help me to troubleshoot the issue.

Thank you for reporting this!

I'm guessing you are using Metricbeat 6.4, which was released with a known issue: https://github.com/elastic/beats/issues/8104

6.4.1 should include the fix, in the meanwhile, there is a workaround explained in the given link

1 Like

Hello Carlos,

Thank you for your response.

Yes, i am using metricbeat6.4.0. I am facing one more issue, when i am checking the logs on kibana dashboard for metricbeat-* index its showing error. But i am getting logs on dashboard because metricbeat dashboard is showing graphs for system module.

Please refer the below screenshot for system module:

Screenshot for error when i check logs in metricbeat-* index:-

Please help me to troubleshoot the issue.

Thanks.

Hi,

Did you run the setup command? Not only for dashboards, but the full setup, that one should have created the index pattern for you. It looks like if something went wrong there

Br,

Hello Carlos,

Thank you for your response.

Yes, i have run the setup command for full setup. in template i am using index filebeat-6.4.0-*.

But on kibana i have created the index filebeat-*. Its working fine. The above issue is fixed after making some changes in nginx configuration.

I have added the below line in nginx configuration:-

proxy_buffer_size          128k;
proxy_buffers              4 256k;
proxy_busy_buffers_size    256k;

Now i have one question:-

i have created the index on kibana with name filebeat-*

Any bad impact of this naming convention?

Thanks.

The index pattern looks correct, glad you fixed the issue!

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