Need advice about which tool to choose?Ask the StackShare community!
Logentries vs Sentry: What are the differences?
Logentries: Real-time log management and analytics built for the cloud. Logentries makes machine-generated log data easily accessible to IT operations, development, and business analysis teams of all sizes. With the broadest platform support and an open API, Logentries brings the value of log-level data to any system, to any team member, and to a community of more than 25,000 worldwide users; 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.
Logentries belongs to "Log Management" category of the tech stack, while Sentry can be primarily classified under "Exception Monitoring".
Some of the features offered by Logentries are:
- Logs as Metrics - Extract field level values, analyze them using powerful search functions, and visualize them with detailed dashboards.
- Dynamic Log Correlation - Dynamically group and correlate your logs in a single dashboard, or aggregate logs from a particular system to give an end-to-end view.
- Live Tail - View your streaming logs in real-time and highlight important events to easily see errors or exceptions in your live data.
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 31 developers like Logentries, 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 Logentries, which is listed in 136 company stacks and 18 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 Logentries
- Log search34
- Live logs27
- Easy setup19
- Heroku Add-on14
- Backup to S35
- Easy setup, independent of existing logging setup2
- Free2
- Search/query with regex2
- E0
Pros of Sentry
- Consolidates similar errors and makes resolution easy235
- Email Notifications121
- Open source108
- Slack integration84
- Github integration71
- Easy48
- User-friendly interface44
- The most important tool we use in production28
- Hipchat integration18
- Heroku Integration17
- Good documentation15
- Free tier14
- Self-hosted9
- Easy setup9
- Realiable7
- Provides context, and great stack trace6
- Feedback form on error pages4
- Love it baby4
- Gitlab integration3
- Easy Integration3
- Filter by custom tags3
- Super user friendly3
- Captures local variables at each frame in backtraces3
- Performance measurements1
Sign up to add or upvote prosMake informed product decisions
Cons of Logentries
Cons of Sentry
- Confusing UI12
- Bundle size3