LogCaptor
sentry-java
Our great sponsors
LogCaptor | sentry-java | |
---|---|---|
5 | 5 | |
331 | 1,077 | |
- | 1.4% | |
6.7 | 9.4 | |
9 days ago | 5 days ago | |
Java | Kotlin | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
LogCaptor
sentry-java
-
Methods and processes for reduce bugs in production
>As now we've introduced some peers code review, automatic testing on most critical stuff (but since the codebase sucks these aren't really reliable tests)
They may not be "reliable", but these are your safety net, or harness, so you don't fall. I wrote about similar issues, for instance here: https://news.ycombinator.com/item?id=26591067 and, given your promotion, here: https://news.ycombinator.com/item?id=37211796. It contains a few steps starting from "So...".
You can add monitoring, something like Sentry (https://sentry.io) will capture exceptions that were not handled that you have not seen because the stack trace is buried in hundreds of pages of logs or something. It groups them by exception and counts them. It's pretty awesome. (https://docs.sentry.io). It supports around 108 platforms (Java, Python, JavaScript, etc.). This lets you see the exceptions and makes prioritizing easier (which ones are the most frequent, which ones impact the most, etc.).
If you don't have them already, issue templates are really useful and the comment I linked to explains why, but here's an example of an issue template (again, you can configure them for different types of issues so team members select from a dropdown for a bug or a feature):
-
GraphQL Observability with Sentry
Sentry provides informative guides for many platforms. In our server's case, we apply Apollo Server v2 as an Express middleware; therefore, Sentry's Express Guide with request, tracing, and error handlers is a great starting point.
-
Integrating OpenReplay with Sentry
The last step is to extract the openReplaySessionToken from the header and add it to your Sentry scope (ideally using a middleware or decorator) in your backend. The method to do this depends on the programming language of your backend, you can consult the Sentry docs on how to configure scope. The snippet below shows how to configure a Sentry scope if your backend is built with node.js/express
-
Plato Removes Ads from the App
In a lot of cases crash report SDKs are open source?
What are some alternatives?
zipkin - Zipkin is a distributed tracing system
Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
Jaeger client - 🛑 This library is DEPRECATED!
openreplay - Session replay and analytics tool you can self-host. Ideal for reproducing issues, co-browsing with users and optimizing your product.
console-captor - 🎯 ConsoleCaptor captures console output for unit testing purposes
logger - ✔️ Simple, pretty and powerful logger for android
Bugsnag - BugSnag crash monitoring and reporting tool for Android apps
leakcanary - A memory leak detection library for Android.
cve-2021-44228-qingteng-online-patch - Hot-patch CVE-2021-44228 by exploiting the vulnerability itself.
tinylog - tinylog is a lightweight logging framework for Java, Kotlin, Scala, and Android
Reasonable-Test-Logs - Junit5 test execution listener that hides log events for "green" tests.
CVE-2021-44228-Scanner - Vulnerability scanner and mitigation patch for Log4j2 CVE-2021-44228