{"_id":"55d3b64af77e6d0d00b1b2a0","user":"55c50f4a7c199a2f00665cbf","__v":37,"parentDoc":null,"category":{"_id":"55d3b645f77e6d0d00b1b276","version":"55d3b644f77e6d0d00b1b273","__v":1,"project":"55c505b41469ad2500fa2ab7","pages":["55d3b64af77e6d0d00b1b29f","55d3b64af77e6d0d00b1b2a0","55d3b64af77e6d0d00b1b2a1","55d3b64af77e6d0d00b1b2a2"],"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-08-10T18:44:12.108Z","from_sync":false,"order":3,"slug":"triggers","title":"Triggers"},"project":"55c505b41469ad2500fa2ab7","version":{"_id":"55d3b644f77e6d0d00b1b273","project":"55c505b41469ad2500fa2ab7","__v":6,"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:07:51.876Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"Neptune has direct integration with several popular monitoring tools and adding more to the list every week. If you currently use a tool not in the supported list (See integration guides on your left), please reach out to <mailto:support:::at:::neptune.io>\n\n## Most integrations will involve two steps :\n1. Adding a Neptune webhook to your monitoring tool, so that Neptune gets a copy of the alert\n2. Adding your monitoring tool API keys in Neptune, so that we can query your monitoring tool for more details around the alert. (eg : Dynamic information about what all hosts are running a particular application when the alert triggers etc.)\n\n## Pagerduty users\n**IMPORTANT : ** If you are Pagerduty user, we recommend that you first integrate your Pagerduty account with Neptune and then integrate your specific monitoring tool. \n\n1. Pagerduty will be the alert source in this case and we automatically add our webhooks to all your services in pagerduty, so that Neptune gets a copy of the alert.\n2. You also need to integrate your monitoring tool with Neptune by adding API keys. This will allow Neptune to query your monitoring tools and gather dynamic contextual information around the alert. \n[block:callout]\n{\n  \"type\": \"danger\",\n  \"title\": \"Pagerduty users should NOT add a Neptune webhook in your monitoring tool\",\n  \"body\": \"Doing so will send two alerts to Neptune, one from pagerduty and other from your monitoring tool\"\n}\n[/block]\nPlease refer to [pagerduty integration guide](doc:pagerduty-integration) for more details\n\n## Non-pagerduty users\nIf you are a non-pagerduty user, then the alert source will be your monitoring tool, so :\n1. You need to add a Neptune webhook in your monitoring tool, so that Neptune gets a copy of the alert\n2. Add your monitoring tool API keys in Neptune, so that we can gather dynamic contextual information around the alert \n\nPlease refer to your monitoring tool integration guide in the left sidebar for detailed instructions on adding Neptune webhook to your monitoring tool and API keys in Neptune","excerpt":"","slug":"monitoring-tool-triggers","type":"basic","title":"Monitoring Tool Triggers"}

Monitoring Tool Triggers


Neptune has direct integration with several popular monitoring tools and adding more to the list every week. If you currently use a tool not in the supported list (See integration guides on your left), please reach out to <mailto:support@neptune.io> ## Most integrations will involve two steps : 1. Adding a Neptune webhook to your monitoring tool, so that Neptune gets a copy of the alert 2. Adding your monitoring tool API keys in Neptune, so that we can query your monitoring tool for more details around the alert. (eg : Dynamic information about what all hosts are running a particular application when the alert triggers etc.) ## Pagerduty users **IMPORTANT : ** If you are Pagerduty user, we recommend that you first integrate your Pagerduty account with Neptune and then integrate your specific monitoring tool. 1. Pagerduty will be the alert source in this case and we automatically add our webhooks to all your services in pagerduty, so that Neptune gets a copy of the alert. 2. You also need to integrate your monitoring tool with Neptune by adding API keys. This will allow Neptune to query your monitoring tools and gather dynamic contextual information around the alert. [block:callout] { "type": "danger", "title": "Pagerduty users should NOT add a Neptune webhook in your monitoring tool", "body": "Doing so will send two alerts to Neptune, one from pagerduty and other from your monitoring tool" } [/block] Please refer to [pagerduty integration guide](doc:pagerduty-integration) for more details ## Non-pagerduty users If you are a non-pagerduty user, then the alert source will be your monitoring tool, so : 1. You need to add a Neptune webhook in your monitoring tool, so that Neptune gets a copy of the alert 2. Add your monitoring tool API keys in Neptune, so that we can gather dynamic contextual information around the alert Please refer to your monitoring tool integration guide in the left sidebar for detailed instructions on adding Neptune webhook to your monitoring tool and API keys in Neptune