logstash pulls the logs from aws kinesis, so it will read as per its own speed and there wont be sudden spike because data isnt pushed to logstash instead logstash pulls it.
in this case is PQ (persistent queue) really needed?
logstash pulls the logs from aws kinesis, so it will read as per its own speed and there wont be sudden spike because data isnt pushed to logstash instead logstash pulls it.
in this case is PQ (persistent queue) really needed?
does anyone know the answer?
I presume persistent queues may help preserve events that were pulled from Kinesis but weren't able to reach ElasticSearch. (cluster maintenance?)
But this is just speculation. I can't find information on if PQ is compatible with Kinesis input.
Confirmation would be really helpful. Or better yet, updated documentation.
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.