Geoffrey
My feedback
162 results found
-
2 votesGeoffrey
supported this idea
·
-
10 votesGeoffrey
supported this idea
·
-
3 votesGeoffrey
supported this idea
·
-
18 votes
An error occurred while saving the comment Geoffrey
supported this idea
·
An error occurred while saving the comment Geoffrey
commented
You state that your platform supports AWS, GCP, and Azure cloud providers. However, certain features such as “Push Logs to AWS S3 bucket” are only available on AWS. There is no equivalent for other cloud providers.
When will you offer this feature on other cloud providers to provide your customers with a consistent experience?
Our organization is on Azure, and it would be extremely useful to be able to push these logs directly to Azure services (log analytics, storage accounts, etc.) in order to meet security requirements without having to create in-house processes that can alter the data in these logs and thus reduce their quality and usefulness.
You already have plenty of requests to forward logs to all kinds of platforms (Dynatrace, Securonix, Splunk, Datadog, etc.).
Collecting these logs via API calls is exhausting and pollutes the event log at the project level.
Let's go MongoDB. Roll up your sleeves.
-
2 votesGeoffrey
supported this idea
·
-
3 votesGeoffrey
supported this idea
·
-
17 votesGeoffrey
supported this idea
·
-
3 votesGeoffrey
supported this idea
·
-
3 votesGeoffrey
supported this idea
·
-
14 votesGeoffrey
supported this idea
·
-
20 votes
An error occurred while saving the comment Geoffrey
commented
We also use Dynatrace as APM and as monitoring tools for infrastructure. Integration with Dynatrace would be really beneficial for us. We tested Dynatrace's current integration capabilities with MongoDB Atlas, and it's not enough. Not enough detail.
We would also like to be able to collect mongodb logs and audit logs directly in Dynatrace.
Geoffrey
supported this idea
·
-
21 votesGeoffrey
supported this idea
·
-
25 votesGeoffrey
supported this idea
·
An error occurred while saving the comment Geoffrey
commented
It's will be helpful also for us to have a native connector with ServiceNow.
-
234 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.
An error occurred while saving the comment Geoffrey
commented
I vote for this feature again.
This feature is very useful in the context that we need to recover or revalidate the contents of a database at a specific time without having to recover the entire cluster.
Saves time and money.
Hoping that this time will be the right one.
An error occurred while saving the comment Geoffrey
commented
Hello,
The Atlas portal/API offers the ability to restore a complete database instance from snapshot or restore point. However the scope of this restoration covers the entire instance.
It would be a great asset to be able to restore a simple database from snapshots (encrypted or not). Currently, restoring a database (not a cluster) is a heavy workload that requires outputting data to a local workstation.
Thanks.
Geoffrey
supported this idea
·
-
7 votesGeoffrey
supported this idea
·
An error occurred while saving the comment Geoffrey
commented
Hello MongoDB,
I totally agree with Ershad's request about the ability to select the source of the backup you want to restore.
This functionality is necessary to meet the requirements of the regulatory authorities governing our field.
I've already opened a support ticket on this subject (Case #01328025).
I hope to have this feature available very soon.
Best regards.
-
12 votes
An error occurred while saving the comment Geoffrey
commented
Samething for us. Actually we have 14 linked organisation and more than 42 projects to support more than 81 clusters.
We managed that with API Key and Terraform.
As a member of a infrastructre team, it can be very usefull to be able to have a master API key to manage that.
Geoffrey
supported this idea
·
-
14 votes
An error occurred while saving the comment Geoffrey
commented
Hello MongoDB,
We made this request a long time ago. This problem is still relevant to us.
Currently, the only way to manage this is to create separate projects for each cluster. Obviously, we don't like this solution. It is already possible to limit users to a cluster, why not extend this ability to the custom role as well.
Thank you for considering our request.
We currently manage more than 71 MongoDB clusters in around 40 separate projects. Our projects allow us to segment by environment and business sector.
Thus, a business sector can use several MongoDB clusters. Each MongoDB cluster is dedicated to a separate application, which is why we would need to limit the security of "Custom Roles" to very specific clusters.
Thanks.
Geoffrey
shared this idea
·
-
41 votesGeoffrey
supported this idea
·
-
55 votes
Thank you all for your feedback!
We hear you loud and clear and are working on exposing these details in the next quarter.
Geoffrey
supported this idea
·
-
20 votesGeoffrey
supported this idea
·
Yes. Another one on Azure.
Let's Go MongoDB. You state that your platform supports AWS, GCP, and Azure cloud providers.
It's time for implementing that on Azure.