Serverless architectures enable developers to build resilient distributed applications in which messages are exchanged between different functions and creates a business transaction to achieve a certain business goal. Out-of-the-box solutions provide visibility through functions but it is hard to track a business transaction happening in a serverless architecture.
Thundra provides developers to track business flows via Unique Traces page. Traces are basically chain of several applications such as AWS Lambda or container application. A distributed trace can occur multiple times in a system. We can call these traces as a business flows that achieve a job. Listing all of the traces does not help you to understand and keep track of your KPIs. At this point, Thundra automatically detects and lists unique flows that your application performs under Unique Traces!
You can navigate to traces page by clicking Unique Traces icon button on left side bar.
On unique traces page, unique flows are listed in terms of:
Alias - Name of the unique trace is the combining resource name of trigger of the transaction and main lambda function's name. You can click on pencil button and give a name to your unique traces. Press enter to save the name.
Entry point - Lambda function which is firstly executed on the transaction
Trace count - Number of how many times this unique trace is visited.
Error count - Number of erroneous visits of unique trace.
Average duration - Average end to end duration of a unique trace.
Resources - Resources interacted in a unique trace. Hover on a resource to display its name.
You can search through unique traces by name using search bar on the top of list.