GitLab

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

- Now is header-only to make SensorBase happy

- Implementation has been split into a SensorMetadata class and a
MetadataStore one to simplify integration in DCDBPusher and Collect Agent

- If a subSampling value of 0 or lower is chosen for a sensor, it will
never be pushed out over MQTT/Cassandra and only kept in memory

- Now using references instead of pointers
- Return type is now bool

- If users specify a single timestamp (startTs==endTs) when performing
a sensor query through dcdbquery or libdcdb, a fuzzy sensor query is
performed, and the closest sensor reading to the target timestamp is
returned

- A regular expression (jobFilter) can be applied to the jobs' nodelists
to identify the jobs that need to be treated by each collectagent in a
cluster
- By default only the first node in the nodelist is considered, but this
behavior can be customized

- This plugin allows to write arbitrary sensor data to the local file system
- Removed the obsolete sink functionality in SensorBase
- Also fixed a minor bug concerning MQTT topic assignment in template analyzers

- When the start and end timestamps of a query are equal, it is enforced
that only one sensor value will be retrieved

- Staleness checks when performing sensor queries in the cache are
now enforced both in relative and absolute modes
- Fixed a race condition causing wrong results when performing queries
in absolute mode
- Changed logging in the TesterAnalyzer plugin

- Fixed a fair amount of bugs related to job analyzers
- Added a "getJobsInIntervalRunning" method to JobDataStore, to get
the list of jobs that were running in a certain time interval
- Some code refactoring for the JobDataStore class to reduce duplication
- Job analyzers have been tested and are working properly as of now

- Now supports also standard deviation and percentile computation
- Multiple output sensors per analyzer can be defined, each performing
a different aggregation task
- QueryEngine has been slightly modified so as not to clear the input
sensor reading buffer (if any), thus allowing to accumulate sensor
values with subsequent calls

- The MQTT topic of a sensor is now used to identify the file name of the
sink and is appended to the path given as input

- Template for Job Analyzers, derived from AnalyzerInterface

RESTHttpsServer: lower log level on socket shutdown to warning, as an error code does not necessarily indicate a problem

- Fixing a bug that caused endianness detection to not work properly
after switching to the new BOOST macros, causing dcdbquery and other
tools to break

- Analytics plugins can be now loaded and unloaded dynamically
- DCDBPusher now looks into the current configuration directory if no
path is supplied when loading/reloading a plugin

- Added a catch for an exception thrown when using on-demand analyzers
- Checking that the HTTPS server is actually running before stopping it in
the destructor

- 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