Information Technology Reference
In-Depth Information
Visualization/management/etc.
Message gateway service
Registry
+
schema
repository
Monitor service
Archive
repository
Local
storage
Sensor-II
Transfer
&
control
protocol
Adaptor
Sensor-I
Other data
sources
FIGURE 4.4
Architecture of CGSV.
4.5.1.1.1
Unlike many existing monitor tools, the most signii cant characteristics of
the CGSV sensor is that the sensor is runtime coni gurable, which means
that the monitor metadata, such as each metric's switch, collection
frequency, and granularity, is able to be changed over runtime on demand;
for example, demanding to turn off all the resource monitoring metrics
except CPU load and also lowering down the information collecting
frequency to alleviate intrusiveness on some machines with heavy load.
For most of the existing monitoring tools, coni guration is preloaded at
startup, therefore the required action needs users to login on the monitor-
ing node, to shutdown the tool, to change the coni guration i le and start
the tool again. While in CGSV, this action only needs users to send a
command according to the protocol, the sensor will automatically change
the coni guration. The coni guration i le is also used in CGSV implemen-
tation, which is used for initialization and logging coni guration when
changes occur. In other words, this i le is a real-time hard-disk backup of
the sensor coni guration, and is read only at startup.
There are two main types of sensors, called Sensor-I and Sensor-II, in
CGSV. The difference between the two types is their function and
deployment location. For corresponding components in GMA, Sensor-I
is the producer and Sensor-II can be treated as the re-publisher. Sensor-I
is deployed on computational resources, and is responsible for collecting
resource information. Broadcast discovery and data transmission
between Sensor-Is are performed via UDP packets with the specii c
Collection Layer
 
Search WWH ::




Custom Search