It’s nice to see the new nested events being useful. The
observeChanges would never have been recorded in the past.
The agent only records the first reason it finds, and the checks for old versions of Meteor is broken with newer Meteor versions. With all of the checks working, it should have shown:
reason: "This query should support oplog. It's weird if it's not.",
solution: "Please contact Kadira support and let's discuss."
Reactive publications also require the
ordered option to be set for
findOne to use the Oplog: https://github.com/peerlibrary/meteor-reactive-mongo#reactive-queries-and-polling-vs-oplog
Since the agent only supports Meteor 1.4 and newer, I will remove the oplog checks for old versions of Meteor and look into adding one for using findOne with reactive publish.