\u00a0<\/p>
Latency Threshold<\/b> \u2013 I would say to start with 50-60 Seconds to avoid any false positives.<\/p>
Failure Counter threshold<\/b> –\u00a0 I would suggest to start with 5-6 for the same reasons.<\/p>
Admin Notifications<\/b> \u2013 I would suggest to notify via SMS as well, in case email is down. But if you are doing that, you will firstly have to make sure you are syncing the Mobile numbers from AD using the correct AD Attribute in Mimecast(https:\/\/community.mimecast.com\/docs\/DOC-1478<\/a>). Then you also have to make sure that you set that attribute up to be used as the mobile attribute for SMS notifications in Administration > Account > Account Settings > System Notification Options. Then, you also have to make sure that the admins that need these SMS notifications, subscribe to them. Guidance on subscribing here – https:\/\/community.mimecast.com\/docs\/DOC-2085<\/a>. Further details on using SMS in Continuity Here – https:\/\/community.mimecast.com\/docs\/DOC-2104<\/a>.<\/p> Affected Group<\/b> \u2013 You have to select a group that covers all users. Otherwise when you get the notification, if you opt to start a Continuity Event from the dashboard, it will only affect the Admin group you have selected.<\/p>","protected":false},"excerpt":{"rendered":" \u00a0Latency Threshold \u2013 I would say to start with 50-60 Seconds to avoid any false positives.Failure Counter threshold –\u00a0 I would suggest to start with 5-6 for […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[3023,3024,1797],"class_list":["post-4242","post","type-post","status-publish","format-standard","hentry","category-research","tag-continuity","tag-continuity-event-monitor","tag-mimecast"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t