Hey HN,<p>I’m exploring an idea for a plug-and-play analytics solution specifically for CLI tools — think Google Analytics, but for the command line. After reviewing multiple open-source CLI tools, I noticed that many teams end up building analytics from scratch. Setting up and maintaining this kind of infrastructure can be resource-intensive and often lacks features that would make it more actionable.<p>Here’s what I imagine this solution would offer:<p>1. Automatic command tracking to capture usage patterns and activity frequency<p>2. Error and crash reporting to help identify pain points in real-time<p>3. Opt-in/opt-out strategies for respecting user privacy preferences<p>4. A web dashboard for data visualization and analysis<p>I’d love to get the community’s perspective on this. Is this something you’ve encountered a need for? If you’re already using or building a CLI, would such a tool be useful, and what features would be most valuable to you?<p>Also, if anyone here has tackled CLI analytics themselves, I’d be interested to hear about any challenges you faced or any DIY solutions you’ve found effective. Thanks for any feedback!
I'm confused by your points.<p>What's wrong with using any current event tracking solution ?<p>Segment/GA/Posthog/Umami/.../.. even today published Trench [0]<p>[0 ]<a href="https://news.ycombinator.com/item?id=41945458">https://news.ycombinator.com/item?id=41945458</a>