Flow Mapper
The flow mapper acts as a gateway component in the flow engine, to ensure that requests originating from outside the Corda cluster A complete set of worker processes. Clusters require a fully functioning virtual node infrastructure. are deduplicated correctly. Mapper metrics give an indication of the health and performance of this component.
| Metric | Type | Tags | Description |
|---|---|---|---|
corda_flow_mapper_event_processing_time_seconds | Timer |
| The time it took to process a single message in the flow mapper. |
corda_flow_mapper_deduplication_count | Counter |
| The number of events dropped due to deduplication of start events by the mapper. |
corda_flow_mapper_creation_count | Counter |
| The number of new states An immutable object representing a fact known by one or more participants at a specific point in time. You can use states to represent any type of data, and any kind of fact. being created. |
corda_flow_mapper_cleanup_count | Counter | None | The number of states being cleaned up. |
corda_flow_mapper_event_lag | Counter |
| The time between a mapper event being published and processed. |
corda_flow_mapper_expired_session_event_count | Counter | None | The number of expired session events dropped by the mapper. |
Tags:
flow_event: The type of event that was being processed for a given metric.
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.