https://github.com/nmsa/tma-framework-m

Component M - Trustworthiness Monitoring & Assessment Framework
https://github.com/nmsa/tma-framework-m

measurements monitoring trustworthiness

Last synced: 4 months ago
JSON representation

Component M - Trustworthiness Monitoring & Assessment Framework

• Host: GitHub
• URL: https://github.com/nmsa/tma-framework-m
• Owner: nmsa
• License: apache-2.0
• Created: 2018-04-09T16:27:55.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2022-11-16T08:56:18.000Z (almost 3 years ago)
• Last Synced: 2024-04-17T18:01:36.303Z (over 1 year ago)
• Topics: measurements, monitoring, trustworthiness
• Language: Java
• Size: 7.36 MB
• Stars: 1
• Watchers: 5
• Forks: 5
• Open Issues: 6
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# Monitor Component @ TMA Framework

According to the [architecture of the TMA Framework](https://github.com/eubr-atmosphere/tma-framework/blob/master/architecture/diagrams/TMA-Platform_Architecture.jpg)

the `TMA_Monitor` component provides a generic interface that can be used by the probes installed in the different layers of the system to send data about the collected measurements and events. 

These data are then stored in the `TMA_Knowledge` component, where it will be available to be used in by the `TMA_Analyze`, `TMA_Planning`, and `TMA_Execute` components.

The monitoring interface receives data regarding a **broad range of components in a generic fashion**.

To use this interface, the protocol defined [here](https://github.com/eubr-atmosphere/tma-framework/blob/master/architecture/diagrams/TMA-M/TMA-M_sequence.jpg) must be followed, to assure the basic security properties in the data transmission (integrity and confidentiality). 

*![Monitor Usage Sequence Diagram](https://github.com/eubr-atmosphere/tma-framework/blob/master/architecture/diagrams/TMA-M/TMA-M_sequence.jpg) Sequence diagram for the usage of the monitor component.*

Each probe starts its activity with an authentication synchronous message, in which it will receive is `probeId` and the token to use in the ensuing messages. 

All communication is performed over SSL sockets.

Each of the post observations interactions is an asynchronous message, which includes the obtained token in the headers. 

The messages format allows to aggregate multiple metrics and observations before sending, to avoid the communication overhead.

## TMA Monitor Message Format

The messages to be submitted to the `TMA_Monitor` follow the `JSON` schema specified in [tma-m_schema](interface/atmosphere_tma-m_schema.json), which is currently in the version `0.3`.

The [figure below](interface/atmosphere_tma-m_schema.png)  presents a representation of this schema, which is also explained below. 

*![Monitor Schema](interface/atmosphere_tma-m_schema.png)Format of the data to be provided to the monitor component.*

Each message includes:

* `probeId` -- obtained during authentication

* `resourceId` -- identifies the resource that is the subject of the attached data

* `messageId` -- control information 

* `sentTime` -- control information 

* `data` -- an array of objects, each one including: 

	* `type` -- event or measurement

	* `descriptionId` -- identifies the event or measurement, and an array of 

	* `observations` -- each one is a pair of 

		* `time` -- at which the specific observation was performed

		* `value` -- the observerd value which can be 0 in the case of `event`.

## TMA Monitor Server

Documentation is available at [development](development) and [server](development/server).

## TMA Monitor Client libraries

Documentation is available at [development](development), [libraries](development/libraries) and [probes](development/probes).