What is Runbook?
Why developers like Runbook?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Runbook in their tech stack.
We eat our own dog food and use our own service to monitor itself. We have reactions setup to restart nginx, rethinkdb, redis, our app and even our servers if it comes down to it. All automagically. Oh, we don't have an on call setup. Runbook takes care of that for us. Runbook
- 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