With today’s Serverless Framework Enterprise release we are extending the capabilities of Serverless Error Insights to support invocation logs. Developers can now easily access invocation logs along with stack traces from new error type alerts and error metrics to help developers discover, troubleshoot and easily resolve errors.
Errors happen, and the sooner you know about them after they are introduced the better equipped you are to proactively mitigate their impact. Serverless Framework Enterprise will track all the unhandled exceptions in your application and notify you when a new error type is identified. In the Serverless Framework Enterprise dashboard you can see the “new error type identified” alert on the “activity & insights” list.
We wish the world was bug free but we can’t fix every single one of them. To manage the errors over time we need to view the trends. The errors metrics chart shows error count trends for a service over time. Click into a point on the chart to see error counts and error types by function. Click on an error type to see an occurrence of an error.
Serverless Framework Enterprise shows your code stack trace right in the dashboard. You can navigate from a new error alert or the error metrics chart to view the stack trace of your service when the error occurred. If you use tools like Webpack or Typescript which generate the package code, you can also upload a source map to properly generate the stack trace.
AWS Lambda automatically monitors and reports metrics on your lambda functions through AWS CloudWatch. AWS Lambda automatically tracks the requests, execution duration per request and a number of other metrics.
While CloudWatch captures a lot of critical information to help you identify and troubleshoot errors with your functions, it is also difficult to identify an individual invocation and log stream related to an error or unhandled exception.
To help navigate CloudWatch logs we’ve added the CloudWatch logs directly into the Serverless Framework Enterprise dashboard. When you receive a New Error Type alert, the CloudWatch logs for that error are made available with the alert and stack trace. Similarly, when you select an individual error from the errors chart, you will be presented with the stack trace and the AWS CloudWatch logs in the same dialog. You no longer need to fire up the AWS console to get the relevant CloudWatch logs.
If you’re already developing your service using the Serverless Framework then integrating these new features is easy peasy. First, register for a Serverless Framework Enterprise account, then just update your existing service to use the enterprise plugin.
Maciej Skierkowski is the Director of Product at Serverless, Inc.