github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-23 22:27:21 -04:00
Code Issues Projects Releases Packages Wiki Activity

Small doc change to clarify which Elasticsearch response codes will cause DLQ to be used.

Browse source 
Fixes #8646
This commit is contained in:
Joshua Rich 2017-11-13 11:41:36 +11:00 • committed by Jordan Sissel
parent be68e31588
commit 0bc80e38a7
1 changed files with 7 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/static/dead-letter-queues.asciidoc vendored
View file

@ -2,10 +2,13 @@
=== Dead Letter Queues
NOTE: The dead letter queue feature is currently supported for the
<<plugins-outputs-elasticsearch>> output only. Support for additional outputs
will be available in future releases of the Logstash plugins. Before configuring
Logstash to use this feature, refer to the output plugin documentation to
verify that the plugin supports the dead letter queue feature.
<<plugins-outputs-elasticsearch>> output only. Additionally, The dead
letter queue is only used where the response code is either 400
or 404, both of which indicate an event that cannot be retried.
Support for additional outputs will be available in future releases of the
Logstash plugins. Before configuring Logstash to use this feature, refer to
the output plugin documentation to verify that the plugin supports the dead
letter queue feature.
By default, when Logstash encounters an event that it cannot process because the
data contains a mapping error or some other issue, the Logstash pipeline