Monitoring
The Mu Platform provides an extensive set of monitors that allow the tester to define service-specific fault conditions. The Mu Platform automatically correlates the faults triggered by the monitors to accurately pin-point the test case that caused the failure.
Service-level monitors allow the testers to monitor the health of one or more services directly by executing synthetic transactions against them. This allow the Mu Platform chart in real-time, the failures and service-degradation caused by tests executed against the service. All of the protocols that are part of the Mu Content can be leveraged as service-level monitors. System-level monitors identify root cause failures by actively logging into the systems that are running the service and executing various user-defined commands.
The following the various monitor available on the Mu Platform:
|
|
Execute commands on a host and use the output to identify possible failures or faults occurring on the Target. The command monitor allow the tester to grep log files, look for process restarts, existence of core files, etc. while the tests are executed.
|
|
|
Passively monitor output generated from a terminal server or a serial console. The console monitor is typically used when the Target is an embedded device without a login shell.
|
|
|
Monitor the expected frequency associated with an input line on an I/O device. The Digital IO monitor uses the Ontrak ADU200 and ADU208 DAQ's (Data Acquisition Module) to measure the % tolerance of variation from the expected frequency. These monitors are used when testing devices like Programmable Logic Controllers (PLC's) which are extensively used in SCADA networks.
|
|
|
Remote log monitors allow the tester to tail log output of one or more processes to look for patterns that indicate a fault condition.
|
|
|
SNMP monitors allow the tester to periodically track of one or more MIB entities on a system to look for counters and gauges that might indicate fault conditions. These monitors are used to correlate CPU load, memory usage, interface packet counters, etc. to detect fault conditions.
|
|
|
Syslog monitors allows the tester to monitor the content of syslog messages sent from the Target to the Mu platform.
|
|
