Skip to main content

Transactions

Transactions serve as crucial records of actions and events within M-Trust, offering a comprehensive view of all key activities. Each transaction is logged with a set of core properties, providing insight into what actions took place, which services were involved, and whether they were executed successfully.

Properties​

Each transaction consists of the following parameters:

Timestamp​

The timestamp property records the exact date and time when a transaction occurs, providing a precise chronological reference. This information is critical for analyzing transaction patterns over time, identifying peak usage periods, and tracing the sequence of events during troubleshooting.

Service​

The service parameter categorizes transactions by grouping various actions under specific functionalities within your App. This categorization enables you to monitor usage and performance within distinct service areas, facilitating targeted analysis and troubleshooting.

Action​

The action parameter specifies the exact event or task that triggered the transaction. Actions represent distinct activities logged under each service, offering detailed insight into specific tasks. Analyzing actions allows you to identify trends and pinpoint precise areas for improvement or investigation.

Status​

The status of a transaction indicates its outcome. Statuses play a vital role in assessing transaction success rates and identifying issues requiring attention. When a transaction is first created, it’s usually in the Pending state. Once the process completes, it moves to Confirmed, Canceled, or Error.

  • Confirmed: The transaction completed all steps as expected. Confirmed transactions are typically final and require no further action.
  • Canceled: The transaction was intentionally stopped or reversed before completion. This could happen due to user choices or automated system responses.
  • Error: The transaction encountered an error, preventing it from finishing successfully. Checking the Error status can help you identify issues in your App’s transaction flow.

These status indicators streamline the process of identifying operational patterns and isolating potential issues.

Payload​

The payload holds any additional data relevant to the transaction. Payloads are composed of key-value pairs that provide dynamic, context-specific details such as user inputs, processed data, or system variables. This flexible structure allows each transaction to carry rich contextual information, aiding in thorough analysis and interpretation.