Rollbar is better together and our latest account setting makes it easier to get everyone together. I'm happy to introduce Email Domain Whitelists. Read More
You can now rename/edit your error titles. Fix ugly long titles. Hover over, click, edit, and save.
Supercharge your issue and error tracking workflow when you connect your Rollbar and Bitbucket accounts. New Items in Rollbar will instantly create Issues in your Bitbucket repo, or you can create and link Issues with the click of a button within Rollbar. Read More
Yes, that's correct.
Daily, Hourly, New Errors, and Trend graphs are now clickable. You can find and fix bugs even faster, and in less clicks. :D
Common usability feedback we get from our users:
Sure would be nice if I could click the dashboard bar graphs and sparklines to quickly see what caused a spike in error events etc.
Couldn't agree more. We love aggregating data and we love it clickable. So we enabled it!
The following are now clickable in the project Dashboard:
Trends are also clickable on the Items page. For reference Trends are these guys also called 'sparklines'.
When viewing a specific error item, the Last 60 Minutes, Hours, and Days are now clickable and aggregate error data by your selection.
We're excited to get this features out the door. It reduces a lot of friction in navigating Rollbar. One of many UI and UX improvements to come. :)
Login today and go click through your data now.
Don't have a Rollbar account? No worries, you can give our Live Demo a try and 'click all the things'. ;)
Deploy and enjoy!
The infrastructure behind most modern web applications includes an assortment of tools for collecting server and application metrics, logging events, aggregating logs, and providing alerts. Most systems are made up of a collection of best-in-class tools and services, selected and deployed over time as team members arrive and depart, needs change, the system grows, and new tools are introduced. One of the challenges web development and operations teams face is collecting and analyzing data from these disparate sources and systems and then piecing together what’s happening by looking at multiple reports and dashboards.
Two common pieces in this puzzle are Logstash and Rollbar.
Logstash (and the Kibana web interface, both of which are heavily supported by and integrated with Elasticsearch) lets you collect and parse logs, store them in a central location, search and explore the data via the Kibana UI, and output events to other services. Logstash provides a powerful tool for taking logs in many different formats, converting them into JSON events, then routing and storing those events.
Rollbar collects errors from your application, notifies you of those errors, and analyzes them so you can more efficiently debug and fix them. With a few lines of code or config changes to your application, you can make errors, complete stack traces, trends and affected user reports accessible via your Roller dashboard. Like Logstash, Rollbar collects and analyzes events represented in JSON.
By connecting Logstash and Rollbar, you can not only centralize and analyze your system and application logs, but also improve error tracking and simplify debugging by providing context to developers looking at errors generated by their code.
For Rollbar users, Logstash allows you to collect errors from external applications and ship them to Rollbar, where they'll appear on the same dashboard as your application errors. Database and web server errors, for example, can be passed along to Rollbar to help developers determine whether the error is due to a bug, database performance issue, or operational issue with the web server.
To get started...
Quick tip: If you are running out of file descriptors in your Beanstalkd process, use /etc/default/beanstalkd to set the ulimit before the init script starts the process.
# file: /etc/default/beanstalkd BEANSTALKD_LISTEN_ADDR=127.0.0.1 BEANSTALKD_LISTEN_PORT=11300 START=yes BEANSTALKD_EXTRA="-b /var/lib/beanstalkd -f 1" # Should match your /etc/security/limits.conf settings ulimit -n 100000
Lot's of resources online tell you to update your /etc/security/limits.conf and /etc/pam.d/common-session* settings to increase your maximum number of available file descriptors. However, the default beanstalkd installation on Ubuntu 12.04+ uses an init script that starts the daemon process using start-stop-daemon which does not use your system settings when setting the processes ulimits. Just add this line to your defaults and you're good to go!
You can now setup notifications every time an error occurs. Previously specific error Notifications were only avaiable for New Items and 10^th Occurrences. Notification Rules are available for all Channels (Email, Slack, HipChat, Trello, PagerDuty).
Ever wanted to assign error items to other team members in Rollbar? Of course you have. Now you can. It is a pretty straight forward enhancement, but here is an overview.
On the error ‘items’ details page, there's an “Assigned to" dropdown with the members of your team. Once assigned, we’ll shoot an email to that team member letting them know you assigned that specific item to them, including link and details. They'll be automatically added as a 'watcher' for that specific item and will receive notifications about any comments and updates.
Assignment events will be listed in the item history section, so you can see who assigned it to whom, when.
To quickly find items assigned to yourself or others on your team, search 'assigned:me', ‘assigned:username’, or 'assigned:unassigned' on the Items page.
We're excited to get this out into the wild. Especially for some of the larger teams using Rollbar. Let us know what you think and how we can make it better for you and your team.
Node.js has a built-in debugger that you can start in running processes. To do this, send a
SIGUSR1 signal to the running process and connect a debugger. The one, big caveat here is that the debugger only listens on the local interface,
The following are instructions for debugging Node.js applications running in your company's private network from your laptop, through a bastion host.
prod-host $> kill -s SIGUSR1 <pid>
prod-host $> ssh -N -q -L <private-ip>:8585:localhost:5858 <private-ip>
laptop $> ssh -N -q -L 5858:<private-ip>:8585 <username>@<bastion-host>
127.0.0.1using port 5858, name it and save.
At this point your laptop will have connected to your local SSH tunnel which will be connected to your production host's private network interface which will be tunneled to your production host's local network interface and your Node.js process.
PyCharm → local SSH tunnel → bastion host → production host private network → production host localhost → Node.js
Set some breakpoints in PyCharm and watch as your production process begins waits for you to step through your app.
Note: If you'd rather use the command line instead of PyCharm just run the node debugger from your laptop:
laptop $> node debug localhost:5858
Sometimes PyCharm will just not connect to the running process on your production machine. Try restarting each of the SSH tunnels.