diff --git a/Documentation.md b/Documentation.md index ce56dc47ae7baf45125d35e49bd5373a1a10c559..34eb57ab996b0cead8f1f447af7eb19af1f8a605 100644 --- a/Documentation.md +++ b/Documentation.md @@ -1,13 +1,13 @@ -# Metrics Collector System (METCO) +# Metrics Component (METRICO) ## Definitions of the problem -Services (& resources) created through OSL provide a vast amount of data and metrics. The data can be used to perform actions on the said services. Up until now (OSL v1.0) external tools are used to leverage those data. - +Services (& resources) created through OSL provide a vast amount of data and metrics. The data can be used to perform actions on the said services. Up until now (OSL v1.0) external tools are used to leverage those data. -The goal of this feature is to create a mechanism that, through OSL, can retrieve the data and return them to the services (and/or resources) they are associated with. +The goal of this feature is to create a mechanism that, through OSL, can retrieve the data and return them to the services (and/or resources) they are associated with. This goal creates challenges on multiple levels: + * How does OSL retrieves data that come from multiple, non-homogenous environments? * How does OSL associates the data with their respective services? * How the services receive the data that were retrieved by the MDAS? @@ -17,8 +17,7 @@ Most of the above challenges can be split in further tecnhical and technology ch ## High Level Design +* METRICO enables users to retrieve metrics monitored via a Prometheus. +* The infrastructure has to be monitored with any monitoring tool that has a Prometheus exporter and will export the collected data to a Prometheus. -## Tools used - - - +