Dead_letter_queue input plugin

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

For other versions, see theVersioned plugin docs.

Getting Help

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

Logstash input to read events from Logstash’s dead letter queue.

input {  dead_letter_queue {    path => "/var/logstash/data/dead_letter_queue"    start_timestamp => "2017-04-04T23:40:37"  }}

+For more information about processing events in the dead letter queue, see+Dead Letter Queues.

Dead_letter_queue Input Configuration Options

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

Setting Input type Required

commit_offsets

boolean

No

path

a valid filesystem path

Yes

pipeline_id

string

No

sincedb_path

string

No

start_timestamp

string

No

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

 

commit_offsets

  • Value type is boolean
  • Default value is true

Specifies whether this input should commit offsets as it processes the events.Typically you specify false when you want to iterate multiple times over theevents in the dead letter queue, but don’t want to save state. This is when youare exploring the events in the dead letter queue.

path

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

Path to the dead letter queue directory that was created by a Logstash instance.This is the path from which "dead" events are read and is typically configuredin the original Logstash instance with the setting path.dead_letter_queue.

pipeline_id

  • Value type is string
  • Default value is "main"

ID of the pipeline whose events you want to read from.

sincedb_path

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

Path of the sincedb database file (keeps track of the current position of dead letter queue) thatwill be written to disk. The default will write sincedb files to <path.data>/plugins/inputs/dead_letter_queue.

Note

This value must be a file path and not a directory path.

start_timestamp

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

Timestamp in ISO8601 format from when you want to start processing the events from.For example, 2017-04-04T23:40:37.

Common Options

The following configuration options are supported by all input plugins:

Setting Input type Required

add_field

hash

No

codec

codec

No

enable_metric

boolean

No

id

string

No

tags

array

No

type

string

No

Details

 

add_field

  • Value type is hash
  • Default value is {}

Add a field to an event

codec

  • Value type is codec
  • Default value is "plain"

The codec used for input data. Input codecs are a convenient method for decoding your data before it enters the input, without needing a separate filter in your Logstash pipeline.

enable_metric

  • Value type is boolean
  • Default value is true

Disable or enable metric logging for this specific plugin instanceby default we record all the metrics we can, but you can disable metrics collectionfor a specific plugin.

id

  • 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 usefulwhen you have two or more plugins of the same type, for example, if you have 2 dead_letter_queue inputs.Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.

input {  dead_letter_queue {    id => "my_plugin_id"  }}

tags

  • Value type is array
  • There is no default value for this setting.

Add any number of arbitrary tags to your event.

This can help with processing later.

type

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

Add a type field to all events handled by this input.

Types are used mainly for filter activation.

The type is stored as part of the event itself, so you canalso use the type to search for it in Kibana.

If you try to set a type on an event that already has one (forexample when you send an event from a shipper to an indexer) thena new input will not override the existing type. A type set atthe shipper stays with that event for its life evenwhen sent to another Logstash server.