Hi Barnabás,

Thanks for raising this. We need a bit more detail before we can evaluate the issue and route it to the right team.

Can you clarify where you are seeing this “oplogs.rs finder” issue?

1. What product or environment is this in?

   • Atlas, Ops Manager, Cloud Manager, a self-managed MongoDB deployment, or another tool?

   • If this is in Atlas, what page or workflow are you using?

   • If this is a shell/query workflow, are you querying local.oplog.rs directly?

2. What “extremely slow” means in practice

   • How long does the finder take to return results?

   • Is it consistently slow, or only for certain clusters, time ranges, namespaces, or workloads?

3. What “no results” means

   • What result did you expect to see?

   • Can you share an example query/filter, namespace, cluster, deployment type, or time window where this happens?

4. What impact this is having

   • Is this blocking investigation of a production issue, making debugging harder, or creating a supportability gap?

   • How often do you need to use this workflow?

5. What outcome you want

   • Faster search over local.oplog.rs data?

   • More reliable results?

   • Better filtering or discoverability?

   • A different diagnostic workflow entirely?

The current title gives us a useful signal, but we need to understand the surface area, expected behavior, and impact before we can size or route this appropriately.