LATEST INTELLIGENCE
Device Health Monitoring
Monitor for continuous critical events
Identify when a device is unintentionally rebooted
Identify devices in need of a reboot
Monitor for offline endpoints
Monitor for hardware changes
Monitor for prolonged high CPU usage
Condition : Critical Events Threshold : 80 critical events over 5 minutes Action : Ticket and investigate
Condition : Windows Event Event Source : Microsoft-Windows-Kernel-Power Event ID : 41 Note : This condition is better suited for servers as workstations and laptops can create this error from user intervention . Action : Ticket and investigate
Condition : System Uptime Threshold recommendation : 30 or 60 days Action : Restart the device during an appropriate window . Automated remediation may work for workstations .
Condition : Device Down Threshold recommendation : – 10 minutes or less ( servers ) – 5 days or longer ( workstations ) Action : – Ticket and investigate – Wake-on-lan ( servers only )
Activity : System Name : Adapter added / changed , CPU added / removed , Disk drive added / removed , Memory added / removed Action : Ticket and investigate
Condition : CPU Threshold : 90 % or greater to reduce noise , with 95 %+ also being common over a 15 minute or greater period Action : Ticket and investigate concrete while others may require a small amount of customization to fit them to your use case .
These monitoring ideas are obviously not exhaustive , and may not apply to every situation or circumstance . Once you ’ ve gotten started building out your monitoring around these suggestions , you ’ ll need to develop a more customized and robust monitoring strategy specific to your clients and their needs . We end this guide with additional recommendations to help with that effort and make monitoring , alerting , and ticketing a competitive advantage for your MSP . p
Download whitepapers free from www . intelligentcio . com / me / whitepapers /
www . intelligentcio . com INTELLIGENTCIO MIDDLE EAST 23