Share your experience using GDB

I've recently created an issue for a project I'm working on. We use it to categorize the issue with specific tags, assign it to particular users, track its status, and set its priority. This allows for better organization and ensures that tasks are appropriately tagged and assigned to the responsible individuals.

It enables mapping issues to specific team members, making it a valuable feature. The user-friendly nature of this functionality enhances the overall experience.

The challenge lies in the initial setup and the difficulty of adding new Issues.

I have been working with it for a few months.

It is stable, and I haven't encountered any issues.

In terms of scalability, we can include as many Issues as needed without encountering any apparent limits. Based on my observations from various open-source projects, even those with hundreds or thousands of Issues, there don't seem to be significant problems. There are around twenty to twenty-five members in the prototype.

The initial setup wasn't straightforward. I had to search for instructions on how to configure it.

It doesn't necessarily have to be deployed; instead, it is essentially assigned to an individual. We can create and assign a person to it, along with adding a suitable title. Maintenance is generally unnecessary, and the status doesn't need regular checking. Instead, the individual who oversees the issues, typically the leader, ensures completion by periodically verifying the assigned tasks.

It is an open source. There are no extra charges associated with it.

Overall, I would rate it eight out of ten.

The solution's dashboard is used to check how many users were online, how many users were using our application, how many times the application crashed, and which call had crashed.

With BugSnag, we are able to get some data out of it. I am currently working for a payment app, and we have to redirect the customer to the VGS pages. When a crash occurs, we know that the crash is not on our side. We know that the crash happened on the VGS side or something is wrong with our integration with VGS.

Since BugSnag is a web application and not a mobile application, a user's attempts to click on the back or forward buttons also get logged.

It's hard to integrate with the application, and the setup was not very straightforward.

I have been using BugSnag for eight to nine months.

BugSnag is a stable solution.

I rate BugSnag a nine out of ten for stability.

I rate BugSnag a seven out of ten for scalability.

I previously used Instabug.

We implemented the solution through an in-house team. The solution's deployment was a one-time effort. After we figured out how to integrate it, it took us two hours to deploy it.

Before choosing BugSnag, we were evaluating other options, including Instabug. We chose BugSnag because the other solutions were not supported for web applications.

I would advise users to create logs for as many requests as possible because you don't know what's going to crash on production.

Overall, I rate BugSnag an eight out of ten.