{"__v":76,"_id":"55d3b649f77e6d0d00b1b29c","category":{"__v":2,"_id":"55d3b645f77e6d0d00b1b274","pages":["55d3b649f77e6d0d00b1b29c","55e7b3e86f626a0d0084ae05"],"project":"55c505b41469ad2500fa2ab7","version":"55d3b644f77e6d0d00b1b273","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-08-11T00:52:57.334Z","from_sync":false,"order":0,"slug":"overview","title":"Overview"},"parentDoc":null,"project":"55c505b41469ad2500fa2ab7","user":"55c505857c199a2f00665c83","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":["55da58cbb29f250d005c9073","55e49d8c830ec32300e1a38d"],"next":{"pages":[],"description":""},"createdAt":"2015-08-07T19:23:35.670Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"** Neptune provides remediation-as-a-service for all your cloud and on-premise servers**. It integrates with your existing monitoring tools like NewRelic, Nagios, Pingdom etc. to automatically run diagnostic or remediation actions in response to an alert. Think of it as **If this then that** for DevOps. Simply put, you can create RULES to tie a TRIGGER to an ACTION.\n\n** Triggers can be : **\n1. Alerts from your existing monitoring tools or PagerDuty\n2. Webhooks\n3. Cron-triggers\n\n**Actions can be : **\n1. Making API calls to your cloud provider (Scale up/down, Restart etc)\n2. Executing simple remediation shell scripts on a single or cluster of hosts\n3. Collecting graph snapshots of health metrics and logs relevant for an alert\n4. Collecting health status details of your micro-services & stack components\n\n## So What can you accomplish with Neptune ?\n\n**Automate your incident response** : Instead of waking up at midnight to manually fix an  alert, you can automatically run either a diagnostic or remediation action with Neptune. Choose one of the three models of automation : \n\n1. **Auto-diagnostics :**  For those uncertain alerts requiring manual intervention, automatically collect relevant diagnostics ( graph snapshots, logs, micro-service health statuses) so that you get a detailed incident report and you can fix the issue in minutes instead of hours\n2. **Auto-fix-it :** For those commonly occurring alerts,automatically execute your runbook (simple shell scripts) on a single or cluster of hosts\n3. **Email runbook :** Even if you don't want to execute any action automatically, you can codify  your troubleshooting steps in a runbook and email it automatically to your on-call engineer\n\n**Streamline your IT operations**\n1. **One-stop incident dashboard :** See all your alerts from various monitoring tools in one place, and fix the incidents without logging in to hosts that trigger the alerts\n2.  **Alert statistics & analytics :** Easily understand which are the most frequently occurring alerts and which are the most damaging alerts (higher MTTR).You can then apply 80-20 rule to automate the top 20 alerts and you can sleep 80% of the time\n\n**Event-driven automation** : You can go creative by leveraging the simple **trigger-action** platform to automate several of you daily tasks and infrastructure components\n1. **Auto-scale** your infrastructure on **any cloud** based on custom triggers\n2. Using webhooks and cron-triggers, you can **act on a cluster of hosts at once**\n3. Scale your AWS resources (dynamoDB etc) based on **throughput alarms**\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/abp3r7zISYutQxaHZF1W_Screen%20Shot%202015-08-10%20at%207.44.36%20PM.png\",\n        \"Screen Shot 2015-08-10 at 7.44.36 PM.png\",\n        \"895\",\n        \"364\",\n        \"#960c4c\",\n        \"\"\n      ],\n      \"caption\": \"Neptune.io architecture\"\n    }\n  ]\n}\n[/block]\n \n## How it works :  A highly reliable & scalable event driven architecture\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Start your automation journey now, so that you don't  wake up at midnight for another dumb alert.\",\n  \"body\": \"[Get started](doc:integrate-monitoring-tools)\"\n}\n[/block]","excerpt":"","slug":"neptuneio-overview","type":"basic","title":"Overview"}
** Neptune provides remediation-as-a-service for all your cloud and on-premise servers**. It integrates with your existing monitoring tools like NewRelic, Nagios, Pingdom etc. to automatically run diagnostic or remediation actions in response to an alert. Think of it as **If this then that** for DevOps. Simply put, you can create RULES to tie a TRIGGER to an ACTION. ** Triggers can be : ** 1. Alerts from your existing monitoring tools or PagerDuty 2. Webhooks 3. Cron-triggers **Actions can be : ** 1. Making API calls to your cloud provider (Scale up/down, Restart etc) 2. Executing simple remediation shell scripts on a single or cluster of hosts 3. Collecting graph snapshots of health metrics and logs relevant for an alert 4. Collecting health status details of your micro-services & stack components ## So What can you accomplish with Neptune ? **Automate your incident response** : Instead of waking up at midnight to manually fix an alert, you can automatically run either a diagnostic or remediation action with Neptune. Choose one of the three models of automation : 1. **Auto-diagnostics :** For those uncertain alerts requiring manual intervention, automatically collect relevant diagnostics ( graph snapshots, logs, micro-service health statuses) so that you get a detailed incident report and you can fix the issue in minutes instead of hours 2. **Auto-fix-it :** For those commonly occurring alerts,automatically execute your runbook (simple shell scripts) on a single or cluster of hosts 3. **Email runbook :** Even if you don't want to execute any action automatically, you can codify your troubleshooting steps in a runbook and email it automatically to your on-call engineer **Streamline your IT operations** 1. **One-stop incident dashboard :** See all your alerts from various monitoring tools in one place, and fix the incidents without logging in to hosts that trigger the alerts 2. **Alert statistics & analytics :** Easily understand which are the most frequently occurring alerts and which are the most damaging alerts (higher MTTR).You can then apply 80-20 rule to automate the top 20 alerts and you can sleep 80% of the time **Event-driven automation** : You can go creative by leveraging the simple **trigger-action** platform to automate several of you daily tasks and infrastructure components 1. **Auto-scale** your infrastructure on **any cloud** based on custom triggers 2. Using webhooks and cron-triggers, you can **act on a cluster of hosts at once** 3. Scale your AWS resources (dynamoDB etc) based on **throughput alarms** [block:image] { "images": [ { "image": [ "https://files.readme.io/abp3r7zISYutQxaHZF1W_Screen%20Shot%202015-08-10%20at%207.44.36%20PM.png", "Screen Shot 2015-08-10 at 7.44.36 PM.png", "895", "364", "#960c4c", "" ], "caption": "Neptune.io architecture" } ] } [/block] ## How it works : A highly reliable & scalable event driven architecture [block:callout] { "type": "success", "title": "Start your automation journey now, so that you don't wake up at midnight for another dumb alert.", "body": "[Get started](doc:integrate-monitoring-tools)" } [/block]