{"__v":8,"_id":"55d3b645f77e6d0d00b1b280","category":{"__v":1,"_id":"55d3b645f77e6d0d00b1b277","pages":["55d3b645f77e6d0d00b1b27e","55d3b645f77e6d0d00b1b27f","55d3b645f77e6d0d00b1b280","55d3b645f77e6d0d00b1b281","55d3b645f77e6d0d00b1b282"],"project":"55c505b41469ad2500fa2ab7","version":"55d3b644f77e6d0d00b1b273","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-08-10T18:44:21.139Z","from_sync":false,"order":4,"slug":"actions","title":"Actions"},"parentDoc":null,"project":"55c505b41469ad2500fa2ab7","user":"55c50f4a7c199a2f00665cbf","version":{"__v":6,"_id":"55d3b644f77e6d0d00b1b273","project":"55c505b41469ad2500fa2ab7","createdAt":"2015-08-18T22:48:36.632Z","releaseDate":"2015-08-18T22:48:36.632Z","categories":["55d3b645f77e6d0d00b1b274","55d3b645f77e6d0d00b1b275","55d3b645f77e6d0d00b1b276","55d3b645f77e6d0d00b1b277","55d3b645f77e6d0d00b1b278","55d3b645f77e6d0d00b1b279","55d3b645f77e6d0d00b1b27a","55d3b645f77e6d0d00b1b27b","55d3b645f77e6d0d00b1b27c","55d3b645f77e6d0d00b1b27d","55d7c2939510f00d007ec6fe","56fac9925df15a20002972a2","56fb2f7668e1d30e00a0b672","583498d411e8af2500f6b334","58e52a180ab7b03b00f4a97a"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.1.0","version":"1.1"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-08-10T23:08:36.230Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":2,"body":"Executing a runbook is probably the most widely used action by Devops. Ops fixes/investigates most of the production issues by running the commands or instructions present in a pre-existing runbook.\n\nYou can use EXECUTE_RUNBOOK action on Neptune to either gather diagnostics or to take remediation actions when an alert is raised. Neptune captures the output spit by the runbook and keeps it available for you at your disposal. So, you can even write commands like getting most recent logs also in your runbooks.\n\nThere are different variants of runbook actions that Neptune supports.\n * Executing runbook on a single host\n * Executing runbook on all of the hosts in host group/tag\n * Executing runbook on only one host in a host group/tag\n\nYou can also manage your runbooks on Neptune platform and reuse runbooks across the rules.\n\nPlease see [Private Github runbooks](doc:private-github-runbooks) section to see details on how to manage your runbooks on Github and use in neptune. You can also reuse the community runbooks provided by Neptune. Please see [Overview](doc:runbooks-overview) for more details.","excerpt":"","slug":"runbook-actions","type":"basic","title":"Runbook Actions"}
Executing a runbook is probably the most widely used action by Devops. Ops fixes/investigates most of the production issues by running the commands or instructions present in a pre-existing runbook. You can use EXECUTE_RUNBOOK action on Neptune to either gather diagnostics or to take remediation actions when an alert is raised. Neptune captures the output spit by the runbook and keeps it available for you at your disposal. So, you can even write commands like getting most recent logs also in your runbooks. There are different variants of runbook actions that Neptune supports. * Executing runbook on a single host * Executing runbook on all of the hosts in host group/tag * Executing runbook on only one host in a host group/tag You can also manage your runbooks on Neptune platform and reuse runbooks across the rules. Please see [Private Github runbooks](doc:private-github-runbooks) section to see details on how to manage your runbooks on Github and use in neptune. You can also reuse the community runbooks provided by Neptune. Please see [Overview](doc:runbooks-overview) for more details.