I built an error tracker that opens the pull request for you (self-hosted, PHP/JS/Flutter)
Every error tracker I have used stops at the same place: here is the stack trace, here is how many times it happened, good luck. The next 40 minutes — open the file, read the code around the line, figure out the change — are always mine. I wanted that part to happen before I open the ticket. So I built Bugban . What happens when an error arrives Grouping. A fingerprint (class, file, line,…
Bugban is an error tracker that streamlines the process of identifying and resolving software issues. Instead of merely providing a stack trace and a count of occurrences, Bugban offers a comprehensive solution that includes grouping, context, AI analysis, and a pull request for the fix. When an error occurs, Bugban creates a fingerprint based on the error's class, file, line, and normalized message. This allows similar errors to be grouped together, making it easier to analyze and address the root cause.
The tracker provides context about the error, including the request method, URL, route template, controller, action, signed-in user, session, breadcrumbs, device information, and for browser projects, a DOM snapshot with masked inputs. Additionally, Bugban offers AI analysis, generating explanations and concrete fixes in the language of the user's choice, such as English, Azerbaijani, Russian, or Turkish.
One of the unique features of Bugban is the ability to generate a pull request directly from the error. This pull request automatically reads only the files indicated by the stack trace and applies a whole-file change to a designated branch. The responsibility of merging the pull request back into the main branch remains with the user, ensuring that only when the fix has been verified and deployed should the error be considered resolved.
Bugban also includes several practical safeguards to prevent unnecessary work. For instance, it only triggers a fix for new or reopened errors, and caps the number of open PRs per error to one, with a daily limit per project. The tracker acknowledges when it is unsure about the fix and returns a "I'm not sure" response instead of pushing a potentially incorrect solution. Moreover, it requests the entire file rather than a diff, recognizing that models may sometimes misinterpret line numbers in unified diffs.
Bugban also focuses on performance optimization, particularly for mobile platforms. Mobile apps often face different challenges compared to web applications, and Bugban acknowledges this by measuring app start, screen load, and jank times, rather than relying on Web Vitals. The tracker also provides detailed insights into slow queries, including the query plan, rows examined, and key used, ensuring that developers can make informed decisions about database optimization.
In summary, Bugban is an all-in-one error tracking solution that not only helps developers identify and fix errors but also provides insights into performance issues, especially for mobile applications. Its user-friendly interface, comprehensive feature set, and emphasis on security make it a valuable tool for developers seeking a more efficient and effective way to manage their software errors.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
