contention: fingerprints of contended transactions do not resolve on tenants #96353
Description
On tenant clusters, the fingerprint IDs of contended transactions are never resolved in the event store. This results in the {blocking, waiting}_txn_fingerprint_id columns of the crdb_internal.transaction_contention_events table always having the value \x0000000000000000.
To reproduce:
- Create a local multi-tenant (demo) cluster.
- Run the
insightsworkload against a tenant on the cluster. - Query the
crdb_internal.transaction_contention_eventstable on that tenant.
This bug was found on a 22.2.2 serverless cluster, and was reproduced on tenants of a 22.2.2 and 23.1-alpha1 demo cluster (cockroach demo --multitenant=true --nodes=3).
Jira issue: CRDB-24082