Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1402 results found
-
peering
allow multiple Atlas CIDR (VPC Region) in the same project and allow attaching each cluster to the desired vpc.
today in order to have multiple vpcs in atlas (for example dev &prod)
they need to be separated projects, that create a lot of duplicated work and settings34 votes -
Adding indexes(Not search index) using terraform
I would like to create mongodb atlas index using terraform. But as of now we can able to create search index in mongodb atlas using terraform. here the expectation is to create normal index using terraform.
33 votes -
Add the ability to trigger alerts for testing purposes
It would be useful to have a "Test Alert" button for each configured alert in order to integrate and test alerts with third-party systems. Otherwise, it is difficult if not impossible to determine what the alert will look like until it is triggered.
33 votes -
Autoscaling - CPU/ Memory Utilization duration monitor - Minutes
Hi, Currently there is no option to initiate auto scaling during heavy workload/ requests comes and the cpu/ memory utilization is 75% for the even within
- 5 minutes
- 15 minutes
- 30 minutes
- 45 minutesThe system has to wait for 1 hour to autoscale to next tier.This one of the concerns for the heavy workload applications.
Idea:
Add a custom duration option as
- minutes also while monitoring the cpu / memory utilization
Example : When a CPU / Memory utilization is above 75% for the past 15 minutes , move the cluster to the next tier…
33 votes -
Propagation of NodeType via Prometheus metrics
Context: we rely on Prometheus metrics for various systems in the company. The setup of clusters until now was pretty standard, so basically we had replica sets and sharded clusters with electable nodes only – clusters with three nodes per RS or shard which numbers correspond to <clustername>-<shardnumber>-<(00|01|02)>>. Now we have a fourth analytics node in the clusters, which out of convention seems to get the next incremented number 03.
The thing is we cannot rely on convention and we need to have a way to distinguish the node types from Prometheus metrics (or at least from the Atlas API)…
32 votes -
Improvement: Add severity to alert definitions in Atlas MongoDB
The alert payload only contains status field with 'open' or 'closed' value. No severity definition option is available.
32 votes -
Add Terraform support for Realm Apps
Realm Apps (https://docs.mongodb.com/realm/get-started/create-realm-app/) can't be managed via Terraform. This would be a great addition to the provider!
31 votes -
make auto scaling alert message granular
When a cluster is changed due to auto scaling a message is sent to all project members. Project member cannot unsubscribe to this.
Request :
Provide the option, like all other alerts, to change the the alert settings for auto scaling30 votes -
New view with connection statistics
It would be valuable to have a per-cluster view showing an overview of connections into each cluster including:
- The number of connections per hours (opened, closed == churn)
- Which IPs connections are coming from and how many from each over time
- What drivers are being used for these connections and from which IPs
- Which user is opening the connections
This information can be very useful in understanding which applications/microservices are opening up the most connections, and helping to find old drivers etc.
28 votes -
Implement conditional DNS forwarders in Atlas to support internal LDAP servers
When a customer wants to use their private LDAP server in Atlas, they currently need to either expose their name via public DNS or use an internal CA and an IP address. For some customers these scenarios are suboptimal since they want to keep their infrastructure details private, even at DNS layer.
The proposed solution is to use the Conditional DNS forwarders in all cloud providers supported by Atlas, so the requests to resolve a private DNS zone (specified by the customer) will be forwarded to the listed DNS servers across the VPC peering connection while all other (public) DNS…
27 votes -
Allow cluster to define priority of availability zones
Similar to how it's possible to select the preferred region in a multi-region cluster, it would be beneficial being able to select the preferred availability zone in a single-region cluster. This would allow an application to live as close to the cluster's PRIMARY node as is possible.
27 votes -
Prometheus database and collection metrics
We checked the Prometheus metrics provided by MongoDB Atlas and didn't find metrics for the following:
Database sizeCollection storage size
Record per collection
Indexes per collection
Index size
We would like to have this kind of metrics to add to dashboards.
26 votes -
Allow cost allocation tags
on behalf of the customer,
would be great if we could allow tags on Org/ project level for cost allocation reasons (similar to how AWS allows this). When creating a project we can eg. add the type of environment, cost centre, bearer etc - without it showing up in the name. Does not necessarily need to show up on the invoice but we must be able to create a view which includes this info.26 votesI'm excited to announce that we recently released tags on database deployments. Start applying tags today and they will soon be available in billing invoices.
https://www.mongodb.com/docs/atlas/tags/
-
Log user Login to Activity Feed for Auditing
When a user logins into the Atlas Portal this is logged to the Activity Feed.
This feature would allow to better user auditing and identify potential security breaches.
26 votes -
Restrict specific users or client IPs to only Analytics node(s)
There are use-cases where certain users or client IPs need to be given access restricted to only the Analytics node(s) . While it is possible to grant such users read-only permissions at the database/collection level, and have them use the ANALYTICS replica set tag in their connection string URI, it might still be possible for those users to connect to a Primary or a Secondary node (when not using the Analytics replica set tag) and run their query there.
Therefore, a feature that will either restrict specific users access to only the Analytics node(s) or a functionality that will restrict…
25 votes -
Support for User Groups with Separate Authentication Configurations
Currently Atlas only uses a single (flat) user group which only allows for 1 type of authentication per Organization.
However if Federated Authentication is enabled, the authentication mechanism in Atlas is bypassed for the IdP based on the domain name of the user and the configuration of Atlas Authentication.
This causes a problem if there are multiple groups of users who all share a domain name, some of whom are registered in an IdP, and some of whom are not registered in an IdP (for example users in 2 divisions of the same company).
In this scenario, users who are…
25 votes -
Projects Organization
It would be great if we could organize the projects and not have them all at the same level of organization.
We could use this hierarchy to put rights, consult costs ...
A bit like the idea of Azure's management group or GCP's "Folder".25 votes -
New relic integration
We have an atlas account where all of are databases are, and we use new relic for monitoring and alerting.
It would be great if i could show in new relic dashboards of the status of our mongoDB, because all other dashboards are already there24 votes -
Include Human-Friendly Cluster Names in Alert Notifications
Please include the human-friendly cluster/host names in Monitoring Alert Notifications (e.g. email, PagerDuty, etc) in addition to, or instead of, the less clear internal cluster/hostnames (i.e. atlas-abcdef-shard-0).
24 votes -
Official ServiceNow Connector
Would love to see an official connector to ServiceNow for automatic ticket creation triggered by various database alerts.
23 votes
- Don't see your idea?