#Transaction tracker
The transaction tracker is responsible for saving transaction metadata to the Operational snapshot after a successfully executed commit or checked-commit RPC. Transaction metadata contains information about performed transactions, such as the following:
transaction-id
- Identifier for transaction.type-of-commit-time
- Timestamp for eitherlast-commit-time
(if the transaction was successful) orfailed-commit-time
(if the transaction failed). If multiple devices are configured,last-commit-time
contains a timestamp for the last update on the last device.metadata
- Items in this field represent nodes configured in the transaction. Each item contains adiff
item with additional information.diff
- Items in this field are specific changes. Each item contains a path to changes, data before the change and data after the change. For failed transactions, this information is not included.topology
- Which topology the node is installed on. Eitheruniconfig
orunistore
.
Data-before
is visible only if data was updated or deleted. Data-after
is visible only if data was updated or created.
]
#Configuration
By default, UniConfig stores transaction metadata. Their removal depends only on the transactions.max-transaction-age
parameter.
#Show transaction-metadata
The response to this GET request contains all stored transaction metadata, transaction ids and other items such as node id, updated data before and after update, etc.
RPC Request
RPC Response, Status: 200