User Tools
snc_heartbeat_alert_handling
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
snc_heartbeat_alert_handling [2017/02/07 19:08] jackson created |
snc_heartbeat_alert_handling [2020/12/17 14:16] (current) paul |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Heartbeat Alerts ====== | ====== Heartbeat Alerts ====== | ||
| + | <WRAP round important> | ||
| + | Observer and this feature have been deprecated. Please contact support@perspectium.com for information. | ||
| + | </WRAP> | ||
| + | |||
| ===== What is the Heartbeat ===== | ===== What is the Heartbeat ===== | ||
| - | The Agent will send a heartbeat to MBS every minute in order to report its version and that it is currently alive. Within our system we will then create Alerts if the heartbeat is stale (ie your Agent hasn't reported one soon enough). Using these Alerts and the native ServiceNow Replicator and Observer capabilities you can process and fire notifications. Using these alerts you can also configure your own custom workflows. | + | The Replicator Agent will send a heartbeat to MBS every minute in order to report its version and that it is currently alive. Within our system we will then create Alerts if the heartbeat is stale (i.e. your Agent hasn't reported one recently enough). Using these Alerts and the ServiceNow Replicator and Observer capabilities you can process and fire notifications. |
| + | |||
| + | Using these alerts you can also configure your own custom workflows. | ||
| + | |||
| + | You can also generate these alerts entirely through MBS and your portal, independent of ServiceNow. To do so you can read more [[observer_heartbeat_alert_handling|here]]. | ||
| ===== How to Receive these Alerts ===== | ===== How to Receive these Alerts ===== | ||
| These alerts are placed into a queue based on your current Agent name. Your Agent name inputed on installation, and can be found by navigating to the //wrapper.conf// file and finding the entry for //wrapper.name//. | These alerts are placed into a queue based on your current Agent name. Your Agent name inputed on installation, and can be found by navigating to the //wrapper.conf// file and finding the entry for //wrapper.name//. | ||
| - | If you named your Agent //company_agent// you will create a Subscribe Queue to **psp.out.servicenow.company_agent** | + | If you named your Agent **company_agent** you will create a Subscribe Queue to **psp.out.servicenow.company_agent** |
| By doing so you will pull in the generated Alerts and they will automatically be placed into the Alert table, if you have Observer. These Alerts can be found here: | By doing so you will pull in the generated Alerts and they will automatically be placed into the Alert table, if you have Observer. These Alerts can be found here: | ||
| Line 27: | Line 35: | ||
| {{::Heartbeat_Email.png|}} | {{::Heartbeat_Email.png|}} | ||
| - | Then you can insert this record, which you can also find in the Notifications table within ServiceNow. | + | Then you can save this record. This record will be pulled up by the Error Notification module unless you rename it, in which case you can find it in the ServiceNow notifications table. |
snc_heartbeat_alert_handling.1486523330.txt.gz · Last modified: 2017/02/07 19:08 by jackson
Page Tools
