The history db was migrated and included in the observers module of the new Tower 4Clouds Repository
In the context of MODAClouds European project, the Politecnico di Milano was one of the partners involved in the development of the Monitoring Platform.
HistoryDB is a component that logs in a datastore (usually Apache Fuseki) a number of different requests, making it possible to check the evolution of the system step by step.
A queue (usually RabbitMQ) is used for decoupling the sub-component listening to the requests and the sub-component that manages the datastore.
Useful links to the documentation:
- A subscription is used instead of polling the queue: better performances should be expected.
- Now a fake message is sent at the beginning for each queue handled, so that the code could work with older versions of RabbitMQ.
- Better handling of failures: the fuseki and rabbitmq hosts are checked at the beginning and signaled if they're wrongly configured.
- Now an executor service is used also while adding messages to the datastore, fixing all the problems!
- Bug fixes.
- Better handling of the queue (maybe fixing some "too many files opened" bug).
- Two new parameters to the script "historydb" for launching fake messages at the beginning of the tool.
- Few bug fixes.
- First (actually and hopefully) working version. The previous one wasn't saving all the messages received.
- Added some other information in the "default" graph, as described in the datastore guide.
- First beta release!