Logstash by default relies on reading data from MongoDB's oplog (operations log), which captures all changes made to the database. If Logstash is not reflecting the changes made in MongoDB, it could be due to one of the following reasons:
The changes made to MongoDB were not written to the oplog yet, which means Logstash has not yet received the updates.
The Logstash pipeline might be misconfigured or not configured to use the correct database or collection.
The Logstash input plugin for MongoDB may need to be restarted to refresh the connection.
The Logstash output plugin may not have been configured correctly to write data to the correct location.
There might be a connection issue between Logstash and MongoDB, which could be caused by network issues or firewall rules blocking the connection.
To troubleshoot the issue, one can check the Logstash logs or MongoDB logs for any errors or warning messages. Additionally, one can also verify the configuration files and ensuring that the pipeline is set up correctly.
Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss
Asked: 2022-09-09 11:00:00 +0000
Seen: 17 times
Last updated: Oct 06 '22
What is the process of integrating API data into MongoDB using Spark/Python?
How can additional fields that have been transformed be queried in MongoDB?
What is the difference between indexing in Elasticsearch and MongoDB?
How can the Mongo Operator be used to deploy MongoDB in EKS/EFS?
How can data be extracted from Azure DocumentDB for exporting purposes?
How can I link or integrate mongodb with Google Data Studio?
How can I link to two distinct MongoDB databases in my Nuxt 3/ Vue 3 application?