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

« pagerduty rabbitmq »

› ›

pipe

edit

pipe

edit

Version: 3.0.2
Released on: July 14, 2016
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

Pipe output.

Pipe events to stdin of another program. You can use fields from the event as parts of the command. WARNING: This feature can cause logstash to fork off multiple children if you are not carefull with per-event commandline.

Synopsis

edit

This plugin supports the following configuration options:

Required configuration options:

pipe {
    command => ...
}

Available configuration options:

Setting	Input type	Required
`codec`	codec	No
`command`	string	Yes
`enable_metric`	boolean	No
`id`	string	No
`message_format`	string	No
`ttl`	number	No
`workers`	<<,>>	No

Details

edit

`codec`

edit

Value type is codec
Default value is "plain"

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.

`command`

edit

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

Command line to launch and pipe to

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

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

`message_format`

edit

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

The format to use when writing events to the pipe. This value supports any string and can include %{name} and other dynamic strings.

If this setting is omitted, the full json representation of the event will be written as a single line.

`ttl`

edit

Value type is number
Default value is 10

Close pipe that hasn’t been used for TTL seconds. -1 or 0 means never close.

`workers`

edit

Value type is string
Default value is 1

when we no longer support the :legacy type This is hacky, but it can only be herne

« pagerduty rabbitmq »