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.1 out of 10
N/A
Sentry provides engineering teams with tools to detect and solve user-impacting bugs and other issues.
Great platform for managing application and server logs at a large scale. Elasticsearch can be integrated into 3rd-party software. For example, when combined with Kibana, beats, and logstash to build a full ELK stack it is very powerful and extremely useful for log evaluation, analysis showing detailed information, and creating a monitoring system.
[Sentry] is honestly an amazing product. It allows us to detect errors in real time complete with stack traces and any extra accompanying information the developer wants to provide in the alert. With the alerting into Slack it has allowed us to quickly triage and tag in people who need eyes on a specific issue. It would be really useful in any Saas product environment.
Elastic observability has a lot of features and good customer support. And Overall cost is good. Product functionality and performance are good but have some charting issues. But it is good. Elastic observability has a product roadmap and future vision. And it also has a good and strong user community with a lot of people engaging with good customer support for all needs.
We actually ended up using both because New Relic is a more robust overall IT infrastructure monitoring product. However, sentry is more developer oriented on the backend and more client friendly on the front end as far as showing results and the dashboard etc. It can provide product level insights that New Relic does not.
Error tracking is a must in any modern dynamic website or app. By looking into the error notifications I'm able to fix errors before anyone even has a chance to complain about them!
Surprisingly, many website issues aren't showing up in Sentry, because they don't trigger exceptions. I'm interested in seeing if I can use Sentry to catch manually-triggered exceptions for "undesirable states" that my website can find itself in. Of course, that means I have to figure out how to have my client code recognize that it's in an undesirable state...
