AdminAndrew Davidson
(VP, Cloud Products, MongoDB)
My feedback
184 results found
-
8 votes
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment A clarification: Atlas clusters can be paused for up to 30 days.
-
4 votes
An error occurred while saving the comment Hi Itay, I'm sorry to hear that this happened. Have you looked at using Billing Alerts (they can be configure at the Project and Org level): https://docs.atlas.mongodb.com/reference/alert-conditions/#billing-alerts
-
4 votes
An error occurred while saving the comment Hi Baris,
This is a great idea, similar to what we have done for IP whitelist entries. You might look at whether those could be used as a proxy for this over the near term, assuming you're whitelisting each peered VPC's private CIDR range separately. I'd love to get you a better solution eventually.
-Andrew
-
2 votes
An error occurred while saving the comment Great idea, Thomas. We actually support cluster-level key-value pair tagging today, but via API only. We need to eventually bring this concept to the Project-level, and make both visible/usable in the UI context as well. There are many use cases for this, ranging from what you've described, to being able to help with automation and billing management.
-Andrew
-
3 votes
An error occurred while saving the comment Hi Samith,
Great concept but it's not straight forward to be able to deduce the amount of a particular cluster's cost that each constituent database/namespace is responsible for. For example, is storage usage the key driver, or workload intensity, or some combination therefore?
For what it's worth, we do have a billing API as well as monitoring metrics API so you could use together to do some of what you're aiming to do but you'll need to come up with the logic yourself.
Have you looked into using the MongoDB Atlas M2 and M5 cluster tiers to offer low-priced starter tier clusters with multi-tenant economics? I can see that this might not be workable depending on your goal cost per tenant, but wanted to point it out as an option.
Cheers
-Andrew -
5 votes
An error occurred while saving the comment Hi Kyle, There are a number of serious downsides to using arbiters: for example it's not possible to use majority writes during maintenance if only one data-bearing node remains online temporarily.
Out of curiosity, if it were possible to deploy a third replica on GCP or Azure, would that suffice? I ask because we've had a long-term roadmap objective to enable true multi-cloud clusters on Atlas and we see situations like this, where you're looking increase in-country availability as a great use case for this.
Cheers
-Andrew -
1 vote
An error occurred while saving the comment Hi Daniel,
I'm sorry you're running into this, but it's a nuanced one: peering with public ranges means giving up internet access which could potentially alter the manageability of the Atlas-side cluster and this is not something we can consider.
If you're using public ranges in a private VPC, I strongly suggest that you either move to a private range and if that's not palatable, consider using either selective public IP Whitelisting or Atlas Private Endpoints (powered by AWS PrivateLink).
Cheers
-Andrew -
32 votes
An error occurred while saving the comment Hi Dan, We've hoped that folks would find the Atlas shared tier (M0 free tier, M2, and M5) offerings would address the lower-cost offering category. Have you explored these offerings: is there anything we can do to improve them to better service your needs?
-
12 votes
An error occurred while saving the comment It's important to emphasize that if ever folks are finding that an application needs to be restarted after MongoDB Atlas cluster-level maintenance, then there is a critical issue that needs to be addressed in the application, potentially in the driver that needs to be addressed.
If this happens to folks, please work with MongoDB support to get to the bottom of these issues which are completely antithetical to the continuous availability which MongoDB aims to deliver.
-
1 vote
An error occurred while saving the comment Hi Scott, I do want to make sure you've seen the API endpoint for this https://docs.atlas.mongodb.com/reference/api/organization-get-all-invoices/
-
2 votes
An error occurred while saving the comment Hi Scott,
Thanks for the suggestion and definitely a cool concept. I also want to eventually build a better billing explorer into the core experience. We are coming at this from a number of different directions and will definitely use this as food for thought.
Cheers
-Andrew -
3 votes
An error occurred while saving the comment Hi Itay,
Thank you for suggesting this: We will have some exciting news to share on this topic soon :)
-Andrew
-
1 vote
An error occurred while saving the comment Thank you for the suggestion, Martin! We definitely have an aspiration to eventually revamp our API toward a number of usability and maintenance improvements: it's one of those things that is difficult to prioritize over the near term since the existing API gets the job done in most cases. Still, hearing it from you helps keep this top of mind.
-Andrew
-
1 vote
An error occurred while saving the comment Hi Michael, Thanks for posting--I want to make sure that you've seen this: https://docs.atlas.mongodb.com/import/mongorestore/ This tutorial shows how you can actually pipe directly from mongodump to mongorestore without needing to save the file from the former before using it with the latter.
Cheers
-Andrew -
57 votes
An error occurred while saving the comment Hi Omar, Thanks for flagging this.
We completely agree and want to generally make alerts more prescriptive where possible. There are many classes of alerts so we're starting where we can make the biggest difference. For example for the alert you referenced, we'd like to move to a model in the future where we alert when we can see a way to improve e.g. when we have an index suggestion.
-Andrew
-
2 votes
An error occurred while saving the comment Hi Markiyan,
Thanks for bringing this up: we regret not having a path to deliver this one on the timeline we wish we could.
Unfortunately, as you may be aware, Heroku's billing model is somewhat incompatible with the liquid credits model that MongoDB Atlas uses. We've spoken to the Heroku team quite a few times about this over the last few years, and they do understand the challenge.
We do have a few ideas for how we might be able to approximate an Altas-ready model with the Heroku model, but there are a number of caveats. We're hopeful that Heroku's integrations model may become more flexible in future.
Out of curiosity, is it specifically the billing integration that's most important to you, or the ease of setting of the plugin integration to your application stack? I ask because it would be great if we could find a way for the latter to be possible without the billing piece being a blocker.
-Andrew
-
2 votes
An error occurred while saving the comment Hi Andy, Thank you for flagging the gzip issue: we are getting this fixed.
-AndrewAn error occurred while saving the comment Hi Manish,
To say the least, this is completely unacceptable. MongoDB Atlas page load times are higher than ideal in many parts of the world, but our analytics show that the vast majority of users do not wait on the order of *minutes*.
When we see reports about load times of this order of magnitude, we've usually been able to pin these down to ISP-specific issues. In fact you can run a test yourself to see if another connection (for example even via your mobile device) is able to load the page much faster: I bet it will. Usually these issues are transient.
We have a plan to deliver the MongoDB Cloud assets via a global CDN in the future and hope to improve this experience over time. I am very sorry that we're getting in your way here in the interim.
-Andrew
-
31 votes
An error occurred while saving the comment This is a great idea. There are many great capabilities that MongoDB Compass has that we just haven't been able to build into MongoDB Atlas yet, and we expect that pattern to continue since Compass iterates so quickly. I hope we will be able to bring this directly into MongoDB Atlas in the future.
Cheers
-Andrew -
1 vote
An error occurred while saving the comment As an update, we're getting this fixed
An error occurred while saving the comment Hi Márton,
Thanks for flagging this, I have routed your feedback to our EDU team that.
Cheers
-Andrew
Can you elaborate more on the use case and why this is important? What are you trying to do that requires this, or is it more of a hypothetical?