Beats input plugin v6.0.10

• Plugin version: v6.0.10
• Released on: 2020-05-12
• Changelog

For other versions, see the overview list.

To learn more about Logstash, see the Logstash Reference.

For questions about the plugin, open a topic in the Discuss forums. For bugs or feature requests, open an issue in Github. For the list of Elastic supported plugins, please consult the Elastic Support Matrix.

This input plugin enables Logstash to receive events from the Elastic Beats framework.

The following example shows how to configure Logstash to listen on port 5044 for incoming Beats connections and to index into Elasticsearch.

input {
  beats {
    port => 5044
  }
}

output {
  elasticsearch {
    hosts => ["http://localhost:9200"]
    index => "%{[@metadata][beat]}-%{[@metadata][version]}" 1
  }
}

1. %{[@metadata][beat]} sets the first part of the index name to the value of the beat metadata field and %{[@metadata][version]} sets the second part to the Beat’s version. For example: metricbeat-7.4.0.

Events indexed into Elasticsearch with the Logstash configuration shown here will be similar to events directly indexed by Beats into Elasticsearch.

To minimize the impact of future schema changes on your existing indices and mappings in Elasticsearch, configure the Elasticsearch output to write to versioned indices. The pattern that you specify for the index setting controls the index name:

index => "%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}"

%{[@metadata][beat]}

Sets the first part of the index name to the value of the beat metadata field, for example, filebeat.

%{[@metadata][version]}

Sets the second part of the name to the Beat version, for example, {{logstash_version}}.

%{+YYYY.MM.dd}

Sets the third part of the name to a date based on the Logstash @timestamp field.

This configuration results in daily index names like filebeat-{{logstash_version}}-2025-01-30.

This plugin supports the following configuration options plus the Common options described later.

Also see Common options for a list of options supported by all input plugins.

• Value type is boolean
• Default value is false

Flag to determine whether to add host field to event using the value supplied by the beat in the hostname field.

• Value type is array
• Default value is java.lang.String[TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256]@459cfcca

The list of ciphers suite to use, listed by priorities.

• Value type is number
• Default value is 60

Close Idle clients after X seconds of inactivity.

• Value type is string
• Default value is "0.0.0.0"

The IP address to listen on.

• Value type is boolean
• Default value is true

• This is a required setting.
• Value type is number
• There is no default value for this setting.

The port to listen on.

• Value type is boolean
• Default value is false

Events are by default sent in plain text. You can enable encryption by setting ssl to true and configuring the ssl_certificate and ssl_key options.

• Value type is path
• There is no default value for this setting.

SSL certificate to use.

• Value type is array
• Default value is []

Validate client certificates against these authorities. You can define multiple files or paths. All the certificates will be read and added to the trust store. You need to configure the ssl_verify_mode to peer or force_peer to enable the verification.

• Value type is number
• Default value is 10000

Time in milliseconds for an incomplete ssl handshake to timeout

• Value type is path
• There is no default value for this setting.

SSL key to use. NOTE: This key need to be in the PKCS8 format, you can convert it with OpenSSL for more information.

• Value type is password
• There is no default value for this setting.

SSL key passphrase to use.

• Value can be any of: none, peer, force_peer
• Default value is "none"

By default the server doesn’t do any client verification.

peer will make the server ask the client to provide a certificate. If the client provides a certificate, it will be validated.

force_peer will make the server ask the client to provide a certificate. If the client doesn’t provide a certificate, the connection will be closed.

This option needs to be used with ssl_certificate_authorities and a defined list of CAs.

• Value type is boolean
• Default value is false

Enables storing client certificate information in event’s metadata.

This option is only valid when ssl_verify_mode is set to peer or force_peer.

• Value type is number
• Default value is 1.2

The maximum TLS version allowed for the encrypted connections. The value must be the one of the following: 1.0 for TLS 1.0, 1.1 for TLS 1.1, 1.2 for TLS 1.2

• Value type is number
• Default value is 1

The minimum TLS version allowed for the encrypted connections. The value must be one of the following: 1.0 for TLS 1.0, 1.1 for TLS 1.1, 1.2 for TLS 1.2

These configuration options are supported by all input plugins:

• Value type is hash
• Default value is {}

Add a field to an event

• Value type is codec
• Default value is "plain"

The codec used for input data. Input codecs are a convenient method for decoding your data before it enters the input, without needing a separate filter in your Logstash pipeline.

• Value type is boolean
• Default value is true

Disable or enable metric logging for this specific plugin instance by default we record all the metrics we can, but you can disable metrics collection for a specific plugin.

• Value type is string
• There is no default value for this setting.

Add a unique ID to the plugin configuration. If no ID is specified, Logstash will generate one. It is strongly recommended to set this ID in your configuration. This is particularly useful when you have two or more plugins of the same type, for example, if you have 2 beats inputs. Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.

input {
  beats {
    id => "my_plugin_id"
  }
}

• Value type is array
• There is no default value for this setting.

Add any number of arbitrary tags to your event.

This can help with processing later.

• Value type is string
• There is no default value for this setting.

Add a type field to all events handled by this input.

Types are used mainly for filter activation.

The type is stored as part of the event itself, so you can also use the type to search for it in Kibana.

If you try to set a type on an event that already has one (for example when you send an event from a shipper to an indexer) then a new input will not override the existing type. A type set at the shipper stays with that event for its life even when sent to another Logstash server.