This is a consolidated list of terms and concepts, with precise definitions, which are used within Serverless Console and the broader cloud industry. Whenever possible, Serverless Console adopts existing industry terms, rather than create new ones.
An organization is a single tenant in Serverless product suite (including Dashboard, and Serverless Cloud). An organization name needs to be unique and you need to add at least one AWS Integration to start using Serverless Console.
Integrations are how Serverless Console keeps track of third party tools you choose to instrument and monitor. You need at least one Integration to utilize Serverless Console features and you can use add multiple Integrations to a single organization.
Resources are an instance of a service on which you can enable monitoring. Currently this is limited to AWS Lambda Functions, but the set of supported resources is expected to grow over time.
A function is an instance of an AWS Lambda application. Functions can be written in a variety of languages and support a large number of runtime environments.
Active Resources is a Resources that have been active in the last 24 hour period. See our pricing page for more details about how we use Active Resources.
AWS Lambda is a Serverless, event-driven computing environment for running Serverless applications also known as functions.
Initialization refers to the period of function execution prior to the invocation of your handler. More details on the AWS Execution environment are available in our understanding Lambda duration guide.
A cold start is the name for a first-time initilization phase which takes longer than subsequent initilizations. See more details in our understanding Lambda duration guide.
The handler of an AWS Lambda function is where your business logic resides. Regardless of language or runtime all AWS Lambda functions have a Handler which corresponds to the Invocation phase of the execution.
Function errors are errors caught in an exception handlers you have included in your code. It can be helpful to include function handlers in your code for known failure points so you can find these failures in Trace Explorer.
A function failure occurs when an error occurs that is not handled as an exception. In these cases the function may fail to invoke. These appear on the metrics page and are sortable on the Trace Explorer.
Lambda runtimes provide a language and architecture specific environment for executing your code. Serverless Console works on all function regardless of functions but enabling tracing requires Node.14 or later.
CloudFormation is an AWS Service which allows you to create templates for creating AWS Infrastructure. Serverless Console creates the Serverless-Inc-Role-Stack in your account when you add the AWS Integration.
An Identity Access Management Role defines a set of permissions for interacting with your AWS Account. Serverless Console adds an the ServerlessMonitoringRole to create the following additional pieces of AWS Infrastructure.
A Kinesis Firehose is a streaming data pipeline used to send log data to Serverless Console.
A Cloudwatch Log Subscription Filter specifies a set of logs to be set to a destination, such as Kinesis Firehose.
EventBridge is an event bus for publishing events, and is used for transporting CloudTrail events from your AWS account to Serverless Console. These events are used to track new Lambda function deployments.
CloudTrail is a service used for getting a history of all AWS API calls in your AWS account.
Cloudwatch Metric Streams are used to collect aggregate metrics. Cloudwatch Metric streams allow you to collect metrics from any AWS Services. For a list of metrics we collect, see our metrics section.
A Lambda Layer is a packaged library for distributing Lambda Functions. The Serverless external extension and Serverless Node SDK are packaged as Lambda Layers and attached to your function when you enable additional monitoring features.
An AWS Lambda Extension is extra code which you can add to your AWS Lambda Function via an AWS Lambda Layer in order to track telemetry data about each Invocation. Serverless Console uses a sophisticated AWS Lambda Extension for collecting telemetry data in AWS Lambda Functions.
A Trace is collection of Logs, Metrics, and Spans associated with an a functions initialization, invocation and shutdown phases. A Trace allows you to understand the progression of these phases and further troubleshoot slowness or errors.
A namespace is a tag that can be applied to one or more of your functions to group functions that have related business outcomes - e.g. shopping-cart.
Environment allows you to group functions across specific environments like development, production, etc.
Spans are child interactions that occur within your Trace. This include the various phases of your execution as well as more detailed interactions that occur within your function.
This is a unique id used on your trace. It is used to associate logs and metrics for a Trace.
This is the architecture (x86_64 or ARM64) that executed the function.
This is the Max Memory in MB used by your function.
This is the version of the function that executed.
A log group is collection of logs organized for filtering and sorting in CloudWatch.
This is the log subscription filter we used to collect logs for this function.