Try our new research platform with insights from 80,000+ expert users

Mezmo vs Sentry comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Mezmo
Ranking in Application Performance Monitoring (APM) and Observability
92nd
Average Rating
9.0
Number of Reviews
2
Ranking in other categories
Log Management (55th), Observability Pipeline Software (7th)
Sentry
Ranking in Application Performance Monitoring (APM) and Observability
8th
Average Rating
8.6
Reviews Sentiment
7.1
Number of Reviews
13
Ranking in other categories
Debugging (1st)
 

Mindshare comparison

As of June 2025, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Mezmo is 0.1%, up from 0.1% compared to the previous year. The mindshare of Sentry is 6.9%, up from 4.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

TO
It consolidates all logs into one place and provides required features and functionalities
Every once in a while, our IBM cloud operational implementation gets behind. Sometimes, when we have a customer event, we do not get access to the latest logs for about 30 minutes, particularly for the sites that are heavily utilized. This is clearly not good. It is impossible to do RCA when you can't look at the logs that pertain to the time period in which the event occurred. It could be more of an operational problem than a feature problem. I don't have visibility about whether it is a LogDNA issue or just an operational issue.
Abdullah Baig - PeerSpot reviewer
An easy-to-use solution that has a good dashboard, performs well, and provides flexible pricing
Sentry was easy to learn compared to New Relic and Azure Monitor. I saw some valuable input. It took us the least amount of time to see how Sentry is valuable. It took just a few minutes. Session Replay provides a replay of the recorded errors. It is a good feature. Azure Monitor does not have this feature. The error reporting is straightforward. We can see everything that we need to see. The dashboard seems pretty fine. The product performs well. We can see the user's IP addresses.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"LogDNA consolidates all logs into one place, which is super valuable."
"The solution aggregates all event streams, so that if there are any issues, it's all in the same interface."
"The solution is user-friendly."
"It's a great visibility tool for the developer team."
"Great for capturing application performance metrics and error logs."
"Sentry is more accurate than some other tools such as Datadog because it has more integration with Slack, GitLab, Jira, or other ticketing tools."
"Sentry breaks everything down in real time."
"The implementation is easy. After one or two days, I can learn and use it. It's not too hard."
"Overall, I give Sentry a rating of 10."
"The product performs well."
 

Cons

"No ability to encapsulate a query or a filter, and communicate or share that among the team."
"Every once in a while, our IBM cloud operational implementation gets behind. Sometimes, when we have a customer event, we do not get access to the latest logs for about 30 minutes, particularly for the sites that are heavily utilized. This is clearly not good. It is impossible to RCA when you can't look at the logs that pertain to the time period in which the event occurred. It could be more of an operational problem than a feature problem. I don't have visibility about whether it is a LogDNA issue or just an operational issue."
"I have not worked with Sentry long enough to provide advice for improvements. I need more experience and time."
"The log centralization and analysis could be improved in Sentry."
"It should be easier to integrate Sentry with other tools, and the end-to-end tracing capabilities could be improved."
"The price could be lowered."
"It would be nice if the product provided a map showing the users’ geographic location."
"I would like to see a role registration feature added."
"The settings for an administrator are complex."
"Its debugging feature needs to be faster."
 

Pricing and Cost Advice

Information not available
"Currently, we are in the production phase of our project and we are on free plans to use Sentry. Once we go live we will have to be on a subscription-based plan."
"I am currently using a self-hosted open version."
"We are currently paying through Cloudera for the Sentry service."
"We can adjust the price a little bit based on our needs."
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
857,585 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Computer Software Company
19%
Comms Service Provider
10%
Financial Services Firm
10%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for Sentry?
Sentry is very affordable. We spend less than $200 to $300 a month. Compared to New Relic, it provides the necessary features at a cheaper cost, especially since we moved infrastructure monitoring ...
What needs improvement with Sentry?
Right now, Sentry meets our needs and we have not encountered any bottlenecks. However, additional personalization and easier setup for capturing all the different application logs could be an area...
 

Comparisons

 

Also Known As

LogDNA
No data available
 

Overview

 

Sample Customers

Instacart, Asics, Lime, Salesforce
Dropbox, Airbnb, Stripe, Uber
Find out what your peers are saying about Mezmo vs. Sentry and other solutions. Updated: June 2025.
857,585 professionals have used our research since 2012.