Can’t find any answer for your question? Log into Serverless Framework and ask us in the support widget.
No. Deployments via the Serverless Framework CLI are unlimited. Deployments via CI/CD are also unlimited; however, each deployment is limited to 30 mins.
Yes. Just hit the “cancel” button on the dashboard at any time and you’ll be cancelled immediately.
A Trace is a payload which includes the request/response details, detailed spans, errors and performance information for each AWS Lambda invocation. You can access and query Traces in Serverless Framework via the Trace Explorer.A Metric is a single numerical payload which captures the AWS Lambda Invocation duration, invocation, max memory, initialization duration, and custom metrics instrumented in your AWS Lambda handler. You can access metrics in Serverless Framework via the Global Metrics View, the Trace Explorer and within the Metrics views of your Serverless Framework Services.
Yes. Each AWS Lambda function can be controlled individually from the Serverless Framework AWS Integration settings page. Enabling instrumentation 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. Logs are not collected or stored in Serverless Framework; instead, Logs are retrieved from AWS CloudWatch from the Trace details. To access Logs, query Traces via the Trace Explorer. The Framework will auto-tag your workloads as best as it can, but you may want to add custom tags as well to each function or Trace via our SDK to improve querying. Click on a Trace to load Logs, errors and more.
Serverless Framework provides automatic Trace sampling to limit the number of ingested Traces. This helps you save costs.No further action is needed to enable sampling. Trace sampling is applied progressively in proportion to invocation load. At low volumes the sample rate will be 0%, meaning 100% of invocations will generate traces, while at high volumes (1M+ invocations) only 20% of successful invocations will be generate traces. If a trace contains any error or warning events, including any warnings generated by the SDK (e.g. invalid tag key on setTag()), then the Trace will not be sampled. This ensures that all errors and warnings will be available in the Trace Explorer. Metrics are not subject to Sampling. All metrics generated and collected by the Instrumentation will continue to work, even if the trace was successful. Our pricing allows for higher Metrics volumes due to this.
A Concurrent Build refers to the number of jobs (build, test, deploy) which our CI/CD features can run at the same time. The free tier includes 1 Concurrent Build and the team tier includes 2 Concurrent Builds. This is enough for the majority of use cases; however, if you have a high volume of CI/CD deployments, you can buy more Concurrent Builds for $25/month.
Automatic deployments with CI/CD are included on both the Free and Team tiers; however, the Free tier is limited to deployments from personal user accounts. Deployments from organization accounts are available on the Team tier.
Yes, we offer premium support packages for Serverless Framework and general serverless architecture help. A Subscription is required in order to purchase Support. Please check out the Support page for more details.
Yes, support plans can be cancelled but they are not refundable. Your plan will automatically cancel at the end of the billing cycle. For monthly subscriptions that will be the end of the month, for annual subscriptions that will be on the annual anniversary. Until the end of that billing period you will continue to have access to premium support.
For the "Team" tier, all payments are processed on the last day of each month. For the "Enterprise" plan, payments may be made in advance depending on your individual contract, as well as after each month if any overages apply. Please see your "Enterprise" subscription for more details.
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.
The fees are calculated based on usage for the last billing period. Member and CI/CD Concurrent Build usage is determined by the high water mark. The high water mark is reset at the end of each billing cycle. For example, if you have 10 members in the middle of the month, but you remove 5 of them by the end of the month, then you will be charged for 10 members as that is the high water mark. Since you have 5 members at the start of the next billing cycle you will only be charged for 5 Members at the end of the following billing cycle if you do not add members at any point in that billing cycle.Currently we do not support proration if you chose to cancel your account. Therefore you will be charged for the full billing cycle for Members and CI/CD Concurrent Builds. Please contact support for a partial refund.
Yes. In each billing cycle the number of users is determined by the high water mark for the number of users. For example, if you start the billing cycle with 4 users, then add 1, but remove them before the end of the billing cycle, you will be charged for 5 users.
Credit card payments are automatically charged at the end of the billing cycle. The credit card transaction will be retried periodically for 14 days during the grace period. If the credit card payments continue to fail, then the organization plan will be cancelled.Once an account is in a cancelled state the organization will only have access to the Free tier features. CI/CD concurrent builds will be downgraded, monitoring transactions may be throttled, and only the organization owner will be permitted to deploy with the dashboard.