You can also use the client to create custom events.
When you move things to "the cloud". Take a look at Sentry[1] for error monitoring. It'll show you errors and exceptions aggregated instead of you looking into logs for exceptions and errors. It has integrations with GitLab, Slack, etc.
Additional resources you might be interested in are Segment[2] and RudderStack[3].
One good way to get things going is to have a way to interact with your users. Having a button that says "Send us an issue" for when they have problems with an `href` that opens a mail client with a prefilled template and email addresses can be useful.
<a href="mailto:support@yourstartup.com?cc=founder@yourstartup.com;cofounder@yourstartup.com&subject=The issue title&body=You can have a template here" rel="email">Complain!</a>
Another useful thing is to have either Slack channels so people can ask for help there, or help each other out to solve their problems. Essentially building a community.(I'm biased against chatbots, but you may not have an allergic reaction).
Essentially, all these help focus on issues based on impact (positive or negative) and frequency.
When you get the 20th user complains about something, you know the next thing is to get that fixed if its impact is big.
I wrote a bit about this here[4], here[5], and generally about stuff here[6]
- [0]: https://posthog.com
- [1]: https://www.sentry.com
- [2]: https://segment.com
- [3]: https://rudderstack.com
- [4]: https://news.ycombinator.com/item?id=22827841