From 0bd926fb305c8cd086d837d465277a3a4dd1e75c Mon Sep 17 00:00:00 2001 From: Michael Boniface <mjb@it-innovation.soton.ac.uk> Date: Wed, 11 Apr 2018 12:32:29 +0000 Subject: [PATCH] Update clmc-information-model.md --- docs/clmc-information-model.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/clmc-information-model.md b/docs/clmc-information-model.md index 0e8d61a..46ffb27 100644 --- a/docs/clmc-information-model.md +++ b/docs/clmc-information-model.md @@ -55,8 +55,6 @@ The diagram highlights the need to monitor three views on an endpoint: network, Not all information acquired will be aggregated and stored within the CLMC. The CLMC is not responsible for capturing every measurement point related to transferring bytes over the network. It's also not responsible for capturing every interaction between a user and a service. The key design principle is to acquire information from one context that can be used in another context. For example, instead of recording every service interaction an aggregate service usage metric (e.g. request rate/s) would be acquired and stored, and the similar aggregation would be needed for infrastructure monitoring. - - ### Configuration Configuration information describes the structure and state of the system over time. Each configuration item has a lifecycle that defines configuration states and events that cause a transition between states. The following table gives examples of configuration items and states. -- GitLab