3 ms·

Looks like a good tool for incident management. Create notes/summary on the go and access them quickly next time similar event happens. There's definitely deman

Looks like a good tool for incident management. Create notes/summary on the go and access them quickly next time similar event happens. There's definitely demand for it. There's also been recent discussion at r/DevOps: https://www.reddit.com/r/devops/comments/8qi33c/manage_incidents/ https://www.reddit.com/r/devops/comments/8qi33c/manage_incid... One thing that might be useful is to see aggregate incident data and find components that are operational burden for the team. Shameless plug: I built http://nurtch.com http://nurtch.com for quick incident response with interactive runbooks. You can pull in graphs, get deployment status, rollback deployments, run SQL queries, run bash scripts and terminal commands over SSH directly from runbook.

dzimine 8y ago
Nurtch DOES look like an awesome idea: jupyter notebooks proved to be a greatest interactive tool as well as for sharing the work. Good job with the site, too, best of luck with it. If you’re serious about automating operations and wiring with slack/Chataops, check out StackStorm (disclosure I am one of the creators). Open source Apache 2.0,?installable, no mines. It’s much heavier than Nurtch or FireHydrant, as it comes with IfThisThanThat logic and workflows to string individual actions in runbooks, chat ops out-of box, but different strokes for different folks, we all runnops differently, pick your pill. https://GitHub.com/StackStorm/st2 https://GitHub.com/StackStorm/st2
- amirathi 8y ago
  Thanks & good work with StackStorm :) I'm curious to know your take on Rundeck as well? For others: StackStorm/Rundeck offers IFTTT for operations (amongst other things). Alert X -> Run script/workflow Y. It's an ideal approach to operations as it takes human out of the loop. Less on-call alerts, quick recovery. Sort of like a self healing system. Highly recommend. Some companies can't/don't want to invest in full automation workflows. Nurtch is useful in this case as it allows partially automating runbooks by interleaving instructions and code. Downside is that human is still involved, engineer still gets paged :( but on the plus side, resolution could take 10 minutes instead of 2 hours & less upfront investment.
  - dzimine 8y ago
    Rundeck is a good system, around for quite some time. I met many people who are using it in prod, some migrating to StackStorm when they need IFTTT, or those who prefer not to operate Java, some staying as Rundeck has more UI for one-off commands.

dzimine 8y ago

Nurtch DOES look like an awesome idea: jupyter notebooks proved to be a greatest interactive tool as well as for sharing the work. Good job with the site, too, best of luck with it. If you’re serious about automating operations and wiring with slack/Chataops, check out StackStorm (disclosure I am one of the creators). Open source Apache 2.0,?installable, no mines. It’s much heavier than Nurtch or FireHydrant, as it comes with IfThisThanThat logic and workflows to string individual actions in runbooks, chat ops out-of box, but different strokes for different folks, we all runnops differently, pick your pill. https://GitHub.com/StackStorm/st2 https://GitHub.com/StackStorm/st2

amirathi 8y ago
Thanks & good work with StackStorm :) I'm curious to know your take on Rundeck as well? For others: StackStorm/Rundeck offers IFTTT for operations (amongst other things). Alert X -> Run script/workflow Y. It's an ideal approach to operations as it takes human out of the loop. Less on-call alerts, quick recovery. Sort of like a self healing system. Highly recommend. Some companies can't/don't want to invest in full automation workflows. Nurtch is useful in this case as it allows partially automating runbooks by interleaving instructions and code. Downside is that human is still involved, engineer still gets paged :( but on the plus side, resolution could take 10 minutes instead of 2 hours & less upfront investment.
- dzimine 8y ago
  Rundeck is a good system, around for quite some time. I met many people who are using it in prod, some migrating to StackStorm when they need IFTTT, or those who prefer not to operate Java, some staying as Rundeck has more UI for one-off commands.