Component Tests Sample Clauses

Component Tests. Monitoring of Device hardware or software components are performed every eight (8) minutes. Component tests are performed using the most appropriate polling technology as defined by Bright Bear engineering staff. Each component test is performed comparing the result of the poll to specific threshold values defined in the Monitoring system. Example components are as follows: • CPU • Hard drives • Power supplies • Service status If the component test reports success, the component is considered to be fully available. No alert will be sent. If the component test fails, reports an unknown condition, reports a degraded condition, or reports a down condition, the component is considered to be in a troubled state. An alert will be sent to Bright Bear and/or to an e-mail contact defined by Customer after a predefined consecutive number of occurrences of the error condition, which varies by condition. In addition to basic up/down Monitoring, Devices are Monitored for the following conditions (where applicable). • Latency below committed rates • Packet Loss 1% as long as below committed rates Servers are monitored for the following conditions: • Server Off Line • Disk Utilization o Warning: 90% o Critical: 95% • AutoService Stop – if a Service is set to automatically start and is in a stopped state • Processor/Memory statistics that exceed thresholds o Warning: 75% sustained o Critical: 85% sustained • Any specific Monitors requested because the server is mission critical • This does not include Windows Event Logs, Security Event/Auditing Logs, etc. Additional custom Monitors are available upon request and may incur an additional charge for engineering and setup.