Event Management Self Health MonitoringSummaryEvent Management Self Health Monitoring explained Related LinksAll the self-monitoring configurations are defined in the below table: em_monitor_conf https://<your-instance>.service-now.com.service-now.com/em_monitor_conf_list.do "Connectors Status" is responsible for generating events for every 60 secs when the Connector status changes https://<your-instance>.service-now.com/em_monitor_conf.do?sys_id=fc37c59493180300404c74aff67ffb6d In the "Connectors Status" definition, we call "connectors monitor" script which in-turns calls the script include: EvtMgmtHealthMonitorCommon https://<your-instance>.service-now.com/em_monitor_scripts.do?sys_id=bc76508993980300404c74aff67ffbf8&sysparm_view= EvtMgmtHealthMonitorCommon: https://<your-instance>.service-now.com/nav_to.do?uri=%2Fsys_script_include.do%3Fsys_id%3D9a3b752793000300bde576df067ffb6e In the script include we generate a message key, from below code //Will be used by the event/alert generatorgetMessageKey: function(mntrCnfgSysId, mntrConfgGlideRecord, mntrStateSysId, mntrStateGlideRecord) {//If found state- bind to itvar stateGr = this.getGlideRecord(mntrStateSysId, mntrStateGlideRecord, "em_monitor_state");if (stateGr) {return stateGr.sys_id;} else {return "";//use default message_key Going into the "em_monitor_state" table, we can see there are different Monitoring states, these monitoring states will create message keys for the connectors defined. Based on the message key generated the event gets generated.