LogStash JDBC输入是否在外部来源上``last_run_metadata_path''？
我们希望在实例具有短暂生命的ECS环境中运行LogStash。他们可能长期以来生活，但不是永久的。因此，如果logstash存储sql_last_value在last_run_metadata_path中在删除实例然后再次提出的情况下无效。那个状态迷路了。
有没有办法从S3路径中拔出该值？还是通过数据库查询？我只是在寻找一个持久的地方，当实例被删除并再次提出时不会消失。
last_run_metadata_path => "/home/ckessel/.logstash_source_a" <-- need that to be S3 or some such
We want to run logstash in an ECS environment where the instances have transient lives. They might be long lived, but they aren't permanent. Thus, having logstash store the sql_last_value in the last_run_metadata_path doesn't work if the instance is removed and then brought up again. That state gets lost.
Is there a way to have that value pulled from a S3 path? Or via a DB query? I'm just looking somewhere persistent that won't vanish when the instance gets deleted and brought up again.
last_run_metadata_path => "/home/ckessel/.logstash_source_a" <-- need that to be S3 or some such
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
The file input just
The file input just reads the saved value from a file. So the location can be anything that the Ruby IO::read function can read. That does not include s3 or a database. It needs to be a filesystem, but it can be network mounted.