Why can't I import the metricbeat dashboard on Freebsd?

Elastic Stack Beats
1

Good afternoon / afternoon, why can't I import the metricbeat dashboard on Freebsd?

Next is the log Metricbaet Output.

Feb 14 15:32:32 smtp140 metricbeat[3834]: ERROR instance/beat.go:667 Exiting: 1 error: 1 error: metricset 'system/uptime' is not registered, metricset not found
Feb 14 15:32:33 smtp140 metricbeat[3844]: ERROR instance/metrics.go:61 Error while getting memory usage: error retrieving process stats: cannot find matching process for pid=3844
Feb 14 15:32:33 smtp140 metricbeat[3844]: ERROR instance/metrics.go:92 Error retrieving CPU percentages: error retrieving process stats: cannot find matching process for pid=3844
Feb 14 15:32:33 smtp140 metricbeat[3844]: ERROR instance/beat.go:667 Exiting: 1 error: 1 error: metricset 'system/uptime' is not registered, metricset not found

Any idea ?

2

The above error does not have much to do with the dashboard I think. The above metricsets you have configured in the config but are not supported on FreeBSD. If you disable these, you should be able to load your dashboards.

What's the command you use to load dashboards?

3

it is metricbeat setup --dashboards

4

What are the metricsets enabled here?

5

Yes, metricset is enabled

Pada tanggal Sel, 19 Feb 2019 9.56 AM, Kaiyan Sheng via Discuss the Elastic Stack elastic@discoursemail.com menulis:

6

Are you using the system module? Can you tell me what are the metricsets that are enabled? It should be in system.yml:

  • module: system
    metricsets:
    • cpu # CPU usage
    • load # CPU load averages
    • memory # Memory usage
    • network # Network IO
    • process # Per process metrics
    • process_summary # Process summary
    • uptime # System Uptime
7

@Tutorial_Linux_Indon, Can you please share your metricbeat.yml config file? It will be more helpful to check the configuration issue.

Thanks.

8

it is konfig metricbeat.yml

#============================== 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"
host: "10.10.10.1:8080"

#-------------------------- Elasticsearch output ------------------------------
output.elasticsearch:

Array of hosts to connect to.

#hosts: ["localhost:9200"]
hosts: ["10.10.10.1:8001"]

Optional protocol and basic auth credentials.

#protocol: "https"
#username: "elastic"
#password: "changeme"

#----------------------------- Logstash output --------------------------------
#output.logstash:

The Logstash hosts

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

9

yes, i enable metricset

#------------------------------- System Module -------------------------------

  • module: system
    metricsets:
    • cpu # CPU usage
    • load # CPU load averages
    • memory # Memory usage
    • network # Network IO
    • process # Per process metrics
    • process_summary # Process summary
    • uptime # System Uptime
      #- core # Per CPU core usage
      #- diskio # Disk IO
      #- filesystem # File system usage for each mountpoint
      #- fsstat # File system summary metrics
      #- raid # Raid
      #- socket # Sockets and connection info (linux only)
      enabled: true
      period: 10s
      processes: ['.*']

after activating metricset and restarting the metricbeat services. A log appears like this

Feb 27 14:59:47 smtp150 filebeat[9086]: ERROR instance/metrics.go:77 Error while getting memory usage: error retrieving process stats: cannot find matching process for pid=9086
Feb 27 14:59:47 smtp150 filebeat[9086]: ERROR instance/metrics.go:112 Error retrieving CPU percentages: error retrieving process stats: cannot find matching process for pid=9086

10

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