Developer tools are unlike any other kind of software. All your users are power users. This blurs the line between your users and your code.
GitHub issues and Slack conversations are a poor guide to real usage of your software. Only a small proportion of the people who ever used your tool will be motivated enough to speak with you through these channels. The issues that these users have may not be representative of the real issues - the ones, for example, that drive people away from your "Getting started" guide.
At https://bugout.dev, we are building a huge knowledge base of bugfixes to help developers overcome issues with the tools and libraries they depend on. We are also trying to help developer tool maintainers gain a better understanding of how their users use their software.
We have taken a big step forward this week with the release of Humbug, which helps developer tool maintainers collect usage and crash reports from their users only with their full consent.
Here is a short video showing how to use Humbug in your Python developer tool:
Find out more about how to set up Humbug on the GitHub repository:
bugout-dev
/
humbug
Get usage metrics and crash reports for your API, library, or command line tool.
humbug
Humbug helps you understand what keeps users coming back to your developer tool as well as any friction they experience.
Humbug lets you collect basic system information and crash reports while respecting your users' privacy. In addition to getting reports, you get to be GDPR-compliant from day one.
Humbug is currently available in the following programming languages:
-
- System information report
- Error traceback report
- Packages available in the current Python process report
- Logs report
- Environment variables report
- Custom report with full content control
-
- System information report
- Panic report
- Custom report with full content control
-
- System information report
- Error traceback report
If you would like support for another programming language, please create an issue.
Using Humbug
Setup
Follow the instructions in the Getting started with usage and crash reporting guide.
From development to production
We recommend generating one token for development and testing and using different…
Go and Javascript support are coming soon!
Top comments (0)