MODAClouds Monitoring Manager 1.7

• the rest api for attaching observers (POST /metrics/:id/observers) now returns a json object instead of plain text with more information, see the doc
• bug fix
• updated to knowledge-base-api 2.3.2
• updatad to data-collector-factory 0.3.4

MODAClouds Monitoring Manager 1.6

• added a Vagrantfile in the root of the repo for testing purpose, see the developer manual
• added a Vagrantfile in the released assembly for launching the entire monitoring platform using Vagrant, see the user manual
• fixed problem that did not prevent attaching observers with malformed URL
• added initial structure for the webapp
• fixed problem which did not exclude OutputMetric actions from new actions
• improved logging and error messages
• improved validation when updating/uploading the deployment model
• added API for retrieving a single rule
• fixed problem that caused errors when uninstalling rules that were using the same input metric
• implemented test observers and included in the released assembly, see the developer manual and user manual
• updated to knowledge-base-api 2.3.1
• updatad to data-collector-factory 0.3.3
• updated to qos-models 2.4.1

MODAClouds Monitoring Manager 1.5

• integrated with qos-models 2.4 for actions execution
• a private endpoint was implemented for internal communication and the port can be specified through the configuration, see the user manual
• implemented a new REST API for retrieving all resources in the model (GET /model/resources), see the doc

MODAClouds Monitoring Manager 1.4

• Aggregations and mathematical expressions can now be expressed in the OutputAction value parameter.
• The monitoring manager waits for the availability of the DDA and KB for 30 seconds before failing the startup
• Both DDA and KB are now cleaned and reset automatically at monitoring manager startup
• All REST api were bug fixed and are now working
• REST api changes: both GET /metrics and GET /metrics/{id}/observers now return a json file, see the doc
• KB and DDA are now run both on a single vagrant machine during integration test
• updated to csparqool 1.2.2
• updated to knowledge-base-api 2.2.1
• updatad to data-collector-factory 0.3.2
• updated to qos-models 2.3

MODAClouds Monitoring Manager 1.3.4

• the default list of metrics for monitoring rules can now be overwritten by a custom one

MODAClouds Monitoring Manager 1.3.3

• multiple configuration options added, see the doc
• updated to qos-models 2.2.1

Modaclouds Monitoring Manager 1.3.1

• packaged together with executable
• package assembly automated
• updated to data-collector-factory 0.3.1

MODAClouds Monitoring Manager 1.3

• implemented API: GET /model/resources/:id
• updated to csparqool 1.2.1
• updated to knowledge-base-api 2.2
• updatad to data-collector-factory 0.3
• updated to qos-models 2.2
• queries are now created according to the new qos-models 2.2 version of monitoring rules:
  • metricAggregation is optional
• outputMetric action in monitoring rules now accepts 3 parameters (resourceId, metric, value)
• sda are now just observers & data collectors from the monitoring manager perspective
• bug fixes

MODAClouds Monitoring Manager 1.2

• internalComponents can now be a monitoredTarget
• system properties can be used now besides environemnt variables
• inheritance was removed

v1.1.2: monitoring-manager

* Fixed a bug that didn't allow to upload a new model the first time
using the PUT method
* updated to qos-models 2.1.4: check qos-models change list for the new
of version of monitoring rules
* installation instructions updated (look at the documentation)