Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
11 results found
-
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.24 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/
-
Atlas Endpoint Service "Description / Tag" Field
Currently when creating an Atlas Endpoint Service, there is no way to add a "tag" or "description" to the endpoint.
When a large number of endpoints are created, it because very challenging to identify which endpoint aligns with which customer service or application. Giving customers the ability to add "tag" or "description" metadata, would help give them better visibility into their configured endpoints.
This is specifically requested by an Enterprise Atlas Customer - please reach out to me for details / specifics.
16 votes -
Private Endpoint Tags / Custom Names
Private Endpoint names are not user friendly, they are just Amazon resource ID's. If you have multiple Private Endpoints for a project this makes it difficult to select the right one. It would be nice if these endpoints could be tagged or have custom names.
9 votes -
Tag-aware permissions to control access to analytics nodes
MongoDB has the great future of Workload Isolation based on node tags: we can add nodes tagged for analytics or reporting and then configure the same tag for this type of connections so that they do not interfere with the main operational workload.
But it is the responsibility of the BI/Data Scientist/Analyst to properly configure the connection: it cannot be enforced in a centralised way. It would be great if MongoDB permissions could be "tag aware", and allow access for a particular user only to some nodes of the cluster.
5 votes -
Allow tagging of mongo atlas alarms
It would be awesome to have possibility to tag alerts in atlas when creating using API or console. It will allow to process groups by alerts by tags without keeping track of ids.
requires:
adding tag field to API create call
adding query by tag to API delete or update calls.Pavel
4 votes -
Naming or tagging Ops Manager daily/weekly/monthly/yearly backup snapshots
Naming or tagging Ops Manager daily/weekly/monthly/yearly backup snapshots
3 votes -
More Granular Node Read Preference Tags
I would like the ability to set tags on individual nodes so that I can change the read preference with more granularity.
Mongo supports these tags on non-Atlas deployments: https://www.mongodb.com/docs/manual/core/read-preference-tags/#std-label-replica-set-read-preference-tag-sets
Analytic Nodes are very useful, and they are built as way of isolating workloads. The problem is that you can only really isolate into two different buckets (well three if you consider local read nodes). What I'd like to do is isolate more than two different sets of users and queries, so say user reporting and internal dev activities have their own sets, and they work independently.
You could kind…
1 vote -
Support tagging individual replicas in the cluster
Thank for the support for the tagging at the cluster level during database deployments( https://feedback.mongodb.com/forums/924145-atlas/suggestions/43032180-support-for-tagging-clusters-in-atlas)
However it would be useful to have support for tagging individual replicas in the cluster.
For example., we want to deploy the same app as two deployments tagged as tier-1 and tier-2, with tier-1 deployment service accessing tier-1 tagged readonly replicas and vice-versa.
1 vote -
enable a specific set of tags to go in the logs.
Enable a specific set of tags to go in the logs.
1 vote -
attribute based access control on the roadmap? Authorization based on tag value
attribute based access control on the roadmap? Authorization based on tag value
1 vote -
Tags for Functions, Values
A feature to quickly see which functions I already completed, tested, updated, whatever. Like a simple tagging system so that we could add tags to a function just for visibility to quickly see which functions need which work!
(In addition to this idea: https://feedback.mongodb.com/forums/945334-atlas-app-services/suggestions/40550581-folders-for-functions-values )
1 vote
- Don't see your idea?