max database users not visible
We need more than 100 database users, and have had the limit raised for existing projects, but new projects require us to have the limit increased. There is no way for us to verify which projects have the default 100 database users and which ones have had the limit raised. It would also be nice to track the percentage or number of database users available as a metric.
Brian Jones
shared this idea
-
Michael Gerlach
commented
This is a problem in general with Atlas. There is simply no way to see the current effective limits and the available headroom.
We have been waiting for a Prometheus Integration per Org to scrape such metrics for quite a while now.
-
Hi Brian, Geoffrey, thank you for suggesting this. It's something that hasn't been high on our radar yet since it's rare that customers request >100 DB users: I can certainly understand the interest in this capability however as I know what it's like to need to go beyond soft limits with cloud services. I could see this becoming something accessible via the administrative API eventually.
Geoffrey, for what it's worth custom roles are only *applied* via particular database users which as you describe, can in turn be applied to particular clusters in the project: as a result this opens up a lot of flexibility. I am very sorry to hear you feel this has driven you to utilize multiple projects--we will be in touch with you to learn more
-
Geoffrey
commented
Have possibility the manage this limite by ourself.
Also as long as talked about safety. Target clusters for users can be identified. However, this cannot be done for "custom roles". This feature is important because currently, security by "custom role" is deployed on all clusters of a project. This forces us to create one project per cluster to be able to manage database access security.
