Start free trial

Central data platform for your serverless environment.

Get full access to all premium features for 14 days. No code changes and no credit card required.

Password: 8+ characters, at least one upper case letter, one lower case letter, and one numeric digit

By signing up, you agree to our Privacy policy and
Terms and Conditions.

Grouping AWS Lambda functions with Dashbird Project View

One of the serverless best practices is one-purpose functions. You should keep your Lambda functions small and solve exactly one use-case. This way, you can optimize them better and keep potential security problems contained. But creating many small functions can get overwhelming quickly. Even small projects can end up with more than 20 Lambda functions. 

If your serverless systems get bigger with time and solve more and more use-cases, you tend to have multiple sub-systems that use multiple Lambda functions. This makes it rather hard to stay on top of things in terms of monitoring. You want to know what your whole system does, but you also want insight into your sub-systems. You don’t want one sub-system monitoring data to get mixed up with other sub-systems monitoring data.

As a solution to this problem, Dashbird offers Project Views.

Project Views are a way to group your Lambda functions freely, to get a metrics dashboard just for this group. 

You are completely free to assign which Lambda functions will be tracked by one project view. This allows you to group by sub-systems, but it also allows you to group by purpose. You could, for example, create a project view for all your Lambda functions that integrate with third-party APIs to monitor the stability and performance of your external integrations on a cross-project.

Group Your Lambda Functions

If you look at the Dashbird app menu, you find Project Views in the Dashbird console’s sidebar. 

Dashbird Menu
Dashbird Menu

When navigating to the Project Views, you can create groups of Lambda functions called projects.

For demonstration purposes, I deployed two of the CDK example projects. Each of them has at least one Lambda function. Since these projects have nothing to do with each other, it’s a good idea to split them into two projects. You can see in the below example how to create a new project and how to add Lambda functions.

First project creation on Dashbird app
First project creation on Dashbird app

The project requires a unique title that must not include special or whitespace characters. I selected the five Lambda functions of the API Lambda CRUD example and added it to the list of Tracked Lambdas.

Next, I create a project for my second deployment, the Cognito Protected API. The next example shows how I chose to configure it.

Second project creation on Dashbird app
Second project creation on Dashbird app

After the creation, I have two projects in the Project Views list, as shown in the below example. These can be selected and even directly linked to. This way, the dashboard is filtered for each of these Lambda functions.

Project views list on Dashbird app
Project views list on Dashbird app

Summary

Dashbird’s Project Views is an easy way to split the mass of Lambda functions. Group them per project or group them in any other way that makes sense for your business.

This way, you can stay up-to-date on different parts of your applications without getting overwhelmed by looking at everything at once.

You can try it out yourself with Dashbird for free:

  • No code changes
  • No credit card required
  • Simple 2-minute set up
  • Get access to all premium features
  • Start working with your data and troubleshooting immediately

Further reading:

Log-based monitoring for AWS Lambda

Best practices for logging in AWS Lambda

Why AWS Console isn’t the best for serverless debugging?

Read our blog

AWS CloudWatch vs Dashbird

We have compiled this key feature comparison list between AWS Cloudwatch vs Dashbird to help you decide on the most efficient tool for your specific needs.

Optimizing AWS Lambda for Production

Here’s how I get my Lambda functions in line to behave their best in production environments.

Dashbird becomes SOC 2 compliant

We are pleased to announce that Dashbird has successfully completed its SOC 2 Type 2 audit to provide additional security assurance to our clients.

Made by developers for developers

Dashbird was born out of our own need for an enhanced serverless debugging and monitoring tool, and we take pride in being developers.

What our customers say

Thanks to Dashbird the time to discover the occurrence of an issue reduced from 2-4 hours to a matter of seconds or minutes. It also means that hundreds of dollars are saved every month.

Great onboarding: it takes just a couple of minutes to connect an AWS account to an organization in Dashbird. The UI is clean and gives a good overview of what is happening with the Lambdas and API Gateways in the account.

Dashbird provides an easier interface to monitor and debug problems with our Lambdas. Relevant logs are simple to find and view. Dashbird’s support has been good, and they take product suggestions with grace.

Great UI. Easy to navigate through CloudWatch logs. Simple setup.

Dashbird helped us refine the size of our Lambdas, resulting in significantly reduced costs. We have Dashbird alert us in seconds via email when any of our functions behaves abnormally. Their app immediately makes the cause and severity of errors obvious.