A web-based interface for dev-op tasks across remote servers using SSH

I like the idea of this but some visuals like graphs or meters would make it a lot more interesting.

I wrote a little monitoring tool like this for our servers. instead of the monitor using ssh command "recipes", it just hits API endpoints that return JSON. The monitor doesn't really care what the API is checking, it just expects that service to "neutralize" whatever metric it is checking into something that can be graphed. I think the same could be done if you have a specific data format that recipes are required to output. Those recipes that returned a common data format could then be graphed. Of course it takes a minor amount of programming to parse the output from "uptime" (for example) into formatted data, but once one person did it that could be available as a pre-buit recipe for all of your customers.

Our tool is pretty much hard-coded to our system but I had always thought it would be a cool thing to have. I've looked at other monitoring systems that seem to do that already but many of them are so complicated and none of us have the motivation to learn them. We're a typical team of programmers who have to be admins by default.

OK one feature you should add and will make this stand out even more.

Two phase commit.

Admin enters commands, another had to enter same commands on another console and only then are they executed or passed to a third admin to approve actioning.

No more rm -f in root or other slip ups. No more silly mistakes. Added accountability and in that added security.

You would also get x10 the amount of backing from alot of institutions alone for that feature and even if you don't have it now, factor it in down the line as the quality of admins has gone down hill over the years and in that more mistakes get made. This will reduce that and the impact as well as protecting jobs as well as the machines from human shortcommings.

Logging aspect you have outlinesd is good. Get it robust by design and cater for remote logging servers and with all that you could go far.

Good luck

I work with clusters of hundreds of machines every day. When I watched the video I cringed, a lot. I can't imagine using a web app for this task. I thought there is no way in hell I'm ever going to enter in the hostnames of hundreds of hosts into a fucking web form. Lay off the bogus terminology too. I write scripts and programs, not 'recipes'. A script with a version number is still a damn script.

I watched most of the video, and I had a visceral negative reaction to the product and the presentation.

For simple multiplexing, if you need to work with more than 20 servers at a time, take a look at omnitty. It has a different layout that makes it much easier to work with larger groups in interactive sessions.

It definitely does: when I launch a job in RunDeck, I can see the live output (essentially a form of tail -f in the RunDeck web interface) and I can see the output of every previous job as well.