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.
What is Logentries?
What is Sentry?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Logentries?
- Free2
Why do developers choose Sentry?
- Easy43
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Logentries?
What are the cons of using Sentry?
What companies use Logentries?
What companies use Sentry?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
For my portfolio websites and my personal OpenSource projects I had started exclusively using React and JavaScript so I needed a way to track any errors that we're happening for my users that I didn't uncover during my personal UAT.
I had narrowed it down to two tools LogRocket and Sentry (I also tried Bugsnag but it did not make the final two). Before I get into this I want to say that both of these tools are amazing and whichever you choose will suit your needs well.
I firstly decided to go with LogRocket the fact that they had a recorded screen capture of what the user was doing when the bug happened was amazing... I could go back and rewatch what the user did to replicate that error, this was fantastic. It was also very easy to setup and get going. They had options for React and Redux.js so you can track all your Redux.js actions. I had a fairly large Redux.js store, this was ended up being a issue, it killed the processing power on my machine, Chrome ended up using 2-4gb of ram, so I quickly disabled the Redux.js option.
After using LogRocket for a month or so I decided to switch to Sentry. I noticed that Sentry was openSorce and everyone was talking about Sentry so I thought I may as well give it a test drive. Setting it up was so easy, I had everything up and running within seconds. It also gives you the option to wrap an errorBoundry in React so get more specific errors. The simplicity of Sentry was a breath of fresh air, it allowed me find the bug that was shown to the user and fix that very simply. The UI for Sentry is beautiful and just really clean to look at, and their emails are also just perfect.
I have decided to stick with Sentry for the long run, I tested pretty much all the JS error loggers and I find Sentry the best.
SquareSentry has been very useful for me and my team. I caught a bug in staging โ just as one example โ which I wouldn't have caught before deploying to production. That's the sort of thing that happens on a regular basis with Sentry.
I didn't personally make the decision to use Sentry since I'm part of a very large organization that chose it before I joined company. But we've been more than happy enough with Sentry that we use it across most of our teams, regardless of their stack.
Fresha Engineering
Regarding Continuous Integration - we've started with something very easy to set up - CircleCI , but with time we're adding more & more complex pipelines - we use Jenkins to configure & run those. It's much more effort, but at some point we had to pay for the flexibility we expected. Our source code version control is Git (which probably doesn't require a rationale these days) and we keep repos in GitHub - since the very beginning & we never considered moving out. Our primary monitoring these days is in New Relic (Ruby & SPA apps) and AppSignal (Elixir apps) - we're considering unifying it in New Relic , but this will require some improvements in Elixir app observability. For error reporting we use Sentry (a very popular choice in this class) & we collect our distributed logs using Logentries (to avoid semi-manual handling here).
SentryLots of companies I respect were using it + open-source + great features and UI. Went for the hosted version, since it plays nice with Heroku. I like how they group together similar errors, give you the ability to mute events or mark them as solved. P.S. check out the Founder Stories feature we did on Sentry if you want to know how they started, its an awesome story.
SentryThe error and event tracking in Sentry is superb. Being able to assign the raw error to people along with all information at the time the event occurred means that we're tracking and fixing problems before they become apparent to customers. We use the self-hosted instance of Sentry.
SentrySentry is a very powerful error reporting tool. We use it both on front-end and back-end of Ataccama One. It proved to be invaluable in providing insights on our errors - what caused it, what user did before the error occured, stack trace, release tracking and more.
SentryWe use Sentry to gather our thrown non-checked exceptions in one place, so we don't have to crawl through all our logs manually. All standalone-applications, our website aswell as our game-servers are linked into sentry.
SentrySentry is amazing, most of our systems send their exceptions to sentry. We couldn't live without it and get a much better understanding of how our code is behaving in the wild. Plus it integrates with Github.
LogentriesLogentries is an easy-to-use, self-hosted log management and analytics service for teams of all sizes. It is integrated as a Heroku add-on which makes it simple to search, analyze, and manage the logs.
LogentriesMain service used by Coolfront Mobile and Coolfront Books to capture logging information.
LogentriesWe are still trying to figure out the best logging approach for production
LogentriesDistributed system log tracking
LogentriesLog file storage and analysis.