Can’t find any answer for your question?
Ask our customer support
We do not charge for monitoring idle infrastructure on your AWS account. An Active Resource Day is a unit indicating that 1 resource was used at least once on a given day. You are only charged for the days where the resource generated metrics.
A resource is any AWS service instance monitoring by Serverless Console. Currently only AWS Lambda is the only active resource measured by Console, but support for other services like API Gateway, and DynamoDB, are coming soon.
A resource is considered active if it generates metrics at least once per day. Whether your service generates 1 or 1,000,000 invocations in a day, it is still considered just 1 active resource.
No. Serverless Console will ingest all metrics for all supported AWS services, which currently only includes AWS Lambda. There is a small Active Resource Day fee for each of the resources, but it only applies if the resource is active. In most cases this accounts for a small portion of the total cost.
A Trace is a payload which includes the request/response details, logs, and detailed spans, for each AWS Lambda invocation. If tracing and/or logs are enabled on an AWS Lambda function, then each invocation will generate one trace. You can access traces in Serverless Console via Dev Mode, or using the advanced filtering/navigation in the Trace Explorer.
If tracing is enabled on an AWS Lambda function, then an extension will be added which generates and collects the request/response details, and detailed spans for each invocation. If logging is enabled for the AWS Lambda function, then the logs are also associated with the trace.
Serverless Console also includes free basic tracing which includes request/response information for each invocation, without request/response details, logs, or spans.
Yes. Each AWS Lambda function can be controlled individually from the Serverless Console AWS Integration settings page. Enabling tracking for a function will add a layer with an extension to add instrumentation for request/response details, and spans for HTTP requests and AWS service requests.
Yes, Logs are included in traces. If tracing is disabled for a function, but logging is enabled, then the logs will generate a trace and associate the logs with the trace.
Yes. The Serverless Console integration settings allows you to enable logging on individual AWS Lambda functions.
If you exceed the Free tier usage then ingestion of new metrics, traces, and logs will be disabled until the end of the month. At the beginning of the next billing cycle, the following month, your month to date usage will be reset and ingestion will automatically be reenabled for metrics, traces, and logs.
Yes. If you downgrade from the Team or Business tier to the Free tier, you will be charged the prorated cost for month-to-date usage.
Yes, premium support is available on a limited basis for large scale teams. Standard support is available to all customers. If you are interested in premium support, please contact sales for details.
All invoices are generated on the first day of each month.
Serverless Console has a usage-based pricing model, therefore you are charged for all services incurred at the end of the billing cycle. You can view your month-to-date usage and estimated invoice on the organization billing settings page.
All major credit card payments are supported.
On Serverless Console you can visit the organization billing settings page to view the month to date usage of Active Resource Days and Traces (with logs). You can use this to estimate your end of month bill by applying the Active Resource Days and Trace pricing.