Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1380 results found
-
Add sendCollectionLatencyMetrics and sendDatabaseMetrics switches for Datadog Integration
Atlas API supports (https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Third-Party-Integrations/operation/createThirdPartyIntegration) two (relatively new) keys for Datadog integration:
*sendCollectionLatencyMetrics
*sendDatabaseMetricsWe need to have these switches in the terraform provider as well.
2 votes -
1 vote
-
mongodbatlas_federated_database_instance add GCP support
Is GCP support planned for terraform provider and GCP?
dataprocessregion {
cloudprovider = "GCP"
region = "IOWAUSA"
}Trying to use this in Terraform results in 500 Internal Server Error
│ Error: error creating MongoDB Atlas Federated Database Instace: https://cloud.mongodb.com/api/atlas/v2/groups/***/dataFederation POST: HTTP 500 Internal Server Error (Error code: "UNEXPECTED_ERROR") Detail: Unexpected error. Reason: Internal Server Error.
1 vote -
Atlas Profiler could add readConcern and greater granularity for Commands such as say, FIND or INSERT etc.
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…1 vote -
take autosnap shot before upgrade
When upgrading to a new major version automatically take a snapshot of the current cluster before completing the upgrade to alleviate one more step in the process.
1 vote -
Add connection pooling metrics for sharded clusters
We recently ran into an issue where we hit the internal mongoS -> mongoD connection pool limit when reading from secondary's requiring Atlas support to increase the value of ShardingTaskExecutorPoolMaxSize.
As a result it would be great to be able to monitor the internal mongoS -> mongoD connection pool usage so we can monitor it and set up alarms if it gets near the limit.
2 votes -
Support multiple U2F devices (e.g Yubikeys)
It makes me nervous to only have one entered here. I always add a backup key to each site that use a U2F device. That is generally recommended and I have learned that the hard way.
The means there would be an option to name each device instead of accepting the one I currently plugged in.
And btw, I am very happy about the recent MFA addition. SMS is gone!
1 vote -
MongoDB::Atlas::DatabaseUser is missing Description
Please add the possibility within MongoDB::Atlas::DatabaseUser to add a Description
1 vote -
Allow API key with project owner rights the update of project API keys
We would like to use the terraform provider
mongodbatlas_access_list_api_keyto maintain the access list of our existing API keys.
We don't have an API key with organization owner rights. We have only an API key with project owner rights.
When I do the changes via web ui project owner rights are enough. I don't understand why the terraform provider needs organization owner rights.
In my understanding it should be possible to execute the providermongodbatlas_access_list_api_keyalso with project owner rights.2 votes -
Improve "Query Targeting Alerts" alert by including the database name and collection name
The "Query Targeting Alerts" alert notification does not contain any reference to the database or collection that triggered it making it hard to figure out where it came from. A hostname reference would be very helpful.
https://www.mongodb.com/docs/atlas/reference/alert-conditions/#query-targeting-alerts
6 votes -
Improve "Host has index suggestions" alert by including the database name and collection name
The "Host has index suggestions" alert notification does not contain any reference to the database or collection that triggered it making it hard to figure out where it came from. A hostname reference would be very helpful.
4 votes -
Force query to appear in MongoDB Logs and bypass slowms and Profiling settings
As of now operations that are above the slowms threshold appear within the MongoDB Logs. This can be altered by changing the slowms value to a lower/higher value, or by changing the Profiling Levels.
If customers want to change the Profiling Settings to collect all operations, they would need to change the Profiling Level to 2. However, doing so can lead to Performance Degradation on the underlying Cluster/Instance as increasing to this level has an effect on database performance and disk use.
It would be helpful if there was a way so that when an operation is being executed, that…
1 vote -
Please allow self-service for cancelling Atlas Restore jobs in progress.
Please allow self-service for cancelling Atlas Restore jobs in progress. Going through Support results in delays and is not practical.
1 vote -
fix example at https://www.mongodb.com/docs/atlas/operator/current/atlascustomrole-custom-resource/#basic-example
in the example at spec:
- "name" indentation is wrong
- also action should be specified as in API example connPoolStats should be actually "CONNPOOLSTATS" (with underscores, seems they disappear here when I post)
- at inheritedRoles there is no "role" as child field, should be databasea correct manifest would be:
apiVersion: atlas.mongodb.com/v1
kind: AtlasCustomRole
metadata:
name: tester
namespace: tester
labels: {}
annotations:
mongodb.com/atlas-resource-policy: keep
spec:
projectRef:
name: tester
namespace: tester
role:
name: tester
actions:
- name: CONNPOOLSTATS
resources:
- cluster: true
database: tester-database
collection: tester-collection
inheritedRoles:
- name: operator-role-1
database: tester-database2 votes -
Atlas tags exposed as labels in GCP billling
When you link your Atlas Account to the GCP Billing, the total cost comes through as an aggregated amount; I wish to use the Label functionality to further drill-down the costs by the Tag names and values assigned to Atlas resources (such as clusters).
This is a followup as suggested by Mongo support representative in support case #01436008
4 votes -
Expose hourly cost data as a metric for monitoring cluster cost
The hourly cost of a cluster is already availble in the Atlas UI. Expose this same data as a metric for monitoring cluster cost. We understand it may not include the data transfer and some other costs but monitoring the spike or valleys in the monitor over time for a given cluster is helpful when autoscaling is turned on. Then we can also be able to set an alarm on the metric.
2 votes -
Allow entering the time values directly by editing the text instead of keyboard arrows
When you want to filter a custom date and time range, you need to use the arrow keys on the keyboard to scroll through the hours, and minutes. This is annoying and inefficient. Let me type it in please. Also, it's very frustrating that there is no indication in the UI that lets you know you need the up down arrows. I had to connect with a support person to find this out.
Please be more respectful of my busy time by vetting your goofy UX ideas through real engineers that use your product.
1 vote -
backups export to s3 bucket custom folder name
It would be very nice to have a possibility to change
exported_snapshotsfolder name to custom name. And also if it would be possible to set this via terraform.2 votes -
Add sendCollectionLatencyMetrics and sendDatabaseMetrics to third_party_integration
Could you introduce sendCollectionLatencyMetrics and sendDatabaseMetrics to the tf provider defined in API spec https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Third-Party-Integrations/operation/createThirdPartyIntegration
1 vote -
Enhancing Performance Advisor
Identify MongoDB Connection Users: Display which MongoDB connection users generated the queries listed in the index proposals. For instance, avoid creating indexes for queries originating from Atlas UI and MongoDB Compass.
Respect Custom Collation: Ensure that Performance Advisor respects custom collation settings. When creating an index from Performance Advisor, it should automatically include the custom collation options. Currently, these options are left empty, leading to potential negative impacts rather than improvements.
8 votes
- Don't see your idea?