Clubspeed Self Healing Overview
Clubspeed Self Healing Overview
This document is going to go over the background overview, roll out, and response for Clubspeed self-healing.
TABLE OF CONTENTS
Background
To lower the customer system and feature downtime and support load imposed by issues with services key to Club Speed functionality, we are utilizing LogMeIn Alerts, One To Many, and Self Healing features to monitor Club Speed controller statuses and numerous windows services that Club Speed utilizes.
Roll out
- Current active monitoring with alerts:
- Sustained CPU usage at a certain threshold for a certain time period
- Sustained RAM usage at a certain threshold for a certain time period
- System downtime alert after a certain time period
- ClubspeedV8 MDF file size alerts after reaching a certain size limit
- System free storage space after hitting a minimum threshold in GB’s
- Current active alerts with self-healing tasks:
- Start MSSQLSERVER service if stopped
- Start SMTPSVC service if stopped
- Start TSGateway service if stopped
When one of these alerts is triggered it lists an alert log in LogMeIn as well as sending an email alert that is tied to a Slack channel, named logmein-alerts and logmein-alerts-critical, to notify support staff of an issue.
Alerts in the logmein-alerts-critical channel should be responded to right away as these alerts are as if a server-down call has come in.