Easier way to get your team on Rollbar

Posted by Mike Smith on May 19, 2015 · announcements, product, changelog

Joining and getting your team on Rollbar is now easier.

Rollbar is better together and our latest account setting makes it easier to get everyone together. I'm happy to introduce Email Domain Whitelists.

Previously the only way to join your team on Rollbar was being invited via email. Admins had to send email invites one by one. This can be tough for large organizations and fast growing engineering teams.

With Email Domain Whitelists, now you can set an email domain whitelist, so that anyone with an address at a specified domain can join your account (once confirmed). No more one off invitations. Making the workflow for admins and new team members easier and less confusing.



As we have grown we've seen more and more new users who are employees at companies that are already using Rollbar get lost trying to join their company’s account. The scenario looks something like this:

  1. You see a notification in your company's Slack, HipChat, or an issue in JIRA, GitHub etc.
  2. Click link to view more details
  3. Hit the Rollbar login page (confusion ensues)
  4. Decide to signup and create a new separate account that is orphaned from your company’s account
  5. Ask Admin to add/invite you to their Team on Rollbar
  6. The new account you created gets abandoned :( 



With the new email domain whitelist, anyone who signs up (from specified domains) automatically gets added to your account once they confirm their email address. Go to /settings/accounts/Name/ to setup (need to be on the Owners team to enable). 



Few items of note. Invites are on and email whitelists are off by default. Currently it only works on pages that would normally require login (i.e. link to project, error item, deploy). Here's how it works: 


  1. Next time someone clicks a link in Slack, HipChat, JIRA, GitHub they will prompted to login or join a team



      2.   Confirmation


Interested? Have your account admins enable the setting, send your team links to your projects and get everyone onboard. 

This is our first solution to solving this problem. We're evaluating how we can extend this to direct signups (that match a whitelist) and sharable links while maintaining the highest privacy and security standards.  

PS - It doesn't cost you more to add additional team members. So if you have 1 trillion members on your team, it's all good. :)


RQL String Functions

Posted by Brian Rue on December 16, 2014 · changelog

RQL now includes a basic library of string functions. You can use these to slice and group your data in arbitrary ways. For example, "email domains with the most events in the past hour":

SELECT substring(, locate('@',, count(*)
FROM item_occurrence
WHERE timestamp >= unix_timestamp() - 3600 AND IS NOT NULL

The new functions: concat, concat_ws, lower, upper, left, right, substring, locate, length, char_length. The functions are implemented to be compatible with MySQL; see the RQL docs for details.

RQL minor updates

Posted by Brian Rue on September 25, 2014 · changelog

A couple minor updates to RQL today:

  • IS NULL and IS NOT NULL are now supported
  • Fixed a crash in queries that contain a GROUP BY plus an ORDER BY on a column referenced only in the ORDER BY.


New "Reports" API calls

Posted by Brian Rue on August 20, 2014 · changelog

We've released two new API calls, exposing some of the data on the Dashboard via our JSON API.

Use the /reports/top_active_items to fetch the same data as "Top 10 Active Items in last 24 hours". And use /reports/occurrence_counts to fetch the same data as "Daily Error/Critical Occurrences" and "Hourly Error/Critical Occurrences".

More details in the docs. If you give this a try, send us any feedback at

Occurrence counts by minute

Posted by Brian Rue on July 31, 2014 · product, changelog

We've released an improvement to our Item Detail pages, adding a graph showing the aggregate occurrence counts per minute. It's live now for everyone and looks like this:

You can use this to see patterns that previously were hard to spot, like errors that occur on a regular, sub-hour interval (like the one shown above). It's also useful for quickly seeing how the occurrence rate changes after a deploy.

node_rollbar 0.3.11

Posted by Brian Rue on July 24, 2014 · javascript, changelog

We've released a new version of our Node.js library, version 0.3.11. It's available on npm and GitHub.

This release adds a new function to the public API, handleErrorWithPayloadData. The name's a mouthful, but it allows you to use (nearly) the full power of the Rollbar API when reporting errors. For example, to report an error as a "warning" and pass some additional data:

rollbar.handleErrorWithPayloadData(err, {level: "warning", custom: {someKey: "some value"}});

See more examples in the docs for caught exceptions.

More stack trace filename search filters

Posted by Brian Rue on July 22, 2014 · product, changelog

We've released several new search filters to make it easier to find errors by the filenames in their stack trace. If you've ever wanted to find JavaScript errors that only occurred within your own specific domain, or exceptions originating in a specific part of your code, keep reading.

You've always been able to search for errors where *any* filename contains a string, but now you can also search for errors where:

  • all filenames contain a string (allfiles:myproject)
  • no filenames contain a string (nofiles:evilproject)
  • the top stack frame's filename contains a string (
  • the bottom stack frame's filename contains a string (bottomfile:some_important_library
  • the number of filenames is within a range (minfiles:1 and/or maxfiles:10)
  • any filename contains a string (file:.rb)

These filters can all be combined in a single query. If you forget which filters exist, mouse over the ? next to the search box to see the help text.

rollbar-gem v0.13.2

Posted by Brian Rue on July 8, 2014 · changelog

We've released a patch version (0.13.2) of our Ruby gem, fixing two issues.

  • The use_sucker_punch config option could cause timeouts when using Unicorn (#121) - thanks to Fabio Napoleoni for the report
  • Sidekiq payloads were being mutated, causing the sidekiq-failures UI not to display parameters correctly (#122) - thanks to @Ditchou and Dmitry Krasnoukhov for investigating and reporting this.

It's available now on Rubygems and GitHub.

Prettier Node.js stack traces

Posted by Brian Rue on July 1, 2014 · changelog

Small tweak of the day: we now render Node.js stack traces to look more like they do via console.log(err.stack). We also fixed an issue where the context lines would appear indented at random levels.