Hi,
In my logstash configuration i got http as input, some filter, ES as output.
Logstash will return status code 200 even when ES won't get it eventually.
How can i know for sure that when i send a log, that log will arrive or did arrived to ES?
Hi,
In my logstash configuration i got http as input, some filter, ES as output.
Logstash will return status code 200 even when ES won't get it eventually.
How can i know for sure that when i send a log, that log will arrive or did arrived to ES?
Hi,
How can i know for sure that when i send a log, that log will arrive or did arrived to ES?
When logs arrive on ES, indices are created on ES or you can check it by using below command:
curl -X GET "<ES_Node_IP>:9200/_cat/indices?v"
Ok, but if my client send a log over http, how can the logstash retrive to him that the log was saved.
Is there a way to configure logstash to do so? return some status code that is not 200 for example.
Maybe the mapping is wrong for instance and the log won't be saved.
inputs, filters and outputs are separate, the only communication from output to filter to input is back-pressure which stops the ingestion of events when the queues are full. There is no way to change the response based on what happens further down the pipeline.
To increase the reliability of delivery you can use persistent queues and DLQs.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.