On this page you can analyze Lambda invocations, looking for invocations that contain specific strings or that express certain properties. Lumigo provides a number of fields on which you can query.
You can search on any field that Lumigo collects (the fields are described below) by typing the field name, followed by a colon (“:”), followed by the term you are searching for.
These sample queries demonstrate the power and flexibility of our query language
all executions that took more than 1000 ms
duration: [1000 TO *]
all executions with errors in the region us-west-1:
error: * AND region: "us-west-1
all warm executions that took over 500ms (functions that did not have a cold start):
readiness: "warm" AND duration: >500
all HTTP requests that didn't return 200 or 202
entity_type: http AND NOT status_code: 200 AND NOT status_code: 202
Lumigo collects the following data fields for each invocation:
- event - the event that the Lambda function receives
- return_value - the data that the Lambda function returns
- transaction_id - the unique id for a specific transaction
- started - the start time of the invocation (in unix format)
- ended - the end time of the invocation (in unix format)
- arn - the Lambda function's ARN
- region - the execution AWS region (e.g, us-west-1)
- runtime - the Lambda execution runtime (e.g, python3.7)
- duration - the duration of the Lambda function's execution
There are additional fields we may collect, depending on which service and triggers you are using. Contact us with any questions about the additional fields we collect.
The following example lets us search for all of the invocations related to a specific Stripe charge ID:
You can also use simple query syntax to combine multiple conditions together. The fields are described below.
searching for a string
searching a specific attribute
range of values
[ TO ]
[210 TO 360]
multiple conditions (intersection)
John Doe AND duration: >1000
region: us-west-1 AND (duration: >500 OR error: Timeout)
Updated 2 months ago