Sergey
My feedback
80 results found
-
3 votes
Thanks for voting on this request to add support for a command to list and check invoices via the Atlas CLI. Great news: the latest version of the Atlas CLI ships with a new Public Preview feature that makes all Atlas Admin API endpoints available, including invoices.
You can now run commands like `atlas api invoices listInvoices` to return invoices for your organization. We're written an overview for using the feature here, and you can read more about the invoices subcommand, as well as other new `api` subcommands in our documentation here.
Please note that the `atlas api` subcommand is a Public Preview feature; we'd love you to try it and to submit your feedback here. Thanks again for your suggestions and votes.
Sergey
supported this idea
·
-
3 votesSergey
supported this idea
·
-
14 votesSergey
supported this idea
·
-
7 votes
An error occurred while saving the comment Sergey
supported this idea
·
-
11 votesSergey
supported this idea
·
-
2 votesSergey
shared this idea
·
-
11 votesSergey
supported this idea
·
-
8 votes
-
9 votes
-
2 votes
-
5 votes
-
8 votes
-
6 votes
-
9 votes
-
22 votes
-
1 voteSergey
shared this idea
·
-
20 votes
An error occurred while saving the comment Sergey
commented
+1
We must run "service continuity test" for every application on scheduled basis. To do this we must shutdown nodes on demand to demonstrate that application can survive it.
-
28 votesSergey
supported this idea
·
-
86 votesSergey
supported this idea
·
An error occurred while saving the comment Sergey
commented
If you want to catch full scan on collection you could set up alert "Query Targeting: Scanned / Returned > 1".
OPS Manager does not provide any details where it was triggered.
it would be nice to get db/collection/query which caused this issue. Query still can be fast (for example, not many document in collection yet or hardware is idle/fast at the moment) and will not go to slow operation group. -
228 votes
Hi all – We are currently developing collection and database-level restores. We expect this feature to be released in CY2025, but will update here once it is launched.
Sergey
supported this idea
·
it's very important feature if you have a requirement to validate your snapshots and ability to restore your clusters.
Currently to restore snapshot for any reason, you have to build new cluster with exactly the same encryption settings as they were during snapshot time. So you have to
1. analyse snapshot first and extract some parameters
2. build new cluster with exactly the same parameters
3. restore snapshot to this new cluster.
it would be very nice to bundle all these step into 1 - restore snapshot into new cluster.