What is Rollbar?
Who uses Rollbar?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Rollbar in their tech stack.
After splitting our monolith into a Rails API + a React Redux.js frontend app, it became a necessity to monitor frontend errors. Our frontend application is not your typical website, and features a lot of interesting SPA mechanics that need to be followed closely (many async flows, redux-saga , etc.) in addition to regular browser incompatibility issues. Rollbar kicks in so that we can monitor every bug that happens on our frontend, and aggregate this with almost 0 work. The number of occurrences and affected browsers on each occurence helps us understand the priority and severity of bugs even when our users don't tell us about them, so we can decide whether we need to fix this bug that was encountered by 1k users in less than a few days days VERSUS telling this SINGLE user to switch browsers because he's using a very outdated version that no one else uses. Now we also use Rollbar with Rails, Sidekiq and even AWS Lambda errors since the interface is quite convenient.
- Errors get queued, de-duped, grouped and prioritized
- View detailed stack traces with local variables
- Real time email alerts, daily summaries or integrate with your chat & issue tracker tools
- Drill down w/ graphs & data trends by occurrence, browser, OS, location, user, host
- Language support - Ruby, Python, JS, Node, PHP, .NET, Android, iOS, more
- Deployment tracking and unlimited deploys
- Resolve, mute, replay, fix errors in the Rollbar dashboard
- Affected user reports and history
- Unlimited users, teams, projects, apps and integrations
- Error item commenting for agile teams
- Engineer-level support
- Enterprise options, including on-premise deployment