Gunnery vs Runbook: What are the differences?
What is Gunnery? Multipurpose task execution tool for distributed systems with web-based interface. If your application is divided into multiple servers, you are probably connecting to them via ssh and executing over and over the same commands. Clearing caches, restarting services, backups, checking health. Wouldn't it be cool if you could do that from browser or smartphone? Gunnery is here for you!.
What is Runbook? Infrastructure Monitoring with Automated Remediation. Runbook is a SaaS application that monitors your servers and performs automated tasks when your monitors fails. Use Runbook to automatically recover from application crashes and unexpected failure without interrupting your service or your well earned sleep!.
Gunnery and Runbook belong to "Remote Server Task Execution" category of the tech stack.
Some of the features offered by Gunnery are:
- Support for wide variety of tools
- Designed for distributed systems
- Usable for deployment, service control, backups
On the other hand, Runbook provides the following key features:
- Monitors are used to check the status of your environment. They can be webhooks that call to the Runbook RESTful API, they can be Datadog alerts, they can be ping requests. Or, you can setup our TCP custom port to validate connectivity.
- Reactions are automated tasks that are called when Monitors fail. It can be anything from starting or restarting servers on AWS, Digital Ocean, or elsewhere, to running a custom script or executing a command. You know, all the first things you try when you get a 4am wake-up call
- Integrated with the tools you use today: Heroku, Salt, Rackspace, DigitalOcean, Logentries
Gunnery and Runbook are both open source tools. It seems that Gunnery with 685 GitHub stars and 72 forks on GitHub has more adoption than Runbook with 193 GitHub stars and 55 GitHub forks.