Monitoring Timeliness
by
Raman Kazhamiakin
—
last modified
Apr 26, 2012 11:25
—
filed under:
KnowledgeModel
Definitions
| Term: Monitoring Timeliness |
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) |
Monitoring data is considered timely, or
fresh, if, at a given point in time if it is synchronized with
the real-world value at the Grid site or component (that is, both values
are the same) [Zanikolas, 2008] |
||||
| Generic (domain independent) |
Monitoring timeliness (timing) is the characteristic
of the time difference between the moment, when the event actually
takes place, and the moment it is reported by the monitor. In these
regards, one can distinguish between reactive monitoring
approaches, which aim to report events as soon as it is possible,
post-mortem approaches, which report information considerably
after the events (or even series of events) take place, and
predictive approaches that try to predict the occurrence of
events. [CD-JRA-1.2.2] |
||||
Competencies
- N/A
References
- [CD-JRA-1.2.2] Taxonomy of adaptation principles and mechanisms.
- [Zanikolas, 2008] S. Zanikolas and R. Sakellariou. An
Importance-Aware Architecture for Large-Scale Grid Information
Services. Parallel Processing Letters, 18(3):347–370, July 2008.
