Loading...

XML

Word

Printable

Details

Type: Sub-task
Resolution: Done
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: MTA Documentation
Labels:
None

Story Points:
2
Blocked:
False
Blocked Reason:
None
Ready:
False
RCA Description:

Hide
* *Why we missed the bug?*
** Pick to proper answer from drop-down field upper.
+_Additional comments:_+

* *What is required:*
** Pick to proper answer from drop-down field upper.
+_Additional comments:_+

Show
* *Why we missed the bug?* ** Pick to proper answer from drop-down field upper. +_Additional comments:_+ * *What is required:* ** Pick to proper answer from drop-down field upper. +_Additional comments:_+
[QE] How to address?:
---
[QE] Why QE missed?:
---

Sprint:
AMM Sprint 219, AMM Sprint 220, AMM Sprint 221, AMM Sprint 223, AMM Sprint 222, AMM Sprint 224, AMM Sprint 225, AMM Sprint 228, AMM Sprint 226, AMM Sprint 227

SFDC Cases Links:
SFDC Cases Counter:

Description

Please update the Table A.1. to include the new argument

--enableTransactionAnalysis

Description: This tech preview feature will generate a Transactions Report that displays the call stack that executes operations on relational database tables. It supports Spring Data JPA and the traditional preparedStatement() method for SQL statement execution. It does not support ORM frameworks such as Hibernate.

Also can the MTA CLI arguments table heading be visible in the index on the left hand side.

It would also be apropriate to add an example of the report in section 3.1

Place Transactions report between Application dependencies graph report and Source report.

Use the same description as provided above.

The example is attached.