We admit it. In the serverless realm, getting the observability you need can be really frustrating.
In his series on serverless observability, Yan Cui has stated the challenges, and the reasons behind them, incredibly well.
But there is hope.
There is a constant onslaught of new tools, new features, and loud voices demanding change. At this point, we’re truly at the cusp of serverless observability being not just passable, but great.
In this post, we are compiling resources that you can use to have top notch insight into your functions. We will update this as new information becomes available, so it can serve as an observability tools guide for you, the intrepid serverless developer.
Read on for the best tools and best practices.
CloudWatch is the native AWS logging tool. It’s primarily for logging, monitoring, and alerts.
Metrics: Cloudwatch comes with easy Lambda metrics; no setup.
Logs: Logs from your Lambda function, plus general status logs, are sent directly to Cloudwatch Logs.
X-ray is a distributed tracing system you can use for debugging across various AWS systems. It’s usage is not mutually exclusive with another tool, like IOpipe or CloudWatch, and most people use X-ray in conjunction with another monitoring tool.
Ever used the native CloudWatch interface? Not always touted as the most user-friendly UI. Dashbird sits on top of CloudWatch and provides a more navigable user experience, plus a few additional features.
Performance metrics: includes extras like Lambda cost analysis.
Architecture metrics: track account-level stats across your entire architecture (individual microservice views also available).
IOpipe works with AWS Lambda functions written in Node.js, Python, and Java. It provides tracing, profiling, monitoring, alerts, and real-time metrics.
Real-time metrics: Monitor invocations, duration, memory usage, and errors in one place.
Search functionality: You can add multiple “rules” to find invocations that match. The example below looks for long-running invocations over 100ms, but you can search for errors, cold starts, or even custom metric values (e.g., “userId” = 1234).
Thundra has not yet hit general availability, but you can sign up for beta access here.
Much like IOpipe, it promises to provide tracing, profiling, monitoring, alerts, and metrics.
Thunda will differ from IOpipe in a couple ways. They plan to focus on Java rather than Node.js or Python. They are also attempting to avoid latency by keeping data-sending separate from the Lambda function itself. Instead, they’ll first write their metrics to logs, and an out-of-band log processor will send those metrics to the Thundra backend.
Note that this is a standard, and not a tool. You’ll have to set up your own collector and interface, or you can use a paid tool such as LightStep.
Feel free to leave comments, and/or submit a PR against this post to leave us suggestions.
To get started, pop open your terminal & run
npm install serverless -g
Join 12,000+ other serverless devs & keep up to speed on the latest serverless trends