Monitoring Tool

 Coordinated by

The monitoring tool is an infrastructure in charge of setting up and managing a monitoring component. It is based on event messages and enables the collection of complex events.


Describe the innovation content of the result:
The monitoring tool is based on a Complex Event Processor that allows one to infer complex events from simple ones through a set of rules the user can set up.
The tool provides features related to the auto-generating rules during the execution, starting from a set of templates that will be instantiated at runtime according to the events observed. This feature, in conjunction with the digital twin, allows the execution of a conformity monitor to check if the real system behaves as the DT forecasted.
Another powerful feature is the integration of the monitoring. with the Ontology Manager that has been developed.
Who will be the customer?
Developers, Testers and Companies using ICT systems
What benefit will it bring to the customers?
The overall infrastructure provides tools and facilities to monitor several levels of the stack. It allows also to instrument the code in intrusive and non-intrusive way for getting information that allow the complex event processing so as the inference of complex event from simpler one. The integration of the tool with the Ontology, that is a research product of the CNR, will allow to close the loop between business manager to tester going through the developer.
When is the expected date of achievement in the project (Mth/yr)?
When is the time to market (Mth/yr)?
What are the costs to be incurred after the project and before exploitation?
Industrialization of the product in terms of orchestration with a powerful user interface and other costs related to a security testing of the product that is actually working in a safe environment. Currently, CNR is already taking proactive steps by proposing the utilization of Runtime Monitoring in the SERICS (Cod. PE00000014) and RESTART (Cod. PE00000001, CUP B53C22003970001) projects under the NRRP
MUR program, which is funded by the EU-NGEU.
What is the approximate price range of this result/price of licences?
The product is released under GPL3
What are the market size in Millions € for this result and relevant trend?
How will this result rank against competing products in terms of price/performance?
In terms of price, the tool is released under GPL3 so it does not have any impact on costs. In terms of performance: we do not execute yet any comparison with existing tools but we developed a system that is able to manage huge number of events (around 1-2 mil per day) with a desktop machine.
Who are the competitors for this result?
Ganglia, Nagios, Pandora
How fast and in what ways will the competition respond to this result?
Who are the partners involved in the result?
Who are the industrial partners interested in the result (partners, sponsors, etc.)?


Have you protected or will you protect this result? How? When?
A preliminary version of this result has been presented at CISIS-ICEUTE4 2021 and WEBIST5 2021. We are planning to prepare an extended contribution for a journal article by the end of the project.

Other results

Data Collection Tool

Data Collection Tool (DCT) stores information from relevant vulnerability related datasets, providing a single access point to information required by the vulnerability detection and forecasting tools developed in T3.3, as well as for the failure prediction tools developed in T4.2.

Vulnerability Detection Tool

Vulnerability Detection Tool will detect existing vulnerabilities within the source code which may lead to the successful execution of an attack.

Fuzzing Tool

Fuzzing Tool will test System Under Test (SUT) security vulnerabilities or inputs not contemplated that could compromise the system; as a black-box process, by using unintended or incorrect inputs and monitoring their corresponding outputs.

BIECO Project

SUBSCRIBE and become part of the BIECO community!

We don’t spam!

Share This