Navigating CloudWatch Logs Effectively With Dashbird

To get some serious work done, we usually need to prepare for it. “Baby steps first,” they say. In our niche, these “baby steps” would be countless small jobs that need to be done before we can start with our main project. Proper preparation(try saying this 5 times fast) is the key to success, but after we’ve achieved our primary goal, there will always be something to do to keep it steady and flowing.

What does it take to keep your application working flawlessly? Well, among many other things, navigating CloudWatch logs is undoubtedly one of them, and today we’ll talk more about how to navigate CloudWatch logs effectively with Dashbird.

What Is CloudWatch?

CloudWatch is essentially the AWS monitoring service for AWS cloud resources for all applications that you run on your AWS cloud. Therefore, CloudWatch will provide you with alerts in case something goes down the rails. CloudWatch allows you to collect and track metrics so that you can get the system-wide visibility, resource usage, application performance along with the overall operational health. These insights will allow you to stay ahead of potential problems and to keep your application running smoothly.

With CloudWatch, you are able to collect as well as have access to all your operational data and performance in the form of logs and metrics from a single platform. This further means that you can overcome the challenge of monitoring individual apps and systems in a server, network, database, etc. CloudWatch enables you to track all of it together (applications, services, infrastructure) and to set alarms, logs, and events data to take actions automatically.


There are three main types of logs within the Amazon CloudWatch services:

1. Vended logs - are logs published by AWS services on the customer behalf. Amazon VPC Flow Logs and Amazon Route 53 logs are the two supported types. 2. Logs released by AWS services - there are over 30 AWS services that publish logs to CloudWatch like AWS CloudTrail, AWS Lambda, Amazon API Gateway, and many others. 3. Custom logs - which usually come from your application as well as from on-premise resources. You are able to utilize the AWS System Manager in order to install a CloudWatch Agent or even use the PutLogData API action for a secure log publishing.

Dashbird’s Role

Dashbird is a custom-made service that provides a syntactic analysis of the pre-formatted CloudWatch logs which are emitted from all Lambda functions after every invocation. Every piece of data coming from these logs is formatted into different Lambda invocation events and is further compiled into generic bird-eye view dashboard. Attaching a module or extra bits of code to your monitored function( which will furthermore cause execution delays) is not needed like it is within some alternative services.

What’s interesting with Dashibrd it’s the way it structures logs in a manner that makes them extremely easy to navigate. Other perks provided by Dashbird are live tailing logs from CloudWatch as well as full-text searches. Directly speaking, Dashbird collects important CloudWatch logs and sorts out actionable and meaningful metrics from the ones that aren’t which is very important for making your service an excellent one.

All that’s important is already captured in the dashboard view which is of help for developers since it provides them with the overall health and an excellent overview of their functions as well as function utilization.

Dashbird gives you a whole new way of compiling individual invocations in an easy-to-find view which is an experience for itself. In case you work with Lambda functions every day you know how annoying it can be to search through the entire log streams to discover that in most cases only a single line is what’s causing problems in your services.

An essential part of Dashbird services is that it also provides daily updates along with key points of interest brought all together from the invocation logs in the last 24 hours. All of this means that even if everything is going flawlessly, in case something happens, Dashbird’s alert system will let you know of it instantly via email or Slack.

Visual noise is something most of us are thinking of when it comes to CloudWatch logs, but Dashbird offers something different. Dashbird is easy to set up, to use, and above all - to understand it’s working principles. Custom made services like Dashbird will cut a big piece of execution logs leaving you with small parts in which you could much faster and efficiently search for the specific invocation within the particular function.

Let’s Wrap It Up

From what we’ve already said, we know that Dashbird’s ease-of-use and friendly UI will for sure make you every day log navigation much easier from what you’re probably used to by now. There are various benefits in using Dashbird’s services, and while billing is one of them since Dashbird will add almost nothing to your monthly AWS bill, you should check for the rest by yourself. Take a look at our Dashbird Survey Results and learn more about what Dashbird can offer. In case you’ve spent countless hours searching for someone or something to help you with wasting your time searching through the logs, try out Dashbird and see how it works for you. Inform us as well as our readers of your experience in the comment section below.

A collection of lessons learned at Dashbird after working with 4,000+ customers and 300,000+ Lambda functions

Write for us!

We're looking for developers to share their experience with serverless.

Emails and pull requests welcome!

Start using Dashbird for free!

Failure detection, analytics and visibility for serverless applications in under 5 minutes.

Request Demo