Sentry and Elastic Observability offer robust monitoring solutions. Users are happier with Sentry's ease of use and customer support, but Elastic Observability excels in feature depth and performance, making it a favorable choice despite the higher cost.
Features: Sentry provides real-time error tracking, intuitive alerts, and a user-friendly interface. Elastic Observability offers comprehensive log analytics, multi-source data integration, and extensive data visualization capabilities.
Room for Improvement: Sentry needs enhanced integration with other DevOps tools, better performance monitoring, and scalability improvements. Elastic Observability requires a simpler setup process, more intuitive error tracking, and enhanced user documentation.
Ease of Deployment and Customer Service: Sentry has straightforward deployment and responsive support. Elastic Observability has a steeper learning curve but benefits from good customer support, though users find Sentry's deployment ease an advantage.
Pricing and ROI: Sentry is cost-effective with quick ROI and lower setup costs. Elastic Observability is more expensive but justifies the cost with its extensive features, leading to satisfactory ROI. Users feel Elastic Observability's higher costs are worthwhile due to its powerful capabilities.
Elastic Observability seems to have a good scale-out capability.
What is not scalable for us is not on Elastic's side.
It has been easy to use and configure across multiple systems, each having several environments.
It is very stable, and I would rate it ten out of ten based on my interaction with it.
Elastic Observability is really stable.
For instance, if you have many error logs and want to create a rule with a custom query, such as triggering an alert for five errors in the last hour, all you need to do is open the AI bot, type this question, and it generates an Elastic query for you to use in your alert rules.
It lacked some capabilities when handling on-prem devices, like network observability, package flow analysis, and device performance data on the infrastructure side.
Elastic Observability could improve asset discovery as the current requirement to push the agent is not ideal.
Integrations or single sign-on capability with Microsoft would be beneficial for securing all assets.
Elastic Observability is cost-efficient and provides all features in the enterprise license without asset-based licensing.
Observability is actually cheaper compared to logs because you're not indexing huge blobs of text and trying to parse those.
The license is reasonably priced, however, the VMs where we host the solution are extremely expensive, making the overall cost in the public cloud high.
Compared to New Relic, it provides the necessary features at a cheaper cost, especially since we moved infrastructure monitoring to Azure.
The most valuable feature is the integrated platform that allows customers to start from observability and expand into other areas like security, EDR solutions, etc.
the most valued feature of Elastic is its log analytics capabilities.
All the features that we use, such as monitoring, dashboarding, reporting, the possibility of alerting, and the way we index the data, are important.
Real-time error tracking helps our Quality Assurance team easily identify the root causes of problems or bugs and promptly inform the developers about specific issues.
At this time, I focus on finding and fixing bugs.
Elastic Observability is primarily used for monitoring login events, application performance, and infrastructure, supporting significant data volumes through features like log aggregation, centralized logging, and system metric analysis.
Elastic Observability employs Elastic APM for performance and latency analysis, significantly aiding business KPIs and technical stability. It is popular among users for system and server monitoring, capacity planning, cyber security, and managing data pipelines. With the integration of Kibana, it offers robust visualization, reporting, and incident response capabilities through rapid log searches while supporting machine learning and hybrid cloud environments.
What are Elastic Observability's key features?Companies in technology, finance, healthcare, and other industries implement Elastic Observability for tailored monitoring solutions. They find its integration with existing systems useful for maintaining operation efficiency and security, particularly valuing the visualization capabilities through Kibana to monitor KPIs and improve incident response times.
Sentry is a tool for monitoring web and application performance, tracking errors, processing request times, and managing user data access.
Developers integrate Sentry with web and application environments to capture front-end and back-end errors, utilize error logs, trace requests, and observe metrics without real-time production access. Sentry's use extends to monitoring internal applications, leveraging CyberArk PAM integration, deploying notifications, and detecting silent failures. Users benefit from detailed error and performance reports, contextual cause-stack information, and real-time breakdowns. There is room for improvement, as users desire refined integration and administrative settings, enhanced alert policies, and more customization in event metrics.
What are Sentry's most important features?Sentry is implemented across industries ranging from tech startups to large enterprises. These organizations use Sentry to enhance application reliability, track performance, and secure user data within protected environments. Integration with CyberArk PAM ensures secure deployment. Organizations find Sentry useful for monitoring internal applications, efficiently processing request times, and tracing changes in production without direct access.
We monitor all Application Performance Monitoring (APM) and Observability reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
