
Mon.sh
Monitor your scripts with a single command
After discovering the competition in the space alongside the lack of compelling TAM I haven't been actively doing this anymore. There just doesn't seem to be a big enough space for it, and the market leader is actually pretty good for that. If I need it, it will still be here. I'm committed to being a bit more public about things so I'll be posting updates for other software more frequently.

With the launch of the latest help guide https://www.mon.sh/help/monitoring_recurring_jobs and another simple guide I'm putting together tomorrow based on existing features (I just added scheduled job detection today) I'm hoping that mon.sh will be usable for at least a few people. Time to see if people like it or not and what they want out of it.

2 Comments
2 Comments
I built mon.sh as a result of the necessity of developing long running scraping tasks for Sose.app and not necessarily having the time to make each of them instrumentable or alertable while trying to get them out. Because some of the data scraping tasks run for 40+ hours I really wanted to be able to track them without having to instrument them. It then occurred to me that a lot of how and what to track would be common across any generic script. For example seeing run time, or parsing progress bars or alerting on exceptions/errors/faults etc, or comparing runs across different executions of the same script. I've launched Mon.sh now with basic functionality that streams your logs to the cloud (although there is an issue with progress bars because they rewrite lines generally, supporting which would be a future improvement), and makes it easy to alert on those tasks when they start and when they finish.

Comment
About
Makes it easy to monitor long running processes like build, scraping, data processing, and training scripts without spending time setting up instrumentation or having to babysit them.


Comment