-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 8.1.1
-
Component/s: None
-
Replication
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
0
Today we capture transaction metrics but do not differentiate between a client-initiated abort and a server-initiated abort likely for transactionLifetimeSeconds expiry or cache overload.
We should make it easier for customers to understand who/what is initiating the abort of their transactions to make better transaction management choices in their applicaiton