What is a transaction?

A transaction is defined as one coherent unit of work within your application.

Each transaction represents all activity from when a web request is received until the point that a response is sent.

When you integrate Lumigo with your Lambda functions, your functions will automatically report HTTP requests to our platform. Lumigo then traces your interconnected services, so that you can:

  • Trace the path of a request across your distributed system.
  • Understand the latency of components within the transaction.
  • Identify components creating a bottleneck along that path.

Monitoring transactions

The Transactions view presents a table of all the transactions detected across your system.
For every transaction you will see the following information:

  • Entry point
  • Components
  • Number of cold starts
  • Start time
  • HTTP response code
  • Duration
  • Number of issues
  • Cost


What can I do in the Transactions view?

The Transactions view allows you to understand the health and performance of your distributed environment from a variety of angles. You can, for example:

  • Identify your most expensive flow
  • Pinpoint transactions that have issues
  • Explore which entry points trigger lengthy executions

By clicking on a row, the Transaction Drilldown View of the selected transaction is opened. This screen presents a visualization of the transaction alongside fine-grained data, such as log information and performance metrics for each component.

To search and filter your transactions, use the query bar. You can choose a specific entry point and/or time on which to filter, so that you can view only the relevant transactions.



Transactions are uniquely identified by a 24-digit Transaction ID. If you want to go directly to a specific transaction, you can do so using our Transaction API:

β€œFor me, it is far better to grasp the Universe as it really is than to persist in delusion, however satisfying and reassuring.”
-Carl Sagan

Did this page help you?