Fix for open /compat/linux/proc: no such file or directory error on FreeBSD?edit

The system metricsets rely a Linux comparability layer to retrieve metrics on
FreeBSD. You need to mount the Linux procfs filesystem using the following
commands. You may want to add these filesystems to your /etc/fstab so they are
mounted automatically.

Using OS tools to perform bandwidth throttling gives you better control over policies. For example, you can use
OS tools to cap bandwidth during the day, but not at night. Or you can leave the bandwidth uncapped, but assign a low priority to the traffic.

Either there is a problem with the structure of your config file, or you have
used a path or expression that the YAML parser cannot resolve because the config
file contains characters that aren’t properly escaped.

You may have configured Logstash or Metricbeat incorrectly. To resolve the issue:

Make sure that Logstash is running and you can connect to it. First, try to ping the Logstash host to verify that you can reach it
from the host running Metricbeat. Then use either nc or telnet to make sure that the port is available. For example:

ping <hostname or IP>
telnet <hostname or IP> 5044

Verify that the config file for Metricbeat specifies the correct port where Logstash is running.

Make sure that the Elasticsearch output is commented out in the config file and the Logstash output is uncommented.

Logstash outputs remove @metadata fields automatically. Therefore, if Logstash instances are chained directly or via some message
queue (for example, Redis or Kafka), the @metadata field will not be available in the final Logstash instance.

To preserve @metadata fields, use the Logstash mutate filter with the rename setting to rename the fields to
non-internal fields.

Beats are lightweight data shippers that you install as agents on your servers to send specific types of operational
data to Elasticsearch. Beats have a small footprint and use fewer system resources than Logstash.

Logstash has a larger footprint, but provides a broad array of input, filter, and output plugins for collecting, enriching,
and transforming data from a variety of sources.

The host running Logstash might be unreachable or the certificate may not be valid. To resolve your issue:

Make sure that Logstash is running and you can connect to it. First, try to ping the Logstash host to verify that you can reach it
from the host running Metricbeat. Then use either nc or telnet to make sure that the port is available. For example:

ping <hostname or IP>
telnet <hostname or IP> 5044

Verify that the certificate is valid and that the hostname and IP match.

For testing purposes only, you can set verification_mode: none to disable hostname checking.

Use OpenSSL to test connectivity to the Logstash server and diagnose problems. See the OpenSSL documentation for more info.