I held off on making this post for a little while because I was afraid I'd do the thing where you give yourself a happy brain chemical boost for having "done" something without actually making anything, but I think I'm finally at the point where it makes sense to talk about what I've done so far.
So, to get right into what I'm building: Houston is an app you can use to track a bunch of things about your website/web app that people commonly want to track. It's primarily aimed at indie devs building relatively small apps, particularly those who can't or don't want to use the big name apps to get these features (most of which you typically have to pay for to get something you can reasonably use in production).
The features I'm working on for the MVP are uptime monitoring and logging, but if/when this takes off, the end goal is to add a bunch of features, like (privacy-focused) analytics, performance monitoring (e.g. automated Lighthouse audits), etc.
Here's a bird's-eye view of what I'm looking at for the MVP:
So far, I've got most of the core services built (for the most part), as well as the uptime monitoring infrastructure. Now I'm moving onto the logging infrastructure, and after that will be actually building the user-facing app (which I suspect is going to be what takes up most of my time).
One thing that concerns me is that, at least in my local testing, the number of concurrent requests the monitor agent can make seems lower than I expected - it starts getting timeouts as soon as I push it past 500 monitors or so per minute. Obviously this is fine for an MVP, and I have ideas for how to make the monitoring infrastructure more scalable, but I was kind hoping I wouldn't have to think about that for a while. Maybe this is just my home connection and it'll be fine in production? I guess we'll see.
So, yeah, I think that's all I have so far. What does everyone think? Is this something you can see yourself wanting to use? Am I barking up the wrong tree?