Include database name in performance bar
What does this MR do?
As part of &5759 we're preparing the GitLab application to handle connections to multiple databases. As such we want to improve our observability to understand these multiple databases.
This MR just adds the database name to the performance bar details.
Unfortunately the default rails database config name is primary.
Eventually we will force this to be main and it will be distinct from
the new ci database. This does create a little bit of confusion now as
we also use the words primary/replica to distinguish between our
read/write and read-only database servers. This means you may see
"Replica" next to "Config name: primary" which could be confusing. I
hope that the usage of "Config name" should help to disambiguate. I also
added a feature flag for this to be less disruptive.
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
- [-] I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
- [-] I have added/updated documentation, or it's not needed. (Is documentation required?)
-
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) - [-] I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
-
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #333066 (closed)