Invocation detail page displays trace and log data of specific invocation along with other metrics. Metrics give an overview of how your Lambda function is performed during a specific invocation. Invocation details page consists of two sections: Invocation Profile and Monitoring Data Tabs.
Invocation profile section displays all related information and statistics about specific invocation.
Three fields are included in invocation profile:
Function name: Name of Lambda function, when invocation is occured and located in which traces. you can click and display Trace Map of function is located.
Invocation stats: Invocation statistics along with the exact time of the invocation, and the request ID to better identify the invocation.
Invocation Info: Displays badges where the first three indicate the runtime, region and stage profile information of the invocation. The last two indicate whether an error has occurred and what error, and whether or not the invocation resulted in a cold start or not.
Trace Chart - Illustrates the trace data collected with the invocation and displays the data in terms of traces and spans. These spans relate to every single interaction that the Lambda function had with external services such as DynamoDB and Redis, along with all the functions that have been called upon. Moreover, you can click on a span and get additional information request and response data, tags embedded into the span and span logs. Visit the Trace Chart tab section to get a more detailed insight into how your trace data is displayed.
Logs - Displays all the log data and console prints that your Lambda function creates according to the specific invocation you are analyzing. Logging is runtime specific, however, Thundra displays your logs irrespective of runtime in a uniform format so that you may see uniform logs across your several Lambda functions irrespective of the runtime used. Visit the Logs tab section to get a better understanding of how your Log and console data is presented to you.