- Data is correctly parsed from DCDBPusher, sent as JSON, and received
by collectagents
- Integration in libdcdb is still pending

- When building the SensorNavigator, trailing whitespace must be
stripped from the sensor names if they were shorter than 16 characters

- Fixed a bug that prevented pipelines in collectagent deployments
- Incremented the tolerance threshold of fuzzy queries to 1h
- Fixed the assignment of MQTT topics to job sensors

- Make clean might be required

- Now it is possible to perform queries on raw topics without doing
a lookup on the publishedsensors table, by using the -d option

- Removed the dlclose call on plugin unloads to avoid segmentation fault
issues at destruction time of boost thread objects due to failed symbol resolution
- QueryEngine in DCDBPusher does not block anymore while being updated,
but simply returns NULL

- In the new implementation the sensor map used to speed up access to
sensor data is rebuilt synchronously when plugins are reloaded/loaded/unloaded
- Any threads accessing the sensor query callback will block until
the update has finished

- New method is lock-based and compatible with all features (e.g. REST API)
in the framework
- Performance impact is expected to be negligible as race conditions will
not be frequent

- Template for Job Analyzers, derived from AnalyzerInterface

- Added documentation to the new SensorID implementation
- NOTE: virtual sensors will likely require some modifications due to
how topics are handled now ('/' separator clashing with divide symbol)

- String topics are now used across all of DCDB, up to Cassandra
- As of now, sensor names ALWAYS match MQTT topics
- Users can still define sensor "aliases" via dcdbconfig that point
to the same topics

- Textual MQTT topics working in dcdbpusher and data analytics framework
- REST API still not working properly
- Testing on the collectagent not performed yet

- a "filter" configuration parameter has been added, which is used
to discard sensor names when building the sensor navigator
- Can be used to e.g. build a sensor navigator in a collectagent
using only the sensors that are directly collected by it
- Implemented a switch to select leftmost/rightmost binary search
in CacheEntry, used for the QueryEngine

- Virtual threads can now be automatically aggregated for procstat and
sar groups
- the htVal parameter is the number of physical threads; corresponding
virtual threads are determined via modulo arithmetic
- Minor changes to AnalyticsController in collectagent

- The GlobalConfiguration class includes all shared logic to read and
parse configuration attributes for the collectagent and dcdbpusher
- The class is further expanded to add application-specific
configuration parameters and blocks

- The REST API of the data analytics framework is now functional in
the collectagent as well
- This implementation is temporary and should be replaced with a generic
REST API server whenever possible

- Integration of data analytics framework in collectagent complete
- REST API integration still pending
- Added some documentation to the code

- QueryEngine integration done (but not functional yet, debugging required)
- Changed behavior on exceptional conditions: if SensorNavigator or
AnalyticsManager initialization fails, termination follows
- Now the QueryEngine can also access output sensors of other Analyzers
- Minor bugfixes

- First step for integration of the analytics framework in the collectagent
- QueryEngine and REST API integration still missing
- Proper testing still to be done
- Added a probe function: the global config file is scanned before
initialization, and if no data analytics plugins are requested, no
sensor navigator is built