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.
A simple output which prints to the STDOUT of the shell runningLogstash. This output can be quite convenient when debuggingplugin configurations, by allowing instant access to the eventdata after it has passed through the inputs and filters.
For example, the following output configuration, in conjunction with theLogstash -e command-line flag, will allow you to see the resultsof your event pipeline for quick iteration.
output { stdout {}}
Useful codecs include:
rubydebug: outputs event data using the ruby "awesome_print"libraryThis is the default codec for stdout.
output { stdout { }}
json: outputs event data in structured JSON format
output { stdout { codec => json }}
There are no special configuration options for this plugin,but it does support the Common Options.
The following configuration options are supported by all output plugins:
"rubydebug"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.
trueDisable 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 stdout outputs.Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.
output { stdout { id => "my_plugin_id" }}