Download our free e-book now: "Serverless Best Practices"!

Nothing came up.

Try with different keywords or contact using the chat bubble.

Back to article.

Frequently Asked Questions

How do I set up Dashbird?

Setting up Dashbird takes under 5 minutes and requires no code changes.

To start, sign up and follow the on-screen instructions to link your AWS account with Dashbird.

Is there any overhead?

Dashbird does not affect the performance of your lambda functions.

Dashbird gets all of the information from logs when they reach AWS CloudWatch, meaning that the service has no effect on the execution itself.

Read more about overhead and how Dashbird avoids it here.

Is there added cost to my AWS bill?

Dashbird relies on CloudWatch logs to gather data of your Lambda functions.

AWS prices Data-transfer out of CloudWatch equivalently to Data-transfer from EC2.
Check it out for yourself on AWS at CloudWatch pricing. The amount added to your bill is insignificant. Here’s an article explaining it in more detail.

What is the latency of Dashbird?

It usually takes under 30 seconds after the execution for invocations to be visible in Dashbird.

How do I change my password?

Navigate to the user profile page, where you can press to change your password.
To change your password: Menu -> Profile -> General settings -> Password -> Click here to change password. You’ll be taken to a change password page.

How do I invite my team members?

You can invite as many team members to Dashbird as you like. Menu -> Users -> Add +

Can I choose which lambda functions to monitor?

Yes, you can control our log importer by specifying filters.
Navigate to Menu -> Importer settings

Lambda filtering

Filters are glob patterns.

Use some-service- to include and !some-service-prod- to exclude lambda functions. You can also use the name includes or name excludes to filter functions.

By default, all lambda functions are imported to Dashbird. Check out our step by step guide to read about it in more detail!

How do I delete my account?

To delete your Dashbird account, first exclude all Lambda functions from being monitored at the Lambda filtering page. Wait until all log-group subscriptions to Dashbird Kinesis stream have been removed from under you AWS account. After that it’s safe to delete the CloudFormation stack under your AWS. Notify Dashbird support from the support bubble to swipe data from our system.

Can't find what you're looking for? We'd love to help. Send us a message through the chat bubble or email us.