You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use http output plugin to push the events to our own java service and we wanted to retry at later time/push failed events to separate outputs in case of 404 or 401 or 403 from our java service. But, currently there is no way to capture the failed events.
I see that DLQ is already supported in elasticsearch output plugin. I suppose DLQ support in http output is also possible without major changes. I am more than happy to raise a PR for the same if we decide to include the support for DLQ
The text was updated successfully, but these errors were encountered:
Hi @RashmiRam the desire is to use DLQ in more output other than Elasticsearch output. So if you want to contribute with a PR to the output http would be awesome.
RashmiRam
added a commit
to RashmiRam/logstash-output-http
that referenced
this issue
Mar 23, 2020
1. Used the same logic as elasticsearch output plugin to find out if dlq is enabled or not
[execution_context? && execution_context.dlq_writer? && execution_context.dlq_writer is not a dummy writer?]
2. if dlq is enabled, send it to dlq_writer or log and drop the the events otherwise.
Fixeslogstash-plugins#109
Signed-off-by: RashmiRam <[email protected]>
We use http output plugin to push the events to our own java service and we wanted to retry at later time/push failed events to separate outputs in case of 404 or 401 or 403 from our java service. But, currently there is no way to capture the failed events.
I see that DLQ is already supported in elasticsearch output plugin. I suppose DLQ support in http output is also possible without major changes. I am more than happy to raise a PR for the same if we decide to include the support for DLQ
The text was updated successfully, but these errors were encountered: