Scapegoat: An Adaptive Monitoring Framework for Component-Based Systems

Abstract

Abstract-Modern component frameworks support continuous deployment and simultaneous execution of multiple software components on top of the same virtual machine. However, isolation between the various components is limited. A faulty version of any one of the software components can compromise the whole system by consuming all available resources. In this paper, we address the problem of efficiently identifying faulty software components running simultaneously in a single virtual machine. Current solutions that perform permanent and extensive monitoring to detect anomalies induce high overhead on the system, and can, by themselves, make the system unstable. In this paper we present an optimistic adaptive monitoring system to determine the faulty components of an application. Suspected components are finely instrumented for deeper analysis by the monitoring system, but only when required. Unsuspected components are left untouched and execute normally. Thus, we perform localized just-in-time monitoring that decreases the accumulated overhead of the monitoring system. We evaluate our approach against a state-of-the-art monitoring system and show that our technique correctly detects faulty components, while reducing overhead by an average of 80%.

ScapeGoat: Spotting abnormal resource usage in component-based reconfigurable software systems

“…There exists more than one technology to monitor the property and they produce different performance overhead on the application execution. For instance, in our framework we provide lightweight global monitoring based on the Java Management API 13 , and a more heavy monitoring method based on bytecode instrumentation.…”

“…An early version of the Scapegoat monitoring framework is presented in [13]. This paper introduces four new majors contributions:…”

“…In [13], memory monitoring cannot be turned off. As a consequence, the probes used to account for memory consumption are always activated.…”

“…• In addition to the experiments proposed in [13], a new use case is used to evaluate the monitoring framework.…”