11 results found
I support multiple orgs and projects falling under my enterprise. I'd like the ability to tag projects using a key value pair - similar to GCP, Azure, AWS. Tags will help us organise and understand what's running in our projects.
Basic functionality that operates on tags will be helpful like filtering projects and enhanced billing that can group costs based on a tag would be beneficial.
Right now, we need to add cost metadata to the project name, which is the only place where we can do so.32 votes
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.23 votes
I'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.
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.15 votes
Give the ability to tag/label a project8 votes
I'm excited to announce that we recently released tags on database deployments.
Tags on projects is coming soon! If you want to be one of the firsts to test out tags on projects, let me know!
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.8 votes
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
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.
adding tag field to API create call
adding query by tag to API delete or update calls.
Naming or tagging Ops Manager daily/weekly/monthly/yearly backup snapshots3 votes
Enable a specific set of tags to go in the logs.1 vote
attribute based access control on the roadmap? Authorization based on tag value1 vote
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?