This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
snc_heartbeat_alert_handling [2017/02/07 19:37] jackson |
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 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. | 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. | 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 ===== |