For other versions, see theVersioned plugin docs.
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.
Pipe output.
Pipe events to stdin of another program. You can use fields from theevent 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.
This plugin supports the following configuration options plus the Common Options described later.
Also see Common Options for a list of options supported by alloutput plugins.
Command line to launch and pipe to
The format to use when writing events to the pipe. This valuesupports any string and can include %{name}
and other dynamicstrings.
If this setting is omitted, the full json representation of theevent will be written as a single line.
10
Close pipe that hasn’t been used for TTL seconds. -1 or 0 means never close.
The following configuration options are supported by all output plugins:
"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.
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 collectionfor a specific plugin.
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 usefulwhen you have two or more plugins of the same type. For example, if you have 2 pipe outputs.Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.
output { pipe { id => "my_plugin_id" }}