Grafana Logs (powered by Loki) brings together logs from applications and infrastructure in a single place. By using the exact same service discovery and label model as Prometheus, Grafana Logs can systematically guarantee logs have consistent metadata with metrics. Grafana Logs lets users send logs in any format, from any source so it’s easy to add to existing infrastructure and get up and running quickly. Leverage a wide array of clients for shipping logs like…
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.
Loki is an essential complement to Grafana and provides logging metrics for dashboards and other visual tools. Loki can handle the service logging, while other data source plugins can provide more specific quantifiable metrics to support the logging data. Different types of …
First and foremost if Grafana Loki is based on CNCF open source projects so organizations can get freedom to choice to configure it at your own other main thing is Grafana Loki is totally free of cost and we can deploy it on our infrastructure. On compared with other managed …
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 …
Both AppD and Instana are a superset of sentry the majority of the time. Sentry is specialised in error tracking does the best in it, but the other too mentioned does a similar job along with multiple other monitoring features. Also, sampling of data is best in Instana, and is …
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 …
Sentry was cheaper and lighter weight/easier to deal with. New Relic always felt like it was slowing the site down some. I don’t think either has had any major negative impact, but Sentry always seemed better/faster. Also, Sentry doesn’t have contracts like New Relic does …
Sentry is better suited for tracking and aggregating exceptions over New Relic. New Relic does report on exceptions that occur, but Sentry is better at rolling up similar exceptions and filtering out the noise. Sentry also does a great job at identifying when an exception first …
Sentry is really a tool to be used in combination with other things, like Pingdom and PagerDuty. For those applications, Sentry is a far more full-features offering that lets you see why errors happened, not just be alerted to their occurrence. We chose it over other error …
There are quite a few players in this space, but Rollbar and Sentry seem to be the top two. I can't remember why I chose Sentry over Rollbar, but they seem pretty close in terms of features.
[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.
Loki is an essential complement to Grafana and provides logging metrics for dashboards and other visual tools. Loki can handle the service logging, while other data source plugins can provide more specific quantifiable metrics to support the logging data. Different types of metrics make a robust data dashboard.
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...