Personal tools
You are here: Home Knowledge Model REPOSITORY of Terms I Invasiveness of the Monitoring Architecture

Invasiveness of the Monitoring Architecture

by Raman Kazhamiakin last modified Apr 26, 2012 22:25
— filed under:

Definitions

Term:
Invasiveness of the Monitoring Architecture
Domain: Cross-cutting issues
Engineering and Design
(KM-ED)
Adaptation and Monitoring
(KM-AM)
Quality Definition, Negotiation and Assurance
(KM-QA)
Generic
(domain independent)
D
o
m
a
i
n
:
L
a
y
e
r
s

Business Process Management
(KM-BPM)




Service Composition and Coordination
(KM-SC)




Service Infrastructure
(KM-SI)

Invasive monitoring takes place within the bounds of a Grid or Grid component.  Non-invasive monitoring observes the behaviour of a Grid or Grid component from outside its administrative boundary. [Coghlan, 2002] [PO-JRA-2.3.1] [PO-JRA-1.2.1]

Generic
(domain independent)

A characteristic of the monitoring framework from the perspective of how tightly it is integrated with the monitoring subject. We distinguish between the cases, when the monitoring facilities are integrated with the subject, the cases, when the monitoring facilities are integrated with the platform, where the subject operates, and the cases, when the monitoring facilities are completely separated and independent from the subject of monitoring. [CD-JRA-1.2.2]

Placement of the execution of the monitoring code. The monitoring code can perform an inline check, i.e., the monitoring code is embedded in the target code (including calls to subroutines). In this case, the monitor uses the resources of the monitored program. On the other hand, the monitoring can be performed offline meaning that the monitor executes as a separate thread or process, possibly on a separate machine. [Delgado, 2004]


 

References

 

Document Actions
  • Send this
  • Print this
  • Bookmarks

The Plone® CMS — Open Source Content Management System is © 2000-2017 by the Plone Foundation et al.