Creating first version of metrico (!1) · Merge requests · OSL / code / org.etsi.osl.metrico

.settings/org.eclipse.core.resources.prefs

0 → 100644

+6 −0

Changes for .settings/org.eclipse.core.resources.prefs: 6 added lines, 0 removed lines.
Original line number	Diff line number	Diff line
		eclipse.preferences.version=1
		encoding//src/main/java=utf-8
		encoding//src/main/resources=utf-8
		encoding//src/test/java=utf-8
		encoding//src/test/resources=utf-8
		encoding/<project>=UTF-8

0 → 100644

+4 −0

Changes for .settings/org.eclipse.jdt.apt.core.prefs: 4 added lines, 0 removed lines.
Original line number	Diff line number	Diff line
		eclipse.preferences.version=1
		org.eclipse.jdt.apt.aptEnabled=true
		org.eclipse.jdt.apt.genSrcDir=target/generated-sources/annotations
		org.eclipse.jdt.apt.genTestSrcDir=target/generated-test-sources/test-annotations

0 → 100644

+9 −0

Changes for .settings/org.eclipse.jdt.core.prefs: 9 added lines, 0 removed lines.
Original line number	Diff line number	Diff line
		eclipse.preferences.version=1
		org.eclipse.jdt.core.compiler.codegen.targetPlatform=17
		org.eclipse.jdt.core.compiler.compliance=17
		org.eclipse.jdt.core.compiler.problem.enablePreviewFeatures=disabled
		org.eclipse.jdt.core.compiler.problem.forbiddenReference=warning
		org.eclipse.jdt.core.compiler.problem.reportPreviewFeatures=ignore
		org.eclipse.jdt.core.compiler.processAnnotations=enabled
		org.eclipse.jdt.core.compiler.release=disabled
		org.eclipse.jdt.core.compiler.source=17

0 → 100644

+4 −0

Changes for .settings/org.eclipse.m2e.core.prefs: 4 added lines, 0 removed lines.
Original line number	Diff line number	Diff line
		activeProfiles=
		eclipse.preferences.version=1
		resolveWorkspaceProjects=true
		version=1

0 → 100644

+23 −0

Changes for Documentation/Documentation.md: 23 added lines, 0 removed lines.
Original line number	Diff line number	Diff line
		# 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.

		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?
		* What mechanisms are trigered to perform actions based on the data recieved?

		Most of the above challenges can be split in further tecnhical and technology challenges.

		## 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.

		![METRICOInANutshell](https://labs.etsi.org/rep/groups/osl/code/-/uploads/085c07b57f24ee97251ccfd95c25dd01/NewFeatureInANutshell.png)