Need advice about which tool to choose?Ask the StackShare community!
Papertrail vs Sentry: What are the differences?
Papertrail: Hosted log management for servers, apps, and cloud services. Papertrail helps detect, resolve, and avoid infrastructure problems using log messages. Papertrail's practicality comes from our own experience as sysadmins, developers, and entrepreneurs; Sentry: Cut time to resolution for app errors from five hours to five minutes. Sentry is an open-source platform for workflow productivity, aggregating errors from across the stack in real time. 500K developers use Sentry to get the code-level context they need to resolve issues at every stage of the app lifecycle.
Papertrail and Sentry are primarily classified as "Log Management" and "Exception Monitoring" tools respectively.
Some of the features offered by Papertrail are:
- Intuitive Web-based log viewer
- Powerful command-line tools
- Long-term archive (S3)
On the other hand, Sentry provides the following key features:
- Real-Time Updates: For the first time, developers can fix code-level issues anywhere in the stack well before users even encounter an error.
- Complete Context: Spend more time where it matters, rather than investing in low-impact issues.
- Integrate Everywhere: Drop-in integration for every major platform, framework, and language -- JavaScript, Python, PHP, Ruby, Node, Java, .NET, mobile.
"Log search" is the top reason why over 85 developers like Papertrail, while over 215 developers mention "Consolidates similar errors and makes resolution easy" as the leading cause for choosing Sentry.
Sentry is an open source tool with 21.2K GitHub stars and 2.42K GitHub forks. Here's a link to Sentry's open source repository on GitHub.
According to the StackShare community, Sentry has a broader approval, being mentioned in 1323 company stacks & 421 developers stacks; compared to Papertrail, which is listed in 244 company stacks and 46 developer stacks.
I essentially inherited a Shopify theme that was originally created by an agency. After discovering a number of errors being thrown in the Dev Console just by scrolling through the website, I needed more visibility over any errors happening in the field. Having used both Sentry and TrackJS, I always got lost in the TrackJS interface, so I felt more comfortable introducing Sentry. The Sentry free tier is also very generous, although it turns out the theme threw over 15k errors in less than a week.
I highly recommend setting up error tracking from day one. Theoretically, you should never need to upgrade from the free tier if you're keeping on top of the errors...
Pros of Papertrail
- Log search86
- Integrates with Heroku43
- Easy log aggregation across multiple machines43
- Simple interface37
- Backup to S326
- Easy setup, independent of existing logging setup19
- Heroku add-on15
- Command line interface3
- Alerting1
Pros of Sentry
- Consolidates similar errors and makes resolution easy232
- Email Notifications120
- Open source106
- Slack integration84
- Github integration69
- Easy48
- User-friendly interface41
- The most important tool we use in production28
- Hipchat integration18
- Heroku Integration17
- Good documentation15
- Free tier11
- Self-hosted9
- Easy setup8
- Realiable7
- Provides context, and great stack trace6
- Love it baby4
- Feedback form on error pages4
- Filter by custom tags3
- Captures local variables at each frame in backtraces3
- Gitlab integration3
- Super user friendly3
- Easy Integration3
Sign up to add or upvote prosMake informed product decisions
Cons of Papertrail
- Expensive1
Cons of Sentry
- Confusing UI7