Hey HN,I'm building a service that monitors your webapp and gives you a definitive signal when something is broken, all with minimal setup.You can check it out at: https://www.catalystmonitor.com/, read the docs at: https://docs.catalystmonitor.com/, or see the dashboard at: https://app.catalystmonitor.com/You can also see a (very quickly made) demo at: https://www.loom.com/share/5b38a328ded94f93a980f1ba28081329?sid=5afe55d1-0e0a-42a1-b748-1c230eacd430I've seen how having robust internal monitoring infra maintained by dedicated teams helped developers at large companies. This was something I missed when I later moved to a startup. I was disappointed by how much setup and maintenance was required by existing monitoring products: I constantly fiddled with Splunk queries, pruned Sentry errors, and created New Relic dashbords, all to get weak signals to the only thing I cared about: is my product currently broken or not for users? So I decided to build the tool that I would've wanted.Most people building a product want to maximize effort on actually building their product and minimize effort monitoring it, so I built this service to be easy to set up: you can sign up, integrate it, and get useful signals within a day without worrying about configuration or monitoring new code-paths.The downside to being easy to set up is that it's opinionated, less configurable, and won't be 100% effective for certain use-cases. If you throw errors and use HTTP error codes instead of swallowing errors, you'll get useful monitoring with minimal effort right out of the box.There are currently client libraries for the browser, Node.JS, Express, and React Router, but integration with other JS/TS frameworks shouldn't be hard while integration with other languages is definitely possible. Please let me know if you'd be interested in support for another language or framework.Also, I know it's ironic, but it's still under development, and thus may have bugs. I'd love to know what you think. Either way, may your queries flow and your pagers stay silent.
Users are interested in the product, requesting a loom or sample dashboard for a clearer view before signing up, as images on the site are blurry. They find the dashboard clean and are inquiring about pricing information, with a particular interest in affordability for indie developers. Questions about support for Next.js, setup, traffic handling, and pricing differences are also raised. One user suggests trying Monibot for app metrics and server usage.
Users criticized the product for its unclear market position, blurry images on the website, inaccessible pricing for independent developers, inability to import metrics from other tools, and lack of comparability to established products like Catalyst.