Ruby is a popular open source programming language that is highly flexible, and used for everything from basic "hello world" apps to sophisticated, dynamic programs. Whether you've been programming in Ruby for years or you're a complete beginner, tracking down errors in your Ruby app is simple and easy. Let's go through some basic Ruby error handling, and discover how easy it can be to integrate Rollbar into your Ruby app to automatically log and report your exceptions.
Raise and Rescue Exceptions
Ruby's default exception handling is to terminate the program in the event of an exception. That's not really useful when you're trying to build a complex web application for multiple users. Luckily there's a way around this - declaring exception handlers. Exception handlers are blocks of code that are called if an exception occurs in the execution of another block of code in your program. For the most basic Ruby exception handling, you need to know how to Raise and Rescue an exception.
When you Raise an exception, you stop the normal flow of the program, and execute the code that deals with handling an error. This code can either deal with the error in some way, or terminate the program. If you provide a Rescue clause in your error handler, you can choose how to deal with the exception; without it, the program will simply terminate.
Join us this year at Amazon Web Services annual conference, re:Invent! Rollbar will be participating along side of Atlassian and other Atlassian ecosystem partners like StatusPage, Splunk, Puppet, Xmatters and Workato. We will all be in the Atlassian booth demonstrating how our solutions work better together. Come by and check it out - booth 2446.
Deep links to your source code in Bitbucket
Our friends at Losant wanted to share how they built an actual 'error-alarm' using the Rollbar and Losant API's. Enjoy!
When I envision a tech company's smart office, I see tons of dashboards and indicator lights that monitor everything. Efficient monitoring is a critical piece of today's technology stack, and there are always ways to improve. Rollbar already does an impeccable job at alerting you when errors are thrown in your application. But, to increase awareness, accountability, and awesomeness in the office, we can connect Rollbar to our smart office. In this tutorial, we are going to build an office error alarm powered by Rollbar and Losant.
Join us next week for CircleCI's November Office Hours!
Cory Virok, Co-founder and CTO of Rollbar, along with others from the startup community will be participating in a panel discussion on October's DDoS attack that took down a lot of the services we rely on in our everyday workflows.
When: Wednesday November 16th @ 6pm PT
Our friends at Split wanted to let you know that you can now integrate Rollbar with Split. And take control of your error handling and feature rollouts - together. Enjoy! :-)
Rollbar is an excellent error monitoring service that works across all of the languages Split supports. It’s great at telling you what’s going wrong and where, but doesn’t necessarily have all the details on why. That’s where Split comes in, with our new Rollbar integration.
We built Split to help teams take control of their deployments by slowly delivering features to targeted groups of users. In this way you can limit the scope of trouble when things do go wrong, killing the feature until it’s fixed, then slowly rolling it out again. Our new integration brings rollout metadata from features in Split into the Rollbar interface, so teams can quickly correlate errors against the latest deployments.
We had a significant outage this past Friday, October 21. Many customers were not able to reach rollbar.com or api.rollbar.com, some data was lost, and a few customers experienced cascading issues caused by our API outage. The root cause was a Distributed Denial of Service (DDoS) attack on our DNS provider.
We weren't the only service that had issues on Friday, but that is no excuse—we know that our customers rely on Rollbar as a critical monitoring service and it's all the more important that we are up when everything else is down. We'd like to share some of the details about what happened and what we're doing to prevent this kind of issue from happening again.
Dealing with errors can be time consuming and often an interruption in your everyday development workflow. It's important that we at Rollbar continue to work to improve this process and that we extend the capabilities and insights of your current toolset and workflows.
Atlassian users can now rejoice! 🎉 Debugging errors just got a whole lot easier and faster. With our latest improvements and integrations with Atlassian products you can now keep tabs on your application directly within the tools you're already using to build it. No more switching between multiple tools and services to debug and deploy code. Creating a seamless user experience and unified workflow around production errors.
Integrating Rollbar’s error monitoring with Atlassian’s products provides teams with:
- Instant error grouping and aggregation: Errors are grouped by root cause and linked to your source code within Bitbucket.
- Real-time notifications: Intelligent alerting rules configured for HipChat and JIRA.
- Easy workflow and prioritization: Discover the most impactful errors with data and create issues in JIRA instantly with rich data, contextual details and error analytics.
- Faster time to resolution: Debug, deploy fixes and track regressions much faster when your error data moves through HipChat, JIRA and Bitbucket automatically.
Watch our short video for an overview of how Rollbar and Atlassian's products work together: