UTXO Ledger
This section outlines the metrics that enable you to monitor the UTXO Unspent Transaction Output. The unspent output of a cryptocurrency transaction, representing the amount of digital currency that has not been spent and is available for use in future transactions. ledger performance.
The UTXO ledger is built on Corda’s flow functionality with several specialized processors that execute various operations. Each of these processors is connected via the message bus to flows. Therefore, the most prominent performance improvements revolve around decreasing the number of times a flow suspends and reducing the time lost to the message bus.
| Metric | Type | Tags | Description |
|---|---|---|---|
corda_ledger_flow_verification_time_seconds | Timer | None | The time taken from calling transaction verification within a flow until a response is returned to the calling code. |
corda_ledger_verification_time_seconds | Timer | None | The time taken from receiving an event in the verification processor to completing the event’s processing. |
corda_ledger_verification_contract_total_time_seconds | Timer | None | The time taken to execute contracts when verifying a transaction. |
corda_ledger_verification_contract_time_seconds | Timer |
| The time taken to execute a contract’s contract code. |
corda_ledger_verification_contract_count | Counter | None | The number of executed contracts when verifying a transaction. |
corda_ledger_flow_persistence_time_seconds | Timer |
| The time taken from calling any ledger persistence operation within a flow until a response is returned to the calling code. |
corda_ledger_persistence_time_seconds | Timer |
| The time taken from receiving an event in the ledger persistence processor to completing the event’s processing. |
corda_serialization_amqp_serialization_time_seconds | Timer |
| The time taken to serialize an object. |
corda_serialization_amqp_deserialization_time_seconds | Timer |
| The time taken to deserialize an object. |
corda_ledger_backchain_resolution_chain_length | Distribution Summary | None | The number of transactions resolved within a transaction’s backchain. |
Tags:
ledger_contract_name: Contract name.operation_name: Operation name.ledger_type: Ledger type.serialized_class: The class being serialized.
Was this page helpful?
Thanks for your feedback!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.
We're sorry this page wasn't helpful. Let us know how we can make it better!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Create an issue
Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.