Jira Link: DB-18646

Description

We currently expose a transaction_promotions metric to track transaction promotions. But this does not give visibility into whether a workload is using global transactions or not, since we also try to start transactions as global whenever we know it's needed, and such transactions do not involve a transaction promotion.

Additionally, we don't expose transaction locality anywhere explicitly except via vlogs, so combined with the above, it is difficult to verify that global transactions are or are not being used except indirectly via commit latency.

Adding metrics for e.g. number of transactions started as global would allow better testing.

Issue Type

kind/enhancement

Warning: Please confirm that this issue does not contain any sensitive information

• I confirm this issue does not contain any sensitive information.