When a cluster update happens and things change such as the certificates, why wouldn't this show in the activity feed? The only thing noted in a recent issue we had was "cluster update". If we could see the details of the update we could have resolved our problem quickly without opening a case.

there is no way to download cluster logs after one month, we have an issue of one process today and the cluster log shows the operations registered and the time spent, the same process ran a couple of months ago and it's impossible to know or check in the cluster logs the operations(insert,update...) if the process had an issue two or three months ago.

Cluster updates do not show the old version Atlas is updating from, or the new version Atlas is updating to. It'd be great to see both of these pieces of information in the activity feed.

Today when looking for items to appear in the activity feed, I have to repeatedly refresh the page which is slow/painful. In future it would be better to automatically stream/poll for changes behind the scenes and load them without requiring a page refresh.

I usually visit the Project Activity Feed to discover "who did what", but the feed is littered with events triggered via the System. I would love to be able to filter out those events and just see those initiated by a user. Bonus points for being able to filter by the user :-).

Hi Team,

can we consider supporting the transactions when we use $merge stage in mongodb aggregation pipeline?
https://docs.mongodb.com/manual/reference/operator/aggregation/merge/#restrictions

We have a requirement where we need to use the merge stage in pipeline and we would like to ensure automaticity in the transaction.

The aggregation pipeline we are building can merge multiple documents into the same collection and we would like to have either all or none by using transactions and the current merge operation cant support it.

thank you

It would be good to post-facto expose some indication (in the Activity Feed, or a logfile or alert) that an unplanned VM migration occurred at the cloud provider level. This would allow customers to identify and distinguish cloud provider hardware issues from cluster issues arising from other causes.

There are many new web developer come on MongoDB Atlas. There create there account and start working but don't know any thing about MongoDB. Something goes wrong on there setup and decided to recreate there account and follow all the instructions. But after deleting there account they see that they can't use there old email address.
Because of this situations that I faced. I don't want these to be faced by someone else so I recommend MongoDB Atlas to remove this security policy. Guys, Do you support me?