{"_id":"55d3b64af77e6d0d00b1b29f","parentDoc":null,"__v":23,"user":"55c50f4a7c199a2f00665cbf","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"},"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"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-08-10T23:07:38.599Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"## What is a Trigger?\nNeptune is a typical event driven system. You can create RULES to connect a TRIGGER to an ACTION. Neptune accepts various forms of triggers as mentioned below. A single trigger can be used in multiple rules as well.\n\n## What triggers are supported?\n\n1. **[Monitoring tool triggers](doc:monitoring-tool-triggers) :** We have direct integration with several popular monitoring tools and we are adding more to the list. e.g : NewRelic, Datadog, Pingdom, Pagerduty and more (See integration guides on your left). \n    \n2. **[Webhooks](doc:webhook-triggers) :** You get a Neptune endpoint, which can be called from any monitoring tool or manually from a command-line. Whenever the webhook is called, we treat it as trigger, and all rules using the webhook trigger will be executed \n    \n3. **[Cron-triggers](doc:cron-triggers) : **  Neptune supports simple cron expressions to schedule actions. At the specified time, Neptune will generate an internal trigger, and the rules using the trigger will get executed. Since we support actions on a single host or a cluster of hosts, you essentially get a **distributed-cron service**\n    \n## Neptune trigger intelligence \nOur deep integration with both monitoring and alerting tools lends us unique advantages. We can intelligently understand the trigger, so that we deliver richer context and diagnostics around the alert. We also let you run actions on right set of trigger hosts without even logging in. He is a glimpse of what we understand better : \n\n* More information around the trigger host, host group, host tags, etc\n* Alert severity levels\n* Alert metrics, and associated graph snapshots when alert triggers\n* Dynamic application information to determine right set of hosts to act on\n* Two-way integration with some monitoring tools allows us to feed back action details to suppress or resolve the alerts.","excerpt":"","slug":"triggers-overview","type":"basic","title":"Overview"}
## What is a Trigger? Neptune is a typical event driven system. You can create RULES to connect a TRIGGER to an ACTION. Neptune accepts various forms of triggers as mentioned below. A single trigger can be used in multiple rules as well. ## What triggers are supported? 1. **[Monitoring tool triggers](doc:monitoring-tool-triggers) :** We have direct integration with several popular monitoring tools and we are adding more to the list. e.g : NewRelic, Datadog, Pingdom, Pagerduty and more (See integration guides on your left). 2. **[Webhooks](doc:webhook-triggers) :** You get a Neptune endpoint, which can be called from any monitoring tool or manually from a command-line. Whenever the webhook is called, we treat it as trigger, and all rules using the webhook trigger will be executed 3. **[Cron-triggers](doc:cron-triggers) : ** Neptune supports simple cron expressions to schedule actions. At the specified time, Neptune will generate an internal trigger, and the rules using the trigger will get executed. Since we support actions on a single host or a cluster of hosts, you essentially get a **distributed-cron service** ## Neptune trigger intelligence Our deep integration with both monitoring and alerting tools lends us unique advantages. We can intelligently understand the trigger, so that we deliver richer context and diagnostics around the alert. We also let you run actions on right set of trigger hosts without even logging in. He is a glimpse of what we understand better : * More information around the trigger host, host group, host tags, etc * Alert severity levels * Alert metrics, and associated graph snapshots when alert triggers * Dynamic application information to determine right set of hosts to act on * Two-way integration with some monitoring tools allows us to feed back action details to suppress or resolve the alerts.