Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1360 results found
-
CORS on the Atlas API
The Atlas API does not yet support CORS. Without CORS, calling the API from within a browser, using a React Client, for example, fails the 'preflight checks'.
"...has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource...."
If the Atlas API could add the 'Access-Control-Allow-Origin: *in the header response, then browsers would permit the API to be called.
Note: for the pre-flight check, the browsers call the OPTION method.
1 vote -
Parity of metrics between Atlas UI and Prometheus integration
It would be great if any metrics that are available in the Atlas UI are also available via the the Prometheus integration, especially since the metrics in the Atlas UI get coarse-grained after a while.
For example, in a recent incident it took us a while to do some preliminary investigations, and we wanted to confirm by looking at historical values for the metric "Operation Execution Time".
Unfortunately the chart in the Atlas UI was already too coarse-grained and the metric also does not seem to get exposed via the Prometheus integration.
10 votes -
Set Customer Managed Key (CMK) for wiredtiger encryption at the Organization level
For Organizations with a large number of projects, it is cumbersome to rotate keys for every project. If there was an option to set a default at the Organization level, and maybe override by CMKs set at project level, it will reduce the effort of key rotation for every project.
1 vote -
ATENDIMENTO PERSONA
TER MAIS RELAÇÕES DE DADOS INDIVIDUAIS SOBRE CADA CLIENTE, AGRUPAR EM DE MODO CURTO COMO UM ATALHO AS REGIÕES MAIS PROEMINENTES DE USO QUENTE OU FRIO DO EMPREENDIMENTO, OU SEJA, O DEDICADO COM OS CLUSTERS.
1 vote -
Hello, I had a superb consultative experience with Colin Phillips. He assisted me with understanding support options for a website database
Colin Phillips provided superb and outstanding help to me with the next steps for realizing my dream project.
With Gratitude, Amilcar1 vote -
Atlas access management similar to Azure AD Privileged Identity Management (PMI)
Hello, we are looking for functionality that allows users to auto-promote or adjust their privileges based on the access needed.
For example: if user XYZ needs access to DB:123 he can elevate access himself to this db.
This would be similar to Azure Active Directory (Azure AD) Privileged Identity Management (PIM). A service offered by Microsoft as part of its Azure cloud platform. It helps organizations manage, control, and monitor access within their Azure AD environment, particularly for privileged accounts. These accounts have elevated permissions that can perform critical tasks, such as managing resources, configuring settings, or accessing sensitive data.
…
6 votes -
Suppres/Stop Alerts caused by Mirrored Reads
Sometimes the "Mirrored Reads" queries cause alerts of "Query targeting " to appear in Profiler. Since these queries are related to mongod process, we want to stop this type of alerts
2 votes -
Support Auto-Resume in Trigger resource
can we have an autoresume argument in mongodbatlaseventtrigger (https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/eventtrigger)?
as in the screenshot, Auto-Resume suspended trigger can be switched on in Atlas UI.
2 votes -
Metric reporting private endpoint state
On Mongo Atlas platform we are able to see the status of both Atlas Private Endpoint and Azure Private Endpoint. It would be helpful to have these statuses available as a metric on the prometheus integration.
5 votes -
Hello, your login captcha is a real pain ********** !!!!!
Hello, your login captcha is a real pain ********** !!!!!
2 votes -
Alarm on potential data breach events
Provide capability to raise alarms on specific events like mongodump, mongoexport (eventually mongorestore, mongoimport)
6 votes -
Code support
Your website is a monster where is very difficult to get the useful information.
I wanted to use Realm to use a mongo cluster and after hours trying I give up.
I couldn't connect to the cluster after I created serveral ids (app, api, another api id, ...)Solution: Let's say I have a single cluster and a single realm app created.
Just give me the code with all the ids necessary.In my case I wanted to run it from the browser.
This is the code I tried to execute:
…const app = new Realm.App({ id: 'tradeapp-bozmd' }); const1 vote -
Atlas Role
The idea would be to have more advanced options when configuring access management to different projects/clusters.
A lot of companies would benefit greatly from seeing a segregation of roles and access to different features on a project.
It would be beneficial to have more read roles - focus on the metadata layer, but it would be also nice to have it on the DB level e;g. Onboarding a local entity - DBAs want to see only dedicated DB information - should be then between their responsibility.
The idea is to have differentiation between metadata and data, It can be particularly…
1 vote -
Atlas project capacity should be discoverable
Atlas project capacity should be discoverable. Based on documentation, it seems project capacity is dependent on various factors and can be arbitrarily increased via support request. We currently do not know how many clusters/nodes we have available to deploy in a given project and that is critical information to inform planning at scale.
7 votes -
Kubernetes AtlasDeployment snapshot persistence flag
When AtlasDeployment resources are deleted, the cluster is immediately terminated without the opportunity to enable snapshot persistence after deletion as there is in the Atlas UI. An option in the spec should be added to opt-into this behavior from a Kubernetes perspective.
1 vote -
Backup persistence after termination should be standard
It is odd that snapshots are tied to clusters and lost/destroyed when clusters are terminated. Snapshots have their own retention policies for a reason. Persistence after cluster termination should be the rule, not the exception.
6 votes -
Kubernetes AtlasProject backup compliance
Extending the AtlasProject Kubernetes resource to allow management of a backup compliance policy, including setting project-wide backup schedules and enabling backup persistence after termination by default, would be a major improvement over the current experience.
1 voteIt will be coming in a release in the next few weeks!
-
Kubernetes reconcilation interval
Kubernetes resources generally should be reconciled on a sensible schedule to prevent configuration drift between k8s and Atlas API.
AtlasProject is a critical one that can have widespread impact if API configuration drifts from Kubernetes and is not promptly corrected.
1 vote -
DataDog integration: add metrics for any current resource limits
We're using the DataDog integration to bring MongoDB metrics to DataDog. We want to re-create a DataDog monitor which is an equivalent to Altas alert "Connections of configured limit has gone above <>". However, we cannot do that relying solely on metrics, since the only connection related metric we found is "mongodb.atlas.connections.current".
It looks like the only way to solve this issue is to create a DataDog monitor based on the received event from Atlas.1 vote -
Retrieve latest/max oplog timestamp via the Atlas Administration API
At the moment the latest/max oplog timestamp can be retrieved via the Atlas UI in the backups section for point in time restores. This feedback post is to make this information available as part of the atlas administration api.
For example, in the UI it states:
You can only restore up to this oplog timestamp: 1692580549 and this increment: 1.
Would be good to have this value available to be retrieved via the API for restores requiring oplog timestamp values in this format.
7 votes
- Don't see your idea?