Open slootjes opened 1 month ago
Sounds like a great improvement idea, thanks for opening this. Naive question: is the reader/writer status exposed via the RDS API?
In any case I'm taking note of the idea (no promise on an implementation date ^^)
The information is returned in the describe db clusters API endpoint which is already used as far as I know by this app, this is the relevant output for my cluster:
<DBClusterMembers>
<DBClusterMember>
<DBInstanceIdentifier>some-service-databaseinstance1-azznoqajd0km</DBInstanceIdentifier>
<DBClusterParameterGroupStatus>in-sync</DBClusterParameterGroupStatus>
<PromotionTier>1</PromotionTier>
<IsClusterWriter>true</IsClusterWriter>
</DBClusterMember>
<DBClusterMember>
<DBInstanceIdentifier>some-service-databaseinstance2-cqtwprbtdl09</DBInstanceIdentifier>
<DBClusterParameterGroupStatus>in-sync</DBClusterParameterGroupStatus>
<PromotionTier>1</PromotionTier>
<IsClusterWriter>false</IsClusterWriter>
</DBClusterMember>
</DBClusterMembers>
The "IsClusterWriter" returns the relevant information if it's read/write or read only.
The instance type is available in the Describe Db Instances API call:
<DBInstanceClass>db.serverless</DBInstanceClass>
Maybe returning it as a table would be prettier even when adding more information.
When using Port 7777 on an RDS cluster with multiple instances the output looks something like this:
but based on this names I don't know which of the 2 is a reader or a writer. When making changes I obviously need a writer and while just doing some queries I prefer using a reader instance. Currently I always need to login to AWS to see which one I need. It would be very nice to see the role of the instance in this selection, perhaps like this:
While writing this, maybe also add the instance size to it as well:
What do you think?