Stdout output pluginedit

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

For other versions, see the Versioned plugin docs.

Getting Helpedit

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 running Logstash. This output can be quite convenient when debugging plugin configurations, by allowing instant access to the event data after it has passed through the inputs and filters.

For example, the following output configuration, in conjunction with the Logstash -e command-line flag, will allow you to see the results of your event pipeline for quick iteration.

    output {
      stdout {}

Useful codecs include:

rubydebug: outputs event data using the ruby "awesome_print" library This is the default codec for stdout.

    output {
      stdout { }

json: outputs event data in structured JSON format

    output {
      stdout { codec => json }

Stdout Output Configuration Optionsedit

There are no special configuration options for this plugin, but it does support the Common Options.

Common Optionsedit

The following configuration options are supported by all output plugins:

Setting Input type Required








  • 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 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"

Variable substitution in the id field only supports environment variables and does not support the use of values from the secret store.