( 92 )
Nicht beansprucht: Wir arbeiten an Sentry ?
Sentry ist ein Open-Source-Fehlerverfolgungstool, das Entwicklern hilft, Abstürze in Echtzeit zu überwachen und zu beheben. Es optimiert den Prozess der Identifizierung, Diagnose und Behebung von Fehlern in Softwareanwendungen in verschiedenen Programmiersprachen. Zu den Fähigkeiten von Sentry gehören die Bereitstellung detaillierter Fehlerberichte, Kontext zu den Ursachen der einzelnen Fehler sowie Tools für die Teamzusammenarbeit zur effizienten Lösung von Problemen.
Sentry wird auch oft als Application Performance Monitoring (APM) Tool der Wahl in Indie-Hacker kombiniert mit einem nachhaltigen Materialprofil. Web-Entwicklung Tech-Stacks.
( 1 )
| Unser |
|
|---|---|
| Kategorie |
|
| Einsatz | Cloud / SaaS / Webbasiertes, On-Premise-Linux |
| Unterstützung | Chat, E-Mail/Helpdesk, FAQs/Forum, Wissensdatenbank |
| Training | Dokumentation |
| Sprachen | Englisch |
Vergleichen Sentry mit anderen beliebten Tools in derselben Kategorie.
you can easily integrate sentry with Github to create issues, assign those to users, send messages to slack channels and have a good real-time control of your system's health.
the notifications settings can be tricky. It took some time until I was able to configure it properly to not be bombarded by emails.
I'm using Sentry to track/control bugs in five java ee systems. Sentry helps a lot given all required information and resources to reproduce and understand unexpected behaviors.
I can capture all the necessary information realtime yet don't overwhelmed notification queue because it does "intelligent" notification. Easy to configure and easy integration with Slack.
Project setup UI might not be the most intuitive UI
Issue to be instantly notify developers and proactively fix the issue instead of waiting for someone to report.
We have two hybrid applications written in Javascript with Ionic/Cordova. Without Sentry, it would be impossible to investigate a lot of problems/errors reported by our customers, we like the very detailed erros reports and the filtering feature that lets you search by operating system, device model, and so on. Also, Android Java exceptions tracking is very good.
I don't like frequent errors management: it would be nice, for the same error occoured hundreds or thousands of times, to filter single events by operating systems, device model, more or less like the general error filtering. It would be easier to isolate single events reported by specific customers.
It surely help to save a large amount of time while debugging, and makes possible to solve problems otherwise unsolvable
* It is easy to integrate with our applications. * It supports most commonly used languages such as JavaScript, Python, Php, nodejs, among others. * Easy monitoring of errors in real time with a detailed and accurate description * External Integrations: GitHub, Bitbucket, Trello, Slack, and anothers more
* Some errors are not our application * Email notification can be overwhelming.
I helped to improve the response time in resolving errors as well as in correcting errors in all environments (development, production).
Sentry provides the right level of detail necessary when users experience issues in global applications. It eliminates the time gap it takes to dig through log files to root cause specific stack traces.
The manual installation procedure was a little bumpy. Email notifications are sometimes overwhelming and bothersome (you have the ability to mute these though).
Bug tracking across multiple languages in several regions. Sometimes it's easiest to let users be your QA testers to find every last little glitch.
pretty easy to set up. i used a self-hosted version and didn't have much trouble installing it. i love not receiving 5000 emails for one 500 error but just see in sentry that the same issue occurred 5000 times. and to be able to categorize them and mark as resolved.
i think install process can be even simpler.
i have various clients that have various websites. before webapps were just sending 500 emails to email group aka admins@domain.com which would spam 5 people with many many emails. it's very annoying and creates too much noise. most people just set up email filters so those emails bypass inbox and no one is aware of issues. sentry solves that probles easily, dashboard is awesome too.
error playback! When encountering a bug but there's no way to re-create it. It is primarily the issue. Sentry simplifies it and allows us to do just that. One can monitor the behaviour of the error and most likely will find a solution faster than manual labour.
Added overhead in the production system along with installation. Almost all major framework have their error handling mechanism in place. And they're getting good day by day. So if you're a startup and run a smaller workload, I think you will be better off using native error handling.
Sentry takes the beta tester role and provides rich information regarding the origin, how to reproduce and possible solutions in the context of any given error that may surface.
Very easy to monitor any application Support to send custom exception and event data Support to put alerts on tags
Paid plan is pricier for a largish volumne
Sentry is solving for exception tracking and moving into application performance tracking comprehensiviely. We can monitor a lot of our code using it's features and route them to notify to diff destinations
Helpful in monitoring and notification when we have failures in Production / non-Production environments. Pin-point a component and line of code as the potential cause of failure. Saves trouble-shooting time for the engineering team.
Very difficult to filter the error. Also, not muting repetitive errors causes a lot of extra noise.
Tracking production user failures.
It is easy to install and integrate with multiple languages and platforms. The dashboards and integrations with other systems (Jira, OpsGenie, Slack, etc.) make it easy to integrate into existing developer workflows.
The stack traces and debug information for languages outside of Python are not as detailed as some other platforms. Rate limits and pricing are painful to navigate at times.
Knowing when our applications have issues before customers report them to us. Also, giving us increased confidence to deploy knowing we will be alerted if users are encountering errors.