Dashbird is built so that developers can detect and understand failures quickly and easily. Sometimes it takes a bit of digging to understand what went wrong with a particular piece of code.
Here are the features/views for effective debugging in Dashbird:
Error view is often the point of failure discovery. It shows you the stack trace, occurence count, logs and a list of reoccurences. Usually developers are able to figure out what went wrong from this view.
To debug why a certain function is misbehaving, you can look at the perfomance, resource usage, cost and invocation history of that function, along with all the different errors that function has had. Basically you can put any function under a magnifier glass and work on it. It’s a good fit to work with a function view also when developing a function and iterating between deploys.
Use this to observe function activity in almost real time. Our UI also detect errors and failures on the fly so it’s super easy to observe the life of one function that’s particularly important.
Dashbird seamlessly integrates with X-Ray, giving you great insights of what your invocation actually does.
Our integration with X-Ray connects each invocation with an trace and gives you a breakdown of execution. Read about tracing from here.