IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Tcp output plugin Webhdfs output plugin »

› ›

Udp output plugin

edit

Udp output plugin

edit

Plugin version: v3.0.6
Released on: 2018-04-06
Changelog

Getting Help

edit

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.

Description

edit

Send events over UDP

Keep in mind that UDP will lose messages.

Udp Output Configuration Options

edit

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

Setting	Input type	Required
`host`	string	Yes
`port`	number	Yes

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

`host`

edit

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

The address to send messages to

`port`

edit

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

The port to send messages on

Common Options

edit

The following configuration options are supported by all output plugins:

Setting	Input type	Required
`codec`	codec	No
`enable_metric`	boolean	No
`id`	string	No
`workers`	number	No

`codec`

edit

Value type is codec
Default value is "json"

The codec used for output data. Output codecs are a convenient method for encoding your data before it leaves the output, without needing a separate filter in your Logstash pipeline.

`enable_metric`

edit

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.

`id`

edit

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 udp outputs. Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.

output {
  udp {
    id => "my_plugin_id"
  }
}

`workers`

edit

Value type is string
Default value is 1

« Tcp output plugin Webhdfs output plugin »