Daniel
My feedback
18 results found
-
12 votesDaniel
supported this idea
·
-
12 votesDaniel
supported this idea
·
-
13 votesDaniel
supported this idea
·
-
17 votesDaniel
supported this idea
·
-
19 votesDaniel
supported this idea
·
-
20 votesDaniel
supported this idea
·
-
20 votesDaniel
supported this idea
·
-
22 votesDaniel
supported this idea
·
-
22 votesDaniel
supported this idea
·
-
26 votesDaniel
supported this idea
·
-
35 votes
Hi All,
We are developing a solution directly in Ops Manager that will support swapping their S3 snapshot storage without terminating the backup. Ops Manager will allow you to update the S3 snapshot store ID in the backup job document and the next scheduled snapshot will be a full snapshot in the new S3 snapshot store after the update. This is specifically for S3 stores only at this time.
We are targeting this feature to be included in a minor release of Ops Manager 8 by mid 2025 at this time.
I will update this feedback item once launched.
Daniel
supported this idea
·
-
49 votesDaniel
supported this idea
·
-
54 votesDaniel
supported this idea
·
-
2 votesDaniel
supported this idea
·
Daniel
shared this idea
·
-
2 votesDaniel
shared this idea
·
-
3 votes
An error occurred while saving the comment Daniel
supported this idea
·
-
18 votesDaniel
supported this idea
·
-
5 votes
It would be nice to be able to filter the content of the profiler in the Atlas GUI.
The profiler has proved to be very useful and maybe it could be even better.
Currently you can only filter by "Top namespace operations"; and it would be nice to also filter by:
readConcern: this is because the ones hitting a secondary node are usually not a concern to me. They tend to be ad hoc queries which do not always have a supporting index and that is ok.
Also, when Operation = command, it could actually be many things. It might be a simple FIND or an AGGREGATE or even an INSERT. So filtering by the type of Operation would be good.