Elastic Observability, from Elastic, the makers of Elasticsearch, is a solution that aims to bring logs, metrics, and APM based on the former Opbeat (acquired by Elastic in 2017) traces together at scale in a single stack so users can monitor and react to events happening anywhere in an IT environment. It's free and open to start, and adds the Logs, Metrics, APM (formerly Opbeat), and Uptime modules to the Elastic (ELK) Stack.
N/A
Sentry
Score 9.2 out of 10
N/A
Sentry provides engineering teams with tools to detect and solve user-impacting bugs and other issues.
We can use this Elastic Observability in our business problems such as Creating internal/operational efficiencies issues, customer relations/service, and business process outcomes issues. This product has a lot of features for the above problems. But this product may be having some issues when charting purposes. But it can adjust for that purpose.
Great for standard web application performance monitoring, analytics and error reporting. Shows line level code errors, gives insight into performance issues (plugins, API issues, etc.). Automation and scheduled scanning in production gives client visibility into 'after deployment' value. Also lets a relatively small number of developers keep tabs on a handful of different site/applications without needing a bunch of tools. The UI is pretty complicated and can be overwhelming for new users. Documentation could be better for the learning curve,
Great web interface. Lots of data available in a really clean format, with filtering options and more.
Per-user exception tracking. User is complaining about something being broken? Look up their account ID in Sentry and you can see if they've run into any exceptions (with device information included, of course).
Source map uploading. Took a little while to figure this out but now we have our deploy script upload sourcemaps to Sentry on each deployment, meaning we get to see stack traces that aren't obfuscated!
Very generous free tier – 10,000 events per month. We're nowhere near that yet.
Splunk is a very good product but the licensing costs are high; we utilise the best of both worlds by using both products for slightly different purposes. We put the voluminous data with simple use cases in Elastic where it doesn't cost too much and can be searched quickly while putting the less voluminous data with more complex use cases in Splunk so we can take advantage of Splunk's very comprehensive but often much slower SPL search query language
We used Rollbar but didn't like the configuration its not easy. And also doesn't support wide features like Sentry although its a cheaper option but doesn't have the dash-boarding like Sentry and its was not easy to integrate webhooks for different purposes. Somehow many people in company where not able to understand Rollbar dashboard who were very much used to Sentry.
We had to take it down later due to internal reasons and majorly because of cost-cutting process
If someone has a unstable system and have no way to figure out what to do, can use sentry at least temporarily along with some other APM to fix their system faster
